THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Nick Altmann (nikbyte)
Attached to Project - sip-router
Summary - Kamailio hangs on start after dialog module reads variables from database
Task Type - Bug Report
Category - dialog
Status - Assigned
Assigned To - Timo Reimann
Operating System - Linux
Severity - Critical
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - Trying to use with postgresql. In db_mode > 0 kamailio cannot start if there are any records in table dialog_vars.
In debug:
Nov 5 00:44:20 DEBUG: db_postgres [km_dbase.c:158]: sending query ok: 0x7f40b4c5a4e0 (7) - [select table_version from version where table_name='dialog']
Nov 5 00:44:20 DEBUG: db_postgres [km_dbase.c:158]: sending query ok: 0x7f40b4c5a4e0 (7) - [select table_version from version where table_name='dialog_vars']
Nov 5 00:44:20 DEBUG: db_postgres [km_dbase.c:158]: sending query ok: 0x7f40b4c5a4e0 (7) - [select hash_entry,hash_id,callid,from_uri,from_tag,to_uri,to_tag,start_time,state,timeout,caller_cseq,callee_cseq,caller_route_set,callee_route_set,caller_contact,callee_contact,caller_sock,callee_sock,sflags,toroute_name,req_uri from dialog ]
Nov 5 00:44:20 DEBUG: dialog [dlg_db_handler.c:310]: the database has information about 1 dialogs
Nov 5 00:44:20 DEBUG: dialog [dlg_hash.c:307]: new dialog on hash 3723
Nov 5 00:44:20 DEBUG: dialog [dlg_hash.c:559]: ref dlg 0x7f40b2409878 with 1 -> 1
Nov 5 00:44:20 DEBUG: dialog [dlg_timer.c:115]: inserting 0x7f40b24098c8 for 133873706
Nov 5 00:44:20 DEBUG: dialog [dlg_hash.c:579]: ref dlg 0x7f40b2409878 with 1 -> 2
Nov 5 00:44:20 DEBUG: dialog [dlg_db_handler.c:417]: current dialog timeout is 133873706
Nov 5 00:44:20 DEBUG: db_postgres [km_dbase.c:158]: sending query ok: 0x7f40b4c5a4e0 (7) - [select hash_entry,hash_id,dialog_key,dialog_value from dialog_vars ]
Nov 5 00:44:20 DEBUG: db_postgres [km_res.c:133]: RES_NAMES(0x7f40b4c5b028)[2]=[dialog_key]
Nov 5 00:44:20 DEBUG: db_postgres [km_res.c:133]: RES_NAMES(0x7f40b4c5afb8)[3]=[dialog_value]
Nov 5 00:44:20 DEBUG: db_postgres [km_res.c:252]: [0][2] Column[dialog_key]=[rtpproxy]
Nov 5 00:44:20 DEBUG: db_postgres [km_res.c:252]: [0][3] Column[dialog_value]=[yes]
Nov 5 00:44:20 DEBUG: dialog [dlg_db_handler.c:502]: the database has information about 1 dialog variables
After start kamailio hangs. If I delete records in dialog_vars, kamailio starts ok.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=171
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#171 - Kamailio hangs on start after dialog module reads variables from database
User who did this - Nick Altmann (nikbyte)
http://sip-router.org/tracker/index.php?do=details&task_id=171
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
Hi,
outgoing CANCEL is not in sip trace even if setflag(22) and sip_trace is
used. I saw that there was some issue relating to
http://lists.sip-router.org/pipermail/sr-dev/2011-September/012793.html ,
but I have the nightly build installed - compiled on 07:10:51 Nov 4 2011
with gcc 4.6.1 and there is still the problem.
Mino
Hi all,
I wanted to ask the community what the best way forward is for
incorporating new SIP (IMS specific) headers into Kamailio. Right now I see
two ways:
1. incorporating into existing parser framework in Kamailio
2. Leave it up to individual modules to independently parse for appropriate
IMS headers.
I would think 1 would be the best option?
Here are some examples of the extension headers:
http://docs.redhat.com/docs/en-US/JBoss_Communications_Platform/5.0/html/SI…
Cheers
Jason