Issues with obihai to dial in to a conference call with passcode

<< < (2/2)

Kuda:
Exact same issue I am facing, I have obi100 too.
And tried all Inboud/Software settings recommended on internet, still doesn't work.
Here is what I do....

I dial 10 digit US number
Dial 10 digit passcode for conf call and press '#'
Conf call telco speaks 'Please wait while we check the conf code....', and then 10-20 secs later, the call disconnects.

TrapDoor:
I have an OBi100 on a voip.ms account. I tried the voip.ms DTMF test (dial 4747) using all four different DTMFMethod options on the OBi. Each time all digits reported back properly except the '#' key. The test returned an acknowledgement beep indicating it received something but the verbal message identifying that keypress was missing.

I'm using firmware 1.3.0. build 2824.

ranantha:
any updates? does this need to be fixed by OBIHAI? new firmware?

ProfTech:
It may seem on the surface that this is related to the Obi but I suspect the problem actually lies with the service provider [Google]. There have been many reports of this issue with Google, especially when calling toll free numbers. I have also seen this issue to be worse with some SIP service providers, as well. I personally have seen where the same phone set, same Obi will work fine with one service provider and have major issues with DTMF when using a different provider. Google is free. Sometimes you do get what you pay for.

ranantha:
I have already checked that the same number when called directly with google voice works from multiple phones. So i do not think google is the issue here.

Navigation

[0] Message Index

[*] Previous page