Problems with DTMF tones
ChrisThompson:
I'm having a problem with the OBI110 handling DTMF tones from my handset. I noticed this today when I was calling into a conference call line and the line kept telling me the code was invalid.
At first I thought the problem was that I was calling through the Google Voice line, so I called back using **8 to dial through the POTS line (connected to MagicJack). I watched the MagicJack screen as I dialed the number. When I dialed, the OBI did send the correct number to the MagicJack to be dialed. However, once the connection was made, when I pressed a key on the phone, the number didn't always show up in MagicJack. If I use my phone to key in "123456789", the MagicJack shows it only recognized the keys "124679".
I know this isn't a problem with MagicJack, because I've been using it for years and have never had an issue with it not recognizing the DTMF tones from my handset when it's directly connected to the MagicJack.
jimates:
try it again only instead of pressing **8, press #. This should connect the handset directly to the line port (MJ) without the Obi in play.
Confirm it works ok like that then troubleshoot the Obi.
ChrisThompson:
Okay. I tested by hitting #, waiting for the dial-tone and dialing the number. During the dialing sequence, I can watch the numbers come up in the MJ interface just fine. However, again, once the call is connected, only about 40% of the time does the dialed number show up in the MJ interface.
For example, I was dialing a room code (say 123456), I would have to push each number 1-6 times before it would show up in the MJ interface. Once each number showed up, the conference call number recognized the correct room number. In other words, I had to dial "11112233344566#" for the conference call number to recognize "123456#".
Further testing shows the same problem happens with dialing out over Google Voice on SP1, though I can't watch exactly what numbers are actually recognized. Using the OBI test number (222-222-222), I can hear each DTMF tone as I press each number, but if I don't give sufficient time between each press, the tones won't play or they are cut off (a very short tone) or distorted.
With this new information in mind, I called back via MJ and found that if I left a 1.5-2 second delay between each number press, that the tone would get properly registered.
So it appears that the problem is that you cannot dial a numbers on a connected call without providing a full 2 second delay between each number. This is a fairly serious issue for anyone that uses their phone to call services that request information dialed via tones. A lot of support numbers request you enter your account number, last 4 SS#, telephone number, or other info on the phone. With this issue, I can never be 100% certain that anything I've dialed has actually been recognized as a valid entry by the recipient.
jimates:
well, pressing # is supposed to be the equivalent of the phone plugged directly into the Line device (MJ).
I would send an email to support@obihai.com
link to this thread, include your obi number
victorr:
I have the same issue.
Navigation
[0] Message Index
[#] Next page