News:

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

Main Menu

Delay (latency) when speaking with someone (Google Voice + OBi200)

Started by dstruktNine, December 24, 2014, 03:56:47 PM

Previous topic - Next topic

dstruktNine

I just signed and I've noticed that if I get a call or make a call on my OBi, there's a significant delay between when I'm speaking and listening. This article sums it up:

http://www.pcmag.com/article2/0,2817,2383262,00.asp

I can't take a break when talking because the other person thinks I've stopped and I start talking over them.

I have 50Mbps UPLOAD so it can't be a bandwidth issue. I have DD-WRT installed on my router, but I haven't messed with any QoS settings.

Thanks!

dstruktNine

Ok I made another call and took a screenshot of the data. I guess it doesn't look too bad, but I really don't know what numbers are suppose to be good.


Taoman

How does the echo test sound?  **9222-222-222

Call 206-456-0649 and compare to the echo test there (option 3) after the initial record playback test

What is your ping time to 74.125.39.7 (from your screen shot)?

dstruktNine

The OBi echo test is about 0.30 secs.

The number you mentioned is 0.80 secs, probably more. I was using a stop watch when measuring both echo tests.

My ping to the IP:

Ping statistics for 74.125.39.7:
   Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
   Minimum = 57ms, Maximum = 59ms, Average = 58ms

dstruktNine

Here is a tracert:

Tracing route to 74.125.39.7 over a maximum of 30 hops

 1     1 ms    <1 ms    <1 ms  DD-WRT [192.168.1.1]
 2     4 ms     1 ms     1 ms  xxx.xxx-xx-xx.ftth.swbr.surewest.net [xx.xx.xxx.
xx]
 3     1 ms     3 ms     1 ms  172.22.128.145
 4     1 ms     1 ms     1 ms  172.21.1.1
 5     1 ms     1 ms     2 ms  172.21.0.254
 6    10 ms     8 ms     5 ms  te-7-1.car1.Sacramento1.Level3.net [4.53.200.37]

 7     7 ms     7 ms    12 ms  ae-4-90.edge1.SanJose3.Level3.net [4.69.152.208]

 8     5 ms     6 ms     5 ms  72.14.223.91
 9    11 ms     6 ms     5 ms  209.85.249.3
10    57 ms    61 ms    57 ms  209.85.246.253
11    51 ms    51 ms    51 ms  216.239.46.240
12    57 ms    57 ms    57 ms  216.239.46.55
13    57 ms    60 ms    57 ms  216.239.46.191
14     *        *        *     Request timed out.
15    58 ms    57 ms    57 ms  74.125.39.7

Trace complete.


I'm using Google's DNS, BTW.

Taoman

Quote from: dstruktNine on December 24, 2014, 05:25:58 PM

The number you mentioned is 0.80 secs, probably more.

That could be a problem. What is your subjective feeling about that echo test? Is the latency too high to have a conversation? And you notice no difference between receiving a call and placing a call? They both suck?

I don't see anything terrible in your numbers except potentially the one above. In the end, it all comes down to what is acceptable to you. That said, I don't use Google Voice except to forward. I use SIP providers for both incoming and outgoing. As you are well aware.......latency matters.

dstruktNine

Well, the first echo test was fine, but having almost 1 sec delay on the second test is unacceptable.

During my test call, it didn't seem quite as high as .8 seconds, but my previous calls did seem that high.

The phone isn't mission critical or anything; just a home phone number, but I will give it a few weeks and see what happens.

patlaw

I'm experiencing exactly the same result. The 222 echo test is about a quarter of a second. Any dialed telephone number is about a second. If I call the Obi200 from another phone, the latency is about a quarter of a second. A one-second latency is not acceptable. The latency on my VOIPo service through their Linksys ATA is about a quarter of a second on any call, incoming or outgoing.