7 maj 2008 kl. 04.34 skrev Brian J. Murrell:
> Does anyone have a better ENUM lookup handler than the built-in
> ENUMLOOKUP() function? The built-in function does not properly handle
> multiple return values such as:
>
> 8.9.9.3.2.8.8.6.6.8.1.e164.org has NAPTR record 200 10 "u" "E2U+SIP"
> "!^\\+1866(.*)$!sip:[EMAIL PROTECTED]" .
> 8.9.9.3.2.8.8.6.6.8.1.e164.org has NAPTR record 200 10 "u" "E2U+SIP"
> "!^\\+1866(.*)$!sip:[EMAIL PROTECTED]" .
>
> And thus does not handle roll-over should one be unavailable for
> whatever reason.
Quoting RFC 3824:
"Only one SIP URI, ideally, appears in an ENUM record set for a
telephone number. While it may initially seem attractive to
provide multiple SIP URIs that reach the same user within ENUM,
if
there are multiple addresses at which a user can be contacted,
considerably greater flexibility is afforded if multiple URIs are
managed by a SIP location service that is identified by a single
record in ENUM. Behavior for parallel and sequential forking in
SIP, for example, is better managed in SIP than in a set of ENUM
records."
There's a long section later on in this RFC about how to make it work
if you still want to have multiple SIP records...
We look forward to source code improvements!
/O
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
