<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title></title>
</head>
<body>
<div name="messageBodySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">I think you need to use
<div>t_on_branch_failure() </div>
<div>If I got you correctly</div>
</div>
<div name="messageSignatureSection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;"><br />
Regards, Igor</div>
<div name="messageReplySection" style="font-size: 14px; font-family: -apple-system, BlinkMacSystemFont, sans-serif;">On Sep 6, 2018, 10:06 PM +0300, Henning Westerholt <hw@kamailio.org>, wrote:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #1abc9c;">Am Mittwoch, 5. September 2018, 14:03:10 CEST schrieb Володимир Іванець:<br />
<blockquote type="cite" style="margin: 5px 5px; padding-left: 10px; border-left: thin solid #e67e22;">I wanted to ask those who know if Kamailio's behavior I'm facing is<br />
expected or I should make some improvements to the configuration. Kamailio<br />
version is 5.1.0.<br />
<br />
I have a route where RTPEngine parameters are being collected and<br />
*rtpengine_offer()* is called. After that *t_on_reply("REPLY_SIP_TO_SIP");*<br />
followed by the *t_on_failure("FAILURE_SIP_TO_SIP");* are used. The idea is<br />
to process all responces except 415 or 488 from UAC as usual in<br />
*onreply_route[REPLY_SIP_TO_SIP]* and use<br />
*failure_route[FAILURE_SIP_TO_SIP]* to update SDP with *rtpengine_offer()*<br />
if necessary.<br />
<br />
*onreply_route[REPLY_SIP_TO_SIP]* just goes to *exit;* if *$rs* equals 415<br />
or 488. This works fine with Htek phone which sends 100, 180 and then 488.<br />
But I can not see *failure_route[FAILURE_SIP_TO_SIP]* execution for calls<br />
to Zoiper which replies with 100 and immediately 415.<br />
<br />
t_on_failure(failure_route) documentation says: "Sets failure routing<br />
block, to which control is passed after a transaction completed with a<br />
negative result but before sending a final reply." and to be honest I don't<br />
really understand how lacking of responce prevents failure_route from<br />
executing.<br /></blockquote>
<br />
Hello,<br />
<br />
I did not understand you completely here. Did you receive a 415 and the<br />
failure route is not entered, or you did not receive a response as stated in<br />
the last sentence?<br />
<br />
If the failure_route is entered for the 488, then it should be also entered<br />
for the 415. I am not aware of a special handling of this code in tm. (Only<br />
that 415 is one of the replies that get a priority comparing to normal 4xx.)<br />
<br />
I would suggest to try with debugging enabled and compare the logs for a<br />
working, and for a non-working call. You could also try to concentrate on one<br />
problem first, like the failure_route topic, and then combining this with the<br />
reply_route.<br />
<br />
Best regards,<br />
<br />
Henning<br />
<br />
--<br />
Henning Westerholt<br />
https://skalatan.de/blog/<br />
<br />
_______________________________________________<br />
Kamailio (SER) - Users Mailing List<br />
sr-users@lists.kamailio.org<br />
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users<br /></blockquote>
</div>
</body>
</html>