calls dropped between Teams IP Phones

Iniobong Nkanga 1,691 Reputation points
2023-04-26T15:28:17.0033333+00:00

Hello

Please i need your help on this issue.

One calls dropped between Teams IP Phones on the 26/03/2023 as follows:  1.15PM 2626 to 2335
1.41pm 2392 to 2335  

Some calls from from 2392 to other destinations have a response code of 487 - Could this be an issue?  

Can you analyse the logs attached for errors relating to the two calls above please?  

Also, is there anything else that can be seen from your end as to why these 2 calls dropped.

Microsoft Teams
Microsoft Teams
A Microsoft customizable chat-based workspace.
9,407 questions
{count} votes

1 answer

Sort by: Most helpful
  1. SokiGuo-MSFT 24,941 Reputation points Microsoft Vendor
    2023-04-27T06:29:37.6433333+00:00

    Hi @Iniobong Nkanga

    Kindly note that Microsoft Q&A forum mainly focus on Teams general usage questions. If possible, please consider contacting support in Microsoft 365 admin center>Support>New service request to have them look into this issue.

    Response code 487 indicates that the previous request was terminated by a user or application action. This can happen when the call is canceled, dropped, or times out. Some possible causes are:

    The caller or callee hangs up before answering the call.

    The call is forked to multiple endpoints, and one endpoint accepts the call, resulting in a 487 response from the other endpoint.

    The call is blocked by a firewall, proxy, or session border controller (SBC) due to policy or configuration issues.

    To resolve this issue, you may need to check the SBC and see if there are any errors or warnings. You may also need to contact your service provider or vendor for assistance.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.


    0 comments No comments