[SR-Users] Final reply code is wrong in case of 302 and 486 busy
Marco Capetta
mcapetta at sipwise.com
Wed Aug 1 17:46:38 CEST 2018
Hello,
we have a problem of final reply code in case of 302 and then 486 busy.
This is our scenario:
A, B and C are subscribers.
A ----------> Kamailio ----------> B
Kamailio <---302---- B
Kamailio -----------------------> C
Kamailio <---486----------------- C
A <---302---- Kamailio
Expected behavior: Kamailio should reply to A with 486, as C was busy,
and not 302.
We have kamailio v5.1.4
In the call to B we set both failure and branch_failure:
t_on_failure("failure_route");
t_on_branch_failure("failure_redirect");
in order to handle the 302 redirect per branch with:
event_route[tm:branch-failure:failure_redirect]
{
if($T_reply_code == 301 || $T_reply_code == 302)
{
do redirect ...
}
}
and the final failure with:
failure_route[FAILURE_ROUTE_LOCAL]
{
do something ...
}
Since we have 'modparam("tm", "failure_reply_mode", 3)' my expectation
is to get the winning reply from the branch of last step.
Is there any configuration I'm missing?
Since we manage the redirect with a branch-failure, is the winning reply
calculated in a different way?
Thanks
Marco
More information about the sr-users
mailing list