Google Voice Call Failures with reason 503
MikeHObi:
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.
QBZappy:
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
CoalMinerRetired:
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. In fact the rate center yo umention is in area code 703
MikeHObi:
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
MikeHObi:
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.
Navigation
[0] Message Index
[#] Next page
[*] Previous page