The following list provides the alarms and events defined for SIP.

ID

Sub-ID

Type

MIB Trap NameOID

Condition

Category

Decode Key

Default Severity

Auto Clear

Notes/Description

9

1

Alarm

uxAlmSIPServerNotResponding1.3.6.1.4.1.177.15.2.589825

SIP Server not responding

Communication

SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

Major

(tick)

  • SIP server has failed to respond and has been taken out of service.
  • This alarm will be cleared by the event 'SIP server became responsive'.

9

2

Alarm

uxAlmSignalingGroupTakenoutofService1.3.6.1.4.1.177.15.2.589826

Signaling Group taken out of service

Communication

SG;PodName;ContainerType

Critical

(tick)

  • All servers in SG have failed.
  • This alarm will be cleared by 'SIP Signaling group enabled' event.

9

3

Event

uxAlmSignalingGroupDisabled1.3.6.1.4.1.177.15.2.589827

Signaling Group disabled

Communication

SG;PodName;ContainerType



  • Configuration action has changed this Signaling Group from Enabled to Disabled.

9

4

Alarm

uxAlmSIPTLSServerHandshakeFailure1.3.6.1.4.1.177.15.2.589828

SIP-TLS Server Handshake Failure

Security

TLSProfile;IPAddress;PodName;ContainerType

Minor


  • TLS server handshake failed with alert code.
  • Action: Refer to Error Alerts in RFC 5246 for the problem.

9

5

Alarm

uxAlmSIPTLSHandshakeInactivityTimeoutFailure1.3.6.1.4.1.177.15.2.589829

SIP-TLS Handshake Inactivity Timeout Failure

Security

TLSProfile;IPAddress;PodName;ContainerType

Minor


  • Handshake failed due to no response from peer within specified timeout.
  • Action: Increase the Handshake Inactivity Timeout in TLS Profile.

9

6

Alarm

uxAlmConfiguredPortNumberMismatch1.3.6.1.4.1.177.15.2.589830

Configured port number mismatch

Processing

SG;IPAddress;Port;PodName;ContainerType

Minor


  • Discrepancy of an FQDN/Port configured in the SipServer object that is different than the DNS SRV lookup.
  • A DNS SRV record can return the port number for the selected protocol.
  • The DNS SRV port value will take priority over the configured port.

9

7

Event

uxAlmSIPServerBecameResponsive1.3.6.1.4.1.177.15.2.589831

SIP Server became responsive

Communication

SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType



  • SIP server came up.

9

8

Alarm

uxAlmSIPclusterwentdown1.3.6.1.4.1.177.15.2.589832

SIP cluster went down

Communication

SIPCluster;PodName;ContainerType

Major

(tick)

  • SIP cluster went down.
  • This is due to all the servers in the clusters being unresponsive.
  • This alarm will be cleared by the event 'SIP Cluster Enabled'. 

9

9

Event

uxAlmSIPClusterEnabled1.3.6.1.4.1.177.15.2.589833

SIP Cluster enabled

Communication

SIPCluster;PodName;ContainerType



  • SIP cluster enabled.

9

10

Event

uxAlmSIPSignalingGroupEnabled1.3.6.1.4.1.177.15.2.589834

SIP Signaling group enabled

Communication

SG;PodName;ContainerType



  • SIP Signaling group enabled.

9

11

Alarm

uxAlmSIPSignalingGroupDNSFailure1.3.6.1.4.1.177.15.2.589835

SIP Signaling Group: DNS Failure

Communication

SG;PodName;ContainerType

Major

(tick)

  • Failed to resolve the FQDN entries in the SIP Signaling Group. [details].

9

12

Event

uxAlmSIPSignalingGroupFQDNResolved1.3.6.1.4.1.177.15.2.589836

SIP Signaling Group: FQDN Resolved

Communication

SG;PodName;ContainerType



  • Successfully resolved the FQDN of the SIP Signaling group.

9

13

Alarm

uxAlmSIPServerDNSFailure1.3.6.1.4.1.177.15.2.589837

SIP Server: DNS Failure

Communication

SIPCluster;ServID;PodName;ContainerType

Major

(tick)

  • Failed to resolve the SIP server FQDN entries in the SIP Server table. [details].

9

14

Event

uxAlmSIPServerFQDNResolved1.3.6.1.4.1.177.15.2.589838

SIP Server: FQDN Resolved

Communication

SIPCluster;ServID;PodName;ContainerType



  • SIP Server config FQDN resolved.

9

15

Alarm

uxAlmSIPCallSessionDNSFailure1.3.6.1.4.1.177.15.2.589839

SIP call session DNS failure

Communication

SG;PodName;ContainerType

Major


  • Failed to resolve an FQDN with DNS server during a SIP call session.

9

16

Alarm

uxAlmAcquiringLicenseforRegisterFailed1.3.6.1.4.1.177.15.2.589840

Acquiring license for Register failed

Communication

SG;PodName;ContainerType

Major


  • Failed to acquire license from License Manager.
917AlarmuxAlmSessionorOtherResourceLeak1.3.6.1.4.1.177.15.2.589841Session or other resource leakCommunicationSG;PodName;ContainerTypeMajor
  • SIP performs self-check for leaks.
  • Please enable logging for SIP and issue 'show resources' command.
918AlarmuxAlmFailedtoBindtoNetworkInterface1.3.6.1.4.1.177.15.2.589842Failed to bind to network interfaceCommunicationSG;PodName;ContainerTypeMinor

(tick)


  • Failed to bind to network interface due to dynamic IP address not available.
919EventuxAlmSuccessfullyBoundtoNetworkInterface1.3.6.1.4.1.177.15.2.589843Successfully bound to network interfaceCommunicationSG;PodName;ContainerType

  • Successfully bound to network interface.
  • DHCP lease renewed.
920AlarmuxAlmSIPRegisterServerNotResponding1.3.6.1.4.1.177.15.2.589844SIP Register Server not respondingCommunicationSIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerTypeMajor

(tick)

  • SIP Register server has failed to respond.
  • This alarm will be cleared by the event 'SIP Regular server became responsive'.
921EventuxAlmSIPRegisterServerBecameResponsive1.3.6.1.4.1.177.15.2.589845SIP Register Server became  responsiveCommunicationSIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

  • SIP Register server came up.

9

22

Alarm

uxAlmRegistrationNotValidReceivedstalefalse1.3.6.1.4.1.177.15.2.589846

Registration not valid; received stale=false

Communication

SG;AorName;PodName;ContainerType

Major

(tick)

  • Stale=false/Registration no longer valid due to incorrect credentials.

9

23

Event

uxAlmConfigChangeforSIPEndpointThatReceivedstalefalse1.3.6.1.4.1.177.15.2.589847

Config change for SIP endpoint that received stale=false

Communication

SG;AorName;PodName;ContainerType



  • Config has changed, clear StaleIsFalse Alarm.

9

24

Alarm

uxAlmQoENotifyMessageResponseWasNotSuccessful1.3.6.1.4.1.177.15.2.589848

QoE Notify Message response was not successful

Communication

SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType

Minor

(tick)

  • QoE Notify Message received a no response or a failed response.
  • This alarm will be cleared by the event 'QoE Notify Message received a successful response'.

9

25

Event

uxAlmQoENotifyMessageResponseWasSuccessful1.3.6.1.4.1.177.15.2.589849

QoE Notify Message Response was successful

Communication

SG;PodName;ContainerType


(tick)

  • QOE Notify Message received a successful response.

9

26

Alarm

uxAlmSystemOverloadDetected1.3.6.1.4.1.177.15.2.589850

System overload detected

Communication

System;Service;PodName;ContainerType

Minor

(tick)

  • System processing is overloaded.

9

27

Event

uxAlmSystemOverloadCleared1.3.6.1.4.1.177.15.2.589851

System overload cleared

Communication

System;Service;PodName;ContainerType



  • System processing resumes standard operation, overload cleared.

9

28

Alarm

uxAlmMaximumNumberofSIPSessionsReached1.3.6.1.4.1.177.15.2.589852

Maximum Number of SIP Sessions Reached

Communication

SG;PodName;ContainerType

Minor

(tick)

  • The maximum number of SIP sessions (calls/register/subscribe) has been reached on the signaling group.
  • Increase the number of SIP Channels for the signaling group.

9

29

Event

uxAlmMaximumNumberofSIPSessionsAlarmCleared1.3.6.1.4.1.177.15.2.589853

Maximum Number of SIP Sessions Alarm Cleared

Communication

SG;PodName;ContainerType



  • SIP sessions per signaling group is under the maximum limit.

9

30

Alarm

uxAlmErrorresolvingSRVrecord1.3.6.1.4.1.177.15.2.589854

Error resolving SRV record

Communication

SIPCluster;ServID;PodName;ContainerType

Major

(tick)

  • Failed to run SRV record query.
  • Suggested action - confirm that DNS server network is reachable, check SRV and DNS server configuration.

9

31

Event

uxAlmSRVrecordresolved1.3.6.1.4.1.177.15.2.589855

SRV record resolved

Communication

SIPCluster;ServID;PodName;ContainerType

None


  • DNS server returned valid SRV record(s).
932AlarmuxAlmSIPTLSHandshakeNegotiationStartFailure1.3.6.1.4.1.177.15.2.589856SIP-TLS Handshake Negotiation Start FailureSecurityTLSProfile;IPAddress;PodName;ContainerTypeCritical(tick)
  • [server] handshake failed to start with invalid certificate; [connectionID], [portID].
  • Action: confirm that both signed Ribbon SBC Edge Certificate and Trusted CA Certificate exist.
933EventuxAlmSIPTLSHandshakeNegotiationStartSuccessful1.3.6.1.4.1.177.15.2.589857SIP-TLS Handshake Negotiation Start SuccessfulSecurityTLSProfile;IPAddress;PodName;ContainerTypeNone(tick)
  • Handshake response was started with valid certificate on local and remote gateway.
  • This event clears the 'SIP-TLS Handshake Negotiation Start Failure' alarm.
934EventuxAlmMaximumsupportedSIPSGsreached1.3.6.1.4.1.177.15.2.589858Maximum supported SIP SGs reachedGeneralSystem;Service;PodName;ContainerTypeWarning(tick)
  • SIP signaling group count reached maximum supported limit.
935EventuxAlmMaximumsupportedSIPSGscleared1.3.6.1.4.1.177.15.2.589859Maximum supported SIP SGs cleared

General

System;Service;PodName;ContainerTypeNone
  • SIP signaling group count is under the maximum supported.
936AlarmuxAlmMaximumnonSIPCallSessionsreached1.3.6.1.4.1.177.15.2.589860Maximum non-SIP call sessions reachedGeneralSystem;Service;PodName;ContainerTypeWarning(tick)
  • Number of SIP non-call sessions is over the system capacity.
937EventuxAlmMaximumnonSIPCallSessionscleared1.3.6.1.4.1.177.15.2.589861Maximum non-SIP call sessions clearedGeneralSystem;Service;PodName;ContainerTypeNone
  • Number of SIP non-call sessions is under the system capacity.
938AlarmuxAlmMaximumSIPCallSessionsreached1.3.6.1.4.1.177.15.2.589862Maximum SIP call sessions reachedGeneralSystem;Service;PodName;ContainerTypeWarning(tick)
  • Number of SIP call sessions is over the system capacity.
939EventuxAlmMaximumSIPCallSessionscleared1.3.6.1.4.1.177.15.2.589863Maximum SIP call sessions clearedGeneralSystem;Service;PodName;ContainerTypeNone
  • Number of SIP call sessions is under the system capacity.
940AlarmuxAlmBroadsoftSIPCallrerouted1.3.6.1.4.1.177.15.2.589864Broadsoft SIP call re-routedGeneralSG;PodName;ContainerTypeWarning(tick)
  • Broadsoft SIP call re-routed.
941EventuxAlmBroadsoftSIPCallReroutedcleared1.3.6.1.4.1.177.15.2.589865Broadsoft SIP Call re-routed clearedGeneralSG;PodName;ContainerTypeNone
  • Broadsoft SIP call re-routed cleared.
942AlarmuxAlmSIPSGListenProtocolandSIPServerHostProtocolmismatch1.3.6.1.4.1.177.15.2.589866SIP SG Listen Protocol and SIP Server Host Protocol mismatchProcessingSIPCluster;ServID;PodName;ContainerTypeMinor
  • Verify that the listen ports and protocols for the SG match those in the server table.
943AlarmuxAlmConfigurationErrorSIPSGandServerProtocolMismatch1.3.6.1.4.1.177.15.2.589867Configuration Error: SIP SG and Server Protocol MismatchProcessingSIPCluster;ServerID or SIPCluster;ServID;PodName;ContainerTypeMajor
  • Verify that the listen ports and protocols for the SG match those in the server table.
944AlarmuxAlmSIPTLSClientHandshakeFailure1.3.6.1.4.1.177.15.2.589868SIP-TLS Client Handshake FailureSecurityTLSProfile;IPAddress;PodName;ContainerTypeMinor(tick)
  • TLS client handshake failed with alert code.
  • Action: Refer to Error Alerts in RFC 5246 for the problem.
945EventuxAlmSIPTLSHandshakeInactivityTimeoutCleared1.3.6.1.4.1.177.15.2.589869SIP-TLS Handshake Inactivity Timeout ClearedSecurityTLSProfile;IPAddress;PodName;ContainerType

  • Handshake response was received within specified timeout.
  • This event clears the 'SIP-TLS Handshake Inactivity Timeout Failure' alarm.
946EventuxAlmSIPTLSServerHandshakeFailureCleared1.3.6.1.4.1.177.15.2.589870SIP-TLS Server Handshake Failure ClearedSecurityTLSProfile;IPAddress;PodName;ContainerType

  • Handshake failure error alert condition was cleared.
  • This event clears the 'SIP-TLS Server Handshake Failure' alarm. 
947EventuxAlmSIPTLSClientHandshakeFailureCleared1.3.6.1.4.1.177.15.2.589871SIP-TLS Client Handshake Failure ClearedSecurityTLSProfile;IPAddress;PodName;ContainerType

  • Handshake failure error alert condition was cleared.
  • This event clears the 'SIP-TLS Client Handshake Failure' alarm. 
948AlarmuxAlmSkypeLyncPresenceServerResponseFailure1.3.6.1.4.1.177.15.2.589872

Skype/Lync Presence Server Response Failure


CommunicationSIPCluster;PodName;ContainerTypeMinor(tick)
  • A Presence Publish Request has been sent to the configured Lync Presence Front End and has received no response or a failed response.
949AlarmuxAlmSkypeLyncPresenceServerResponseFailureCleared1.3.6.1.4.1.177.15.2.589873Skype/Lync Presence Server Response Failure ClearedCommunicationSIPCluster;PodName;ContainerTypeMinor(error)
  • A presence server that previously was unreachable has successfully sent a message that the SBC has received.
950AlarmuxAlmSIPRequestfromUntrustedIP1.3.6.1.4.1.177.15.2.589874SIP Request from Untrusted IPSecurityIPAddress;PodName;ContainerType Minor
  • An INVITE message was received from a host without a matching Federated IP.
951AlarmuxAlmSIPRequestfromUntrustedIPCleared1.3.6.1.4.1.177.15.2.589875SIP Request from Untrusted IP ClearedGeneralIPAddress;PodName;ContainerTypeMajor
  • Source IP is added to the list of federated IP addresses.
952AlarmuxAlmReSyncmessagereceivedonSGnotselectedforAutoConfigtask1.3.6.1.4.1.177.15.2.589876Resync message received on SG, not selected for Auto Config task.ProcessingSG;PodName;ContainerTypeMajor
  • Check Auto configuration Task settings and verify that the Signaling Group selected is correct.
953AlarmuxAlmMaximumNumberofSkypeLyncPresenceSessionsReached1.3.6.1.4.1.177.15.2.589877Maximum Number of Skype/Lync Presence Sessions ReachedCommunicationSG;PodName;ContainerTypeMinor(tick)
  • The maximum number of 500 concurrent SIP Publish sessions for Presence has been reached.
  • Skype/Lync Presence processing will be suspended until the number of concurrent sessions drops below 500 limit.
954EventuxAlmMaximumNumberofS4BPresencePublishSessionsAlarmCleared1.3.6.1.4.1.177.15.2.589878Maximum Number of S4B Presence Publish Sessions Alarm ClearedCommunicationSG;PodName;ContainerType
(tick)
  • SIP Publish sessions for S4B Presence is under the maximum limit.
955AlarmuxAlmEnableMonitoringonSkypePresenceServerforbetterreliability1.3.6.1.4.1.177.15.2.589879Enable Monitoring on Skype Presence Server for better reliabilityCommunicationSIPCluster;PodName;ContainerTypeMinor(tick)
  • Enable Monitoring on Skype Presence Server for better reliability.
956EventuxAlmMonitoringonSkypePresenceServerhasbeenenabled1.3.6.1.4.1.177.15.2.589880Monitoring on Skype Presence Server has been enabledCommunicationSIPCluster;PodName;ContainerType

  • Monitoring on Skype Presence Server has been enabled.
957AlarmuxAlmTheSIPVoiceQualityServerConnectionisBroken1.3.6.1.4.1.177.15.2.589881The SIP Voice Quality Server Connection is BrokenCommunicationProtocol;IPAddress;Port;PodName;ContainerTypeMajor(tick)
  • Suggested Action: Verifying the IP, Port, Protocol, and Certificate (if TLS) are Correct.
958EventuxAlmTheSIPVoiceQualityServerConnectionisResumed1.3.6.1.4.1.177.15.2.589882The SIP Voice Quality Server Connection is ResumedCommunicationProtocol;IPAddress;Port;PodName;ContainerType

  • The SIP Voice Quality Server Connection is Resumed.
959AlarmuxAlmTheVoiceQualityNotifyRejectedbytheSIPVoiceQualityServer1.3.6.1.4.1.177.15.2.589883The Voice Quality Notify Rejected by the SIP Voice Quality ServerCommunicationIPAddress;Port;PodName;ContainerTypeWarning(tick)
  • Suggested Action: Examining the Notify Response Code and the Reason Header (if included) to understand why it was rejected.
960AlarmuxAlmTheVoiceQualityNotifyAcceptbyTheSIPVoiceQualityServer1.3.6.1.4.1.177.15.2.589884The Voice Quality Notify Accept by the SIP Voice Quality ServerCommunicationIPAddress;Port;PodName;ContainerType

  • The Voice Quality Notify has been accepted by the SIP Voice Quality Server.
961AlarmuxAlmFailedtoResolvetheFQDNoftheSIPVoiceQualityServer1.3.6.1.4.1.177.15.2.589885Failed to Resolve the FQDN of the SIP Voice Quality ServerCommunicationIPAddress;PodName;ContainerTypeWarning
  • Failed to Resolve FQDN of the SIP Voice Quality Server.
  • Suggested action - confirm the DNS access and FQDN.
962EventuxAlmtheSIPVoiceQualityServerFQDNhasbeenResolved1.3.6.1.4.1.177.15.2.589886The SIP Voice Quality Server FQDN has been ResolvedCommunicationIPAddress;PodName;ContainerType

  • The SIP Voice Quality Server FQDN has been resolved.
963AlarmuxAlmConfiguredRegistrationLimitreached1.3.6.1.4.1.177.15.2.589887Configured Registration Limit ReachedCommunicationSIPRegistrarTable;PodName;ContainerTypeWarning(tick)
  • Configured Registration Limit reached.
  • New SIP Registrations will be rejected until the number of registered users drops below maximum number of users configured for the Registrar.
964EventuxAlmConfiguredRegistrationLimitCleared1.3.6.1.4.1.177.15.2.589888Configured Registration Limit ClearedCommunicationSIPRegistrarTable;PodName;ContainerType

  • Configured Registration Limit cleared.
965AlarmuxAlmSignalingMediasourceIPissettoAuto1.3.6.1.4.1.177.15.2.589889Signaling/Media source IP is set to AutoCommunicationSG;PodName;ContainerTypeMinor(tick)
  • Signaling/Media source IP is set to Auto and default route uses Admin interface.
966EventuxAlmSignalingMediasourceIPissettoAutocleared1.3.6.1.4.1.177.15.2.589890Signaling/Media source IP is set to Auto clearedCommunicationSG;PodName;ContainerType

  • Signaling/Media source IP is set to Auto cleared.
967AlarmuxAlmSIPRecordingServerNotResponding1.3.6.1.4.1.177.15.2.589891SIP Recording Server Not RespondingCommunicationSIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerTypeMajor(tick)
  • SIP Recording server has failed to respond and has been taken out of service.
  • This alarm will be cleared by the event 'SIP Recording server became responsive'.
968EventuxAlmSIPRecordingServerBecameResponsive1.3.6.1.4.1.177.15.2.589892SIP Recording Server Became ResponsiveCommunication

SIPCluster;ServID;Protocol;IPAddress;Port;PodName;ContainerType




  • SIP Recording server came up.
969AlarmuxAlmSCSLBconnectionisdown1.3.6.1.4.1.177.15.2.589893SC-SLB connection is downCommunicationSystem;PodName;ContainerTypeCritical(tick)
  • Signaling container connection with SLB container is down.
970EventuxAlmSCSLBconnectionisup1.3.6.1.4.1.177.15.2.589894SC-SLB connection is upCommunicationSystem;PodName;ContainerType

  • Signaling container connection with SLB container is up.
971AlarmuxAlmSCCACconnectionisdown1.3.6.1.4.1.177.15.2.589895SC-CAC connection is downCommunicationSystem;PodName;ContainerTypeMajor(tick)
  • Signaling container connection with CAC Manager is Down.
  • Node: [nodename].
  • Login into CAC Manager Pod debug CLI to verify current operational status.
972EventuxAlmSCCACconnectionisup1.3.6.1.4.1.177.15.2.589896SC-CAC connection is upCommunicationSystem;PodName;ContainerType

  • Signaling container connection with CAC Manager is Up.
  • Node: [nodename].
973AlarmuxAlmCallAccessControlDenied1.3.6.1.4.1.177.15.2.589897Call Access Control DeniedCommunicationSG;PodName;ContainerTypeWarning(tick)
  • Call Access Control Denied Over [num] percent calls: Rejects: [num] Timeouts: [num] Sendfail: [num] Unknown: [num].
974AlarmuxAlmSLBDiscoveryFailure1.3.6.1.4.1.177.15.2.589898SLB Discovery FailureCommunicationSystem;PodName;ContainerTypeCritical(tick)
  • SLB discovery failure because of kubeapi failure.
975EventuxAlmSLBDiscoverySuccess1.3.6.1.4.1.177.15.2.589899SLB Discovery SuccessCommunicationSystem;PodName;ContainerTypeMajor
  • SLB Discovery Success.
976AlarmuxAlmMediaIPAssociationfailed1.3.6.1.4.1.177.15.2.589900Media IP Associated failedCommunicationInterface;PodName;ContainerTypeMajor
  • Public IP Association to SC failed.
977EventuxAlmMediaIpAssociationsuccessful1.3.6.1.4.1.177.15.2.589901Media IP Association SuccessfulCommunicationInterface;PodName;ContainerType

  • Public IP Association to SC successful: [ip address].
978AlarmuxAlmSignalingContainerMemoryreachedThreshold1.3.6.1.4.1.177.15.2.589902Signaling Container Memory reached ThresholdCommunicationInterface;PodName;ContainerTypeMajor(tick)
  • Signaling container memory reached above [percent] percent threshold.
979EventuxAlmSignalingContainerMemoryRechedBelowThreshold1.3.6.1.4.1.177.15.2.589903Signaling Container Memory Reched Below ThresholdCommunicationInterface;PodName;ContainerType

  • Signaling container memory reached below threshold.
980EventuxAlmCallAccessControlDeniedCleared1.3.6.1.4.1.177.15.2.589904Call Access Control Denied ClearedCommunicationSG;PodName;ContainerType

  • Call Access Control Denied condition cleared.
  • No labels