THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Federico Cabiddu (lester)
Attached to Project - sip-router
Summary - bugs in uac_redirect module
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Low
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - Hi,
working with kamailio 4.0.2 and uac_redirect module I found several problems.
I have a script with two failure routes each calling get_redirects("MAX", "REASON"): when the 2nd of those routes is executed kamailio crashes in acc module (in acc_log_request function).
Digging the problem I found that the function get_redirect_fixup, for the second call, exits before setting the acc_param. This causes the acc module to crash: the function which crashes is acc_log_request (acc.c: 244, maybe it would be worth adding a null pointer check before calling memcpy).
The 2nd problem is related to the uac_redirect "acc_db_table" parameter: there is no fixup of the parameter so, when uac_redirect calls acc_db_request, the table ens up with a totally wrong name.
The 3rd problem is in acc module, in acc_db_set_table_name function: even if env_set_text set the s and the len component all the following operations on the table name are done using the s part. This brings a problem when acc_db_request is called with table names which have different length. The solution I found for this problem is (quite rough, I admit) to put a '\0' at the end of the table name.
And last, the accounting records generated by get_redirects don't contain the error code: in this case I just added to get_redirect the code to put the reply code into the acc_param struct.
I attach two patches against release 4.0.2.
Best regards,
Federico Cabiddu
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=327
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.
in a setup where presence server is behind sip proxy and sip proxy is
restarted, notifys from presence server to tcp watchers stop working.
what would it take for presence server to remove an active watcher if it
gets an 4xx response from sip proxy to the notify it sent to the
watcher?
-- juha
Hello,
I am pleased to announce a new developer for the Kamailio project: Lucian
Balaceanu. Lucian works in our 1&1 office in Bucharest and is for some years
with us in the company. He worked on several internal projects with our
Kamailio stack and will contribute some fixes to the sipcapture and
carrierroute module. He will also probably commit some other smaller fixes from
time to time.
Welcome Lucian and all the best,
Henning
i'm returning to this old thread where peter wrote:
The way to get this working is:
1) Use Git master so that unregister() with ruid is supported
2) Modify save() so that upon successful creation of new contact it copies
the ruid created by usrloc into the sip_msg.ruid variable for the current
SIP message. This means that on return from save() the $ruid PV will
work.
...
and
Actually save() can store the ruid in an xavp, one has to set
the module parameter:
http://kamailio.org/docs/modules/stable/modules/registrar.html#idp1752184
my understanding is that a single register request may contain more than
one contact and if so, several ruids would be generated, one per
contact. if so, what would $ruid contain after save()?
regarding xavp_rcd, after reading registrar module code, it seems that
it is only set upon lookup(), not upon save().
-- juha