[OpenSER-Users] [OpenSER-Devel] [RFC] - siptrace change

Dan Pascu dan at ag-projects.com
Wed May 14 17:14:37 CEST 2008


We use it to trace all traffic, at least on small installations and I 
wouldn't want to miss those ACKs. I cannot use the per user tracing 
capability because it is very cumbersome to trace all the requests and 
replies for a certain user with the current implementation.

On Wednesday 14 May 2008, Bogdan-Andrei Iancu wrote:
> Hi,
>
> I would like to get your opinion/comments on some siptrace issue.
>
> In 1.3, a new capability was added in siptrace - to trace the ACK
> resulted from sending stateless replies.
>
> The problem I discovered with this is that it cannot be controlled by
> selecting the messages or transactions to be be traced. Usually you use
> siptrace to trace only certain transactions / messages - tracing all
> traffic is usually not a realistic option.
>
> So, with the stateless ACK, the siptrace module cannot apply the
> selection from script and trace them all, with no filtering at all. So,
> if you want to trace a traffic for a single user, all ACK going through
> the platform will be traced.
>
> This reduces the usability of the module and you get a lot of garbage
> tracing.
>
> My suggestion will be to disable stateless ACK tracing until a way to
> control/filter it is found. I'm asking this considering the upcoming
> 1.3.2 release from tomorrow.
>
> Regards,
> Bogdan
>
> _______________________________________________
> Devel mailing list
> Devel at lists.openser.org
> http://lists.openser.org/cgi-bin/mailman/listinfo/devel



-- 
Dan




More information about the Users mailing list