Is anyone else having the call failure with Reason 503 right now
DunkinFx:
Problem is with Google - http://www.google.com/appsstatus (Thanks to BJAS for the link)
runningout:
I got 503 as well. It's weird though.
When I started having problems with the phone I couldn't dial up but would receive no error it just simpy would nto dial out but I could still receive inbound calls as the phone would ring. I reboot the phone and still the asme problem. So I rebooted again and now I'm receiving a 503 error on outbound calls and inbound calls do nto ring the phone as it goes to my e-mail.
I connected locally to my obi device to see if it was even registering the calls I make outbound and or inbound which I found out it is. Therefore I went on another google account with a seperate number and dialed my main google number that's attached to the obi phone as well as that number is attacked to my cell as well. No ring on the obi or cell, therefore I am under the assumption that the obi device is working good and it's a google issue based on it not ringing my cell.
DunkinFx thank you I had no idea that page even existed.
xari:
I am having exactly the same problem all day today. I can't place or receive calls. It's been working well for over a month without any problems.
I've had a number of different symptoms. Tried setting my google voice password on the obitalk site. I also deleted my google voice account and the device and readded them. I rebooted the device, router and cable modem. Symptoms have been:
1) When dialing out voice says,There is no service available to complete your call
2) When dialing out voice says, The number you dialed xxx, was rejected by the service provider: reason 500
3) When dialing out, after long delay get noise on the line and nothing else.
4) When dialing in, nothing - goes to voicemail on gvoice
sir_rob:
I started having the 503 rejected issue yesterday. Is there any solution yet?
Macintheus:
I just had this problem myself. The first time it happened, I tried dialing first without, then with area code, and got the 503 message both ways. Then I restarted the OBi100 and dialed the same number (including area code) and the call went through. I then called a different local number with no area code (I input my local area code in the OBi100 setup so as to avoid having to dial it for local numbers) and got the 503 message again. I called the same number again but included the area code and the call went through this time.
So a couple of things to try: reboot your OBi device, and try dialing with area code.
Navigation
[0] Message Index
[#] Next page
[*] Previous page