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?
Oops, I answered your other thread before seeing this one. They seem to be the same problem! Possibly, an issue with your network equipment. Modem make/model? Separate router, if any? Can you test with OBi connected directly to modem?
Or, it may be something corrupted in the OBi. You might try a factory reset, then restoring your configuration.
I really have no idea what happened. It worked fine for a week and now it stopped working. I tried everything I could think of, reset the config, I tried a different GV account, I have another OBI box and tried that one too, they all behave the same way: the call comes in, the phone rings, I pick up the phone and the call keeps ringing for the caller. It seems that the OBI can't notify GV that the call has been answered. I connected the OBI straight to the ISP bypassing my router and still no go.
Anyone else running into the same issue? Has GV changed anything that may be causing this?
I wish sipgate still had free incoming numbers so I could try a different VOIP provider. Anyone have a spare spigate number they could "donate" even on a temporary basis to try some things out? ;)
dhobi,
Does pressing the '1' key on your phone after answering the call on the OBi cause the call to complete?
Quote from: RonR on March 01, 2012, 09:46:27 PM
dhobi,
Does pressing the '1' key on your phone after answering the call on the OBi cause the call to complete?
Wow! That does it. What is going on here? It seems like it broke over night. Obviously I'd like it to work without the '1' key but at least I have a usable phone again...
Weird part is that I have Call Screening set to Off in the GV Calls preferences tab, so I'm not sure why I'm required to press '1' to accept a call. X_SkipCallScreening is also enabled on the OBI which from what I understand does exactly that, it sends a '1'.
I messed with the Trusted Callers today and that's how I noticed that the AA was not picking up my calls, they were being sent to GV voicemail. And after that I could not pickup any incoming GV calls. I would say that's when the trouble started and adding my mobile as a Trusted Caller caused it though it might be just a coincidence.
I have nothing on the list of Trusted Callers now but things are still not working without pressing '1' to accept incoming calls. Any ideas what changes to the OBI the Trusted Callers list may have made? I even removed the device, reset the settings and added it again to OBiTalk and still not working. It seems that something is still persisted and gets changed on the device again.
Quote from: dhobi on March 01, 2012, 10:59:53 PM
Weird part is that I have Call Screening set to Off in the GV Calls preferences tab, so I'm not sure why I'm required to press '1' to accept a call. X_SkipCallScreening is also enabled on the OBI which from what I understand does exactly that, it sends a '1'.
Even with Call Screening disabled, Google Voice still expects a '1' to be pressed in order to accept the call when the XMPP interface is used. It's the way the Google Voice folks implemented it. Simply enable X_SkipCallScreening and this problem will be solved.
Quote from: dhobi on March 01, 2012, 10:59:53 PM
I have nothing on the list of Trusted Callers now but things are still not working without pressing '1' to accept incoming calls. Any ideas what changes to the OBI the Trusted Callers list may have made?
There is absolutely no relationship between Trusted Callers and pressing '1' to accept incoming Google Voice calls. When you specifiy a Trusted Caller, it simply causes the OBiTALK Web Portal to configure the OBi's InboundCallRoute with rules to allow single-stage calling through the PrimaryLine as well as go to the Auto Attendant. Nothing about Trusted Callers is related to pressing '1' to accept a Google Voice incoming call.
Quote from: RonR on March 01, 2012, 11:18:37 PM
Quote from: dhobi on March 01, 2012, 10:59:53 PM
Weird part is that I have Call Screening set to Off in the GV Calls preferences tab, so I'm not sure why I'm required to press '1' to accept a call. X_SkipCallScreening is also enabled on the OBI which from what I understand does exactly that, it sends a '1'.
Even with Call Screening disabled, Google Voice still expects a '1' to be pressed in order to accept the call when the XMPP interface is used. It's the way the Google Voice folks implemented it. Simply enable X_SkipCallScreening and this problem will be solved.
X_SkipCallScreening is already enabled, but it seems to have stopped working. Strange that it worked for about a week and it stopped working today. I think there may be a bit of a delay before the connection is established and the very first packets that send the '1' don't make it to GV.
Quote from: dhobi on March 01, 2012, 11:29:11 PM
[X_SkipCallScreening is already enabled, but it seems to have stopped working. Strange that it worked for about a week and it stopped working today.
Are you verifying this by logging into the OBi directly or are you looking at the OBiTALK Web Portal? The OBiTALK Web Portal doesn't always reflect what's actually in the OBi. The only settings that really count are those in the OBi itself.
If X_SkipCallScreening is actually enabled in the OBi itself, you might try resetting the OBi to factory defaults and then reconfiguring it. The OBi occasionally gets corrupted internally with no outward evidence of such in any of its settings.
I verified both on the device and on OBiTalk. I also unchecked the setting, let it sync and reboot, tried a call then checked the setting again, let it sync and reboot and tried a call.
Still not working without pressing '1', something is broken somewhere.
I tried resetting the device, deleting it from OBiTalk, re-adding it and configuring again and still the same behavior. I might try just removing it from OBiTalk and just managing it locally so nothing else pushes any settings into it. But I have to figure out how to configure GV "by hand" straight on the device. Are the settings posted anywhere?
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
Thanks. I'll give it a try tomorrow and report back.
UPDATE: If I configure the OBI box manually per RonR's instructions above, it seems to work correctly, I do not need to press '1' to take an incoming GV call. But if I let the OBiTalk portal do it, then I have to press '1' for incoming GV calls. In both cases X_SkipCallScreening is enabled but it seems to work only if I configure my OBI manually. There must be something in my OBiTalk online profile that is messing up the configuration and I have no idea what that might be.
This is very strange! I do believe that messing around with that circle of trust yesterday started causing the problem, as strange as it may sound.
Unless you have a compelling reason to use the OBiTALK Web Portal, it's much quicker and easier to configure the OBi directly/manually. Then you know what you're getting and don't waste days of your time trying to solve a mystery that you have no control over.
Quote from: RonR on March 02, 2012, 12:06:43 PM
Unless you have a compelling reason to use the OBiTALK Web Portal, it's much quicker and easier to configure the OBi directly/manually. Then you know what you're getting and don't waste days of your time trying to solve a mystery that you have no control over.
I agree with you, except I'm no expert in the strange device syntax or its features. I like the shortcuts the OBiTalk wizards provide, things like "local area code" for 7-digit dialing, enable GV voicemail notifications, etc. I would not have known these features even existed if it were not for OBiTalk.
I wrote to support, let's say if they find anything.
Good info in this thread! I'm experiencing the same issue! GoogleVoice was working but all of sudden incoming calls were silent. The OBi call status shows a call is in progress but the other end kept ringing. I'll give this a try! Thanks.
Quote from: Huib on March 02, 2012, 12:52:47 PM
Good info in this thread! I'm experiencing the same issue! GoogleVoice was working but all of sudden incoming calls were silent. The OBi call status shows a call is in progress but the other end kept ringing. I'll give this a try! Thanks.
Does it work for you if you press '1' after you answer the phone?
I didn't even try that. I just check the call screening box and voilà, it worked!
I am having the same problem where I would have to press 1 in order to accept the incoming call. I tried the manual setting as it was mentioned earlier:
System Management -> Auto Provisioning -> ITSP Provisioning -> Method : Disabled
System Management -> Auto Provisioning -> OBiTALK Provisioning -> Method : Disabled
Service Providers -> ITSP Profile A -> General -> Name : Google Voice
Service Providers -> ITSP Profile A -> General -> SignalingProtocol : Google Voice
Voice Services -> SP1 Service -> AuthUserName : (Google Voice username)
Voice Services -> SP1 Service -> AuthPassword : (Google Voice password)
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Physical Interfaces -> PHONE Port -> PrimaryLine : SP1 Service
It worked for few calls then I went back to having to enter the 1 to accept a call again. By the way, I couldn't find the BOTiTALK provisioning field, the only thing I was able to change under system management is the method.
When you log into the OBi directly (at the IP address given when you dial ***1) and go to System Management -> Auto Provisioning, you should see a section named ITSP Provisioning and another named OBiTalk Provisioning. In both of these sections, set the Method to Disabled, click Submit. Reboot the device, then confirm that X_SkipCallScreening is checked.
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.
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.
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.
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.
Quote from: RonR on March 14, 2012, 09:40:27 PMEnabling 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?
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.
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.
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.
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.
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.
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.
Looks like a new firmware update was just released that mentions a GV fix: (Mar 15, 2012) - 1.3.0 (2690)
http://www.obitalk.com/forum/index.php?topic=9.msg18471#msg18471
I too was having this problem and did the firmware update. It appears to be fixed now. I was able to receive a call and not have dead air. Woot!
I have the same problem, but pressing 1 after answering the call doesn't fix it. I've running the 3/15/2012 firmware, which didn't fix my issue.
Anyone else? Any other suggestions?
Thanks
Quote from: pjones on March 18, 2012, 04:53:45 PM
I have the same problem, but pressing 1 after answering the call doesn't fix it. I've running the 3/15/2012 firmware, which didn't fix my issue.
Anyone else? Any other suggestions?
Thanks
Try connecting the OBI straight to your ISP without any home routers/firewalls to rule those out.
To all,
I had the same problem stated in this thread. I know for sure that I did not have this problem 5 days ago, however, I don't know when this problem started as I just noticed today, which is when I started looking at the forum for a resolution. I tried a few of the suggestions on here (e.g. upgrade the f/w, reset the OBi, disconnect then reconnect GV from forwarding to Google Chat), but nothing worked.
Here is what solved the problem for me. Hopefully this resolves it for others also.
Assuming Google Voice is your Profile A,
Make sure Service Providers -> ITSP Profile A -> RTP -> X_UseSSL is unchecked.
I was checked in my configuration, and I believe it was always that way when it worked fine, but now only when it is unchecked can I successfully make inbound/outbound calls.
I had the problem where I had to enter '1' for incoming calls (other than GV numbers). Then I upgraded to 1.3.2690 and it works fine again.
Thanks
synchron 8)