<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
I am using long prefix match in my system and rates tables.<br>
<br>
<br>
<br>
<a class="moz-txt-link-abbreviated" href="mailto:alex@pilosoft.com">alex@pilosoft.com</a> wrote:
<blockquote
cite="midPine.LNX.4.44.0502171305570.4825-100000@bawx.pilosoft.com"
type="cite">
<pre wrap="">On Thu, 17 Feb 2005, Kevin P. Fleming wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I wasn't considering NANPA as much as I was the rest of the world :-) In
NANPA, 99% of the routes are the same cost for nearly everyone (unless
you are an OC yourself). Alaska, Hawaii and the Caribbean being the
notable exceptions, of course.
</pre>
</blockquote>
<pre wrap=""><!---->Oh, sorry about that. I do much more domestic than LD, that's why I'm
more concerned with it. I think when you get to certain volume, you
realize that paying per-OCN-tier is more beneficial, because when seller
sells you a blend, they are taking a risk that your ratio will be out of
wack...
</pre>
<blockquote type="cite">
<pre wrap="">Certainly I could see some value in publishing +1 rates down to NPA-NXX
level for certain parts of the country (as you say, NECA routes are a
biggie). I don't think we need to try to duplicate much LERG
information, though. If I publish a route for +1602, that covers all of
+1602 unless there are exceptions listed at a more detailed level (if
there were NECA or cellular at-cost routes here, but there aren't). When
the routing database is used, if you always do a longest-match-wins,
then we don't need to list every single NPA-NXX combination, only the
exceptions.
</pre>
</blockquote>
<pre wrap=""><!---->You'd be surprised how many exceptions are there...
</pre>
<blockquote type="cite">
<pre wrap="">Same goes for international routes too: +44 is primarily a single rate,
except for cellular routes and premium numbers, which can be identified
using a prefix string.
</pre>
</blockquote>
<pre wrap=""><!---->I think unfortunately, everyone has their own rate table, and trying to
unify them won't really help.
On other hand, you can certainly do some cherrypicking based on a database
you are putting together...
-alex
_______________________________________________
Asterisk-Biz mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Asterisk-Biz@lists.digium.com">Asterisk-Biz@lists.digium.com</a>
<a class="moz-txt-link-freetext" href="http://lists.digium.com/mailman/listinfo/asterisk-biz">http://lists.digium.com/mailman/listinfo/asterisk-biz</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
All the Best!
Sergey.
=========================
Sergey Kuznetsov
President/CEO
High Intellectual Technologies, Inc.
Web: <a class="moz-txt-link-freetext" href="http://www.hitcalls.com">http://www.hitcalls.com</a>
E-mail: <a class="moz-txt-link-abbreviated" href="mailto:sergey.kuznetsov@highintellect.com">sergey.kuznetsov@highintellect.com</a>
Business phone: (416) 548-9700
Mobile phone: (647) 287-8448</pre>
</body>
</html>