How can I improve the Round Trip Time

[Anthony R]

Hi team,

One of our customers have some remote extensions located at Manila, Philipines.

The thing is that those extensions are presenting bad quality on their calls. After running a Quality Monitor we got high RTT results >150ms.



We know there is a long distance between the Flowroute server us-west-or.sip.flowroute.com and that is something that we can't change their geopgraphic locations, but is there something we can do to improve the RTT result and have a better call Quality?

Can we request to flowroute to use a different PoP to reduce this latency? Anything that can be implemented or suggested?

Thanks for all your support in advance.

Best,
Anthony R.

 

[lancerichards]

The issue looks to be between your endpoint and the server, not the server and your trunk provider.

 

[Anthony R]

The issue looks to be between your endpoint and the server, not the server and your trunk provider.

So the RTT is between the 3CX server and the remote extensions? So, should I request a 3CX support ticket to change the 3CX server for a closer one to the endpoints?

 

[KyriacosS_3CX]

Hi,

Delay could be server to destination region, but it could be the local WiFi or telephone network. Difficult to say with strict accuracy.

If you could run a traceroute from the destination to the server - using the same internet connection the destination device is using - it might become more clear on which part of the network the delay gets added, so you can target that element.

 

[Anthony R]

Hi Kyriacos,

Thanks for your reply. The traceroute should be to us-west-or.sip.flowroute.com or to the fqdn.ca.3cx.us ?

I have that doubt when server is mentioned. I requested some voip tests to all 3 extensions and results were very acceptable.


I appreciate fot your help in advance.

Sincerely,
Anthony R.

 

[KyriacosS_3CX]

Traceroute towards the 3CX server. A traceroute is better for this rather than a speed test with ping, as you can view how much delay each hop adds.
As we saw in your initial report, the long delay is Phone to 3CX leg. Also monitoring call quality between two local users would show if the problem is located on that leg.

Regardless of the results of the trace etc, if you do decide moving the 3CX system closer to the End Users (always a good idea), you can do that on your own - 3CX deploys to the datacenter nearest to where a Licence keys region is set. For the Philippines the best option would be deployment in Singapore.

You should be able to take a backup, shut the system down completely, change the key region, redeploy and restore as needed.

Of course if you prefer assistance from the team, you can request it.

 

[SteveITS]

remote extensions located at Manila, Philipines

The reason for moving the server is that light can only travel so fast. Per random Internet site https://inventivehq.com/network-latency-calculator/, between Manila and Los Angeles:

"The distance between the origin and destination is 11744.13 km (7297.46 miles).
The theoretical one-way latency based on the speed of light in fiber optic cables is 58.72 ms.
The theoretical round-trip latency based on the speed of light in fiber optic cables is 117.44 ms."

 

[KyriacosS_3CX]

#theydidthemath