[RFC] SIPtrace behaviour

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[RFC] SIPtrace behaviour

Bogdan-Andrei Iancu
Hi,

While doing some work on the siptrace module I remembered some pending
issues in regards to sip tracing:

1) tracing the stateless ACKs - right now, all the stateless ACK (in
response to stateless replies) are traced ; this happens because you do
not get any access to the ACK (from script), so you cannot set the trace
flag, and also because it is stateless, so you cannot keep any state to
remember (at ACK time) if the ACK should or not be traced.

This current behaviour is quite annoying because your siptrace DB will
be actually flooded with ACKs, even is you do not mark no message for
tracing...Personally I do disable from the code the stateless ACK
tracing in order to get access to only relevant data.

So, the questions are:
    1) any suggestions about how we can do selective tracing on the
stateless ACKs (from sl module)
    2) should we disable it or at least make it configurable in the module?


Regards,
Bogdan

_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|

Re: [RFC] SIPtrace behaviour

Bogdan-Andrei Iancu
Hi,

Well, if there are no opinion, on this, I will add a parameter to
control the tracing of the stateless ACKs ....by default it will disabled.

Regards,
Bogdan

Bogdan-Andrei Iancu wrote:

> Hi,
>
> While doing some work on the siptrace module I remembered some pending
> issues in regards to sip tracing:
>
> 1) tracing the stateless ACKs - right now, all the stateless ACK (in
> response to stateless replies) are traced ; this happens because you do
> not get any access to the ACK (from script), so you cannot set the trace
> flag, and also because it is stateless, so you cannot keep any state to
> remember (at ACK time) if the ACK should or not be traced.
>
> This current behaviour is quite annoying because your siptrace DB will
> be actually flooded with ACKs, even is you do not mark no message for
> tracing...Personally I do disable from the code the stateless ACK
> tracing in order to get access to only relevant data.
>
> So, the questions are:
>     1) any suggestions about how we can do selective tracing on the
> stateless ACKs (from sl module)
>     2) should we disable it or at least make it configurable in the module?
>
>
> Regards,
> Bogdan
>
> _______________________________________________
> Users mailing list
> [hidden email]
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
>  


_______________________________________________
Users mailing list
[hidden email]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users