After running the “Easy Config Wizard” to integrate the SBC with Teams Direct Routing, the customer informed me that they need to use another name for the SBC
So, I have done the following steps
- Installed a new certificate that contains a subject name that is equal to the new name of the SBC
- Register the new name of the SBC using the PowerShell command New-CsOnlinePSTNGateway
- Changed all the voice routing policies to use the new
- Unregistered the old name of the SBC using Remove-CsOnlinePSTNGateway
- Changed the name of the SBC using the web interface under Settings tab > System > “Node-Level Settings“
After that I noticed that the calls are failing and when I checked Teams Admin Center, I noticed that there is a warning next to the new name of SBC under Voice > Direct Routing
If clicked the warning, and I got the details below
The title of the warning was “No SIP Option warning” and the body of the warning was
The Session Border Controller exists in our database (your administrator created it using the command New-CSOnlinePSTNGateway). But we have difficulties determining SIP Options status. Please check in 15 minutes
Although there are other reasons for this warning, I guessed that the reason was that the SBC is still communicating with Office 365 servers with its old name and that would cause the TLS to fail
I have tried the steps under the section Changing Host Profile Settings below and that fixed the issue.
But first, here are the steps for changing the name of the SBC under “Node-Level Settings”
Changing the Name of the SBC
In case, you haven’t changed the name of the SBC under “Node-Level Settings“, here are the steps
On the web interface, click on the Settings tab, expand System and click on Node-Level Settings
The Node-Level Settings are shown
Under Host Information, type the new Host Name and Domain Name if needed
Click on Apply
Changing Host Profile Settings
Go to Settings Tab > SIP > SIP Profiles and select the SIP Profile that is used for Teams Direct Routing integration
Usually, you have used “Easy Config Wizard” to create the integration with Teams, so the name of the SIP Profile is “Scenario_Name: Teams Direct Routing Profile”
In my case the Scenario Name I have used during the running “Easy Config Wizard” was Teams, that is why the name of the SIP profile is “Teams: Teams Direct Routing Profile” as shown in the image below
The following is what the SIP Profile for Teams Direct Routing would look like
Scroll Down to “SDP Customization”
Change “Origin Field Username” to the new name of the SBC and click apply
With this, your SBC will communicate to Office 365 / Teams server using the new name
Note:
- Don’t forget to register the new name of SBC using the PowerShell command New-CsOnlinePSTNGateway
- Don’t forget to install a certificate that uses the new name