[OpenSIPS-Users] Handling various CANCEL scenarios

[Bogdan-Andrei Iancu]

Hello Andreas,

The approach is good - still, for 480 or 487 you should not anything - a 
the default behavior of the failure route is to let the final reply to 
be routed back to the caller. You have to explicitly handle there the 
cases (based on reply code) when you want to re-route the call (create a 
new branch) to a new destination.

Best regards,

Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com

On 02/07/2017 04:03 PM, Andreas Bøckmann wrote:
> Hello everybody
>
> How can I separate different Reason headers to achieve a setup where 
> NO_ANSWER (480) ends the dialog (and sends CANCELs) while other 
> reasons like e.g. TM timeout leads to routing the requests to GW?
>
> Could this be handled in the failure route as something like below or 
> am I way off here?
>
>   if (t_check_status("480")) {
>      t_relay();
>      exit;
>   }
>
>   if (t_check_status("487")) {
>      t_relay();
>      exit;
>   }
>
>   if (t_check_status("404")) {
>      route_to_gw("gwname");
>      t_on_failure("gwfailure");
>   }
>
> Thanks!
>
> //Andy
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20170210/a7b5b376/attachment.html>