Hi Mickael,
If you do the drop in branch route, that branch will be discarded (not
sent out at all). IF no branch is actually sent out, you will get the
error logs from t_forward_nonack (as you have).
In this case, the t_relay() will fail (nothing sent) - to get that error
in script, set flag 0x02
(http://www.opensips.org/html/docs/modules/1.11.x/tm.html#id294578),
otherwise the error will be internally handled.
A failure on sending does not trigger a failure route - failure route is
triggered only if request sent out and the transaction completed with a
negative code.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 06.10.2014 11:59, Mickael Marrache wrote:
Hi,
What happens after drop() is called from a branch_route?
In my case, I armed a failure route for the incoming INVITE in the
request route and therefore, I would expect that the failure route
would be called after drop() is called. However, I see the following
error in the logs and the following reply is returned to the UAC.
Oct 6 08:57:27 DBG:tm:pre_print_uac_request: dropping branch
sip:x@x:;user=phone
Oct 6 08:57:27 ERROR:tm:t_forward_nonack: failure to add branches
SIP/2.0 500 Server error occurred (1/TM)
I use the failure route to detect current transaction failure and try
the next termination if there is.
Thanks,
Mickael
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
___
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
