I'm not sure if this is an Obi or an GV issue.
Anyone else having similar issues?
CLICK THE LINK BELOW TO HEAR THE ERROR MESSAGE:
http://freemobilesitetoday.com/wp-content/uploads/2012/02/Error-503.mp3
Who is your service provider?
A SIP error 503 is : Service Unavailable
you mean my ISP? (Comcast)
No, your telephone service provider (Google Voice, Callcentric, etc.).
Soryy I meant GV instead of "Gtalk"
Does every other call fail when originated from the Google Voice web page?
Ok, let's start over.
This is happening from my Obi110. I am not using Gtalk (i meant to saying GV)
I am not placing calls from Google's webpage, but rather my phone handset.
Quote from: RonR on February 07, 2012, 04:00:13 PM
Does every other call fail when originated from the Google Voice web page?
Not sure what to say aside from what's in the title. I upgraded to the newest firmware today. The VM notifications work again, but I don't care too much about that. But now at least 1/2 of my incoming calls don't ring my phone. I get an email telling me I have a voicemail. I'm using Google Voice BTW.
Am I the only one? This started happening AS SOON as I upgraded. I was home all day and on the phone a lot so I am quite aware of when this began.
Quote from: otherwhirl on February 07, 2012, 04:11:35 PM
Ok, let's start over.
This is happening from my Obi110. I am not using Gtalk (i meant to saying GV)
I am not placing calls from Google's webpage, but rather my phone handset.
I understand that. But if calls also fail from the Google Voice web page, the problem can't be with the OBi, can it?
I've got the same problem. All has been working fine until today. Now all of the sudden, when I place a call I am getting a service unavailable message "reason 503". My primary line out (sp2) is Google Voice. If i press **2 (I have voip.ms connected to sp2), then I get through no problem. It is definately related to the google voice / gmail setup through the OBI110.
We have two OBI110 devices, each tied into separate google voice service, and each also connected to a separate voip.ms account. Both phones are having the same problem.
Any help? Any suggestions?
I can make a call from the google voice webpage with no issues.
The same thing is happening with me. I have GV configured so that incoming calls ring on my cell phone and my home cordless phones (through the Obi). About half of my incoming calls ring only on my cellphone and not my cordless phones. I am positive the callers are dialing my GV number, not my "hidden" cellphone number.
In addition, on outbound calls, I occasionally receive a 503 error. If I immediately redial, sometimes the calls go through.
This is a major problem that may be affecting everyone using the Obi with Google Voice.
Obitalk folks, please look into this!
Quote from: otherwhirl on February 07, 2012, 03:22:41 PMAnyone else having similar issues?
I am having this issue on both of my obi/google.voice phones. When I dial out the obi auto attendant says that "the call was rejected by your service provider "reason 503." Receiving calls is also hit or miss.
Please pardon my 'noobie'ish' ways.... as i'm definitely new to all of this RonR (and everyone else :P)
Hey, but this how i'm learning!
Thanks
Quote from: RonR on February 07, 2012, 04:17:58 PM
Quote from: otherwhirl on February 07, 2012, 04:11:35 PM
Ok, let's start over.
This is happening from my Obi110. I am not using Gtalk (i meant to saying GV)
I am not placing calls from Google's webpage, but rather my phone handset.
I understand that. But if calls also fail from the Google Voice web page, the problem can't be with the OBi, can it?
I am getting the 503 error as well. I got it today when dialing an 800 number and figured maybe it was just Google Voice not liking certain 800 numbers so I just called it on my cell phone. After seeing this though I gave the same number a few tries and it does seem to be about 50/50 for a successful call or a 503 error.
I too am being affected by this. Very disturbing that this is happening. I hope that it gets resolved soon.
FWIW, the problem is reproducible here also.
Here's what the 503 error looks like in the Syslog:
[Feb 08 00:09:55]<7> GTT:call state changed from 0 to 2
[Feb 08 00:09:55]<7> GTALK:sess callsess_36 state changed from 0 to 2
[Feb 08 00:09:55]<7> [CPT] --- FXS h/w tone generator (reorder)---
[Feb 08 00:09:55]<7> GTALK:sess callsess_37 state changed from 2 to 6
[Feb 08 00:09:55]<7> GTALK:not redirect or redirect with no content:503!
[Feb 08 00:09:55]<7> [CPT] --- FXS h/w tone generator (reorder)---
[Feb 08 00:09:55]<7> RTP:Del Channel
[Feb 08 00:09:55]<7> [CPT] --- FXS h/w tone generator (ringback)---
[Feb 08 00:09:55]<7> [CPT] --- FXS s/w tone generator (sit_1) ---
When the OBi announcement makes the "Service Unavailable" 503 message is is is not an issue with your OBi device's operation. The OBi is simply providing some additional context as to why the particular call cannot be completed by the service provider (we feel this is a bit better than returning a generic busy signal or other special information tone).
That said, we are studying this particular issue. As well, please look to the GV Help Forum for more information.
The 503 error may indicate service being unavailable temporarily on the Google Voice connection. And yes, a redial of the same number might make the call go through.
When the OBi announcement makes the "Service Unavailable" 503 message is is is not an issue with your OBi device's operation. The OBi is simply providing some additional context as to why the particular call cannot be completed by the service provider (we feel this is a bit better than returning a generic busy signal or other special information tone).
That said, we are studying this particular issue. As well, please look to the GV Help Forum for more information.
The 503 error may indicate service being unavailable temporarily on the Google Voice connection. And yes, a redial of the same number might make the call go through.
Quote from: OBiSupport on February 07, 2012, 11:56:38 PM
When the OBi announcement makes the "Service Unavailable" 503 message is is is not an issue with your OBi device's operation. The OBi is simply providing some additional context as to why the particular call cannot be completed by the service provider (we feel this is a bit better than returning a generic busy signal or other special information tone).
That said, we are studying this particular issue. As well, please look to the GV Help Forum for more information.
The 503 error may indicate service being unavailable temporarily on the Google Voice connection. And yes, a redial of the same number might make the call go through.
Well I'm not getting a 503 error. The phone isn't ringing. Any input on that?
I think what OBiSupport is saying is that if there are problems with Google Voice itself or from the GV end, you will experience the issue you are having. If you check the GV Help Forum you will see that a number of GV users who are NOT using the OBi ATA is experiencing just the problem you are having. This is outside the control of OBi and nothing they can do to correct the issue. In other words, the issue is unrelated to the Firmware upgrade and just happen to coincide with it!
Quote from: S--F on February 08, 2012, 03:02:10 AM
Quote from: OBiSupport on February 07, 2012, 11:56:38 PM
When the OBi announcement makes the "Service Unavailable" 503 message is is is not an issue with your OBi device's operation. The OBi is simply providing some additional context as to why the particular call cannot be completed by the service provider (we feel this is a bit better than returning a generic busy signal or other special information tone).
That said, we are studying this particular issue. As well, please look to the GV Help Forum for more information.
The 503 error may indicate service being unavailable temporarily on the Google Voice connection. And yes, a redial of the same number might make the call go through.
Well I'm not getting a 503 error. The phone isn't ringing. Any input on that?
Well then this is a pretty big coincidence, and I'm not sure I believe it.
I have the OBI110 up and running fine with GV. I am getting ready to port my Landline (with AT&T) to a AT&T Go Phone and then port to GV. I have read that many have done this. I chatted with AT&T to confirm it could be done and they said yes.
Just checking to see if anyone has had any issues doing this lately.
Thanks much
Setup: GV configured on Obi box and generally working fine.
We have seen a few instances of the following:
Nobody using the phone.
No known internet connectivity issues.
Obi box online
Google Voice (on my machine where I am logged into my Google account) goes 'ping' and indicates that an inbound call has just been missed.
No inbound call is shown on the Obibox log.
If I call the same GV number from another phone (Eg Bobsled) the phone rings as usual for the inbound test call. If we call out to the number that just called us (the so-called missed call) it connects perfectly.
Last night this happened twice (from the same caller), a cell phone from area code 614.
Since there is nothing in the Obi log I suspect the problem is external to our home network - either in Google or in the ObiHai network.
Has anyone else seen this?
This just happened to me twice. Once about 30 min ago and once while I was typing this. Both times when my wife called from her cell. Another call came in about 10 min ago that rang all the phones as normal.
this has happened before but very very rare, I think perhaps less than 5 times in many months.
I am sure it is a google problem. I called my cell phone from my GV page using the google talk phone and my Obi rings fine.
Remember also, you can't have your gmail open in a browser or have Groove IP or Talkatone active on a cell phone. If you do the Obi will not be logged into the corresponding Google Voice account.
I'm experiencing this issue as well calling through two different obis/accounts/internet service addresses. So far no trouble using the gmail chat caller to make calls from gmail or using google voice through my cell phone using grooveip. Hopefully this is a small problem with a quick fix and not Google starting to block out great complementary products like the Obi.
Hi S--F, it is a coincidence. Other long time users who did not change any firmware yesterday, including me, noticed this same problem appear yesterday as well. Just bad timing for your problem but it is not related to the firmware upgrade.
Quote from: RFord on February 08, 2012, 08:07:38 AM
If you check the GV Help Forum you will see that a number of GV users who are NOT using the OBi ATA is experiencing just the problem you are having.
Could you provide a link to your reference? I see a number of posts on the Google Voice help forum regarding the inablility to obain a phone number in area code 503, but nothing that would appear to be related to the problems OBi users are experiencing.
See if these comments fit the bill?
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/LbvREN3XEmg (https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/LbvREN3XEmg)
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/zDVITEWnGJo (https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/zDVITEWnGJo)
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/TIvA2w75QSw (https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/TIvA2w75QSw)
etc.
etc.
;D
Edit:
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/4FaC9oxhGOs (https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/4FaC9oxhGOs)
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/no3AwYQwgHc (https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/no3AwYQwgHc)
Quote from: RonR on February 08, 2012, 10:04:19 AM
Quote from: RFord on February 08, 2012, 08:07:38 AM
If you check the GV Help Forum you will see that a number of GV users who are NOT using the OBi ATA is experiencing just the problem you are having.
Could you provide a link to your reference? I see a number of posts on the Google Voice help forum regarding the inablility to obain a phone number in area code 503, but nothing that would appear to be related to the problems OBi users are experiencing.
Could there be some form of conflict while having Groove IP running simultaneously on your Cell Phone? See issues with running Groove IP on this Forum.....
Quote from: mtown on February 08, 2012, 09:39:22 AM
I'm experiencing this issue as well calling through two different obis/accounts/internet service addresses. So far no trouble using the gmail chat caller to make calls from gmail or using google voice through my cell phone using grooveip. Hopefully this is a small problem with a quick fix and not Google starting to block out great complementary products like the Obi.
None of these threads appear to be about non-OBi users with problems even remotely related.
Quote from: RFord on February 08, 2012, 10:38:07 AM
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/LbvREN3XEmg
This thread appears to be about people having DTMF recognition problems when they press 1 to accept an incoming call.
Quote from: RFord on February 08, 2012, 10:38:07 AM
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/zDVITEWnGJo
This one person can't receive any Google Voice calls.
Quote from: RFord on February 08, 2012, 10:38:07 AM
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/TIvA2w75QSw
This is an OBi user.
Quote from: RFord on February 08, 2012, 10:44:02 AM
Could there be some form of conflict while having Groove IP running simultaneously on your Cell Phone? See issues with running Groove IP on this Forum.....
I have several Google Voice accounts with nothing but a single OBi connected to each of them. The 503 errors are very reproducible on each of the Google Voice accounts.
If you have Groove IP or Talkatone running on a cell phone then the Obi may not be logged into GV and therefor no service detected by the Obi and an error message returned.
In the past having gmail open in a browser also affected the Obi but that seems to be changing. I can now have my gmail open and still receive calls on the Obi.
Edit:
I just opened Talkatone on my iphone and successfully placed a call from both the app and from the Obi. An incoming call only rang the Talkatone app and the Obi did not ring.
Can't test Groove IP until later when an android phone is here.
I am also having the same problem in the last 2-3 days, in a very reproducible manner. Almost every alternate call through Obi110 and GV results in the male voice error message of the number being rejected by service provider and error 503. The maximum I have had to redial is three times, i.e 2 consecutive times it gave me same error, but third time the call went through. Usually the call goes through on the second attempt.
BTW, in order to further diagnose the issue, I have 1) tried turning on QOS in my router and turning off QOS. The error has occurred in both cases. 2) Additionally, I have run diagnostics on my IP setup and the 30Mbps internet connect is rock solid with no breaks in connections and no drops in pings (22ms to Google servers) and 3) The calls go through fine with no errors when I use the web front end of GV to make calls. and 4) I have updated to latest firmware ( the one which fixes the voice mail inidcator issues), with same error 503. I got the error 503 even with the firmware previous to the latest version.
At this point it looks like an issue between the Obi110 device and Google Voice. I hope the detail above helps Obihai in diagnosing the issue. I will be more than happy to help out in any manner, in getting to the root of the problem.
Thanks.
Quote from: RonR on February 08, 2012, 10:54:22 AM
Quote from: RFord on February 08, 2012, 10:44:02 AM
Could there be some form of conflict while having Groove IP running simultaneously on your Cell Phone? See issues with running Groove IP on this Forum.....
I have several Google Voice accounts with nothing but a single OBi connected to each of them. The 503 errors are very reproducible on each of the Google Voice accounts.
I just did it. No problems whatsoever. Completed in approx. 48 hours. Go for it!!
Quote from: BillS on February 08, 2012, 09:03:38 AM
I have the OBI110 up and running fine with GV. I am getting ready to port my Landline (with AT&T) to a AT&T Go Phone and then port to GV. I have read that many have done this. I chatted with AT&T to confirm it could be done and they said yes.
Just checking to see if anyone has had any issues doing this lately.
Thanks much
I just posted my experience with this error 503 in another thread. I am reproducing it below for your benefit.
BTW, I too upgraded the firmware yesterday and the error 503 occurred *both* before and after the firmware upgrade.
----------------------------------------------------------------------------------------------------------
I am also having the same problem in the last 2-3 days, in a very reproducible manner. Almost every alternate call through Obi110 and GV results in the male voice error message of the number being rejected by service provider and error 503. The maximum I have had to redial is three times, i.e 2 consecutive times it gave me same error, but third time the call went through. Usually the call goes through on the second attempt.
BTW, in order to further diagnose the issue, I have 1) tried turning on QOS in my router and turning off QOS. The error has occurred in both cases. 2) Additionally, I have run diagnostics on my IP setup and the 30Mbps internet connect is rock solid with no breaks in connections and no drops in pings (22ms to Google servers) and 3) The calls go through fine with no errors when I use the web front end of GV to make calls. and 4) I have updated to latest firmware ( the one which fixes the voice mail inidcator issues), with same error 503. I got the error 503 even with the firmware previous to the latest version.
At this point it looks like an issue between the Obi110 device and Google Voice. I hope the detail above helps Obihai in diagnosing the issue. I will be more than happy to help out in any manner, in getting to the root of the problem.
Thanks.
Quote from: RonR on February 08, 2012, 10:50:00 AM
None of these threads appear to be about non-OBi users with problems even remotely related.
Quote from: RFord on February 08, 2012, 10:38:07 AM
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/LbvREN3XEmg
This thread appears to be about people having DTMF recognition problems when they press 1 to accept an incoming call.
Quote from: RFord on February 08, 2012, 10:38:07 AM
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/zDVITEWnGJo
This one person can't receive any Google Voice calls.
Quote from: RFord on February 08, 2012, 10:38:07 AM
https://groups.google.com/a/googleproductforums.com/forum/#!category-topic/voice/making-and-receiving-calls/TIvA2w75QSw
This is an OBi user.
well I have my gmail open all the time in a browser... but I dont think it is that because:
a) the gmail in the browser did not ring either
b) if the gmail was 'winning' then the test call would have not rung the phone either.
Interestingly, this just happened to me 5 minutes ago. I had my phone next to me. It did not ring at all and the voicemail indicator started blinking. Checked the VM and there was a VM from an inbound call in the last 5 minutes, but the phone did not ring!!!
I wonder what is going on. As detailed in my other posts, I am now having two major issues, which has got my wife completely mad. On the outbound calls, almost every alternate call results in error message of number rejected by service provider and error code 503. And now for inbound call, the phone does not ring at all. Net result is that I am not able to have reliable phone service both outbound and inbound!!!
This is a major issue. It seems to be affecting multiple people. Can Obi support please look into it expeditiously?
For the record, I'm not experiencing the 503 error. I have yet to hear that, although my daughter told me she heard it several times last night on her obi100. She tried calling back 3 times to no avail. This has never happened before.
The reason I started this thread is only because I was getting voicemails without the phone ever ringing.
Hi S--F,
I too am now having your same problem ( as of last one hour) of phone not ringing but going directly to VM. I too upgraded the firmware yesterday and this problem has started today. Not sure if this is a coincidence or related to firmware upgrade. In addition, I am also having error 503 problem, which I definitely had even before the firmware upgrade.
Quote from: S--F on February 08, 2012, 12:15:58 PM
For the record, I'm not experiencing the 503 error. I have yet to hear that, although my daughter told me she heard it several times last night on her obi100. She tried calling back 3 times to no avail. This has never happened before.
The reason I started this thread is only because I was getting voicemails without the phone ever ringing.
My wife has called from her cell 4 times today and none of her calls rang my "google talk" forwarding phone. They did all ring my cell which is also a forwarding phone.
Only one other number called (twice) and both times it did ring all the forwarding phones including the Obi (google talk).
I called my GV number from my cell phone earlier and I don't think the Obi rang then either. I will have to test it and see about that.
Same problem here.
In fact, the problem started last night, when I was testing the newly arrived obi-110. First I got the error code 503. I didn't know what it was about. While I was testing more this morning, I cane to realize the phone did not ring at all.
I dont know what is Obi's user base. I am curious why so few people reported this problem thus far.
Having same issues as everyone above -- started today.
Please see posted comments on the GV Help forum (http://groups.google.com/a/googleproductforums.com/forum/#!categories/voice/making-and-receiving-calls). This issue is not at all confined to the OBi.
Thank you for your support.
OBiSupport,
Why are you deleting my posts?
Same problem experienced here. Glad to hear I'm not the only one experiencing this. I have only noticed it for the past 5 days or so. Multiple calls going straight to voicemail or missed -- without ringing the Obi. I also am not logged into Gmail in any way during these times.
I did just go into the Google Voice settings and uncheck all of the forwarding phones. Then, I re-checked the ones I wanted. Will see if anything improves, but I am wondering if it is a call routing error by GV.
Quote from: OBiSupport on February 07, 2012, 11:53:32 PMThe 503 error may indicate service being unavailable temporarily on the Google Voice connection.
If this is the case, that would make three separate problems recently observed due to GV. I just had the 503 error happen to me last night for the very first time. Tack on the missed incoming calls and loss of MWI prior to recent Obi updates, and the resilience of my phone setup appears to be going downhill quickly.
But let's hope for the best :) Maybe some solution(s) can be found!
same issues on my 2 obi110 and GV. started yesterday " error 503" and today it's hit and miss. :(
Earlier today I had one call that got "the number you called xxxxxxxxxx was rejected by the service provider". I redialed immediately and the call went through. I do currently have problems with certain calls ringing all my phones except my "google Talk" phone.
If it is a google problem, of course we know there is no support there.
While I was reading through the google voice help forum I made one change in my gmail. My wife just called again and all phones rang including the Obi and my Obion app.
Some posts on the help forum said their problem started after the new gmail interface. I changed back to the "old look" and now the call comes in correctly. I can't say for sure that was the problem but now it is working.
Give it a try and let us know what results.
Update:
My daughter called from her cell and it rang all forwarding phones except google talk.
I get the 503 error when calling out too. Also, I get incoming calls that I hear from my cell phone, but not from the Obi phone so if it were not for my cell phone, those calls would go to voice mail too. Unfortunately I don't want to use the minutes on my cell.
We set up our Obi110 with Google Voice and ported our home phone to GV. The process was flawless and it worked very well for a few weeks. Sometime in the past few days, we noticed that our phone stopped ringing. Our phone still dials out, just no incoming calls.
We went through the procedures in the FAQ, but nothing seems to be working.
Now I've had this today too! "the call was rejected by your service provider reason 503." I thought it was from the far end, at first, but I tried like 4 more times anyway. Then called my GV # from my cell phone. My Obi110 didn't ring. the OBI web status looked fine. but restarted it anyway and both issues cleared up. I have my obi110 restarting every morning already.. wierd.
Quote from: RonR on February 08, 2012, 01:23:26 PM
OBiSupport,
Why are you deleting my posts?
Uh-oh!! RonR, does that mean we won't be able to get any assistance (Technical Support) from you anymore. Shame on you OBiSupport!! ::) ;D
In an effort to consolidate all the related discussion topics/threads, please use this thread/topic to discuss the Google Voice 503 issue as it has been reported on multiple topics in the OBiTALK forum.
Some, but not all, Google Voice users are experiencing sporadic call failures on in-bound and out-bound calling using Google Voice. The message as read back by the OBi device refers to a "503" reason message. This message indicates service provider (Google Voice) network congestion or some other network or call routing issue causing calls to not be completed. This issue is not confined just to OBi users.
If you experience this issue, it has been observed that repeated tries will oftentimes result in a successful call.
Obihai technical support are monitoring the issue and will provide new information as it becomes available.
Thank you for your support!
Update 1:
We believe the issue to be on the mend.
For those of you experiencing call failures, please try some calls now and report back on your experience.
Thanks!
Quote from: OBiSupport on February 08, 2012, 04:05:41 PM
In an effort to consolidate all the related discussion topics/threads, please use this thread/topic to discuss the Google Voice 503 issue as it has been reported on multiple topics in the OBiTALK forum.
Some, but not all, Google Voice users are experiencing sporadic call failures on in-bound and out-bound calling using Google Voice. The message as read back by the OBi device refers to a "503" reason message. This message indicates service provider (Google Voice) network congestion or some other network or call routing issue causing calls to not be completed. This issue is not confined just to OBi users.
If you experience this issue, it has been observed that repeated tries will oftentimes result in a successful call.
Obihai technical support are monitoring the issue and will provide new information as it becomes available.
Thank you for your support!
Add another one with a pissed off wife who wants to get rid of the obi and go back to reliable pots
Quote from: OBiSupport on February 08, 2012, 04:23:29 PM
Update 1:
We believe the issue to be on the mend.
For those of you experiencing call failures, please try some calls now and report back on your experience.
Thanks!
Was the fix done by google as a result of a google voice problem or was it an obi issue?
The only way OBihai could have corrected the problem would be to PUSH an updated firmware to each OB Box (directly or indirectly). I haven't seen a reboot of my OBi110. Alternatively, in order for OBihai to know that the "issue to be on the mend", they would have to been some level collaboration between OBihai and Google. Is this the case...who knows.
Quote from: bennettg on February 08, 2012, 04:39:56 PM
Was the fix done by google as a result of a google voice problem or was it an obi issue?
As I reported in another thread that I do experience the inbound problem. I spoke to obihai earlier and they told me it was google's issue.
However, when I call a google voice number where the setup includes PC and headphone attached to PC, the desktop does receive the signal of an incoming call. To that end, google voice is working. What I am saying is obihai should look further into the problem given google voice@PC works and google voice@obi-110 not.
Of course my observation has "small sampling data" limitation.
Quote from: OBiSupport on February 08, 2012, 04:23:29 PM
Update 1:
We believe the issue to be on the mend.
For those of you experiencing call failures, please try some calls now and report back on your experience.
Thanks!
still not working for me. random inbound calls not ringing. obi support: please provide more specifics.
I just updated my firmware and am experiencing the similar issues. obi110
Worked fine before update
after update, hear stutter tones, indicating message.
could only call out for a couple hours.
Now I cannot call in or out.
receiving 503 code.
I am able to use the google web application to call, so it is unlikely the account that has the issue.
analogmonster,
See this thread: Inbound calls just plain stopped tonight? (http://www.obitalk.com/forum/index.php?topic=2957.0)
I got this today. Tried it twice. Added area code (local number) and it went through.
Outbound calls are sporadic, sometimes they go out, othertimes:
call was rejected by the service provider: reason is 503..
Inbound calls do not seem to be going through either currently..
My experience is just like analogmonster's. Got my 110 last week, hooked it up, and never had a problem until Tuesday night. Then I started getting some outgoing calls that would ring once and then I'd get a fast busy, but the call went through via the website. I figured I should update my firmware after looking at the posts here, so I did that. Now I get the 503 error, but the call goes through just fine when dialed via the Web. Whatever was done to fix the problem doesn't seem to have been enough!
Add me to the the list...since last night my incoming calls are no longer reaching my Obi. I also just tried placing a call and got the 503 error.
Hope they get this fixed SOON or I will have to find another provider instead of GV...
I think I found one of the reasons for this error.
Today when I tried to dial into my conference call - I got 503 error. I tried from OBIon on my iPhone and then with handset connected directly to OBI appliance.
Suspecting it was OBI issue, I tried calling from Talkatone app (also configured with google voice) and finally directly from google voice app.
The call failed every time with google voice saying - "This is not a valid number".
Finally, I called the number from my cell and was able to get through.
Final Take - THIS IS GOOGLE VOICE issue (at least for this case).
The real problem is that services like freeconferencecall use high connection fee numbers to make money and GV, being free doesn't want that surcharge. It could also be that these numbers are virtual, unregistered, voip numbers not recognizable by GV.
Read more about it here - http://groups.google.com/a/googleproductforums.com/forum/#!topic/voice/glPvnNQnpB8
Here is the GV log from inside gmail.com. obi110 was powered off. (408) xxx-xxxx is the same number. When called from cell phone to this number - it always work.
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:01 PM. Please wait a bit and try again.
Thank you!
(Error ID: f243822d993cf3af)
At 6:01 PM (408) xxx-xxxx was not available for a phone call.
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:02 PM. Please wait a bit and try again.
Thank you!
(Error ID: cf5437d0298c5bef)
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:02 PM. Please wait a bit and try again.
Thank you!
(Error ID: d9d3104b58a5ca68)
Sorry! The phone call with (408) xxx-xxxx failed because of a problem
with our servers at 6:02 PM. Please wait a bit and try again.
Thank you!
(Error ID: 872111814d33d386)
Is it time to forget about GV and move to other provider?
Ya, I have noticed this issue since the last 2 or 3 days too. It seems that rebooting the OBI110 device fixes this for a few hours, but then the problem returns.
Same issue here too.. redirected Google Voice number to secondary SIP installed as Line 1 for temp solution
Not fixed yet!
There is definitely a problem with Google Voice. However, the issue extends to the Obi as well. I have my cell phone set up with Google Voice, and my number is set to ring both on my cell and my Obi. Yesterday I was able to make calls on the Obi, but only to local numbers. Other numbers failed with the 503 error.
Then I received an incoming call, and my cell phone rang but NOT the Obi!! So I logged into the Obi and rebooted it, and then all was well again for a few hours, then it started acting up again.
So, it would appear that Google is choking, but after it comes back on-line, the Obi is NOT reconnecting properly. I looked for an option in the Obi setup to reboot every 24 hours and reconnect, but no such option was found.
Obi support, I realize that the initial problem is on Google's side, but you need to make a change to re-establish connection once the service is restored! If we can't rely on the phone service, then what good is it? I have an OOMA voip box as well, and have never had 1 problem with their service in 2 and 1/2 years! I bought my Obi as a second line for work, but now I'm questioning that decision.
Please address this issue quickly! Thank you.
The problem is with google, not the Obi. When google gets things worked out the Obi will again work properly. Many of us have not experienced any problems.
I also got this problem. It's almost 9 months. Are there have any solution?
a couple uses today so far and no issue after being able to repeat it at will yesterday.
Also started receiving the 503 call failure msg yesterday and today. In all cases just redialed and was able to place the call.
My calls originate from New Jersey (if this matters). So far seems to affect outbound call only. But then again how would I know if it is affecting inbound calls. ::)
I noticed i have this problem only when i dial the number immediately after taking phone off hook especially when using speed dial with # for quick dialing. it seems if i wait approximately 7 sec or so before i finish dialing, i don't get the 503 error. Perhaps others can try to see if the delay solves the problem or is just a coincidence?
PS. My friend who works with VOIP a bit says this is a COMMON PROBLEM WITH ata's DEVICES. He says it has to do with delays in sensing availability and termination of the line for the call. I continue to not have the 503 problem if i use a 7 or 8 second delay between calls.
Joseph
Quote from: JosephM on October 22, 2012, 12:00:34 PM
I noticed i have this problem only when i dial the number immediately after taking phone off hook especially when using speed dial with # for quick dialing. it seems if i wait approximately 7 sec or so before i finish dialing, i don't get the 503 error. Perhaps others can try to see if the delay solves the problem or is just a coincidence?
Thank you, JosephM, for this info & tip! (http://www.getsmile.com/emoticons/smileys-91853/w/thumbs.gif)
I started getting this
"rejected by the service" 503 error today when dialing the local numbers with the 281 area code. I followed your tip to dial the numbers manually to extend the dialing time instead of using the speed dial/memory dial and the calls went through with no problems. Thanks again!!!
Hi all:
I love my OBi202 so far, but I've experienced the 503 error a couple of times. A few days ago, before I upgraded the firmware, I couldn't call my bank. I tried two or three times (can't remember exactly) then gave up and called from another phone.
After the firmware upgrade, everything seemed to be working fine. But today, I couldn't call a friend and it was the same error as before. I'm not sure if I've missed any inbound calls.
I'm off to read the Google Voice threads recommended above, and will try the 7-8 second delay tip from above. I'll follow up later with the results I get using the delay.
My thanks to everyone who has been posting on this issue!
I think it's Google Voice. I have been having this "503" problem for several days now. It happens whether I call through my Obi phones or through my internet only laptop.
I did try the advice to wait a few seconds before dialing and that seemed to work this time.
Hope Google fixes it soon. How do we contact Google for information about this problem?
I didn't need to wait before dialing, I only dialed the numbers slowly like 1 digit/sec. (Thanks to Joseph's post).
I noticed that I didn't have this 503 problem anymore since this afternoon. Now I could dial from the phone directory with no problems.
I don't think some of you guys understand how a device like the OBi works. When you pick up the phone, you get dial tone generated by the device, not the service providier, and then it collects the digits you dial and only when you have completed dialing does it actually send anything to the service provider. Pausing between digits does nothing, nor does picking up the phone and waiting a few seconds before dialing, because either way nothing gets sent to the service provider until you finish dialing.
"But it works for me", you may say. That's called coincidence. You experience the problem and redial more slowly, and it seems to work. In actuality, redialing a second time seems to work much of the time, but it doesn't matter how fast or slow you dial. There is no VoIP adapter anywhere that sends digits to the provider individually as you dial them, before the call is connected - after that, if you are talking to a computer at the distant end of the call, that's a different story, but that's also not the service provider.
What Obihai could do that would help this situation is to make a firmware change that doesn't just accept the first 503 error and give up, but instead immediately retries the call. You might be able to make it work that way by creating a Trunk Group and specifying the same service provider, in this case your Google Voice account, multiple times. For example, if your Google Voice account is sp1, you could try using sp1,sp1,sp1 as the TrunkList value, which in theory would try the call three times before giving up. You'd then have to use the Trunk Group as the destination for your outbound calls. I don't know if that would actually work because I have never tried to create a Trunk Group; I just remember reading about them in the Obihai manual that you can download.
I'm having a similar issue with GV - Current call drops, then when I try to reconnect, I get the "there is no service available" message. GV works from my laptop. My obi100 is ring no answer on incoming calls.
Redialing the 2nd time, 3rd time, 4th time never worked for me if I used the memory dialing. After reading Joseph's post and doing what he said, I could dial out every time. Now the problem seemed to disappear so it's back to normal again. (http://www.getsmile.com/emoticons/smileys-91853/r/auskosten.gif)
Could GV be using Callcentric behind the scenes ::)
google voice is the cause of the 503 almost positively. If you get disconnected calls and stuff like that, go to your obi Status Page and check out the Uptime. I bet it's pretty low. That indicates the Obi has rebooted for no apparent reason. Normally it will have a code like (3) next to the time if it is a planned reboot.
Reboots are Obi problems, sometimes caused by services it connects to but still it should handle such issues better than spontaneously rebooting.
Quote from: MikeHObi on October 25, 2012, 04:20:31 PM
Reboots are Obi problems, sometimes caused by services it connects to but still it should handle such issues better than spontaneously rebooting.
This may be the Achilles heel of the OBI. Whether it is still true, the PAP2 ata has a reputation for having echo issues. I hope that this problem doesn't get out from this forum. Sometimes these things are hard to shake off once people start talking about it. Until they fix the spontaneous reboots, mum's the word on this. OK folks!
Quote from: JosephM on October 22, 2012, 12:16:32 PM
PS. My friend who works with VOIP a bit says this is a COMMON PROBLEM WITH ata's DEVICES. He says it has to do with delays in sensing availability and termination of the line for the call. I continue to not have the 503 problem if i use a 7 or 8 second delay between calls.
Joseph
Joseph,
Thanks to you and your ATA Device Expert Friend, I'm able to make outgoing without the "reason 503" error by slowing down my dialing to about one digit per second. However, I still have a problem with incoming calls occasionally not ringing.