Forum Discussion
Microsoft Teams won't send dial pad inputs when navigating a phone tree during a conference call
Our users sometimes need to dial to an external number from the Teams app on their phone, add another external number to the call, then use the dial pad to navigate a phone tree. However, the Teams conference won't send the dialpad inputs to the phone tree system. Is there a way we can make this work?
jcjchavez(and a message to my future self when I get annoyed by this again)
So I realised that there are two dial pads. The one in the main Teams window doesn't send tones.
But if you can navigate to the call itself there is another dial pad at the top. This does send tones.
🙂
JULY 2023 UPDATE FROM MY FUTURE SELF:
They Keypad option in Teams sends tones on the call. To add another participant, click on People and then dial another number.
- rconivBrass ContributorGlad there is something of a workaround but would think they would just setup the main keypad to be able to send the needed tones instead of people figuring out they have to use a hidden 10 key in the call window.
- cgigate1460Brass Contributor
Actually, there is no effective workaround solution after 4 years later...
The telephony features are not complete after so many years of Teams launch 😔
- GraniteStateColinSteel Contributor
I came here looking for a solution because this is not working for me today, even after restarting the affected systems, but has worked fine for over a year before this (and even worked earlier this morning). I can dial out just fine, but Teams is not sending touch tones to navigate phone trees. I can even call my own cell phone, then use Teams to send tones and they don't come through, so the problem is definitely Teams, not the party on the other end.
It must be an intermittent problem, but no idea what causes it or how to resolve it when it gets in this state. Is it a server-side or client-side issue? Seems to be a server-side problem, because it's not working from any Teams device (stand-alone Teams phone device or Windows PC). Frustrating that no one has ever added to this long-running thread with a technical explanation.