First, what is DTMF?
DTMF Explained
Next, where does a DTMF issue have a known problem? From 12/20 in our Nexus forum -
When using speaker phone with volume all the way up the tones are not recognized. If you turn down the volume the tones are recognized. Example, checking voicemail on speaker phone. If the volume us all the way up the system tells you that the password is incorrect. However, if you turn the volume down the system will recognize the password.
Known issue reported on droidforums.net.
Finally, is it possible for DTMF at play with one-way calls?
There's been quite a bit of controversy, most taking the position I went to immediately - how do dialing signals affect calls?
While that gets argued out, some are claiming that setting your DTMF from short to long helps the one-way call problem:
https://community.verizonwireless.com/thread/759860?start=30&tstart=0
Hit the blue phone widget, then settings, settings, you will see DTMF Tones. Hit that then change from normal to long. If anyone else has any success or not with this please post.
It seems VZW is handing out the overlapping DTMF story quite a bit.
In my opinion, worth every penny you paid for it:
- the reps got this explanation wrong
- changing DTMF length is a placebo
- OR there's some relationship with the DTMF signaling software and phone audio that are getting tangled, and changing the DTMF length alleviates that tangling to some degree
- example might be: the DTMF portion goes active when it ought not, but there's no DTMF signaling heard, just the voice mute is implemented
- example normal DTMF transaction:
- "Press 0 to speak to an operator"
- (keypad up)
- (you press 0 )
- (voice mutes)
- DTMF for 0 is sent
- (voice un-mutes)
I hope the reps are getting this partially right, the fix is really coming, and that's the audio software tangle I postulated some are suffering. If true, we'd have never found it.