Hi!
I'm having a problem with the ENUM module in SER. I'm running the
"latest" SER 0.8.12 downloaded today. Compiled without any extra
flags or settings on a Redhat 9 box.
I'm getting "Enum() regexp parse error" when I'm doing a ENUM lookup. I
have my own (private network) ENUM domain and I think that everything in
DNS is ok. I've set the correct ENUM domain parameters with the
'modparam'.
This works when I'm using the Cisco SIP proxy for ENUM lookups, and the
request and answer to/from my DNS looks identical as the SER lookup.
However, SER failes to parse the expression coming back from DNS while
Cisco does it correctly and forwards on.
The regular expression I'm getting back is like this:
sip+E2U#/^(.*)$/sip:\1@mydomain.com/
where I think that the '\1' paramter should be replaced by the dialed
number in this case. This works with the Cisco...
The ENUM lookup seems to work ok, but there must be somethng wrong with
the answer or with the SER parsing the answser. Since the Cisco is
working my guess is that SER is doing something wrong. Could this be the
case?
Anyone got any clues? What am I doing wrong?
best regards,
/Staffan Kerker
--
Staffan Kerker, KIS
Commuications, AerotechTelub
m. staffan.kerker(a)aerotechtelub.se
c. +46(0)70 539 13 65
--
"Don't get involved in politics man,
just play the gig..."
/Sgt Floyd, Electric Mayhem Band
Show replies by date
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