how-to block ads
Primus TBB servers.
Ping the Primus TBB server to determine the (roundtrip) latency from your DVG ATA to it - you can get the IP address from the "Notify Entity" line when you login to the DLINK DVG ATA.
(For Windows users: from a "Command Prompt" in Start->Accesories)
ping -n 10 [fill in your DVG`s "Notify Entity" IP address here]
(For Macintosh OS X users: from a Terminal prompt in Applications/Utilities)
ping -c 10 [fill in your DVG`s "Notify Entity" IP address here] You may also yuse the Network Utility instead of the Terminal application.
You will get 10 lines of response with ..32 bytes (64 for Macintosh), a time and TTL. The avg, min, max times are displayed on the last line.
The round trip latency to the TBB server should be 50-60ms for a decent connection. This is not an *absolute* figure, since it also depends on the rest of the "path"... including where the call is terminating, amongst other factors.
You should use a wired connection when using ping, to minimize any artificial LAN delays in the results. Using a WiFi connection will introduce variable delays which may be erroneously interpreted as jitter.
If you are having periodic short "half-second" problems (chops voice for a split second) every now and then, then using ping is difficult as standard pings run every 1 sec. The ping would have to run almost in sync with the other packets generating the congestion within that half second.. to show a latency/jitter problem. In other words, the ping packets may come just before or after the half second congestion, and so they do not have/show any delay.
If you have continuous VoIP problems (ex choppy for 5 seconds straight) then the pings will most likely show the latency/jitter; since the traffic causing the congestion is there during four pings in this example; the ping packets are going to get held up and this will be reflected in the results output...