[Serusers] ENUM parsing error?
Zeus Ng
zeus.ng at isquare.com.au
Thu Jun 24 15:20:15 CEST 2004
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 at iptel2.mydomain.com!" .
Zeus
> -----Original Message-----
> From: serusers-bounces at lists.iptel.org
> [mailto:serusers-bounces at lists.iptel.org] On Behalf Of Kerker Staffan
> Sent: Thursday, 24 June 2004 4:38 PM
> To: Juha Heinanen
> Cc: serusers at 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 at iptel2.mydomain.com/" .
>
>
> Any clues?
>
> rgds,
> /Staffan
>
>
>
> -----Ursprungligt meddelande-----
> Från: Juha Heinanen [mailto:jh at tutpro.com]
> Skickat: den 24 juni 2004 06:54
> Till: Kerker Staffan
> Kopia: serusers at 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 at 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 at lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
>
More information about the sr-users
mailing list