On Mon, 21 May 2007, Steve Underwood wrote:
> That might fix his problem, but why did he got garbage in the strings.
> Surely they should be set to something clean.
Yes, I think it's unrelated to the zaptel patch - I think it's just not
setting the CLID strings when it doesn't have a CLID.
On a slightly unrelated note, I think I found some kind of race condition
with the ENUM code. Accessing several ENUM records for the same lookup:
GET VARIABLE ENUMLOOKUP(+123456789|ALL|1|e164.org)
GET VARIABLE ENUMLOOKUP(+123456789|ALL|2|e164.org)
GET VARIABLE ENUMLOOKUP(+123456789|ALL|3|e164.org)
These all return the same URI, even though the number it's looking up has
several records. If I do this instead then it correctly returns several
different records:
GET VARIABLE ENUMLOOKUP(+123456789|ALL|1|e164.org)
GET VARIABLE ENUMLOOKUP(+123456789|ALL|c|e164.org)
GET VARIABLE ENUMLOOKUP(+123456789|ALL|2|e164.org)
GET VARIABLE ENUMLOOKUP(+123456789|ALL|c|e164.org)
GET VARIABLE ENUMLOOKUP(+123456789|ALL|3|e164.org)
I presume that this is timing related, and adding the extra ENUMLOOKUP
calls (asking for record 'c') causes it to delay enough for the bug to
disappear.
It's also worth noting that using "ALL" in the lookup causes it to return
the results in standard URI format such as "sip:[EMAIL PROTECTED]" instead of a
format that can be handed directly to the Dial command
("sip/[EMAIL PROTECTED]"), so you have to replace the first ":" with a "/"
yourself before using the result.
--
- Steve
xmpp:[EMAIL PROTECTED] sip:[EMAIL PROTECTED] http://www.nexusuk.org/
Servatis a periculum, servatis a maleficum - Whisper, Evanescence
_______________________________________________
Callweaver-users mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-users
