The number you dialed___ has not received a response from the service provider
sweh:
There's definitely an issue somewhere in the OBi/GV world. For the past week or two calls would start to die after 20 minutes or so (a static burst then silence). Trying to re-dial after that causes these "not received a response" error. Maybe 3 or 4 minutes later the device will make calls again.
Incoming calls to GV routed to my OBi200 may also fail; I've had two go straight to voicemail and one caused my Obi to ring once then go to VM.
In in NJ on Verizon FIOS. My co-worker in Houston and my boss in Denver are also seeing issues with their OBI setups, so I know it's not just me.
njweb:
Quote from: wpsb on April 06, 2020, 07:52:02 am
Please also post your issue in the google voice help area. The more people who report it, the higher the likelyhood that someone will fix it
https://support.google.com/voice/thread/37682987?hl=en
Are we sure the issue is on Google's end and not something related to our OBI units? I.e. are other GV users who use OBI alternatives also suddenly all experiencing issues currently (past several weeks)?
drgeoff:
Quote from: njweb on April 08, 2020, 05:03:00 am
Quote from: wpsb on April 06, 2020, 07:52:02 am
Please also post your issue in the google voice help area. The more people who report it, the higher the likelyhood that someone will fix it
https://support.google.com/voice/thread/37682987?hl=en
Are we sure the issue is on Google's end and not something related to our OBI units? I.e. are other GV users who use OBI alternatives also suddenly all experiencing issues currently (past several weeks)?
The are no "OBi alternatives" that support GV.
Once an Obi is configured for GV, no server or network infrastructure operated by or on behalf of Obihai/Poly plays a necessary part in GV calls. The OBi communicates directly with Google for call setup and voice carriage.
As there has been no change to OBi devices since they were working satisfactorily with GV one must assume:
1. Google now has some faulty equipment or has knowingly or unknowingly made some change which adversely impacts OBi devices.
2. If Google has knowingly made some change they have not advised Obihai of what change need to be made to OBi devices or if they have advised then Obihai has not released updated firmware for OBi devices.
andyhi:
Quote from: wpsb on April 06, 2020, 07:52:02 am
Please also post your issue in the google voice help area. The more people who report it, the higher the likelyhood that someone will fix it
https://support.google.com/voice/thread/37682987?hl=en
Google Voice support replied on that thread stating they found and corrected an issue on their end and then asked for feedback if the issue reoccurred. The problem reoccurred (outgoing call dropped at ~15:32) the next morning so I replied.
Now the GV thread has been deleted.
Agree that everything indicates an issue with Google at this point. Really looks like they are dropping communications from some Obi clients after a timeout period... Perhaps due to changes on Googles end with network comms/LB/firewall/IPS/session timeouts.
The only other thing I can come up with is that perhaps the comms from the Obi202 is slightly different from the Obi200 given the 202 has a firewall/router built in. I do have my 202 configured in bridge mode with firewall (NAT) disabled best I can tell. Moved one of my lines back to an Obi200. Haven't noticed the issue on the 200, but haven't had enough time/usage on that line to say for certain if there is a difference between the 200 and 202 at this point.
Update - Noticed my Obi200 f/w:3.2.2 (Build: 5898EX) Obi202 f/w:3.2.2 (Build: 5921EX).
Also the last page in the following thread suggests an issue with firmware 5921EX. (Downgrading the 202 to 5859EX now. If I had a link to 5898 I would try that instead.)
http://www.obitalk.com/forum/index.php?topic=9983.360
SteveInWA:
Quote from: andyhi on April 16, 2020, 12:56:59 pm
Quote from: wpsb on April 06, 2020, 07:52:02 am
Please also post your issue in the google voice help area. The more people who report it, the higher the likelyhood that someone will fix it
https://support.google.com/voice/thread/37682987?hl=en
Google Voice support replied on that thread stating they found and corrected an issue on their end and then asked for feedback if the issue reoccurred. The problem reoccurred (outgoing call dropped at ~15:32) the next morning so I replied.
Now the GV thread has been deleted.
Agree that everything indicates an issue with Google at this point. Really looks like they are dropping communications from some Obi clients after a timeout period... Perhaps due to changes on Googles end with network comms/LB/firewall/IPS/session timeouts.
The only other thing I can come up with is that perhaps the comms from the Obi202 is slightly different from the Obi200 given the 202 has a firewall/router built in. I do have my 202 configured in bridge mode with firewall (NAT) disabled best I can tell. Moved one of my lines back to an Obi200. Haven't noticed the issue on the 200, but haven't had enough time/usage on that line to say for certain if there is a difference between the 200 and 202 at this point.
Update - Noticed my Obi200 f/w:3.2.2 (Build: 5898EX) Obi202 f/w:3.2.2 (Build: 5921EX).
Also the last page in the following thread suggests an issue with firmware 5921EX. (Downgrading the 202 to 5859EX now. If I had a link to 5898 I would try that instead.)
http://www.obitalk.com/forum/index.php?topic=9983.360
This a steaming pile of BS, based solely on anecdotal reports and speculation.
The 15-minute disconnect issue was an actual bug, that was identified and fixed. The thread was locked for that reason, since future posts would be unrelated to the resolved problem.
Experimenting with downlevel firmware isn't going to fix anything. Your speculations about the differences between the 200 and 202 demonstrate your lack of understanding. They use the exact same firmware, and, other than the router portion, which you can easily bypass, it's the same product.
If you truly have a consistent, reproducible symptom/failure that can be demonstrated and documented with test phone calls, then open your own, dedicated discussion post on the Google Voice forum (not here).
https://support.google.com/voice/thread/new?hl=en
I have the ability to work directly with Google Voice engineering to investigate reproducible problems. Otherwise, stop randomly guessing and spreading nonsense.
Navigation
[0] Message Index
[#] Next page
[*] Previous page