THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#362 - send_reply() bug when called from branch route
User who did this - Juha Heinanen (jh)
----------
for example, the some security violation is detected in the branch that would result in terminating the whole call. my original point, however, was that readme claims that send_reply() can be called from BRANCH_ROUTE, which currently results in error.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=362#comment1158
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#361 - Unmet dependency for kamailio-perl-modules
User who did this - Daniel-Constantin Mierla (miconda)
----------
It looks like the constraint is to have libperl greater than 5.10. Perhaps something wrong in the control file. I'll check
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=361#comment1157
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#362 - send_reply() bug when called from branch route
User who did this - Daniel-Constantin Mierla (miconda)
----------
send_reply() is just a wrapper, calls t_reply() if transaction was created and sl_send_reply() when there is no transaction yet. For branch route, it applies the rules of t_reply(). Probably the readme is wrong.
What would be a reason to send a reply in branch route? Typically that should end the entire transaction.
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=362#comment1156
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 - Juha Heinanen (jh)
Attached to Project - sip-router
Summary - send_reply() bug when called from branch route
Task Type - Bug Report
Category - Module
Status - New
Assigned To -
Operating System - All
Severity - Medium
Priority - Normal
Reported Version - Development
Due in Version - Undecided
Due Date - Undecided
Details - i think this is still unresolved:
according to sl readme, send_reply() can be called from branch route.
however, when i tried with recent master i got:
Oct 14 08:47:34 rautu /usr/sbin/sip-proxy[11203]: : tm [tm.c:1342]: w_t_reply(): BUG: w_t_reply entered in unsupported mode
Oct 14 08:47:34 rautu /usr/sbin/sip-proxy[11203]: ERROR: sl [sl.c:277]: send_reply(): failed to reply stateful (tm)
is this a bug in code or readme?
-- juha
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#360 - Dialog callback on pua_dialoginfo after restart
User who did this - Kristian Høgh (kfhdk)
----------
Hi Daniel,
I took a look at it, but I am out of my comfort zone. Hope this is better.
After second patch, existing dialogs are loaded after restart.
If not using use_pubruri_avps, in-dialog (including BYE) publish are sent.
If using use_pubruri_avps, the values are lost, so we have to store the values in database.
That is what the third patch does, and I agree it is a feature.
It also restores the values after restart.
I tried to use dlg_var in script to set pubruri_avps instead of third patch, but the in-dialog callback is run right after loose_route.
----------
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=360#comment1155
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#360 - Dialog callback on pua_dialoginfo after restart
User who did this - Daniel-Constantin Mierla (miconda)
----------
Thanks.
First patch was applied.
Second patch doesn't seem that it handles error cases, it returns NULL and dlginfo variable is lost - it was allocated in shared memory. The code seems to be like that from older versions, but it would be good to get fixed. Do you have time for it? If not, probably I will get back to it later when I get some spare time.
Third patch - does it have relevance in the context of reported issue? It seems a feature enhancement. If yes, it will be pushed as we unfreeze from testing phase for v4.1
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=360#comment1154
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.