I recently migrate a Teams Direct Routing pair of SBCs from one tenant to another, in other words its a tenant to tenant migration but not a data migration but a pair of SBC :). In this scenario it was full active and running calls like Local SBC since these were connected to different tenant. To explain this clearly, Ill take as an example Tenant A to Tenant B. However I'm planning to discuss in the future, how these calls were connected via tenant A to tenant B SBCs in a different article but this article is about simple mistake and the experience during the preparation to migrate the SBC Tenant A to Tenant B.
Media bypass enabled
Its common recommendation and best practice coming from Microsoft Teams Direct Routing is use media bypass for all the direct routing deployment or environments, so that call can connect with less RTT (Round Trip Time). This will be totally big topic and scenario can be easy to complex depend on your environment.
Required dependency
You cannot run Media Bypass in Teams Direct Routing without enabling ICE Lite on your SBC configuration, the media is kept directly between the Teams user to SBC, Following diagram explain,
Following call flow diagram explain better
Media bypass uses ICE protocol (RFC5245), to enabled end to end you may need to allow correct range of Microsoft Teams Optimize IPs, URLs, and Ports. Microsoft 365 IP, URLs and Ports are important to keep part of every 3 months maintainer cycles to apply if any changes.
Mistake what i did
Following configuration is my SIP Trunk to Direct Routing, i have already done with Roots certificates. DNS A records, Firewall NAT as well as security policy related to this. Signal Group configuration in the Ribbon SBC completed as well.
I can see options are good, able to Ring calls but cant establish a call, but calls are not establish. I found that i have missed to enabled ICE support on NAT Traversal in the MS Teams Direct Routing Signal Trunk.
Success
Ribbon logs during success shows, ICE negotiation
v=0
o=- 0 0 IN IP4 52.115.170.249
s=session
c=IN IP4 52.115.170.249
b=CT:4000
t=0 0
m=audio 3479 RTP/SAVP 104 102 9 111 18 0 8 103 97 13 118 119 101
a=rtcp:3480
a=ice-ufrag:0jUT
a=ice-pwd:87ihU5oy0fdzg+aZ/9/SOOdn
a=rtcp-mux
a=candidate:8 1 UDP 1258287615 52.115.170.249 3479 typ relay raddr XXXXX rport 50000 MTURNID 15287110339259904237
a=candidate:8 2 UDP 1258287102 52.115.170.249 3480 typ relay raddr XXXXX rport 50001 MTURNID 16012866942974815766
Fixed
Comments
Post a Comment