DTMF problems after firmware upgrade
AndyJ:
After upgrading to 1.2.1(2283), I'm seeing issues with services using DTMF codes. I did not see this with the previous release. This is occurring both with Google Voice and with a standard SIP provider. The far end seems to have trouble recognizing the codes on many (but not all) calls. For instance, if I call a service that requires me to enter a PIN or password, it will tell me that the I entered the wrong value when, in fact, I have entered the correct value.
Interestingly, this doesn't seem to be consistent. For instance, I just called a number, and the first 2 times, the DTMF signaling didn't work right. The third time, it worked fine.
Edit: I see there's a previous thread with some suggestions for solving DTMF issues at http://www.obitalk.com/forum/index.php?topic=577.15 ; however, it worked fine before the upgrade, so I'm not sure what changed. I'll have to try some of those suggestions.
XDRich:
I see the same effects when sending DTMF to Google Voice.
I too have upgraded to this firmware.
Moderator ... Please submit bug report.
RonR:
I'm seeing the same problem here. With 2103, I never had a single issue with DTMF anywhere, but I've got a couple of services that are now totally broken with 2283. One is DiscoverCard : (800) 347-2683 It also appears that incoming audio (prompts) is being echoed back which is interpreted as DTMF coming from the caller. This is occurring on both Google Voice and SIP calls. DiscoverCard worked perfectly prior to 2283. A similar thing happens with the iNum echo test: 883510000000091
This is a serious problem.
There's another anomaly that may or may not be related. When a call is first connected, there is an annoying 'thump' after dialing and the call is connected as the audio is enabled. This wasn't present in previous releases.
XDRich:
Found a fix in the forums.
Set the DTMF to InBand and all is well. ;D
http://www.obitalk.com/forum/index.php?topic=577.15
AndyJ:
Quote from: XDRich on May 11, 2011, 09:39:41 am
Found a fix in the forums.
Set the DTMF to InBand and all is well. ;D
http://www.obitalk.com/forum/index.php?topic=577.15
... but that doesn't answer the question of why it worked perfectly with the previous firmware with the default settings, and is broken with the current firmware. (Did OBi change the defaults in the new firmware?). So, using InBand is really a workaround, not a fix :)
Navigation
[0] Message Index
[#] Next page