The t_check_trans() is performing a matching of the current request
against the known transaction. Such matching, for relies, doesn't make
too much of a sense as:
1) if you use an onreply_route[], it means your reply already
matched the transaction
2) for replies, there is no special handling for retransmissions,
they are handled in the same way as the first reply. (unlikely for the
requests)
If you want to "catch" the 200 OK retransmission, simply use a bflag -
set it on first 200OK and test it for the next 200 OKs :)
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
On 4/6/20 6:56 PM, johan wrote:
Is there a specific reason why t_check_trans can't be called in a
reply route ?
To me this seems handy to see if a 200 OK is a retransmission.
BR,
_______________________________________________
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
