Call2Teams - Customers
Users of Teams Direct Routing may be used to using PowerShell commands such as New-CsOnlinePstnGateway to tell Microsoft about their Session Border Controller.
Doing this caused it to display in the Teams Direct Routing Dashboard.
This is not the case for Call2Teams.
Microsoft have a different model for multi-tenant carriers such as Call2Teams.
In this model the PSTN Gateways are created in a Call2Teams carrier tenant and do not appear in the customer's Office 365 tenant.
Adding the domains to the customer's Office 365 tenant allows their Voice Routes to refer to the PSTN Gateways in the Call2Teams tenant.
The result is that this means they will not appear in the customer's Teams Direct Routing Dashboard.
The reasons for this are as follows:
- Microsoft only need one set of SIP OPTIONS pings per SBC rather than the hundreds that would be sent if every customer configured their own PSTN Gateways.
- There is no need for customers to publish DNS records for the SBC.
- This approach uses wildcard SSL certificates, removing delay as there is no need to acquire a specific certificate for each customer.
- The carrier can fine-tune the PSTN Gateway settings without needing the customer's involvement.
See this article for more information about operating Direct Routing SBCs in carrier mode:
Please note Dstny Automate cannot be held responsible for the content of any third-party documentation offered.