Call2Teams - Customers/Partners
Users who have used Teams Direct Routing may have used powershell commands such as New-CsOnlinePstnGateway to tell Microsoft about the SBC.
This will have caused it to display in the Teams Direct Routing Dashboard.
Multi Tenant Carriers
Microsoft have a different model for multi-tenant carriers such Call2Teams, where the PSTN Gateways are created in the platform carrier tenant and do not appear in the customer's Microsoft 365 tenant.
By adding the domains to the customer's Microsoft 365 tenant it allows for Voice Routes to refer to the PSTN Gateways in the Call2Teams tenant.
This means they will not appear in the Teams Direct Routing Dashboard.
- 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 to publish DNS records for the SBC.
- This approach uses wildcard SSL certificates, reducing delay as there is no need to acquire a specific certificate.
- The carrier can fine-tune the PSTN Gateway settings without needing customer involvement.
For more information about operating Direct Routing SBCs in carrier mode review this Microsoft article:
Please note Dstny Automate cannot be held responsible for the content of any third-party documentation offered.