if tcp uas is not reachable, sr prints ERRORs to syslog:
Apr 20 13:23:10 localhost /usr/sbin/sip-proxy[22508]: INFO: Routing first INVITE to sip:foo@192.98.102.10:4040;transport=tcp and <<null>> Apr 20 13:23:10 localhost /usr/sbin/sip-proxy[22508]: ERROR: tm [../../forward.h:169]: msg_send: ERROR: tcp_send failed Apr 20 13:23:10 localhost /usr/sbin/sip-proxy[22508]: ERROR: tm [t_fwd.c:1249]: ERROR: t_send_branch: sending request on branch 0 failed
since this is not really an error, would it be possible to downgrade the messages to WARNINGs?
-- juha
2010/4/20 Juha Heinanen jh@tutpro.com:
if tcp uas is not reachable, sr prints ERRORs to syslog:
Apr 20 13:23:10 localhost /usr/sbin/sip-proxy[22508]: INFO: Routing first INVITE to sip:foo@192.98.102.10:4040;transport=tcp and <<null>> Apr 20 13:23:10 localhost /usr/sbin/sip-proxy[22508]: ERROR: tm [../../forward.h:169]: msg_send: ERROR: tcp_send failed Apr 20 13:23:10 localhost /usr/sbin/sip-proxy[22508]: ERROR: tm [t_fwd.c:1249]: ERROR: t_send_branch: sending request on branch 0 failed
since this is not really an error, would it be possible to downgrade the messages to WARNINGs?
+1
I have a log filter to inspect just NOTICE, WARNING, ERROR and CRITICAL and it's not good to see so many ERROR logs due to normal TCP "errors".