Starting today unable to mke GV calls. WAs fine as of yesterday.
When I dial out just get busy tone.
Tried deleting the device and reconfig.
Tried both on a obi110 and a obi100.
Status on obitalk portal shows GV as connected
unable to make gv calls even in gmail chat. seems like a google problem.
I was able to make call using Google.com/vioce call feature with no issues.
Is the marriage with Obi in trouble?
Quote from: arvind1971 on April 21, 2011, 07:20:36 PMIs the marriage with Obi in trouble?
FWIW, there's no problem making calls from the OBi through Google Voice from here.
i guess it's only some google accounts that are affected because i'm unable to dial out. i keep getting a busy signal on obi. on chat, i get this:
Sorry! The phone call with (xxx) xxx-xxxx failed due to an error [Code: 3 Remote: true] at 7:34 PM.
Click here to report this to Google.
Any suggestions?
Quote from: arvind1971 on April 21, 2011, 07:09:51 PMStatus on obitalk portal shows GV as connected
Are you looking at the OBi's System Status Page?:
Status -> System Status -> SPx Service Status -> Status
checked status.
Status Connected.
No issue on Callcentric configured as sp2
Do your outgoing GV calls show up in the Call History?
Fails for me as well; every call attempt results in a busy tone.
I have tried several different GV accounts; all fail. Just started today
around noon.
If I call from an regular cell phone to a GV # setup to connect to Google Chat,
the incoming call alert pops up in my Safari window, but does complete when
I click answer - probably a red herring. Will reinstall Gchat plugin and report back.
If I make call through obi then no it is neither connecting (busys signal) nor it shows in history.
If I make through google site then yes.
Also tried form my android phone it goes through fine
Quote from: arvind1971 on April 21, 2011, 07:54:06 PMIf I make call through obi then no it is neither connecting (busys signal) nor it shows in history.
Are you looking in the OBi's Call History?
Are you looking in the OBi's Call History?
[/quote]
Yes it does show in history
See attached screen shot.
I would suggest capturing the call with Syslog as described in the following thread and see if it sheds any light on the problem:
http://www.obitalk.com/forum/index.php?topic=707.0
Computer Gmail CallPhone is not working from certain IP addresses since earlier this afternoon.
Since OBi connection to GoogleVoice is equivalent to Gmail CallPhone, dialed numbers will return busy, incoming calls won't connect either.
There has been reports sent to Google Forum. Need to wait till Google fix this problem.
Quote from: OBi-Guru on April 21, 2011, 08:17:54 PM
Computer Gmail CallPhone is not working from certain IP addresses since earlier this afternoon.
Since OBi connection to GoogleVoice is equivalent to Gmail CallPhone, dialed numbers will return busy, incoming calls won't connect either.
There has been reports sent to Google Forum. Need to wait till Google fix this problem.
You might consider posting known issues like this in the "Firmware / Advisories / Notifications for OBi Products" section of the forum so users don't wonder if their OBi has failed.
I had the GV problem since around 2pm, I can tell be cause I was making GV call into my obi just before that, then I added a speed dial, save config, reboot obi, then GV started to fail, all along I thought it was the OBi110 problem, I rebooted and reloaded different versions of saved config from backup, none of these helped, I was thinking that the OBi110 depends on OBi server to make GV call, and OBi server must be down. I suspected this because calls to ob222222222 also fail, however calls to ob333333333 has no problem reaching aa, yet, neither option "2" nor option "3" results in successful calling.
My question is: does ob333333333 uses GV for outgoing call? and why does ob222222222 fails?
Quote from: daibaan on April 21, 2011, 08:30:03 PMMy question is: does ob333333333 uses GV for outgoing call? and why does ob222222222 fails?
I can't answer your question, but I can confirm that **9 222 222 222 fails with a "No response from service provider" message and **9 333 333 333 fails as you noted.
Quote from: OBi-Guru on April 21, 2011, 08:17:54 PM
Computer Gmail CallPhone is not working from certain IP addresses since earlier this afternoon.
Since OBi connection to GoogleVoice is equivalent to Gmail CallPhone, dialed numbers will return busy, incoming calls won't connect either.
There has been reports sent to Google Forum. Need to wait till Google fix this problem.
Any link to google forum to track?
I wonder if this is relevant:
http://www.google.com/support/forum/p/gmail/thread?tid=01e357607ba65c50&hl=en
There are several listed here:
http://www.google.com/support/forum/p/voice/label?lid=7c2a1629dac84e4d&hl=en
**9 222 222 222 was out of service in the last hour and is now up running (nothing to do with GV service being down).
**9 333 333 333 is working but the subsequent outgoing call on GV service isn't working due to GV down.
syslogs if it makes sense to anyone
^C
C:\>syslogd -nl -s=all
[Apr 21 21:22:12][192.168.2.142]<7> [SLIC]:Slic#0 OFF HOOK
[Apr 21 21:22:12][192.168.2.142]<7> [CPT] --- FXS SiLab h/w tone generator ---
[Apr 21 21:22:14][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 1 @ 6957
0 ms----
[Apr 21 21:22:14][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 69710 ms ----
[Apr 21 21:22:14][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 8 @ 6984
0 ms----
[Apr 21 21:22:14][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 69990 ms ----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 0 @ 7010
0 ms----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 70260 ms ----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 0 @ 7037
0 ms----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 70520 ms ----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 3 @ 7064
0 ms----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 70790 ms ----
[Apr 21 21:22:15][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 2 @ 7091
0 ms----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 71060 ms ----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 8 @ 7117
0 ms----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 71340 ms ----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 8 @ 7146
0 ms----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 71610 ms ----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 7 @ 7172
0 ms----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 71870 ms ----
[Apr 21 21:22:16][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 9 @ 7199
0 ms----
[Apr 21 21:22:17][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 72140 ms ----
[Apr 21 21:22:17][192.168.2.142]<7> [DSP]: ---- H/W DTMF ON (level:1) : 7 @ 7226
0 ms----
[Apr 21 21:22:17][192.168.2.142]<7> [DSP] ---- H/W DTMF OFF @ 72410 ms ----
[Apr 21 21:22:19][192.168.2.142]<7> GTT:call state changed from 0 to 2
[Apr 21 21:22:19][192.168.2.142]<7> GTALK:sess callsess_3 state changed from 0 t
o 2
[Apr 21 21:22:19][192.168.2.142]<142> PARAM Cache Write Back(256 bytes)
[Apr 21 21:22:20][192.168.2.142]<7> GTALK:sess callsess_4 state changed from 2 t
o 6
[Apr 21 21:22:20][192.168.2.142]<7> [CPT] --- FXS SiLab h/w tone generator ---
[Apr 21 21:22:20][192.168.2.142]<7> RTP:Del Channel
[Apr 21 21:22:24][192.168.2.142]<7> [SLIC] FAX MODE --- OFF
[Apr 21 21:22:24][192.168.2.142]<7> [SLIC]:Slic#0 ONHOOK
[Apr 21 21:22:28][192.168.2.142]<7> [SLIC]:Slic#0 OFF HOOK
[Apr 21 21:22:28][192.168.2.142]<7> [CPT] --- FXS SiLab h/w tone generator ---
[Apr 21 21:22:31][192.168.2.142]<7> [SLIC] FAX MODE --- OFF
[Apr 21 21:22:31][192.168.2.142]<7> [SLIC]:Slic#0 ONHOOK
^C
**9 222 222 222 is still failing, now, instead of OBi announcing service not answering, I can hear the remote side ring once, then silence, then call dropped -- back to dial tone
Quote from: daibaan on April 21, 2011, 10:05:29 PM
**9 222 222 222 is still failing, now, instead of OBi announcing service not answering, I can hear the remote side ring once, then silence, then call dropped -- back to dial tone
It's a bit slow to connect here, but the echo test finally works.
Quote from: RonR on April 21, 2011, 10:17:03 PM
Quote from: daibaan on April 21, 2011, 10:05:29 PM
**9 222 222 222 is still failing, now, instead of OBi announcing service not answering, I can hear the remote side ring once, then silence, then call dropped -- back to dial tone
It's a bit slow to connect here, but the echo test finally works.
Nop, still does not work for me, same ring once, then dial tone symptom
Getting the same thing. Thought my obi died on me guess its google. Hope they get this fixed soon.
This was also an issue for PBX in a Flash users yesterday:
http://pbxinaflash.com/forum/showthread.php?p=63891
What it is with Google Voice? It appears they just aren't content to leave well enough alone. Seems like every couple of weeks they break functionality for some subset of their users, and sometimes the problem gets fixed and sometimes it doesn't (inbound call functionality for Asterisk is still severely broken, unless you resort to having Google Voice send the calls to a DID and then bringing that into Asterisk).
I don't know what their plans are for after 2011, but if this is the level of service they plan to offer to paying customers they had better stop and re-think that, because no one who is paying real money for their service would accept all these outages without complaint.
I guess we get what we pay for. I've switched to CallCentric for outgoing calls.
GV staff is now aware:
http://www.google.com/support/forum/p/voice/thread?tid=5928ae65c67a57e2&hl=en&fid=5928ae65c67a57e20004a18597dea8c5