[VoiceOps] Helluva time with international

[Mark R Lindsey]

Unless you've got a QoS-enabled path for the RTP to flow on -- where packet delivery rates are guaranteed somehow -- isn't Call Quality just a crapshoot?

Maybe the RTP path 
...will only traverse uncongested paths
...maybe the same paths will be in use today that were in use yesterday
...maybe nobody will add additional traffic to the path
...maybe nobody will add any rate limiting because of a billing dispute between two carriers I don't know
...maybe there won't be any failover events
...maybe nobody will economize and reduce link capacities


mark at ecg.co  |  +1-229-316-0013  |  http://ecg.co/lindsey



On Jul 29, 2011, at 12:07 PM, Darren Schreiber wrote:

> Thanks. We actually use Flowroute already.  The customer is still complaining. :-(
> 
> 
> -- 
> 
> 
> From: Matthew Williams <mgwilliams at gmail.com>
> Date: Fri, 29 Jul 2011 08:31:44 -0700
> To: Darren Schreiber <d at d-man.org>
> Cc: "VoiceOps at voiceops.org" <VoiceOps at voiceops.org>
> Subject: Re: [VoiceOps] Helluva time with international
> 
> Hi Darren,
> 
> At Flowroute (http://www.flowroute.com) we use Global, Level3, AT&T and other in country carriers like telecom italia, NTT for routing to ensure the highest quality -- We also let the RTP stream go directly to the final carrier. I think they would be happy with our quality.
> 
> Regards,
> Matthew Williams
> Flowroute LLC
> 
> On Thu, Jul 28, 2011 at 10:38 PM, Darren Schreiber <d at d-man.org> wrote:
>> We have a client who does sales in international locations and is constantly calling random countries. They are very sensitive to call quality. Countries called are generally in Europe, specifically lots of calls to France, Germany, Italy.
>> 
>> We have been using a carrier whom gets 60%-70% ASR on each route and gave us three routes. The problem is that when calls fail on one route, sometimes there's a long delay before we get a failure code back. If we hangup quickly and move on to the next carrier, often the phone becomes "busy" because the first attempt was actually completing, just slowly. Sometimes we also get improper early media. So waiting for a response is hit/miss on speed, and not waiting for a response is hit/miss on call completion/quality.
>> 
>> We're only doing $500-1,000 in international right now per month.
>> 
>> I'm looking for a reliable carrier to move this traffic to. I was looking at PacWest for this. We're too low on $s to go direct to Global Crossing. I'm hyper-sensitive to running through extra media servers for no reason – I want the RTP stream to go direct to the final carrier if possible.
>> 
>> I wonder if anyone can make a recommendation on whom I can use? Or how I might get access to iBasis / Global Crossing routes directly in terms of RTP? I don't meet their minimums yet.
>> 
>> - Darren
>> 
>> 
>> 
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>> 
> 
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

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