February 24, 2018, 07:52:11 am *
Welcome, Guest. Please login or register.
News:
 
   Forum Home   Search Login Register OBiTALK  
Pages: [1]
  Print  
Author Topic: Obi200 w/GV - Calls sometimes go silent (esp when on long hold)  (Read 3328 times)
Rick441
Jr. Member
**
Posts: 26


« on: November 20, 2017, 04:14:28 pm »

I have had my Obi200 for about a month, using Google Voice. I connect the Obi200 to my router with the OBiWiFi5G Wireless USB instead of a direct ethernet connection.  The Obi200 is about 15 feet from the router, with no obstructions.

I have had a fair number of calls go to permanent silence during the call.  They don't disconnect, but neither party can hear the other.

The most typical scenario is an outgoing call where I am on a lengthy hold, hearing music and an intermittent recorded apology for the extended hold.

That just happened again a few hours ago.  I was on hold for about 40 minutes, then suddenly silence.  (During the silence I called my Obi number from my mobile just to see if I would get a call waiting tone, and I did.)  After about 20 more minutes, the call finally cut off and I got a dial tone.  (I have a screenshot of the Obi portal call record taken while it was silent, if that could be of any value in diagnosis.)

Any suggestions on possible causes, and how I might remedy this?  Thanks.
« Last Edit: November 20, 2017, 04:17:21 pm by Rick441 » Logged
Rick441
Jr. Member
**
Posts: 26


« Reply #1 on: November 27, 2017, 05:00:40 pm »

Any suggestions? 
Logged
videobruce
Jr. Member
**
Posts: 45


« Reply #2 on: December 01, 2017, 11:20:32 am »

Have you tried a wired connection?
15' away, run an Ethernet cable, wireless is prone to problems.
Logged
Rick441
Jr. Member
**
Posts: 26


« Reply #3 on: December 30, 2017, 12:00:12 am »

Have you tried a wired connection?
15' away, run an Ethernet cable, wireless is prone to problems.

Thanks for the suggestion,  I'm testing an ethernet connection starting today.  At least initially, I'm testing by moving the Obi and the phone to a less-convenient location adjacent to the router, and if that solves the issues I'll move everything back and their original locations and run a cable.

(Sorry for the long delay in replying; I thought I had enabled notifications, but apparently not.)
« Last Edit: December 30, 2017, 12:16:40 am by Rick441 » Logged
Lavarock7
Sr. Member
****
Posts: 493



« Reply #4 on: December 30, 2017, 03:43:47 am »

I was going to ask if this was a Google Voice call because I remembered that they disconnect after a long hold. However I see reports that is 3 hours so probably not your issue.
Logged

My websites: Kona Coffee: http://ItsKona.Com and Web Hosting: http://PlanetAloha.Info
A simplified Voip explanation: http://voip.planet-aloha.com
Rick441
Jr. Member
**
Posts: 26


« Reply #5 on: December 30, 2017, 01:57:39 pm »

I was going to ask if this was a Google Voice call because I remembered that they disconnect after a long hold. However I see reports that is 3 hours so probably not your issue.

Your post reminds me that it had gotten to the point where the situation would often happen *early* in the call, too.  And sometimes result in a dial tone rather than silence.  And BTW, again this is all using Google Voice.

BTW, it also occurred to me last night that the phone can be at a distance from an ethernet-connected Obi just by running a phone wire, not a long ethernet cable.  But I'll still test for awhile with all components in the same place.
Logged
Rick441
Jr. Member
**
Posts: 26


« Reply #6 on: January 04, 2018, 04:09:14 pm »

While, thus far, I have not had any calls go to silent since switching to a direct ethernet connection, I am having a different kind of dropped calls problem:

When I call a business, moments after I am put on hold (either by a voice menu or by someone I was talking to) the call often *fully disconnects* within about 5 seconds and I get a dialtone.  This has now happened with too many different businesses to think the system/person on the other end is to blame.  I have already tried the self-help advice to switch to full-duplex for the ethernet connection to the router but that didn't help.  Any suggestions?  Thanks.
« Last Edit: January 04, 2018, 04:12:40 pm by Rick441 » Logged
videobruce
Jr. Member
**
Posts: 45


« Reply #7 on: January 05, 2018, 07:31:50 am »

Have you ever run a TraceRoute program? Not that useless POS that M$ offers in a command prompt, but a real program?

I would suggest '3d Traceroute'. It is now defunct, BUT most of the functions are enabled, only a couple are not and they aren't important.

Take a look here;
http://www.majorgeeks.com/files/details/3d_traceroute.html
https://www.techrepublic.com/article/take-a-graphical-look-at-the-net-with-3d-traceroute/

What you want to look for is high latency (labeled "max") & 'jitter' (labeled "var") at any of the hops, specifically the 2nd or 3rd. The top program is another, but 3d Route is far better since it included 'jitter' which is a major issue with VoIP. The concept is to let the porgtam run over a period of time. Many issues are intermittent and running a single 'ping' or TraceRoute is usually useless since it won't 'catch' the occurrence.

You don't need a long route, it's the 'hops' within your ISP that are usually the concern. if you can get the addresses for your VoIP providers servers that's even better.

« Last Edit: January 05, 2018, 07:52:40 am by videobruce » Logged
Rick441
Jr. Member
**
Posts: 26


« Reply #8 on: January 05, 2018, 08:40:56 pm »

Thanks for the suggestion. I'm going to try a factory reset first, and if that doesn't help (and I'm not optimistic it will), I 'll try TraceRoute.
Logged
Pages: [1]
  Print  
 
Jump to:  

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