Can't make or receive calls using GVoice since this morning
SteveInWA:
DNS service supplied by ISPs is notorious for either not getting promptly updated, or redirecting bad DNS queries to some advertisement or other bogus destination.
Use a DNS other than your ISP's DNS.
These should be promptly updated, and they are spam/malware free:
Google's DNS: 8.8.8.8 and 8.8.4.4
Quad9 DNS: 9.9.9.9 (this DNS is run by a consortium of Internet security companies, including IBM, and hosted by IBM).
wsalopek:
EDIT...
I figured it out...I had changed the firewall security settings on my router from "low" to "medium" a few days ago...AND FORGOT! Yeesh. Sorry about that.
But OK...I read the Obitalk FAQ about which ports to have open...it's Greek to me (and I only know a little Greek)...could someone point me to a page that helps explain how to open ports?
I have a Motorola SBG-6782-AC if that helps at all, and here is a screenshot of my "port forwarding" page on the router:
https://photos.app.goo.gl/FCge1nVXMA7NbvhR9
Steve,
I'm having this same issue...except that my problem just cropped up in the last few days...early December 2018...is it possible that your explantion of the issues from May 2018 would just now be affecting me in December? Or would the problem most likely be something else?
Again, my problem is when I try to make an outbound call, I get the message:
The number you dialed...XXXXXXX...has not received a response from the service provider.
Also, the Obi200 falls offline very quickly...within minutes of bootup, and/or immediately after I try to make a call....which may or not be related.
Thanks...
Quote from: SteveInWA on May 05, 2018, 04:32:31 pm
Google has shut down its old "Google Chat/Talk" (XMPP) service, so OBiTALK devices will no longer work with that old method of connecting to Google Voice.
Polycom has pushed out updates to current model OBi devices to support the new Google Voiced platform. If you have done anything to disable OBiTALK provisioning or other attempts to block communications with the OBiTALK network, your device will fail.
3.2.2 (Build: 5898EX) is the current version, as of July 22nd, of the 200/202 firmware that supports Google Voice. Some units may have a newer firmware build number.
If you still see "Google Chat" on the "Legacy" settings page of Google Voice, then your device has not been properly provisioned using the new firmware. After the conversion, there is no longer a "Chat" entry. Instead, you'll see an "OBiTALK device" entry for each device you have authenticated to your Google account(s).
A few possible issues: it could be that you are looking at two different Google accounts, or you have blocked/disabled remote provisioning and didn't let the system take care of upgrading your device, or that you have made configuration modifications that are incompatible with the new platform, or that your device was partially upgraded, but it is now in some sort of limbo state.
Since there are multiple factors involved, and we do not have a symptom/fix knowledge base, I recommend completely clearing everything out and starting over.
Note: do not make any changes from the device's own, local web configuration page. Do everything from the OBiTALK portal.
Go to your OBiTALK dashboard, https://www.obitalk.com/obinet/pg/obhdev. Click the OBiTALK device you want to use. On the next page, click the blue "Delete Device" icon to remove it completely off of the dashboard. Wait a few minutes while it resets and removes the device, and the LEDs have stopped blinking (except for the middle LED flickering).Then, unplug the Ethernet and power cables from the device, leaving just the phone cable. Plug back in only the power cable, and wait for it to boot up.Pick up the phone and key in ***8 then 1 to confirm restore to factory defaults. Wait for it to go through the blinking lights thing for several minutes.On your browser, go here: https://myaccount.google.com/. In the "Apps with account access section", click the "MANAGE APPS" link, and then delete any telephony apps that have permission to use your account, including Simonics GVGW and/or Asterisk.Now, plug in the Ethernet cable and go to the OBiTALK dashboard, and click the button to add a device. Follow the instructions to press **5 xxxx to add your device.After the device is successfully added back, follow the instructions to add Google Voice again.When you get to the step where it will ask your permission to access your Google account, look closely at the gmail address it displays. This address must be the same one that displays your Google Voice phone number, here: https://voice.google.com/settings, and you must see "Google Voice number" at the top of the Google Voice settings page, with your inbound Google Voice number next to it. If you not see a Google Voice number, then you are either looking at the wrong Google account, or you don't have a number.
SteveInWA:
Your issue is unrelated to this discussion thread.
SailingMagnus:
I hopped on this thread back in May 2018 reporting the same problems when GV switched from XMPP to SIP. At that time I tried all the suggested steps and still could not get RTP to flow reliably and occasionally would get the number your trying to call has not registered with SP message. I switched my Wife's phone to Callcentric and she has had flawless service since. I stayed on my old GV number and left the country till September. When I was home in September I still had RTP problems so I reset the OBI202 and problem still there, tried moving my GV number to a new account and later back, problem still there. Here we are in 2019 and I have not seen any new firmware releases from Polycomm and it seems like this GV problem is still present for some, so I am wondering what are the latest recommendations to resolve? I don't have Google Chat settings in the legacy settings of GV configuration.
My current situation: Reboot my Cisco E4200 router and then I can make phone calls on my GV # on SP1 and RTP flows fine. In general I can make calls for about 10 minutes before RTP stops flowing. I have made a call last for an hour after a reboot, but then the very next call I make no audio. Something blocks RTP after about 10 minutes but yet calls can be made outbound with no audio and I receive calls inbound with no audio. Mean while my wife's Callcentric # on SP2 works fine. My OBI202 is configured to be in my router's DMZ so it's outside the firewall. My service provider has my cable modem in bridged mode so nothing should be blocked. SIP ALG is not enabled on my router.
I'd like to get my GV working consistently again any suggestions on how to proceed? Hate to buy another router (thinking that might be the problem) as this one has worked fine for GV XMPP for 2 years and Vonage for 8 years before that.
spinedoc777:
Quote from: SteveInWA on May 05, 2018, 04:32:31 pm
Google has shut down its old "Google Chat/Talk" (XMPP) service, so OBiTALK devices will no longer work with that old method of connecting to Google Voice.
Polycom has pushed out updates to current model OBi devices to support the new Google Voiced platform. If you have done anything to disable OBiTALK provisioning or other attempts to block communications with the OBiTALK network, your device will fail.
3.2.2 (Build: 5921EX) is the current version, as of December 22nd, of the 200/202 firmware that supports Google Voice. Some units may have a newer firmware build number.
If you still see "Google Chat" on the "Legacy" settings page of Google Voice, then your device has not been properly provisioned using the new firmware. After the conversion, there is no longer a "Chat" entry. Instead, you'll see an "OBiTALK device" entry for each device you have authenticated to your Google account(s).
A few possible issues: it could be that you are looking at two different Google accounts, or you have blocked/disabled remote provisioning and didn't let the system take care of upgrading your device, or that you have made configuration modifications that are incompatible with the new platform, or that your device was partially upgraded, but it is now in some sort of limbo state.
Since there are multiple factors involved, and we do not have a symptom/fix knowledge base, I recommend completely clearing everything out and starting over.
Note: do not make any changes from the device's own, local web configuration page. Do everything from the OBiTALK portal.
Go to your OBiTALK dashboard, https://www.obitalk.com/obinet/pg/obhdev. Click the OBiTALK device you want to use. On the next page, click the blue "Delete Device" icon to remove it completely off of the dashboard. Wait a few minutes while it resets and removes the device, and the LEDs have stopped blinking (except for the middle LED flickering).Then, unplug the Ethernet and power cables from the device, leaving just the phone cable. Plug back in only the power cable, and wait for it to boot up.Pick up the phone and key in ***8 then 1 to confirm restore to factory defaults. Wait for it to go through the blinking lights thing for several minutes.On your browser, go here: https://myaccount.google.com/. In the "Apps with account access section", click the "MANAGE APPS" link, and then delete any telephony apps that have permission to use your account, including Simonics GVGW and/or Asterisk.Now, plug in the Ethernet cable and go to the OBiTALK dashboard, and click the button to add a device. Follow the instructions to press **5 xxxx to add your device.After the device is successfully added back, follow the instructions to add Google Voice again.When you get to the step where it will ask your permission to access your Google account, look closely at the gmail address it displays. This address must be the same one that displays your Google Voice phone number, here: https://voice.google.com/settings, and you must see "Google Voice number" at the top of the Google Voice settings page, with your inbound Google Voice number next to it. If you not see a Google Voice number, then you are either looking at the wrong Google account, or you don't have a number.
Just wanted to say thank you, as I was pulling my hair out but this eventually worked. I was getting the backing off error and nothing worked. My 202 refused to update to the newest firmware, but this solution worked perfectly. Of course Obi customer service was useless, I wonder if they will see a class action lawsuit or some kind of fraud issues on how they are handling customer service. I paid the $10 but they never ever reply to my emails for tech support and I see others complain about not getting responses as well.
Anyway thanks again!!
Navigation
[0] Message Index
[#] Next page
[*] Previous page