Using 5.3 branch, I have
sip-proxy_ctl> siptrace.status check Disabled
but still these kind of errors appear in syslog:
Oct 16 12:07:10 salmon /usr/bin/sip-proxy[26459]: ERROR: siptrace [siptrace.c:1250]: trace_onreq_out(): retransmission Oct 16 12:07:11 salmon /usr/bin/sip-proxy[26459]: ERROR: siptrace [siptrace.c:1250]: trace_onreq_out(): retransmission Oct 16 12:07:13 salmon /usr/bin/sip-proxy[26459]: ERROR: siptrace [siptrace.c:1250]: trace_onreq_out(): retransmission
How is it possible?
-- Juha
I made it a debug message. It seems to have been cause by a new check to detect the retransmissions.
There are transaction callbacks enabled because some of them can be set only at startup, detection whether siptrace should be done or not for that transaction being done later in that function, once the pointer to the message is figure out.
Cheers, Daniel
On 16.10.19 11:16, Juha Heinanen wrote:
Using 5.3 branch, I have
sip-proxy_ctl> siptrace.status check Disabled
but still these kind of errors appear in syslog:
Oct 16 12:07:10 salmon /usr/bin/sip-proxy[26459]: ERROR: siptrace [siptrace.c:1250]: trace_onreq_out(): retransmission Oct 16 12:07:11 salmon /usr/bin/sip-proxy[26459]: ERROR: siptrace [siptrace.c:1250]: trace_onreq_out(): retransmission Oct 16 12:07:13 salmon /usr/bin/sip-proxy[26459]: ERROR: siptrace [siptrace.c:1250]: trace_onreq_out(): retransmission
How is it possible?
-- Juha
Kamailio (SER) - Development Mailing List sr-dev@lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
Daniel-Constantin Mierla writes:
There are transaction callbacks enabled because some of them can be set only at startup, detection whether siptrace should be done or not for that transaction being done later in that function, once the pointer to the message is figure out.
My understanding is that callbacks are used only in hep mode. If so, no callbacks should be enabled when hep mode is off.
-- Juha
On 16.10.19 12:30, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
There are transaction callbacks enabled because some of them can be set only at startup, detection whether siptrace should be done or not for that transaction being done later in that function, once the pointer to the message is figure out.
My understanding is that callbacks are used only in hep mode. If so, no callbacks should be enabled when hep mode is off.
The callbacks for tm are used also for database storage, those from the core for packet-in/packet-out are for hep only at this moment.
Daniel
On 16.10.19 12:40, Juha Heinanen wrote:
Daniel-Constantin Mierla writes:
The callbacks for tm are used also for database storage, those from the core for packet-in/packet-out are for hep only at this moment.
What if only messages are traced, i.e., not transactions nor dialogs. Are callbacks still used?
You can look in the code, but some options can be changed at runtime via rpc, and registration of some callbacks can be done only at startup.
Daniel
-
Daniel-Constantin Mierla -
Juha Heinanen