Applies To
Call2Teams - partner
Overview
Microsoft have announced they will be making some changes to Teams Direct Routing.
"Note: Starting on January 3, 2022, Direct Routing will stop processing SIP requests which have Replaces headers."
What you need to know
This Microsoft change doesn’t impact the platform at all and existing call flows will continue to work as expected.
What does this mean?
Replaces headers, as you’d perhaps expect, are used on an INVITE such that a new INVITE (call) can take over/replace an existing call. There are scenarios where INVITEs are sent in to the platform and a Replaces is used (e.g. some transfer scenarios or conference scenarios). These will continue to work the way they current do, which is the packet goes all the way through to the core SBC, at that point there is a configuration setting to ‘Handle Locally’. That basically means that the core SBC will handle the header/INVITE, and nothing will be sent upstream to Microsoft. The core SBC will handle closing off the old call and joining up the new one.
Further reading
This is the full MS announcement:
Direct Routing will stop processing SIP requests which have 'Replaces' headers
MC299922 · FEKA ICT
We'll be making some changes to Teams Direct Routing.
Note: Starting on January 3, 2022, Direct Routing will stop processing SIP requests which have Replaces headers.
When will this happen:
We will begin this change in early January '22 and expect to complete mid-January '22.
How this will affect your organization:
When this change is implemented, Direct Routing will reject SIP requests that have Replaces headers defined.
What you need to do to prepare:
Please check your Session Border Controller configuration and be sure that you are not using Replaces headers in SIP requests.
Learn more:
View this message in the Microsoft 365 admin center
Disclaimer
Please note Qunifi cannot be held responsible for the content of any third-party documentation offered.