December 08, 2019, 05:06:24 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Google Voice Disconnects at 10, 30, 60 minutes  (Read 4678 times)
CLTGreg
Full Member
***
Posts: 112


« on: September 30, 2014, 06:10:54 pm »

I have seen threads before about hangups at exactly 60 minutes with an OBi. I have experienced this with a 202 and lately have been stung at 30 minutes. Today for the first time I was cut off at 10 minutes.

I have always blamed the providers for this but today I was looking at the phone when cut off at 10 minutes. It is a two line corded phone.

Usually the light for a call in progress is red when in use and the other line will be green. When the disconnected happened both lines went red which is usually how it looks when receiving an update through OBitalk. This tells me that something freaked out the 202. This was on an incoming call.

When I tried to call back the party I got an authentication error for GV. It told me if I changed my password to log in to OBitalk to update it. A few minutes later it worked again.

I hope the unit isn't bad because it is out of warranty. 90% of the time it works fine. Please help!

Logged
giqcass
Hero Member & Beta Tester
*****
Posts: 1436


« Reply #1 on: September 30, 2014, 09:45:05 pm »

The auto disconnects are typically the result of router settings.  I can't remember which ones anymore.  What you experienced here seems to be something else.  If the problem doesn't clear up I would attempt to remove GV from the Obi and then put it back.
« Last Edit: September 30, 2014, 09:47:35 pm by giqcass » Logged

Long live our new ObiLords!
CLTGreg
Full Member
***
Posts: 112


« Reply #2 on: October 01, 2014, 06:17:35 am »

It's been looped in and out. I did move it to a 200 and I can test that way if I have too but it's inconvenient since it might take 50 calls to do it again.

I swear I remember some sort of time out available that could come with audio warning when the time is almost up but I can't remember who/what/where it is.
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 5806



« Reply #3 on: October 01, 2014, 09:19:16 pm »

This happened fairly often a couple years ago, and then it gradually went away.  I never saw anything that definitively identified the cause of the problem, and there are unfortunately several different things in the path that can cause it.

In the SIP world, there is the periodic registration with the SIP server, but GV doesn't use SIP, so ignore any of those settings.

If you have a problem with your home internet service, it could cause GV to erroneously detect that the call has been hung up, so it kills the connection.  Happening at exact intervals is what is so mysterious.  So many other factors can interfere.  Just one that comes to mind is something else that gets kicked off periodically on your home network, like one of your devices periodically contacting a server to sync files or download updates.  If something even momentarily swamps your network connection, it could cause the drop.

For now, you may want to try running the VoIP call quality test at this website provided by Visualware.  The regular speedtest.net tests are meaningless for VoIP, which is sensitive to network jitter and latency and brief dropouts, not shown by basic speed tests.  Pick your geographic location, pick an endpoint, and let the test run a simulated VoIP conversation.  Use the G.711 codec.  A MOS of less than 4.0 is a sign that you have network problems.

http://myspeed.visualware.com/index.php

If you do have call quality or reliability issues with a GV call, note that when you immediately call back, Google's system is keeping track of these events.  If it determines a pattern of repeated dropped calls, followed by call-backs, it flags the call route for investigation.
Logged

--Steve

Google Voice Forum Product Expert

https://support.google.com/voice/community
CLTGreg
Full Member
***
Posts: 112


« Reply #4 on: October 03, 2014, 01:06:15 am »

Thanks for the info especially the VOIP test. I ran it from Charlotte to San Jose and got jitter 0 packey loss 0 MOS of 4.2.

I agree that it's a mystery but my assumption is that an internal network glitch should cause a disconnect but not the hooks to flash on both lines. It's very similar as to getting an update pushed down from OBitalk. If I update my speed dials online or change any of the SP settings, a few seconds later the phone flashes on both lines even when on hook. This last time it was like that. I would expect the TA to be bothered by a network glitch internally but why would it push that disturbance out the ports?
Logged
SteveInWA
Hero Member & Beta Tester
*****
Posts: 5806



« Reply #5 on: October 03, 2014, 04:46:53 am »

Thanks for the info especially the VOIP test. I ran it from Charlotte to San Jose and got jitter 0 packey loss 0 MOS of 4.2.

I agree that it's a mystery but my assumption is that an internal network glitch should cause a disconnect but not the hooks to flash on both lines. It's very similar as to getting an update pushed down from OBitalk. If I update my speed dials online or change any of the SP settings, a few seconds later the phone flashes on both lines even when on hook. This last time it was like that. I would expect the TA to be bothered by a network glitch internally but why would it push that disturbance out the ports?

Your VoIP test results are stellar.  So that's not the issue.  I say, WTF?!  It sounds like maybe your OBi is spontaneously rebooting, or otherwise dropping the connection.  Can you watch the lights on the box to see if the left-most LED blinks when this happens?
Logged

--Steve

Google Voice Forum Product Expert

https://support.google.com/voice/community
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF 1.1.11 | SMF © 2006-2009, Simple Machines LLC