Weird incoming Google Voice problem
dhobi:
I believe DTFM not being reliable is the reason why this is happening and it must have to do with packet loss or ports not being opened fast enough or the router getting confused for a brief amount of time. It still does it for me sometimes, but I know what to do now, just press '1' after a couple of "hello hello".
It is very strange that GV requires '1' to be pressed anyway even if call screening is disabled, but I do understand the quick and dirty XMPP hack. Hopefully they will not change it in a way that prevents devices such as OBI to use GV at all.
MichiganTelephone:
Quote from: dhobi on March 01, 2012, 05:16:14 pm
I have a strange incoming calls via Google Voice problem: the phone rings, I pick up the phone but somehow the OBI device/GV do not realize I picked up and the caller keeps hearing the rings and is eventually sent to the GV voicemail.
Outgoing calls work fine, so it's not a broken phone. This started happening today and I am not sure what setting I may have broken to cause it to do this.
Any ideas what to check?
It's possible that your problems have nothing to do with your Obihai device, and that the issue is actually with Google voice. As I wrote to someone else today who was having a similar issue:
I have found that once in a great while Google Voice seems to get confused and lose its configuration. So try this: Log into Google Voice and look to see what destination you have set (should be Google Chat). UNCHECK Google Chat, and if you have another destination set, check that. Optionally, place a test call to see if the call goes through to the other destination. Now change it back to the way to was — uncheck the other destination and re-check Google Chat. Then try another test call.
Weird I know, but I've seen this work on at least two occasions now. I can't explain why it works and can't guarantee that it will work in all such situations, but it's worth a try.
It sounds like perhaps you may be having a different issue, but maybe it wouldn't hurt to give this a try anyway.
dhobi:
Quote from: MichiganTelephone on March 14, 2012, 11:36:54 pm
Quote from: dhobi on March 01, 2012, 05:16:14 pm
I have a strange incoming calls via Google Voice problem: the phone rings, I pick up the phone but somehow the OBI device/GV do not realize I picked up and the caller keeps hearing the rings and is eventually sent to the GV voicemail.
Outgoing calls work fine, so it's not a broken phone. This started happening today and I am not sure what setting I may have broken to cause it to do this.
Any ideas what to check?
It's possible that your problems have nothing to do with your Obihai device, and that the issue is actually with Google voice. As I wrote to someone else today who was having a similar issue:
I have found that once in a great while Google Voice seems to get confused and lose its configuration. So try this: Log into Google Voice and look to see what destination you have set (should be Google Chat). UNCHECK Google Chat, and if you have another destination set, check that. Optionally, place a test call to see if the call goes through to the other destination. Now change it back to the way to was — uncheck the other destination and re-check Google Chat. Then try another test call.
Weird I know, but I've seen this work on at least two occasions now. I can't explain why it works and can't guarantee that it will work in all such situations, but it's worth a try.
It sounds like perhaps you may be having a different issue, but maybe it wouldn't hurt to give this a try anyway.
It is clearly not what you are suggesting because the phone rings but GV doesn't detect the call was picked up unless I press '1' on the phone. So the call is routed correctly. I believe it's the initial DTMF '1' that the OBI device sends automatically that occasionally gets lost.
NameerObi:
I think that the Obi devise is sending the DTMF '1' too soon. I was wondering if there is any way we can prolong the initiation of this task, where it would be sent 2-3 seconds after the call is received instead of its current setting.
dhobi:
Quote from: NameerObi on March 15, 2012, 08:34:01 am
I think that the Obi devise is sending the DTMF '1' too soon. I was wondering if there is any way we can prolong the initiation of this task, where it would be sent 2-3 seconds after the call is received instead of its current setting.
Don't know if it's too soon or because the initial UDP packets get lost, the router/firewall takes a bit to open the holes for the UDP packets, etc. You can try the OBI connected straight to the ISP, no routers/firewalls in between.
Navigation
[0] Message Index
[#] Next page
[*] Previous page