[Devel] reason code for multi-leg accounting
Andreas Granig
andreas.granig at inode.info
Mon May 15 12:26:07 CEST 2006
Bogdan-Andrei Iancu wrote:
> yes, there is a lot of info that make sense to be additionally logged
> for each leg. My idea is to make the multi-leg accounting more flexible
> - instead of having the fixed pair of source/destination, you will
> define a set of avp to be logged for each leg - so you will define the
> source, destination, comment, etc...
As a workaround, we currently print several avps into one
comma-separated string which is used as call leg avp, and the mediation
system parses that info.
Andy
More information about the Devel
mailing list