[Asterisk-Users] New ENUM service, what do you think?

[Duane]

John Todd wrote:

> TRIP (RFC 3219) is the answer, but I'm the only one pounding that drum, 
> it seems.  If anyone here on the list has $100,000 to put together a 
> real programming effort towards getting that implemented, y'all let me 
> know.  The longer this waits, the more lame and broken become the 
> solutions offered.  <sigh>

One small oversight in your thinking, something like TRIP will only 
benefit large telcos and VOIP providers with interconnects, I don't see 
this flowing down to a tangible benefit to the average person, where as 
something like enum.164 is.

TRIP is based on BGP and BGP already does most of the IP routing smarts 
TRIP is supposed to be beneficial for, however that $100k would be 
better spent on improving the smarts in the call routing software rather 
then turning things back into a hub and spoke model, p2p is way more 
efficient if it can be utilised to it's full potential.

At this stage the only potential method to prevent VOIP spam is 
something like SPF records, which would only end up duplicate enum. It's 
a lot harder to get phone numbers then IP addresses, so this would 
overcome people's concerns about dynamically allocated IPs, phone 
numbers aren't.

-- 
Best regards,
  Duane

http://www.cacert.org - Free Security Certificates
http://www.nodedb.com - Think globally, network locally
http://www.sydneywireless.com - Telecommunications Freedom
http://happysnapper.com.au - Sell your photos over the net!
http://e164.org - Using Enum.164 to interconnect asterisk servers