1 Mar
2013
1 Mar
'13
12:18 p.m.
On 28/02/13 20:20, Daniel-Constantin Mierla wrote:
I am not sure that data in request can be really
useful in this case
for a general solution. Have in mind parallel forking, when only one
branch gets in failure_route, so if one branch gets 430 and and
another one 3xx, the one for 3xx is handled.
Maybe handling in onreply_route would be better. The field ruid might
need propagation to dst set (and branch) -- that's unique identifier
for location records, making very easy to find and remove desired
contact.
Adding an exported function that can remove something based on ruid
seems like a good solution. Can you point me to any examples of other
things propagated to dst set and branch so I can work out how to make
this available?
Thanks,
Peter