Start a conversation

Calls from the third-party SIP Device to MS Teams Fail

Overview

Calls to MS Teams numbers made from a particular third-party SIP device fail. The call rings for an MS Teams user but fails after the user attempts to answer the call.

Solution

Please note that one of the known root causes of such behavior is the device offering video codec in the invite, which is not supported by SBC. Check that no video is set up on the device profile (if needed, verify with Microsoft that video codecs are not offered from this particular device).

If you are sure that video is not offered, but the issue persists, to start with troubleshooting, we will need fresh call samples. Reproduce the issue and open a ticket with Support, making sure to describe the issue and any symptoms you observe, and add at least two call samples in the following format:

  • Calling From Number:
  • Calling To Number:
  • Date of call: dd/mm/yy
  • Time of call: xx:xx am/pm (time zone)
  • Trouble observed: Inbound or Outbound
  • Description of the failing scenario
2023-01-17 05:38:00 -0800 : 52.114.132.46:5061 -> 198.17.84.84:5061
SIP/2.0 488 Not Acceptable Here
FROM: "Front Door";tag=gK006792e8
TO: ;tag=8db60f3effffffff144a942b0efc9bdc
CSEQ: 917805 INVITE
CALL-ID: 104903443_127178351@198.17.84.84
VIA: SIP/2.0/TLS 198.17.84.84:5061;branch=z9hG4bK00B0f0ca975481330b5
REASON: Q.850;cause=79;text="8fe32bab-0520-44c4-bfb1-0861bff2920c;There are no ICE candidates in the SDP. Non-ice endpoints cannot use bypass."
...
01/17/2023 09:49:32.682 -05:00: 52.114.132.46:5061 --> 198.17.84.84:5061
SIP/2.0 200 OK
FROM: "Front Door"sip:+12023137681@iu45b2fvksm2igui.sbc.cul.sbcaas.com;tag=gK080fe701
TO: sip:+15714734576@sip.pstnhub.microsoft.com;tag=41b8c75649338176493312bc12bc4933
CSEQ: 438017 INVITE
...
a=ice-ufrag:WzFO

a=ice-pwd:44PfCTFGB37bG+NQqi+8KMZX

Based on the troubleshooting, the Support team will either take action to fix the issue on our side or reach back with findings and any next steps required from you.

Verification

Once the root cause is fixed, try to replicate the issue to confirm that it is no longer there.

Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted a month ago

Comments