24 Jun
2004
24 Jun
'04
9:38 a.m.
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(a)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
24 Jun
24 Jun
4:20 p.m.
New subject: [Serusers] ENUM parsing error?
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(a)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(a)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(a)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(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
5:22 p.m.
New subject: [Serusers] ENUM parsing error?
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(a)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(a)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(a)lists.iptel.org
Ämne: [Serusers] ENUM parsing error?
Kerker Staffan writes:
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers
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(a)lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
6:08 p.m.
New subject: [Serusers] ENUM parsing error?
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
7458
days inactive
7458
days old
3 comments
4 participants
participants (4)
-
Juha Heinanen -
Kerker Staffan -
Klaus Darilion -
Zeus Ng