All,
This is just a placeholder for issue we're facing in our deployment of Kamailio IMS core : client uses TCP to send REGISTER. Occasionally client crashes/lost connection so new REGISTER is sent towards P-CSCF. Instead of removing old registration (there is no way to match these obviously) P-CSCF will create new entry and keeps this information for future use. Once SIP request is sent out to the contact, P-CSCF uses all registration entries in the memory and forks requests to all destinations (which are in most cases unreachable). This creates flood of timeouts from S-CSCF towards AS and sometimes bad timing is even causing calls not being processed since 408 Request Timeout is delivered sooner than 200 OK. I'm pretty sure Carsten is aware about this issue that's why this note at very beginning about "placeholder"
thank you
Dan.
--
Daniel Ciprus
Integration engineer
http://www.acision.com
9954 Mayland Dr
Suite 3100
Richmond, VA 23233
USA
T: +1 804 762 5601
E: daniel.ciprus(a)acision.com<mailto:daniel.ciprus@acision.com>
________________________________
This e-mail and any attachment is for authorised use by the intended recipient(s) only. It may contain proprietary material, confidential information and/or be subject to legal privilege. It should not be copied, disclosed to, retained or used by, any other party. If you are not an intended recipient then please promptly delete this e-mail and any attachment and all copies and inform the sender. Thank you for understanding.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#413 - RPATH contains illegal absolute entry
User who did this - Eugene Prokopiev (enp)
----------
build log
----------
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=413#comment1355
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 - Eugene Prokopiev (enp)
Attached to Project - sip-router
Summary - RPATH contains illegal absolute entry
Task Type - Bug Report
Category - Core
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - 4.1
Due in Version - Undecided
Due Date - Undecided
Details - I got following errors while compiling Kamailio 4.1.2 from git:
verify-elf: ERROR: ./usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/modules/nathelper.so: RPATH contains illegal absolute entry "/usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/": /usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/
verify-elf: ERROR: ./usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/modules/nathelper.so: RPATH contains illegal entry "/usr/src/tmp/kamailio-buildroot": /usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/
verify-elf: ERROR: ./usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/modules/group.so: RPATH contains illegal absolute entry "/usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/": /usr/src/tmp/kamailio-buildroot/usr/lib64/kamailio/
...
Full build log is attached. RPATH related problems are described in http://fedoraproject.org/wiki/Packaging:Guidelines#Beware_of_Rpath and https://wiki.debian.org/RpathIssue. Is it possible to fix it?
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=413
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.
The following task has a new comment added:
FS#410 - textops: add functions to convert and append multipart bodies.
User who did this - Víctor Seva (linuxmaniac)
----------
Well, it crashes at msg_translation.c:replace_body when I try to delete the old body lump.
But, as you can see on the output(k.log), this is called twice. The first execution is OK. I see the right message sent, but it is executed a second time for the retransmission, getting the crash at delete_lump.
It seems I'm doing something wrong when I try to replace the body part.
I'm using invite03-multipar.sip message with protoshoot for testing.
----------
One or more files have been attached.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=410#comment1354
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.
The following task has a new comment added:
FS#410 - textops: add functions to convert and append multipart bodies.
User who did this - Daniel-Constantin Mierla (miconda)
----------
look at backtrace to see where it crashes
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=410#comment1353
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.
The following task has a new comment added:
FS#410 - textops: add functions to convert and append multipart bodies.
User who did this - Víctor Seva (linuxmaniac)
----------
missed unset the new flag. But now it crashes if retransmission.
am I doing something really wrong?
----------
One or more files have been attached.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=410#comment1352
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.