1

1

alarm

AD caching failed

communication

System;Service;IPAddress

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

• Failed to execute 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

• New user [username] logged in from [ip address] at [time].

1

5

alarm

User login failed

security

Username;IPAddress

major

• User [username] login failed from [ip address] at [time].
• This alarm will be cleared by event User logged in.

1

6

alarm

AD Unreachable

communication

System:Service;IPAddress; DCType

major

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

1

7

event

AD Reachable

communication

System:Service;IPAddress; DCType

• Active directory is now reachable.
• DCType will be either Authentication or Call Route

1

8

event

AD caching successful

communication

System:Service;IPAddress

• AD caching was successful.

1

9

alarm

AD backup failed

equipment

System:Service;IPAddress

minor

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

1

10

event

AD successfully backed up

equipment

System:Service;IPAddress

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

1

11

alarm

AD cache truncated

equipment

System:Service

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

major

• Either the RADIUS server is network unreachable, or the configuration is incorrect.
• 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

• RADIUS server is online.

1

14

alarm

CDR logging failed

communication

System:Service;IPAddress

major

• Sonus SBC 1000/2000 failed to send CDR to RADIUS based accounting server.
• Either the RADIUS 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

major

• Sonus SBC 1000/2000 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

• Logged any time password is changed by specified user or an administrator.

• Event Text: User 'username' password changed successfully by 'username' from 'IP address'.

  Info
  If not preceded by a password expired event, this was a voluntary password change.

1

18

alarm

User password change failed

Security

Username

warning

• Logged any time an attempted password change failed by specified user or an administrator.
• Event Text: User 'username' password change attempted by 'username' from 'IP address" failed.

• Cleared by event 1.17 - User password changed successfully.

  Info
  If not preceded by a password expired event, this was a voluntary password change.

1

19

event

User account disabled

Security

Username

• Event Text: User 'username' account has been disabled by 'username' from 'IP address'.

1

20

event

User account activated

Security

Username

• Event Text: User 'username' account has been activated by 'username' from 'IP address'.

1

21

event

Global Security Options Changed

Security

Username;IPAddress

• Event Text: Global security options changed by 'username' from 'IP address'.

1

22

alarm

User login blocked

Security

Username

major

• Event Text: User 'username' blocked from login due to excessive incorrect login attempts.
• Cleared by event 1.23 - User login unblocked.

1

23

event

User login unblocked

Security

Username

• Event Text: User 'username' unblocked.

• Password has expired.

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

2

1

alarm

Invalid Card ID EEPROM Data

equipment

System;Card

critical

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

2

2

alarm

Card Health Check Failed

equipment

System;Card

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 Sonus TAC with the alarm information.

2

3

alarm

Card not Supported

equipment

System;Card

major

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

2

4

alarm

Power Supply input failure

equipment

System;PSU

major

• A Power supply module has indicated a failure of input power.
• The Sonus SBC 1000/2000 System 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

• 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

major

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

2

7

alarm

Single Fan failure

equipment

System;Fan

major

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

2

8

alarm

Multiple Fan Failures

equipment

System;Fans

critical

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

2

9

alarm

System Temperature Warm

equipment

System

minor

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

2

10

event

System Temperature Warm Cleared

equipment

System

• 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

critical

• The temperature sensors have indicated that system is running hot.

2

12

event

System Temperature Hot Cleared

equipment

System

• 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

critical

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

3

2

alarm

License expires in 2 weeks.

general

System;Service

major

• License of the node will expire in 2 weeks.

3

3

event

New License applied.

general

System;Service

• New License is applied on the node.

3

4

alarm

Failed to Apply License.

general

System;Service

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 Sonus Sales to obtain a new license.

3

5

alarmFailed

to acquire licenseLicense(s) for 'license type' has been exhausted, or is not licensed.

general

System;Service

minor (SBC 1k/2k)

critical (SWe Lite)

• The alarm is generated when the required license is not available.
• Check the number of licensed SIP or TDM channels, the number of SIP registrations, SBA, Transcoding or AD.
• Suggested action - obtain license for missing functionality.
• NOTE: The alarm is throttled to at most every 5 minutes per feature.

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

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

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

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

5

1

alarm

ASM Unreachable

communication

SBA Instance

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

• Clears alarm 'ASM Unreachable'.

5

3

alarm

ASM Failure Recovered

equipment

SBA Instance

minor

• 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

critical

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

5

5

event

Clear ASM Services Not Running

processing

SBA Instance

• Clears alarm 'ASM Services Not Running'.

5

6

alarm

ASM Services Restarted

processing

SBA Instance

minor

• 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

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

• 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

• 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

major

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

5

11

event

Ethernet Link Up

equipment

SBA Instance

• Ethernet port specific has recovered link.

5

12

alarm

ASM-SBC IP Subnet Mismatch

equipment

SBA Instance

critical

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

5

13

event

ASM-SBC IP Subnet Match

equipment

SBA Instance

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

• The QoE database is unreachable from ASM, make sure the Lync Server 2013 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.

• 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

Alarmalarm

ASM IP Address conflict

SBA

SBA Instance

Criticalcritical

• The configured ASM IP was not applied due to conflict with other device(s) on the network.

5

24

Eventevent

Clear ASM IP address conflict

SBA

SBA Instance

• ASM IP address conflict cleared.

• ASM Etherent Port has been detected down.

7

1

event

Configuration change occurred on Action Set

general

• There is an action set table number/name that should be printed with this event.

• ASM Ethernet Port has been detected down is cleared.

• Cloud Connector Edition entered in Maintenance mode.

• Cloud Connector Edition exited maintenance mode.

• Cloud Connector Edition Windows Product Key is missing.

• Cloud Connector Edition Windows Product Key has been found.

• Cloud Connector Edition Windows Product Failed to Activate

7

1

event

Configuration change occurred on Action Set

general

ActSetTble

• There is an action set table number/name that should be printed with this event.

7

2

event

Configuration change occurred on Normalization Table

general

NormTble

7

2

event

Configuration change occurred on Normalization Table

general

NormTble

• 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

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

7

4

event

Configuration change occurred on Transformation Tables

general

TransTble

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

7

5

alarm

Route temporarily disabled

communication

RtTble

warning

• This alarm is set if a link is down or some other event has occured to take a route entry out of service.

7

6

event

Route enabled

communication

RtTble

• Route came up.

7

7

alarm

A Call exceeded the limit for number of destinations

communication

CallDest

warning

• A call with destination of X tried to be forked more than the limit allows (currently 8).

7

8

alarm

Call forking used with no forking license

communication

CallDest

warning

• A call with a destination of X was forked with no forking license available.

7

9

alarm

Invocation of InvokeActionSet exceeded the maximum nesting limit

communication

CallDest

warning

• A call with with destination of X tried to execute InvokeActionSet more the the limit allows (currently 10).

7

10

event

Configuration change occurred on Callback Tables

general

CallbackTble

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

7

3

event

Configuration change occurred on Route Table

general

RtTble

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

7

4

event

Configuration change occurred on Transformation Tables

general

TransTble

8

1

event

Channel is in service

communication

Card;Port;Channel

• 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

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

minor

• Emergency Call is Attempted from Calling Number, Calling Extension, Caller IP address.

8

4

event

Emergency Call Attempted

communication

Number;Extension;IPAddress

• Emergency Call Alarm will be cleared after expiry time in emergency status table.

QoE report not sent due to RTCP Media List

• Generated when the Media List does not have RTCP-XR configuration enabled.

• The call is not in RTP mode hence the call transfer could not be honored.

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

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

7

5

alarm

Route temporarily disabled

communication

RtTble

warning

• This alarm is set if a link is down or some other event has occured to take a route entry out of service.

7

6

event

Route enabled

communication

RtTble

• Route came up.

7

7

alarm

A Call exceeded the limit for number of destinations

communication

CallDest

warning

• A call with destination of X tried to be forked more than the limit allows (currently 8).

7

8

alarm

Call forking used with no forking license

communication

CallDest

warning

• A call with a destination of X was forked with no forking license available.

7

9

alarm

Invocation of InvokeActionSet exceeded the maximum nesting limit

communication

CallDest

warning

• A call with with destination of X tried to execute InvokeActionSet more the the limit allows (currently 10).

7

10

event

Configuration change occurred on Callback Tables

general

CallbackTble

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

98

1

alarm

event

Channel is in serviceSIP Server not responding

communication

SIPClusterCard;ServID;Protocol;IPAddress;Port

major

Port;Channel

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

98

2

alarm

Signaling Group taken Channel is out of service

communication

SG

Card;Port;Channel

minorcritical

• All servers in SG have failedChannel Out Of Service Alarm.
• This alarm will be cleared by 'SIP Signaling group enabled' event.is automatically cleared when Channel is in service.

89

3

event

alarm

Emergency Call AttemptedSignaling Group disabled

communication

SG

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

Number;Extension;IPAddress

minor

• Emergency Call is Attempted from Calling Number, Calling Extension, Caller IP address.

8

4

event

Emergency Call Attempted

communication

Number;Extension;IPAddress

• Emergency Call Alarm will be cleared after expiry time in emergency status table.

QoE report not sent due to RTCP Media List

• Generated when the Media List does not have RTCP-XR configuration enabled.

• The call is not in RTP mode hence the call transfer could not be honored.

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

9

1

alarm

SIP Server not responding

communication

SIPCluster;ServID;Protocol;IPAddress;Port

major

• SIP server has failed to respond and has been taken out of service

9

4

alarm

SIP-TLS Server Handshake Failure

security

TLSProfile;IPAddress

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

minor

9

6

alarm

Configured port number mismatch

processing

SG;IPAddress;Port

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

• SIP server came up.

9

8

alarm

SIP cluster went down

communication

SIPCluster

major

• SIP cluster went down.
• This is due to all the servers in the clusters are not responsive.
• This alarm will be cleared by the event 'Sip cluster enabledSIP server became responsive'.

99

2

event

alarm

Signaling Group taken out of serviceSIP Cluster enabled

communication

SIPClusterSG

 critical

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

9

103

event

SIP Signaling group enabledGroup disabled

communication

SG

• SIP Signaling group enabledConfiguration action has changed this Signaling Group from Enabled to Disabled.

9

114

alarm

SIP Signaling group: DNS failure

communication

SG

major

-TLS Server Handshake Failure

security

TLSProfile;IPAddress

minor

• TLS server handshake failed with alert code. Action: Refer to Error Alerts in RFC 5246 for the problemFailed to resolve the FQDN entries in the SIP Signaling Group. Suggested action - confirm the FQDNs, and confirm DNS access.

9

125

eventalarm

SIP Signaling Group; FQDN resolved

communication

-TLS Handshake Inactivity Timeout Failure

security

TLSProfile;IPAddress

minorSG

9

136

alarm

Configured port number mismatch

processing

SG;IPAddress;Port

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

SIP Server; DNS failure.

communication

SIPCluster;ServID

major

• Failed to resolve the SIP server FQDN entries in the SIP Server table.
• Suggested action - check the FQDN syntax.

9

14

event

SIP Server; FQDN resolved

communication

SIPCluster;ServID;Protocol;IPAddress;Port

• SIP Server config FQDN resolvedserver came up.

9

158

alarm

SIP call session DNS failurecluster went down

communication

SGSIPCluster

major

• SIP cluster went down.
• This is due to all the servers in the clusters are not responsive.
• This alarm will be cleared by the event 'Sip cluster enabled'Failed to resolve an FQDN with DNS server during a SIP call session.

9

169

alarm

event

SIP Cluster enabledAcquiring license for Register failed

communication

SGSIPCluster

major 

• Failed to acquire license from License ManagerSIP cluster enabled.

9

10

event

SIP Signaling group enabled

communication

SG

• SIP Signaling group enabled.

9

11

alarm

SIP Signaling group: DNS failure

communication

SG

major

• Failed to resolve the FQDN entries in the SIP Signaling Group. Suggested action - confirm the FQDNs, and confirm DNS access.

9

12

event

SIP Signaling Group; FQDN resolved

communication

SG

• Successfully

• resolved the FQDN of the SIP Signaling group.

9

13

alarm

SIP

Server; DNS failure.

communication

SIPCluster;ServID

major

• Failed to resolve the SIP

• server FQDN entries in the SIP Server table.
• Suggested action - check the FQDN syntax.

9

14

event

SIP

Server

; FQDN resolved

communication

SIPCluster;ServID

• SIP

• Server config FQDN resolved.

9

2215

alarmRegistration not valid; received stale=false

SIP call session DNS failure

communication

SIPCluster;ServID;Protocol;IPAddress;PortSG

major

• Failed to resolve an FQDN with DNS server during a SIP call session.Server has sent stale=false. Contact is not Registered.

9

2316

eventalarm

Config change for SIP endpoint that received stale=falseAcquiring license for Register failed

communication

SG;AorName

 major

• Endpoint which had Stale is False has config changeFailed to acquire license from License Manager.

SIPCluster;ServID;Protocol;IPAddress;Port

minor

• QoE Notify Message Response was not successful”/” QoE Notify Message received a no response or a failed response. This alarm is cleared by the event 'QoE Notify Message received a successful response'.”

9

25

event

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

alarm

• Successfully bound to network interface. DHCP lease renewed.

System;Service

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

28

alarm

SIP maximum sessions per SG reached

communication

SG

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

• SIP

• Register server came up.

9

3022

alarmError resolving SRV record

Registration not valid; received stale=false

communication

SIPCluster;ServID;Protocol;IPAddress;Port

major

• Failed to execute SRV record query. Suggested action - confirm that DNS server network is reachable, check SRV and DNS server configurationServer has sent stale=false. Contact is not Registered.

9

3123

eventSRV record resolved

Config change for SIP endpoint that received stale=false

communication

SIPClusterSG;ServIDAorName

none 

• DNS server returned valid SRV record(s)Endpoint which had Stale is False has config change.

9

24

alarm

• Handshake failed due to start with invalid certificate. Action: Import a valid signed Sonus SBC Certificate on local and/or remote gateway.

• 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

• Number of SIP Call Sessions is under the system capacity.

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

QoE Notify Message was not successful

communication

SIPCluster;ServID;Protocol;IPAddress;Port

minor

• QoE Notify Message Response was not successful”/” QoE Notify Message received a no response or a failed response. This alarm is cleared by the event 'QoE Notify Message received a successful response'.”

9

25

event

QoE Notify Message Response was successful

communication

SG

• QOE Notify Message received a successful response.

9

26

alarm

SIP overload detected

communication

System;Service

minor

• SIP application session processing is overloaded.

9

27

event

SIP overload cleared

communication

System;Service

• SIP application session processing resumes to normal operation, overload cleared.

9

28

alarm

SIP maximum sessions per SG reached

communication

SG

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

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

9

30

alarm

Error resolving SRV record

communication

SIPCluster;ServID

major

• Failed to execute 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

none

• DNS server returned valid SRV record(s).

• Handshake failed due to start with invalid certificate. Action: Import a valid signed Sonus SBC Certificate on local and/or remote gateway.

• 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

• Number of SIP Call Sessions is under the system capacity.

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

A Presence Publish Request has been sent to the configured Skype/Lync Presence Front End and either:

• • no response has been received, or
  • the response failed.
    
    

Only one alarm is raised at any time. The alarm is cleared when the SIP presence entity receives a successful response to a Publish message.

The SBC has received a message from a previously unreachable presence server.

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

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

This alarm is raised if:

• The connection to Nectar UCD server is broken
• VQ Notify is rejected by Nectar UCD server.
• The Nectar UCD's FQDN is not resolved by DNS server.

The active alarm gets cleared when NOTIFY is accepted by Nectar UCD successfully.

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

• Enable Monitoring on Skype Presence Server for better reliability.

• Monitoring the 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 Accept 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 Boice Quality Server FQDN has been Resolved

The SBC has received a message from a previously unreachable presence server.

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

This alarm is raised if:

• The connection to Nectar UCD server is broken
• VQ Notify is rejected by Nectar UCD server.
• The Nectar UCD's FQDN is not resolved by DNS server.

10

1

alarm

D-Channel down

communication

Card;Port

critical

• The data link layer of the port has come down.

10

2

event

D-Channel up

communication

Card;Port

• The data link layer of the port has come back up.

10

3

alarm

Call released due to channel restart by far end

communication

Card;Port;Channel

minor

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

11

1

alarm

Port disabled by operator

communication

Card;Port

major

• The physical layer of the port has been brought down by the operator.

11

2

event

Port enabled by operator

communication

Card;Port

• The physical layer of the port has been brought back up by the operator.

11

3

alarm

DS1 Loopback Enter

communication

Card;Port

critical

• The DS1 has been put into a loopback state by the operator.

11

4

event

DS1 Loopback Exit

communication

Card;Port

• The DS1 has been taken out of the loopback state by the operator.

11

5

alarm

Red Alarm - Loss of Signal

communication

Card;Port

critical

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

11

6

event

Red Alarm - Loss of Signal cleared

communication

Card;Port

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

11

7

alarm

Red Alarm - Loss of Frame

communication

Card;Port

critical

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

11

8

event

Red Alarm - Loss of Frame cleared

communication

Card;Port

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

11

9

alarm

Blue Alarm

communication

Card;Port

critical

• The physical layer has detected a blue alarm.

11

10

event

Blue Alarm Cleared

communication

Card;Port

• The physical layer has detected an alarm clearing.

11

11

alarm

Yellow Alarm

communication

Card;Port

critical

• The physical layer has detected an yellow alarm.
• This can be originated because of an alarm assert issued by operator or a detection of alarm condition from far end.

11

12

event

Yellow Alarm Cleared

communication

Card;Port

• The physical layer has detected an yellow alarm clear.

11

13

alarm

Port disabled as port not found on DS1

communication

Card;Port

critical

• This alarm is generated to indicate that a port which was present in the UI 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

critical

• This alarm is generated to indicate that the primary port from which clock was being recovered has gone down and so clock recovery is now being performed on the secondary port.

11

15

event

Clock recovery switchover to secondary port cleared

communication

System

• This event is generated to indicate that the primary port from which clock was being recovered is back in operation and so clock recovery is now being performed on the primary port.

11

16

alarm

Clock recovery switched to freerun clock

communication

System

critical

• This alarm is generated to indicate that the primary and secondary ports from which clock was being recovered have gone down and so clock recovery is now being performed internally from oscillator holdover clock.

11

17

event

Clock recovery switchover to freerun clock cleared

communication

System

• This event is generated to indicate that either the primary or secondary port from which clock was being recovered is back in-service, so clock will be recovered from the in-service port instead of the oscillator holdover clock.

11

18

alarm

Line card not detected

communication

Card

warning

• Line card not detected.

11

19

event

Line card detected

communication

Card

• Line card detected.

11

20

alarm

Port disabled for relay passthrough state activation

communication

Card;Port

warning

• Port disabled because the corresponding port is activated for relay passthrough state.

11

21

event

Port enabled for relay online state activation

communication

Card;Port

• Port enabled because the corresponding port is re-activated for relay online state.

11

22

alarm

Layer 1 down

communication

Card;Port

critical

• The physical layer has detected layer 1 down due to state conditions that results in non-operational state of the BRI port.
• The physical layer state as per I.
• 430 specification can be found in the UI Port View for troubleshooting.

11

23

event

Layer 1 up

communication

Card;Port

• 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

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 through state change on analog relay card pairs

communication

System;Card;Card

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

• 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

warning

• Line down condition detected.

11

28

event

Port status up

communication

Card;Port

• Line down condition cleared.

11

29

alarm

Port disabled as port not found on BRI

communication

Card;Port

critical

• This alarm is generated to indicate that a port which was present in the UI 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

critical

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

12

1

alarm

DSP not coming up

DSP

critical

• This alarm will be generated if a DSP cannot be initialized.
• If the DSP does not come up, contact Sonus TAC with the information in this alarm.

12

2

alarm

DSP reset

equipment

DSP

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

Card

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

12

4

event

DSP Channel Failure

processing

Card;Port;Channel

• This event will be generated if a DSP channel encounters a fatal error condition and has to be closed.

• This alarm is generated if a RTP/RTCP port is found to be invalid. The conflicting port is skipped, however, 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.

13

1

alarm

TLS Own Server Certificate will Expire

security

CertificateCommonName

major

• The Server certificate will expire in a window time.
• Suggested Action: Generate, Export CSR and Import a new signed certificate.

13

2

alarm

TLS Own Server Certificate has Expired

security

CertificateCommonName

critical

• The Server certificate has expired.
• Suggested Action.
• Generate, Export CSR and Import a new signed certificate.

13

4

alarm

TLS Self Sign Certificate Generation Failed

security

CertificateCommonName

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

• The Server certificate was uploaded, validated, and good to use in successfully establishing a TLS connection.

13

6

alarm

TLS Trusted Certificate Authority will Expire

security

CertificateCommonName

major

• The Trusted CA Certificate will expire in a window time. Suggested Action: Import a new trusted CA certificate.

13

7

alarm

TLS Trusted Certificate Authority has Expired

security

CertificateCommonName

critical

• The Trusted CA Certificate has expired. Import a new trusted CA certificate.

13

8

event

TLS Trusted Certificate Authority was Deleted

security

CertificateCommonName

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

• The Server certificate will expire in a window time. Suggestion Action: Generate, Export CSR and Import a new signed certificate.

• The Trusted CA certificate will expire in a window time. Suggestion Action: Import a new trusted CA certificate.

14

1

alarm

Invalid Session for attempted realtime connection

security

IPAddress

• Invalid Session for attempted realtime connection.

14

2

alarm

BMP-TLS Handshake Alert Failure

security

IPAddress

minor

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

14

3

alarm

BMP-TLS Handshake Inactivity Timeout Failure

security

IPAddress

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

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 admin-status is ADMIN_UP.
• The alarm is automatically cleared when the interface returns to working condition or when the admin-status is configured to be ADMIN-DOWN.
• Is generated only on Sonus SBC 2000 platform.
• This alarm is not generated on the Sonus SBC 1000 platform (See ID: 15, Sub-ID: 7 in this table).
• The operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on Sonus SBC 1000/2000 and on the device connected to the other end of the Ethernet cable.
• If the alarm is reported on an unused port, the admin-status of the unused port should be configured as "ADMIN-DOWN".

15

2

event

Interface oper up

communication

Port

• 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

• Is generated when the admin-status of the Port or Logical Interface is configured to be ADMIN-UP.
• Is applicable to Sonus SBC 2000 platform only.

15

4

event

Interface admin down

communication

LogicalInterface

• Is generated when the admin-status of the Port or Logical Interface is configured to be ADMIN-DOWN.
• Is applicable to Sonus SBC 2000 platform only.

15

5

event

Admin Port oper down

communication

Port

• Is generated when the Admin Port is operationally down (e.g. cable unplugged, mismatched duplex/speed settings).
• Is applicable to Sonus SBC 2000 platform only.
• The operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on Sonus SBC 1000/2000 and on the device connected to the other end of the Ethernet cable.
• It is very common and typical for Sonus SBC 2000 to leave the ADMIN-PORT unconnected and hence this condition is reported as an event and not an alarm.

15

6

event

Admin Port oper up

communication

Port

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

15

7

event

Port oper down

communication

Port

• Occurs when an Ethernet port (of ports 1 and 2) is operationally down (e.g. cable unplugged, mismatched speed/duplexity settings).
• Is generated only on Sonus SBC 1000 platform.
• The same conditions are reported as alarm (ID: 15, Sub-ID: 1) on Sonus SBC 2000 platform.
• When this event occurs (noticed as a trap), operator should check the physical cabling of the port that has this condition and verify the speed and duplexity settings on Sonus SBC 1000/2000 and on the device connected to the other end of the Ethernet cable.

15

8

event

RIP license not enabled

communication

System

• RIP feature license is not enabled.

15

9

event

OSPF license not enabled

communication

System

• OSPF feature license is not enabled.

15

10

alarm

Link Monitor Peer down

communication

IPAddress

major

• Generated when a Gateway or host is declared down.

15

11

event

Link Monitor Peer ready

communication

IPAddress

event

• Is generated when a gateway or host is ceclared to be ready for service. It clears the Peer Down alarm.

15

12

event

Tunnel connection disabled by operator

communication

NetworkName

• Tunnel connection is placed Out of Service by operator.

15

13

event

Tunnel connection enabled by operator

communication

NetworkName

• Tunnel connection is placed Back in Service by operator.

15

14

alarm

Tunnel Link Lost

communication

NetworkName

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

• Tunnel is successfully re-established with the peer.

15

16

event

IPsec license not enabled

communication

System

• IPsec license is not enabled.

15

17

alarm

Negotiated  Duplexity Half

communication

Port

warning

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

15

18

event

Negotiated Duplexity Full

communication

Port

•  Port negotiation duplexity is back to full.

15

19

alarm

Preferred Link down

communication

IP address

critical

• Is generated when the preferred Link is down.

15

20

event

Preferred Link Ready

communication

IP address

event

• Is generated when the preferred link is ready for service. This clears the Preferred Link down alarm.

15

21

alarm

Tunnel Notification failure

communication

NetworkName

critical

• Is generated when Tunnel negotiation failed.

15

22

event

Tunnel local subnet(s) are non-negotiable

communication

NetworkName

event

• Is generated when one or more local subnet(s) failed negotiation as a result of peer config mismatch.

15

23

event

Tunnel remote subnet(s) are non-negotiable

communication

NetworkName

event

• Is generated when one or more remote subnet(s) failed negotiation as a result of peer config mismatch.

• Is generated when a Port State is Learning in a Multiple Spanning Tree Instance.

• Is generated when a Port State is Forwarding in a Mulitple Spanning Tree Instance.

• Is generated when a Port State is Discarding in a Multiple Spanning Tree Instance.

• Packet capture has started.

• Packet capture has stopped due to 'reason'.

• Is generated when duplicate address detection fails for a configured IPv6 address.

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

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

16

1

alarm

Application Service restarted

processing

Service

major

• A Sonus SBC 1000/2000 Application service was restarted.

16

2

alarm

Active partition switched

processing

Partition

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

major

• While booting, one of the partition could not be mounted.
• Likely a eUSB corruption.
• Contact Sonus TAC with the information in this alarm.

16

4

alarm

Failed to set active partition

processing

Partition

major

• Failed to set active partition.
• Contact Sonus TAC with the information in this alarm.

16

5

alarm

Attempt to repair boot parameter mismatch failed.

processing

Partition

major

• Attempt to auto repair boot parmeters failed.
• Contact Sonus TAC with the information in this alarm.

16

6

alarm

Failed to mount partition

processing

Partition

major

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

16

7

alarm

Failed Power-on memory self test

equipment

Partition

critical

• Power-on self test failure.

16

8

alarm

Failed Power-on Core Switch test

equipment

Partition

critical

• Power-on self test failure.

16

9

alarm

Failed Power-on Secondary Switch test

equipment

Partition

critical

• Power-on self test failure.

16

10

alarm

Failed Power-on external Quad PHY test

equipment

Partition

critical

• Power-on self test failure.

16

11

alarm

Failed Power-on external Single PHY test

equipment

Partition

critical

• Power-on self test failure.

16

12

alarm

Failed Power-on CPU PHY test

equipment

Partition

critical

• Power-on self test failure.

16

13

alarm

Failed Power-on TSI test

equipment

Partition

critical

• Power-on self test failure.

16

14

alarm

Failed Power-on internal 5-Port PHY test

equipment

Partition

critical

• Power-on self test failure.

16

15

event

System Up After Planned Restart

equipment

System

• System up after planned restart

16

16

alarm

System Up After Unplanned Restart

equipment

System

major

• System up after unplanned restart.

• 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 storge device is connected.

• USB storge device is disconnected. This alarm is cleared when USB drive is connected.

• A Critical Sonus SBC application has crashed, system will be restarted. Contact Sonus TAC with the information in this alarm and all core files present on the system. Core files can be found in Diagnostics->Restart Report under the '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 messageSIP NOTIFY message.

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

• Node Reboot requested by user "Username" from "IP Address".

• Full factory default requested by user "Username" from "IP Address".

• Full factory default requested via hardware reset buttonCurrent SIP NOTIFY message cannot be processed as software update is in progress.

17

1

alarm

No response

communication

Card;Port;Channel

major

• No response to seizure.

17

2

alarm

Remote end did not back off in glare

communication

Card;Port;Channel

minor

• Remote end did not back off in glare.

17

3

alarm

Wink expected, did not arrive

communication

Card;Port;Channel

major

• Wink expected, did not arrive.

17

4

alarm

No dial tone

communication

Card;Port;Channel

major

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

17

5

event

CAS signaling group disabled

communication

SG

• CAS signaling group disabled.

17

6

alarm

CAS license not enabled

general

System;Service

major