1

1

Alarm

AD caching failed

Communication

System;Service;IPAddress;PodName;ContainerType

Minor

• Failed to cache attributes from AD in memory.
• Suggested action - try again later.
• This alarm will be cleared by event AD caching successful.

1

2

Event

Online AD query failed

Communication

System;Service;PodName;ContainerType

• Failed to run AD query.
• Suggested action - confirm that AD is network reachable, check the AD configuration as well as AD access credentials.

1

4

Event

User logged in

Security

Username;IPAddress;PodName;ContainerType

• Specified user logged in.

1

5

Alarm

User login failed

Security

Username;IPAddress;PodName;ContainerType

Major

• Specified user login failed on [time] due to [reason].
• This alarm will be cleared by event User logged in.

1

6

Alarm

AD Unreachable

Communication

System;Service;IPAddress;DCType;PodName;ContainerType

Major

• Either AD is network unreachable, or the AD credentials are invalid.
• This alarm will be cleared by 'AD Reachable' event.

1

7

Event

AD Reachable

Communication

System;Service;IPAddress;DCType;PodName;ContainerType

• Active directory is now reachable.

1

8

Event

AD caching successful

Communication

• AD caching was successful.

1

9

Alarm

AD backup failed

Equipment

System;Service;IPAddress;PodName;ContainerType

Minor

• Failed to backup cached values from AD to storage device.
• Either the storage device is not present, or it is full.
• Contact Ribbon Service for further assistance.

1

10

Event

AD successfully backed up

Equipment

System;Service;IPAddress;PodName;ContainerType

• Successful backup of cached values from AD to storage device.

1

11

Alarm

AD cache truncated

Equipment

System;Service;PodName;ContainerType

Minor

• AD Cache is truncated, AD cache results have exceeded the maximum cache size.
• Consider caching only the required attributes.
• If the query is not found in cache, Online query will be performed, while affecting performance.

1

12

Alarm

RADIUS Server Unreachable

Communication

System;Service;IPAddress;PodName;ContainerType

Major

• Either the RADIUS server is network unreachable, the configuration is incorrect, or due to service impacting change.
• Suggested action - check shared secret, listening port, RADIUS server IP.
• This alarm will be cleared by 'RADIUS Reachable' event.

1

13

Event

RADIUS Reachable

Communication

System;Service;IPAddress;PodName;ContainerType

• RADIUS server is online.

1

14

Alarm

CDR logging failed

Communication

System;Service;IPAddress;PodName;ContainerType

Major

• SBC Edge failed to send CDR to RADIUS based accounting server.
• Either the server is network unreachable, or the configuration is incorrect.
• Suggested action - check shared secret, listening port, RADIUS server IP.

1

15

Alarm

CDR backup failed

Communication

System;Service;IPAddress;PodName;ContainerType

Major

• SBC Edge failed to backup CDR in local file.
• Either running with low disk space or CDR backup maximum limit is crossed.
• Suggested action - Free up the disk space or save the CDR Queued file for future reference.

1

17

Event

User password changed successfully

Security

Username;PodName;ContainerType

• Password changed successfully by [username] from [ipAddress].

1

18

Alarm

User password change failed

Security

Username;PodName;ContainerType

Warning

• Password change attempted by [username] from [ipAddress] failed.

1

19

Event

User account disabled

Security

Username;PodName;ContainerType

• Account has been disabled by [username] from [ipAddress].

1

20

Event

User account activated

Security

Username;PodName;ContainerType

• Account has been activated by [username] from [ipAddress].

1

21

Event

Global Security Options Changed

Security

Username;IPAddress;PodName;ContainerType

• Global security options changed.

1

22

Alarm

User login blocked

Security

Username;PodName;ContainerType

Major

• User attempting to log in from [ipAddress] blocked due to excessive incorrect login attempts.

1

23

Event

User login unblocked

Security

Username;PodName;ContainerType

• User login is unblocked.

Username;IPAddress;PodName;ContainerType

• Password has expired.
• User [username] logging in from [ipAddress] password is expired.

System;Service;PodName;ContainerType

• AD has reached maximum threads. Please inform your service representative.

System;Service;IPAddress;PodName;ContainerType

• Timed out caching attributes due to lack of response from AD.
• Suggested action - try again later.
• The SBC will attempt to load the last successful cache from backup.

System;Service;IPAddress;PodName;ContainerType

• AD Cache encryption failed.
• Cache will not be saved.

System;Service;IPAddress;PodName;ContainerType

AD Cache encryption successful.

2

1

Alarm

Invalid Card ID EEPROM Data

Equipment

System;Card;PodName;ContainerType

Critical

• A Card was detected with invalid Card ID EEPROM (failed CRC-CCITT check).
• Suggested action - provide the entire alarm message including the numbers at the end to Ribbon Service for further assistance.

2

2

Alarm

Card Health Check Failed

Equipment

System;Card;PodName;ContainerType

Critical

• During Line Card activation, a Card Fault was detected after power was applied to the card.
• The Card will remain out-of-service.
• Suggested action - reboot system.
• If issue persists, contact Ribbon Service with the alarm information.

2

3

Alarm

Card not Supported

Equipment

System;Card;PodName;ContainerType

Major

• A Card was detected which can be identified, but the SBC Edge software is unable to support.
• The Card will remain out-of-service.
• Suggested action - reboot system.
• If issue persists, contact Ribbon Service with the alarm information.

2

4

Alarm

Power Supply input failure

Equipment

System;PSU;PodName;ContainerType

Major

• A Power supply module has indicated a failure of input power.
• The SBC Edge has lost Power Supply redundancy.
• Suggested action - Verify that the power cable is connected and that the PS is functioning properly.

2

5

Event

Power Supply input restored

Equipment

System;PSU;PodName;ContainerType

• A Power Supply module has indicated that input power has been restored.
• This event clears the "Power Supply Input Failure" Alarm.

2

6

Alarm

Power Supply output failure

Equipment

System;PSU;PodName;ContainerType

Major

• A Power Supply module has indicated a failure of output power.
• The SBC Edge has lost Power Supply redundancy.
• Suggested action - Verify that the PS is functioning properly.

2

7

Alarm

Single Fan failure

Equipment

System;Fan;PodName;ContainerType

Major

• Check the System tab to find the Fan ID of the failed fan.
• Contact Ribbon Service with this information.

2

8

Alarm

Multiple Fan Failures

Equipment

System;Fans;PodName;ContainerType

Critical

• Check the System tab to find the Fan ID's of the failed fans.
• Contact Ribbon Service with this information.

2

9

Alarm

System Temperature Warm

Equipment

System;PodName;ContainerType

Minor

• The temperature sensors have indicated that the system is running warm (55°C threshold).

2

10

Event

System Temperature Warm Cleared

Equipment

System;PodName;ContainerType

• The temperature sensors have indicated that the system is no longer running warm (55°C threshold).
• This event clears the 'System Temperature Warm' Alarm.

2

11

Alarm

System Temperature Hot

Equipment

System;PodName;ContainerType

Critical

• The temperature sensors have indicated that system is running hot (65°C threshold).

2

12

Event

System Temperature Hot Cleared

Equipment

System;PodName;ContainerType

• The temperature sensors have indicated that the system is no longer running hot (65°C threshold).
• This event clears the 'System Temperature Hot' Alarm.

3

1

Alarm

Licenses expired

General

System;Service;PodName;ContainerType

Critical

• License of the node has expired, all the licensed features would fail to work.
• Contact Ribbon Enterprise Sales.

3

2

Alarm

License will expire in 14 days

General

System;Service;PodName;ContainerType

Major

• License of the node will expire in 2 weeks.

3

3

Event

New License applied.

General

System;Service;PodName;ContainerType

• New License is applied on the node.

3

4

Alarm

Failed to Apply License.

General

System;Service;PodName;ContainerType

Critical

• Either an invalid key is used, or the license key applies to a different node, or the license key expiry is past the present date.
• Contact Ribbon Sales to obtain a new license.

3

5

Alarm

Failed to acquire license.

General

System;Service;PodName;ContainerType

Minor

• Either [license type] are unlicensed, or all license(s) are exhausted.

System;Service;PodName;ContainerType

• The alarm is generated when the license key applied has more DS1 ports licensed than are installed in the system.
• The number of BRI ports installed will get activated.
• As a fix, obtain a license with the correct number of DS1 ports.

System;Service;PodName;ContainerType

• The alarm is generated when the license key applied has more BRI ports licensed than are installed in the system.
• The number of BRI ports installed will get activated.
• As a fix, obtain a license with the correct number of BRI ports.

System;Service;PodName;ContainerType

• The alarm is generated when the license key applied has more FXS ports licensed than are installed in the system.
• The number of FXS ports installed will get activated.
• As a fix, obtain a license with the correct number of FXS ports.

System;Service;PodName;ContainerType

• The alarm is generated when the license key applied has more FXO ports licensed than are installed in the system.
• The number of FXO ports installed will get activated.
• As a fix, obtain a license with the correct number of FXO ports.

• Failed to get key for license generation.

• SIP Signaling Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).

• SIP Registration Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).

Enhanced Media Sessions with Transcoding exceeds system capability.

• SIP Media Sessions Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).

Enhanced Media Sessions w/o Transcoding exceeds system capability.

• Proxy Local SRTP Media Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).

• SIP RTP Proxy Sessions of [number] licenses exceeds the capability of the system of [number] licenses.

• SIP Video Sessions of [number] licenses exceeds the capability of the system of [number] licenses. As a fix, obtain a license with correct number of SIP Video Sessions.

• SIP High Capacity (250+) Sessions of [number] licenses exceeds the capability of the system of [number] licenses.

• As a fix, obtain a license with correct number of SIP High Capacity Sessions.

• The license includes 250 or more SIP Sessions but no High Capacity Enabled license.
• Obtain a High Capacity Enabled license to use these additional sessions.

• An Azure-enabled license has been successfully installed.

• License Version 2 is unsupported.

• Please contact Ribbon Support for a free feature equivalent License Version 3 immediately.
• Roll back to the previous partition until this license is available.

• SILK Transcoding Sessions of [number] licenses exceeds the capability of the system of [number] (Allocated Media Ports).

Licensed SIPREC Sessions exceeds system capability.

• SIPREC Sessions of [number] licenses exceeds the capability of the system of [number].

Online License Mode Conflict

• Management platform indicates NWDL mode, but no NWDL license received.
• Review the management platform license server to resolve.

• NWDL license applied.
• This clears the online license mode conflict alarm.

• Feature: [feature string] : [line ID] expired.
• Please check the Current License page.

• Invalidating [license type] licenses.

5

1

Alarm

ASM Unreachable

Communication

SBA Instance;PodName;ContainerType

Critical

• ASM system can not be reached, system is down.
• Check whether the ASM is rebooting.

5

2

Event

Clear ASM Unreachable

Communication

SBA Instance;PodName;ContainerType

• Clears alarm 'ASM Unreachable'.

5

3

Alarm

ASM Failure Recovered

Equipment

SBA Instance;PodName;ContainerType

Warning

• ASM system was previously unreachable, but has come up.
• This alarm doesn't autoclear so the user can investigate the cause, but the system should be working correctly now.

5

4

Alarm

ASM Services Not Running

Processing

SBA Instance;PodName;ContainerType

Critical

• ASM services are not running, calls through the ASM cannot be placed.

5

5

Event

Clear ASM Services Not Running

Processing

SBA Instance;PodName;ContainerType

• Clears alarm 'ASM Services Not Running'.

5

6

Alarm

ASM Services Restarted

Processing

SBA Instance;PodName;ContainerType

Warning

• ASM Services was previously stopped, but has started.
• This alarm doesn't autoclear so the user can investigate the cause, but ASM Services should be working correctly now.

5

7

Alarm

ASM Service Restart Failed

Processing

SBA Instance;PodName;ContainerType

Critical

• The system attempted to restart a failed service on the ASM, service did not start successfully.
• User interaction is required.

5

8

Event

ASM System Started

Processing

SBA Instance;PodName;ContainerType

• This event is set when the SBA communication system is first established, and usually indicates that the Application Solution Module (ASM) has finished booting.
• It should come up at system startup, it may come again if the ASM hardware is rebooted.

5

9

Event

ASM System Shutting down

Processing

SBA Instance;PodName;ContainerType

• A planned or deliberate shut down is taking place on the Application Solution Module (ASM).

5

10

Alarm

Ethernet Link Down

Equipment

SBA Instance;Port;PodName;ContainerType

Major

• Ethernet port specified has lost link.
• Source Instance: Eth0/Eth1 via SBA Monitor.

5

11

Event

Ethernet Link Up

Equipment

SBA Instance;Port;PodName;ContainerType

• Ethernet port specific has recovered link.

5

12

Alarm

ASM-SBC IP Subnet Mismatch

Equipment

SBA Instance;PodName;ContainerType

Critical

• The ASM and SBC Edge IP interfaces are in different subnets and cannot communicate.

5

13

Event

ASM-SBC IP Subnet Match

Equipment

SBA Instance;PodName;ContainerType

• The ASM and SBC Edge IP interfaces are in the same subnet and can now communicate.

• The QoE database is unreachable from ASM, make sure Skype for Business Server or Skype/Lync is deployed and Monitoring database is running.

• The QoE database is now reachable from ASM.

• Failed to store the QoE information from ASM.

• The ASM hasn't been able to apply the CAC update.

• ASM-SBC CAC Update applied.

• ASM Windows Server is not able to activate as genuine Microsoft product.
• Unlicensed ASM sends the alarm.
• The alarm is removed after the license key is successfully installed and the ASM module is restarted.

• NFS mounting of ASM drive failed, make sure ASM module is up and NFS service is running on the ASM module.
  

• ASM hard drive is NFS mounted and available.
  

• ASM Windows Server is activated as genuine Microsoft product.

5

23

Alarm

ASM IP Address conflict

Equipment

SBA Instance;PodName;ContainerType

Critical

• The current ASM IP [ipAddress] is in use by a [address] ('MAC address'), Change the [address] IP 'Is PowerCycle required' and retry.

5

24

Event

Clear ASM IP address conflict

Equipment

SBA Instance;PodName;ContainerType

• ASM IP address conflict cleared.

• ASM Ethernet Port has been detected down.

• ASM Ethernet Port has been detected down is cleared.

• ASM ([SbcCommsVersion]) and SBC ([SBCVersion]) firmware version does not match.

• ASM and SBC firmware version does not match is cleared.

7

1

Event

Configuration change occurred on Action Set

General

ActSetTble;PodName;ContainerType

• Action set modified [id].

7

2

Event

Configuration change occurred on Normalization Table

General

NormTble;PodName;ContainerType

• There is a normalization table number/name that should be printed with this event.

7

3

Event

Configuration change occurred on Route Table

General

RtTble;PodName;ContainerType

• Routing table modified [id].

7

4

Event

Configuration change occurred on Transformation Tables

General

TransTble;PodName;ContainerType

• Transformation table modified [id].

7

5

Alarm

Route temporarily disabled

Communication

RtTble;PodName;ContainerType

Warning

• Route temporarily disabled due to signaling group(s) down.

7

6

Event

Route enabled

Communication

RtTble;PodName;ContainerType

• Route enabled as the signaling group is up.

7

7

Alarm

A Call exceeded the limit for number of destinations

Communication

CallDest;PodName;ContainerType

Warning

• Maximum (8) call forks exceeded, no more forks for this destination

7

8

Alarm

Call forking used with no forking license

Communication

CallDest;PodName;ContainerType

Warning

• Call forking used with no forking license.

7

9

Alarm

Invocation of InvokeActionSet exceeded the maximum nesting limit

Communication

CallDest;PodName;ContainerType

Warning

• Maximum (10) nested InvokeActionSet exceeded.

7

10

Event

Configuration change occurred on Callback Tables

General

CallbackTble;PodName;ContainerType

• Callback table [id] modified.

8

1

Event

Channel is in service

Communication

Card;Port;Channel;PodName;ContainerType

• Channel is up and is in service.
• This clears the 'Channel out of service' alarm.

8

2

Alarm

Channel is out of service

Communication

Card;Port;Channel;PodName;ContainerType

Minor

• Channel Out Of Service Alarm.
• This alarm is automatically cleared when Channel is in service.

8

3

Alarm

Emergency Call Attempted

Communication

Number;Extension;IPAddress;PodName;ContainerType

Minor

• Specified emergency call is attempted, AttempTime: [time].

8

4

Event

Emergency Call Completed

Communication

Number;Extension;IPAddress;PodName;ContainerType

• Emergency Call completed.
• The alarm will be cleared after expiry time in emergency status table.

QoE report not sent due to RTCP Media List

• QoE Report for the Signaling Group not sent.
• To enable QoE report for this Signaling Group, check the Media List associated with the SG and set RTCP Mode to RTCP-XR.

• The call is not in DSP mode - hence the call transfer could not be honored.
• Set Agent Type as Access Mode to pass through the SIP REFER.

• The call failed due to Media Mode mismatch across SG and Call Route configuration.

• SG set to Drain Mode, all channels are idle.

• Non-Emergency Call Preempted due to an Emergency Call Attempt.

uxAlmLicensedEnhancedMediaSessionswithTranscodingcountreached

• Number of licensed Enhanced Media Sessions with Transcoding has been reached.

uxAlmSRTPCallAttemptedNoLicenseAvailable

• Either Enhanced Media Session without Transcoding is not licensed on this node, or the license count has reached zero.

• AMR Wideband call attempted but not licensed.

• Maximum call duration exceeded for call and call has been disconnected.

• Country Code is unavailable. Ribbon Protect Bad Actors detection will be impacted.

• Country Code is Available.

• Number of licensed SILK transcoded media session has been reached.

9

1

Alarm

SIP Server not responding

Communication

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

Major

• 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

Signaling Group taken out of service

Communication

SG;PodName;ContainerType

Critical

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

9

3

Event

Signaling Group disabled

Communication

SG;PodName;ContainerType

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

9

4

Alarm

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

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

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

SIP Server became responsive

Communication

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

• SIP server came up.

9

8

Alarm

SIP cluster went down

Communication

SIPCluster;PodName;ContainerType

Major

• 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

SIP Cluster enabled

Communication

SIPCluster;PodName;ContainerType

• SIP cluster enabled.

9

10

Event

SIP Signaling group enabled

Communication

SG;PodName;ContainerType

• SIP Signaling group enabled.

9

11

Alarm

SIP Signaling Group: DNS Failure

Communication

SG;PodName;ContainerType

Major

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

9

12

Event

SIP Signaling Group: FQDN Resolved

Communication

SG;PodName;ContainerType

• Successfully resolved the FQDN of the SIP Signaling group.

9

13

Alarm

SIP Server: DNS Failure

Communication

SIPCluster;ServID;PodName;ContainerType

Major

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

9

14

Event

SIP Server: FQDN Resolved

Communication

SIPCluster;ServID;PodName;ContainerType

• SIP Server config FQDN resolved.

9

15

Alarm

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

Acquiring license for Register failed

Communication

SG;PodName;ContainerType

Major

• Failed to acquire license from License Manager.

• SIP performs self-check for leaks.
• Please enable logging for SIP and issue 'show resources' command.

• Failed to bind to network interface due to dynamic IP address not available.

• Successfully bound to network interface.
• DHCP lease renewed.

• SIP Register server has failed to respond.
• This alarm will be cleared by the event 'SIP Regular server became responsive'.

• SIP Register server came up.

9

22

Alarm

Registration not valid; received stale=false

Communication

SG;AorName;PodName;ContainerType

Major

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

9

23

Event

Config change for SIP endpoint that received stale=false

Communication

SG;AorName;PodName;ContainerType

• Config has changed, clear StaleIsFalse Alarm.

9

24

Alarm

QoE Notify Message response was not successful

Communication

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

Minor

• 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

QoE Notify Message Response was successful

Communication

SG;PodName;ContainerType

• QOE Notify Message received a successful response.

9

26

Alarm

System overload detected

Communication

System;Service;PodName;ContainerType

Minor

• System processing is overloaded.

9

27

Event

System overload cleared

Communication

System;Service;PodName;ContainerType

• System processing resumes standard operation, overload cleared.

9

28

Alarm

Maximum Number of SIP Sessions Reached

Communication

SG;PodName;ContainerType

Minor

• 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

Maximum Number of SIP Sessions Alarm Cleared

Communication

SG;PodName;ContainerType

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

9

30

Alarm

Error resolving SRV record

Communication

SIPCluster;ServID;PodName;ContainerType

Major

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

9

31

Event

SRV record resolved

Communication

SIPCluster;ServID;PodName;ContainerType

None

• DNS server returned valid SRV record(s).

• Handshake response was started with valid certificate on local and remote gateway.
• This event clears the 'SIP-TLS Handshake Negotiation Start Failure' alarm.

• SIP signaling group count reached maximum supported limit.

General

• SIP signaling group count is under the maximum supported.

• Number of SIP non-call sessions is over the system capacity.

• Number of SIP non-call sessions is under the system capacity.

• Number of SIP call sessions is over the system capacity.

• Number of SIP call sessions is under the system capacity.

• Broadsoft SIP call re-routed.

• Broadsoft SIP call re-routed cleared.

• Verify that the listen ports and protocols for the SG match those in the server table.

• Verify that the listen ports and protocols for the SG match those in the server table.

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

• Handshake response was received within specified timeout.
• This event clears the 'SIP-TLS Handshake Inactivity Timeout Failure' alarm.

• Handshake failure error alert condition was cleared.
• This event clears the 'SIP-TLS Server Handshake Failure' alarm. 

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

Skype/Lync Presence Server Response Failure

• A Presence Publish Request has been sent to the configured Lync Presence Front End and has received no response or a failed response.

• A presence server that previously was unreachable has successfully sent a message that the SBC has received.

• An INVITE message was received from a host without a matching Federated IP.

• Source IP is added to the list of federated IP addresses.

• Check Auto configuration Task settings and verify that the Signaling Group selected is correct.

• 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.

• SIP Publish sessions for S4B Presence is under the maximum limit.

• Enable Monitoring on Skype Presence Server for better reliability.

• Monitoring on Skype Presence Server has been enabled.

• Suggested Action: Verifying the IP, Port, Protocol, and Certificate (if TLS) are Correct.

• The SIP Voice Quality Server Connection is Resumed.

• Suggested Action: Examining the Notify Response Code and the Reason Header (if included) to understand why it was rejected.

• The Voice Quality Notify has been accepted by the SIP Voice Quality Server.

• Failed to Resolve FQDN of the SIP Voice Quality Server.
• Suggested action - confirm the DNS access and FQDN.

• The SIP Voice Quality Server FQDN has been resolved.

• 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.

• Configured Registration Limit cleared.

• Signaling/Media source IP is set to Auto and default route uses Admin interface.

• Signaling/Media source IP is set to Auto cleared.

• 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'.

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

• SIP Recording server came up.

• Signaling container connection with SLB container is down.

• Signaling container connection with SLB container is up.

• Signaling container connection with CAC Manager is Down.
• Node: [nodename].
• Login into CAC Manager Pod debug CLI to verify current operational status.

• Signaling container connection with CAC Manager is Up.
• Node: [nodename].

• Call Access Control Denied Over [num] percent calls: Rejects: [num] Timeouts: [num] Sendfail: [num] Unknown: [num].

• SLB discovery failure because of kubeapi failure.

• SLB Discovery Success.

• Public IP Association to SC failed.

• Public IP Association to SC successful: [ip address].

• Signaling container memory reached above [percent] percent threshold.

• Signaling container memory reached below threshold.

• Call Access Control Denied condition cleared.

10

1

Alarm

D-Channel down

Communication

Card;Port;PodName;ContainerType

Critical

• The D-channel (layer 2) is out of service..

10

2

Event

D-Channel up

Communication

Card;Port;PodName;ContainerType

• The D-channel (layer 2) is in service..

10

3

Alarm

Call released due to channel restart by far end

Communication

Card;Port;Channel;PodName;ContainerType

Minor

• Call released as the ISDN channel has been restarted by far end.

11

1

Alarm

Port disabled by operator

Communication

Card;Port;PodName;ContainerType

Warning

• Port is placed Out of Service by operator.

11

2

Event

Port enabled by operator

Communication

Card;Port;PodName;ContainerType

• Port is placed back in Service by operator.

11

3

Alarm

DS1 Loopback Enter

Communication

Card;Port;PodName;ContainerType

Critical

• The physical layer is in loopback state.

11

4

Event

DS1 Loopback Exit

Communication

Card;Port;PodName;ContainerType

• The physical layer is out of loopback state.

11

5

Alarm

Red Alarm - Loss of Signal

Communication

Card;Port;PodName;ContainerType

Critical

• The physical layer has detected a Red (LOS) alarm.

11

6

Event

Red Alarm - Loss of Signal cleared

Communication

Card;Port;PodName;ContainerType

• The physical layer RED alarm (LOS) is cleared..

11

7

Alarm

Red Alarm - Loss of Frame

Communication

Card;Port;PodName;ContainerType

Critical

• The physical layer has detected a Red (LOF) alarm.

11

8

Event

Red Alarm - Loss of Frame cleared

Communication

Card;Port;PodName;ContainerType

• The physical layer RED alarm (LOF) is cleared.

11

9

Alarm

Blue Alarm

Communication

Card;Port;PodName;ContainerType

Critical

• The physical layer has detected a BLUE alarm.

11

10

Event

Blue Alarm Cleared

Communication

Card;Port;PodName;ContainerType

• The physical layer BLUE alarm is cleared.

11

11

Alarm

Yellow Alarm

Communication

Card;Port;PodName;ContainerType

Critical

• The physical layer has detected a YELLOW alarm.

11

12

Event

Yellow Alarm Cleared

Communication

Card;Port;PodName;ContainerType

• The physical layer YELLOW alarm is cleared.

11

13

Alarm

Port disabled as port not found on DS1

Communication

Card;Port;PodName;ContainerType

Critical

• Port is now marked as disabled because the corresponding port was not present on the DS1 physical hardware.

11

14

Alarm

Clock recovery switched to port configured as secondary

Communication

System;PodName;ContainerType

Critical

• System has switched over to secondary clock recovery port as primary is lost.

11

15

Event

Clock recovery switchover to secondary port cleared

Communication

System;PodName;ContainerType

• Secondary clock recovery alarm is being cleared as primary clock is recovered.

11

16

Alarm

Clock recovery switched to freerun clock

Communication

System;PodName;ContainerType

Critical

• System has switched over to QF free-run clock as both primary/secondary recovery clocks are invalid.

11

17

Event

Clock recovery switchover to freerun clock cleared

Communication

System;PodName;ContainerType

• Free-run clock recovery alarm is being cleared as primary clock is recovered.

11

18

Alarm

Line card not detected

Communication

Card;PodName;ContainerType

Warning

• Line card not detected.

11

19

Event

Line card detected

Communication

Card;PodName;ContainerType

• Line card is detected.

11

20

Alarm

Port disabled for relay passthrough state activation

Communication

Card;Port;PodName;ContainerType

Warning

• Port is now marked as disabled for activated relay passthrough state.

11

21

Event

Port enabled for relay online state activation

Communication

Card;Port;PodName;ContainerType

• Port is now marked as enabled for activated relay online state.

11

22

Alarm

Layer 1 down

Communication

Card;Port;PodName;ContainerType

Critical

• The physical layer has detected layer 1 down due to state conditions that results in non-operational state of the BRI port.

11

23

Event

Layer 1 up

Communication

Card;Port;PodName;ContainerType

• The physical layer 1 down alarm is cleared with operational state of the BRI port.

11

24

Alarm

Port disabled as port not found on analog card

Communication

Card;Port;PodName;ContainerType

Critical

• Port is now marked as disabled because the corresponding port was not present on the analog physical hardware.

11

25

Alarm

Ports disabled for relay pass thru state chg on analog relay cards

Communication

System;Card;Card;PodName;ContainerType

Warning

• Ports are now marked as disabled for activated relay passthrough state on analog FXS/FXO card pair.

11

26

Event

Ports enabled for relay online state change on analog relay card pairs

Communication

System;Card;Card;PodName;ContainerType

• Ports are now marked as enabled for activated relay passthrough state on analog FXS/FXO card pair.

11

27

Alarm

Port status down detected

Communication

Card;Port;PodName;ContainerType

Warning

• Line down condition detected due to no battery.

11

28

Event

Port status up

Communication

Card;Port;PodName;ContainerType

• Line down condition is cleared.

11

29

Alarm

Port disabled as port not found on BRI

Communication

Card;Port;PodName;ContainerType

Critical

• Port is now marked as disabled because the corresponding port was not present on the BRI physical hardware.

11

30

Alarm

System not operational

Communication

System;PodName;ContainerType

Critical

• System not operational because DSP cannot be initialized.
• Contact Ribbon Service with the information in this alarm.

• DS1 sync failure could be due to mismatching line configuration.
• Suggested Action: Disable "Admin State" of unused ports to avoid performance impact.

• DS1 sync failure cleared.

12

1

Alarm

DSP not coming up

DSP;PodName;ContainerType

Critical

• DSP board [boardType] could not be brought up.
• If the DSP does not come up, contact Ribbon Service with the information in this alarm.

12

2

Alarm

DSP reset

Equipment

DSP;PodName;ContainerType

Major

• This alarm will be generated if a DSP encounters a fatal error condition and has to be reinitialized.

12

3

Event

DSP Card is UP

Equipment

DSP;PodName;ContainerType

• This event will clear the 'DSP not coming up' and 'DSP reset' alarms.

12

4

Event

DSP Event Failure

Processing

System;Service;PodName;ContainerType

• Call related command on Connection ID [value] failed with error code [value].

• This alarm is generated if a RTP/RTCP port range is found to be invalid.
• This condition should be resolved by reconfiguring the RTP/RTCP Port Range under Media System Configuration.

• This event will clear the "RTP/RTCP Port Range Invalid" alarm.

• This alarm is generated when there is a mismatch in media stream mode of the two call legs.
• Suggested Action: Match "Audio/Fax Stream Mode" settings and clear alarm.

• Music-On-Hold enabled; source is not properly configured. 
• If source is set to File: upload a file, disable music-on-hold or switch source to an FXS port.

• This alarm is generated if we exceed the configured number of RTP/RTCP port pairs.
• This condition should be resolved by increasing the "Number of Port Pairs" in Media System Configuration.

• Virt DSP Command Failure: Conf=[conf] Type=[type] Error=[error].

MSC-DTLS Server Handshake Failure

DTLSProfile;IPAddress;PodName;ContainerType

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

MSC-DTLS Server Handshake Failure Cleared

DTLSProfile;IPAddress;PodName;ContainerType

• Handshake failure error alert condition was cleared.
• This event clears the 'MSC-DTLS Server Handshake Failure' alarm.

MSC-DTLS Handshake Inactivity Timeout Failure

DTLSProfile;IPAddress;PodName;ContainerType

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

MSC-DTLS Handshake Inactivity Timeout Cleared 

DTLSProfile;IPAddress;PodName;ContainerType

• Handshake response was received within specified timeout.
• This event clears the 'MSC-DTLS Handshake Inactivity Timeout Failure' alarm. 

MSC-DTLS Handshake Negotiation Start Failure

DTLSProfile;IPAddress;PodName;ContainerType

MSC-DTLS Handshake Negotiation Start Successful

DTLSProfile;IPAddress;PodName;ContainerType

• DTLS Handshake response was started with valid certificate on local and remote gateway.
• This event clears the 'MSC-DTLS Handshake Negotiation Start Failure' alarm.

MSC-DTLS Client Handshake Failure

DTLSProfile;IPAddress;PodName;ContainerType

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

MSC-DTLS Client Handshake Failure Cleared

DTLSProfile;IPAddress;PodName;ContainerType

• Handshake failure error alert condition was cleared.
• This event clears the 'MSC-DTLS Client Handshake Failure' alarm.

13

1

Alarm

TLS Own Server Certificate will Expire

Security

CertificateCommonName;PodName;ContainerType

Major

• CommonName: [name] StartDate: [startdate] EndDate: [enddate] will expire in a window time.
• Action: Generate, Export CSR and Import a new signed certificate.

13

2

Alarm

TLS Own Server Certificate has Expired

Security

CertificateCommonName;PodName;ContainerType

Critical

• CommonName: [name] StartDate: [startdate] EndDate: [enddate] has expired.
• Action: Generate, Export CSR and Import a new signed certificate.

• This Server certificate is found to be missing or has failed validations.
• Suggestion Action. Generate, Export CSR and Import a new signed certificate.

13

4

Alarm

TLS Self Sign Certificate Generation Failed

Security

CertificateCommonName;PodName;ContainerType

Critical

• Failed to create a default self signed certificate on the system.

13

5

Event

New and Valid TLS Own Server Certificate Detected

Security

CertificateCommonName;PodName;ContainerType

• Imported and validated common name: [name] StartDate: [startDate] EndDate: [endDate].
• This event clears the Server Certificate Expiring, Expired and Missing alarms.

13

6

Alarm

TLS Trusted Certificate Authority will Expire

Security

CertificateCommonName;PodName;ContainerType

Major

• CommonName: [name] StartDate: [startDate] EndDate: [endDate] will expire in a window time.
• Action: Obtain and Import a new valid certificate from the CA vendor.

13

7

Alarm

TLS Trusted Certificate Authority has Expired

Security

CertificateCommonName;PodName;ContainerType

Critical

• CommonName: [name] StartDate: [startDate] EndDate: [endDate] has expired.
• Action: Obtain and Import a new valid certificate from the CA vendor.

13

8

Event

TLS Trusted Certificate Authority was Deleted

Security

CertificateCommonName;PodName;ContainerType

• The Trusted Certificate Authority is successfully deleted due to the expired or expiring soon validity status.

• CommonName: [name] StartDate: [startDate] EndDate: [endDate] will expire in a window time.
• Action: Obtain and Import a new valid certificate from the CA vendor.

• CommonName: [name] StartDate: [startDate] EndDate: [endDate] has expired.
• Action: Obtain and Import a new valid certificate from the CA vendor.

14

1

Alarm

Invalid Session for attempted realtime connection

Security

IPAddress;PodName;ContainerType

• If a web-client tries to open a realtime monitor connection with invalid session ID, BMP will generate this alarm.

14

2

Alarm

BMP-TLS Handshake Alert Failure

Security

IPAddress;PodName;ContainerType

Minor

• This alarm will be generated if TLS Connection failed with an Alert.
• The connection associated with a TLS Connection ID is terminated.

14

3

Alarm

BMP-TLS Handshake Inactivity Timeout Failure

Security

IPAddress;PodName;ContainerType

Minor

• This alarm will be generated if there was long period of inactivity during exchange of handshake messages for an associated TLS Connection ID.

15

1

Alarm

Interface oper down

Communication

Port;PodName;ContainerType

Major

• Occurs when an Ethernet port (of ports 1, 2, 3 and 4) is operationally down (e.g. cable unplugged, mismatched speed/duplexity settings) and if administrative state is enabled.
• Is generated only on the SBC 2000.

15

2

Event

Interface oper up

Communication

Port;PodName;ContainerType

• Is generated when an Ethernet port (of ports 1, 2, 3 and 4) becomes operationally up.
• This event automatically clears the 'Interface oper down' alarm.

15

3

Event

Interface admin up

Communication

LogicalInterface;PodName;ContainerType

• Is generated when the administrative state of the Logical Interface is configured to be enabled.

15

4

Event

Interface admin down

Communication

LogicalInterface;PodName;ContainerType

• Is generated when the administrative state of the Logical Interface is configured to be disabled.

15

5

Event

Admin Port oper down

Communication

Port;PodName;ContainerType

• Is generated when the Admin Port is operationally down (e.g. cable unplugged, mismatched duplex/speed settings).
• Is applicable to the SBC 2000 only.

15

6

Event

Admin Port oper up

Communication

Port;PodName;ContainerType

• Is generated with the port becomes operational after being in an 'Admin port oper down' state.
• Is applicable to the SBC 2000 only.

15

7

Event

Port oper down

Communication

Port;PodName;ContainerType

• This event is generated when the port is operationally down.
• It is generated for the SBC 1000 only.

15

8

Event

RIP license not enabled

Communication

System;PodName;ContainerType

• RIP feature license is not enabled.

15

9

Event

OSPF license not enabled

Communication

System;PodName;ContainerType

• OSPF feature license is not enabled.

15

10

Alarm

Link Monitor Peer down

Communication

IPAddress;PodName;ContainerType

Major

• Connection to the monitored host or gateway is down.

15

11

Event

Link Monitor Peer ready

Communication

IPAddress;PodName;ContainerType

• Connection to the monitored host or gateway is established.

15

12

Event

Tunnel connection disabled by operator

Communication

NetworkName;PodName;ContainerType

• Tunnel connection is placed Out of Service by operator.

15

13

Event

Tunnel connection enabled by operator

Communication

NetworkName;PodName;ContainerType

• Tunnel connection is placed Back in Service by operator.

15

14

Alarm

Tunnel link lost

Communication

NetworkName;PodName;ContainerType

Critical

• Tunnel lost communication with the peer.
• This alarm will be cleared by the "Tunnel link restored" event.

15

15

Event

Tunnel link restored

Communication

NetworkName;PodName;ContainerType

• Tunnel is successfully established with the peer

15

16

Event

IPsec license not enabled

Communication

System;PodName;ContainerType

• IPsec feature license is not enabled.

15

17

Alarm

Negotiated  Duplexity Half

Communication

Port;PodName;ContainerType

Warning

• Port negotiated duplexity is half.
• This degrades the performance.

15

18

Event

Negotiated Duplexity Full

Communication

Port;PodName;ContainerType

• Port negotiation duplexity is back to full.

15

19

Alarm

Preferred link down

Communication

IPAddress;PodName;ContainerType

Critical

• This event is generated when the preferred link is down.

15

20

Event

Preferred link ready

Communication

IPAddress;PodName;ContainerType

• This event is generated when the the preferred link is ready for service.
• This event automatically clears the 'preferred link down' alarm.

15

21

Alarm

Tunnel Notification failure

Communication

NetworkName;PodName;ContainerType

Critical

• Tunnel negotiation failed.
• Suggested Action: Look up the 'Failure Reason' attribute details for the Source in the IPsec Tunnel Table.

15

22

Event

Tunnel local subnet(s) are non-negotiable

Communication

NetworkName;PodName;ContainerType

• Local subnets [subnets] failed negotiation as a result of peer config mismatch.

15

23

Event

Tunnel remote subnet(s) are non-negotiable

Communication

NetworkName;PodName;ContainerType

• Remote subnets [subnets] failed negotiation as a result of peer config mismatch.

• MSTP port is in learning state.

• MSTP port is in forwarding state.

• MSTP port is in discarding state.

• Packet capture has started.

• Packet capture has stopped due to [reason].

• The indicated IPv6 address has been detected as a duplicate address.

• This event is generated when an IP address is configured on the node.

• This event is generated when an IP address is removed from the node.

• Link failover detected, the indicated Ethernet port became active.

• Some MAC addresses have changed since the last time the system was up.
• It is recommended to log into console as 'netconfig' user and remap the interfaces as desired.

• Domain Name for Split DNS should not be empty.

• ACL Rule Addition has failed on a SWe Edge Instance.

• Clear Alarm for ACL Rule Addition Failure.

16

1

Alarm

Application Service restarted

Processing

Service;PodName;ContainerType

Major

• An SBC Edge Application service was restarted.
• Contact Ribbon Service with the information in this alarm and any core files present.
• These can be found in Diagnostics->Restart Report under the 'Core Files' tab.

16

2

Alarm

Active partition switched

Processing

Partition;PodName;ContainerType

Major

• System detected a problem during previous boot cycle, active partition has switched automatically.
• Suggested Action: Backup the configuration and re-apply the upgrade to the currently inactive partition.

16

3

Alarm

Failed to mount partition

Processing

Partition;PodName;ContainerType

Major

• Mounting failed for partition [number].

16

4

Alarm

Failed to set active partition

Processing

Partition;PodName;ContainerType

Major

• Failed to set active partition.
• Contact Ribbon Service with the information in this alarm.

16

5

Alarm

Attempt to repair boot parameter mismatch failed.

Processing

Partition;PodName;ContainerType

Major

• Attempt to auto repair boot parameters failed.
• Contact Ribbon Service with the information in this alarm.

16

6

Alarm

Boot parameter mismatch detected

Processing

Partition;PodName;ContainerType

Major

• Boot parameter mismatch was detected.
• Attempting to auto repair.

16

7

Alarm

Failed Power-on memory self test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

8

Alarm

Failed Power-on Core Switch test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

9

Alarm

Failed Power-on Secondary Switch test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

10

Alarm

Failed Power-on external Quad PHY test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

11

Alarm

Failed Power-on external Single PHY test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

12

Alarm

Failed Power-on CPU PHY test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

13

Alarm

Failed Power-on TSI test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

14

Alarm

Failed Power-on internal 5-Port PHY test

Equipment

Partition;PodName;ContainerType

Critical

• Power-on self test failure.

16

15

Event

System Up After Planned Restart

Equipment

System;PodName;ContainerType

• System up after planned restart.
• Reboot reason [reason].

16

16

Alarm

System Up After Unplanned Restart

Equipment

System;PodName;ContainerType

Major

• System up after unplanned restart.
• Reboot reason [reason].

• SBC has entered password recovery mode.

• SBC has exited password recovery mode.

• SBC discovered USB storage.
• SBC can mount flash drives formatted with FAT32 file system only.

• USB storage device is connected.

• USB storage device is disconnected.
• This alarm will be cleared when USB drive is connected.

• A critical SBC Edge application has crashed, and the system will be restarted.
• Contact Ribbon Service with the information in this alarm and any core files present.
• These can be found in Diagnostics->Restart Report/Core Files tab.

• A USB firmware update is available.
• To perform upgrade, please first load SW release v4.1.1.

• Auto Configuration successful after receiving SIP NOTIFY message.

• Failed to perform Auto Configuration after receiving SIP NOTIFY message.

• Current SIP NOTIFY message cannot be processed as software update is in progress.

• Node Reboot requested by user [Username] from [ipAddress].

• Full factory default requested by user [Username] from [ipAddress].

• Unexpected memory size for virtual CPU detected.
• Please consult documentation for memory requirement.

• Full factory default requested via hardware reset button.

uxAlmSCMCconnectionisdown

1.3.6.1.4.1.177.15.2.1048607

• Signaling container connection with media container is down.

uxAlmSwitchoverToActive

• Logged when the Standby instance switches to the active role.
• Event Text: System has switched to active HA role.

uxAlmLostHAProtection

• Logged when the Standby instance has gone offline.
• Event Text: Peer HA node has gone offline.

uxAlmHAProtectionRestored

• Event Text: Peer HA node has come back online.
• Clears alarm 16.33.

17

1

Alarm

No response

Communication

Card;Port;Channel;PodName;ContainerType

Major

• No response to seizure.

17

2

Alarm

Remote end did not back off in glare

Communication

Card;Port;Channel;PodName;ContainerType

Minor

• Remote end did not back off in glare.

17

3

Alarm

Wink expected, did not arrive

Communication

Card;Port;Channel;PodName;ContainerType

Major

• Wink expected, did not arrive.

17

4

Alarm

No dial tone

Communication

Card;Port;Channel;PodName;ContainerType

Major

• Event of off-hook did not produce dial tone as expected.

17

5

Event

CAS signaling group disabled

Communication

SG;PodName;ContainerType

• CAS signaling group disabled.

17

6

Alarm

CAS license not enabled

General

System;Service;PodName;ContainerType

Major

• Call attempted but CAS feature is not enabled.
• This alarm is cleared by CAS license enabled event.

17

7

Event

CAS license enabled

General

System;Service;PodName;ContainerType

• License manager notify CAS that license is enabled.

17

8

Event

Wink Received

Communication

Card;Port;Channel;PodName;ContainerType

• Wink failure had occurred, but wink is received now.

17

9

Event

Dial Tone Received

Communication

Card;Port;Channel;PodName;ContainerType

• No Dial Tone was received, but Dial Tone is received now.

17

10

Event

Response Received

Communication

Card;Port;Channel;PodName;ContainerType

• No Response to seizure was received, but Response is received now.

17

11

Alarm

Invalid character(s) in calling number

Communication

Calling;PodName;ContainerType

Warning

• Invalid character(s) removed, correct issue and delete warning.

17

12

Alarm

Invalid character(s) in called number

Communication

Called;PodName;ContainerType

Warning

• Invalid character(s) removed, correct issue and delete warning.

17

13

Event

CAS signaling group enabled

Communication

SG;PodName;ContainerType

• CAS signaling group enabled.

17

14

Alarm

CAS-R2 CD Bit error

Communication

Card;Port;PodName;ContainerType

Minor

• CAS-R2 CD-Bits are mismatched on the span, this alarm is cleared when all channels match.

17

15

Event

CAS-R2 CD Bit error clear

Communication

Card;Port;PodName;ContainerType

• CAS-R2 CD-Bits now match on this span for all channels.

17

16

Alarm

Network Glare occured

Communication

Card;Port;Channel;PodName;ContainerType

Minor

• Network glare occurred on this interface.

18

1

Alarm

Config validation failure

General

System;Service;PodName;ContainerType

Warning

• Config validation failure during startup.
• Please check the configuration.

• Configuration loaded from newer release than currently running release.

• Password decryption failed on configuration import operation.

• Partial 'factory default or configuration import' requested by [Username] from [ipAddress].

• Configuration restore requested by [Username] from [ipAddress].