Applies To

Call2Teams - Customers


Overview

There are several reasons why an inbound call may fail to reach your Teams device.

In the first instance, please read this article: Inbound/Outbound Call Issues

Shown below are a few examples for why you may not be receiving calls. Often, looking into the call logs as described in the linked article above, will shed some insight into these.



TABLE OF CONTENTS


Registration Timeouts

If your registration times out, your Teams device will not be available to receive calls. This may be noted as an intermittent ability to receive calls.

Hover over the Registration indicator in the Users section of the portal and check the 'Next Sync' advisory.

Ideally a shorter Sync time of 5 - 10 minutes is advisable to prevent timeouts.

You should amend this setting.


403 Permission Denied: No match for Service User Part

This error usually means the number offered by the PBX or Trunk for a user is incorrect. It is most likley to be caused by E164 number mapping issues.  refer to this article for help: https://support.call2teams.com/support/solutions/articles/6000234808-e164-formatted-number-translations-403-errors- 


404 Not Found Errors

Inbound call to Teams may encounter a '404 not found' error. This is most common when an account is new. The reason is that the user data we share with Microsoft can take some time to propagate through their system. The best solution here is just to wait. This can take an hour or so in some cases but is often much quicker. 


Occasionally the Microsoft platform is out of sync or an admin has changed the user's number in the Office 365 portal, this will cause the Microsoft Teams number associated with the user to be different to that set in the Call2Teams portal and produce the mismatch. To resolve this, set a random/different number for the user in the Call2Teams portal and sync, then set the correct number and sync again. This will ensure the correct number is stored against the user in Microsoft Teams. It may be necessary to allow Microsoft a little time to catch up with the changes made, for half an hour or so.


A less common cause of 404 errors can be attributed to users having both SfB and Teams running in Islands mode. Here is a Microsoft article that explains this in greater detail: Teams & SfB Coexist & Interop 


However, if you believe there to be a genuine error, please raise a service ticket with your partner. Also please check the user has been synced from the portal (Sync Now) as sometimes users are added/deleted and the re-sync is overlooked.


404 errors on outbound calls from Teams

If you are calling from Teams and the PBX or Trunk is returning a 404 error, then the most likely cause is a number formatting error or and E164 error. Please refer to this article for more help:

https://support.call2teams.com/support/solutions/articles/6000243136-configuring-e164-and-non-e164-number-formats

.

.

.

.

.

.




422 Session Interval Too Small

This error relates directly to the MIN-SE and Session-Expiry settings in the INVITE header.

The Min-SE can be left at the default of 90 in most cases, but the Session-Expires needs to be set to at least 1800 to allow for the exchange of INVITES and Re-INVITES.


488 Not Acceptable Here

There are two primary reasons a “488 Not Acceptable Here” response is seen: Unsupported Codecs and Incompatible Encryption.


Unsupported Codecs

If you see this error in the call logs, start by checking the codecs you are sending to the connector service. You can always try limit the codecs to the most common used to see if that resolves the issue. PCMU and PCMA are good choices here.


  • The connector service provides an option in the portal to filter on the Codecs. Note that this is a restrictive filter, so codecs that are missing will not be added in. When you select the codecs here you can also order them in preference, which will then be reflected in the SDP.



                        


Example: A call is dropped where the DTMF was negotiated in the original Invite (SDP) and the Re-Invite(SDP) had no DTMF negotiated hence, forcing the connector to drop the call 


Invite SDP with DTMF negotiation

    


Re-Invite SDP without DTMF negotiation


Incompatible Encryption

Confirm if you expect to send and receive calls to the platform using media encryption. If so, enable this in the PBX/Trunk settings page:

 

        

504 Couldn't Classify Packet or No Response

This is likely to be a mismatch between the IP address used when Call2Teams registered with the PBX, and the PBX IP address being used for the call delivery.


Q850 Codes

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." 


SIP Codes Wiki

This link will take yu to an external Wki listing all known SIP codes and their meanings. SIP Codes Wiki


SIP Methods, Requests & Responses

You can read more on SIP Messages here.


Disclaimer

Please note Qunifi cannot be held responsible for the content of any third-party documentation offered.