with presence, auth, textdb activated.
The scenario is that Kamailio receives a SUBSCRIBE,
sends 200ok then a NOTIFY. (like it should do)
The problem is what when I kill kamailio and run it
again, it gives me this error:
0(30580) ERROR: db_text [dbt_tb.c:474]:
dbt_table_check_row(): null value not allowed - field
17
0(30580) DEBUG: db_text [dbt_file.c:480]:
dbt_load_file(): error at row=1 col=26 c=1
0(30580) ERROR: db_text [dbt_lib.c:307]:
dbt_db_get_table(): could not load database from file
[active_watchers] 0(30580) ERROR: db_text
[dbt_base.c:460]: dbt_delete(): failed to load table
<active_watchers>!
The field with null values is record_route, so if I put
some value I manage to run kamailio.
my conf, maybe I missed some field?
#!define DBURL "text:///etc/kamailio/dbtext"
#!ifdef WITH_PRESENCE
modparam("presence", "db_url", DBURL)
modparam("presence", "max_expires", 3600)
modparam("presence", "server_address", "sip:
10.0.37.1:5060"
)
modparam("pua_reginfo", "default_domain", "10.0.37.1")
modparam("pua_reginfo", "server_address",
"sip:10.0.37.1")
modparam("pua_reginfo", "outbound_proxy",
"sip:10.0.37.1")
modparam("pua_reginfo", "publish_reginfo", 1)
modparam("pua", "db_mode", 2)
modparam("pua", "hash_size", 11)
modparam("pua", "db_url", DBURL)
modparam("pua", "db_table", "pua")
modparam("pua", "min_expires", 0)
modparam("pua", "default_expires", 3600)
modparam("pua", "update_period", 1000)
modparam("pua", "dlginfo_increase_version", 1)
modparam("pua", "reginfo_increase_version", 1)
modparam("pua", "check_remote_contact", 0)
modparam("pua", "fetch_rows", 1000)
modparam("presence_xml", "db_url", DBURL)
modparam("presence_xml", "force_active", 1)
#!endif
Or as a workaround, can I reset the active_watchers table
every time I start kamailio? because kamdbctl
create/drop/init wipes all the other tables...