Hello list,

I see from http://www.opensips.org/Development/Development that the
ENUM module is 'commonly maintained.' Whoever has commit authority
might like to take a look at the new ISN lookup integration that
we are using with freenum.org and DNS delegation of our ITAD:

  http://scm.europalab.com/contrib/file/tip/opensips/
  http://scm.europalab.com/contrib/file/tip/opensips/enum-isn.txt
  http://scm.europalab.com/contrib/file/tip/opensips/enum-isn.diff

References:

  http://www.freenum.org/
  ftp://ftp.ietf.org/rfc/rfc3872.txt
  ftp://ftp.ietf.org/rfc/rfc2871.txt
  http://www.iana.org/assignments/trip-parameters/

Basically, files (both code and documentation) in modules/enum of
SVN trunk revision 6511 were modified to allow ISN formatting and
lookup to succeed. This was broken in all distributions, because
ISN and ENUM URLs must be formatted differently when looking up
their NAPTR entries.

A new function is exported by the ENUM module called 'isn_query()'
as well as the supporting variable isn_suffix. I didn't provide
code to handle the idea of draft-haberler-carrier-enum-01.txt or
a function 'is_from_user_isn()' but that can come later if it's
necessary.

I recommend that this or similar logic be integrated into the
next OpenSIPS distribution, partly because the distributed and
online documentation already implies that ISN lookups succeed
Search with grep(1) for 'freenum.org' in the ENUM module docs.

Cheers,
Michael

-- 
Michael Schloh von Bennewitz
http://michael.schloh.com/

_______________________________________________
Devel mailing list
Devel@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/devel

Reply via email to