Forum Discussion
Microsoft teams Direct routing Carrier model
We are using Microsoft 365 teams direct routing carrier model. We have our carrier trunk in carrier domain which is working fine, the TLS connection is active and option messages are being exchanged...
Rohit001 hi, yes, it's a bit tricky at first. Regarding the derived trunk. However, once you see how easy it is. It is actually quite straight forward. You do not create SIP trunk. Delete that if you have done so. That is for when you have your own SBC. Or you connect to an ISP whose hosting one, not using derived method. All you need to do. Is create those DNS records (add the domain in your tenant). Which you have done.
Then create voice routes. I used Powershell to do this. You simply point the voice route to the DNS and it should work. That is all you need to do.
So, the entire process...
Before you can add the Voice Routes, you need to add the tenant-specific sub-domain to the your Office 365 tenant, as an additional domain.
EG:
Carrier: sbc.voiceisp.com
You: contoso.sbc.voiceisp.com
Once the sub-domain is added for your tenant & 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 Teams license.
EG:
email address removed for privacy reasons
- licensed with E3/E5 etc.
The license only needs to be assigned for 30/60 minutes while the platform activates the domain. You can free it up once it has completed.
Following this, you should then be able to create the voice routes etc. Just add voice route or I prefer through Powershell. Point it to constoso.sbc.voiceisp.com and it should start working.
Before you can add the Voice Routes, you need to add the tenant-specific sub-domain to the your Office 365 tenant, as an additional domain.
EG:
Carrier: sbc.voiceisp.com
You: contoso.sbc.voiceisp.com
Once the sub-domain is added for your tenant & 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 Teams license.
EG:
email address removed for privacy reasons
- licensed with E3/E5 etc.
The license only needs to be assigned for 30/60 minutes while the platform activates the domain. You can free it up once it has completed.
Following this, you should then be able to create the voice routes etc. Just add voice route or I prefer through Powershell. Point it to constoso.sbc.voiceisp.com and it should start working.
- We have got everything working..
We have a very simple setup for Microsoft Teams direct routing. Everything is working fine with incoming and outgoing calls.
We are facing problems after implementing LBR. I am stating a problem as it is with respect to the setup we have.
We have users who are sitting in the office , using team applications on their PCs and were able to make and receive calls.
Now we have implemented LBR to restrict these users to make calls when they are not connected to the office network or restrict when they are trying to make calls from any network except the office.
Now in the office the private network is 192.168/168.0/24 and public IP is X.X.X.X/27.
I have defined the private subnet in the network topology subnet And public IP's in the trusted IPs list.. So , ideally the call should work when users are trying from the office network. But the problem is calls are not working even from the office network which should be allowed as per the LBR.
Users are getting error : calls failing with Get Outbound Direct routing - no trunk config found by LBR selection criteria.
