Ok. good to know I'm not just crazy. I was panicked when I was reviewing the traces and thought that maybe it wasn't actually sending the ACK (which of course, it is). Do I need to submit this anywhere? -Brett
On Fri, Apr 24, 2009 at 9:41 AM, Bogdan-Andrei Iancu <[email protected] > wrote: > Hi Brett, > > I thing this issue need to be documented - it is a known limitation of the > module not to be able to capture the outgoing ACKs (as these are sent > stateless by the core functions and not by TM functions). > > I have on my todo list to find a way do capture those ACKs - it's just a > matter of time ;) > > Regards, > Bogdan > > Brett Nemeroff wrote: > >> Hey All, >> I'm using 1.5.1, and I have enable_ack_trace set to 1: >> modparam("siptrace", "enable_ack_trace", 1) >> >> >> SipTrace is working great, but the RELAYED ACK isn't logged. It logs the >> reception of the ACK from the originator, but it doesn't show that the ACK >> was RELAYED onto the destination. >> >> Am I doing something wrong? I enable tracing with the inital invite using >> "trace_dialog()", so there are no siptrace flags involved with the ACK. This >> works for all other messages (like BYE). >> >> -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
