I have not been able to tesr yet, but it may be that the htable entries that were added in event route disapeared because of htable reload. If so, it Would be nice if enent route would be re-run or if it would be possible to prevent reload affecting entries that do not originate from db.

Juha

Hello,

I looked at the code and no change for deleting auto-expired items -- there is a condition in time function ht_timer() from ht_api.c:

    if(ht->htexpire>0)

Which is "scan for expired items only if the hash table definition has auto expire".

Can you do:

kamcmd htable.listTables

and see if the entry htable is showing an expires value different than 0?

Cheers, Daniel

On 06/10/15 10:57, Juha Heinanen wrote:

...

i noticed that entries that i had added to htable at sip proxy start in event_route [htable:mod-init], e.g.,

$sht(htable=>app_srv::sbc::<null>) = "sip:SBC:SEMS_PORT";

had disappeared from htable after some (don't know exactly how long) time. i have not specified any autoexpire for that table:

modparam("htable", "htable", "htable=>size=HTABLE_SIZE;dbtable=htable;")

after restart of sip proxy they reappeared in htable like this:

# sip-proxy_ctl htable.get htable 'app_srv::sbc::<null>' { item: { name: app_srv::sbc::<null> value: sip:127.0.0.1:5090 flags: 2 expire: NEVER } }

what could explain the disappearance?

-- juha

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Book: SIP Routing With Kamailio - http://www.asipto.com Kamailio Advanced Training, Sep 28-30, 2015, in Berlin - http://asipto.com/u/kat

---

SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-usersp%3E