News:

On Tuesday September 6th the forum will be down for maintenance from 9:30 PM to 11:59 PM PDT

Main Menu

GV delays ringing forwarded phones

Started by erkme73, January 22, 2014, 08:15:23 AM

Previous topic - Next topic

erkme73

I now know that this isn't a problem between GV and the OBi box.   I assumed it was related to how GV communicates with the OBi box.  So I signed up for OBiVoice and see the problem is still there.

Intermittently, when someone calls my GV number, they hear ringing 3-4 times before my OBi box (or cell or hangouts) rings.  By the time I hear the first ring, they've already been intercepted by GV's voicemail.

Does anyone know if there is a setting on GV that will expedite moving the call to the forwarded phones?


MikeHObi

ack... it is a probably a google problem but you should talk with obivoice and let them know about the problem.  See if you can duplicate.
Obi202 user & Obi100 using Anveo and Callcentric.

erkme73

I would, but it's not consistent or repeatable enough.  And for that matter, it's happening on all forwarded lines (my cell, and Hangouts).  So I'm thinking it's with GV's forwarding system.    I guess I'm just venting, and hoping others have seen the same thing - so I know it isn't operator error.

Dixon

I have never noticed a ring delay in my testing of GV>OV.
I will do some more testing tomorrow. I am in MD. What state are you in? Sometimes the call route can make a difference. Do you know how to test for packet loss?

erkme73

#4
Testing for packet loss on the OBi>OV connection? No - but packet/jitter testing in general using visual route, yes.



[edited to add... I reverted back to the delay between caller and recipient during a phone call from here on - sorry]

I saw your post earlier that said 200-400ms to a cell.  So if both caller and recipient are OV, and are both on the high end of that range, that's a very perceptible 1 second delay.

I'm in central FL with FIOS (50/25 package) - and my connection has always been rock-solid. I've been using OBi w/GV for several years, and never saw this kind of delay... That's really the only reason I suspect it's OV - or specifically 2 x OV.



I'm all ears on how and what to test.

Dixon

OV calls to OV must double the delay. Use ping plotter freeware, ping sms.intelaphone.com, and look at the last hop. Mine is avg 115ms. Max 165. The last few hops you can see are in Seattle. That is kinda high. So when I make a local call, there is a ~200-300ms delay since it has to go through Seattle and back to MD. Still usable. But in your case since you are calling another OV user, you have double that or more.

Maybe you should calling that other OV number on GV page and have it ring your OV number. It may take a different route.

gderf

Help me OBiHai PhoneOBi. You're my only hope.

erkme73

Interesting.  I get unreachable:

Target Name: sms.intelaphone.com
         IP: 54.235.159.97
  Date/Time: 1/22/2014 11:27:31 PM

1    0 ms  my.router [192.168.1.1]
2    4 ms  L100.TAMPFL-VFTTP-93.verizon-gni.net [96.254.217.1]
3    8 ms  G0-13-0-7.TAMPFL-LCR-22.verizon-gni.net [130.81.190.128]
4    8 ms  so-2-0-0-0.TPA01-BB-RTR2.verizon-gni.net [130.81.28.214]
5   *       [-]
6   13 ms  [204.255.168.42]
7   *       [-]
8   39 ms  [65.120.78.82]
9   70 ms  [205.251.245.27]
10   71 ms  [205.251.245.41]
11   *       [-]
12   *       [-]
13   *       [-]
14   68 ms  [216.182.232.167]
15   *       [-]
16   *       [-]
17   *       [-]
18   *       [-]
19   *       [-]
20   *       [-]
21   *       [-]
22   *       [-]
23   *       [-]
24   *       [-]
25   *       [-]
26   *       [-]
27   *       [-]
28   *       [-]
29   *       [-]
30   *       [-]
31   *       [-]
32   *       [-]
33   *       [-]
34   *       [-]
35   *       [-]

Destination not reached in 35 hops

dudlee

erkme73,

I have the exact same problem.  When I call the gv number that is being forwarded to my callcentric number, it rings 3 times before the obi rings.  The obi then rings 1 time and is answered by voice mail.

gderf

Quote from: erkme73 on January 22, 2014, 08:27:39 PM
Interesting.  I get unreachable:

That's because it will not respond to ICMP pings. I used TCP pings.
Help me OBiHai PhoneOBi. You're my only hope.

erkme73

#10
I'm game on testing it the proper way.  But using the Ping Plotter software with TCP I get 41ms - but with a number of pink errors.  Is that of concern?