Problem with entering conference call passwords
andrewp:
I did more tests and it turns out that
Service Providers -> ITSP Profile A -> X_UseFixedDurationRFC2833DTMF
does not help at all.
To make it work I had to store DTMF codes in the handset address book with pauses inserted for every 3-4 digits. When call is routed through a Land Line, I don't have to put pauses.
knobby:
Is anyone else still having this problem?
I'm running the latest firmware with GV and if I type the conference code too fast, it's not accepted.
It seems like the same digit repeated requires an extra pause to get it to work.
For example, 12345567# would require me type in 12345... wait a sec then 567# to get it to work.
OBiSupport:
You may dial the conference code from other landline phones, or your cellphone, just for a comparison. If your particular conference system does require extra pause for DTMF transmission, then, you may have to dial that way.
knobby:
Thanks for the reply. The phone I'm using has it programmed in and I used it for the last year with vonage and it never missed. It is only when I switched it over to the Obi with GV that it no longer works.
I will try it on another phone but it's odd that it worked just fine with Vonage.
OBiSupport:
If you have a particular conference number that you want us to verify, please email the support at support@obihai.com, and state your 9-digit OBi number too.
Also, please try Gmail call phone service and see if it behaves similarly.
Navigation
[0] Message Index
[*] Previous page