Home

Incoming call failing to create toast pop notifcation

%3CLINGO-SUB%20id%3D%22lingo-sub-825728%22%20slang%3D%22en-US%22%3EIncoming%20call%20failing%20to%20create%20toast%20pop%20notifcation%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-825728%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20contact%20center%20solution%20built%20off%20a%20sip%20trunk%20via%20direct%20route%20SBC%20to%20teams%20environment.%20When%20the%20system%20delivers%20a%20call%20to%20this%20particular%20teams%20client%20via%20direct%20route%2C%20the%20teams%20client%20fails%20to%20create%20a%20notification%20toast%20pop%20with%20the%20following%20type%20script%20error%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2019-08-27T20%3A14%3A43.304Z%20Err%20Unhandled%20exception.%20TypeError%3A%20Cannot%20read%20property%20'length'%20of%20undefined%2C%20cause%3A%20%2C%20stack%3A%20e.djb2_hash%40%3CA%20href%3D%22https%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.2-app.min-4528048e.js%3A4%3A350330%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.2-app.min-4528048e.js%3A4%3A350330%3C%2FA%3E%26gt%3B%20o.createNotificationData%40%3CA%20href%3D%22https%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.1-app.min-3ff72090.js%3A1160%3A16072%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.1-app.min-3ff72090.js%3A1160%3A16072%3C%2FA%3E%26gt%3B%20o.createVideoNotificationData%40%3CA%20href%3D%22https%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.1-app.min-3ff72090.js%3A1160%3A8755%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.1-app.min-3ff72090.js%3A1160%3A8755%3C%2FA%3E%26gt%3B%20o.createVideoCallNotification%40%3CA%20href%3D%22https%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.1-app.min-3ff72090.js%3A1160%3A8335%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fstatics.teams.microsoft.com%2Fhashedjs%2F3.1-app.min-3ff72090.js%3A1160%3A8335%3C%2FA%3E%26gt%3B...%3CBR%20%2F%3E2019-08-27T20%3A14%3A43.299Z%20Inf%20CallingNotificationServiceImplementation%3A%20notificationData%20ringtoneType%20is%200%2C%20%5Bcall%5D%5BincomingCall%5D%5BringtoneType%3A%7B0%7D%5D%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3D%3C%2FP%3E%3CP%3EThe%20packet%20sent%20to%20SBC%20from%20CC%20system%20looks%20like%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVia%3A%20SIP%2F2.0%2FUDP%2010.213.14.18%3A5080%3Brport%3Bbranch%3Dz9hG4bK9pQe8X4y2cHFr%3CBR%20%2F%3EMax-Forwards%3A%2069%3CBR%20%2F%3EFrom%3A%20%226497782140%22%20%26lt%3B6497782140%26gt%3B%3Btag%3DS2FXc656c184g%3CBR%20%2F%3ETo%3A%20%26lt%3B%26lt%3B82180%26gt%3B%26lt%3B82180%26gt%3Bsip%3A82180%4010.50.12.241%26gt%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%26lt%3B82180%26gt%3B%3CBR%20%2F%3ECall-ID%3A%203a7a7ffb-43bf-1238-3fa9-031fe2c6eaa2%3CBR%20%2F%3ECSeq%3A%208919176%20INVITE%3CBR%20%2F%3EContact%3A%26nbsp%3B%20%3CGW%3E%3CGW%3E%3CGW%3E%3CBR%20%2F%3EUser-Agent%3A%20FreeSWITCH-mod_sofia%2F1.8.7~32bit%3CBR%20%2F%3EAllow%3A%20INVITE%2C%20ACK%2C%20BYE%2C%20CANCEL%2C%20OPTIONS%2C%20MESSAGE%2C%20INFO%2C%20UPDATE%2C%20REGISTER%2C%20REFER%2C%20NOTIFY%3CBR%20%2F%3ESupported%3A%20timer%2C%20path%2C%20replaces%3CBR%20%2F%3EAllow-Events%3A%20talk%2C%20hold%2C%20conference%2C%20refer%3CBR%20%2F%3EContent-Type%3A%20application%2Fsdp%3CBR%20%2F%3EContent-Disposition%3A%20session%3CBR%20%2F%3EContent-Length%3A%20672%3CBR%20%2F%3Ehistory-info%3A%20sip%3A6497782140_c4b51676-f915-48b5-82f0-e977175d8ac2_FS%4010.213.14.18%3CBR%20%2F%3EX-FS-Support%3A%20update_display%2Csend_info%3CBR%20%2F%3ERemote-Party-ID%3A%20%226497782140%22%20%26lt%3B6497782140%26gt%3B%3Bparty%3Dcalling%3Bscreen%3Dyes%3Bprivacy%3Doff%3C%2FGW%3E%3C%2FGW%3E%3C%2FGW%3E%3CP%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20time%20out%2C%20the%20system%20pulls%20the%20call%20back%20then%20this%20call%20is%20recorded%20as%20a%20missed%20call%20on%20teams%20client.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20weird%20thing%20is%20that%20this%20exact%20scenario%20works%20for%20every%20other%20user%20conffigured%20on%20the%20tenant.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20is%20appreciated!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJosie%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CLINGO-LABS%20id%3D%22lingo-labs-825728%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Jingxian Li
New Contributor

Hi there,

 

We have a contact center solution built off a sip trunk via direct route SBC to teams environment. When the system delivers a call to this particular teams client via direct route, the teams client fails to create a notification toast pop with the following type script error:

 

2019-08-27T20:14:43.304Z Err Unhandled exception. TypeError: Cannot read property 'length' of undefined, cause: , stack: e.djb2_hash@https://statics.teams.microsoft.com/hashedjs/3.2-app.min-4528048e.js:4:350330 > o.createNotificationData@https://statics.teams.microsoft.com/hashedjs/3.1-app.min-3ff72090.js:1160:16072 > o.createVideoNotificationData@https://statics.teams.microsoft.com/hashedjs/3.1-app.min-3ff72090.js:1160:8755 > o.createVideoCallNotification@https://statics.teams.microsoft.com/hashedjs/3.1-app.min-3ff72090.js:1160:8335 >...
2019-08-27T20:14:43.299Z Inf CallingNotificationServiceImplementation: notificationData ringtoneType is 0, [call][incomingCall][ringtoneType:{0}]

 

================================================

The packet sent to SBC from CC system looks like this:

 

Via: SIP/2.0/UDP 10.213.14.18:5080;rport;branch=z9hG4bK9pQe8X4y2cHFr
Max-Forwards: 69
From: "6497782140" <sip:6497782140@10.213.14.18>;tag=S2FXc656c184g
To: <<sip:82180@10.50.12.241><sip:82180@10.50.12.241>sip:82180@10.50.12.241></sip:82180@10.50.12.241></sip:82180@10.50.12.241><sip:82180@10.50.12.241>
Call-ID: 3a7a7ffb-43bf-1238-3fa9-031fe2c6eaa2
CSeq: 8919176 INVITE
Contact:  <sip:gw+teamssbcnz@10.213.14.18:5080;transport=udp;gw=teamssbcnz><sip:gw+teamssbc@10.213.14.18:5080;transport=udp;gw=teamssbc><sip:gw+teamssbcnz@10.213.14.18:5080;transport=udp;gw=teamssbcnz>
User-Agent: FreeSWITCH-mod_sofia/1.8.7~32bit
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 672
history-info: sip:6497782140_c4b51676-f915-48b5-82f0-e977175d8ac2_FS@10.213.14.18
X-FS-Support: update_display,send_info
Remote-Party-ID: "6497782140" <sip:6497782140@10.213.14.18>;party=calling;screen=yes;privacy=off</sip:6497782140@10.213.14.18></sip:gw+teamssbcnz@10.213.14.18:5080;transport=udp;gw=teamssbcnz></sip:gw+teamssbc@10.213.14.18:5080;transport=udp;gw=teamssbc></sip:gw+teamssbcnz@10.213.14.18:5080;transport=udp;gw=teamssbcnz></sip:82180@10.50.12.241></sip:6497782140@10.213.14.18>

 

After time out, the system pulls the call back then this call is recorded as a missed call on teams client.

 

The weird thing is that this exact scenario works for every other user conffigured on the tenant.

 

Any help is appreciated!

 

Josie

 

Related Conversations