Bogdan and team, This is on a 1.9 build from October 17, plus the recently committed change to the dialog table schema in dbtext.
Here's the scenario... After a fresh Opensips start, I place a call through it. A dialog is established. I stop Opensips after about five seconds and verify the contents of the dialog table file: dlg_id(bigint) callid(string) from_uri(string) from_tag(string) to_uri(string) to_tag(string) mangled_from_uri(string,null) mangled_to_uri(string,null) caller_cseq(string) callee_cseq(string) caller_ping_cseq(int) callee_ping_cseq(int) caller_route_set(string,null) callee_route_set(string,null) caller_contact(string) callee_contact(string) caller_sock(string) callee_sock(string) state(int) start_time(int) timeout(int) vars(string,null) profiles(string,null) script_flags(int) flags(int) 8672076440446:662bbb7a-8f52-4c26-adaa-6f2f5f870751:.....remaining fields for dialog record..... I again start Opensips. I see this in the log (debug=3): ERROR:dialog:load_dialog_info_from_db: column dlg_id cannot be null/has wrong type 6 -> skipping One interesting note, when Opensips starts the dlg_id column is defined with 'long'. After Opensips exits, it has 'bigint' type. I don't know if that's relevant. - Jeff
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
