[Asterisk-biz] Call termination database 0.2

[Alistair Cunningham]

Kevin & Duane,

Okay, you've persuaded me that patterns need to be more flexible. I'll 
see if I can make them regular expressions, so you can do things like:

61[0-36-9]
61[^45]

There's no way this is going to work with sub range matches, so that 
functionality is going to have to go. This means that if you search for 
  44, a pattern of 4420 isn't going to be found. Which is more important 
to everyone?

Alistair Cunningham,
Integrics Ltd,
Telephony, Database, Unix consulting worldwide
+44 (0)7870 699 479
http://integrics.com/


Kevin P. Fleming wrote:
> Duane wrote:
> 
>> Australia... +61, only a few exceptions compared to non-exceptions...
>>
>> +611, +61[4-5] = mobile and special services...
> 
> 
> That's exactly my point! If a provider lists a termination for +61 and 
> nothing else, are we supposed to assume that their posted rate is good 
> for all of +61, or only for the parts of +61 that we _know_ are 
> fixed-line routes? I think the latter is far, far safer, given than the 
> database will quickly have enough information to be able to identify 
> which routes are fixed-line and which are not.
> 
> I would like to see the system, when you search or download, provide a 
> "not available" route for +614 and +615 for a given provider, if they 
> have only provided a +61 route. I'm not suggesting that the database 
> needs to provide routes for every possible prefix in +61, only the ones 
> that we have learned are non-standard routes (not fixed-line).
> _______________________________________________
> Asterisk-Biz mailing list
> Asterisk-Biz at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-biz
> 
>