Weird incoming Google Voice problem
NameerObi:
I am using the web based expert mode to make these changes. How do I access it via the ip address. Do I telnet to it? I can not access via a web browser.
RonR:
Quote from: Stewart on March 14, 2012, 09:08:47 pm
If you still have trouble, report whether you are prompted to press 1, or if you hear silence, but pressing 1 connects the call anyway.
It's always necessary to send a DTMF '1' to answer an incoming Google Voice call when the XMPP interface is used (as the OBi does) regardless of whether Call Screening is on or off in the Google Voice settings, but no prompt is given by Google Voice. Enabling X_SkipCallScreening should automatically send the DTMF '1' for you. If X_SkipCallScreening is disabled, you must press '1' in the blind to answer an incoming call.
None of this is pertinent to outgoing calls.
NameerObi:
I just did it. I just figured out how to log into the Obi devise via the web browser using my ip address.
I am working on doing the changes manually.
Thanks Stewart, I really appreciate your help.
Stewart:
Quote from: RonR on March 14, 2012, 09:40:27 pm
Enabling X_SkipCallScreening should automatically send the DTMF '1' for you. If X_SkipCallScreening is disabled, you must press '1' in the blind to answer an incoming call.
I'm wondering if (at least some of) this problem is caused by the DTMF not being reliable. For example, a user may have set DTMFMethod to InBand to work around issues with DTMF on outgoing calls. But that would also presumably cause the '1' to be sent as voice; if the RTP path was flaky during the first 100 ms, the digit might not be 'heard' by the GV server. Possibly, even with RFC2833, a few lost packets could cause trouble. Is there any feedback available in the protocol, so the OBi could retry if needed?
RonR:
Quote from: Stewart on March 14, 2012, 10:21:28 pm
I'm wondering if (at least some of) this problem is caused by the DTMF not being reliable.
That's entirely possible.
Quote from: Stewart on March 14, 2012, 10:21:28 pm
Is there any feedback available in the protocol, so the OBi could retry if needed?
I don't know, but I seriously doubt it. It appears Google did a very quick-and-dirty XMPP interface to Google Voice, making as few changes as possible to the underlying Google Voice, not worrying about the ugly rough edges that resulted. They probably assumed they would be the only ones interfacing with it and they could just band-aid around them.
Navigation
[0] Message Index
[#] Next page
[*] Previous page