You can try it, not sure if docs are really in sync there.
On the other hand, could be that the transaction was matching the 2xx and then practically the state of transaction changed to completed, so even doing a drop of not sending out, the transaction is still ended.
An alternative solution is using a hash table with expiration of the items matching the max timeout for transactions.
Cheers, Daniel
On 21/10/16 11:24, Alex Balashov wrote:
The core documentation says that in a named onreply_route[], only provisional replies can be drop()'d. To drop any reply, it is necessary to use a global onreply_route.
Is there any workaround for this, i.e. so I can drop a 2xx reply from a specific TM transaction?
The reason is, to know whether to drop it, I need access to either AVPs or, ideally, dialog variables. Since the global onreply_route is executed by the core, I presume I won't have access to anything that persists through TM there.
Thanks!
-- Alex