Outgoing GV Call Quality Issue, troubleshooting ?

[AndyForum]

Hi,

Had my OBI for about 1 month, generally I love it!

Setup

• OBI110, Static IP address
• USR5461 Router (100MB Port) connected to Time Warner High Speed Internet Modem (Also tried ASUS WL520GU Router).
• SP1 is set up for Google Voice.
• Latest firmware 1.3.0 (Build: 2675)
• Hardware version 3.4

Issue

• Inbound calls - the call quality is usually just fine inbound and outbound
• Outbound calls - I can hear fine but intermittently the other party will hear my line stutter so badly that they cannot understand me. The stutter does not improve if I redial.
• Nothing else is running on the network except my laptop.

I downloaded the OBIApp and installed X-Lite 4, no issues when dialing out from my laptop.

Is there some logging I can turn on or something I can monitor to help me track down the cause of this issue when using a phone connected to OBI110?

Thanks for any advice.

[Rick]

• Outbound calls - I can hear fine but intermittently the other party will hear my line stutter so badly that they cannot understand me. The stutter does not improve if I redial.

I'm assuming you've ensured you have no messages waiting?  If so, then have you tried making the calls with the laptop either off or disconnected?  That would eliminate it from consideration as the issue. 

[AndyForum]

I see this when (from my laptop) I "ping /t 74.125.157.125"

Reply from 74.125.157.125: bytes=32 time=456ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49
Reply from 74.125.157.125: bytes=32 time=95ms TTL=49
Reply from 74.125.157.125: bytes=32 time=53ms TTL=49
Reply from 74.125.157.125: bytes=32 time=51ms TTL=49
Reply from 74.125.157.125: bytes=32 time=62ms TTL=49
Reply from 74.125.157.125: bytes=32 time=60ms TTL=49
Reply from 74.125.157.125: bytes=32 time=388ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49
Reply from 74.125.157.125: bytes=32 time=130ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49
Reply from 74.125.157.125: bytes=32 time=61ms TTL=49
Reply from 74.125.157.125: bytes=32 time=53ms TTL=49
Reply from 74.125.157.125: bytes=32 time=54ms TTL=49
Reply from 74.125.157.125: bytes=32 time=345ms TTL=49
Reply from 74.125.157.125: bytes=32 time=54ms TTL=49
Reply from 74.125.157.125: bytes=32 time=199ms TTL=49
Reply from 74.125.157.125: bytes=32 time=50ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49
Reply from 74.125.157.125: bytes=32 time=497ms TTL=49
Reply from 74.125.157.125: bytes=32 time=51ms TTL=49
Reply from 74.125.157.125: bytes=32 time=130ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49
Reply from 74.125.157.125: bytes=32 time=52ms TTL=49

Ping statistics for 74.125.157.125:
    Packets: Sent = 10423, Received = 10423, Lost =
Approximate round trip times in milli-seconds:
    Minimum = 48ms, Maximum = 506ms, Average = 58ms

The longer durations seem to coincide with issues on the conversation, anybody any ideas what to look for next?

[AndyForum]

Mark this as closed! Turns out to be MS Outlook flooding the network with packets!!!