[asterisk-dev] DUNDI expiration

[Dmitry Andrianov]

Hello.

Does anyone has an idea why DUNDi code adjusts timeouts from the configuration in the following way:

        /* Keep pushes a little longer, cut pulls a little short */
        if (push)
                expiration += 10;
        else
                expiration -= 10;
        if (expiration < 1)
                expiration = 1;

?
The end result is that if you take sample configuration (from well-known "JR_Richardson_Whitepaper.pdf" for example) where cachetime is set to 5 seconds, the effective timeout will be 1 second. Interesting is that "dundi lookup" CLI command still says "expires in 5 s" when displaying result which is not true because two successive lookups query the remote peer no matter the fact only two seconds passed.

What is the reason for that?

Regards,
Dmitry Andrianov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-dev/attachments/20071210/a38835da/attachment.htm