Sandy Maggs
asked on
Microsoft Teams Direct Routing for Enterprise Voice won't make outbound calls...
I have setup Enterprise Voice / Direct Routing for Microsoft's 'Phone System' element of Office 365 and Teams. We're using a Ribbon SBC Edge (1000) border controller which has a very useful wizard and it's own FQDN certificate from godaddy.
I've enabled enterprise voice in Office 365 online powershell and setup routing policies to allow outbound calling to +44 uk numbers.
In Direct Routing, the SBC is showing as active and in use. I can make calls TO MS Teams clients using DDIs on our SBC routing calls successfully to Teams. However, Teams clients cannot dial out to the PSTN.
We've run trace logging on the SBC which shows all the SIP traces - it can see all the 200 OPTIONS coming to and replying from Microsoft, but it never sees microsoft attempt an invite to a call. For some reason Teams is not reaching out to our SBC when we try to make a call.
Does anyone have any advice for troubleshooting in O365/Powershell to determine why the call doesn't reach our SBC?
Thanks
I've enabled enterprise voice in Office 365 online powershell and setup routing policies to allow outbound calling to +44 uk numbers.
In Direct Routing, the SBC is showing as active and in use. I can make calls TO MS Teams clients using DDIs on our SBC routing calls successfully to Teams. However, Teams clients cannot dial out to the PSTN.
We've run trace logging on the SBC which shows all the SIP traces - it can see all the 200 OPTIONS coming to and replying from Microsoft, but it never sees microsoft attempt an invite to a call. For some reason Teams is not reaching out to our SBC when we try to make a call.
Does anyone have any advice for troubleshooting in O365/Powershell to determine why the call doesn't reach our SBC?
Thanks
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.