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
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev
