Teams client failing to create notification toast pop for incoming call

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

4 Replies

@Jingxian Li out of curiosity what is the Teams client version of the affected user?

@GerardNH 

The problem seems to do with this user. We tried this user on both 32bits and 64 bits machines and the result is the same:

 

1.2.00.23456 (64-bit)

1.2.00.23456 (32 bit)

 

Thanks

 

@Jingxian Li what data center / forest / pool info can you share?

@GerardNH 

 

United States datacenters

 

Domain: eidevnzonline.biz

User: dughall stiubhart