Administrator's Guide

Appendix B. Troubleshooting
Log Messages
Here is a presentation of many common log messages that can be found in the Telecommut-
ing Module log.
In many messages, information about IP addresses, usernames and other changing parame-
ters will be displayed in the log messages. In the listing, such information will be presented
contained in angle brackets. The listed log message "<Username> logged on" will mean
that the real message in your log will look like "admin logged on" or "Charlie logged on",
that is, the <Username> will be replaced by a username on your system.
SIP errors
These log messages can appear when the SIP errors box has been checked on the Display
Log page.
SIP send failure -1 on socket -1 <event number>
Something went wrong when the Telecommuting Module tried to send a SIP packet to an-
other SIP device. Maybe there was no TLS connection (if TLS should be used), or the device
is known not to reply, or the Telecommuting Module has no network connection at all on the
interface facing the other device. The event number is an internal parameter to keep track of
different SIP events.
Destination <IP address>:<port> is known bad. Skipping.
The SIP device on <IP address> has been blacklisted by the Telecommuting Module. This
happens when the other SIP device has sent an ICMP type 3 packet in response to a SIP
packet, or when the other SIP device has not responded at all to previous SIP signaling. For
the latter event, you can avoid the blacklisting by setting the SIP blacklist interval on the
Sessions and Media page to 0.
Parse error at ’<character>’ in message from <IP address>, at
line: <SIP line>
Something on the referred line in the SIP message does not comply with the SIP standard or
is something else that the Telecommuting Module does not recognize as valid SIP syntax.
No answer from destination <IP address>:<port>
The Telecommuting Module sent a SIP packet to the IP address, but it hasn’t responded
before the message timed out. If this was a message to a SIP domain, the Telecommuting
Module will try next server handling this domain.
sipfw: SIP <response code> response from <IP address>
rejected, no state
Something in the received SIP response was unexpected. It could be a very late response to
a SIP request, or a message where the topmost Via header does not indicate the Telecom-
muting Module, or something else that does not make it an invalid SIP packet in itself, but
it doesn’t match what has happened in the Telecommuting Module.
332