16 Oct
2019
16 Oct
'19
6:17 a.m.
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(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-dev
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training, Oct 21-23, 2019, Berlin, Germany -- https://asipto.com/u/kat