Hi Hm.. I noticed that one too, but the Cisco proxy is recieving exactly the same expression and then there is no problem.
The NAPTR RR in DNS for extension 2210 looks like:
$ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "/^(.*)$/sip:\1@iptel2.mydomain.com/" .
Any clues?
rgds, /Staffan
-----Ursprungligt meddelande----- Från: Juha Heinanen [mailto:jh@tutpro.com] Skickat: den 24 juni 2004 06:54 Till: Kerker Staffan Kopia: serusers@lists.iptel.org Ämne: [Serusers] ENUM parsing error?
Kerker Staffan writes:
The regular expression I'm getting back is like this:
sip+E2U#/^(.*)$/sip:\1@mydomain.com/
what is sip+E2U# in front of the regexp field? can you show me how exactly the NAPTR record looks like?
-- juha
I'm not 100% sure, but I think enum module expect "!" as the delimiter for regexp. You may try:
$ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "!^(.*)$!sip:\1@iptel2.mydomain.com!" .
Zeus
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Kerker Staffan Sent: Thursday, 24 June 2004 4:38 PM To: Juha Heinanen Cc: serusers@lists.iptel.org Subject: SV: [Serusers] ENUM parsing error?
Hi Hm.. I noticed that one too, but the Cisco proxy is recieving exactly the same expression and then there is no problem.
The NAPTR RR in DNS for extension 2210 looks like:
$ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "/^(.*)$/sip:\1@iptel2.mydomain.com/" .
Any clues?
rgds, /Staffan
-----Ursprungligt meddelande----- Från: Juha Heinanen [mailto:jh@tutpro.com] Skickat: den 24 juni 2004 06:54 Till: Kerker Staffan Kopia: serusers@lists.iptel.org Ämne: [Serusers] ENUM parsing error?
Kerker Staffan writes:
The regular expression I'm getting back is like this:
sip+E2U#/^(.*)$/sip:\1@mydomain.com/
what is sip+E2U# in front of the regexp field? can you show me how exactly the NAPTR record looks like?
-- juha
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
This is my ENUM entry which works fine:
;; ANSWER SECTION: 2.0.1.6.6.3.6.6.9.9.5.3.4.e164.arpa. 10800 IN NAPTR 100 10 "u" "E2U+sip" "!^.*$!sip:e001-366102@enum.at43.at!" .
regards, Klaus
Zeus Ng wrote:
I'm not 100% sure, but I think enum module expect "!" as the delimiter for regexp. You may try:
$ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "!^(.*)$!sip:\1@iptel2.mydomain.com!" .
Zeus
-----Original Message----- From: serusers-bounces@lists.iptel.org [mailto:serusers-bounces@lists.iptel.org] On Behalf Of Kerker Staffan Sent: Thursday, 24 June 2004 4:38 PM To: Juha Heinanen Cc: serusers@lists.iptel.org Subject: SV: [Serusers] ENUM parsing error?
Hi Hm.. I noticed that one too, but the Cisco proxy is recieving exactly the same expression and then there is no problem.
The NAPTR RR in DNS for extension 2210 looks like:
$ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "/^(.*)$/sip:\1@iptel2.mydomain.com/" .
Any clues?
rgds, /Staffan
-----Ursprungligt meddelande----- Från: Juha Heinanen [mailto:jh@tutpro.com] Skickat: den 24 juni 2004 06:54 Till: Kerker Staffan Kopia: serusers@lists.iptel.org Ämne: [Serusers] ENUM parsing error?
Kerker Staffan writes:
The regular expression I'm getting back is like this:
sip+E2U#/^(.*)$/sip:\1@mydomain.com/
what is sip+E2U# in front of the regexp field? can you show me how exactly the NAPTR record looks like?
-- juha
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
Zeus Ng writes:
I'm not 100% sure, but I think enum module expect "!" as the delimiter for regexp. You may try:
$ORIGIN 1.2.2.e164.mydomain.com. 0 NAPTR 100 10 "u" "sip+E2U" "!^(.*)$!sip:\1@iptel2.mydomain.com!" .
that is right. currently enum module assumes that regexp delimiter is "!", which seems to be a common convention and in etsi enum spec is SHALL. i could make it more general, but right now i have other, higher priority things to worry about.
-- juha