Hi Norman,

yup, that is exactly my problem - I use it only for doing siptrace per user and on platform with high traffic, the stateless ACK tracing produces a lot of residual data in DB.

Regards, Bogdan

Norman Brandinger wrote:

This change would be good. We have reduced our use of siptrace for this very reason.

Norm

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@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel