GNOME Bugzilla – Bug 605086
Empathy dialpad DTMF doesn't work with IVR systems
Last modified: 2012-01-27 02:51:10 UTC
With google voice & gizmo to answer a call you must press 1 to talk or 2 to send to voice mail. This leaves empathy users unable to answer calls, or interact with menus during a call. Also see these http://linux.slashdot.org/story/09/11/28/2332254/Google-Eliminates-Gizmo5-Client-For-Linux https://bugs.launchpad.net/ubuntu/+source/empathy/+bug/482597
Can't you open the sidebar in the call window and use the dial pad?
I've tested it with google voice default settings several times & cannot answer calls. There is a workaround for this. Go into the settings menu of google voice and disable call presentation. Pressing 4 to record the call still wouldn't work though.
Q: Can't you open the sidebar in the call window and use the dial pad? A: Yes, I can open the sidebar. However, when I press 1 or 2 on the dialpad, nothing happens. The Google Voice calling system continues to ask me to press 1 or 2 to accept or decline the call. Pressing the dial pad buttons does not generate the appropriate dial pad tone.
triscuit713@go.com , have you tried to reproduce this issue in the development release of empathy (2.29.93)?
The issue is reproducable in 2.29.93.
Downstream comment: "I just tried to use the dialpad in empathy 2.30.0 in Ubuntu 10.04. The automated system I was using required me to press the # key. Upon pressing the # key, no tone was generated; the automated system I called (sipgate.com's echo number) did not recognize any tone."
Confirmed with 2.30.1.
Confirmed with 2.30.3 using Fedora 13. Trying to enter a code for a conference call, the dialpad doesn't seem to send any signals.
I tried this again and was able to get it working by dialing slowly. Without echoing the dialtones, it's hard to tell whether the problem is an incorrect dialing, or the tones aren't being sent correctly.
This is a bug in the connection manager. Which protocol was this?