THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A user has added themself to the list of users assigned to this task.
FS#97 - pooling of libsrdb1 doesnt restrict database connection to 1 thread and gives issues with postgresql
User who did this - Robert Verspuy (exarv)
http://sip-router.org/tracker/index.php?do=details&task_id=97
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 new Flyspray task has been opened. Details are below.
User who did this - Robert Verspuy (exarv)
Attached to Project - sip-router
Summary - pooling of libsrdb1 doesnt restrict database connection to 1 thread and gives issues with postgresql
Task Type - Bug Report
Category - libsrdb1 (kamailio)
Status - Assigned
Assigned To - Henning Westerholt
Operating System - Linux
Severity - High
Priority - Normal
Reported Version - 3.1
Due in Version - Undecided
Due Date - Undecided
Details - In the source lib/srdb1/* some kind of pooling is used.
When kamailio needs a database connection, the cmp_db_id function checks to see if there is already a database connection with the exact same params (username, database, server etc..).
According to the PQ library every proces / thread should have it's own database connection.
The db_postgres is setup to use asynchronous I/O with the PQ library.
So when two threads are using the same database connection it is possible that,
the resultset from a query of thread A is returned to thread B.
The cmp_db_id function in lib/srdb1/db_id.c does _not_ check the PID.
I've created a small patch to fix the problems mentioned above.
The changes are made in lib/srdb1/* files
So if you apply them, it will be active for _every_ database module.
Maybe it's not needed for the mysql database,
but I *assume* it will not break when used on a mysql database. (not tested)
Maybe you will get a bit more database connections, but that depends on
which modules you're using.
What did I do:
* Added pid to the db_id struct.
* During initialization the pid is saved into the db_id struct.
* In cmp_db_id the pid is also checked when searching for a database
connection to be reused.
See complete thread on http://lists.sip-router.org/pipermail/sr-dev/2010-October/009689.html
One or more files have been attached.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=97
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 new Flyspray task has been opened. Details are below.
User who did this - Marc Cardinal (mcardinal)
Attached to Project - sip-router
Summary - Documentation change for drouting module
Task Type - Improvement
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - All
Severity - Low
Priority - Normal
Reported Version - 3.1
Due in Version - Undecided
Due Date - Undecided
Details - I noticed that the documentation at http://www.kamailio.org/docs/modules/stable/modules_k/drouting.html is missing some key information on using the gw_list table. The paragraph f. under the section 1.4.3 currently reads:
f. gwlist column
A comma separated list of gateway identifiers corresponding to a row in table "dr_gateways". The first gateway is tried first and if failure the second one, and so one. If no gateway is left a negative response is sent back to the user.
The following key information should be added:
You can use a predefined list from the table "dr_gw_lists" preceded by the character "#".
I confirmed that this is supported by the current version of drouting by looking at the source code. The # appears to be parsed at the block of code starting at line 535 of modules_k/drouting/dr_load.c:
/* is gw_list a list or a list id? */
if (str_vals[4][0]=='#') {
s_id.s = str_vals[4]+1;
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=96
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#96 - Documentation change for drouting module
User who did this - Marc Cardinal (mcardinal)
http://sip-router.org/tracker/index.php?do=details&task_id=96
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 new Flyspray task has been opened. Details are below.
User who did this - Marc Cardinal (mcardinal)
Attached to Project - sip-router
Summary - SipTrace causing Kamailio not to start
Task Type - Bug Report
Category - Core
Status - Assigned
Assigned To - Andrei Pelinescu-Onciul
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - 3.1
Due in Version - Undecided
Due Date - Undecided
Details - I have installed Kamailio 3.1.0 from repository on a fresh install of Ubuntu 10.04 LTS (Linux test 2.6.32-21-generic-pae #32-Ubuntu SMP Fri Apr 16 09:39:35 UTC 2010 i686 GNU/Linux).
I added the following lines to the stock /etc/kamailio/kamailio.cfg file:
#!define WITH_SIPTRACE
#!ifdef WITH_SIPTRACE
loadmodule "siptrace.so"
#!endif
#!ifdef WITH_SIPTRACE
# ----- siptrace params -----
modparam("siptrace", "db_url", DBURL)
modparam("siptrace", "table", "sip_trace")
modparam("siptrace", "trace_flag", 22)
modparam("siptrace", "traced_user_avp", "$avp(s:traced_user)")
#!endif
Then when I try starting kamailio using: /etc/init.d/kamailio debug
I get the following:
[...]
0(24712) DEBUG: <core> [sr_module.c:871]: DEBUG: init_mod: rtpproxy
0(24712) DEBUG: rtpproxy [rtpproxy.c:531]: url is udp:127.0.0.1:7722, len is 18
0(24712) DEBUG: <core> [sr_module.c:871]: DEBUG: init_mod: siptrace
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <db_bind_api> in module db_mysql [/usr/lib/kamailio/modules/db_mysql.so]
0(24712) DEBUG: <core> [db.c:202]: using db bind api for db_mysql
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <load_tm> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_newtran> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_relay_to_tcp> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_relay_to_udp> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_relay> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_forward_nonack> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <t_release> in module tm [/usr/lib/kamailio/modules/tm.so]
0(24712) DEBUG: <core> [sr_module.c:625]: find_export_record: found <bind_sl> in module sl [/usr/lib/kamailio/modules/sl.so]
0(24710) ERROR: <core> [daemonize.c:269]: Main process exited before writing to pipe
already running.
root@test:/#
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=95
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#95 - SipTrace causing Kamailio not to start
User who did this - Marc Cardinal (mcardinal)
http://sip-router.org/tracker/index.php?do=details&task_id=95
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.
Module: sip-router
Branch: kamailio_3.0
Commit: 691f990e1387c75b10a56bdb1f9c7841970efcc8
URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commit;h=691f990…
Author: Jon Bonilla <manwe(a)aholab.ehu.es>
Committer: Jon Bonilla <manwe(a)aholab.ehu.es>
Date: Thu Oct 21 09:36:42 2010 +0200
pkg debian
changelog updates for 3.0.4 release. This is not really a debian compliant changelog and it does not grant credits to developers.
TODO: Use this changelog for versioning but install the full changelog under / when installing debian packages.
---
pkg/kamailio/deb/debian/changelog | 70 ++++++++++++++----------------------
pkg/kamailio/deb/etch/changelog | 68 +++++++++++++++--------------------
pkg/kamailio/deb/lenny/changelog | 68 +++++++++++++++--------------------
pkg/kamailio/deb/lucid/changelog | 68 +++++++++++++++--------------------
pkg/kamailio/deb/squeeze/changelog | 68 +++++++++++++++--------------------
5 files changed, 143 insertions(+), 199 deletions(-)
Diff: http://git.sip-router.org/cgi-bin/gitweb.cgi/sip-router/?a=commitdiff;h=691…
Hello,
Kamailio (OpenSER) v3.0.4 is released. This is a maintenance release of
previous stable branch, 3.0.x, that includes fixes since release of
v3.0.3. There is no change to database or configuration file required to
upgrade to 3.0.4 from any 3.0.x version.
For more details about version 3.0.4, visit:
http://www.kamailio.org/w/2010/10/kamailio-v3-0-4-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
Hello,
Kamailio (OpenSER) version 1.5.5 is released. This is a maintenance
release of branch 1.5, the last in its series.
The project is officially maintaining the latest two stable branches,
these being now 3.0.x and 3.1.x. As it happened in the past, fixes can
still get into SVN branch 1.5, but there is no plan to package another
version 1.5.x.
If you still run 1.5.x, it is highly recommended that you start to plan
the migration to 3.x versions.
For more details about version 1.5.5, visit:
http://www.kamailio.org/w/2010/10/kamailio-v1-5-5-released/
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com