CUCM-Teams calling name presentation

Andre80 · ‎06-29-2023

Hello,

I have an integration between CUCM and an Audiocodes SBC configured for Teams Direct Routing. SBC was configured as for Audiocodes documentation.

I'm observed a very strange issue with calling name presentation for calls from CUCM to Teams. When the call arrive in Teams desktop client or web client, the toast show only the number and not the name. The strange thing is that in the call history the call appear with the name. In the Teams client for Android, when the call arrive appear with name and number so I suppose that CUCM pass all the relevant informations about calling name to Teams.

Is there something that can I can check on CUCM side (trunk, sip profile etc.) to try to fix this issue?

Thanks!

Roger Kallberg · ‎06-29-2023

If you share the output from a debug of the SIP message we might be able to help you out. At least it should show if you get the information passed in the SIP dialogue.

Andre80 · ‎06-29-2023

Thanks for your reply, here the call flow

Roger Kallberg · ‎06-29-2023

From what I can tell your SBC is stripping the name off from the information that the CM sends. In all steps from the CM it includes a name, but it is not present in the invite sent from the SBC to MS.

Invite from CM to SBC

F1 | INVITE | SIP_CUCM (172.16.4.2) -> Device (172.16.127.31) | 12:36:41

INVITE sip:249@172.16.127.31:5060 SIP/2.0
Via: SIP/2.0/UDP 172.16.4.2:5060;branch=z9hG4bK117b2bf51db9aef
From: "SANTARELLI ROBERTO" <sip:467@172.16.4.2>;tag=60481106~00f5479c-a0f7-4793-9618-3b2bf7004721-46609629
To: <sip:249@172.16.127.31>
Date: Thu, 22 Jun 2023 10:37:07 GMT
Call-ID: baec1100-49412453-6c6476-20410ac@172.16.4.2
Supported: timer,resource-priority,replaces
Min-SE:  3600
User-Agent: Cisco-CUCM11.5
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 120
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback,X-cisco-original-called
Call-Info: <sip:172.16.4.2:5060>;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 30e2449e00105000a00000ccfca61503;remote=00000000000000000000000000000000
Cisco-Guid: 3136033024-0000065536-0000110973-0033820844
Session-Expires:  86400
P-Asserted-Identity: "SANTARELLI ROBERTO" <sip:467@172.16.4.2>
Remote-Party-ID: "SANTARELLI ROBERTO" <sip:467@172.16.4.2>;party=calling;screen=yes;privacy=off
Contact: <sip:467@172.16.4.2:5060>;+u.sip!devicename.ccm.cisco.com="SEP00CCFCA61503"
Max-Forwards: 69
Content-Type: application/sdp
Content-Length: 546


v=0
o=CiscoSystemsCCM-SIP 60481106 1 IN IP4 172.16.4.2
s=SIP Call
c=IN IP4 172.16.4.74
b=TIAS:64000
b=AS:64
t=0 0
m=audio 30196 RTP/AVP 114 9 8 0 116 18 101
b=TIAS:64000
a=rtpmap:114 opus/48000/2
a=fmtp:114  maxplaybackrate=16000;sprop-maxcapturerate=16000;maxaveragebitrate=64000;stereo=0;sprop-stereo=0;usedtx=0
a=rtpmap:9 G722/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:0 PCMU/8000
a=rtpmap:116 iLBC/8000
a=maxptime:20
a=fmtp:116 mode=20
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15

Invite from SBC to MS

F16 | INVITE (SDP) | SIP_Teams (52.114.76.76) -> Device (172.16.127.31) | 12:36:57

INVITE sip:467@sbt.xxxxgroup.it:5067;transport=tls SIP/2.0
FROM: <sip:+39xxxx5874249@172.16.127.31>;tag=79ae22a1c48649e4bac60c4fc0711c0d
TO: <sip:467@sbt.xxxxgroup.it>;tag=1c1258979179
CSEQ: 1 INVITE
CALL-ID: 925242328226xxx@sbt.xxxxgroup.it
MAX-FORWARDS: 70
VIA: SIP/2.0/TLS 52.114.76.76:5061;branch=z9hG4bK202fxxx
CONTACT: <sip:api-du-b-euno.pstnxx.microsoft.com:443;x-i=dcc3d91d-15ca-4225-b872-92d4eeb2ed9b;x-c=0c44e0d7768150248492d9e190081efd/s/1/6621f6c214c448d9a61067cf586e8d9b>
CONTENT-LENGTH: 964
MIN-SE: 90
SUPPORTED: timer
USER-AGENT: Microsoft.PSTNHub.SIPProxy v.2023.6.21.5 i.EUNO.5
CONTENT-TYPE: application/sdp
ALLOW: INVITE,ACK,OPTIONS,CANCEL,BYE,NOTIFY
SESSION-EXPIRES: 86400;refresher=uas

v=0
o=- 120207 2 IN IP4 127.0.0.1
s=session
c=IN IP4 52.112.144.151
b=CT:10000000
t=0 0
m=audio 52754 RTP/SAVP 104 9 103 111 18 0 8 97 101 13 118
c=IN IP4 52.112.144.151
a=rtcp:52755
a=ice-ufrag:+4ey
a=ice-pwd:xxx
a=candidate:1 1 UDP 1862270719 52.112.144.151 52754 typ prflx raddr 10.0.32.199 rport 52754
a=candidate:1 2 UDP 1862270462 52.112.144.151 52755 typ prflx raddr 10.0.32.199 rport 52755
a=remote-candidates:1 85.37.34.141 7024 2 85.37.34.141 7025
a=label:main-audio
a=mid:1
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:M/xxx/56e2a|2^31
a=sendrecv
a=rtpmap:104 SILK/16000
a=rtpmap:9 G722/8000
a=rtpmap:103 SILK/8000
a=rtpmap:111 SIREN/16000
a=fmtp:111 bitrate=16000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000
a=rtpmap:97 RED/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-16
a=rtpmap:13 CN/8000
a=rtpmap:118 CN/16000
a=ptime:20

I suggest that you look in the settings of your SBC to see what can be done to change this behaviour. As it’s not a Cisco product you might need to look elsewhere for help on this.