Any insight on why I'm hearing this the last few days? Rebooting my 200 using ***9 fixes it temporarily but it reverted back today.
Quote from: Revived on January 17, 2019, 08:49:38 AM
Any insight on why I'm hearing this the last few days? Rebooting my 200 using ***9 fixes it temporarily but it reverted back today.
WOW I thought it was just me!! Sometimes a soft reboot fixes it for me, other times I have to pull the power plug, count to 10, and put it back in. I can make 2 calls in a row, no problem, hang up and try making another call and I get same no response error.
Mine started earlier this week, but seems real bad today.
Hopefully, someone here has some insight. If you find a fix, please post here.
Thank you
Joe Sica
I have the same problem. Is this a know problem? Is there a solution?
-Mark
Not one of the three posters thought to name the Service Provider.
Quote from: drgeoff on January 17, 2019, 01:39:56 PM
Not one of the three posters thought to name the Service Provider.
Good point, the ever lovin` Google Voice...
Joe Sica
I have the same problem multiple times over the last month. I'm using GVoice. Rebooting so far has fixed the problem.
Quote from: drgeoff on January 17, 2019, 01:39:56 PM
Not one of the three posters thought to name the Service Provider.
Apologies. I'm using Google Voice and my internet provider is Cox Cable.
I am getting this as well... Gvoice on an Obi 200.
I am getting this as well... Gvoice on an Obi 200 via comcast
Try this (http://www.obitalk.com/forum/index.php?topic=15462.msg97389#msg97389)
Quote from: bitstopjoe on January 17, 2019, 11:21:28 AM
Quote from: Revived on January 17, 2019, 08:49:38 AM
Any insight on why I'm hearing this the last few days? Rebooting my 200 using ***9 fixes it temporarily but it reverted back today.
WOW I thought it was just me!! Sometimes a soft reboot fixes it for me, other times I have to pull the power plug, count to 10, and put it back in. I can make 2 calls in a row, no problem, hang up and try making another call and I get same no response error.
Mine started earlier this week, but seems real bad today.
Hopefully, someone here has some insight. If you find a fix, please post here.
Thank you
Joe Sica
I'm seeing the EXACT same problem. For what it's worth, I tried changing the DNS to 8.8.8.8 and 8.8.4.4 as another person had suggested, but that didn't help.
me too google voice with optimum online internet
This has happened to me a couple times in the past two weeks at only one of three sites (SITE 1 below). The same GV number is set up to ring at all three sites. All three sites use an Obi202. All three sites are with Comcast as the service provider. They use different cable modems/gateways or routers so perhaps that is where the difference lies. Site 1 has the oldest equipment:
1 Obi202, Comcast, Comcast Gateway (Netgear CG3000DCR) & router Cisco RV 180W
2 Obi202, Comcast, Comcast Wireless Gateway (Cisco DPC3941B)
3 Obi202, Comcast, Cable Modem (ARRIS SURFoard SB8200)
I will try changing the DNS to 8.8.8.8 and 8.8.4.4 as suggested by Zorlac above.
I am trying the following:
changing the DNS to 8.8.8.8 / 8.8.4.4
put the Obi on the DMZ
Obi support suggested: Please try opening certain ports within your router for traffic flowing: https://www.obitalk.com/info/faq/Troubleshooting-sec/ports-to-keep-open-on-my-router
Having the same issue for the past week or 2. Using Obi200 with Google Voice. Restarting the device helps temporarily, but the problem occurs. Any help? Has changing port fix it? Exact instructions on how to do it?
Thanks!
Quote from: madhatter on January 23, 2019, 10:07:44 PM
Obi support suggested: Please try opening certain ports within your router for traffic flowing: https://www.obitalk.com/info/faq/Troubleshooting-sec/ports-to-keep-open-on-my-router
That is another fine example of the competence level of OBi support. :(
See what I wrote at http://www.obitalk.com/forum/index.php?topic=15537.msg97386#msg97386
I am having the same problem with Google Voice on one of two separate OBi 202's.
Each box also has Anveo for E911 which continues to function perfectly on both.
Additionally, one of the boxes has Dialpad and it functions fine.
The box that works with Google Voice has firmware 3.2.2 (Build: 5898EX)
The box that DOESN'T work with Google Voice has firmware 3.2.2 (Build: 5921EX).
Both were previously on 1.1.1.1 for DNS through my Pi-Hole but I forced both to Google DNS which didn't help.
I am going to try to downgrade the firmware of the recalcitrant unit and see what happens.
Same issues here when I try to reconnect. I start out making a call and then its drops randomly after a few minutes.
200
HardwareVersion 1.4 help
SoftwareVersion 3.2.2 (Build: 5898EX)
Has anyone found a fix? Since I posted, this issue has been intermittent. Today, however, it happens after every successful outgoing call. The ***9 reboot helps for one call and that's it.
I did a remove and reset and added the device back in. Not sure that helped but i have the later firmware now 5921EX. The issue I still have is my calls are drop after several minutes. One thing I noticed is when dialing a number the ringing i hear sounds like it in slow motion, which I do not care unless its related to my calls dropping, any one have an idea on the drop calls.
Thank You
This is still happening to me.
Rebooting my 200 using ***9 fixes it temporarily.
Sometimes I can use the phone for days without issues. Other days it works for a few hours and then this issue comes back. This week I am having issues everyday for several hours.
If I do nothing on my end the issue comes and goes. If I can't make a call now... waiting and calling later in the day often works... without making any changes as my end.
My xfinity internet connection is trouble free and working consistently without drops. I've also used different DNS settings with no change in performance / reliability... including 8.8.8.8, 8.8.4.4, 1.1.1.1 etc. Tested in the DMZ with no change.
obi 200 3.2.2 (Build: 5921EX) w/ google voice
If anyone finds a fix that works, please share.
I'm guessing a firmware bug, device flaw or did someone at Polycom forget to feed the hamster that routes calls? ???
I am also having the issue that when I make a call and the person receiving the call picks up.. all I hear is white noise and they can't hear me. This happens when making calls to multiple phone systems xfinity, verizon and others... not just one. If I make no changes at my end and call the number over and over, eventually it connects without the white noise upon the answer.. If I get tired of dialing with the obi and switch to using my cell the call from through verizon works fine. So the issue is with the obi200/google voice/Polycom and not the person being called.
Codec issue? firmware issue? Routing issues?
With the above two issues... I am lucky if I can make an outgoing call 50% of the time. Incoming calls are not an issue.
Thanks in advance for any fixes.
CPC
For what it's worth, I've not experienced this issue in the last several days.
Quote from: CPC_obi on February 13, 2019, 10:15:48 AM.. did someone at Polycom forget to feed the hamster that routes calls?
Once your OBi is configured with GV and/or your ITSP(s), OBi/Polycom plays no further part in the routeing or transmission of all calls via GoogleVoice or other ITSPs. Neither call setup signalling nor call audio packets go anywhere near any servers run by, or on behalf of, Obihai/Polycom. (Only calls to other Obi devices, using the 9 digit OBi numbers depend on Obihai/Polycom services.)
Thanks DrGeoff ... I'm glad to hear the hamster is fine. ;D (Thank you for the info re: routing)
I had the obi 100 for years without an issue. I have had two of the OBI 200 in the past year and both have been problematic.
Is it defective devices, bad firmware or a google voice issue? Has anyone who had this issue solved it long term? I can sometimes go days or weeks with no issues ..thinking it's solved.. Then it comes back. This week has been terrible again when trying to make outgoing calls.
I've tried all of the items posted on this subject so far with no luck. Restarting the obi 200 helps sometimes for a few calls.
Thanks in advance for any solutions... ???
CPC
I have had the same problem probably from almost day one (2 years ago) since I had this service, that message and another similar, but NOT with GoogleVoice. My pay provider is Phone Power ($60/yr).
It usually happens in the morning after a long period on non-use (our phone isn't used that much). No specific number, not even long distance. I'll disconnect, then re-dial and all is fine. No re-boot or anything.
My guess is the system needs a 'wake-up' or jolt to get a working connection (path) active again. The 1st call fails, following calls are all fine.
This issue is happening again very often the last few days. Any idea to help that?
I'm using GV with a Obi200 and CallCentric for incoming calls for the past 2 years.
Recently I'm having again the issue that I can't place any outgoing calls. I have a dial tone, and when I dial a number I'm getting a message "The number you've dialed XXX-XXX-XXXX didn't receive a response from the service provider.....". I can't place any call until I restart my Obi device. Restarting helps it temporarily.
Incoming calls works fine.
Who is your service provider? Contact them.
Quote from: ansh on March 30, 2020, 02:39:49 PM
This issue is happening again very often the last few days. Any idea to help that?
I'm using GV with a Obi200 and CallCentric for incoming calls for the past 2 years.
Recently I'm having again the issue that I can't place any outgoing calls. I have a dial tone, and when I dial a number I'm getting a message "The number you've dialed XXX-XXX-XXXX didn't receive a response from the service provider.....". I can't place any call until I restart my Obi device. Restarting helps it temporarily.
Incoming calls works fine.
It was a GV problem and a Google engineer has posted elsewhere that he has fixed it.
Quote from: drgeoff on March 31, 2020, 08:29:35 AM
Quote from: ansh on March 30, 2020, 02:39:49 PM
This issue is happening again very often the last few days. Any idea to help that?
I'm using GV with a Obi200 and CallCentric for incoming calls for the past 2 years.
Recently I'm having again the issue that I can't place any outgoing calls. I have a dial tone, and when I dial a number I'm getting a message "The number you've dialed XXX-XXX-XXXX didn't receive a response from the service provider.....". I can't place any call until I restart my Obi device. Restarting helps it temporarily.
Incoming calls works fine.
It was a GV problem and a Google engineer has posted elsewhere that he has fixed it.
I still have the exact same problem, so maybe not?
As I stated, it is NOT a GV issue! I do NOT have the reboot either.
Quote from: videobruce on March 31, 2020, 08:54:50 AM
As I stated, it is NOT a GV issue! I do NOT have the reboot either.
I replied to ansh, not you.
Since there was no quote used, the post referred to the thread in general.
A little 'testy' aren't we?? ::)
Quote from: drgeoff on March 31, 2020, 08:29:35 AM
Quote from: ansh on March 30, 2020, 02:39:49 PM
This issue is happening again very often the last few days. Any idea to help that?
I'm using GV with a Obi200 and CallCentric for incoming calls for the past 2 years.
Recently I'm having again the issue that I can't place any outgoing calls. I have a dial tone, and when I dial a number I'm getting a message "The number you've dialed XXX-XXX-XXXX didn't receive a response from the service provider.....". I can't place any call until I restart my Obi device. Restarting helps it temporarily.
Incoming calls works fine.
It was a GV problem and a Google engineer has posted elsewhere that he has fixed it.
Thanks for your reply! Was it posted recently as fixed? I just had this again moments ago..
Quote from: videobruce on March 31, 2020, 09:46:29 AM
Since there was no quote used, the post referred to the thread in general.
A little 'testy' aren't we?? ::)
I think your degree of blindness vastly exceeds my testiness.
Count me too. GV provider. Experiencing this issue from couple of days, dropped just now few minutes ago. Any solution? Reboot fixes it temporarily. Happened to me at least 3 times today, every time I had to reboot.
On top of all the other problems mentioned in this thread, all my calls drop at around 15 minutes and 40 seconds.
Similar issues over the last couple of days. OBi202 configured with two GV numbers.
I've been on 3+ hr conference calls with no issues. Other times I'll be a few minutes into a new call, hear a second or so of static, and then silence. At that point I have to hang up and re-dial, but always receive the "The number you dialed xxx-xxx-xxxx has not received a response from the service provider" on both lines until I power cycle/reset the Obi. (Correction - Sometimes powercycle is not required if I wait long enough.) This has happened several times in the last hour.
Network - Gigabit up/down ATT fiber internet connection with robust pFsense firewall/router. Wife and I work from home and have always on VPN connections back to different work networks in different states.... no issues with VPN slowness, no vpn re-connections, no internet packet loss. pFsense logs and traffic graphs show no degradation of service/bandwidth to ISP and no packet loss to upstream ISP gateway. Speed tests show solid and consistent 900+Mbps up/down. Issue isn't my home network or internet connection.
Quote from: andyhi on April 01, 2020, 01:39:28 PM
... with robust pFsense firewall/router...
That's likely your problem. Do not block any [*.]google.com cookies. Do not block HTML5. Do not block WebRTC. Do not block javascript. Do not run any browser extensions that perform any of those things. Do not block the outbound ports used by Google Voice. See: https://support.google.com/a/answer/9206518?hl=en (https://support.google.com/a/answer/9206518?hl=en)
No firewall rules changes on my end in over 6 months. Will turn up additional logging and packet captures if need be.
Quote from: andyhi on April 01, 2020, 02:37:41 PM
No firewall rules changes on my end in over 6 months. Will turn up additional logging and packet captures if need be.
So what? You could have had the wrong settings for over 6 months. Check to be sure that you are not blocking ANY of the items I mentioned, and you are opening the referenced ports.
I really don't care, at this point, how many other anecdotal reports you find. People have reported mysterious disconnects for years, and there are no currently-known issues on Google's side that would cause it. Aside from a few bugs that were found and fixed, these always turn out to be client-side issues.
I am having the same issue. Just started a few days ago. No changes to my network. I'll be on a call and it will get disconnected mid call. Then I cannot make another outbound call until I reboot the phone. I'm using GV.
Quote from: SteveInWA on April 01, 2020, 02:47:08 PM
Quote from: andyhi on April 01, 2020, 02:37:41 PM
No firewall rules changes on my end in over 6 months. Will turn up additional logging and packet captures if need be.
So what? You could have had the wrong settings for over 6 months. Check to be sure that you are not blocking ANY of the items I mentioned, and you are opening the referenced ports.
I really don't care, at this point, how many other anecdotal reports you find. People have reported mysterious disconnects for years, and there are no currently-known issues on Google's side that would cause it. Aside from a few bugs that were found and fixed, these always turn out to be client-side issues.
Multiple people at different locations are reporting the exact same issues and you blame the guy's firewall saying everything is fine on Google's side? Clearly not. Something is very wrong either on Google's side or on Obi's side.
Quote from: Italian on April 02, 2020, 08:38:59 AM
Quote from: SteveInWA on April 01, 2020, 02:47:08 PM
Quote from: andyhi on April 01, 2020, 02:37:41 PM
No firewall rules changes on my end in over 6 months. Will turn up additional logging and packet captures if need be.
So what? You could have had the wrong settings for over 6 months. Check to be sure that you are not blocking ANY of the items I mentioned, and you are opening the referenced ports.
I really don't care, at this point, how many other anecdotal reports you find. People have reported mysterious disconnects for years, and there are no currently-known issues on Google's side that would cause it. Aside from a few bugs that were found and fixed, these always turn out to be client-side issues.
Multiple people at different locations are reporting the exact same issues and you blame the guy's firewall saying everything is fine on Google's side? Clearly not. Something is very wrong either on Google's side or on Obi's side.
Once an OBi is configured the only calls which use OBihai resources are those to and from other OBi devices over the Obitalk network - the calls that are dialled using the **9 prefix. For all other calls to and from ordinary landline and cellphone numbers no signalling or voice trafffic goes anywhere near servers or network links run by or on behalf of Obihai/Polycom etc.
Quote from: drgeoff on April 02, 2020, 09:32:37 AM
Quote from: Italian on April 02, 2020, 08:38:59 AM
Multiple people at different locations are reporting the exact same issues and you blame the guy's firewall saying everything is fine on Google's side? Clearly not. Something is very wrong either on Google's side or on Obi's side.
Once an OBi is configured the only calls which use OBihai resources are those to and from other OBi devices over the Obitalk network - the calls that are dialled using the **9 prefix. For all other calls to and from ordinary landline and cellphone numbers no signalling or voice trafffic goes anywhere near servers or network links run by or on behalf of Obihai/Polycom etc.
Agreed. So something is wrong on Google Voice's end that's causing all these problems.
Quote from: SteveInWA on April 01, 2020, 02:47:08 PM
Quote from: andyhi on April 01, 2020, 02:37:41 PM
No firewall rules changes on my end in over 6 months. Will turn up additional logging and packet captures if need be.
So what? You could have had the wrong settings for over 6 months. Check to be sure that you are not blocking ANY of the items I mentioned, and you are opening the referenced ports.
I really don't care, at this point, how many other anecdotal reports you find. People have reported mysterious disconnects for years, and there are no currently-known issues on Google's side that would cause it. Aside from a few bugs that were found and fixed, these always turn out to be client-side issues.
Well I really don't care what you think or say as you clearly have no clue how network connectivity or firewalls work. If there have been no issues or changes on my end for over 6 months and I start experiencing issues with GV at the same point in time that many others are reporting the exact same issues, clearly my firewall rules are NOT the problem.
Quote from: andyhi on April 02, 2020, 09:22:21 PM
Quote from: SteveInWA on April 01, 2020, 02:47:08 PM
Quote from: andyhi on April 01, 2020, 02:37:41 PM
No firewall rules changes on my end in over 6 months. Will turn up additional logging and packet captures if need be.
So what? You could have had the wrong settings for over 6 months. Check to be sure that you are not blocking ANY of the items I mentioned, and you are opening the referenced ports.
I really don't care, at this point, how many other anecdotal reports you find. People have reported mysterious disconnects for years, and there are no currently-known issues on Google's side that would cause it. Aside from a few bugs that were found and fixed, these always turn out to be client-side issues.
Well I really don't care what you think or say as you clearly have no clue how network connectivity or firewalls work. If there have been no issues or changes on my end for over 6 months and I start experiencing issues with GV at the same point in time that many others are reporting the exact same issues, clearly my firewall rules are NOT the problem.
Well said! I agree 100%!
Same here just started about 3 days ago. Very frustrating. Reboot fixes the situation for a short while. Nothing changed on network/router. Even the incoming calls are going to the cell phones only, obi200 is silent.
Quote from: chrisgabor on April 03, 2020, 12:26:31 PM
Same here just started about 3 days ago. Very frustrating. Reboot fixes the situation for a short while. Nothing changed on network/router. Even the incoming calls are going to the cell phones only, obi200 is silent.
Mine also started 3-4 days ago. I posted a link in another thread with a link to a complaint to google. The more people who reply they are having a problem the more likely they are to fix. I have also escalated to an engineer at Poly since the "moderators" on this board are clueless and not helpful, as usual.
Quote from: wpsb on April 03, 2020, 12:49:42 PM
Mine also started 3-4 days ago. I posted a link in another thread with a link to a complaint to google. The more people who reply they are having a problem the more likely they are to fix. I have also escalated to an engineer at Poly since the "moderators" on this board are clueless and not helpful, as usual.
Yes, no help from the "moderators." Please keep us posted if you hear back from Poly.
Started yesterday at my home in NYC, and happened twice today on each of two Obis (which carry two GV numbers).
Rebooted both twice.
My internet connection is good - 1Gbps Verizon FIOS with low pings to nearby speedtest.net servers. The two Obis are wired to the router, not wifi. Everything else internet seems fine.
So what's causing this?
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.
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)?
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.
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
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 (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.
Quote from: SteveInWA on April 16, 2020, 07:02:08 PM
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.
Great work... I've had the 15 minute problem multiple times on my obi202 since Google "identified and fixed" the issue. And the thread I mentioned (from WSPB's post) is now entirely gone... not locked, not closed, gone after they asked for additional feedback.
https://support.google.com/voice/thread/37682987?hl=en
Quote from: SteveInWA on April 16, 2020, 07:02:08 PM
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.
I know it's the same firmware image, but the hardware is different. This can absolutely create differences in network connectivity if the stateful firewall or secondary NAT components of the 202 are still inline with comms. AT&T does this with certain configs of their FTTH RGs and it causes issues with wifi calling and other types of connectivity due to double NAT even through you are leveraging a WAN network issued IP on the calling device.
Quote from: SteveInWA on April 16, 2020, 07:02:08 PM
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 (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.
Noted... Your customer support skills are top notch!
I was having the same issue yesterday, but I was too busy with work to troubleshoot. I have two GV lines on my Obi and have never had issues before. One is the main house line and the other is the number I use so folks at work can reach me. I've had these numbers for years. ;D When the issue cropped up yesterday, I rebooted the Obi and it fixed the issue, but then cropped up on the other GV line afterwards. I don't have any special equipment other than my Dd-wrt router and nothing has been changed there. If it happens again, I'll try to troubleshoot further and also try to get a TCP dump from the router and look for anything that stands out to see if that helps any.
andyhi and Smee
I have been in touch with Poly about this issue. They are aware of it. They are also aware of SteveInWA and how he responds to people. I have confirmed that He does NOT even work for Poly!!!
Poly's engineers are looking into the problem. However, I suggest that you open a new thread with Google, as well, even though they locked mine.
You SHOULD email Poly's tech support. They made some changes there and now should be more responsive to issues. Let me know how it goes!
Thank you, however, as of today, I haven't experienced the issue. If it does happen again and I'm able to do a packet capture, I'll open up a ticket. Having the time/date, checking the Obi dashboard and the device itself would probably help as well. I'll have to check and see if anything useful is also being sent to the syslog server.
Quote from: wpsb on April 21, 2020, 01:24:45 PM
andyhi and Smee
I have been in touch with Poly about this issue. They are aware of it. They are also aware of SteveInWA and how he responds to people. I have confirmed that He does NOT even work for Poly!!!
Poly's engineers are looking into the problem. However, I suggest that you open a new thread with Google, as well, even though they locked mine.
You SHOULD email Poly's tech support. They made some changes there and now should be more responsive to issues. Let me know how it goes!
WPSB - any update? This is happening non-stop in my wife's SOHO, but not at home for some months now. NYC. Office is 100Mbps through the mini-office company, and home is Verizon FIOS 400Mbps.
Still happening most of the time.
Also, if I dial **9 222 222 222 for the echo test, that also is not connecting some of the time. So is this a Google Voice problem or something else?
This is an Obihai 200 with firmware 3.2.2 (Build: 5898EX).
Is it possible my wife's mini-office landlord is sometimes blocking the VOIP protocol used by the OPbihai? They say no, but why is this happening?
Quote from: glnz2 on June 24, 2020, 08:33:34 PM
Still happening most of the time.
Also, if I dial **9 222 222 222 for the echo test, that also is not connecting some of the time. So is this a Google Voice problem or something else?
This is an Obihai 200 with firmware 3.2.2 (Build: 5898EX).
Is it possible my wife's mini-office landlord is sometimes blocking the VOIP protocol used by the OPbihai? They say no, but why is this happening?
The echo test has nothing to do with GV. If the echo test is not connecting some of the time then that is not caused by any misconfiguration of GV on the OBi device or any problem with the GV account or any fault in GV infrastructure.
Suggest that your wife temporarily brings the OBi, its PSU, ethernet cable and the phone home eg over a weekend and try it there. If the OBi gets its network parameters by DHCP then it only needs plugging in and powering up - no reconfiguration needed.
If it behaves perfectly at home then there is something amiss with how it reaches the internet when at her office. That could be the local network there or the connection to the ISP or an ISP issue.
Dr. Geoff - Thanks. I was thinking exactly the same thing - bring it home and see. (And vice versa!!)
Now, if it works perfectly at home, that probably means my wife's mini-office landlord is doing something to limit the traffic even though our original deal from almost seven years ago was that the rent would include internet, and I was very upfront about that including our own VOIP phone.
But now I need your more advanced advice.
Originally, in the mini-office, we plugged the landlord's ethernet wall socket into a small router - to the router's WAN socket. We then ran everything off the router's LAN sockets or WiFi. So, originally, our small VOIP box was "behind" the router (always wired to one of the router's LAN sockets).
We got our ObiHai 200 and our Google Voice about three years ago. Worked well. Then about a year later (two years ago), Google Voice dropped its original protocol, the ObiHai stopped working although it was supposed to continue working, and I came to the conclusion that our oldish router could not handle Google Voice's new protocol. (That router is an old Westell DSL modem-router that Verizon gave me a long time ago and that I converted to "routed bridge" to use in my wife's mini-office. It still works except for the ObiHai 200.)
So I bought a TP-Link TL-SG105 unmanaged 5-port switch, and now the ObiHai 200 is directly on the landlord's ethernet network and no longer behind our old router. In other words, that TP-Link TL-SG105 unmanaged 5-port switch is connected to three things: the landlord's ethernet socket, the old router's WAN socket and the ObiHai 200. So the ObiHai 200 is no longer going through our router.
Maybe the landlord can now "see" the Obihai 200 as a separate device and is limiting its connection to the internet ???
QUESTION: What replacement router should I get so that, again, I can put the ObiHai 200 "behind" the router, the new router will be able to handle the ObiHai-Google Voice protocol well, and maybe the landlord will stop interfering? (Maybe the landlord will again see only one device??) Such a replacement router should also generate its own WiFi network for our iPhones and iPads when we're in that office.
FYI - the landlord's network bandwidth to us is only 100Mbps, but that's fine for our purposes.
Or could it be that the ethernet cable between my ObiHai 200 and the TP-Link switch is bad and intermittent ???
Thanks for your thoughts. ☺
Went to my wife's SOHO, disconnected the Obihai 200 and brought it home.
So far, it is working with almost no issues. There were two test calls that didn't complete, but the next call completred, and many test calls have now completed. In her SOHO, once the phone stops connecting through, it stays bad for a while. Not so here at home.
So - what do you think the mini-office IT team is doing to us? Is it detecting the nature of the internet connection and clamping down?
Well, give it another day or two of aggressive testing. If it passes that test, then yes, this nails it down as a network problem.
The office IT people aren't deliberately blocking nor throttling anything. It's an issue with the various tenants' usage patterns and load on the one ISP circuit serving the whole location. I seriously doubt they have the sophistication to run a managed network, so it is probably just every tenant on the same LAN (or subnet of that LAN). You cannot get that sort of shared Internet service to reliably support VoIP.
To put it bluntly, the options are:
- Get your own ISP service run into your own office, which sounds unlikely.
- Go back to telephone company POTS service.
- Get the landlord to upgrade their ISP service.
- Move.
SteveinWa - Gave it the extra days of testing at home with great results and then brought it back to my wife's SoHo, where the problem continues.
That min-office company is now mostly empty due to the coronavirus. The load on its network is now only a fraction of what it was before. It's got to be some setting.
Here are two clues:
When I reboot the Obihai200, I can make one call out. (Or one in.) The next call is blocked.
Not only is GoogleVoice blocked, so is Obihai's own internal universe of phone numbers, like the echo test **9 222 222 222.
Is it possible that the mini-office company's router has the same SIP ALG problem that we all had when GV changed protocols two years ago?
Any other thoughts?
Thanks.
I have no idea why it doesn't work, and I don't see how anyone can diagnose it remotely, without a packet sniffer.
I can tell you that the SIP ALG setting is irrelevant when using Google Voice.
Why not take a laptop into that office, sign into the Gmail account that holds your Google Voice phone number, then go here: https://voice.google.com/u/0/calls (https://voice.google.com/u/0/calls)
Make 5 or so calls. They should all work. Warning, do not make a crap-ton of short calls in a short time period, or your Google Voice service will be suspended.
If that works, then there is some unknown issue between your OBiTALK device and their network (and not between your OBiTALK and Google Voice in general, since it worked at home). You will probably have to give up.
Steve - thanks for your encouragement!
I have a ways to go on this -- including bringing a microphone to the mini-office to plug into the existing PC to try GV the way you suggest -- but first - is there any way to put Skype into the Obihai 200 as a VOIP service? That was actually our original service and we had a Freetalk ConnectMe VOIP box for it. Then three (?) years ago, Skype stopped being available that way.
Is there any way to bring Skype back the way I'm trying to use GV?
EDIT - ADDED DETAIL -- In the Obhai Expert settings, in ITSP Service Profile A - General, the STUNServer is http://stun.l.google.com/.
If I put that URL into a browser, I get "This site can't be reached stun.l.google.com took too long to respond."
Clue?
Quote from: glnz2 on July 03, 2020, 09:56:37 AM
Steve - thanks for your encouragement!
I have a ways to go on this -- including bringing a microphone to the mini-office to plug into the existing PC to try GV the way you suggest -- but first - is there any way to put Skype into the Obihai 200 as a VOIP service? That was actually our original service and we had a Freetalk ConnectMe VOIP box for it. Then three (?) years ago, Skype stopped being available that way.
Is there any way to bring Skype back the way I'm trying to use GV?
EDIT - ADDED DETAIL -- In the Obhai Expert settings, in ITSP Service Profile A - General, the STUNServer is http://stun.l.google.com/.
If I put that URL into a browser, I get "This site can't be reached stun.l.google.com took too long to respond."
Clue?
1. No, you cannot run Skype on any OBi.
2. That stun URL gives the same "This site can't .... long to respond" for me. It is a red herring. Getting to the obitalk echo test does not depend on that stun server and you wrote that the echo test is problematic too.
SteveInWA and drgeoff - Last night (Sunday night) in the mini-office and today (Monday) monitoring my Obihai 200 remotely while making test calls, the GV line has been working. Same for the special **9 Obihai number.
It's possible the mini-office IT team did something, but maybe they didn't do anything,
Have you heard whether maybe Google was checking and fixing issues?
Of course, I don't know if this will last.
EDIT - ADDITIONAL INFO - During the past ten days or so trying to fix this issue, I re-connected the Obihai 200 to our GV account a few times, including once by mistake to SP2 in addition to SP1. I then deleted the SP2 connection, leaving the SP1. I also went directly into our GV account and made sure it was showing the Obihai 200 in "My Devices". Well, checking our GV account again right now, I see that our Obihai is listed TWICE in GV "My Devices". Since it all seems to be working, I'm going to leave that alone.
Thanks.
1. There was no issue that Google fixed. The account and the OBi worked fine at your home. Nothing GV does can affect **9 calls.
2. Yes you will now see the OBi listed twice by GV. GV does not distinguish between two OBi devices each with the same GV number on one SP and one OBi with the same GV number on two of its SPs. As you have only deleted an OBi SP config, the effect is the same as two OBis which have previously been connected but one is now unpowered or disconnected from the internet. Both will continue to appear unless/until you explicitly take the removal steps.
Don't want to jinx myself, but it's still working. Even obitalk is much more responsive.
I wonder what did it.
Well, it's still working -- almost a week now.
To anyone else who has this problem but only if it doesn't clear up any other way, you might try this: Add the very same Google Voice account to SP2 so it's on your Obihai twice (both SP1 and SP2). Go to Google Voice itself and check that your Obihai is listed twice as a connected device. Then go back to your Obihai and delete the SP2 setup. Then go back to GV to check that it still shows your Obihai twice. Then cross your fingers.
Please report back here.
Quote from: glnz2 on July 10, 2020, 07:24:59 AM
Well, it's still working -- almost a week now.
To anyone else who has this problem but only if it doesn't clear up any other way, you might try this: Add the very same Google Voice account to SP2 so it's on your Obihai twice (both SP1 and SP2). Go to Google Voice itself and check that your Obihai is listed twice as a connected device. Then go back to your Obihai and delete the SP2 setup. Then go back to GV to check that it still shows your Obihai twice. Then cross your fingers.
Please report back here.
How many times do I need to write this? You had a network problem as evidenced by the fact that both the GV account and the Obitalk network (**9) were affected. Adding/deleting GV accounts does not fix a network problem.
Dr. G - You may well be right, but the mini-office company insists they never blocked or unblocked my VOIP-internet connection.
Maybe they're lying. Is there a way for a network admin to block only GV and Obihai connections and not other internet connections (like browsing and email)?
They are not blocking any of that.
Steve and Dr G - you are the top experts here, but you might be disagreeing with each other?
So what caused the problem, which lasted for months, and what fixed the problem?
Reminder that a few weeks ago the Obihai 200 worked fine when I brought it home but then had the same problem when I brought it back to the mini-office -- until this past Sunday when suddenly the problem was gone.
Wha' happen, mans?
Thanks.
Quote from: glnz2 on July 10, 2020, 12:46:37 PM
Steve and Dr G - you are the top experts here, but you might be disagreeing with each other?
So what caused the problem, which lasted for months, and what fixed the problem?
Reminder that a few weeks ago the Obihai 200 worked fine when I brought it home but then had the same problem when I brought it back to the mini-office -- until this past Sunday when suddenly the problem was gone.
Wha' happen, mans?
Thanks.
I'm sure SteveInWA will agree that he and I are not disagreeing with each other.
i don't and can't know what the problem was. I can be certain what it was not.