Hi Brian, siptrace works like this:
sip_trace() function will siptrace the current SIP message + setting the trace flag (like setflag(22) ) will trace all the messages related to the transaction created by the current request you process trace_dialog() works only for call - use it for initials INVITEs and it will trace the whole dialog. Regards, Bogdan [email protected] wrote: > Hello list, > > According to the online siptrace module docs: > > 'Only messages processed with TM/SL are logged.' > > First, I assume that is why when I do: > > modparam("siptrace", "trace_flag", 22) > route{ > setflag(22); > setbflag(22); > [...] > } > > ...that no REGISTERs are being traced. I assume that all other > messages will be traced by the above code. > > Also, I see that I have the option of: > > if (is_method("INVITE") && !has_totag()) > trace_dialog(); > > ...which seems to have the same effect (no REGISTERs traced.) > But if I do: > > route{ > sip_trace(); > [...] > } > > ...then REGISTERs and INVITEs will be traced, right? > > QUESTION > > How do most people choose which of these three siptrace logging > methods to use? Is there ever a reason to definitely not use one > of them, and is it common to combine any of these three methods? > > Thanks, > Brian > > _______________________________________________ > Users mailing list > [email protected] > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > -- Bogdan-Andrei Iancu www.voice-system.ro _______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
