Forum Discussion
Derived Trunk for Teams direct routing hosting model
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.
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.