From miconda@gmail.com Mon Nov 21 11:34:07 2022 From: Daniel-Constantin Mierla To: sr-users@lists.kamailio.org Subject: Re: [SR-Users] Problem with update/retrigger a htable Date: Mon, 21 Nov 2022 11:34:02 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0422068600==" --===============0422068600== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Hello, check the docs of the module, there is a modparam to set the timer interval, which by default is 20 secods. Then, to troubleshoot, run with debug=3 and watch the log messages for hints of what happens. Also, dump the htable via rpc to see its content. Cheers, Daniel On 21.11.22 08:50, Bernd Krueger-Knauber wrote: > Hi members, > > I run into a problemm with htable. > For user push notifications I need a loop. > > So I did the following for a first test: > > modparam("htable", "htable", "user=>size=3;autoexpire=5") > > ... > > > event_route[htable:mod-init] { >     xinfo("htable init"); >     $sht(user=>testkey) = "testvalue"; > } > > event_route[htable:expired:user] { >     xinfo("Record expired $shtrecord(key) => $shtrecord(value)"); >     $sht(user=>$shtrecord(key)) = $shtrecord(value); > } > > > I see the htable init, and I reach Record expired, but only once. > The 'new' entry > $sht(user=>$shtrecord(key)) = $shtrecord(value); > seams not to be re-added, because I never reach the expired event again. > > I expected to see cyclic expired events. > Also strange: > expire is set to 5 seconds I get: > > Nov 21 08:34:50 xxx /usr/sbin/kamailio[254662]: INFO: