Forum Discussion
Direct Routing SBC failover planning in carrier hosted setup (derived trunk model)
For hosting provider failover routing, the hosting provider will need to configure multiple PSTN gateways in their tenant. For example:
- sbc1.contoso.com
- sbc2.contoso.com
This will require multiple wildcard san names to support each namespace. For example:
- *.sbc1.contoso.com
- *.sbc2.contoso.com
Each customer will be provide two FQDN's to be added to Tenant domain and a single user licensed for SfB Online in the namespace to create the domain in the service forest. For example:
- cust1.sbc1.contoso.com
- cust2.sbc1.contoso.com
Then a route will be created for each of these gateways.
Microsoft
Apologies about the snags you are hitting. Are you ok with sharing the case # that you have open so I can take a peek at the real details and potentially get you past your speed bump?
Regards,
CB
Like others I have followed the steps and cannot get the derived trunks working and accepting calls.
I also had a support call with Microsoft yesterday and it was suggested to wait another 24 hours after creating the subdomain in the customers domain.
- We are getting ready to offer direct routing for our customers but first, we would like to deploy it on a couple of accounts in our organization. We have followed the steps as outlined in the above mentioned post by adding 2 additional base domains (sbc1.ourdomain.com and sbc2.ourdomain.com) along with 2 wildcard certs to match. We will then activate these 2 new base domains by creating 2 new test accounts: email address removed for privacy reasons and email address removed for privacy reasons. In order to get this to work on my account, I will need to add a Teams Calling Plan license (or equivalent) but will I need to change my UPN to match the FQDN of one of our SBCs? Or would it be better to simply use one of these 2 accounts with the proper UPNs and assign the appropriate licensing?
This brings up another question regarding licensing: I currently have Business Standard. What is the cheapest and easiest add-on license to make and receive calls from the PSTN - no need to call outside of Canada. - Thankyou for the reply.
Mine started working around 36 hours after configuration. So I guess even more patience is needed. Strange thing was I did another 2 setups within 20 minutes and they were OK to go after an hour. I have also completed another 3 and they took between 1 and a few hours. - Carolyn Blanding (MS TEAMS)
The above was resolved. Issue was that the FQDN on inbound invites to customer tenant had carrier SBC FQDN defined. Therefore, the lookup for matching user phone numbers was to the carrier tenant and returned a 404.
