Hello,
As you will see I have merged my branch back into master.
These changes add a new event route [tm:branch-failure] to the tm module
which is run when any failure response is received on a transaction.
The event_route uses a new route type BRANCH_ROUTE which limits the
functions that can be run in the route.
The functions t_check_status(), t_next_contact_flow(), t_relay() and
unregister() can be used in this route.
A new pv $T_reply_ruid is accessible in this route which can be used to
unregister a single contact entry.
The following example route can be used on a registrar to handle failed
or invalid flows:
event_route[tm:branch-failure] {
xlog("L_INFO", "event_route[tm:branch-failure]\n");
if (t_check_status("430|403")) {
if (!unregister("location", "$tu", "$T_reply_ruid"))
{
xlog("L_WARN", "failed to unregister $tu with
ruid $T_reply_ruid\n");
}
if (!t_next_contact_flow())
{
xlog("L_INFO", "No more flows\n");
}
else
{
xlog("L_INFO", "Next flow\n");
t_relay();
}
}
}
Any bugs, memory leaks etc. let me know!
Hugh
--
Hugh Waite
Principal Design Engineer
Crocodile RCS Ltd.
Hi,
I am trying to use t_suspend()/t_continue() multiple times on the same
transaction. Calling t_suspend() more than once works, but the second
time I call t_continue() the transaction is killed and a 500 response is
sent. It is the "if (branch == t->nr_of_outgoings)" check from the code
fragment below (from t_suspend.c:t_continue()) that results in the
transaction being killed - you can see the debug/error line I added to
determine this in the fragment.
Is using t_suspend()/t_continue() multiple times something that should
work?
Thanks,
Peter
if (t->uas.status < 200) {
/* No final reply has been sent yet.
* Check whether or not there is any pending branch.
*/
for ( branch = 0;
branch < t->nr_of_outgoings;
branch++
) {
if ((t->uac[branch].request.buffer != NULL)
&& (t->uac[branch].last_received < 200)
)
break;
}
if (branch == t->nr_of_outgoings) {
/* There is not any open branch so there is
* no chance that a final response will be
received. */
ret = 0;
LM_ERR("branch == t->nr_of_outgoings\n");
goto kill_trans;
}
}
--
Peter Dunkley
Technical Director
Crocodile RCS Ltd
Hi, the new RFC 6665 mandates that the subscription dialog is made
*after* the first NOTIFY from the UAS (rather than after the 200 to
the initial SUBSCRIBE). This means that the UAC MUST take the route
set from the *first* received NOTIFY (instead of taking it from the
200 to the initial SUBSCRIBE).
Therefore a proxy compliant with RFC 6665 MUST always add RR to
in-dialog NOTIFY requests and thus, I propose that the default SR
script file implements it.
Regards.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>
Hi,
The Flowroute development team is pleased to announce a complete
overhaul of the json and jsonrpc-c modules, originally authored two
years ago.
Credit should first and foremost go to Joe Hillenbrand who did most of
the new development. Jordan Levy (our CTO) and I were also involved in
the updates and QA to a lesser extent.
The updated modules are available in the mgw/json branch.
In addition to the Kamailio modules, we have developed a Twisted
Python library to complement the jsonrpc-c module:
https://github.com/flowroute/txjason
We would be interested in any critiques of the API, documentation, and
code. Please let us know if you use these modules and especially if
you find any bugs.
We hope to merge this into master once we have had it in production
for awhile and (ideally) have received some feedback from other users.
Feel free to contact either Joe (joe(a)flowroute.com) or me directly
with any questions or comments.
--
Matthew Williams
Flowroute LLC
http://www.flowroute.com/
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
A new Flyspray task has been opened. Details are below.
User who did this - Kevin Scott Adams (TheGrandWazoo)
Attached to Project - sip-router
Summary - SCA - Primary line appearance hangs when secondary is picked up.
Task Type - Bug Report
Category - Module
Status - Unconfirmed
Assigned To -
Operating System - Linux
Severity - Medium
Priority - Normal
Reported Version - 4.0
Due in Version - Undecided
Due Date - Undecided
Details - Using Polycom 650's with SIP Firmware 3.3.5 or 4.0.4 and Kamailio 4.0.2 the following happens..
If you have two line appearances with 1 call each and you select the 2nd appearance the 1st appearance on both phones will illuminate. When you hangup the second appearance the first will stay in a 'seized' state on both phones.
Using the kamcmd sca.release_appearance will clear 'seized' line.
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=329
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.