Is Google Voice down for Obihai connections?

Started by Alak, December 16, 2018, 02:44:28 PM

Previous topic - Next topic

Alak

I've had Google Voice working successfully with my Obi200 for many months now and today all of a sudden it can no longer make outgoing calls.  Google Voice is showing "Offline" and when I tried to delete and reconfigure it, it won't connect back to Google Voice.  The configuration process goes on for a long time and then it eventually ends up as offline.  The Obi200 works fine with Callcentric on SP2 so the Obi200 is fine.  I can make and receive calls on Google Voice separately so Google Voice seems to be fine.  The problem seems to somehow be between Obihai and GV.

Are other people having the same problem?

Thanks!
Alak.

PeterFales

Who is your ISP?   My  own Obi is working fine, but my father's went down today after working just fine for many months.   My diagnosis so far is that "something" is blocking connections to the Obi network.    We know the Obi is connected to the network because the internal call status page shows "Connected" and he can make outgoing calls. However, the Obitalk dashboard shows him offline, and the **9-222-222-222  number does not work.  So it looks to me like he is connected to the network in general, but is being blocked from connecting to the Obi server.

I have no proof of this, but I'm guessing that something changed on his router (either accidentally, or on purpose) like a firmware upgrade, or something changed in the comcast network (again either deliberately or accidentally)

Alak


drgeoff

#3
My calls to the echo test number **9 222 222 222 are also failing with the verbal message "There is no service available to complete your call".  The Obitalk Service Status is showing as "Backing Off (over TCP)".

As I'm in the UK I rather doubt our symptoms are caused by a common ISP.

Obihai does not have 24/7 maintenance on their servers.  Don't expect a fix before Monday morning business hours, US west coast.

However, having said the above, once an Obi has been successfully configured for GV, GV calls to and from an Obi do not require any Obihai server to be operational.  I am able to make outgoing GV calls.  I cannot say either way about incoming GV calls.

Alak

Thanks for the additional confirmation in the UK!

In the meantime, I also tried disabling SIP ALG on my Netgear router but it didn't help.  Anyway it had been working just fine with SIP ALG enabled so that wasn't it.  I guess we'll have to wait for Obihai to resolve this.  I also filed a support ticket with them for this.

Alak.

dboling

#5
More of obiHAi crap infrastructure taking down google voice.  Can't obiHAi afford a decent set of DNS servers, better yet why isn't Google supplying their own DNS ?

Dec 16 18:23:44 obi212  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:45 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:45 obi212  TCP:Connect Failed(pnn)36
Dec 16 18:23:46 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:47 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:49 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:50 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:51 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:52 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:53 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:54 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:55 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:56 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:57 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:58 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:59 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:00 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:01 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:02 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:03 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:04 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:05 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:06 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:07 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:08 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:09 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:10 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:11 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:12 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:13 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:14 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi212  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi212  BASE:resolving root.pnn.obihai.com
-Diane

drgeoff

Quote from: dboling on December 16, 2018, 03:25:50 PM
More of obiHAi crap infrastructure taking down google voice.  Can't obiHAi afford a decent set of DNS servers, better yet why isn't Google supplying their own DNS ?

Dec 16 18:23:44 obi212  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:45 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:45 obi212  TCP:Connect Failed(pnn)36
Dec 16 18:23:46 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:47 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:49 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:50 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:51 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:52 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:53 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:54 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:55 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:56 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:57 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:58 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:59 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:00 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:01 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:02 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:03 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:04 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:05 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:06 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:07 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:08 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:09 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:10 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:11 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:12 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:13 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:14 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi212  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi212  BASE:resolving root.pnn.obihai.com

You are writing nonsense.

1.  Obihai servers falling over do NOT impact on an already configured OBi's ability to make or receive GV calls.

2.  Obihai do not have DNS servers. 

dboling

Quote from: drgeoff on December 16, 2018, 03:32:53 PM
Quote from: dboling on December 16, 2018, 03:25:50 PM
More of obiHAi crap infrastructure taking down google voice.  Can't obiHAi afford a decent set of DNS servers, better yet why isn't Google supplying their own DNS ?

Dec 16 18:23:44 obi212  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:45 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:45 obi212  TCP:Connect Failed(pnn)36
Dec 16 18:23:46 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:47 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:49 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:50 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:51 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:52 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:53 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:54 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:55 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:56 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:57 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:58 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:23:59 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:00 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:01 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:02 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:03 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:04 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:05 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:06 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:07 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:08 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:09 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:10 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:11 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:12 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:13 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:14 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi202  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi212  BASE:resolving root.pnn.obihai.com
Dec 16 18:24:15 obi212  BASE:resolving root.pnn.obihai.com

You are writing nonsense.

1.  Obihai servers falling over do NOT impact on an already configured OBi's ability to make or receive GV calls.

2.  Obihai do not have DNS servers. 

I jumped the gun on the post as I don't see those requests in /var/log/named

These are the only DNS requests I see from /var/log/named from my 202 and 212.

16-Dec-2018 18:37:24.267 queries: info: client 192.168.3.61#55230: query: obihai.telephony.goog IN A + (192.168.3.1)
16-Dec-2018 18:37:24.384 queries: info: client 192.168.3.60#57651: query: obihai.telephony.goog IN A + (192.168.3.1)

However both my 202 and 212 were connected to GV and are now down after this regular scheduled outage
-Diane

PeterFales

As of this evening, **9 calls are working (it was down all afternoon).    I'm still not able to "Add Device" to my account, but the device can now make **9 calls.   (The device has been reset to factory settings, has no service providers, and is not showing on my account)

PeterFales

And a little later this evening, it's all working.  I was successful with "Add device"

JohnOrion

#10
Quote from: drgeoff on December 16, 2018, 03:32:53 PM

You are writing nonsense.

1.  Obihai servers falling over do NOT impact on an already configured OBi's ability to make or receive GV calls.

2.  Obihai do not have DNS servers. 

she may not be saying the right terms but NO you cant make or receive calls today on the OBi .. you can on google voice just not using the OBi .. I still cant make or receive calls on the OBi since 4PM EST (but I got a disconnect email earlier so the problem was happening much earlier.. I just wasn't home to mess with it)

OK .. haven't tried it yet .. probably have to reboot OBi and redo the GV activation but ever since 9:16PM est the log changed and I no longer have the resolving root.pnn.obihai.com error

Yep seems to be working like it did before .. it will ring for the first phone call after going to the webpage and the google voice settings and verifying my email again for the hundredth time then the next call it wont ring again until I again go through the process of redoing the GV setting .. this has been the most useless POS for the whole year I have owned it .. what a waste of money

johnkeo

thanks for letting me know as i was looking for similiar query

Donamy

I'm unable to add a new box I got today, after my other one got broken. Is it a coincidence, Obitalk is down ?

drgeoff

Quote from: Donamy on December 17, 2018, 10:49:21 AM
I'm unable to add a new box I got today, after my other one got broken. Is it a coincidence, Obitalk is down ?
The **9 222 222 222 echo test number is working fine as I type this.  Have you passed that stage?

Donamy


Alak

Hi Guys,

This is still broken for me and no-one responded to my support ticket.

Alak (OP)

SteveInWA

Quote from: Alak on December 18, 2018, 08:40:43 PM
Hi Guys,

This is still broken for me and no-one responded to my support ticket.

Alak (OP)

Carefully read and exactly follow the instructions in my post linked below.  Do not skip or change the order of any instructions.

http://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076

Alak

Quote from: SteveInWA on December 19, 2018, 12:40:48 AM
Quote from: Alak on December 18, 2018, 08:40:43 PM
Hi Guys,

This is still broken for me and no-one responded to my support ticket.

Alak (OP)

Carefully read and exactly follow the instructions in my post linked below.  Do not skip or change the order of any instructions.

http://www.obitalk.com/forum/index.php?topic=13868.msg89076#msg89076

Thanks Steve!

Following your instructions to remove the device from ObiTalk, perform a factory reset, and then reconfigure back the device from scratch worked to solve my problem!  I don't know why this was needed now after working well for so long but this is good to know.

Alak.