[OpenSER-Users] [RFC] - siptrace change

[Bogdan-Andrei Iancu]

Hi Helmut,

As explaining to Dan, this discussion is only about ACK resulting from 
sl_send_reply(negative reply)). 200 OK ACKs and statefull ACKs will 
still be logged.

Regards,
Bogdan

Helmut Kuper wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
> from my point of view, you can disable this feature.
>
> I use the siptrace module "only" for supporting lawful interception on
> signalling level. There I think I can do without ACKs since ACKs are not
> containing too much usefull informations.
>
> Further, debugging of sipflows is done with a separate tool.
>
> regards
> Helmut
>
>
> Bogdan-Andrei Iancu schrieb:
> | 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
> |
> | _______________________________________________
> | Users mailing list
> | Users at lists.openser.org
> | http://lists.openser.org/cgi-bin/mailman/listinfo/users
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.8 (MingW32)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iEYEARECAAYFAkgq5YMACgkQ4tZeNddg3dyJCACgopF5ByV+nMwcj7JNbsL5vu06
> aIYAn09xRZMDP2ecEs6r7swma969ZNVd
> =LBFW
> -----END PGP SIGNATURE-----
>