[asterisk-bugs] [Asterisk 0014576]: ENUMLOOKUP - broken regex.

[Asterisk Bug Tracker]

The following issue has been RESOLVED. 
====================================================================== 
http://bugs.digium.com/view.php?id=14576 
====================================================================== 
Reported By:                chris-mac
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   14576
Category:                   Functions/func_enum
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           SVN 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6.1 
SVN Revision (number only!): 178608 
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2009-03-01 15:56 CST
Last Modified:              2009-03-06 11:19 CST
====================================================================== 
Summary:                    ENUMLOOKUP - broken regex.
Description: 
The following number +44800123123 is registered with e164.org.

$ dig 3.2.1.3.2.1.0.0.8.4.4.e164.org naptr
returns:
....
3.2.1.3.2.1.0.0.8.4.4.e164.org. 11 IN   NAPTR   200 10 "u" "E2U+SIP"
"!^\\+44800(.*)$!sip:44800\\1 at selfnet.at!" .

so in theory it should translate to: sip:44800123123 at selfnet.at

But the following dialplan function:
exten => _X.,n,Set(ENUM_URI=${ENUMLOOKUP(+44800123123,sip,s,,e164.org)})
exten => _X.,n,NoOp(Enum URI: ${ENUM_URI})

returns: 

... "Enum URI: 4480044800123123 at selfnet.at") in new stack


====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-03-06 11:19 svnbot         Status                   assigned => resolved
2009-03-06 11:19 svnbot         Resolution               open => fixed       
======================================================================