Network Discovery

Your public IP address is: Loading..

HOW TO GET THE RETURN TRIP TIME (RTT)

Ask for the IP address of the remote computer you want to get the RTT for.

macOS: Open /Applications/Terminal.app Windows: Select Start > Programs > Accessories > Command Prompt.

Type "ping 12.34.56.77" where the IP address is the remote IP. Hit the Enter key Wait for 10-20 pings. It will look like this:

PING 12.34.56.78 (12.34.56.78): 56 data bytes
64 bytes from 23.45.67.89: icmp_seq=0 ttl=54 time=121.108 ms
64 bytes from 23.45.67.89: icmp_seq=1 ttl=54 time=120.491 ms
64 bytes from 23.45.67.89: icmp_seq=2 ttl=54 time=119.604 ms
64 bytes from 23.45.67.89: icmp_seq=3 ttl=54 time=119.775 ms
64 bytes from 23.45.67.89: icmp_seq=4 ttl=54 time=120.431 ms
64 bytes from 23.45.67.89: icmp_seq=5 ttl=54 time=119.858 ms
64 bytes from 23.45.67.89: icmp_seq=6 ttl=54 time=120.039 ms
64 bytes from 23.45.67.89: icmp_seq=7 ttl=54 time=119.849 ms
64 bytes from 23.45.67.89: icmp_seq=8 ttl=54 time=120.385 ms
64 bytes from 23.45.67.89: icmp_seq=9 ttl=54 time=121.249 ms

On the keyboard press "control + c"

The average RTT time is found:
round-trip min/avg/max/stddev = 119.604/120.279/121.249/0.533 ms

So in this example the RTT is "120 milliseconds" Use this value for the ideal Buffer setting in Source-Connect Pro. We recommend a minimum of 200ms, as lower values may be subject to additional drops where time is insufficient for replacement packets.

FINDING NETWORK DROPOUT ISSUES

This method can also tell you if you have drop-out issues with your connection partner. If you have a high packet loss or 'stddev' value this causes clicks and pops in your audio. Note that this cannot tell us which side may be having network issues however.

Follow the instructions at the top to get a ping display going. Leave it for a while so we get a good sampling.

PING 12.34.56.78 (12.34.56.78): 56 data bytes
64 bytes from 23.45.67.89: icmp_seq=0 ttl=54 time=121.108 ms
64 bytes from 23.45.67.89: icmp_seq=1 ttl=54 time=150.491 ms
64 bytes from 23.45.67.89: icmp_seq=2 ttl=54 time=119.604 ms
64 bytes from 23.45.67.89: icmp_seq=3 ttl=54 time=149.745 ms
64 bytes from 23.45.67.89: icmp_seq=4 ttl=54 time=130.431 ms
64 bytes from 23.45.67.89: icmp_seq=5 ttl=54 time=129.858 ms
64 bytes from 23.45.67.89: icmp_seq=6 ttl=54 time=190.039 ms
64 bytes from 23.45.67.89: icmp_seq=7 ttl=54 time=209.849 ms
64 bytes from 23.45.67.89: icmp_seq=8 ttl=54 time=150.385 ms
64 bytes from 23.45.67.89: icmp_seq=9 ttl=54 time=151.108 ms
64 bytes from 23.45.67.89: icmp_seq=10 ttl=54 time=120.491 ms
64 bytes from 23.45.67.89: icmp_seq=11 ttl=54 time=120.491 ms
64 bytes from 23.45.67.89: icmp_seq=12 ttl=54 time=169.604 ms
64 bytes from 23.45.67.89: icmp_seq=13 ttl=54 time=179.775 ms
64 bytes from 23.45.67.89: icmp_seq=14 ttl=54 time=170.431 ms
64 bytes from 23.45.67.89: icmp_seq=15 ttl=54 time=219.858 ms
64 bytes from 23.45.67.89: icmp_seq=16 ttl=54 time=290.039 ms
Request timeout for icmp_seq 17
64 bytes from 23.45.67.89: icmp_seq=18 ttl=54 time=190.385 ms
64 bytes from 23.45.67.89: icmp_seq=10 ttl=54 time=121.108 ms
64 bytes from 23.45.67.89: icmp_seq=20 ttl=54 time=140.491 ms
64 bytes from 23.45.67.89: icmp_seq=21 ttl=54 time=150.491 ms
64 bytes from 23.45.67.89: icmp_seq=22 ttl=54 time=149.604 ms
64 bytes from 23.45.67.89: icmp_seq=23 ttl=54 time=129.775 ms
64 bytes from 23.45.67.89: icmp_seq=24 ttl=54 time=140.431 ms
64 bytes from 23.45.67.89: icmp_seq=25 ttl=54 time=139.858 ms
^C
--- 12.34.56.78 ping statistics ---
26 packets transmitted, 25 packets received, 4% packet loss
round-trip min/avg/max/stddev = 121.108/205.279/290.039/80.533 ms

We can see above that the RTT is not stable: it jumps from 120 to 290 at the highest, the stddev value is really high at 80ms (ideally should be below 0ms), and may also drop a packet. This shows that the connection between you and that IP address has some issues.

Contact your Source Elements support, your ISP or your IT admin with the Ping report you have generated as shown above for guidance on making improvements.