Hi Tito,

The 477 is locally generated by OpenSIPS prior to send the the request out. This is why you cannot have in in the failure route (which is triggered by the failure of the transaction, AFTER the request was sent out).

What you can do is to use the 2 flag for t_relay() (see http://www.opensips.org/html/docs/modules/2.3.x/tm.html#t_relay) and check in script for the failure of t_relay().

Regards,

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

OpenSIPS Summit May 2017 Amsterdam
  http://www.opensips.org/events/Summit-2017Amsterdam.html

On 05/01/2017 10:55 PM, Tito Cumpen wrote:
Group,

Is there a tm param to force 477 failures to go to failure block ?

IE: I have a wss socket that times out or closes connection but the UL entry is still active so the connection attempt fails and the 477 is sent back to the UAC instead of trying the logic in the failure block. Can anything be done here ?


Thanks,
Tito




_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users

Reply via email to