Teams Direct Routing Call Drop with 403

%3CLINGO-SUB%20id%3D%22lingo-sub-2402545%22%20slang%3D%22en-US%22%3ETeams%20Direct%20Routing%20Call%20Drop%20with%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2402545%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20an%20issue%20with%20outbound%20calls%20using%20Teams%20Direct%20Routing%20on%20Oracle%20SBCs.%20We%20are%20seeing%20SIP%20calls%20dropping%20at%20around%2010%20minutes%20with%20Teams%20responding%20with%20the%20following%20SIP%20403%20Forbidden%20message%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EREASON%3A%20Q.850%3Bcause%3D63%3Btext%3D%222d3ce374-1fc2-4c17-adf6-2e997f090562%3BTarget%20Client%20has%20not%20supplied%20Outgoing%20Negotiation%20Request%20link.%22%3CBR%20%2F%3E%3CBR%20%2F%3EI%20have%20seen%20another%20post%20with%20this%20issue%2C%20however%2C%20the%20cause%20is%20not%20the%20same.%20The%20carrier%20is%20sending%20two%20re-INVITEs%20within%20a%20couple%20of%20second%20of%20each%20other%2C%20however%20the%20second%20contains%20no%20SDP%20(but%20Content-Length%20is%20set%20to%200%20which%20is%20a%20valid%20SIP%20message%20as%20per%20rfc3261)%20and%20Teams%20response%20with%20the%20above%20403%20Forbidden%20message%2C%20thus%20disconnecting%20the%20outbound%20call.%3CBR%20%2F%3E%3CBR%20%2F%3EWould%20anyone%20have%20an%20idea%20of%20where%20we%20could%20look%20or%20fix%20this%20on%20the%20Direct%20Routing%20SBC%3F%20We%20do%20have%20a%20case%20with%20Microsoft%20open%2C%20however%20they%20are%20suggesting%20it's%20the%20re-INVITE%20with%20no%20SDP%20at%20fault.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2402545%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDirect%20Routing%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2410967%22%20slang%3D%22en-US%22%3ERe%3A%20Teams%20Direct%20Routing%20Call%20Drop%20with%20403%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2410967%22%20slang%3D%22en-US%22%3ESo%2C%20for%20those%20who%20experience%20something%20similar.%20I%20managed%20to%20work%20around%2Fresolve%20the%20issue%20with%20a%20setting%20on%20our%20Direct%20Routing%20SBC%20to%20add%20SDP%20on%20re-invites.%3C%2FLINGO-BODY%3E
New Contributor

Hi all,

I have an issue with outbound calls using Teams Direct Routing on Oracle SBCs. We are seeing SIP calls dropping at around 10 minutes with Teams responding with the following SIP 403 Forbidden message:

 

REASON: Q.850;cause=63;text="2d3ce374-1fc2-4c17-adf6-2e997f090562;Target Client has not supplied Outgoing Negotiation Request link."

I have seen another post with this issue, however, the cause is not the same and doesn't really provide the required fix. The carrier is sending two re-INVITEs within a couple of second of each other, however the second contains no SDP (but Content-Length is set to 0 which is a valid SIP message as per rfc3261) and Teams response with the above 403 Forbidden message, thus disconnecting the outbound call.

Would anyone have an idea of where we could look or fix this on the Direct Routing SBC? We do have a case with Microsoft open, however they are suggesting it's the re-INVITE with no SDP at fault.

1 Reply
So, for those who experience something similar. I managed to work around/resolve the issue with a setting on our Direct Routing SBC to add SDP on re-invites.
www.000webhost.com