Thanks Adam and Tim … I see the diversion header but yeah it seems its from CFNA in general and has no hunt info so I don’t want to try a profile that “always” changes it to something else, in case it’s a diversion from something NOT the hunt. I did find this in a cisco pdf:
* Microsoft Phone System clients do not display alerting name or number when called from a UCM client.
I’m thinking I need to create delegates in Teams to replicate this as best I can
Jeffrey McHugh | Solutions Architect --end attach--
Fidelus Technologies
Named Best UC Provider in the USA<http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/>
+1-212-616-7801 office | www.fidelus.com
From: cisco-voip <cisco-voip-bounces@puck.nether.net> On Behalf Of Adam Pawlowski
Sent: Tuesday, August 8, 2023 8:19 AM
To: cisco-voip@puck.nether.net
Subject: [EXT] Re: [cisco-voip] MS Teams Direct Routing
[External Email]
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
It has been a minute, but I believe the RDP does not carry device specific headers that would indicate hunt group info (if that’s how that is done) , but I couldn’t find anything else on how that worked when prowling around.
You do get these though:
Diversion: sip:1248@10.100.101.41;reason=follow-me;privacy=off;screen=yes
Diversion: "William Shakespeare" sip:1248@10.100.101.41;reason=unconditional;privacy=off;screen=yes
But that comes from the original CFNA to hunt pilot, so that probably doesn’t help with what you’re doing.
What sort of header support does Teams have for diversion headers? Does it at least display “For William Shakespeare” or something ?
Adam Pawlowski
Network Engineer?| Network and Communication Services
University at Buffalo Information Technology (UBIT)
243 Computing Center, Buffalo, NY 14260
[cid:image001.png@01D9C9D6.3CC72A10]
From: cisco-voip <cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net>> On Behalf Of Jeffrey McHugh
Sent: Monday, August 7, 2023 10:16 AM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] MS Teams Direct Routing
Morning folks .. curious as to what, if anything, folks are doing with MS teams direct routing via CUBE and hunt groups in CUCM? We have a client that’s looking to throw out jabber/Webex for softphone but keep CUCM hardphones. They have a quite a few hunts and would like to keep the CUCM hunt functionality intact while routing the line group DN’s to MS Teams via SNR. My particular issue is this:
What I’m seeing is that CUCM sends the initial invite, to the DNs of the users in a line group, to CUBE with the calling party name of the user being called and no info/indication that it’s a hunt. For instance, if you’re in a line group that rings in jabber, you see that the call is for that hunt group. In my scenario, in Teams, Teams only shows that the incoming call is to the user originally being called and not from the hunt.
So flow is like this … user Albert Einstein calls William Shakespeare, William Shakespeare’s devices ring, then covers to a broadcast hunt. Users Nikoal Tesla and Alexander Graham Bell are in that hunt group and in Webex and jabber we see the call is for the hunt group.. On Tesla and Bell’s MS Teams client, they see the incoming call from Albert Einstein not that its from his hunt coverage.
Snippet of original invite from CUCM to CUBE (albert Einstein being the original caller and the FROM: sip:+16462931240@10.104.253.47 being the 4 digit to e164 translation to route into MS Teams via SNR):
Received:
INVITE sip:+16462931240@10.104.253.47:5060 SIP/2.0
Via: SIP/2.0/TCP 10.100.101.41:5060;branch=z9hG4bK26f30b32a44dc2
From: "| Albert Einstein | March 14, 1879" sip:+16462931236@10.100.101.41;tag=3962664~ec5b4b96-a721-4d7a-97e1-93e2cb320577-17937987
To: sip:+16462931240@10.104.253.47
Date: Mon, 07 Aug 2023 14:12:04 GMT
Call-ID: 61229780-1ef1532f-26efc7-2965640a@10.100.101.41<mailto:61229780-1ef1532f-26efc7-2965640a@10.100.101.41>
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM14.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: sip:10.100.101.41:5060;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 00002db800105000a000ef3dfa7b6e40;remote=00000000000000000000000000000000
Cisco-Guid: 1629656960-0000065536-0000000299-0694510602
Session-Expires: 1800
Diversion: sip:1248@10.100.101.41;reason=follow-me;privacy=off;screen=yes
Diversion: "William Shakespeare" sip:1248@10.100.101.41;reason=unconditional;privacy=off;screen=yes
P-Asserted-Identity: "| Albert Einstein | March 14, 1879" sip:+16462931236@10.100.101.41
Remote-Party-ID: "| Albert Einstein | March 14, 1879" sip:+16462931236@10.100.101.41;party=calling;screen=yes;privacy=off
Contact: sip:+16462931236@10.100.101.41:5060;transport=tcp;video;audio;+u.sip!devicename.ccm.cisco.com="CSFAEINSTEIN";bfcp;x-cisco-client=desktop
Max-Forwards: 69
Content-Length: 0
Jeffrey McHugh | Solutions Architect --end attach--
[cid:image002.png@01D9C9D6.3CC72A10]<http://www.fidelus.com/>
Fidelus Technologies, LLC
Named Best UC Provider in the USA<http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/>
300 Knickerbocker Rd, Suite 3300, Cresskill, NJ 07626
+1-212-616-7801 office | +1-212-616-7850 fax | www.fidelus.com<http://www.fidelus.com/>
[cid:image003.png@01D9C9D6.3CC72A10]<http://www.linkedin.com/company/fidelus-technologies/products>[cid:image004.png@01D9C9D6.3CC72A10]<http://www.twitter.com/FidelusUCC>[cid:image005.png@01D9C9D6.3CC72A10]<http://www.facebook.com/FidelusUCC>
Disclaimer - This email and any files transmitted with it are confidential and intended solely for the person(s) addressed to. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Fidelus Technologies, LLC. Warning: Although Fidelus Technologies, LLC has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
* Microsoft Phone System clients do not display alerting name or number when called from a UCM client.
I’m thinking I need to create delegates in Teams to replicate this as best I can
Jeffrey McHugh | Solutions Architect --end attach--
Fidelus Technologies
Named Best UC Provider in the USA<http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/>
+1-212-616-7801 office | www.fidelus.com
From: cisco-voip <cisco-voip-bounces@puck.nether.net> On Behalf Of Adam Pawlowski
Sent: Tuesday, August 8, 2023 8:19 AM
To: cisco-voip@puck.nether.net
Subject: [EXT] Re: [cisco-voip] MS Teams Direct Routing
[External Email]
CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe.
It has been a minute, but I believe the RDP does not carry device specific headers that would indicate hunt group info (if that’s how that is done) , but I couldn’t find anything else on how that worked when prowling around.
You do get these though:
Diversion: sip:1248@10.100.101.41;reason=follow-me;privacy=off;screen=yes
Diversion: "William Shakespeare" sip:1248@10.100.101.41;reason=unconditional;privacy=off;screen=yes
But that comes from the original CFNA to hunt pilot, so that probably doesn’t help with what you’re doing.
What sort of header support does Teams have for diversion headers? Does it at least display “For William Shakespeare” or something ?
Adam Pawlowski
Network Engineer?| Network and Communication Services
University at Buffalo Information Technology (UBIT)
243 Computing Center, Buffalo, NY 14260
[cid:image001.png@01D9C9D6.3CC72A10]
From: cisco-voip <cisco-voip-bounces@puck.nether.net<mailto:cisco-voip-bounces@puck.nether.net>> On Behalf Of Jeffrey McHugh
Sent: Monday, August 7, 2023 10:16 AM
To: cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>
Subject: [cisco-voip] MS Teams Direct Routing
Morning folks .. curious as to what, if anything, folks are doing with MS teams direct routing via CUBE and hunt groups in CUCM? We have a client that’s looking to throw out jabber/Webex for softphone but keep CUCM hardphones. They have a quite a few hunts and would like to keep the CUCM hunt functionality intact while routing the line group DN’s to MS Teams via SNR. My particular issue is this:
What I’m seeing is that CUCM sends the initial invite, to the DNs of the users in a line group, to CUBE with the calling party name of the user being called and no info/indication that it’s a hunt. For instance, if you’re in a line group that rings in jabber, you see that the call is for that hunt group. In my scenario, in Teams, Teams only shows that the incoming call is to the user originally being called and not from the hunt.
So flow is like this … user Albert Einstein calls William Shakespeare, William Shakespeare’s devices ring, then covers to a broadcast hunt. Users Nikoal Tesla and Alexander Graham Bell are in that hunt group and in Webex and jabber we see the call is for the hunt group.. On Tesla and Bell’s MS Teams client, they see the incoming call from Albert Einstein not that its from his hunt coverage.
Snippet of original invite from CUCM to CUBE (albert Einstein being the original caller and the FROM: sip:+16462931240@10.104.253.47 being the 4 digit to e164 translation to route into MS Teams via SNR):
Received:
INVITE sip:+16462931240@10.104.253.47:5060 SIP/2.0
Via: SIP/2.0/TCP 10.100.101.41:5060;branch=z9hG4bK26f30b32a44dc2
From: "| Albert Einstein | March 14, 1879" sip:+16462931236@10.100.101.41;tag=3962664~ec5b4b96-a721-4d7a-97e1-93e2cb320577-17937987
To: sip:+16462931240@10.104.253.47
Date: Mon, 07 Aug 2023 14:12:04 GMT
Call-ID: 61229780-1ef1532f-26efc7-2965640a@10.100.101.41<mailto:61229780-1ef1532f-26efc7-2965640a@10.100.101.41>
Supported: timer,resource-priority,replaces
Min-SE: 1800
User-Agent: Cisco-CUCM14.0
Allow: INVITE, OPTIONS, INFO, BYE, CANCEL, ACK, PRACK, UPDATE, REFER, SUBSCRIBE, NOTIFY
CSeq: 101 INVITE
Expires: 180
Allow-Events: presence, kpml
Supported: X-cisco-srtp-fallback
Supported: Geolocation
Call-Info: sip:10.100.101.41:5060;method="NOTIFY;Event=telephone-event;Duration=500"
Call-Info: <urn:x-cisco-remotecc:callinfo>;x-cisco-video-traffic-class=DESKTOP
Session-ID: 00002db800105000a000ef3dfa7b6e40;remote=00000000000000000000000000000000
Cisco-Guid: 1629656960-0000065536-0000000299-0694510602
Session-Expires: 1800
Diversion: sip:1248@10.100.101.41;reason=follow-me;privacy=off;screen=yes
Diversion: "William Shakespeare" sip:1248@10.100.101.41;reason=unconditional;privacy=off;screen=yes
P-Asserted-Identity: "| Albert Einstein | March 14, 1879" sip:+16462931236@10.100.101.41
Remote-Party-ID: "| Albert Einstein | March 14, 1879" sip:+16462931236@10.100.101.41;party=calling;screen=yes;privacy=off
Contact: sip:+16462931236@10.100.101.41:5060;transport=tcp;video;audio;+u.sip!devicename.ccm.cisco.com="CSFAEINSTEIN";bfcp;x-cisco-client=desktop
Max-Forwards: 69
Content-Length: 0
Jeffrey McHugh | Solutions Architect --end attach--
[cid:image002.png@01D9C9D6.3CC72A10]<http://www.fidelus.com/>
Fidelus Technologies, LLC
Named Best UC Provider in the USA<http://www.fidelus.com/fidelus-technologies-named-best-unified-communications-provider-in-the-usa/>
300 Knickerbocker Rd, Suite 3300, Cresskill, NJ 07626
+1-212-616-7801 office | +1-212-616-7850 fax | www.fidelus.com<http://www.fidelus.com/>
[cid:image003.png@01D9C9D6.3CC72A10]<http://www.linkedin.com/company/fidelus-technologies/products>[cid:image004.png@01D9C9D6.3CC72A10]<http://www.twitter.com/FidelusUCC>[cid:image005.png@01D9C9D6.3CC72A10]<http://www.facebook.com/FidelusUCC>
Disclaimer - This email and any files transmitted with it are confidential and intended solely for the person(s) addressed to. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Fidelus Technologies, LLC. Warning: Although Fidelus Technologies, LLC has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
Attached Files:
-
image001.png (2.43 KB)
-
image002.png (1.94 KB)
-
image003.png (1.46 KB)
-
image004.png (1.49 KB)
-
image005.png (1.42 KB)