<!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="#ccffff" text="#000000">
I didn't infer that he wants to evaluate based solely on price. If it
were me, I would want that same information in order to simply put the
price issue to bed such that I could evaluate other factors with less
obfuscation of the total package. Plus, I regard the easy access to
pricing data as a quality issue that reflects on the package and
service as a whole.<br>
<br>
By the same token, I am always suspicious of vendors that obscure their
prices behind a veil of quality claims.<br>
<br>
<br>
Stephen Davies wrote:
<blockquote
cite="mid:e1d90a1a0905031156r70214474xf384ee8ee4317096@mail.gmail.com"
type="cite"><br>
<br>
<div class="gmail_quote">2009/5/1 Peter Beckman <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:beckman@angryox.com">beckman@angryox.com</a>></span><br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Alexander Harrowell wrote:<br>
<br>
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What's
needed is a rate deck that includes every route the provider</blockquote>
</div>
supports, US, Canada and everything else.<br>
</blockquote>
</div>
<br>
<div><br>
</div>
<div>Hi,</div>
<div><br>
</div>
<div>You seem to want to evaluate termination providers on nothing
else except price. I'm not sure why encouraging that simplistic rule
is in the interests of termination providers, or your own, for that
matter.</div>
<div><br>
</div>
<div>What about minor details like quality, CLI support, whether the
terminating lines are legitimate or stolen from innocent third parties
- don't they matter?</div>
<div><br>
</div>
<div>Some unscrupulous scenarios for terminators to use if lots of
originators have all these rate decks in their routing engines and are
routing solely by price:</div>
<div><br>
</div>
<div>1) Publish a low rate to a destination. "Connect" calls in
excess of your capacity (so you can bill them), but connect them to
nowhere. Once originators notice apologise profusely for the technical
problem but keep the money (the originator won't be able to say exactly
which calls failed in this manner). Fail 10% of calls like this and
you can make up what your published low rate is costing you, and the
originator probably will accept the CSR that they get.</div>
<div><br>
</div>
<div>2) Publish a low rate but run your clock a bit fast to make up
the difference. Remember that you only need to be 0.000001c/min
cheapest in order to get lots and lots of minutes because people are
selecting automatically by price. </div>
<div><br>
</div>
<div>3) "Forget" to mention various billing wrinkles. Your excuse is
that the csv format doesn't provide for the flag-fall charge, or the
call attempt charge if your calls' CSR falls below a threshold, or what
have you. Make sure the info is published somewhere even though you
"can't" put them in the csv.</div>
<div><br>
</div>
<div>Can others think of more (this is quite fun >:) )</div>
<div><br>
</div>
<div>So surely you need to know more about your termination partner
than just their price? And do you really want to tell your termination
providers that all you care about is price. Some cheaply terminated
calls already sound pretty terrible. Do we really want to encourage
this race to rock bottom?</div>
<div><br>
</div>
<div>Steve</div>
<div><br>
</div>
<pre wrap="">
<hr size="4" width="90%">
_______________________________________________
--Bandwidth and Colocation Provided by <a class="moz-txt-link-freetext" href="http://www.api-digital.com">http://www.api-digital.com</a>--
asterisk-biz mailing list
To UNSUBSCRIBE or update options visit:
<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>
</body>
</html>