Summary:ASTERISK-04408: [patch] "cachetime" option for dundi.conf, making the hard coded cache time adjustable.
Reporter:David Svanlund (svanlund)Labels:
Date Opened:2005-06-13 16:42:02Date Closed:2008-01-15 15:38:42.000-0600
Versions:Frequency of
Environment:Attachments:( 0) dundi_cache_time.diff
Description:This patch makes it possible to specify for how long a peer shall cache query responses. This is currently set to 3600 seconds, and can not be changed any other way than digging into the code.

The attached patch adds a "cachetime" option to dundi.conf. Unless set, the default value (as specified by DUNDI_DEFAULT_CACHE_TIME) will be used. pbx_dundi.c has been modified to accomplish this feature.

It also includes an update to the DUNDi sample configuration, dundi.conf.sample, to reflect this change.


For the record, I noticed that the first 10 seconds of the cache time seems to "disappear" immediatly. If I from server A query server B the response would say "... expires in 3600 s", and "... expires in 3590 s" on a second query immediatly aftewards. Same result on CVS HEAD from today, as well on a box running for several months. I haven't had time to figure out why it happens, and guess I should bring it up in another bug. I just wanted to mention it in case anyone notice when trying this patch.

Disclaimer faxed earlier today.
Comments:By: Kevin P. Fleming (kpfleming) 2005-06-20 20:57:56

Committed to CVS HEAD, thanks!

By: Digium Subversion (svnbot) 2008-01-15 15:38:42.000-0600

Repository: asterisk
Revision: 5946

U   trunk/configs/dundi.conf.sample
U   trunk/pbx/pbx_dundi.c

r5946 | kpfleming | 2008-01-15 15:38:41 -0600 (Tue, 15 Jan 2008) | 2 lines

make query cache time configurable (bug ASTERISK-4408)