Hi Bogdan,
the reason haven't changed: avps doesn't work in on_reply route since the avp belong to a transaction and the on_reply route execution is not synchronized and may be done in parallel for same transaction.
For the moment there is no solution to this - synchronizing the on_reply routes will be quite ugly :-/
Do you see another - even proprietary - very-short-term-workaround that can provide this functionality (storing avps within onreply_route in the database that can be later on accessed from the route block using avp-ops) without extra module coding? Ugly is not important at all if it works. After all it's just about prototyping, the final code should be clean... ;))
But what will be done (there was a discussion with Juha on this topic) is to add global avps which not being bound to a transaction can be used inside on_reply route. I guess this will solve your problem....
Definitely. That's also conceptually closer to what Service-Route is supposed to do - it's valid for the lifetime of a registration (although it might be changed by re-registrations) and not just for one transaction. Any estimate when this will be available?
Thanks for your help, regards --Joachim