Gate Call Box
SteveInWA:
I'm sorry; I don't understand what you are asking. Please try again.
This bug is impacting most, but not all Google Voice users at this time. It doesn't matter which carrier(s) is/are involved on the other end of the call.
If it helps: OBiTALK devices can support up to four separate VoIP service registrations. For example, I have three Callcentric numbers and one Google Voice number configured on my 200 and 202. You can call out with whichever of those numbers you wish. You designate one of them as the default for outbound calls, and then, if you want to call out using one of the others, you prefix your dial string with **1, 2, 3, or 4, depending on which SP you want to use.
For example, on my OBi 200:
SP1 is Callcentric number xxxx. I set it as the default. When I pick up the phone and key in a number to call, that call will travel over SP1's Callcentric service. SP4 is Google Voice. If I want to make an outbound call using that service, then I key in **4 xxx xxx xxxx.INbound calls will ring according to your configuration settings. On a 200, the default would be for calls people make to any of the four SPs will ring the same physical telephone plugged into the device.
heffneil:
My gate call box is using the OBihai to make the call. The device is using GV. It dials out to the GV number. Which GV service is the problem?
SteveInWA:
That doesn't make sense.
Your gate call box places a regular telephone call, using whatever telephone carrier's service is physically connected to the telephone circuitry in that call box. It is calling your Google Voice phone number, service for which is provided by Google Voice, and configured on your OBiTALK device.
The failure is happening when you, the party answering the call, try to press DTMF digits, and Google Voice is failing to process those digits, so they can't be sent to the call box's telephone.
heffneil:
OBIHAI connected to google voice is used to call ANOTHER GV number. Which is the problem.
SteveInWA:
I don't get it. The call box has its own telephone service, not an OBiTALK device. It calls YOUR OBiTALK device.
Where is the other OBiTALK device?
...and no, as I've already stated, the cause of the failures is a bug in Google Voice's back end telephony infrastructure. It has nothing to do with your devices; it happens to regular calls on mobile phones. The bug is causing touch tones to not be recognized. You can't fix it. You'll have to wait for Google to fix it.
Navigation
[0] Message Index
[#] Next page
[*] Previous page