[VoiceOps] Maximum latency

Ivan Kovacevic ivan.kovacevic at startelecom.ca
Wed Mar 22 14:08:28 EDT 2017

The reality is that you can’t get away from it. A private circuit may cut
it by 10% and provide more stable Jitter… but that’s it. So your client and
500,000 other agents in the Philippines and India are in the same boat.

Where latency gets really nasty and there is some scope to optimize is on
call transfers/conferences. Make sure there is never hairpinning through
the off-shore call centre. Or that call transfers or conferences have to
double up on the path. It will depend on where the media gateways for the
solution reside and whether you have any optimization when multiple call
legs are made through your service.

Not sure if this helps…

Best Regards,

Ivan Kovacevic

Vice President, Client Services

Star Telecom | www.startelecom.ca
| SIP Based Services for Contact Centers | LinkedIn

*From:* VoiceOps [mailto:voiceops-bounces at voiceops.org] *On Behalf Of *Carlos
*Sent:* March 22, 2017 1:59 PM
*To:* voiceops at voiceops.org
*Subject:* [VoiceOps] Maximum latency

One of our larger customers is about to launch a new call center in
Malaysia.  The connection there is fast, the trace looks surprisingly clean
and short, but latency is consistently at 239-245ms.  We've never knowingly
had a connection over 130ms.  Does anyone have experiences, good or bad,
with latency approaching a quarter second?  The jitter level seems fine, so
I believe they'll just have a delay but decent call quality.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20170322/e0441b3c/attachment.html>

More information about the VoiceOps mailing list