Forum Discussion
Anorton1
Feb 15, 2021Copper Contributor
Getting a SIP 403 from Teams Direct Routing and debug/logs are worthless
We are getting the following 403 and need assistance on dete SIP/2.0 403 Forbidden FROM: "CINCINNATI,OH"<sip:+15135557313@customer1.sbc1.directroute.com>;tag=gK0006d317 TO: <sip:5135550967@sip....
- May 22, 2021
If you see a 403 error in response to difficulties placing calls see if you are also noting a Q850 response from Microsoft.
Explanation
Q850 responses provide reason codes which may also carry verbose detail on the cause for the rejection.
Some diagnostics may be necessary to establish the reason why Microsoft are rejecting a call and where we can we will offer suggestions as to how these can be resolved.
Example
Reason header: Q.850 ;cause=63 ;text="9810e5a9-667c-4513-8d3a-5d83503e1c71;Current call site state prevents fork to this entity."
Possible solution: AllowCallingPreventTollByPass Setting
Office365Buddy
May 21, 2021Brass Contributor
Please share the value for
Users > Select affected user > Policies > Calling policy -PreventTollByPass
Users > Select affected user > Policies > Calling policy -PreventTollByPass