Administering Avaya Session Border Controller

Incidents

Last Updated : Sep 01, 2026 |

Prolog information

Metadata

Keywords:

The following sections describe the incidents that can occur in Avaya SBC.

Denial of Service (DoS) incidents

Incident Name	Component generating the trap	Cause and solution
ipcsSingleSourceDoS	SBC	Avaya SBC detects a single source DoS
ipcsSingleSourceCallWalkDoS	SBC	Avaya SBC detects a call walk DoS
ipcsPhoneDoS	SBC	Avaya SBC detects a phone DoS
ipcsPhoneStealthDoS	SBC	Avaya SBC detects a phone stealth DoS
ipcsServerDoS	SBC	Avaya SBC detects a server DoS or blocks a server DoS The incident occurs due to any of the following reasons: Initiated Threshold Crossed - Action Whitelist Pending Threshold Crossed- Action Whitelist Failed Threshold Crossed- Action Whitelist attack from Server side - Initiated Threshold Crossed- Action SIV attack from Server side - Pending Threshold Crossed- Action SIV attack from Server side - Failed Threshold Crossed- Action SIV Initiated Threshold Crossed- Action Limit Pending Threshold Crossed- Action Limit Failed Threshold Crossed- Action Limit
ipcsPhoneStealthDDoS	SBC	Avaya SBC detects a phone stealth DDoS
ipcsDomainDoS	SBC	Avaya SBC detects a domain DoS

Blacklist/Whitelist incidents

Incident Name	Component generating the trap	Cause and solution
ipcsBlackipcsListCallBlocked	SBC	Avaya SBC comes across a blacklisted caller

Incident Name	Component generating the trap	Cause and solution
ipcsDroppedScrubMsg	SBC	Avaya SBC comes across a SDP parser error or scrubber anomaly
ipcsRejectedScrubMsg	SBC	Avaya SBC comes across a scrubber anomaly
ipcsDetectedScrubMsg	SBC	Avaya SBC comes across a scrubber anomaly

Protocol discrepancy incidents

Incident Name	Component generating the trap	Cause and solution
ipcsACKMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue ACK message
ipcsBYEMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue BYE message
ipcsCANCELMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue CANCEL message
ipcsNOTIFYMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue NOTIFY message
ipcsPRACKMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue PRACK message
ipcsREINVITEMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue REINVITE message
ipcsREFERMsgOutofDialogue	SBC	Avaya SBC gets an out of dialogue REFER message
ipcs1XXMsgOutofTransaction	SBC	Avaya SBC gets an out of dialogue 1xx class response
ipcs2XXMsgOutofTransaction	SBC	Avaya SBC gets an out of dialogue 2xx class response
ipcs3XXMsgOutofTransaction	SBC	Avaya SBC gets an out of dialogue 3xx class response
ipcs4XXMsgOutofTransaction	SBC	Avaya SBC gets an out of dialogue 4xx class response
ipcs5XXMsgOutofTransaction	SBC	Avaya SBC gets an out of dialogue 5xx class response
ipcs6XXMsgOutofTransaction	SBC	Avaya SBC gets an out of dialogue 6xx class response
ipcsAuthRealmMismatch	SBC	Avaya SBC comes across a realm mismatch

Incident Name	Component generating the trap	Cause and solution
ipcsCallDenied	SBC	Calls to the Avaya SBC are denied due to any of the following reasons: Video is disabled or disallowed Audio is disabled or disallowed Maximum number of video sessions is exceeded Maximum number of audio sessions is exceeded Maximum number of audio sessions per endpoint is exceeded Maximum number of video sessions per endpoint is exceeded No Server Flow is matched for incoming message No Server Flow is matched for outgoing message No Subscriber Flow is matched Prop method disallowed out of dialog message Standard method disallowed out of dialog message No Routing Rule is matched Codec is disallowed Method is disallowed
ipcsRegistrationDenied	SBC	Avaya SBC denies registration because of any of the following reasons: No Server Flow is matched for incoming message No Server Flow is matched for outgoing message No Subscriber Flow is matched Prop method disallowed out of dialog message Standard method disallowed out of dialog message No Routing Rule is matched Method is disallowed
ipcsSubscriptionDenied	SBC	Avaya SBC denies subscription because of any of the following reasons: No Server Flow is matched for incoming message No Server Flow is matched for outgoing message No Subscriber Flow is matched Prop method disallowed in dialog message Standard method disallowed in out of dialog message No Routing Rule is matched Method is disallowed
ipcsRedirectionDenied	SBC	Avaya SBC denies redirection because of any of the following reasons: No Server Flow is matched for incoming message No Server Flow is matched for outgoing message No Subscriber Flow is matched Prop method disallowed in dialog message Standard method disallowed in dialog message Prop method disallowed in out of dialog message Standard method disallowed in out of dialog message No Routing Rule is matched Method is disallowed
ipcsMessageDropped	SBC	Avaya SBC drops a message because of any of the following reasons: No Server Flow is matched for incoming message No Server Flow is matched for outgoing message No Subscriber Flow is matched Response prop header is disallowed Response standard header is disallowed Response prop header is mandatory Response standard header is mandatory Response prop header is disallowed Response standard header is disallowed Request prop header is mandatory Request standard header is mandatory Prop method disallowed in dialog message Standard method disallowed in dialog message Method is disallowed Prop method disallowed in out of dialog message Standard method disallowed in out of dialog message

Route incidents

Incident Name	Component generating the trap	Cause and solution
ipcsPrimaryRadiusServerUnreachable	EMS	Primary Radius server is unreachable
ipcsSecondaryRadiusServerUnreachable	EMS	Secondary Radius server is unreachable

TLS certificate failure incidents

Incident Name	Component generating the trap	Cause and solution
ipcsTlsCertificate	SBC	Avaya SBC comes across a TLS certificate error because of any of the following causes: Could not create TLS context - for default client mode No cipher list is provided Could not create TLS context for either server or client mode Could not read Certificate Could not read private key Private key does not correspond to the loaded certificate Unable to load Root Certificate or CA list Unable to load CRL list Unable to cipher list provided No cipher list provided

Media anomaly detection incidents

Incident Name	Component generating the trap	Cause and solution
ipcsPacketSizeViolation	SBC	Avaya SBC comes across a packet size violation
ipcsSSRCViolation	SBC	Avaya SBC comes across a synchronization source
ipcsSeqNoViolation	SBC	Avaya SBC comes across a sequence number violation
ipcsTimestampViolation	SBC	Avaya SBC comes across a timestamp violation
ipcsMediaInActivityFromBothSides	SBC	Avaya SBC comes across a media inactivity from both sides of the call There is call audit that runs on the SBC. If there is no media activity or signaling activity for some specified period, that call will be cleared by the audit. You can track the call ID in the incident and then check that in using traceSBC to see the call flow for the specified call.
ipcsUnsupportedMedia	SBC	Avaya SBC comes across unsupported media
ipcsRTPDoSAttack	SBC	Avaya SBC comes across an RTP denial of service attack
ipcsMediaPortUnavailable	SBC	No free media ports are available
ipcsRTPInjectionAttack	SBC	Avaya SBC comes across an RTP injection attack

HA link failover incident

Incident Name	Component generating the trap	Cause and solution
ipcsHAGracefulFailover	SBC	The primary server has gone down voluntarily
ipcsHAKaFail	SBC	High Availability keep alive messages fail
ipcsHATakeoverDone	SBC	HA takeover is completed
ipcsHASecondaryDown	SBC	HA secondary server is down and HA will not be available until the secondary server is up

License incidents

Incident Name	Component generating the trap	Cause and solution
sbcLicenseExceeded	SBC	Avaya SBC gets requests after the maximum number of licensed sessions is exceeded

TURN/STUN incidents

Incident Name	Component generating the trap	Cause and solution
sbcTurnStunMediaRelayCreationFailed	SBC	Media relay flow creation failed
sbcTurnStunMediaRelayDeletionFailed	SBC	Media relay flow deletion failed
sbcTurnStunServerError	SBC	Avaya SBC detects a TURN/STUN error because of any of the following reasons: Invalid User Name is configured Invalid Realm is configured Invalid Password is configured Invalid Realm is configured Relay Port is unavailable TCP/TLS Listener has failed Invalid User Account is configured Invalid User Name is configured

CES Proxy incidents

Incident Name	Component generating the trap	Cause and solution
sbcCesProxy1xMUserLoginFailed	SBC	Login attempts from an Avaya one-X® Mobile user to the CES proxy fails because of any of the following reasons: Protocol Type validation failed CesProxy data is not present Avaya SBC received an invalid response other than login response Object Type validation failed Login request data type validation failed Login request key id validation failed API object type validation failed API data type and key Id validation failed API data type validation failed API key id validation failed Object type validation failed Avaya one-X® Mobile user login failed

Send Feedback