GV issue

Found something wrong ?
Post Reply
macovet1
Posts: 27
Joined: Sun Jan 02, 2011 9:09 pm

GV issue

Post by macovet1 » Tue Feb 07, 2012 3:08 pm

A few days ago GV stoped working properly.
Most of the times I'm getting the following message with out being able to place a call:
"Google Voice Call timed out waiting for callback."

To be more accurate, there are some times (20%) that GV calling is working like in the old times. Some other times the connection is not automatic, I have a new incoming call ringing in my device, so I need to hang up and I take the incoming call to speak.

GV loging, incoming calls etc. seems to work properly.

Code: Select all

DialPlan 14:54:41:426 sip1(2060): New call from udp:46.12.84.91:5074 successfully authenticated by digest.
DialPlan 14:54:41:441 sip1(2060): Using dialplan xxxx for Out call to sip:xxxxxxx@sipsorcery.com.
NewCall 14:54:41:457 sip1(2060): Executing script dial plan for call to xxxxxxxx
NATKeepAlive 14:54:41:504 sip1(5856): Requesting NAT keep-alive from proxy socket udp:69.59.142.213:5060 to udp:xx.xx.xx.xx:xxxx.
DialPlan 14:54:41:520 sip1(2060): ** Call from "xxxxx" <sip:xxxxx@sipsorcery.com>;tag=4842dbd7fcc88e2co3 to xxxxxxxxxxx **
DialPlan 14:54:41:520 sip1(2060): Calling xxxxxxxxxxxx via Google Voice
DialPlan 14:54:41:520 sip1(2060): SDP on GoogleVoiceCall call had RTP socket mangled from 192.168.xx.xx:xxxx to 46.12.84.91:16766.
DialPlan 14:54:41:520 sip1(2060): UAS call progressing with Ringing.
DialPlan 14:54:41:520 sip1(2060): Logging into google.com for xxxxxxxx@gmail.com.
NATKeepAlive 14:54:41:520 sip1(5856): Requesting NAT keep-alive from proxy socket udp:69.59.142.213:5060 to udp:46.12.84.91:5062.
DialPlan 14:54:41:582 sip1(2060): Google Voice pre-login page loaded successfully.
DialPlan 14:54:41:582 sip1(2060): GALX key TDPalCpcyLE successfully retrieved.
DialPlan 14:54:42:176 sip1(2060): Google Voice home page loaded successfully.
DialPlan 14:54:42:207 sip1(2060): Call key I0cMeTrChEOqMK445EQ855Nk6PY= successfully retrieved for xxxxxx@gmail.com, proceeding with callback.
DialPlan 14:54:42:207 sip1(1924): SIP Proxy setting application server for next call to user xxxxx as udp:69.59.142.213:5070.
DialPlan 14:54:42:566 sip1(2060): Google Voice Call to xxxxxxxxxxxxx initiated, callback #xxxxxxxxxx, phone type 1, timeout 30s.
DialPlan 14:55:12:567 sip1(2060): Google Voice Call timed out waiting for callback.

carter
Posts: 14
Joined: Fri Feb 10, 2012 5:26 am

Re: GV issue

Post by carter » Fri Feb 10, 2012 5:34 am

I am having a similar issue:
starting from yesterday (Feb 08), Google Voice calls have become erratic, and today
they fail 100% for both incoming and outgoing

Code: Select all

Google Voice Call timed out waiting for callback
can be seen in the outgoing call logs

anyone has an idea?

carter
Posts: 14
Joined: Fri Feb 10, 2012 5:26 am

Re: GV issue

Post by carter » Fri Feb 10, 2012 6:04 am

As for incoming calls, GV phone does NOT even ring: I used my mobile to call GV phone number and was sent to GV VM after 20s or so...

btw, I am using GV+SIPGate
incoming calls work for SIPGate number, so it could be an internal GV issue, maybe the free service is coming to an end early?

Aaron
Site Admin
Posts: 4652
Joined: Thu Jul 12, 2007 12:13 am

Re: GV issue

Post by Aaron » Fri Feb 10, 2012 11:15 am

My GV calls are currently working with callbacks through sipgate and anveo. However my calls may not be the best gauge since I only ever ring a single test number.

ozimarco
Posts: 51
Joined: Fri Nov 18, 2011 3:49 am
Location: Lower Chittering, WA

Re: GV issue

Post by ozimarco » Fri Feb 10, 2012 1:52 pm

My GV calls are currently working with callbacks via IPKall.
ISP: Telecube ADSL2+, $79 for 250GB (bundled with phone) on regional Telstra exchange
VSPs: MyNetFone, Telecube, Maxotel, Freshtel and others via SIPSorcery
Hardware: Asus DSL-AC68U + Siemens Gigaset A580IP and Yealink T22P.

synchron
Posts: 196
Joined: Fri Jun 26, 2009 5:39 am

Re: GV issue

Post by synchron » Fri Feb 10, 2012 7:28 pm

My GV calls are working "fine" with all 3 of my providers, however:

1) IpComms calls last only 30 sec. (this has been going on for several months)
2) Sipgate last 90 sec. (this has been recent)
3) IPKall last indefinitely (or at the GV 3 hour cutoff).

Who would have guessed IPKall is the best free provider now in 2012?? Go figure.

Synchron 8)

carter
Posts: 14
Joined: Fri Feb 10, 2012 5:26 am

Re: GV issue

Post by carter » Fri Feb 10, 2012 9:46 pm

Today (Feb 10), both incoming and outgoing GV calls are working fine with GV + SIPGate, so it's probably a glitch fixed by itself.

As for various providers, SIPGate has been the most stable (no 90s cutoff for me).
I always had a big problem with IPKall: incoming calls sometimes (>=50% chance) have no sound or one-way audio, this is obviously a headache and an embarrassment when using IPKall number as a primary number
Let's see if it gets any better in 2012!

mackeev
Posts: 34
Joined: Tue May 18, 2010 5:14 am

Re: GV issue

Post by mackeev » Thu Feb 16, 2012 5:55 am

I've just checked my IPComms number with GV (outbound via sys.GoogleVoiceCall method). It was definitely longer than 30 sec. IPKall and Sipgate also work fine for me.
synchron wrote:My GV calls are working "fine" with all 3 of my providers, however:

1) IpComms calls last only 30 sec. (this has been going on for several months)
.........

Synchron 8)
Are your IPComms SIP settings pointing at you@sipsorcery.com? This is crucial.

carter
Posts: 14
Joined: Fri Feb 10, 2012 5:26 am

Re: GV issue

Post by carter » Wed Feb 22, 2012 8:54 pm

Ok, just want to have a follow-up regarding the GV situation. In the past week, I have tested with all three free DID providers I have with GV and this is what I found out (outgoing calls only):

1) GV + SIPGate: no ring, no forwarding, none whatsoever, call to GV directly goes to VM
2) GV + IPKall: error message "this number is not available for call return, goodbye“
3) GV + IPComms: error message "this number is not available for call return, goodbye“

I guess the previous "glitch" turned out to be a major turn of the events, SIPGate is NOT allowing GV forwarding anymore (or vice versa, GV is not forwarding to SIPGate) --- at least in my case. I am a bit surprised that nobody else reported similar issues yet, maybe it is account specific (then it is more troubling) ?

On the bright side, I confirm that indeed IPKall is much more stable in 2012, no single call drop so far (incoming only of course)!

btw, I am not running a commercial server or anything massive if that's what you are wondering.

Post Reply