Summary:ASTERISK-00838: [patch] parse ENUM NAPTR-records which use "!...!...!x" format
Reporter:maik (maik)Labels:
Date Opened:2004-01-14 06:00:39.000-0600Date Closed:2011-06-07 14:11:55
Versions:Frequency of
Environment:Attachments:( 0) enum.patch
Description:Some people think they NAPTR-records like this one:       NAPTR   100 100 "u" "E2U+h323:voice" "!^\\+492241142(.*)$!h323:2\\1@pbx-bi.corponet.info!i" .
(the 'i' means: case insensitive match ...)

The patch makes asterisk ignore the i (or any other of the /very usefull/ things) and parse the record correctly.
Comments:By: Brian West (bkw918) 2004-01-14 10:19:36.000-0600

This patch doesn't make much sense because it breaks how things SHOULD work.  If people can't form valid enum NAPTR records they need to read.  We can't go changing how asterisk processes them because then we also have to change how the world processes them too.

By: maik (maik) 2004-01-14 10:49:57.000-0600

This doesn't break anything and NAPTR-records with 'i' or wathever at the end are still valid (see RFC 3403 6.1). NAPTR-records without the extra-letter are still parsed correctly.

RFC 3403:
6. Examples
6.1 URN Example
 ;;       order pref flags service        regexp           replacement
 IN NAPTR 100   10   ""    ""  "!^urn:cid:.+@([^\.]+\.)(.*)$!\2!i"    .

I know that this is not a ENUM NAPTR-record and it doesn't make sense with ENUM but it really is valid and is used.

Examples:     NAPTR   100 100 "u" "E2U+h323" "!^\\+4971163314(.*)$!h323:\\1@foxi.vc.dfn.de!i" .       NAPTR   100 100 "u" "E2U+h323:voice" "!^\\+492241141(.*)$!h323:1\\1@pbx-bi.corponet.info!i" .

edited on: 01-14-04 11:25

By: Brian West (bkw918) 2004-01-21 01:36:46.000-0600

This patch doesn't work.  I added a few records with an i and it wouldn't work.

By: Brian West (bkw918) 2004-01-28 00:59:51.000-0600

This patch doesn't work.  Submit a new patch and we will re open and apply.