Forum Discussion
Direct Routing Hosting Model
Hi fowler_23
Thanks and this is basically what I have however I do not have a carrier subdomain defined do I need that? I hadn't read anywhere you needed that, I understood just a carrier base domain and tenant subdomains.
So when I create the carrier OnlinePSTNGateway I use the base domain as the FQDN .
When I define the voice route in the customer tenant do I still have to add the -OnlinePSTNGatewayList parameter and add the FQDN of the OnlinePSTNGateway or is this derived some how auto-magically?
Thanks again for your continued assistance!
If you refer to https://docs.microsoft.com/en-us/microsoftteams/direct-routing-sbc-multiple-tenants
and under the section Register a Base Domain and subdomains. Their example has the carrier base domain as adatum.biz and then an additional domain customers.adatum.biz so my example follows Microsoft's logic.
No - you don't need to add PSTNOnlineGateway parameter to the customer tenant. That same document again. Search for Create a trunk and provision user. That gives some information there about derived trunks.
- ASharpieSep 28, 2020Copper Contributor
Hi fowler_23
I got all this working in the end but I didn't need to create subdomains as per the MS example and you do need to have the PSTN Gateway List populated when creating the carrier trunk. If you dont do this there is no way to tell the voice route where it should route to so I believe the MS document to be misleading. Their documentation states you need to use the FQDN of the SBC in the voice route but the command doesn't show this and you cannot add it in any other way apart from that parameter. I have reviewed other posts on this and found the same. I just thought I'd update this post and feedback my findings.
Thanks!
- ASharpieSep 17, 2020Copper Contributor
Hi fowler_23
OK thanks. I've had to change and create new domains now, I also have the complexity of load balancing between two sites which has driven the need to create new carrier subdomains, one for each SBC pair and also new customer domains based on the carrier subdomain. What an ache!
It's clear to me that documentation needs updating and full explanations of how you achieve fail-over etc is required, that part is especially not clear.
Thanks for your help!