Actually it is the underscore. When I look at the logs I think we can see a problem:
- When using a htable name without underscore myTable1: _modparam("htable","htable","myTable1=>size=1024;autoexpire=86400");_ and _event_route[htable:expired:myTable1] { ...}_ I get the following logs at starting time: **Oct 6 13:48:16 torso1 kamailio-0[14834]: DEBUG: htable [ht_api.c:360]: ht_init_tables(): initializing htable [myTable1] with nr. of slots: 1024 Oct 6 13:48:16 torso1 kamailio-0[14834]: DEBUG: htable [ht_api.c:375]: ht_init_tables(): event route for expired items in [myTable1] exists**
- When using a hatable with an underscore my_table_1: _modparam("htable","htable","my_table_1=>size=1024;autoexpire=86400");_ and _event_route[htable:expired:] { ...}_ **Oct 6 13:51:20 torso1 kamailio-0[16020]: DEBUG: <core> [route.c:129]: route_add(): mapping routing block (0xb01140)[htable:expired:my_table_1] to 15 Oct 6 13:51:20 torso1 kamailio-0[16020]: DEBUG: htable [ht_api.c:372]: ht_init_tables(): event route for expired items in [my_table_1] does not exist**