DTMF Tones do not work when in a call
If i use teams to make an external call (using my skype for business phone number) the DTMF tones are not detected. So if i'm on a call that asks me to enter my PIN or some other input, it does not work
SteveT
shared this idea
73 comments
-
Francis
commented
It works for us, but we have to manually open the dial pad in the call window after dialling the number.
This is not user friendly at all. Simply opening the dial pad automatically in a new call window would save a lot of headaches. -
Steph
commented
Teams does so many great things for us. An update in this area would be beneficial for all.
-
Darcy
commented
Sometimes the DTMF codes are read incorrectly. I'll enter "8 0 1 5" and the autoattendant will say "8 8 8 8 is not a valid extension"
-
Anonymous
commented
It is confusing to have 2 different dial pads for calls. The phone that works with phone trees is hidden
-
C Durr
commented
I have found a workaround, but it is not elegant. When I started with the audio call first, using the "calls" icon on the left menu bar, I had the DTMF tones available. I then had to show the participant list and manually add the people I wanted to include on video. Now, I am in a "meeting"
The REAL feature I was trying to get to was the ability to record a meeting that included both audio and video participants. This feature is only evoked when Teams is in a "meeting" not in a "call."
Besides the obvious downsides of my manual work around, another one is once I am in the "meeting" the DTMF tones are now disabled and no longer accessible.
-
Patricia Stenquist
commented
DTMF tones and keypad are not functional within the audio conferencing feature in teams. This is necessary when dialing out extensions to phone numbers.
-
Anonymous
commented
DTMF function is essential for training New Hires on phone calls using the conference call feature.
-
Anonymous
commented
It Teams is going to be a voice platform the DTMF tones must work. This is an epic fail on Microsoft's part.
-
Carl PIazza
commented
Since I had posted on Feb 19 2021, I have discovered the issue was the caller (AT&T IPFlex) is Offering DTMF Payload Type 100, Teams Answer is 101. The 101 does not make it back to the Caller due to Oracle SBC not relaying it thru. Should the Caller be Teams, AT&T does negotiate to 101. Therefore it only happens when Teams is the Callee and its the DTMF in the direction back to the Caller that fails. Until now, I had not experienced an issue with Payload type mismatches. We have a request in to AT&T to change to 101, and a request into Oracle to see why its not relaying back to Caller for negotiation.
-
Carl PIazza
commented
Peer to Peer call cannot hear DTMF digit presses, PSTN same thing. However when I dial testcall.com 804-222-1111 I get the DTMF reading back. If I do the same call to testcall.com while in conference it does not work. Some of my users are reporting they cannot get connected to conference bridges on call back feature, others are good. This is pretty basic stuff and should work full time all the time.
-
Nick
commented
Agree, this is a big problem especially when conferencing in an interpreter and need to use the options to select the language. Please fix this.
-
Gary Frisco
commented
Any update on a fix for this?
-
Gary Frisco
commented
When is the fix for this? This is absurd!
-
homeiot
commented
please fix. I would have thought this is basic by now
-
Chris Pope
commented
DTMF tones work in a 1:1 call by activating the secondary keypad but if you are in a conf call they do not work
-
Julia
commented
Please fix DTMF.
-
chirag Acharya
commented
It's important to us to have the DTMF functionality.
-
Jig
commented
Voted but doesn't need "vote" to fix the issue.
-
Jenise
commented
This is a real frustration
-
Michael A. Bowling
commented
I had a similar issue when I attempted to call a client and my responses to their phone tree were not recognized.