MS Teams Direct Routing Q850 - error code 63

%3CLINGO-SUB%20id%3D%22lingo-sub-1429164%22%20slang%3D%22en-US%22%3EMS%20Teams%20Direct%20Routing%20Q850%20-%20error%20code%2063%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1429164%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20encountered%20this%20SIP%26nbsp%3B%20error%20message%20before%20%3F%26nbsp%3B%3C%2FP%3E%3CP%3EREASON%3A%20Q.850%3Bcause%3D63%3Btext%3D%22ac95c6f7-9819-4902-b180-a15447bf0f77%3BTarget%20Client%20has%20not%20supplied%20Outgoing%20Negotiation%20Request%20link.%22%3C%2FP%3E%3CP%3EWe%20are%20using%20MS%20Teams%2FDirect%20routing%26nbsp%3B%20behind%20our%20PBX%2FSBC%20and%20we%20setup%20a%20hunt%20group%20to%20ring%20multiple%20users%20and%20unfortunately%20the%20call%20drop%20after%20couple%20seconds.%20I've%20done%20some%20researches%20but%20couldn't%20find%20anything%20related%20to%20this%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3EHelp%20are%20more%20than%20welcome%20!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3EVP%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1429164%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

Hi,

 

Has anyone encountered this SIP  error message before ? 

REASON: Q.850;cause=63;text="ac95c6f7-9819-4902-b180-a15447bf0f77;Target Client has not supplied Outgoing Negotiation Request link."

We are using MS Teams/Direct routing  behind our PBX/SBC and we setup a hunt group to ring multiple users and unfortunately the call drop after couple seconds. I've done some researches but couldn't find anything related to this issue. 

Help are more than welcome !

 

Thanks

VP

2 Replies

@Vanna__Bullseye  Did you manage to resolve this issue? I've come across similar issue. Microsoft are rejecting calls with 403 forbidden with reason: REASON: Q.850;cause=63;text=....;Target Client has not supplied Outgoing Negotiation Request link.". Before 403 we see reINVITE to Teams without SDP. reINVITE without SDP might be the reason of this issue. Are you seeing same in the trace?

 

Regards,

Sajid

@SajidRashid Yes we did - We look at the sip traces and there was a  un-necessary 183 session progress coming from MS TEams direct routing. We discarded it within our SBC and the issue is fixed now. Hope that helps