I use a FreeBSD box as a bump-in-the-wire to test and introduce additional 
latency, packet loss, and jitter using ipfw – this is a pretty good overview of 
how to do it: 
http://fjoanis.github.io/2013/08/31/Network_Simulation_FreeBSD_DummyNet/

From: VoiceOps <[email protected]> on behalf of Carlos Alvarez 
<[email protected]>
Date: Wednesday, March 22, 2017 at 2:13 PM
To: "[email protected]" <[email protected]>
Subject: Re: [VoiceOps] Maximum latency

Those are some excellent points, Ivan.  They do indeed transfer calls regularly 
between agents in various US cities, so I assume the foreign ones will also.  
I'll have to ask.

The US agents are on MPLS to us, 2-3ms at most.

Also, my satellite phone seems to have around 700ms delay, which is quite 
challenging.  I should try synthesizing 250ms for them and let them try it.  
Not sure how, but assume there's some open source out there to do it.



On Wed, Mar 22, 2017 at 11:08 AM, Ivan Kovacevic 
<[email protected]<mailto:[email protected]>> wrote:

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<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1qMvVnW3LjyBM63K6FlW63JXmj56dLPjf6TyZWx02?t=http%3A%2F%2Fwww.startelecom.ca%2F&si=6470560385859584&pi=36c7d4bb-13b1-426d-bf96-c8c2ff149bdd>
 | SIP Based Services for Contact Centers | 
LinkedIn<http://t.sidekickopen61.com/e1t/c/5/f18dQhb0S7lC8dDMPbW2n0x6l2B9nMJW7t5XYg1qMvVnW3LjyBM63K6FlW63JXmj56dLPjf6TyZWx02?t=https%3A%2F%2Fwww.linkedin.com%2Fcompany%2Fstar-telecom-www-startelecom-ca-%3Ftrk%3Dbiz-companies-cym&si=6470560385859584&pi=36c7d4bb-13b1-426d-bf96-c8c2ff149bdd>

From: VoiceOps 
[mailto:[email protected]<mailto:[email protected]>] On 
Behalf Of Carlos Alvarez
Sent: March 22, 2017 1:59 PM
To: [email protected]<mailto:[email protected]>
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.

Error! Filename not specified.

_______________________________________________
VoiceOps mailing list
[email protected]
https://puck.nether.net/mailman/listinfo/voiceops

Reply via email to