The accounting is at transaction level, so you can do acc in the same way for INVITE and re-INVITE....no difference.
So mark for accounting all INVITEs (initial or sequential) - and group all records belonging to the same call by CallID, ToTAG and FromTAG. Regard, Bogdan Brett Nemeroff wrote: > What about re-invites? I've seen those show up, like when negotiating > T.38 transactions, where the source and IP get flipped around.. is > there something I need to do to ensure those transactions arn't part > of the CDR? I'm not sure how to handle them > > Thanks, > Brett > > > On Fri, Feb 20, 2009 at 10:02 AM, Bogdan-Andrei Iancu > <[email protected]> wrote: > >> Hi Brett, >> >> For serial forking, the ACC module will account the last used branch, so $ru >> will point to the RURI of the last branch >> >> If you do parallel forking, the $ru will point to the RURI of the winning >> branch (the branch to be sent back to the UAC). >> >> Regards, >> Bogdan >> >> >> Brett Nemeroff wrote: >> >>> Here's another ACC question. I know this has been asked in the past, >>> but I'm not sure it's ever gotten a good answer. >>> >>> >>> So I'm looking at my call accounting with ACC module. I'm logging $rd >>> in there as an extra variable. When I'm using serial routing, what's >>> the "right" way to determine which gateway took the call?? >>> -Brett >>> >>> _______________________________________________ >>> 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
