Forum Discussion
Derived Trunk for Teams direct routing hosting model
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.
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.
- swernerOct 02, 2019Copper 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.
- Vasileios_TOct 08, 2019Copper Contributor
swerner I am also trying to configure the customer's tenant and confused with the documentation. Your assistance would be really helpful, since you have a working scenario.
I am confused at the point of a voice routing creation. If I execute the command on a customer's tenant:
New-CsOnlineVoiceRoute -Name “Example” -NumberPattern ‘^\+\d+’ -OnlinePstnGatewayList sbc1.example.com -Priority 1 -OnlinePstnUsages “Example”
I am getting an error, that it cannot find the specified PSTN usage. Could you please be so kind to help me with this?
P.S. The customer's subdomain has been created and added to the configuration.
Thank you in advance.
- seanwernerOct 08, 2019Copper Contributor
Hi Vasileios_T,
Before you can add the Voice Routes, you need to add the tenant-specific sub-domain to the customer's Office 365 tenant, as an additional domain.
EG:
Carrier: hosted.example.com
Cust 1: cust1.hosted.example.com
Once you've added the sub-domain for the customer & added the TXT record to the carrier's DNS to authorise the sub-domain addition, you then create a dummy user within the new domain, with a S4B Online license at least.
EG:
test.user@cust1.hosted.example.com - licensed with E3/E5 etc.
The license only needs to be assigned for 30/60 minutes while the platform activates the domain.
Following this, you should then be able to create the voice routes etc. as you've attempted.
- ElmarNiederkoflerOct 02, 2019Copper Contributor
swernerHello, thanks for the clarification.
Our carrier trunk on our domain is working also test users within this site can make calls.
For our costumer i have now removed the pstn gateway and added the fqdn of the costumers subdomain to the voiceroute. The fqdn has an A record pointing to our sbc.
did i make anything right?
thanks
regards elmar
- fanzhangrobOct 08, 2019Copper Contributor
Thanks for the reply. I'm using the SIP trunk through the DNS A record too. However, I assume it should by just a TXT record according to the article.