Hello Jean
It does enum query but only supports single sip addresses without
regular expressions.
For example:
if you have the following query : 6.6.2.4.7.2.5.0.e164.arpa
and response : naptr = 10 100 "u" "E2U+sip" "!^(.*)$!sip:\
\
1...@82.80.200.62!" .
DefaultDnsServiceLocator lookupSipUri function will translate it to
sip:\\
1...@82.80.200.62 and will try to create SipURI from that
which of course is invalid.
Another example
===========================================================================
The regexp handling is extremely handy if you use DNS wildcards in
your
ENUM zone. Then one DNS record will match many different DNS queries
and
thus apply to many E.164 numbers. In order to have the resulting URI
reflect the initial E.164 number, you have to use a more complex
regexp.
Consider e.g.
+43 1 5056416. That's our office phone number here
in Vienna. We're free to define extensions to that number, e.g.
+43 1 5056416 33 is my desk phone. Austria uses an open numbering
plan where the length of a number isn't fixed. We could thus
use two single ENUM entries to cover all our needs:
; main number
6.6.1.4.6.5.0.5.1.3.4.e164.arpa. NAPTR 10 10 "u"
"E2U+sip" "!^.*$!sip:office at
enum.at!" .
; all extensions:
*.6.6.1.4.6.5.0.5.1.3.4.e164.arpa. NAPTR 10 10 "u"
"E2U+sip" "!^\\
+4315056416(.*)$!sip:extension-\\1 at
enum.at!" .
This maps
+43 1 5056416 XY to sip:extension-XY at
enum.at
[The use of wildcards in the DNS is quite controversal, our experience
with open numbering plans tells us that you can't avoid them, though.]
=============================================================================
I will try tomorrow to resolve the issue , if i will success i will
post a code update
Best Regards
Yulian Oifa