User's Manual 176 Document #: LTRT-27045
Mediant 1000B Gateway & E-SBC
Where SI is the SIP Interface and NI is the network interface.
The device also sends IDS notifications and alarms in Syslog messages to a Syslog
server. This occurs only if you have configured Syslog (see ''Enabling Syslog'' on page
892). An example of a Syslog message with IDS alarms and notifications is shown below:
Figure 13-9: Syslog Message Example with IDS Alarms and Notifications
The table below lists the Syslog text messages per malicious event:
Table 13-6: Types of Malicious Events and Syslog Text String
Reason Description Syslog String
Connection
Abuse
TLS authentication failure abuse-tls-auth-fail
Malformed
Messages
ï‚§ Message exceeds a user-defined maximum
message length (50K)
ï‚§ Any SIP parser error
ï‚§ Message policy match
ï‚§ Basic headers not present
ï‚§ Content length header not present (for TCP)
ï‚§ Header overflow
ï‚§ malformed-invalid-
msg-len
ï‚§ malformed-parse-error
ï‚§ malformed-message-
policy
ï‚§ malformed-miss-
header
ï‚§ malformed-miss-
content-len
ï‚§ malformed-header-
overflow
Authentication
Failure
ï‚§ Local authentication ("Bad digest" errors)
ï‚§ Remote authentication (SIP 401/407 is sent if
original message includes authentication)
ï‚§ auth-establish-fail
ï‚§ auth-reject-response
Dialog
Establishment
Failure
ï‚§ Classification failure
ï‚§ Routing failure
ï‚§ Other local rejects (prior to SIP 180 response)
ï‚§ Remote rejects (prior to SIP 180 response)
ï‚§ Malicious signature pattern detected
ï‚§ establish-classify-fail
ï‚§ establish-route-fail
ï‚§ establish-local-reject
ï‚§ establish-remote-
reject
ï‚§ establish-malicious-
signature-db-reject
Abnormal Flow
ï‚§ Requests and responses without a matching
transaction user (except ACK requests)
ï‚§ Requests and responses without a matching
transaction (except ACK requests)
ï‚§ flow-no-match-tu
ï‚§ flow-no-match-
transaction