Scenario is as follows:
1) Make call from cellphone to OBI (home phone).
2) Answer home phone, hear dead silence.
3) Caller's phone (cell phone) continues to ring until GV voicemail picks up
4) Can make outbound calls through OBI110 with no issues
This problem started around 3/8/12 and it has been hit or miss. Sometimes the call goes through and works and sometimes it does not. Most of the time it does not work (like 95% of the time). Used a different VOIP box and service through same home network and that VOIP box/service works just fine. Tried reloading OBI110 firmware, reset OBI box to defaults, reloaded configuration from scratch, deleted config and reloaded GV from scratch. Nothing fixes this problem. I have read some of the other recent similar forum posts but those are talking about outbound issues (which I am not seeing). This is 100% an inbound issue.
OBI110 box is shown a status of GREEN on the Obi Dashboard and GV is shown as connected. Everything shows as normal but inbound calls do now work. It seems that the phone is telling the OBI box that it has answered the call but the OBI box is not routing the audio to the phone plus telling the network to go ahead and pass the call on.
Does anyone have any ideas? ??? :(
Thanks,
Troy
In situations like this, the first thing to do is to bypass your router and connect the OBi ATA directly to your Modem. Power up the Modem first and once "online"/Ready, attached your OBi ATA. Do a Test call to see if it works properly. If it does, then the issue is related to your Router.
Do you have the other VOIP ATA connected to your LAN at the same time as the OBi ATA? If yes, maybe you might want to disconnect the other ATA, power cycle the Modem/Router/OBi ATA and test to see if incoming works.
Just started having the same problem today, also.
Emailed obihai tech support.
Been having the exact same issue for a few days using an Obi100. At least we get an email from GV for a missed call and can see who tried to call. Have checked setups and router settings and still can't find a solution. E-mailed tech support also.
It's not a problem with my other VOIP ATA as they both have been plugged into my LAN and working fine together. I use my other VOIP ATA for 911 calls and as a backup in case my Obi110 goes south (or has problems like this). The problem started around the 8th, but I had the Obi110 in-use for many months now with absolutely no issues. This is the first time I have seen any issues with my Obi110. :(
Now, I did hear back from Obihai Tech Support and they told me to press "1" after I answered the home phone to see if the call now connects. Once I pressed "1", the call went through and I heard the caller (and the caller's cellphone stopped ringing). I have asked Obihai Tech Support why I have to press "1" to make the call connect after I press "TALK" on my cordless phone. I am waiting for their response but I feel it is either the Obi110 box configuration has been corrupted or maybe the Obi110 box is now defective (cannot detect off-hook condition)
It's like the DTMF digit "1" triggers something in the Obi110 box to get the call to answer. It seems that the Obi110 box is no longer detecting an off-hook condition to connect the call, and pressing "1" is a way to "force" the call to connect.
I hope to hear back from Obihai tech support soon. I had to move over to my backup VOIP ATA to keep inbound calls working in my house but I am still using the Obi110 to make the outbound calls.
The "press 1" is Google's Call Screening. Turn it off in the OBi at Voice Services, SPx Service, SkipCallScreening (checked).
SkipCallScreening is already checked.
It's my understanding that with SkipCallScreening checked, the OBi will automatically "press 1" for you - and that GV always has the call screening enabled through the chat phone even if you disable in it GV.
I could be wrong though so you could try making sure it's disabled in GV and see if that makes a difference.
I have it checked in OBi and disabled in GV.
I understand the "press 1" for call screening and that may be part of the problem but, I miss calls because sometimes the phone never rings. I only know the call was missed because it was me calling home or an email from GV saying we missed it. Never had this problem until recently.
Same problem here too. Started yesterday. Doing more testing today **9 222 222 222 works perfectly. I use Google Voice. On outbound calls, ringing is heard then silence. Inbound calls to the Obi, the box rings the phone but when I pickup no voice connection, the other end continues to Google Voice mail. Using 1.3.0 (2675) firmware.
The Obihai support team is aware of the issue where answered inbound calls are met with silence while the far end continues to hear ringing, eventually going to voice-mail.
This issue has been observed by a relatively small number of users. If you are experiencing the behavior described above, feel free to report this using the Open a Support Request form (http://www.obihai.com/supportTicketForm.php) on the Obihai web site.
I'm suffering from this problem as well. I first noticed it on the 12th. Call screening was initially enabled on Google Voice, but this problem persists even after I disabled it.
I filled out the support request form, but am posting here too for good measure.
Here is the fix:
System Providers --> ITSP Profile A --> RTP: X_UseSSL (set this to default, make sure the box is NOT checked)
Quote from: Agate on March 14, 2012, 10:00:16 AM
Here is the fix:
System Providers --> ITSP Profile A --> RTP: X_UseSSL (set this to default, make sure the box is NOT checked)
X_UseSSL is disabled (unchecked) by default. How did X_UseSSL get enabled? Did you enable it, did the OBiTALK Web Portal mistakenly enable it, or what?
Pressing "1" after receiving an incoming call w/ silence did not help.
Quote from: AndrewH on March 14, 2012, 10:51:00 AM
Pressing "1" after receiving an incoming call w/ silence did not help.
Did you also confirm that your problem is not the issue posted by Agate?
Quote from: Stewart on March 14, 2012, 10:57:21 AM
Quote from: AndrewH on March 14, 2012, 10:51:00 AM
Pressing "1" after receiving an incoming call w/ silence did not help.
Did you also confirm that your problem is not the issue posted by Agate?
Yes. X_UseSSL is NOT checked. It is grayed out, and the Default box is checked.
I also just checked the same parameter and X_UseSSL is disabled (unchecked) by default in my Obi110 configuration. So that is not the problem either.
I have confirmed that pressing "1" after I take the call (while I hear the silence) does get the call to go through 100% of the time. It seems to force the call to connect.
I hope to hear back from Obihai tech support later on today.
Quote from: TroyB on March 14, 2012, 11:21:28 AM
I have confirmed that pressing "1" after I take the call (while I hear the silence) does get the call to go through 100% of the time. It seems to force the call to connect.
Log into the OBi directly at the IP address returned by dial ***1 and confirm:
Voice Services -> SP1 Service -> X_SkipCallScreening : (checked)
Having X_SkipCallScreening enabled (checked) is supposed to be pressing the '1' for you.
RonR, I run 12 of these boxes, all using Google Voice. Only 2 started having behaviors in the last 3 days as follows: Inbound calls would ring but upon pickup no one seemed to be connected. The calling party would eventually ring through to Google Voice mail and be processed normally from that point forward. From the calling parties perspective it seemed like no one answered the call was handled by voice mail.
Outbound calls would sometimes connect, sometimes not. If they did not connect to the called party number, there would be one ring heard then go silence.
Upon checking all 12 boxes settings, only 2 had this problem, and only 2 had the X_UseSSL box checked.
RonR, SkipCallScreening is already checked in my Obi110 configuration. I agree that this parameter does the "1" press for me automatically, but it's not working anymore. I am thinking of RESETTING the Obi110 box to 100% defaults (again) and then reconfiguring the box from scratch to see if that clears up this issue. I will try that tonight when I get home and then report back.
I have not heard back from Obihai Tech Support yet, but I am sure they are trying to figure out what is going on.
Quote from: TroyB on March 14, 2012, 12:04:59 PM
I am thinking of RESETTING the Obi110 box to 100% defaults (again) and then reconfiguring the box from scratch to see if that clears up this issue.
That has solved a number of other mysteries in the past. Please let us know the results.
RonR, After reviewing my notes, in message ( http://www.obitalk.com/forum/index.php?topic=1909.msg12234#msg12234 ) the obi-support2 Administrator replying to
Re: Another person in need of help with Google Voice and Obi dropping calls
« Reply #1 on: November 20, 2011, 07:21:31 PM »
"One quick remedy you can try is to enable this option (using OBi expert page on
the portal, or the device local web page directly):
ITSP Profile A/B > RTP > X_UseSSL
It might reduce/eliminate false disconnect."
This must be why I set it, as a few of my boxes were experiencing dropped calls.
Looks like GoogleVoice does no support this now.
I just reset my Obi, deleted and readded it in the Obitalk portal, and reconfigured my GV account. Incoming calls still give me silence, but pressing '1' seems to put them through now. This is even with X_SkipCallScreening checked.
FYI.. Great News!!! it looks like the Obihai Tech Support team has figured out why this is happening and is working on a new firmware release!!! As follows:
From: Obihai Support Team
"We will have a new official firmware soon that have fix for this issue. You can check our firmware update (if available) sometime tomorrow, by pressing *** 6 It is not with your OBi's configuration."
Thank you Obihai Tech Support Team!!! ;D
I have the same problem for 4-5 days , I did a clean re-install of the obi100 last night and problem returned.
I un-checked X_SkipCallScreening for GV sp1 and it seem fine now.
Jimmy
Unfortunately, I'm still experiencing this problem after applying the new firmware update released today.
I just installed the following version of firmware and it resolved the problem I reported at the beginning of this thread. -> 1.3.0 (Build: 2690)
Thank you Obihai !!! ;D
I also had this issue (sorry for posting an additional thread). I did a Web-based factory reset, and reconfigured from scratch (I didn't have a LOT changed from the defaults, so it went fairly quickly), plus the option 27=1 full/100 from the builtin IVR (aa2). It's been working fairly well since then. If I restored a config XML made previously, the problem would return. So GV seems to have changed something slightly, just enough to trick the OBi firmware into not working properly. I agree, I also wanted the SSL option, but as of right now, it doesn't work. I also applied the firmware released 15-Mar-2012, but it didn't cause much of a change (although I don't experience any other issues).
Another maybe slightly interesting data point is that calls from VoicePulse would not connect properly or would be reported by voice announcement as being out of service, but using an alternate GV account (with an IPKall number to serve as the termination of the first call initiated from the Web page) seemed to work OK regardless. But then again, I kind of figured that would work "better" because it's Google calling Google :-).
Quote from: AndrewH on March 15, 2012, 11:01:03 AM
Unfortunately, I'm still experiencing this problem after applying the new firmware update released today.
Same here. Problem started maybe 3 or 4 days ago and happens to 5 out of 6 calls I receive.
In the same time frame, on out going calls to busy phone #s, I hear one standard ring before the busy signal. This is quite annoying because the *05 doesn't work since it calls right back after detecting the normal ring. This too was not corrected by the new firmware released yesterday (2690).
I'm putting a support ticket in now, as was suggested earlier in the thread.
Same here. Upgraded firmware this morning. 1.3.0 (Build: 2690)
Can't call out, "you hear one ring then dead air sometimes it just rings and rings". Inbound has to be picked up on cell phone,
Fwd into google voice. Everything has been fine for months.
Netgear router 3700 v1. Obi 110 has Static IP in the DMZ AT&T DSL. Westell modem
in bridge mode. This all started around 3 days ago.
Deleted google voice and re-entered data no go. Tried Ron's
half duplex trick , did not work. Shut down router modem reboot no help.
NetTalk hooked up to line port works good. Tried it with Netalk powered off. no go.
Tried unchecking google chat in Google Voice per Michigan Telephone and then
rechecking that option no go.
I guess the message of this is that this problem depends on the firmware and not to upgrade unless you are having some problem. It should not to too difficult to get a copy of the firmware that worked for you from Obihai and reinstall it.
current
http://www.obihai.com/firmware/OBi-1-3-0-2690.fw
previous
http://www.obihai.com/firmware/OBi-1-3-0-2669.fw
My Obi110 was rebooted at 6:07pm by support team.
I put in a support ticket and it seems ok now !
Working again ! ;D Thank you !
This was their email back to my support ticket.
"There was a parameter "UseSSL" enabled/checked in your OBi.
That parameter is not supposed to be modified from default setting.
We have fixed this, your calls should be ok now."
-Obihai Support Team
maybe this will help out someone else.
not sure what field "UseSSL" is under ?
Quote from: BruceW on March 16, 2012, 03:19:40 PM
not sure what field "UseSSL" is under ?
Voice Services -> ITSP Profile x -> RTP -> X_UseSSL