Forum Discussion
Force Teams-to-Teams calls to use Direct Routing SBC
Hi StevenC365
The problem is that we combine Teams with another platform using Direct Routing (hosting model). Teams in "on the top", so to speak. So we have a feature rich PBX underneath, with desk phones, cell phones, advanced voice recording, statistics etc. And the users can then decide if inbound calls should be sent to their desk phone, cell phone, Teams, etc. (or a combination of those, and overflow, VM, etc., etc.).
But when Teams-to-Teams calls are not routed via the PSTN voice route/Direct Routing, we cannot control the call. Meaning our call rules are not used - so if Alice receives an inbound call, that normally goes to her cell phone, Teams and desk phone, that doesn't happen if it's another Teams user that calls her, because we don't get the call.
From the artickle you linked to (thanks, btw :-)), the location-based routing is configured on the PSTN gateway (SBC). But in the Direct Routing (hosting model) setup we only have a voice route and no SBC.
So my thoughts was if there was an option in Teams, to force all calls to break out - for us to return them to the destination user, if it's another Teams user.
BR,
Kasper
Can you clarify what you mean by your "Direct Routing (hosted model)" doesn't have an SBC? Even if you were to do direct hosted with a carrier, there should still be an SBC involved. What's the output of Get-CsOnlinePstnGateway?
- KasperLethAug 03, 2020Copper Contributor
Hi jangliss
No, the "new" (not so new anymore) way does not require a PSTN gateway on the tenants. Running your command returns nothing.
From https://docs.microsoft.com/en-us/microsoftteams/direct-routing-sbc-multiple-tenants
"In the customer tenant, the carrier need only to add the derived trunk FQDN to the voice routing policies of the users. There is no need to run New-CSOnlinePSTNGateway for a trunk."
So there is only a voice route on the tenant, no SBC/PSTN gateway.