[Asterisk-biz] Call termination database

[Linus Surguy]

Just a thought, when people buy VoIP termination they should also be asking 
where the IP gateway is located - for example a lot of people in the UK and 
Europe are choosing us for their PSTN termination because we are well 
connected and based in Telehouse in London, rather than the added distance 
of a US carrier. This gives not only reduced latency to European 
destinations, but also reduces the transit element on the public internet.

When you work on your database, you should at least store region (North 
America, Europe, etc) if not country.

Linus
Magrathea

----- Original Message ----- 
From: "Alistair Cunningham" <acunningham at integrics.com>
To: "Commercial and Business-Oriented Asterisk Discussion" 
<asterisk-biz at lists.digium.com>
Sent: Friday, February 18, 2005 12:21 AM
Subject: Re: [Asterisk-biz] Call termination database


> Duane,
>
> Yes, this is exactly what I had in mind. I've made a start on this today. 
> So far so good, and the only gotcha so far is handling different 
> currencies. For version 1, there's probably only going to be one currency, 
> most likely USD.
>
> I'm also considering adding DID offerings. Would people be interested in 
> this?
>
> Alistair Cunningham,
> Integrics Ltd,
> Telephony, Database, Unix consulting worldwide
> +44 (0)7870 699 479
> http://integrics.com/
>
>
> Duane wrote:
>> Kevin P. Fleming wrote:
>>
>>
>>>As it stands now, pretty much every provider has their own "rate chart"
>>>format, and many of them are incomplete and/or inaccurate. I wasn't
>>>really thinking about actually building a _rate_ database, since the
>>>rates are frequently not public, based on volume, etc.
>>
>>
>> Actually this would be something simple to build, and could even include
>> more specific routes as needed.
>>
>> In the number field you store the number as specific as possible,
>> minimum amount of minutes and cost.
>>
>> Then you allow people to enter the route they want access to the amount
>> of minutes they think they will make use of. Off the top of my head
>> something like the sql (works in mysql) below should work just fine.
>> What wouldn't be so trivial is comparing minimum call lengths, billing
>> times and rounding etc, you'd just have to display on the matching
>> minutes/route and the person looking to buy would have to make their own
>> mind up as to what was a better deal (not just price per minute)...
>>
>> SELECT * FROM `rates` where LOCATE('$number', `route`) = 1 and `minutes`
>> <= '$minutes' ORDER BY `cost` ASC
>>
> _______________________________________________
> Asterisk-Biz mailing list
> Asterisk-Biz at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-biz
>