Using firmware 4.0.5 (Build: 5903EX), working fine yesterday and since the new firmware update. Suddenly all configured GV lines on multiple 508 and 504 units at multiple sites cannot connect to the GV accounts with "Connect Failed: No Response". Outbound calling states number not available. Inbound calls no ring. Am able to connect to Obi's remotely. Anyone else experiencing this issue? Seems like it could be a Google Voice issue since it brought down multiple lines and units, but would like to get out in front of this issue if Google Voice is not the problem.....
Yes, something's gone awry. Another poster (http://www.obitalk.com/forum/index.php?topic=15390.0) and myself confirm.
As those TV captions used to say "Do not adjust your set".
I am having this same issue, has anyone figured out a fix? I am using the Obi200, and it just happened to me today for the first time.
Me too. Done multiple resets, deleted and re-added device. No joy. Anyone have an update on this?
I am using an Obi200 device and had the same issue starting this afternoon.
Looking at the google voice settings (legacy page), the familiar Google Chat box that needs to be enabled for the service to work appears to be missing.
My guess (and I am no Google expert) is Google changed google voice and removed the chat connection option. They have been migrating over to hangouts for VoIP and likely killed the old method the Obi used to connect.
Hopefully Obihai can come up with a firmware update the fix the connection method....
Again this is my educated guess.....
I am having the same issue tonight with Google Voice on my Obi200. I have factory reset, deleted the OBI out of Google Voice, then set it all up again to no avail.
Quote from: Greek_God on December 07, 2018, 09:55:00 PM
Looking at the google voice settings (legacy page), the familiar Google Chat box that needs to be enabled for the service to work appears to be missing.
Chat was killed off earlier this year and the Chat box was removed from that Settings page months ago. Instead for each OBi configured with your GV number you should see two lines of the form:
OBiTALK device – *********
sip:******************************************************************===@obihai.sip.google.com
where the first of those two lines contains the 9 digit number of the OBi and the second has a long string of random looking numbers and upper case letters.
Seems many of us got failed connections tonight, December 7th. I've had my Obi200 working with GV for 3 and a half months with no issues whatsoever. Now, like others are experiencing, it simply won't connect.
same thing happened to me at the same time as everyone else apparently
This appears to be on the Obi/Google side. I took a sniffer trace and the obihai.telephony.goog proxy server is not responding properly. It is closing the connection abnormally.
Connect issues
Obihai 202 hx 1.4
fw 3.2.2 (Build: 5898EX)
started 12/7/2018
2 GV lines, both now show the following after multiple reboots
Connect Failed: No Response (server=64.9.241.172; retry in XXXs)
Same here on my Obi 200. Been working great for a long time and suddenly last night I am dead in the water.
Same here - received email "Service Offline Alert -- OBi Device (xxxxxxxxx) is Not Registered " at 1:45am MST on Dec 8, 2018.
ObiTALK dashboard says "Connect Failed: No Response" for SP1 and SP2.
Obi202, SoftwareVersion 3.2.2 (Build: 5898EX)
Submitted a support request to Obi.
- Wayne
I strongly suspect this is something caused by GV, that only GV can rectify and not something that Obihai support can fix for you. Once your OBi device is successfully configured for GV the connection is between your device and GV servers.
Although several people are reporting the same issue, it is not affecting everyone. As I type this I have an Obi200 with GV showing as connected.
add me to the list of Google Voice users with issues.. hope the issue is resolved soon
I have 7 devices spread across 4 locations connected variously to 4 GV numbers. 3 Obi1022 devices lost their connections yesterday, same as others reporting, the others remain connected and working fine - to the same numbers. Other devices are an Obi1062 and 3 Obi200 devices remain connected to the numbers. The 3 1022 units with problems are connected to numbers that both the Obi1062 & 2 of the Obi200 units are connected to.
Obi1022 & Obi1062 units all on firmware 5.1.11
I'd speculate there is some regional problem with Obi or GV. Of course lots of possible causes for that. The units having problems are in Houston & connected to internet via AT&T. The others are in Michigan (Spectrum), Oklahoma (Suddenlink) & California (Comcast/Xfinity).
For those of you that are working, what IP address is it connected to?
My failed IP was also the 64.9.241.172, which is what googles 8.8.8.8 and 8.8.4.4 DNS are resolving to. Doing a dig via the internet a new IP comes up 216.239.36.144. It looks like this outage is the result of some DNS changes on the obihai.telephone.goog DNS name.
For those of you that are still having issues switching your DNS away from google's DNS may fix it. I switched my DNS server to cloudfare's 1.1.1.1 and it is now connected. Or you can wait for DNS to converge and it should correct on it's own....eventually.
SP1 Service Status
Status Connect Failed: No Response (server=64.9.241.172; retry in 139s)
Quote from: wuench on December 08, 2018, 11:00:06 AM
For those of you that are working, what IP address is it connected to?
That is not easy to answer as it just shows "Connected" with no mention of the IP address.
However, during a call it shows the peer RTP address as 74.125.39.42
Quote from: wuench on December 08, 2018, 11:00:06 AM
For those of you that are working, what IP address is it connected to?
My failed IP was also the 64.9.241.172, which is what googles 8.8.8.8 and 8.8.4.4 DNS are resolving to. Doing a dig via the internet a new IP comes up 216.239.36.144. It looks like this outage is the result of some DNS changes on the obihai.telephone.goog DNS name.
For those of you that are still having issues switching your DNS away from google's DNS may fix it. I switched my DNS server to cloudfare's 1.1.1.1 and it is now connected. Or you can wait for DNS to converge and it should correct on it's own.
Great sleuthing to figure that out, thank you!
I suddenly have the same issue as well. Tried deleting device, reseting obi to factory and reconnecting. Still get the connect failed: no response.
Stable since Obihai 202 reconnected at 1:15pm CT 12/8/2018 on my 2 GV numbers assigned to the device. ISP is AT&T Uverse in Dallas. Down since 8:45pm CT 12/7/2018.
Agree it is a DNS issue, I just looked into the logs on my pihole\unbound setup
Previous dig for obihai.telephony.goog
was
now
- obihai.telephony.goog. 3527 IN CNAME c.telephony.goog.
c.telephony.goog. 3600 IN A 216.239.36.144
Switching DNS1 from 8.8.8.8 to 1.1.1.1 resolved the issue for me as well.
Thanks for posting a work around. :)
Quote from: wuench on December 08, 2018, 11:00:06 AM
For those of you that are working, what IP address is it connected to?
My failed IP was also the 64.9.241.172, which is what googles 8.8.8.8 and 8.8.4.4 DNS are resolving to. Doing a dig via the internet a new IP comes up 216.239.36.144. It looks like this outage is the result of some DNS changes on the obihai.telephone.goog DNS name.
For those of you that are still having issues switching your DNS away from google's DNS may fix it. I switched my DNS server to cloudfare's 1.1.1.1 and it is now connected. Or you can wait for DNS to converge and it should correct on it's own....eventually.
Thanks for figuring this out! My phones are working again.
Note that the domain name is obihai.telephon
y.goog
Ping this to see if you are getting the new IP address. Your router might have a diagnostic command to do this.
On your computer, flush your DNS cache first.
(For example: ipconfig /flushdns)
ping obihai.telephony.goog
Quote from: S_in_Forum on December 08, 2018, 12:05:16 PM
Switching DNS1 from 8.8.8.8 to 1.1.1.1 resolved the issue for me as well.
Thanks for posting a work around. :)
Where do I switch the DNS? On the computer, the router, or the Obi200?
I changed the DNS setting on my router.
But, I suppose you can change the DNS settings on the OBi device instead.
Quote from: wuench on December 08, 2018, 11:00:06 AM
For those of you that are working, what IP address is it connected to?
My failed IP was also the 64.9.241.172, which is what googles 8.8.8.8 and 8.8.4.4 DNS are resolving to. Doing a dig via the internet a new IP comes up 216.239.36.144. It looks like this outage is the result of some DNS changes on the obihai.telephone.goog DNS name.
For those of you that are still having issues switching your DNS away from google's DNS may fix it. I switched my DNS server to cloudfare's 1.1.1.1 and it is now connected. Or you can wait for DNS to converge and it should correct on it's own....eventually.
Thanks. I am using 8.8.8.8 as my DNS server in my router.
It fixed itself with time. Odd that Google's DNS didn't get updated when Google's Goovle Voice server was changed.UPDATE: I got an e-mail from OBiTALK that SAID it was working but when I tested it I still can't make calls.
UPDATE 2: I changed the DNS on the OBi200 to 1.1.1.1 and 1.0.0.1 and rebooted. Working now. Fingers crossed.
Quote from: wseltzer on December 08, 2018, 01:07:42 PM
I changed the DNS setting on my router.
But, I suppose you can change the DNS settings on the OBi device instead.
I have an ATT Gateway, which doesn't allow me to change the DNS. If anyone knows how to make the change on the OBI200, I'd appreciate it.
Changing the DNS server to 1.1.1.1 doesn't help in Dallas, Tx with Spectrum.
ping obihai.telephony.goog yields 64.9.241.172 no matter which DNS provider I go with
(Google - 8.8.8.8, Cloudflare - 1.1.1.1, Cisco/OpenDNS - 208.67.222.222).
i changed dns setting on my router, didn't work
If you are using ping you will need to flush the dns cache between tests. ipconfig /flushdns. An easier way to test is to use nslookup, it will ignore the cache.
nslookup obihai.telephony.goog 1.1.1.1
Also if you are just changing this on your router, you may need to reboot your obihai and/or router to clear the caches there.
I changed the dns entry on the obihai and had to reboot for it to take.
$ nslookup obihai.telephony.goog 1.1.1.1
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: obihai.telephony.goog
Address: 64.9.241.172
Looks like the DNS updates aren't quite working yet.
I just purged the cache on 1.1.1.1 for obihai.telephony.goog
https://1.1.1.1/purge-cache/
and now their DNS server is returning the new address again, 216.239.36.144
I changed my Obi's DNS to 1.1.1.1 and 1.0.0.1 and I'm back in action.
Not sure if it just flushed the cache.
If you can't find where to do this, go to the IP address of your device in a web browser (something like http://192.168.1.54 ) and use admin/admin to login.
Go to System Management -> WAN Settings.
Uncheck DNSServer1 and DNSServer2 at Default on the right.
Enter: 1.1.1.1 in one and 1.0.0.1 in the other.
Save at the bottom.
Reboot at the top right.
That's what did the trick for me.
Quote from: josephstern on December 08, 2018, 03:11:26 PM
I changed my Obi's DNS to 1.1.1.1 and 1.0.0.1 and I'm back in action.
Not sure if it just flushed the cache.
If you can't find where to do this, go to the IP address of your device in a web browser (something like http://192.168.1.54 ) and use admin/admin to login.
Go to System Management -> WAN Settings.
Uncheck DNSServer1 and DNSServer2 at Default on the right.
Enter: 1.1.1.1 in one and 1.0.0.1 in the other.
Save at the bottom.
Reboot at the top right.
That's what did the trick for me.
I tried this, and it didn't work. What did work, however, was a similar action. I unchecked the DNSserver1 box and entered 1.1.1.1. I left the DNSserver2 box checked. Now it's working. Thanks guys!
For me setting the DNS to 1.1.1.1 and flushing the DNS cache worked only intermittently - the proxy IP address kept going bad.
I fixed it on my 1022 phone by going to the local (built in to the phone) web interface (in my case typing 192.168.1.16 into my browser address field), then:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
6. Select Reboot at the top of the page
Quote from: Chronoblast on December 08, 2018, 04:00:52 PM
For me setting the DNS to 1.1.1.1 and flushing the DNS cache worked only intermittently - the proxy IP address kept going bad.
I fixed it on my 1022 phone by going to the local (built in to the phone) web interface (in my case typing 192.168.1.16 into my browser address field), then:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
6. Select Reboot at the top of the page
Do not follow this advice. Never hard-code server IP addresses; they can change in the future, and then you will have a difficult-to-diagnose problem that nobody can help you figure out, because nobody does this.
It is entirely unnecessary. When IP addresses change, it can take some time for the new IP address to propagate to all DNS servers. After that happens, there's no need to reference a server's IP address.
It's a work-around, and it worked for me on both OBI200s. After someone reports that the DNS change has been propogated (at least to the ATT DNS server), without making a change, I'll change it back!
It works just fine on the Google DNS (8.8.8.8 ) and on the Quad9 high security DNS (9.9.9.9)
Quote from: josephstern on December 08, 2018, 03:11:26 PM
I changed my Obi's DNS to 1.1.1.1 and 1.0.0.1 and I'm back in action.
Not sure if it just flushed the cache.
If you can't find where to do this, go to the IP address of your device in a web browser (something like http://192.168.1.54 ) and use admin/admin to login.
Go to System Management -> WAN Settings.
Uncheck DNSServer1 and DNSServer2 at Default on the right.
Enter: 1.1.1.1 in one and 1.0.0.1 in the other.
Save at the bottom.
Reboot at the top right.
That's what did the trick for me.
You can also access the "Expert Settings" from the ObiTalk.com pannel, but the steps are nearly the same, and oddly, doing it there does not require a reboot - mine found the new DNS service immediately on saving!
BTW, if you want to use the IP address as Joseph shows doing, dial ***1 from any phone on your Obihai box to see what the IP address is.
(I have mine reserved as a specific address by the router, but oddly at times it wants to use something else anyway.)
Quote from: wuench on December 08, 2018, 11:00:06 AM
For those of you that are working, what IP address is it connected to?
My failed IP was also the 64.9.241.172, which is what googles 8.8.8.8 and 8.8.4.4 DNS are resolving to. Doing a dig via the internet a new IP comes up 216.239.36.144. It looks like this outage is the result of some DNS changes on the obihai.telephone.goog DNS name.
For those of you that are still having issues switching your DNS away from google's DNS may fix it. I switched my DNS server to cloudfare's 1.1.1.1 and it is now connected. Or you can wait for DNS to converge and it should correct on it's own....eventually.
Just tried this switch and its working fine now
Quote from: Chronoblast on December 08, 2018, 04:00:52 PM
For me setting the DNS to 1.1.1.1 and flushing the DNS cache worked only intermittently - the proxy IP address kept going bad.
I fixed it on my 1022 phone by going to the local (built in to the phone) web interface (in my case typing 192.168.1.16 into my browser address field), then:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
6. Select Reboot at the top of the page
Thank you Chronoblast! What a great workaround. I use OpenDNS on my network so it is resolving wrong IP too. My Google Voice service came right up with the local DNS entry!
This worked for me as well on my Obi200. Just went to expert settings and followed the directions below:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
I am not expert user. Are you guys saying that the problem is with Google Voice DNS server? It has been fixed, however, the corrected address has not been propagated to all the home devices yet. That means, if I wait for another day or so, my Obi200 will work again. Do I understand correctly?
Chris
Quote from: chriszing on December 08, 2018, 06:08:35 PM
I am not expert user. Are you guys saying that the problem is with Google Voice DNS server? It has been fixed, however, the corrected address has not been propagated to all the home devices yet. That means, if I wait for another day or so, my Obi200 will work again. Do I understand correctly?
Chris
What happened was the IP address assigned to the GV server url was changed, but that had not yet propagated to the various DNS servers, but eventually should. But yes, you should see the OBI200 working soon. Use the workaround only if you need it today.
Quote from: Chronoblast on December 08, 2018, 04:00:52 PM
For me setting the DNS to 1.1.1.1 and flushing the DNS cache worked only intermittently - the proxy IP address kept going bad.
I fixed it on my 1022 phone by going to the local (built in to the phone) web interface (in my case typing 192.168.1.16 into my browser address field), then:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
6. Select Reboot at the top of the page
Thanks Chronoblast, this fixed my Obi202 that wouldn't work using 1.1.1.1 or others. I logged into the webpage for the Obi and set the local DNS entry there, rebooted and all was fixed. I'll just have to remove the entry when the issue is resolved.
SteveInWA said: "Do not follow this advice. Never hard-code server IP addresses;"
@SteveInWA - I totally agree. It is foolish and reckless. Only do it if you want your phone to work.
Then set a reminder to erase this entry after a few days.
Quote from: keithobri on December 08, 2018, 05:44:59 PM
This worked for me as well on my Obi200. Just went to expert settings and followed the directions below:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
thanks for the tip; unfortunately for me, i cannot make any changes to the DNS settings.
Thanks to whoever posted it's a DNS issue. I've google mesh router and it's default DNS is 8.8.8.8 and I was getting the connect failed error.
But the moment I switched the router to use Spectrum's DNS, both my google voice accounts connected immediately.
thanks for the tip; unfortunately for me, i cannot make any changes to the DNS settings.
[/quote]
Same here. My AT&T U-Verse/Pace unit doesn't allow manual DNS settings.
Quote from: DG3CA on December 09, 2018, 03:42:00 AM
thanks for the tip; unfortunately for me, i cannot make any changes to the DNS settings.
Same here. My AT&T U-Verse/Pace unit doesn't allow manual DNS settings.
The settings are being changed on the obihai not the router. I also have AT&T , the changes are to the obihai by logging in to the obihai's IP using admin/admin as the user and password then follow chromblast steps here: http://www.obitalk.com/forum/index.php?topic=15391.msg96475#msg96475
Same thing has happened to me. I seem to have the same issue since yesterday. I am using the 202 device. Please let us know what the fix is. I an using OpenDNS and I an still getting this message. I will try Cloudflare to see if this fixes the issue.
QuoteThe settings are being changed on the obihai not the router. I also have AT&T , the changes are to the obihai by logging in to the obihai's IP using admin/admin as the user and password then follow chromblast steps here: http://www.obitalk.com/forum/index.php?topic=15391.msg96475#msg96475
i re-read the post (from the link above), made the change and GV is working for me now. my miss was not logging "directly onto the obitalk device" using the IP address assigned by my router. :)
UPDATE: Device Offline AgainOBI202 device is offline again due to the DNS record changed at 9:00am CT 12/9/2018
for
changed back to
Note: this is the configuration that is now *not working* for an unknown reason as of 12/7/2018.1. Using
Expert Configuration https://www.obitalk.com/obinet/pg/obhdev (https://www.obitalk.com/obinet/pg/obhdev)
Select Service Providers > ITSP Profile A SIP > Outbound Proxy
Uncheck both
OBITalk Settings and
Device Default2. Replace
with
3. Click the
Submit button
Repeat for ITSP Profile B SIP, ITSP Profile C SIP, ITSP Profile D SIP as needed for your environment.
To revert, swap c.telephony.goog with obihai.telephony.goog in step 2 and recheck both OBITalk Settings and Device Default
This is what worked for me. I switched to Cloud Flare and after doing the fix below, I rebooted the phone by using the phone menu (*** option 9).
Finally!!! Thanks to all who worked on this. I have been down for three days!!!
Quote from: keithobri on December 08, 2018, 05:44:59 PM
This worked for me as well on my Obi200. Just went to expert settings and followed the directions below:
1. On the menu on the left select System Management, then WAN Settings
2. Scroll down to Local DNS Records
3. Uncheck the Default box on record 1
4. Put:
obihai.telephony.goog=216.239.36.144
5. Select Submit at the bottom of the page
Same problem here. I deleted the obi device out of my google voice, and now it won't reconnect. Have gone through the reset and re-add steps numerous times. What do I do?
Quote from: torchredraider on December 09, 2018, 08:53:28 AM
UPDATE: Device Offline Again
OBI202 device is offline again due to the DNS record changed at 9:00am CT 12/9/2018
for
changed back to
Note: this is the configuration that is now *not working* for an unknown reason as of 12/7/2018.
1. Using Expert Configuration https://www.obitalk.com/obinet/pg/obhdev (https://www.obitalk.com/obinet/pg/obhdev)
Select Service Providers > ITSP Profile A SIP > Outbound Proxy
Uncheck both OBITalk Settings and Device Default
2. Replace
with
3. Click the Submit button
Repeat for ITSP Profile B SIP, ITSP Profile C SIP, ITSP Profile D SIP as needed for your environment.
To revert, swap c.telephony.goog with obihai.telephony.goog in step 2 and recheck both OBITalk Settings and Device Default
I had same issue in Houston area. Thanks to Torchredraider! Your recommended configuration changes worked perfectly. I now have incoming and outgoing calls working perfectly. Appreciate you posting the solution.
Folks, Torchredraider's solution is the correct one. You can view all of Torchredraider's posts about this evolving issue here:
http://www.obitalk.com/forum/index.php?action=profile;u=29101;sa=showPosts
Torchredraider's latest post at 8:53:28am today (12/9/18) is the best way to get your phones working while we are waiting for Google and Obihai to resolve this issue.
Actually, my OBI is a 200. Quit working like many others after a couple of years in service. Got the "out of service". Couldn't make outgoing calls nor receive incoming. Here's what finally worked for me:
After diddling with the DNS changes, etc and not having it work I decided to go all out.
1. Removed my OBI from the dashboard.
2. Did a factory reset.
3. Added my OBI back to the dashboard.
4. Changed the DNS servers to 1.1.1.1 and 1.0.0.1 (my router DNSes had been changed to these earlier.
Now everything is working again. Can make outgoing calls, receive incoming calls which now ring.
Of course it's possible OBI and/or Google coincidently fixed everything at the same time I was doing all this and my changes didn't have anything to do with it :)
-jj
Quote from: Jay-Jay on December 10, 2018, 12:05:28 PM
Actually, my OBI is a 200. Quit working like many others after a couple of years in service. Got the "out of service". Couldn't make outgoing calls nor receive incoming. Here's what finally worked for me:
After diddling with the DNS changes, etc and not having it work I decided to go all out.
1. Removed my OBI from the dashboard.
2. Did a factory reset.
3. Added my OBI back to the dashboard.
4. Changed the DNS servers to 1.1.1.1 and 1.0.0.1 (my router DNSes had been changed to these earlier.
Now everything is working again. Can make outgoing calls, receive incoming calls which now ring.
Of course it's possible OBI and/or Google coincidently fixed everything at the same time I was doing all this and my changes didn't have anything to do with it :)
-jj
All you needed to do was to change DNS servers. None of the other stuff was necessary, nor advised.
Quote from: Jay-Jay on December 10, 2018, 12:05:28 PM
After diddling with the DNS changes, etc and not having it work I decided to go all out.
Steve,
If you read my post, just changing the DNS addresses on my router, nor changing them on the OBI through the web interface did NOT help. I had to go through the process of removing the OBI, doing a factory reset, and then adding it back and making the DNS changes. It was not hard to do.
And why in the heck would this not be advised? What harm is there in doing a factory reset and starting fresh?
-jj
Quote from: Jay-Jay on December 10, 2018, 02:32:53 PM
Quote from: Jay-Jay on December 10, 2018, 12:05:28 PM
After diddling with the DNS changes, etc and not having it work I decided to go all out.
Steve,
If you read my post, just changing the DNS addresses on my router, nor changing them on the OBI through the web interface did NOT help. I had to go through the process of removing the OBI, doing a factory reset, and then adding it back and making the DNS changes. It was not hard to do.
And why in the heck would this not be advised? What harm is there in doing a factory reset and starting fresh?
-jj
Have you equated "nor advised" and "nor advisable"? They have different meanings.
Talk to Steve before issuing a citation from the grammar police. He used it first. :) You are correct, there is a difference, though I think everyone reading these posts can figure out what is meant, either way. Hope I don't have any dangling participles or misplaced commas. I wouldn't be able to sleep tonight.
Nuff said for me. Enough wasted bandwidth.
-jj
Quote from: Jay-Jay on December 10, 2018, 02:52:09 PM
Nuff said for me. Enough wasted bandwidth.
That's a typical ploy by someone trying to close off a debate when knowing to be on a losing wicket.
It is quite clear that the "advised" in your "And why in the heck would this not be advised?" was intended to have the meaning of "advisable".
Neither the fix posted by torchredraider nor SteveInWA's posts included resetting and starting again. SteveInWA's comment "None of the other stuff was necessary, nor advised." was accurate.
Quote from: drgeoff on December 10, 2018, 03:10:55 PM
Quote from: Jay-Jay on December 10, 2018, 02:52:09 PM
Nuff said for me. Enough wasted bandwidth.
That's a typical ploy by someone trying to close off a debate when knowing to be on a losing wicket.
It is quite clear that the "advised" in your "And why in the heck would this not be advised?" was intended to have the meaning of "advisable".
Neither the fix posted by torchredraider nor SteveInWA's posts included resetting and starting again. SteveInWA's comment "None of the other stuff was necessary, nor advised." was accurate.
"nor advised" means: people post "solutions" here that are either unnecessary or incorrect. Then, other people read the post, and they take that "solution" as gospel, and then spread the gospel. The result is wasted time and effort, by other people. Some people make things worse, by following the unnecessary instruction, but screwing it up, and now they have two problems. Therefor, I was pointing out that the only thing necessary to solve this problem was to change the DNS. Doing other things may or may not hurt, but they are not, by themselves, the actual solution.
Don: "My car won't start. What should I do?"
Dave: "Have you tried waving a rubber chicken over the starter? I did that after I replaced my car battery, and now the car starts fine."
After waiting three days for Obihai and Google Voice to implement DNS change with no result, I changed DNS to 1.1.1.1. Everything has been working. Just wonder what is the situation now. When should I change it back to standard setting? Should I leave it alone until something fails again?
Quote from: chriszing on December 12, 2018, 06:40:42 PM
After waiting three days for Obihai and Google Voice to implement DNS change with no result,
That shows you don't understand DNS. "implement DNS change" is, and never has been, something that OBihai or GV could do.
So mine stopped working *again*.
I had changed to cloudflare's 1.1.1.1 and 1.0.0.1 servers.
Changed that back. Nothing.
Change the outbound proxy to "c.telephony.goog" and I'm back in action.
Can't wait to see what next week brings.
Today I received an e-mail from admin@obitalk.com that said "Your OBi Device (...) is Offline". When I checked it a couple of hours later it was fine.
After last week's problems I had changed the DNS to 1.1.1.1/1.0.0.1 and that resolved last week's problem.
my GV went out days ago and we never noticed. A simple OBI device reboot resolved the issue for us (Dec 28). The OBI dashboard was slow and reported offline even though it was working for at least 30 minutes..
(Obi200)
Update 3/12/2019
Obi202 offline and unable to connect to GV as of 1:15am CT.
Began diagnosis at 1:00pm, same day.
Multiple reboots via web interface and re-saving of GV credentials did not improve connection.
Replaced c.telephony.goog with obihai.telephony.goog by re-checking OBiTALK Settings in ITSP Profile A SIP menu and clicking save.
Device reconnected after 30 seconds.
Reference
dig c.telephony.goog and dig obihai.telephony.goog returned same IP address (216.239.36.144), unsure of cause
Quote from: torchredraider on March 12, 2019, 01:45:47 PM
Replaced c.telephony.goog with obihai.telephony.goog by re-checking OBiTALK Settings in ITSP Profile A SIP menu and clicking save.
Device reconnected after 30 seconds.
Reference
dig c.telephony.goog and dig obihai.telephony.goog returned same IP address (216.239.36.144), unsure of cause
Thanks. Your post helped me fix the same problem.
I had 2 OBi 200s connecting to the same GV account. One worked and the other gave the error message about being unable to connect to 216.239.36.144. I checked the config on the one that wasn't working and for some reason I had c.telephony.goog listed instead of obihai.telephony.goog. I made the switch and it connected immediately.
I can't speak to how the OBiTALK portal configures Google Voice on 508s, but on the 200/202 configuration, obihai.sip.google.com is automatically configured, and is the correct value. During the beta, there were a couple of other values used, but this is now the "production" value.
Unrelated to that, although 508s can use Google Voice, it is not recommended. The free, consumer version of Google Voice is neither intended nor supported for business use. Google can and does shut down accounts for abuse if it becomes aware of calling patterns associated with call center or telesales, or any other sort of business use that involves high-volume outbound calling. If that happens, you lose all of your Google Voice phone numbers. Now that Google has a paid, commercial version of Google Voice for G Suite customers, it's a good bet that they will step up enforcement.
It's best to use a 508 with one or more paid ITSPs.
Quote from: torchredraider on March 12, 2019, 01:45:47 PM
Update 3/12/2019
Obi202 offline and unable to connect to GV as of 1:15am CT.
Began diagnosis at 1:00pm, same day.
Multiple reboots via web interface and re-saving of GV credentials did not improve connection.
Replaced c.telephony.goog with obihai.telephony.goog by re-checking OBiTALK Settings in ITSP Profile A SIP menu and clicking save.
Device reconnected after 30 seconds.
Reference
dig c.telephony.goog and dig obihai.telephony.goog returned same IP address (216.239.36.144), unsure of cause
Thanks for this, my disconnect was resolved following this post.
Having similar problem on my OBI202 device with 2 different google voice accounts set up as SP1 and SP2 -- was working fine for I think, more than a year...
Now in last coupl'o'weeks the connection to google is going on and off a few times a day, seemingly random -- if I don't notice it, I get auto-email warnings like this from no-reply@obitalk.com :
"Service Offline Alert -- OBi Device (5004xxxxx) is Not Registered
Your voice service is not registering. This could be due to a temporary service disruption or an incorrect login credential.
In most cases, reconfiguring the voice service with the proper login credential will resolve the issue. "
I checked that obihai.telephony.goog is set. So that's not the problem...
Help!