At 20:37 10-6-2003 -0700, you wrote:
You should investigate TRIP (RFC 3129):
http://www.zvon.org/tmRFC/RFC3219/Output/
Find BSD-licensed proof-of-concept code at http://www.vovida.org/downloads/trip/trip-1.0.0.tar.gz
If someone could incorporate this into Asterisk and extend the functionality, that would be pretty nice. The basic ENUM support in Asterisk already can handle specific number paths, but I think TRIP or something like TRIP would be best for handling situations where larger groups of numbers need to be "advertised" into a routing table behind a particular Asterisk server. Think "BGP for phone numbers."
I'm sorry, but I see no real benefits to TRIP over ENUM. Large amounts of data in DNS databases have not been a real problem yet, provided the tree is delegated properly (as ENUM does), and works quite effectively due to caching.
TRIP only makes it harder for widespread use to deal with such things as number portability (can't ever do that with IP, remember). As far as I can tell from the TRIP docs this looks a lot like some big telco tries to make it more difficult for customers to move to another telco and still use their old number...
Florian
_______________________________________________ Asterisk-Users mailing list [EMAIL PROTECTED] http://lists.digium.com/mailman/listinfo/asterisk-users
