Teams phone auto-dialling incomplete numbers after Teams app update

Question

Teams phone auto-dialling incomplete numbers after Teams app update

Tom 20

Hi everyone,

I'm hoping someone may have come across this issue before.

We have a Yealink MP52 E2 Teams phone, and after updating the firmware from 176.15.0.164 to 176.15.0.194, we've noticed a change in the dialling behaviour.

Prior to the update, the phone would not place a call until the full number had been entered. Since the update, the phone appears to automatically dial after only a few digits have been entered. In some cases, it treats an incomplete number as complete and places the call before the user has finished dialling.

The previous Teams app version on the phone was 1449/1.0.94.2025084203. Following the firmware update, the Teams app was updated to version 1449/1.0.94.2026101002, which appears to coincide with the change in behaviour.

We contacted Yealink support, and they advised that the auto-dial functionality is controlled by the Microsoft Teams application rather than the device firmware. They suggested raising the issue with Microsoft to determine whether this behaviour was intentionally changed in a recent Teams app release.

Has anyone else experienced this issue or found a way to control the auto-dial behaviour? Is there a setting, dial plan configuration, or policy that determines when Teams considers a number complete and initiates the call?

Any advice would be greatly appreciated.

Thanks.

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hi Tom,

Thank you for sharing the detailed information regarding the dialing behavior on your Yealink MP52 E2 devices.

The auto-dial behavior on Teams-certified phones is controlled by the Microsoft Teams application rather than the device firmware itself. As a result, there is no direct setting on the Yealink device to adjust or disable this behavior. The dialing logic is determined by the Teams client and its interaction with tenant dial plans and number normalization.

Teams checks the dialed digits against the emergency dictionary first, then tenant and regional dial plan rules, and only after that falls back to adding the user’s country code. Because of that, a partial number can be treated as complete if it matches a normalization rule earlier than expected. This behaviour combines with the Auto Dial feature from Yealink documents could be the culprit for your issue:
User's image

As of now, you should review any custom tenant dial plan rules that might match short numbers or extensions and check whether the issue affects only certain digit patterns or all dialing.

If the behavior began only after the Teams app update and no dial plan issue is found, collect device logs from Teams Admin Center / the Yealink device and raise a Microsoft support case so the Teams phone client behavior can be reviewed.

You IT admin can use their admin credentials to submit a support request through the Microsoft 365 Admin Center on your behalf.

Microsoft also provides customer service phone numbers based on your region. Your IT admin can find the appropriate contact number here: Customer service phone numbers - Microsoft Support

This route ensures that a Microsoft support engineer can initiate a remote session to investigate backend configurations, run advanced diagnostic tools, and, if necessary, escalate the case to specialized teams with access to internal systems and logs. These backend resources are essential for resolving issues that go beyond what’s visible in the user interface.

As community moderators, we’re here to guide you, but due to privacy and security limitations, we don’t have access to the backend tools required for a full resolution. For this reason, contacting Microsoft Support via the Admin Center is the most secure and efficient way forward.

In case you do not know who is your IT admin, kindly refer to this article: How do I find my Microsoft 365 admin? - Microsoft Support

I hope this helps you resolve the issue quickly. I’m glad to assist and truly hope the information provided has been useful. Please feel free to reach out anytime if you need further assistance.

If you find my post helpful, kindly consider marking it as the accepted answer. Doing so can assist others in the community who may have similar questions in finding solutions more quickly.

Thank you for your kindness and contributions to the forum.

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.