i would prefer to call sip_trace() up front in the script in order to avoid calling it many places. currently, however, looks like setting of traced_user_avp after sip_trace() is called has no effect.
how about if i add a module var delayed_avp_trace (or something) so that if it has value 1, trusted_user_avp value is checked when the message is actually stored by sip_trace_store_db function?
-- juha
sip_trace() stores the message at the moment of execution, if the avp is not set at that moment, it is not found, thus not used.
There is a flag that can be set and the message is stored at the moment of delivery.
Cheers, Daniel
On 22/02/15 02:07, Juha Heinanen wrote:
i would prefer to call sip_trace() up front in the script in order to avoid calling it many places. currently, however, looks like setting of traced_user_avp after sip_trace() is called has no effect.
how about if i add a module var delayed_avp_trace (or something) so that if it has value 1, trusted_user_avp value is checked when the message is actually stored by sip_trace_store_db function?
-- juha
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Daniel-Constantin Mierla writes:
sip_trace() stores the message at the moment of execution, if the avp is not set at that moment, it is not found, thus not used.
There is a flag that can be set and the message is stored at the moment of delivery.
the flags seems to mostly affect only outgoing messages, but i do see also some received replies in the database. in this test i only set the flag at the start of the script and don't call sip_trace() at all.
-- juha
-
Daniel-Constantin Mierla -
Juha Heinanen