Forum Discussion
fanzhangrob
Sep 19, 2019Copper Contributor
Derived Trunk for Teams direct routing hosting model
I am working on a case about Teams direct routing hosting model. After going through the article about 'Configure a Session Border Controller for multiple tenants'
https://docs.microsoft.com/en-us/microsoftteams/direct-routing-sbc-multiple-tenants
I found the part describing the derived trunk from customer tenant to carrier's tenant confusing.
Quoting from the article
' Sbc1.customers.adatum.biz – the derived trunk in a customer tenant that does not need to be created in PowerShell. You can simply add the name of the derived trunk in the customer tenant in the online voice routing policy without creating it.'
Does anyone have experiences on similar cases and can kindly provide me with some suggestions on how to configure the derived trunk?
Thank you so much.
- ElmarNiederkoflerCopper ContributorAny information about this?
Tried to understand how to configure an derived trunk but cannot find any solution to get it working. The doc says you dont need powershell for a derived trunk, so i belive there is a option on either the teams admin center or directly on the carrier partner portal for our costumers.
Also considering the doc it says
'the derived trunk in a customer tenant that does not need to be created in PowerShell. You can simply add the name of the derived trunk in the customer tenant in the online voice routing policy without creating it'
So i have tried to add our carrier trunks FQDN to the Voice Route but either Set-CsOnlineVoiceRoutingPolicy and Set-CsOnlineVoiceRoute fails that they cant find the PSTN Usage or PSTN.- fanzhangrobCopper Contributor
ElmarNiederkofler Thanks for the reply. I really hope someone has some idea of how to get it work.
I am guessing that this solution is no available for now but somehow there's an article talking about the future.
1. As you said set-csonlinevoiceroutingpolicy is not an option.
2. I cannot see a way to tell the carrier tenant to route the signaling from the customer tenants to the SBC or push the trunk setting to the derived trunks.
For now I'm using the old school way which is new-csonlinepstngateway at every customer tenants. At least it works.
- swernerCopper Contributor
fanzhangrob the documentation still needs a bit of work, but the derived trunk model works as expected.
In the carrier tenant, you just need to ensure TLS & SIP Options are active/working in both directions (can be viewed via the Admin center)
Once active, the following needs to be done:
1. Register a customer sub-domain of the carrier trunk FQDN in the customer's 365 tenant (EG: Sbc1.customers.adatum.biz where Sbc1 is the customer subdomain)
2. Create the voice routes & add these to a voice routing policy in the customer's teams tenant
As long as the subdomain is added to the customer's tenant and verified, S4Bonline powershell will allow the FQDN to be added to the voice route.
There's no need to use New-CSOnlinePSTNGateway.