Ladies & Gentlemen,
I was recently given the Kamailio Pacemaker RA script as posted in:
http://lists.sip-router.org/pipermail/sr-dev/2014-January/022639.html
Via the Pacemaker mailing list.
I wanted to inquire if anyone else has had issues with monitoring
portion of the script. I have manually verified that the sipsak command
does in fact work from the command line as the user that pacemaker is
running as, but for some reason I am not seeing the monitoring command
being run.
I added the appropriate portion of call routing code to the configuration:
if (is_method("OPTIONS") && ($ru=~"sip:monitor@.*")) {
xlog("L_INFO", "Kamailio Monitoring Request");
sl_send_reply("200", "Kamailio is alive");
exit;
}
Unfortunately, when I parse my logs, I never see the log entry, nor do I
see any entry in syslog about kamailio monitoring being performed (even
though I see MySQL and everything being tested)
Furthermore, when I kill the kamailio process, Pacemaker does not
"notice" this happening and continues on as if Kamailio is running properly.
Has anyone else used this script (I'm on Ubuntu 12.04 LTS 64bit, and
adapted the RA script to specifically run /bin/bash due to Ubuntu using
/bin/dash) and run into this issue?
Thank you,
Sherwood McGowan
VOIP Solutions Consultant
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#362 - send_reply() bug when called from branch route
User who did this - Daniel-Constantin Mierla (miconda)
Reason for closing: Fixed
Additional comments about closing: Readme was updated a while ago to reflect where send_reply() can be used.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=362
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#382 - dlg_end_dlg on a two-armed proxy only sends bye to one party
User who did this - Daniel-Constantin Mierla (miconda)
----------
Can you try with mhomed=1 in kamailio.cfg?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=382#comment1293
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.
I've noticed a problem with registrations on the pcscf when doing some
testing with sipp
If I send in a REGISTER with SIPP followed by an INVITE calls go through
my system no problem.
If I then stop the sipp script and run it again, I find that although
the registration succeeds, subsequent INVITES are rejected telling me
that I have not registered!
If I unregister at the end of my script everything is fine, and the
problem goes away after the original REGISTRATION times out, so this led
me to think that we had a problem with multiple registrations entries in
the system.
The problem seems to be a result of the fact that sipp always places the
same ip address and port number on the contact line when using tcp
connections.
I've had a look through the code and believe that we are getting
multiple entries in the usrloc hash table in this scenario, and
ul_get_pcontact only ever returns the first one which causes
pcscf_is_registered to incorrectly report that the UE is not registered.
Paul
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#380 - fixes for memory leak in TLS module
User who did this - Ding Ma (mading087)
----------
Reviewed the code and agreed with most of your changes:
- the removal of the history parts is fine
- using lock on the config updates is a lot better than locking around the loading of tls config file
However, think the lock around decrementing the reference count may be needed when the -- operation is not atomic.
Based on Intel document:
INC and DEC belong to the family of instructions that can read, modify, and write a data value in memory. Thus, their operation is not guaranteed to be atomic unless the LOCK prefix is used for these instructions (when referencing a location in memory). The XCHG instruction automatically causes the LOCK behavior to occur regardless of whether the prefix is used or not.
Here is an example of race condition for the ref_count decrement in tls_h_tcpconn_clean(). Assuming 2 threads are trying to tear down two connections, the correct way would be
thread1 (ref_count 2->1), then thread2 (ref_count 1->0)
But if thread2 reads the ref_count before thread1 writes, you'd get
thread1 (ref_count 2->1) and thread2 (ref_count 2->1). The result would be wrong, and could cause dangling memory block. Realistically, this would be a rare case, but can still happen.
Volatile just tells the compiler not to optimize the ref_count, won't guarantee atomicity. Think your suggestion of using atomic_t type and atomic ops for the ref_count is the absolute right fix. The potential issue with atomic_t is that it would cause some extra work when porting kamailio to non-linux or linux with older kernel. The other alternative would be to use lock around the ref_count decrement, which would have impact on performance when there are a large number of IP phones in the system.
If you agree with my assessment, I can take a shoot at changing the ref_count to atomic_t, and provide that as another patch on top of your changes. Or you can make this change and give me a patch, which I can test for you in a real system. let me know whichever way works for you.
If possible, wonder if it would be better to merge the current patch plus your changes to the stable main line. This would address the original memory leak issue for 99.9% of the cases. The atomic_t change can come later. Thanks.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=380#comment1292
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!
I would like to add cacert.org root certificates to the Kamailio distribution, so that every Kamailio server gets these as approved certificates by default with the default TLS settings.
Anyone having problems with doing that?
/O