<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>RE: [asterisk-biz] Least Cost Routing Rates</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>>-----Original Message-----<BR>
>From: asterisk-biz-bounces@lists.digium.com on behalf of Alex Balashov<BR>
>Sent: Fri 8/3/2007 4:44 PM<BR>
>To: Commercial and Business-Oriented Asterisk Discussion<BR>
>Subject: Re: [asterisk-biz] Least Cost Routing Rates<BR>
><BR>
>On Fri, 3 Aug 2007, Douglas Garstang wrote:<BR>
><BR>
>> Assuming you used several ITSP's, and you wanted to do least cost<BR>
>> routing, does anyone have any suggestions as to the best way to manage<BR>
>> all the routes and their costs?<BR>
><BR>
> There are a number of home-brewed and enterprise-strength LCR and<BR>
>general call routing/settlement/peering platforms out there. My personal<BR>
>recommendation is TransNexus's NexSRS:<BR>
><BR>
> <A HREF="http://www.transnexus.com/">http://www.transnexus.com/</A><BR>
><BR>
> We use it at my workplace. Very robust.<BR>
<BR>
I'll check them out. I often end up rolling my own solutions because rarely do solutions provided by a third party deliver on all the requirements.<BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>