OBiTALK Community

Hi,
Problem here - Google Voice and Obi202, calls made from home to outside getting the error code 503 (Rejected by service provider) - no matter to what number we call, usually redialing 2-3 times the call gets thru - started since yesterday, no recent firmwares done.
has anyone else having the same problem? is this OBi or Google Voice issue?

thanks!

adi9,

At the moment this seems to be shared by several who have reported it here on this forum. It seems that it might be related to issues with Callcentric. Any chance you are using CC?

Hi,
No, I am using Google Voice as the primary one (anveo as secondary but dont use it to call out just as fax line), all calls comes in and go out using google Voice.

Same problem here, not using CallCentric nor any other provider on Obi110, only Google Voice.

What's up?

"Call was rejected by the service provider. Reason is 503."

adi9, obiJuanKanobi,

Perhaps there is a pattern that we can spot. If you like can you provide the "X" portion of your GV number:
(XXX) XXX-1111

(415) 673-NNNN

(360) 356-NNNN

(240)745-xxxx

My wife has experienced this 503 error multiple times over the last 2 days.  I do use call centric and have disabled it after she reported it the first time.  But today after it being disabled she has received that error 503 twice.   Both times if she retries the call it will connected.

Both were to local calls for our gv number.  One a residence, the other a hospital.  I happened to see the call status on one attempt, and it showed something about an "Announcement" when she was given the 503 message.

I wish I could have more advance logging for stuff like that which could be reviewed afterwards.

MikeHObi,

You have a syslog on the OBi. If you would like to document it in order to understand what might be happening.
System Management=>Device Admin=>Syslog

Free syslog servers
http://tftpd32.jounin.net/
http://www.vercot.com/~serva/

GV# (717) 308-XXXX.

Quote from: QBZappy on October 20, 2012, 02:39:20 PM
MikeHObi,

You have a syslog on the OBi. If you would like to document it in order to understand what might be happening.
System Management=>Device Admin=>Syslog

Free syslog servers
http://tftpd32.jounin.net/
http://www.vercot.com/~serva/

Thanks.  I'll look into that.  my GV number is (651) 321-XXXX

Same problem here in NH area code 603.  Actually, first day I'm using my Obi so glad it's service provider and not the Obi itself. Will be testing for the next couple of weeks with GV to see if it's reliable enough for regular use.  If not, will try another provider for a while.  Meanwhile, still have the pots line connected as backup.

Exact same problem here with GV, sometimes takes up to three tries before the call will go through. 
(239) 206-XXXX and (239) 963-XXXX

I just now noticed that my obi110 didn't have the latest firmware.  We'll see if it helps.

I have two phone lines with two different obi100 boxes. I'm using two different Google Voice numbers for them. I experienced yesterday twice error message "503". Yesterday I called a number and I  heard  the ring tone but nobody answered. I called from my cell phone and the person answered and told me that she did not hear the ring tone from my first call. Today  I got error message "503" several times from my other obi100 box.

I cannot find any announcement from Google Voice or Obitalk explaining this.
Does anybody knows more about the background of error "503"?

For phone, this is a highly unreliable service.

Went with The Dude from MicroTik. http://www.mikrotik.com/thedude.php
Logging is up now, so hopefully I can catch it acting up again.  I am curious if this the Obi kicking that message or Google Voice.

503=Service Unavailable

I looked up these numbers to see if there where some commonalities. If these are GV numbers they seem to be occuring in different parts of the country at difference Rate Centers. It still is not obvious if it is a hardware (OBi firmware) or GV issue. Although at this point we cann't be certain at what is causing this, I would have a difficult time pointing fingers at GV since after a quick look around at voip forums and searching Google itself, I cann't find other GV users complaining about the GV service. "If you eliminate the impossible, whatever remains, however improbable, must be the truth". At the moment the evidence seems to be pointing at the OBi.

Telcodata
http://www.telcodata.us/

(651) 321 State=MN Rate Center=STCROIXBCH MN
(415) 673 State=CA Rate Center=SNFC CNTRL CA
(360) 356 State=WA Rate Center=VANCOUVER WA
(240) 745 State=MD Rate Center=DAMASCS236 MD
(717) 308 State=VA Rate Center=DOVER VA State=PA Rate Center=DOVER PA
(239) 206 State=FL Rate Center=NAPLES FL
(239) 963 State=FL Rate Center=NAPLES FL

Edit: Made correction

I've been getting the 503 failure code when dialing a number in the 703 (Virginia) area code, it started with some regularity later in the week. First saw it Wed, then Thu and on Fri got it a lot.  I dial the same number in area code 703 a lot.

My suspicion: I've been seeing intermittent off behaviors in my Obi202 and I'm quite certain they are related to the CallCentric up and down (intermittent connectivity) issues.  So, even though the 503 failed call is going out on GV, based on recent observations, my suspicion is CallCentric is the root cause. 

Is it a commonality that all people reporting the issue have one or more CC services setup?  Also, an important detail to add, I was seeing these intermittent off behaviors in my device even when the CC voice service was disabled, maybe the ITSP profile for CC (where the DNS SRV names are reoslved) was still imposing a latent effect?   

Side note: area code 717 in your list Code is in south central PA, not VA, map (http://www.nanpa.com/area_code_maps/display.html?pa). In fact the rate center yo umention is in area code 703

Attached is a Syslog of it not working.  I don't know enough to understand what it tells me.

I have changed the phone number to be 1234567890.  In a section where it looks like it is doing DTMF ON and shows a number, it appears it did it wrong or out of order.  As it shows it in the order of the log as toning 1234569780 (note the 9 between the 6 and 7)

Though the CCTL:NewCallOn Term16[0] shows the correct number and order.
It shows GTALK:sess callsess stage change from 0 to 2.
Then GTALK:sess callsess stage change from 2 to 6
then GTALK:not redirect or redirect with no content:503!

So I wonder if the Obi is not sending the right number to Google talk

Natch... upload folder is full so I cant upload the log here it is shared on google docs. Has embedded nuls that I haven't got rid of yet so can't preview.  have to download.  It's a csv.
https://docs.google.com/open?id=0B7jTkH327MqqQmZiUE1XOXRpd0k

Not sure who is telling me 503 error by reading back the number dialed (read back correctly) but if it is Google, then the issue is with Google.  If it is the Obi, perhaps the obi told google talk the wrong number, but the obi knows the right number so it reads back to me the right one.

MikeHObi,

If it is a
Male voice= OBiMAN.
Female voice=GV

There are at least 2 threads on https://productforums.google.com/forum regarding GV and error reason 503. After reading both, they both involve OBi users.

https://productforums.google.com/forum (SEARCH REASON 503)
https://productforums.google.com/forum/#!search/reason$20503/voice/9DToDQ1516E/6p8oUFdlV2oJ
https://productforums.google.com/forum/#!search/reason$20503/voice/YPp8XrRCJ_E/FYaf3zZW8z8J
Here was another run on this forum during the beginning of Feb 2012, when a similar "reason 503" was affecting users.

Google Voice Sporadic Call Failures, e.g. "503 Issue"
http://www.obitalk.com/forum/index.php?topic=2516.0

This was the official OBi response the last time this 503 business happened.

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!

Same thing happening here

GV# 631-223-XXXX

Yeah... I'm thinking this google talk failure.  The app status shows it up, but I can't find a good way to even notify google that there is an issue, and even if I did I wouldn't know how to explain it.  I think Obi may need to try to get in touch with them to let them know there is an issue.

And it's a male voice.

MikeHObi,

If it is a GV issue, it seems odd that I can not find others talking about it in the popular voip forums. If you google it, you will find any mention of it pointing back to this forum.

Using OBI110 GV# 212 865 XXXX
I had the 503 problem with calls to  718, 212, 305 area codes and calls to the UK as well.

Same here for the past couple days. (858) area code.

Having the same issue with Google Voice. Usually the call goes through on the second attempt.

I am receiving the 503 error when calling Canada from the US. Domestic calls seem to be fine. I do not have this problem when dialing the Canadian number directly from Gmail or initiating the call on the Google Voice website and having it call me at Google Chat (which rings my home phone connected to the Obi).

Has anyone else tried calling through Google Chat (Gmail) directly or using the callback function on the Google Voice website to diagnose whether this is a Google Voice issue or a Obi interface to Google Voice issue?

My GTalk 410 449-xxxx experiencing the 503's for past two days after nearly 4 months of perfect service.  I use almost exclusively outbound.  May be unrelated, but seems to have closely followed a FW upgrade to my 110.

Quote from: QBZappy on October 20, 2012, 09:21:17 PM
MikeHObi,

If it is a GV issue, it seems odd that I can not find others talking about it in the popular voip forums. If you google it, you will find any mention of it pointing back to this forum.

Perhaps a GoogleChat API issue? How many other people (but us) are programmatically accessing GoogleVoice as often?

I've had the same problem with 503 Google Voice call rejections since the most recent Obi device update. Usually local calls made from my 317 area code. Sometimes recalling works. I have no problem calling out with Google Voice not using Obi.

The call dropped today after about 15 mins and when I tried to call back twice I got the 503 message.

I'm experiencing the same thing. I have the OBi202 w/ GV.  I ported the number from Frontier to an old T-Mobile cell phone and then ported into GV.  I don't know if porting has anything to do with this issue.

My number is 503-649-XXXX.  The first number that I couldn't call was a bank. 503-601-XXXX and this was a few days ago before the firmware upgrade.  Then today, I couldn't call a friend at 503-524-XXXX.  So, I don't think the firmware is the problem.

I have Frontier FioS for my internet.  And I'm using the OBiWiFi.  A few people from the other thread on the 503 error suggested getting a dial tone, then waiting 7-8 seconds before dialing the number.  I'm going to try that if I get the error again and will post the results.

Some folks suggested dialing 1 first on the GV forum. I'll try this as well.