Direct Routing sip issues

%3CLINGO-SUB%20id%3D%22lingo-sub-327141%22%20slang%3D%22en-US%22%3EDirect%20Routing%20sip%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327141%22%20slang%3D%22en-US%22%3E%3CP%3EGood%20Morning.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHopefully%20someone%20can%20shed%20a%20little%20light%20on%20an%20issue%20we%20seem%20to%20be%20having%20setting%20up%20direct%20routing%20for%20calls%20within%20teams.%20We%20have%20set%20up%20our%20tenant%20and%20base%20domain.%26nbsp%3B%20We%20have%20configured%20our%20SBC%20(%20ribbon%20Sonus%20SWe%20)%20via%20a%203rd%20party%2C%20with%20relevant%20certs%20and%20ports%20configured.%26nbsp%3B%20We%20can%20PING%20the%20sbc%20using%20the%20FQDN%20set%20in%20Teams%20Domains%20and%20have%20set%20up%20the%20pstn%20gateway%20via%20powershell%20without%20issue.%26nbsp%3B%20The%20problem%20seems%20to%20be%20that%20our%20SBC%20is%20not%20getting%20a%20response%20from%20the%20microsoft%20side%20when%20sending%20the%20OPTIONS%20messages%20and%20therefore%20doesn't%20set%20up%20a%20link..%26nbsp%3B%20Our%20SBC%20support%20guys%20say%20its%20not%20them%20and%20Microsoft%20support%20say%20its%20not%20them...%20I'm%20pulling%20my%20hair%20out%20at%20this%20point%20because%20im%20not%20sure%20if%20its%20something%20to%20do%20with%20the%20tenant%20settings%20that%20determines%20the%20communication%20between%20the%202%20environments.%26nbsp%3B%20I%20have%20followed%20the%20documentation%20set%20out%20by%20microsoft.%26nbsp%3B%20For%20our%20customers%20who%20had%20issues%20with%20SfB%20this%20doesn't%20promote%20any%20faith%20with%20teams...%26nbsp%3B%20%26nbsp%3BI'm%20a%20little%20up%20against%20it%20here%20and%20im%20not%20getting%20answers%20from%20the%20support%20team%20on%20either%20side%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-327141%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESkype%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-327742%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20sip%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-327742%22%20slang%3D%22en-US%22%3E%3CP%3EDon't%20you%20get%20any%20response%20at%20all%20from%20Microsoft%20when%20you%20send%20OPTION%20to%20them%3F%20Sounds%20like%20a%20routing%20problem%20then.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHow%20about%20the%20OPTIONS%20that%20Microsoft%20sends%20to%20you%2C%20does%20your%20SBC%20reply%20to%20them%20correctly%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-783594%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20sip%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-783594%22%20slang%3D%22en-US%22%3E%3CP%3Eas%20from%20what%20I'm%20seeing%20u'll%20never%20get%20OPTIONS%20back%20from%20MS%20until%20SBC%20OPTIONS%20transaction%20finishes(successfully)%20that%20means%20you%20need%20OPTIONS%2F200OK%20before%20getting%20anything%20back%20from%20MS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1504759%22%20slang%3D%22en-US%22%3ERe%3A%20Direct%20Routing%20sip%20issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1504759%22%20slang%3D%22en-US%22%3E%3CP%3EI%20seem%20to%20be%20having%20the%20same%20issue.%26nbsp%3B%20Did%20you%20get%20a%20resolution%20to%20this%20in%20the%20end%3F%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F260731%22%20target%3D%22_blank%22%3E%40WelshViking%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Contributor

Good Morning.

 

Hopefully someone can shed a little light on an issue we seem to be having setting up direct routing for calls within teams. We have set up our tenant and base domain.  We have configured our SBC ( ribbon Sonus SWe ) via a 3rd party, with relevant certs and ports configured.  We can PING the sbc using the FQDN set in Teams Domains and have set up the pstn gateway via powershell without issue.  The problem seems to be that our SBC is not getting a response from the microsoft side when sending the OPTIONS messages and therefore doesn't set up a link..  Our SBC support guys say its not them and Microsoft support say its not them... I'm pulling my hair out at this point because im not sure if its something to do with the tenant settings that determines the communication between the 2 environments.  I have followed the documentation set out by microsoft.  For our customers who had issues with SfB this doesn't promote any faith with teams...   I'm a little up against it here and im not getting answers from the support team on either side here.

3 Replies
Highlighted

Don't you get any response at all from Microsoft when you send OPTION to them? Sounds like a routing problem then.

 

How about the OPTIONS that Microsoft sends to you, does your SBC reply to them correctly?

 

Highlighted

as from what I'm seeing u'll never get OPTIONS back from MS until SBC OPTIONS transaction finishes(successfully) that means you need OPTIONS/200OK before getting anything back from MS.

Highlighted

I seem to be having the same issue.  Did you get a resolution to this in the end?@WelshViking