Table Of Contents

Signaling Troubleshooting

Introduction

Signaling Events and Alarms

SIGNALING (1)

SIGNALING (2)

SIGNALING (3)

SIGNALING (4)

SIGNALING (6)

SIGNALING (7)

SIGNALING (8)

SIGNALING (9)

SIGNALING (10)

SIGNALING (11)

SIGNALING (12)

SIGNALING (13)

SIGNALING (14)

SIGNALING (15)

SIGNALING (16)

SIGNALING (17)

SIGNALING (18)

SIGNALING (19)

SIGNALING (20)

SIGNALING (21)

SIGNALING (22)

SIGNALING (23)

SIGNALING (24)

SIGNALING (25)

SIGNALING (26)

SIGNALING (27)

SIGNALING (28)

SIGNALING (29)

SIGNALING (30)

SIGNALING (31)

SIGNALING (32)

SIGNALING (33)

SIGNALING (34)

SIGNALING (36)

SIGNALING (40)

SIGNALING (42)

SIGNALING (43)

SIGNALING (44)

SIGNALING (45)

SIGNALING (46)

SIGNALING (49)

SIGNALING (50)

SIGNALING (51)

SIGNALING (52)

SIGNALING (53)

SIGNALING (54)

SIGNALING (55)

SIGNALING (57)

SIGNALING (58)

SIGNALING (59)

SIGNALING (60)

SIGNALING (61)

SIGNALING (62)

SIGNALING (63)

SIGNALING (64)

SIGNALING (65)

SIGNALING (66)

SIGNALING (68)

SIGNALING (69)

SIGNALING (70)

SIGNALING (71)

SIGNALING (72)

SIGNALING (73)

SIGNALING (74)

SIGNALING (75)

SIGNALING (76)

SIGNALING (77)

SIGNALING (78)

SIGNALING (79)

SIGNALING (80)

SIGNALING (81)

SIGNALING (82)

SIGNALING (83)

SIGNALING (84)

SIGNALING (85)

SIGNALING (86)

SIGNALING (87)

SIGNALING (88)

SIGNALING (89)

SIGNALING (90)

SIGNALING (91)

SIGNALING (92)

SIGNALING (93)

SIGNALING (94)

SIGNALING (95)

SIGNALING (96)

SIGNALING (97)

SIGNALING (98)

SIGNALING (99)

SIGNALING (100)

SIGNALING (101)

SIGNALING (102)

SIGNALING (103)

SIGNALING (104)

SIGNALING (105)

SIGNALING (106)

SIGNALING (107)

SIGNALING (108)

SIGNALING (109)

SIGNALING (110)

SIGNALING (111)

SIGNALING (112)

SIGNALING (113)

SIGNALING (114)

SIGNALING (115)

SIGNALING (116)

SIGNALING (117)

SIGNALING (118)

SIGNALING (119)

SIGNALING (120)

SIGNALING (121)

SIGNALING (122)

SIGNALING (124)

SIGNALING (125)

SIGNALING (126)

SIGNALING (127)

SIGNALING (132)

SIGNALING (133)

SIGNALING (134)

SIGNALING (135)

SIGNALING (136)

SIGNALING (137)

SIGNALING (138)

SIGNALING (139)

SIGNALING (140)

SIGNALING (141)

SIGNALING (142)

SIGNALING (143)

SIGNALING (144)

SIGNALING (145)

SIGNALING (150)

Monitoring Signaling Events

Test Report - Signaling (1)

Message Encoding Error - Signaling (2)

Message Decoding Error - Signaling (3)

Invalid Message Received - Signaling (4)

Database Module Function Call Failure - Signaling (6)

Socket Failure - Signaling (7)

Session Initiation Protocol Message Receive Failure - Signaling (8)

Timeout on Internet Protocol Address - Signaling (9)

Failed to Send Complete Session Initiation Protocol Message - Signaling (10)

Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)

Feature Server is not Up or is not Responding to Call Agent - Signaling (12)

Signaling System 7 Signaling Link Down - Signaling (13)

Link is Remotely Inhibited - Signaling (14)

Link is Locally Inhibited - Signaling (15)

Link is Congested - Signaling (16)

Link: Local Processor Outage - Signaling (17)

Link: Remote Processor Outage - Signaling (18)

Link Set Inaccessible - Signaling (19)

Link Set Congestion - Signaling (20)

Route Set Failure - Signaling (21)

Route Set Congested - Signaling (22)

Destination Point Code Unavailable - Signaling (23)

Destination Point Code Congested - Signaling (24)

Unanswered Blocking Message - Signaling (25)

Unanswered Unblocking Message - Signaling (26)

Unanswered Circuit Group Blocking Message - Signaling (27)

Unanswered Circuit Group Unblocking Message - Signaling (28)

Unanswered Circuit Query Message - Signaling (29)

Unanswered Circuit Validation Test Message - Signaling (30)

Unanswered Reset Circuit Message - Signaling (31)

Unanswered Group Reset Message - Signaling (32)

Unanswered Release Message - Signaling (33)

Unanswered Continuity Check Request Message - Signaling (34)

Trunk Locally Blocked - Signaling (36)

Trunk Remotely Blocked - Signaling (40)

Continuity Testing Message Received on the Specified Circuit Identification Code - Signaling (42)

Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code - Signaling (43)

Continuity Recheck is Performed on Specified Circuit Identification Code - Signaling (44)

Circuit is UNEQUIPPED on Remote Side - Signaling (45)

Specified Circuit Identification Code is Invalid for the Operation - Signaling (46)

A General Processing Error Encountered - Signaling (49)

Unexpected Message for the Call State is Received: Clear Call - Signaling (50)

Set Trunk State as Remotely Unequipped - Signaling (51)

Set Trunk State as NOT Remotely Blocked - Signaling (52)

Set Trunk State as Remotely Blocked - Signaling (53)

Circuit Validation Test Aborted - Signaling (54)

Circuit Validation Successful - Signaling (55)

Continuity Recheck Failed - Signaling (57)

Continuity Recheck Successful - Signaling (58)

Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)

Integrated Services Digital Network STATUS Message Containing Error Indication Received - Signaling (60)

Trunk Operational State Changed by Service Message - Signaling (61)

Received Integrated Services Digital Network RESTART Message - Signaling (62)

Media Gateway/Termination Faulty - Signaling (63)

Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)

Media Gateway Adapter Running out of Heap Memory - Signaling (65)

Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)

Media Gateway or Termination are Found Administratively Out of Service - Signaling (68)

Call Agent and Feature Server Communication Message Timeout - Signaling (69)

Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication - Signaling (70)

Integrated Services Digital Network Unable to Establish D-channel - Signaling (71)

Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time - Signaling (72)

Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired - Signaling (73)

Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired - Signaling (74)

Signaling System 7 Stack not Ready - Signaling (75)

Timeout on Remote Instance - Signaling (76)

Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling - Signaling (77)

Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)

Media Gateway Unreachable - Signaling (79)

Out of Bounds, Memory/Socket Error - Signaling (80)

Insufficient Heap Memory - Signaling (81) (H.323)

Insufficient Shared Memory Pools - Signaling (82) (H.323)

Error While Binding to Socket - Signaling (83)

Reached Maximum Socket Limit - Signaling (84) (H.323)

Initialization Failure - Signaling (85)

Remote H323 Gateway is not Reachable - Signaling (86) (H.323)

H323 Message Parsing Error - Signaling (87) (H.323)

H323 Message Encoding Error - Signaling (88) (H.323)

Gatekeeper not Available/Reachable - Signaling (89)

Alternate Gatekeeper is not Responding - Signaling (90)

Endpoint Security Violation - Signaling (91) (H.323)

Invalid Call Identifier - Signaling (92)

Invalid Call Reference Value - Signaling (93)

Invalid Conference Identifier - Signaling (94)

Invalid Message from the Network - Signaling (95)

Internal Call Processing Error - Signaling (96)

Insufficient Information to Complete Call - Signaling (97)

H323 Protocol Inconsistencies - Signaling (98) (H.323)

Abnormal Call Clearing - Signaling (99)

Codec Negotiation Failed - Signaling (100)

Per Call Security Violation - Signaling (101)

H323 Network Congested - Signaling (102) (H.323)

Aggregation Connection Down - Signaling (103)

Aggregation Unable To Establish Connection - Signaling (104)

Aggregation Gate Set Failed - Signaling (105)

Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)

Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)

Current SIA Configuration only Valid for Simplex Systems - Signaling (108)

Stream Control Transmission Protocol Association Failure - Signaling (109)

Signaling Gateway Group is Out-of-Service - Signaling (110)

Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) - Signaling (111)

Stream Control Transmission Protocol Association Configuration Error - Signaling (112)

Signaling Gateway Failure - Signaling (113)

Signaling Gateway Process is Out-of-Service - Signaling (114)

Invalid Routing Context Received - Signaling (115)

Destination Point Code User Part Unavailable - Signaling (116)

Circuit Validation Test Message Received for an Unequipped Circuit Identification Code - Signaling (117)

Circuit Verification Response Received with Failed Indication - Signaling (118)

Signaling System 7 Adapter Process Faulty - Signaling (119)

Signaling System 7 Module/Signaling System 7 Adapter Faulty - Signaling (120)

Message Transfer Part 3 User Adapter Cannot Go Standby - Signaling (121)

Message Transfer Part 3 User Adapter Cannot Go Active - Signaling (122)

Remote Subsystem is out of Service - Signaling (124)

Signaling Connection Control Part Routing Error - Signaling (125)

Signaling Connection Control Binding Failure - Signaling (126)

Transaction Capabilities Application Part Binding Failure - Signaling (127)

Transaction Capabilities Application Part Reaches the Provisioned Resource Limit - Signaling (132)

Unable to Decode Generic Transport Descriptor Message - Signaling (133)

Signaling System 7 Message Encoding Failure - Signaling (134)

Signaling System 7 Message Decoding Failure - Signaling (135)

Signaling System 7 Message Invalid Received - Signaling (136)

Signaling System 7 Confusion Message Received - Signaling (137)

Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit - Signaling (138)

Signaling System 7 Trunk was Found to be in Erroneous State - Signaling (139) (SS7)

Unanswered Information Message - Signaling (140)

Address not Resolved by Domain Name System Server - Signaling (141)

Session Initiation Protocol Trunk Operationally Out-of-Service - Signaling (142)

Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down - Signaling (143)

All Internet Interface Links to Signaling System 7 Signaling Gateway are Down - Signaling (144)

One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down - Signaling (145)

Stream Control Transmission Protocol Association Congested - Signaling (150)

Troubleshooting Signaling Alarms

Socket Failure - Signaling (7)

Media Gateway Control Protocol

Session Initiation Protocol

Session Initiation Protocol Message Receive Failure - Signaling (8)

Session Initiation Protocol

Timeout on Internet Protocol Address - Signaling (9)

Media Gateway Control Protocol

Session Initiation Protocol

Failed to Send Complete Session Initiation Protocol Message - Signaling (10)

Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)

Feature Server is not Up or is not Responding to Call Agent - Signaling (12)

Signaling System 7 Signaling Link Down - Signaling (13)

Signal System 7 and Call Agent Fail-over Interaction

Link is Remotely Inhibited - Signaling (14)

Link is Locally Inhibited - Signaling (15)

Link is Congested - Signaling (16)

Link: Local Processor Outage - Signaling (17)

Link: Remote Processor Outage - Signaling (18)

Link Set Inaccessible - Signaling (19)

Link Set Congestion - Signaling (20)

Route Set Failure - Signaling (21)

Route Set Congested - Signaling (22)

Destination Point Code Unavailable - Signaling (23)

Destination Point Code Congested - Signaling (24)

Trunk Locally Blocked - Signaling (36)

Trunk Remotely Blocked - Signaling (40)

Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)

Media Gateway/Termination Faulty - Signaling (63)

Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)

Media Gateway Adapter Running out of Heap Memory - Signaling (65)

Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)

Media Gateway or Termination are Found Administratively Out of Service - Signaling (68)

Call Agent and Feature Server Communication Message Timeout - Signaling (69)

Signaling System 7 Stack not Ready - Signaling (75)

Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)

Media Gateway Unreachable - Signaling (79)

Out of Bounds, Memory/Socket Error - Signaling (80)

Insufficient Heap Memory - Signaling (81) (H.323)

Insufficient Shared Memory Pools - Signaling (82) (H.323)

Error While Binding to Socket - Signaling (83)

Reached Maximum Socket Limit - Signaling (84) (H.323)

Initialization Failure - Signaling (85)

Remote H323 Gateway is not Reachable - Signaling (86) (H.323)

H323 Message Parsing Error - Signaling (87) (H.323)

H323 Message Encoding Error - Signaling (88) (H.323)

Gatekeeper not Available/Reachable - Signaling (89)

Alternate Gatekeeper is not Responding - Signaling (90)

Endpoint Security Violation - Signaling (91) (H.323)

Invalid Call Identifier - Signaling (92)

Invalid Call Reference Value - Signaling (93)

Invalid Conference Identifier - Signaling (94)

Invalid Message from the Network - Signaling (95)

Internal Call Processing Error - Signaling (96)

Insufficient Information to Complete Call - Signaling (97)

H323 Protocol Inconsistencies - Signaling (98) (H.323)

Abnormal Call Clearing - Signaling (99)

Codec Negotiation Failed - Signaling (100)

Per Call Security Violation - Signaling (101)

H323 Network Congested - Signaling (102) (H.323)

Aggregation Connection Down - Signaling (103)

Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)

Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)

Current SIA Configuration only Valid for Simplex Systems - Signaling (108)

Stream Control Transmission Protocol Association Failure - Signaling (109)

Message Transfer Part 3 User Adapter Troubleshooting Procedure

Signaling Connection Control Part User Adapter Troubleshooting Procedures

Signaling Gateway Group Is Out-of-Service - Signaling (110)

Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) - Signaling (111)

Message Transfer Part 3 User Adapter Troubleshooting Procedure

Signaling Connection Control Part User Adapter Troubleshooting Procedure

Stream Control Transmission Protocol Association Configuration Error - Signaling (112)

Message Transfer Part 3 User Adapter Troubleshooting Procedure

Signaling Connection Control Part User Adapter Troubleshooting Procedure

Signaling Gateway Failure - Signaling (113)

Signaling Gateway Process Is Out-of-Service - Signaling (114)

Destination Point Code User Part Unavailable - Signaling (116)

Circuit Validation Test Message Received for an Unequipped Circuit Identification Code - Signaling (117)

Circuit Verification Response Received with Failed Indication - Signaling (118)

Signaling System 7 Adapter Process Faulty - Signaling (119)

Signaling System 7 Module/Signaling System 7 Adapter Faulty - Signaling (120)

Message Transfer Part 3 User Adapter Cannot Go Standby - Signaling (121)

Message Transfer Part 3 User Adapter Cannot Go Active - Signaling (122)

Remote Subsystem is Out Of Service - Signaling (124)

Signaling Connection Control Part Routing Error - Signaling (125)

Signaling Connection Control Part Binding Failure - Signaling (126)

Transaction Capabilities Application Part Binding Failure - Signaling (127)

Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit - Signaling (138)

Session Initiation Protocol Trunk Operationally Out-of-Service - Signaling (142)

Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down - Signaling (143)

All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway are Down - Signaling (144)

One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down - Signaling (145)

Stream Control Transmission Protocol Association Congested - Signaling (150)

Signaling Troubleshooting

---

Revised: October 23, 2008, OL-11335-06

Introduction

This chapter provides the information needed to monitor and troubleshoot Signaling events and alarms. This chapter is divided into the following sections:

•Signaling Events and Alarms - Provides a brief overview of each Signaling event and alarm.

•Monitoring Signaling Events - Provides the information needed to monitor and correct Signaling events.

•Troubleshooting Signaling Alarms - Provides the information needed to troubleshoot and correct Signaling alarms.

---

Caution The use of the UNIX ifconfig down command on any signaling interface to test or troubleshoot network or interface failures of the Cisco BTS 10200 Softswitch Signaling Interface may lead to undesirable consequences or conditions.

---

---

Note The following billing records are created when a call is rejected due to overload conditions:
· SS7 termination cause code 42
· Cable signaling stop event cause code "resource unavailable"
Calls rejected by the signaling adapter will not generate a billing record.

---

Signaling Events and Alarms

This section provides a brief overview of the Signaling events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 10-1 lists all signaling events and alarms by severity.

---

Note Click the Signaling message number in Table 10-1 to display information about the event or alarm.

---

Table 10-1 Signaling Events and Alarms by Severity 

CRITICAL	MAJOR	MINOR	WARNING	INFO
SIGNALING (12)	SIGNALING (7)	SIGNALING (10)	SIGNALING (2)	SIGNALING (1)
SIGNALING (64)	SIGNALING (8)	SIGNALING (14)	SIGNALING (3)	SIGNALING (42)
SIGNALING (65)	SIGNALING (9)	SIGNALING (15)	SIGNALING (4)	SIGNALING (43)
SIGNALING (69)	SIGNALING (11)	SIGNALING (16)	SIGNALING (6)	SIGNALING (44)
SIGNALING (75)	SIGNALING (13)	SIGNALING (17)	SIGNALING (25)	SIGNALING (45)
SIGNALING (80)	SIGNALING (19)	SIGNALING (18)	SIGNALING (26)	SIGNALING (46)
SIGNALING (81)	SIGNALING (20)	SIGNALING (22)	SIGNALING (27)	SIGNALING (49)
SIGNALING (82)	SIGNALING (21)	SIGNALING (24)	SIGNALING (28)	SIGNALING (50)
SIGNALING (83)	SIGNALING (23)	SIGNALING (36)	SIGNALING (29)	SIGNALING (51)
SIGNALING (84)	SIGNALING (40)	SIGNALING (78)	SIGNALING (30)	SIGNALING (52)
SIGNALING (85)	SIGNALING (59)	SIGNALING (92)	SIGNALING (31)	SIGNALING (53)
SIGNALING (107)	SIGNALING (63)	SIGNALING (93)	SIGNALING (32)	SIGNALING (54)
SIGNALING (110)	SIGNALING (66)	SIGNALING (94)	SIGNALING (33)	SIGNALING (55)
SIGNALING (119)	SIGNALING (68)	SIGNALING (95)	SIGNALING (34)	SIGNALING (57)
SIGNALING (120)	SIGNALING (79)	SIGNALING (96)	SIGNALING (60)	SIGNALING (58)
SIGNALING (142)	SIGNALING (86)	SIGNALING (97)	SIGNALING (70)	SIGNALING (61)
SIGNALING (144)	SIGNALING (87)	SIGNALING (98)	SIGNALING (71)	SIGNALING (62)
	SIGNALING (88)	SIGNALING (99)	SIGNALING (72)	SIGNALING (76)
	SIGNALING (89)	SIGNALING (100)	SIGNALING (73)	SIGNALING (77)
	SIGNALING (90)	SIGNALING (101)	SIGNALING (74)	SIGNALING (104)
	SIGNALING (91)	SIGNALING (102)	SIGNALING (115)	SIGNALING (105)
	SIGNALING (103)	SIGNALING (106)	SIGNALING (132)	SIGNALING (133)
	SIGNALING (108)	SIGNALING (112)	SIGNALING (138)	SIGNALING (134)
	SIGNALING (109)	SIGNALING (117)	SIGNALING (141)	SIGNALING (135)
	SIGNALING (111)	SIGNALING (118)		SIGNALING (136)
	SIGNALING (113)	SIGNALING (124)		SIGNALING (137)
	SIGNALING (114)	SIGNALING (143)		SIGNALING (139)
	SIGNALING (116)	SIGNALING (145)		SIGNALING (140)
	SIGNALING (121)	SIGNALING (150)
	SIGNALING (122)
	SIGNALING (125)
	SIGNALING (126)
	SIGNALING (127)

SIGNALING (1)

For additional information, refer to the "Test Report - Signaling (1)" section.

DESCRIPTION	Test Report
SEVERITY	Information (INFO)
THRESHOLD	10000
THROTTLE	0

SIGNALING (2)

To monitor and correct the cause of the event, refer to the "Message Encoding Error - Signaling (2)" section.

DESCRIPTION	Message Encoding Error
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Endpoint Name - STRING [40] Message Type - STRING [40] Gateway Type - STRING [32]
PRIMARY CAUSE	Issued when there is a message encoding error on sending an MGCP message.
PRIMARY ACTION	If this Error Report is issued while doing interoperability testing with a gateway using MGCP, then capture the MGCP message flow and forward it to Cisco TAC technical support for analysis. (Contact Cisco TAC.)
SECONDARY ACTION	When an unexpected MGCP message occurs, call Cisco TAC technical support to identify the root cause. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (3)

To monitor and correct the cause of the event, refer to the "Message Decoding Error - Signaling (3)" section.

DESCRIPTION	Message Decoding Error
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Endpoint Name - STRING [40] Gateway Type - STRING [40] Message Type - STRING [40]
PRIMARY CAUSE	Issued when there is a message decoding error on receiving an MGCP message.
PRIMARY ACTION	If this Error Report is issued while doing interoperability testing with a gateway using MGCP, then capture the MGCP message flow and forward it to Cisco TAC technical support for analysis. (Contact Cisco TAC.)
SECONDARY ACTION	When an unexpected MGCP message occurs, call Cisco TAC technical support to identify the root cause. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (4)

To monitor and correct the cause of the event, refer to the "Invalid Message Received - Signaling (4)" section.

DESCRIPTION	Invalid Message Received
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Endpoint Name - STRING [40] Message Type - STRING [40]
PRIMARY CAUSE	Issued when a signaling adapter has received an invalid message from the specified endpoint.
PRIMARY ACTION	Monitor the associated signaling link to see if there is an interruption of service on the link.
SECONDARY ACTION	If there is a communication problem, restart the link.
TERNARY ACTION	Verify that the version of the protocol used by the device at the endpoint is consistent with the version expected by the call agent.
SUBSEQUENT ACTION	If there is a mismatch, then either the endpoint or call agent must be re-provisioned.

---

Note SIGNALING (5) is not used.

---

SIGNALING (6)

To monitor and correct the cause of the event, refer to the "Database Module Function Call Failure - Signaling (6)" section.

DESCRIPTION	Database Module Function Call Failure
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Endpoint Name - STRING [40] Return Code - FOUR_BYTES Function Name - STRING [64] Calling Function - STRING [64] Index - FOUR_BYTES
PRIMARY CAUSE	A signaling adapter has detected an error while accessing a database interface.
PRIMARY ACTION	If the database that the adapter attempted to access is not available, restart the associated process.
SECONDARY ACTION	If an incompatible versions of the signaling adapter process and the database processes are present on the system, correct the error and restart the processes.

SIGNALING (7)

To troubleshoot and correct the cause of the alarm, refer to the "Socket Failure - Signaling (7)" section.

DESCRIPTION	Socket Failure
SEVERITY	MAJOR
THRESHOLD	30
THROTTLE	0
DATAWORDS	Reason Text - STRING [30]
PRIMARY CAUSE	Issued when there is a failure in creating the UDP port used by the MGCP stacks.
PRIMARY ACTION	Reconfigure the MGCP stack to use a free UDP port.
SECONDARY CAUSE	Some other application may already be active on the same UDP port and IP address to which the Call Agent MGCP stack is assigned.

SIGNALING (8)

To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Message Receive Failure - Signaling (8)" section.

DESCRIPTION	Session Initiation Protocol Message Receive Failure (SIP Message Receive Failure)
SEVERITY	MAJOR
THRESHOLD	30
THROTTLE	0
DATAWORDS	Reason Text - STRING [50]
PRIMARY CAUSE	Operating system level network errors or invalid network configuration.
PRIMARY ACTION	Have your network administrator resolve network errors. Contact Cisco TAC if you need assistance. Manually clear alarm. Restart this call agent instance using the platform start command.

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (9)

To troubleshoot and correct the cause of the alarm, refer to the "Timeout on Internet Protocol Address - Signaling (9)" section.

DESCRIPTION	Timeout on Internet Protocol Address (Timeout on IP Address)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	MGW/Term Name - STRING [80] Gateway Type - STRING [32] Possible Cause - STRING [32]
PRIMARY CAUSE	Issued when opticall is unable to communicate with a gateway.
PRIMARY ACTION	Verify that the gateway is both configured for service and that it has been set in service.
SECONDARY ACTION	Attempt to ping the gateway using the Internet Protocol (IP) address from the event report. If the ping is not successful, then diagnose the issue that prevents the address from being reached.
TERNARY ACTION	Use the status media gateway (MGW) identification (ID) = xxx, where xxx is the IP address given in the event report. If the status is not in service (INS), then use control mgw command to put it in service.

SIGNALING (10)

To troubleshoot and correct the cause of the alarm, refer to the "Failed to Send Complete Session Initiation Protocol Message - Signaling (10)" section.

DESCRIPTION	Failed to Send Complete Session Initiation Protocol Message (Failed to Send Complete SIP Message)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Destination Address - STRING [64]
PRIMARY CAUSE	Notifies the user that the Session Initiation Protocol (SIP) stack failed to send an SIP message due to it exceeding the maximum length of a UDP packet.
PRIMARY ACTION	If encountered in normal network operations, the message should be captured on passive testing equipment and sent to Cisco TAC for evaluation. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (11)

To troubleshoot and correct the cause of the alarm, refer to the "Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)" section.

DESCRIPTION	Failed to Allocate Session Initiation Protocol Control Block (Failed to Allocate SIP Control Block)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Size - TWO_BYTES Detail - STRING [80]
PRIMARY CAUSE	Issued when there is not enough memory to allocate a SIP call control block.
PRIMARY ACTION	Increase the SIP call control block (CCB) count specified in mem.cfg file.
SECONDARY ACTION	Restart call agent to take effect.

SIGNALING (12)

To troubleshoot and correct the cause of the alarm, refer to the "Feature Server is not Up or is not Responding to Call Agent - Signaling (12)" section.

DESCRIPTION	Feature Server is not Up or is not Responding to Call Agent
SEVERITY	CRITICAL
THRESHOLD	30
THROTTLE	0
DATAWORDS	Domain Name of FS - STRING [65] Feature Server ID - STRING [20]
PRIMARY CAUSE	Feature server platform is down or is not operating properly.
PRIMARY ACTION	Restart the applicable feature server.

SIGNALING (13)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Signaling Link Down - Signaling (13)" section.

DESCRIPTION	Signaling System 7 Signaling Link Down (SS7 Signaling Link Down)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link_Number - ONE_BYTE Link_Name - STRING [25]
PRIMARY CAUSE	Signaling System 7 (SS7) trunk group may be out-of-service (OOS).
PRIMARY ACTION	Use control ss7-trunk-grp to place the trunk group in service (INS).
SECONDARY CAUSE	The local Ulticom stack may be down.
SECONDARY ACTION	Run the Ulticom stack again.
TERNARY CAUSE	SS7 link may be disconnected or faulty.
TERNARY ACTION	Check the Ulticom local configuration.
SUBSEQUENT CAUSE	Remote SS7 signaling site may be down or incorrectly configured.
SUBSEQUENT ACTION	Check the Ulticom remote configuration.

SIGNALING (14)

To troubleshoot and correct the cause of the alarm, refer to the "Link is Remotely Inhibited - Signaling (14)" section.

DESCRIPTION	Link is Remotely Inhibited
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link - ONE_BYTE Link Name - STRING [8]
PRIMARY CAUSE	Issued when the specified Signaling System 7 (SS7) link is inhibited at the remote end.
PRIMARY ACTION	Monitor events at the network level for any related to the specified SS7 link. Restorative actions needs to be taken on the remote end.

SIGNALING (15)

To troubleshoot and correct the cause of the alarm, refer to the "Link is Locally Inhibited - Signaling (15)" section.

DESCRIPTION	Link is Locally Inhibited
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link No - ONE_BYTE Link Name - STRING [8]
PRIMARY CAUSE	Issued when the specified SS7 link is inhibited at the local end.
PRIMARY ACTION	Verify that the SS7 signaling adapter process is running and that the SS7 interface card(s) are in service.
SECONDARY ACTION	If a component is found to be non-operational, restore it to service.

SIGNALING (16)

To troubleshoot and correct the cause of the alarm, refer to the "Link is Congested - Signaling (16)" section.

DESCRIPTION	Link is Congested
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link No - ONE_BYTE
PRIMARY CAUSE	Issued when the specified SS7 link is experiencing congestion.
PRIMARY ACTION	Monitor event reports at the network level to determine if the traffic load on the specified SS7 link is too high on the local end, or if the remote end is lagging in processing the traffic.
SECONDARY ACTION	Verify that the SS7 link has not degraded in quality.
TERNARY ACTION	Verify that the traffic load has not become unbalanced if multiple SS7 links are used.
SUBSEQUENT ACTION	Verify that local SS7 signaling adapter process is running normally.

SIGNALING (17)

To troubleshoot and correct the cause of the alarm, refer to the "Link: Local Processor Outage - Signaling (17)" section.

DESCRIPTION	Link: Local Processor Outage
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link No - ONE_BYTE Link Name - STRING [8]
PRIMARY CAUSE	Issued when the specified SS7 link has experienced a processor outage.
PRIMARY ACTION	Monitor the system for maintenance event reports associated with the signaling adapter or underlying platform instance that support the specified SS7 link. Verify that the process and or platform are restarted and returned to service.

SIGNALING (18)

To troubleshoot and correct the cause of the alarm, refer to the "Link: Remote Processor Outage - Signaling (18)" section.

DESCRIPTION	Link: Remote Processor Outage
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link No - ONE_BYTE Link Name - STRING [8]
PRIMARY CAUSE	Issued when the specified SS7 link has experienced a processor outage.
PRIMARY ACTION	Monitor the network level event reports for any events associated with the processing complex used by the specified SS7 link. Verify that the SS7 link is returned to service.

SIGNALING (19)

To troubleshoot and correct the cause of the alarm, refer to the "Link Set Inaccessible - Signaling (19)" section.

DESCRIPTION	Link Set Inaccessible
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link Set No - ONE_BYTE Link Set Name - STRING [8]
PRIMARY CAUSE	Issued when the specified SS7 link set is inaccessible.
PRIMARY ACTION	If the SS7 signaling adapter is not running normally and the associated call agent platform is not active, return them to service.

SIGNALING (20)

To troubleshoot and correct the cause of the alarm, refer to the "Link Set Congestion - Signaling (20)" section.

DESCRIPTION	Link Set Congestion
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Link Set No - ONE_BYTE Link Set Name - STRING [8] Congestion Level - ONE_BYTE
PRIMARY CAUSE	Issued when the specified SS7 link set is experiencing congestion.
PRIMARY ACTION	Monitor event reports at the network level to determine if the traffic load on the specified SS7 link set is too high on the local end, or if the remote end is lagging in processing the traffic.
SECONDARY ACTION	Verify that the SS7 link set has not degraded in quality.
TERNARY ACTION	Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used.
SUBSEQUENT ACTION	Verify that local SS7 signaling adapter process is running normally.

SIGNALING (21)

To troubleshoot and correct the cause of the alarm, refer to the "Route Set Failure - Signaling (21)" section.

DESCRIPTION	Route Set Failure
SEVERITY	MAJOR
THRESHOLD	200
THROTTLE	0
DATAWORDS	Route Set No - TWO_BYTES Route Set Name - STRING [8]
PRIMARY CAUSE	Issued when the specified route set has experienced a failure.
PRIMARY ACTION	Verify that the processing complex supporting the route set is functional.
SECONDARY ACTION	Monitor event reports at the network level to determine the failing component and verify its restoral to service.

SIGNALING (22)

To troubleshoot and correct the cause of the alarm, refer to the "Route Set Congested - Signaling (22)" section.

DESCRIPTION	Route Set Congested
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Route Set No - TWO_BYTES Route Set Name - STRING [8] Congestion Level - ONE_BYTE
PRIMARY CAUSE	Issued when the specified route set is experiencing congestion.
PRIMARY ACTION	Monitor event reports at the network level to determine if the traffic load on the specified SS7 link set is too high on the local end, or if the remote end is lagging in processing the traffic.
SECONDARY ACTION	Verify that the SS7 link set has not degraded in quality.
TERNARY ACTION	Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used.
SUBSEQUENT ACTION	Verify that local SS7 signaling adapter process is running normally.

SIGNALING (23)

To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Unavailable - Signaling (23)" section.

DESCRIPTION	Destination Point Code Unavailable (DPC Unavailable)
SEVERITY	MAJOR
THRESHOLD	200
THROTTLE	0
DATAWORDS	DPC - STRING [12]
PRIMARY CAUSE	Issued when the specified destination point code (DPC) is not available. This is usually caused by one of the following: 1) A failure in the affected DPC. 2) An unavailable route between the Cisco BTS 10200 Softswitch and the affected DPC.
PRIMARY ACTION	Verify that alternate routing has been assigned for traffic destined to the affected DPC.

SIGNALING (24)

To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Congested - Signaling (24)" section.

DESCRIPTION	Destination Point Code Congested (DPC Congested)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	DPC - STRING [12] DPC Type - ONE_BYTE Congestion Level - ONE_BYTE
PRIMARY CAUSE	Issued when the specified destination point code is congested.
PRIMARY ACTION	Monitor event reports at the network level to determine if the traffic load to the specified DPC is too high on the local end, or if the remote end is lagging in processing the traffic.

SIGNALING (25)

To monitor and correct the cause of the event, refer to the "Unanswered Blocking Message - Signaling (25)" section.

DESCRIPTION	Unanswered Blocking Message (Unanswered BLO)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a blocking (BLO) message was not acknowledged before the timer 13 (T13) expired for the associated circuit identification code (CIC).
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
SECONDARY ACTION	Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
TERNARY ACTION	Verify that the T13 timer is set to an appropriate level.
SUBSEQUENT ACTION	Verify that the SS7 link is not congested.

SIGNALING (26)

To monitor and correct the cause of the event, refer to the "Unanswered Unblocking Message - Signaling (26)" section.

DESCRIPTION	Unanswered Unblocking Message (Unanswered UBL)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a unblocking message (UBL) message was not acknowledged before the timer 15 (T15) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
SECONDARY ACTION	Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
TERNARY ACTION	Verify that the T13 timer is set to an appropriate level.
SUBSEQUENT ACTION	Verify that the SS7 link is not congested.

SIGNALING (27)

To monitor and correct the cause of the event, refer to the "Unanswered Circuit Group Blocking Message - Signaling (27)" section.

DESCRIPTION	Unanswered Circuit Group Blocking Message (Unanswered CGB)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a circuit group blocking (CGB) message was not acknowledged before the timer 19 (T19) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
SECONDARY ACTION	Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
TERNARY ACTION	Verify that the T13 timer is set to an appropriate level.
SUBSEQUENT ACTION	Verify that the SS7 link is not congested.

SIGNALING (28)

To monitor and correct the cause of the event, refer to the "Unanswered Circuit Group Unblocking Message - Signaling (28)" section.

DESCRIPTION	Unanswered Circuit Group Unblocking Message (Unanswered CGU)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a circuit group unblocking (CGU) message was not acknowledged before the timer 21 (T21) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally.
SECONDARY ACTION	Verify that the call agent platform is active.
TERNARY ACTION	Verify that the SS7 interface hardware is in service.
SUBSEQUENT ACTION	Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

SIGNALING (29)

To monitor and correct the cause of the event, refer to the "Unanswered Circuit Query Message - Signaling (29)" section.

DESCRIPTION	Unanswered Circuit Query Message (Unanswered CQM)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a circuit query message (CQM) message was not acknowledged before the timer 28 (T28) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally.
SECONDARY ACTION	Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service.
TERNARY ACTION	Verify that the associated SS7 signaling link is available.
SUBSEQUENT ACTION	Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

SIGNALING (30)

To monitor and correct the cause of the event, refer to the "Unanswered Circuit Validation Test Message - Signaling (30)" section.

DESCRIPTION	Unanswered Circuit Validation Test Message (Unanswered CVT)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a circuit validation test (CVT) message was not acknowledged before the Tcvt expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally.
SECONDARY ACTION	Verify that the call agent platform is active.
TERNARY ACTION	Verify that the SS7 interface hardware is in service.
SUBSEQUENT ACTION	Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

SIGNALING (31)

To monitor and correct the cause of the event, refer to the "Unanswered Reset Circuit Message - Signaling (31)" section.

DESCRIPTION	Unanswered Reset Circuit Message (Unanswered RSC)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a reset circuit (RSC) message was not acknowledged before the timer 17 (T17) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
SECONDARY ACTION	Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
TERNARY ACTION	Verify that the T13 timer is set to an appropriate level.
SUBSEQUENT ACTION	Verify that the SS7 link is not congested.

SIGNALING (32)

To monitor and correct the cause of the event, refer to the "Unanswered Group Reset Message - Signaling (32)" section.

DESCRIPTION	Unanswered Group Reset Message (Unanswered GRS)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a group reset (GRS) message was not acknowledged before the timer 23 (T23) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
SECONDARY ACTION	Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
TERNARY ACTION	Verify that the T13 timer is set to an appropriate level.
SUBSEQUENT ACTION	Verify that the SS7 link is not congested.

SIGNALING (33)

To monitor and correct the cause of the event, refer to the "Unanswered Release Message - Signaling (33)" section.

DESCRIPTION	Unanswered Release Message (Unanswered REL)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a release (REL) message was not acknowledged before the timer 5 (T5) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally.
SECONDARY ACTION	Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service.
TERNARY ACTION	Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level.
SUBSEQUENT ACTION	Verify that the SS7 link is not congested.

SIGNALING (34)

To monitor and correct the cause of the event, refer to the "Unanswered Continuity Check Request Message - Signaling (34)" section.

DESCRIPTION	Unanswered Continuity Check Request Message (Unanswered CCR)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when an loop prevention acknowledgement (LPA) message was not acknowledged before the timer continuity check request (TCCR) expired for the associated CIC.
PRIMARY ACTION	Verify that the SS7 signaling adapter processes is running normally.
SECONDARY ACTION	Verify that the call agent platform is active.
TERNARY ACTION	Verify that the SS7 interface hardware is in service.
SUBSEQUENT ACTION	Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

---

Note SIGNALING (35) is not used.

---

SIGNALING (36)

To troubleshoot and correct the cause of the alarm, refer to the "Trunk Locally Blocked - Signaling (36)" section. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

DESCRIPTION	Trunk Locally Blocked
SEVERITY	MINOR
THRESHOLD	500
THROTTLE	0
DATAWORDS	CIC Number - STRING [40] TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20] MGW-EP-NAME - STRING [64] MGW-TSAP-ADDR - STRING [80] Reason - STRING [80]
PRIMARY CAUSE	Issued when a BLO or CGB message was sent on the specified CIC.
PRIMARY ACTION	Refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

---

Note SIGNALING (37) through SIGNALING (39) are not used.

---

SIGNALING (40)

To troubleshoot and correct the cause of the alarm, refer to the "Trunk Remotely Blocked - Signaling (40)" section.

DESCRIPTION	Trunk Remotely Blocked
SEVERITY	MAJOR
THRESHOLD	500
THROTTLE	0
DATAWORDS	CIC Number - STRING [40] TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20] MGW-EP-NAME - STRING [64] MGW-TSAP-ADDR - STRING [80]
PRIMARY CAUSE	Issued when a BLO or CGB message was received on the specified CIC if it is SS7 trunk. Issued when a SERVICE OOS message is received for Integrated Services Digital Network (ISDN) trunks. Issued when Reverse Make Busy (RBZ) signal is received for channel-associated signaling (CAS) operator trunk.
PRIMARY ACTION	No action required. Can manually recover from this condition locally by controlling effected trunks to unequipped (UEQP) state and back INS.

---

Note SIGNALING (41) is not used.

---

SIGNALING (42)

For additional information, refer to the "Continuity Testing Message Received on the Specified Circuit Identification Code - Signaling (42)" section.

DESCRIPTION	Continuity Testing Message Received on the Specified Circuit Identification Code (COT Message Received on the Specified CIC)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a continuity testing (COT) message was received on the specified CIC.
PRIMARY ACTION	No action required.

SIGNALING (43)

For additional information, refer to the "Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code - Signaling (43)" section.

DESCRIPTION	Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code (RLC Received in Response to RSC Message on the Specified CIC)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a release complete (RLC) message was received in response to a RSC message on the specified CIC.
PRIMARY ACTION	No action required.

SIGNALING (44)

For additional information, refer to the "Continuity Recheck is Performed on Specified Circuit Identification Code - Signaling (44)" section.

DESCRIPTION	Continuity Recheck is Performed on Specified Circuit Identification Code (Continuity Recheck is Performed on Specified CIC)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a continuity recheck was performed on the specified CIC.
PRIMARY ACTION	No action required.

SIGNALING (45)

For additional information, refer to the "Circuit is UNEQUIPPED on Remote Side - Signaling (45)" section.

DESCRIPTION	Circuit is UNEQUIPPED on Remote Side
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when an unequipped circuit has been detected on the remote side.
PRIMARY ACTION	Monitor the event reports at the network level to verify if an existing circuit was unequipped causing a status mismatch with the local end.

SIGNALING (46)

For additional information, refer to the "Specified Circuit Identification Code is Invalid for the Operation - Signaling (46)" section.

DESCRIPTION	Specified Circuit Identification Code is Invalid for the Operation (Specified CIC is Invalid for the Operation)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when an invalid operation was performed on the specified CIC.
PRIMARY ACTION	Verify that the SS7 provisioning tables are properly configured at the circuit level.

---

Note SIGNALING (47) and SIGNALING (48) are not used.

---

SIGNALING (49)

For additional information, refer to the "A General Processing Error Encountered - Signaling (49)" section.

DESCRIPTION	A General Processing Error Encountered
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a general SS7 processing error occurred due to all resources being busy or an invalid event occurring.
PRIMARY ACTION	Verify the status of the signaling adapter process and the SS7 signaling interface to verify proper operation.

SIGNALING (50)

For additional information, refer to the "Unexpected Message for the Call State is Received: Clear Call - Signaling (50)" section.

DESCRIPTION	Unexpected Message for the Call State is Received: Clear Call
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when an unexpected message was received for the current call state.
PRIMARY ACTION	The call is cleared. Verify the status of the signaling adapter process and the SS7 signaling interface to verify proper operation.

SIGNALING (51)

For additional information, refer to the "Set Trunk State as Remotely Unequipped - Signaling (51)" section.

DESCRIPTION	Set Trunk State as Remotely Unequipped
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when the specified CIC is marked at remotely unequipped due to the CQM response indicating that it is unequipped at the far end.
PRIMARY ACTION	Equip the trunk circuit at the far end.

SIGNALING (52)

For additional information, refer to the "Set Trunk State as NOT Remotely Blocked - Signaling (52)" section.

DESCRIPTION	Set Trunk State as NOT Remotely Blocked
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when the specified CIC is marked as not remotely blocked due to the CQM response indicating that it is not remotely blocked at the far end.
PRIMARY ACTION	No action required.

SIGNALING (53)

For additional information, refer to the "Set Trunk State as Remotely Blocked - Signaling (53)" section.

DESCRIPTION	Set Trunk State as Remotely Blocked
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when the specified CIC is marked as remotely blocked due to the CQM response indicating that it is remotely blocked at the far end.
PRIMARY ACTION	Clear the blocking situation at the far end based on network level event reports.

SIGNALING (54)

For additional information, refer to the "Circuit Validation Test Aborted - Signaling (54)" section.

DESCRIPTION	Circuit Validation Test Aborted
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when the circuit specified failed a validation test due to an internal failure.
PRIMARY ACTION	Verify the SS7 signaling adapter process and SS7 interface is operating normally.

SIGNALING (55)

For additional information, refer to the "Circuit Validation Successful - Signaling (55)" section.

DESCRIPTION	Circuit Validation Successful
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when the specified circuit was successfully validated.
PRIMARY ACTION	No action required.

---

Note SIGNALING (56) is not used.

---

SIGNALING (57)

For additional information, refer to the "Continuity Recheck Failed - Signaling (57)" section.

DESCRIPTION	Continuity Recheck Failed
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a continuity recheck of the specified CIC failed.
PRIMARY ACTION	Verify the SS7 signaling adapter process and SS7 interface is operating normally.

SIGNALING (58)

For additional information, refer to the "Continuity Recheck Successful - Signaling (58)" section.

DESCRIPTION	Continuity Recheck Successful
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Issued when a continuity recheck of the specified CIC was successful.
PRIMARY ACTION	No action required.

SIGNALING (59)

To troubleshoot and correct the cause of the alarm, refer to the "Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)" section.

DESCRIPTION	Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway (Auto State Change for ISDN Trunk Group by Media Gateway)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES Media Gateway Name - STRING [65] Media Gateway Index - FOUR_BYTES Service Status - FOUR_BYTES
PRIMARY CAUSE	Issued when the specified ISDN trunk group's status was changed due to a media gateway operation.
PRIMARY ACTION	Monitor the event reports at the network level to determine which media gateway caused the status change of the trunk group.
SECONDARY ACTION	Verify that the gateway is reconfigured properly to support the usage of the trunk group.

SIGNALING (60)

To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network STATUS Message Containing Error Indication Received - Signaling (60)" section.

DESCRIPTION	Integrated Services Digital Network STATUS Message Containing Error Indication Received (ISDN STATUS Message Containing Error Indication Received)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Termination Name - STRING [40] Termination Index - FOUR_BYTES Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES Cause Value - ONE_BYTE Call State - ONE_BYTE
PRIMARY CAUSE	Issued when an ISDN status message was received containing an error indication for the specified termination.
PRIMARY ACTION	If the specified termination is not operating normally, place it in service state.

SIGNALING (61)

For additional information, refer to the "Trunk Operational State Changed by Service Message - Signaling (61)" section.

DESCRIPTION	Trunk Operational State Changed by Service Message
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	Termination Name - STRING [40] Termination Index - FOUR_BYTES Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES Service Status - FOUR_BYTES
PRIMARY CAUSE	Issued when the specified trunk group's operational status was changed via a service message from the specified gateway.
PRIMARY ACTION	Monitor the event reports at the network level to verify that the specified gateway and terminations are operating normally.

SIGNALING (62)

For additional information, refer to the "Received Integrated Services Digital Network RESTART Message - Signaling (62)" section.

DESCRIPTION	Received Integrated Services Digital Network RESTART Message (Received ISDN RESTART Message)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	Termination Name - STRING [40] Termination Index - FOUR_BYTES Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES Flag - FOUR_BYTES
PRIMARY CAUSE	Issued when an ISDN restart message was received from the specified gateway.
PRIMARY ACTION	Monitor the event reports at the network level to verify that the specified gateway and terminations are operating normally.

SIGNALING (63)

To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway/Termination Faulty - Signaling (63)" section.

DESCRIPTION	Media Gateway/Termination Faulty
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Fully Qualified Name - STRING [80] Type of Gateway - STRING [32] Reason for Failure - STRING [80]
PRIMARY CAUSE	Issued when a media gateway or termination has gone faulty due to the detection of an unknown endpoint, unknown package type, and unknown event, a hardware failure, or a general call agent error.
PRIMARY ACTION	Verify the proper operation of the media gateway specified. Place the termination out-of-service and then back into service from the call agent.

SIGNALING (64)

To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)" section.

DESCRIPTION	Media Gateway Adapter Running out of Shared Memory Pools (MGA Running out of Shared Memory Pools)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
PRIMARY CAUSE	Issued when the Media Gateway Control Protocol (MGCP) signaling adapter was unable to allocate data store for an inter-process communication (IPC) message due to a lack of resources.
PRIMARY ACTION	Call Cisco TAC technologies for assistance. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (65)

To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Adapter Running out of Heap Memory - Signaling (65)" section.

DESCRIPTION	Media Gateway Adapter Running out of Heap Memory (MGA Running out of Heap Memory)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
PRIMARY CAUSE	Issued when the MGCP signaling adapter was unable to allocate data store for an IPC message from the heap due to a lack of resources.
PRIMARY ACTION	Call Cisco TAC Technologies for assistance. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (66)

To troubleshoot and correct the cause of the alarm, refer to the "Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)" section.

DESCRIPTION	Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - (CA Internal Error (Because of Which MGA has to Start Automatically))
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Fully Qualified Name - STRING [80] Reason - STRING [80] Detailed Reason - STRING [80]
PRIMARY CAUSE	Issued when a call agent internal error has occurred causing the restart of the MGCP signaling adapter.
PRIMARY ACTION	Send log files to Cisco TAC for analysis and corrective action. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

---

Note SIGNALING (67) is not used.

---

SIGNALING (68)

To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway or Termination are Found Administratively Out of Service - Signaling (68)" section. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

DESCRIPTION	Media Gateway or Termination are Found Administratively Out of Service
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Fully Qualified Name - STRING [80] Type of MGW- STRING [32] Failure Cause - STRING [80] Subscriber Info - STRING [80] ICMP Ping Status - STRING [80]
PRIMARY CAUSE	Issued when the specified media gateway is going out-of-service due to being powered down, the MGCP application going faulty, or a hardware failure.
PRIMARY ACTION	Cycle the power on the specified media gateway. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

SIGNALING (69)

To troubleshoot and correct the cause of the alarm, refer to the "Call Agent and Feature Server Communication Message Timeout - Signaling (69)" section.

DESCRIPTION	Call Agent and Feature Server Communication Message Timeout (CA and FS Communication Message Timeout)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Configured CA Name - STRING [70]
PRIMARY CAUSE	Call Agent (CA) - Feature Server (FS) communication failure due to wrong system configuration; -OR- CA or FS is down.
PRIMARY ACTION	Check the configuration related to CA-FS communication. FS table entries, CA entry.

SIGNALING (70)

To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication - Signaling (70)" section.

DESCRIPTION	Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication (ISDN Unable to Restore D-channel Due to Failed Communication)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES
PRIMARY CAUSE	The ISDN signaling adapter is unable to restore a D-channel due to incorrect backhaul provisioning at the media gateway or call agent.
PRIMARY ACTION	Ensure the provisioning of the backhaul port is correct at both the call agent and media gateway.

SIGNALING (71)

To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network Unable to Establish D-channel - Signaling (71)" section.

DESCRIPTION	Integrated Services Digital Network Unable to Establish D-channel (ISDN Unable to Establish D-channel)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES
PRIMARY CAUSE	The ISDN signaling adapter is unable to establish a D-channel due to layer one parameters not being provisioned correctly or improper provisioning of the network or user side.
PRIMARY ACTION	Verify the correct provisioning at the media gateway.

SIGNALING (72)

To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time - Signaling (72)" section.

DESCRIPTION	Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time (ISDN - Calls Lost Due to D-channel Down for Period of Time)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES
PRIMARY CAUSE	The ISDN signaling adapter has lost calls due to a D-channel being down as a result of a media gateway power loss or a loss of connection between the private branch exchange (PBX) and media gateway.
PRIMARY ACTION	Resupply power to the media gateway and verify that the connection between the PBX and media gateway is intact.

SIGNALING (73)

To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired - Signaling (73)" section.

DESCRIPTION	Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired (ISDN - Unable to Send RESTART Due to RESTART Timer Expired)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Termination Name - STRING [40] Termination Index - FOUR_BYTES Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES Restart Class - FOUR_BYTES
PRIMARY CAUSE	The ISDN signaling adapter was unable to send a RESTART message due to the expiration of the RESTART timer.
PRIMARY ACTION	Verify that the RESTART timer is set to an appropriate level.

SIGNALING (74)

To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired - Signaling (74)" section.

DESCRIPTION	Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired (ISDN: Unable to Send the SERVICE Due to the SERVICE Timer Expired)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Termination Name - STRING [40] Termination Index - FOUR_BYTES Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES Service Status - FOUR_BYTES
PRIMARY CAUSE	The ISDN signaling adapter was unable to send a SERVICE message due to the expiration of the SERVICE timer.
PRIMARY ACTION	Ensure that the RESTART timer is set to an appropriate level.

SIGNALING (75)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Stack not Ready - Signaling (75)" section.

DESCRIPTION	Signaling System 7 Stack not Ready (SS7 Stack not Ready)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	LogicalName - STRING [64]
PRIMARY CAUSE	SS7 stack not configured properly.
PRIMARY ACTION	Check SS7 stack configuration.
SECONDARY CAUSE	SS7 stack not ready.
SECONDARY ACTION	Check SS7 stack status. Do platform "start -i omni" to bring up SS7 stack.

SIGNALING (76)

For additional information, refer to the "Timeout on Remote Instance - Signaling (76)" section.

DESCRIPTION	Timeout on Remote Instance
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	Port Number - TWO_BYTES Hostname - STRING [64]
PRIMARY CAUSE	Communication between call agent and remote instance is faulty.
PRIMARY ACTION	No action needed.

SIGNALING (77)

For additional information, refer to the "Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling - Signaling (77)" section.

DESCRIPTION	Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling (ISDN D-channel Switchover for NFAS)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group ID - FOUR_BYTES Trunk Group Index - FOUR_BYTES
PRIMARY CAUSE	Manually switched the D-channels using the command line interface (CLI).
PRIMARY ACTION	Verify operator action.
SECONDARY CAUSE	Lost active D-channel.
SECONDARY ACTION	Verify that gateway is operational and connection to PBX is good.

SIGNALING (78)

To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)" section.

DESCRIPTION	Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling (ISDN Single D-channel Down for NFAS)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group ID - FOUR_BYTES Trunk Group Idx - FOUR_BYTES IS Primary D Channel - FOUR_BYTES
PRIMARY CAUSE	One of the ISDN D-channels in primary rate interface (PRI) is down.
PRIMARY ACTION	Check gateway power, and gateway connection to PBX.

SIGNALING (79)

To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Unreachable - Signaling (79)" section. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

DESCRIPTION	Media Gateway Unreachable
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Entity Name - STRING [40] General Context - STRING [40] Specific Context - STRING [40] Failure Context - STRING [40]
PRIMARY CAUSE	MGCP signaling interop error has occurred.
PRIMARY ACTION	Refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x" or notify customer support. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (80)

To troubleshoot and correct the cause of the alarm, refer to the "Out of Bounds, Memory/Socket Error - Signaling (80)" section.

DESCRIPTION	Out of Bounds, Memory/Socket Error
SEVERITY	CRITICAL
DATAWORDS	Process Name - STRING [40] Description - STRING [40] Extra Info - STRING [40]
PRIMARY CAUSE	Out of heap memory.
PRIMARY ACTION	Notify customer support. Increase random access memory (RAM). (Contact Cisco TAC.)
SECONDARY CAUSE	Out of IPC pool memory.
SECONDARY ACTION	Resize IPC pool size in the platform configuration file.
TERNARY CAUSE	Socket error has occurred. Inappropriate/already bound socket is in use.
TERNARY ACTION	Check UDP port supplied with media gateway adapter (MGA) command-line for validity and prior use.

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (81)

To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Heap Memory - Signaling (81) (H.323)" section.

DESCRIPTION	Insufficient Heap Memory
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32]
PRIMARY CAUSE	Issued when the H.323 Protocol (H323) signaling adapter is unable to allocate memory from the system.
PRIMARY ACTION	Call CISCO TAC for assistance. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (82)

To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Shared Memory Pools - Signaling (82) (H.323)" section.

DESCRIPTION	Insufficient Shared Memory Pools
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32]
PRIMARY CAUSE	Issued when H323 signaling adapter was unable to allocate storage.
PRIMARY ACTION	Call Cisco TAC for corrective action. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (83)

To troubleshoot and correct the cause of the alarm, refer to the "Error While Binding to Socket - Signaling (83)" section.

DESCRIPTION	Error While Binding to Socket
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Socket ID - FOUR_BYTES Local TSAP Address - STRING [32] Reason - STRING [128]
PRIMARY CAUSE	An error has occurred while binding to a socket.
PRIMARY ACTION	Contact Cisco TAC.

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (84)

To troubleshoot and correct the cause of the alarm, refer to the "Reached Maximum Socket Limit - Signaling (84) (H.323)" section.

DESCRIPTION	Reached Maximum Socket Limit
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Active Sockets - FOUR_BYTES
PRIMARY CAUSE	The configuration setting of an H.323 signaling adapter (H3A) parameter in platform.cfg file is wrong.
PRIMARY ACTION	Reconfigure platform.cfg file and restart the H3A process.

SIGNALING (85)

To troubleshoot and correct the cause of the alarm, refer to the "Initialization Failure - Signaling (85)" section.

DESCRIPTION	Initialization Failure
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Reason - STRING [128]
PRIMARY CAUSE	Process initialization failure has occurred.
PRIMARY ACTION	Check Dataword 2 (Reason) for the failure cause and take action accordingly.

SIGNALING (86)

To troubleshoot and correct the cause of the alarm, refer to the "Remote H323 Gateway is not Reachable - Signaling (86) (H.323)" section.

DESCRIPTION	Remote H323 Gateway is not Reachable
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Remote GW TSAP Addr - STRING [32]
PRIMARY CAUSE	Loss of communication with a remote gateway has occurred.
PRIMARY ACTION	Perform standard connectivity tests - both physical checks and IP tests. Also, ensure that the gateway is not out of service.

SIGNALING (87)

To troubleshoot and correct the cause of the alarm, refer to the "H323 Message Parsing Error - Signaling (87) (H.323)" section.

DESCRIPTION	H323 Message Parsing Error
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Remote GW TSAP Addr - STRING [32]
PRIMARY CAUSE	Unable to successfully parse an incoming H323 message.
PRIMARY ACTION	This is a result of either a software bug or bad message being received - a message with a valid message type but an invalid field within the message. Snoop the message from the endpoint and verify it's content or call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (88)

To troubleshoot and correct the cause of the alarm, refer to the "H323 Message Encoding Error - Signaling (88) (H.323)" section.

DESCRIPTION	H323 Message Encoding Error
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Reason - STRING [128]
PRIMARY CAUSE	Unable to encode an H323 message for sending.
PRIMARY ACTION	This is indicative a software bug. Contact Cisco TAC.

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (89)

To troubleshoot and correct the cause of the alarm, refer to the "Gatekeeper not Available/Reachable - Signaling (89)" section.

DESCRIPTION	Gatekeeper not Available/Reachable
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Gatekeeper ID - STRING [32] GK TSAP Addr - STRING [32]
PRIMARY CAUSE	Gatekeeper is not available or is unreachable.
PRIMARY ACTION	Check network connectivity. Check to ensure gatekeeper (GK) is reachable by trying to ping GK IP address. If reachable, then check to ensure that GK is configured up.

SIGNALING (90)

To troubleshoot and correct the cause of the alarm, refer to the "Alternate Gatekeeper is not Responding - Signaling (90)" section.

DESCRIPTION	Alternate Gatekeeper is not Responding
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Gatekeeper ID - STRING [32] GK TSAP Addr - STRING [32]
PRIMARY CAUSE	Alternate gatekeeper is not responding.
PRIMARY ACTION	Check network connectivity. Check to ensure the alternate GK is reachable by trying to ping the alternate GK IP address. If reachable, then check to ensure that alternate GK is configured up.

SIGNALING (91)

To troubleshoot and correct the cause of the alarm, refer to the "Endpoint Security Violation - Signaling (91) (H.323)" section.

DESCRIPTION	Endpoint Security Violation
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Gatekeeper ID - STRING [32] GK TSAP Addr - STRING [32]
PRIMARY CAUSE	An H323 security violation has occurred.
PRIMARY ACTION	The password on the Cisco BTS 10200 Softswitch and/or gatekeeper is wrong - the H323 gateway (H323GW) table may not be provisioned properly OR there is a time synchronization problem between the Cisco BTS 10200 Softswitch and/or gatekeeper and the Network Time Protocol (NTP) server. Ensure both the Cisco BTS 10200 Softswitch and gatekeeper are pointing to the same NTP server.

SIGNALING (92)

To troubleshoot and correct the cause of the alarm, refer to the "Invalid Call Identifier - Signaling (92)" section.

DESCRIPTION	Invalid Call Identifier
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Remote GW TSAP Addr - STRING [32] Call ID - EIGHT_BYTES
PRIMARY CAUSE	The call ID was invalid or changed mid-call.
PRIMARY ACTION	This is a software problem on the Cisco BTS 10200 Softswitch or endpoint. Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (93)

To troubleshoot and correct the cause of the alarm, refer to the "Invalid Call Reference Value - Signaling (93)" section.

DESCRIPTION	Invalid Call Reference Value
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Remote GW TSAP Addr - STRING [32] Call ID - EIGHT_BYTES Call Ref Value - EIGHT_BYTES
PRIMARY CAUSE	The call ID was invalid or changed mid-call.
PRIMARY ACTION	This is a software problem on the Cisco BTS 10200 Softswitch or endpoint. Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (94)

To troubleshoot and correct the cause of the alarm, refer to the "Invalid Conference Identifier - Signaling (94)" section.

DESCRIPTION	Invalid Conference Identifier
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Reason - STRING [32] Remote GW Port - TWO_BYTES Call ID - EIGHT_BYTES Conference ID - EIGHT_BYTES
PRIMARY CAUSE	The call ID was invalid or changed mid-call.
PRIMARY ACTION	This is a software problem on the Cisco BTS 10200 Softswitch or endpoint. Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (95)

To troubleshoot and correct the cause of the alarm, refer to the "Invalid Message from the Network - Signaling (95)" section.

DESCRIPTION	Invalid Message from the Network
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Remote GW TSAP Addr - STRING [32] Call ID - EIGHT_BYTES Conf ID - EIGHT_BYTES Call Ref Value - EIGHT_BYTES
PRIMARY CAUSE	Unsupported or invalid message type received from network.
PRIMARY ACTION	Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (96)

To troubleshoot and correct the cause of the alarm, refer to the "Internal Call Processing Error - Signaling (96)" section.

DESCRIPTION	Internal Call Processing Error
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Call ID - EIGHT_BYTES Reason - STRING [128]
PRIMARY CAUSE	A software error has occurred.
PRIMARY ACTION	Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (97)

To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Information to Complete Call - Signaling (97)" section.

DESCRIPTION	Insufficient Information to Complete Call
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Call ID - EIGHT_BYTES Conf ID - EIGHT_BYTES Call Ref Value - EIGHT_BYTES
PRIMARY CAUSE	Not enough initial call setup information was received to establish the call.
PRIMARY ACTION	Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (98)

To troubleshoot and correct the cause of the alarm, refer to the "H323 Protocol Inconsistencies - Signaling (98) (H.323)" section.

DESCRIPTION	H323 Protocol Inconsistencies
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Call ID - EIGHT_BYTES Reason - STRING [128]
PRIMARY CAUSE	The H323 endpoint and Cisco BTS 10200 Softswitch are running different protocol versions.
PRIMARY ACTION	This is only an issue where the endpoint is running a higher version of the H323 protocol than the Cisco BTS 10200 Softswitch. Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (99)

To troubleshoot and correct the cause of the alarm, refer to the "Abnormal Call Clearing - Signaling (99)" section.

DESCRIPTION	Abnormal Call Clearing
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Call ID - EIGHT_BYTES Reason - STRING [128]
PRIMARY CAUSE	Unsupported or invalid message type received from network.
PRIMARY ACTION	Call Cisco TAC. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (100)

To troubleshoot and correct the cause of the alarm, refer to the "Codec Negotiation Failed - Signaling (100)" section.

DESCRIPTION	Codec Negotiation Failed
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Call ID - EIGHT_BYTES Reason - STRING [128]
PRIMARY CAUSE	Codec negotiation failed.
PRIMARY ACTION	Find a compatible set of codec settings for both sides, re-provision the endpoints of the call and try the call again.

SIGNALING (101)

To troubleshoot and correct the cause of the alarm, refer to the "Per Call Security Violation - Signaling (101)" section.

DESCRIPTION	Per Call Security Violation
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Call ID - EIGHT_BYTES Gatekeeper ID - STRING [32]
PRIMARY CAUSE	This is a future trap definition.
PRIMARY ACTION	None

SIGNALING (102)

To troubleshoot and correct the cause of the alarm, refer to the "H323 Network Congested - Signaling (102) (H.323)" section.

DESCRIPTION	H323 Network Congested
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Gateway ID - STRING [32] Gatekeeper ID - STRING [32]
PRIMARY CAUSE	The H323 application processes has depleted it's resources. no more calls can be completed.
PRIMARY ACTION	The high water mark has been reached - all new call requests are rejected until the low water mark is reached. Reprovision the water marks or check the network for overload. Also verify that alternate routes have been provisioned on the Cisco BTS 10200 Softswitch.

SIGNALING (103)

To troubleshoot and correct the cause of the alarm, refer to the "Aggregation Connection Down - Signaling (103)" section.

DESCRIPTION	Aggregation Connection Down (AGGR Connection Down)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	AGGR-ID - STRING [16]
PRIMARY CAUSE	Transmission Control Protocol (TCP) connection is down.
PRIMARY ACTION	Check the associated cabling and perform PINGs to test the connectivity.

SIGNALING (104)

For additional information, refer to the "Aggregation Unable To Establish Connection - Signaling (104)" section.

DESCRIPTION	Aggregation Unable To Establish Connection (AGGR Unable To Establish Connection)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	AGGR-ID - STRING [16]
PRIMARY CAUSE	TCP connection establish failure.
PRIMARY ACTION	Check the IP connectivity of CA and cable modem termination system (CMTS).

SIGNALING (105)

For additional information, refer to the "Aggregation Gate Set Failed - Signaling (105)" section.

DESCRIPTION	Aggregation Gate Set Failed (AGGR Gate Set Failed)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	AGGR-ID - STRING [16] Error-Code - TWO_BYTES Sub-Error-Code - TWO_BYTES
PRIMARY CAUSE	Gate set acknowledgement never came from the CMTS.
PRIMARY ACTION	None

SIGNALING (106)

To troubleshoot and correct the cause of the alarm, refer to the "Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)" section.

DESCRIPTION	Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down (ESA BTS DF Connection Down)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
PRIMARY CAUSE	Delivery function (DF) server not responding.
PRIMARY ACTION	Check the encryption key or IP connectivity to DF.

SIGNALING (107)

To troubleshoot and correct the cause of the alarm, refer to the "Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)" section.

DESCRIPTION	Logical Internet Protocol Addresses not Mapped Correctly (Logical IP Addresses not Mapped Correctly)
SEVERITY	CRITICAL
THRESHOLD	30
THROTTLE	0
DATAWORDS	Contact Domain Name - STRING [128] Number of IP Addresses Resolved - FOUR_BYTES Number of Virtual IP Addresses - FOUR_BYTES
PRIMARY CAUSE	Contact name in the configuration file not configured in domain name system (DNS).
PRIMARY ACTION	Verify name in DNS matches name in platform.cfg and opticall.cfg files.
SECONDARY CAUSE	Contact could not be resolved to an IP address on the host.
SECONDARY ACTION	Verify DNS resolves to IP addresses reserved for process on the Cisco BTS 10200 Softswitch.
TERNARY CAUSE	IP address manager not running.
TERNARY ACTION	Verify Internet Protocol Manager (IPM) process is running and check for alarms from IPM.
SUBSEQUENT CAUSE	Mis-configuration during installation or manual changes made after installation.
SUBSEQUENT ACTION	Contact Cisco TAC for support. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (108)

To troubleshoot and correct the cause of the alarm, refer to the "Current SIA Configuration only Valid for Simplex Systems - Signaling (108)" section.

DESCRIPTION	Current SIA Configuration only Valid for Simplex Systems
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	SIA Host Domain Name - STRING [128] SIA Contact Domain N - STRING [128]
PRIMARY CAUSE	SIA host and contact parameters are the same in platform.cfg file.
PRIMARY ACTION	If this is a duplex installation, regardless of current operational state, contact Cisco TAC.
SECONDARDY CAUSE	SIA is configured for use on a simplex system.
SECONDARY ACTION	If this is a simplex installation only, this alarm can be turned off.

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (109)

To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Failure - Signaling (109)" section.

DESCRIPTION	Stream Control Transmission Protocol Association Failure (SCTP Association Failure)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	SCTP Association ID - STRING [17]
PRIMARY CAUSE	Ethernet cables on signaling gateway process (SGP) are unplugged or severed.
PRIMARY ACTION	Plug Ethernet cables in or fix severed connection.
SECONDARY CAUSE	SGP is not operational.
SECONDARY ACTION	Check SGP alarms to determine why it is not operating properly.

SIGNALING (110)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Group Is Out-of-Service - Signaling (110)" section.

DESCRIPTION	Signaling Gateway Group is Out-of-Service
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	SG Group ID - STRING [17]
PRIMARY CAUSE	All Stream Control Transmission Protocol (SCTP) associations between CA and SGs are out-of-service.
PRIMARY ACTION	Make sure all Ethernet connections on the CA and SGs are plugged in. Also make sure all associated IP routers are operational.
SECONDARY CAUSE	The MTP3 user adapter (M3UA) layer is down between the CA and SGs.
SECONDARY ACTION	Use Cisco Snooper application to determine why the M3UA layer is down.

SIGNALING (111)

To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) - Signaling (111)" section.

DESCRIPTION	Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) (SCTP Association Degraded (One of Two IP connections Down))
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	SCTP Association ID - STRING [17] Destination IP Address - STRING [11]
PRIMARY CAUSE	Single Ethernet connection on CA or SGP is unplugged or severed.
PRIMARY ACTION	Plug in all Ethernet connections or repair if severed.
SECONDARY CAUSE	SCTP communication problem - protocol timeout.
SECONDARY ACTION	Use Cisco Snooper application to determine why SCTP association is degraded.

SIGNALING (112)

To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Configuration Error - Signaling (112)" section.

DESCRIPTION	Stream Control Transmission Protocol Association Configuration Error (SCTP Association Configuration Error)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	SCTP Association ID - STRING [17]
PRIMARY CAUSE	Destination IP address is invalid.
PRIMARY ACTION	Input new destination IP address - see log for additional details.
SECONDARY CAUSE	Local IP address is invalid.
SECONDARY ACTION	Input new local IP address information.
TERNARY CAUSE	IP Routing Table is not configured properly.
TERNARY ACTION	Have the system administrator configure IP routing table.

SIGNALING (113)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Failure - Signaling (113)" section.

DESCRIPTION	Signaling Gateway Failure
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Signaling Gateway ID - STRING [17]
PRIMARY CAUSE	All associated signaling gateway processes are out-of-service.
PRIMARY ACTION	Determine why each associated SGP is out-of-service (see SGP alarm definition).

SIGNALING (114)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Process Is Out-of-Service - Signaling (114)" section.

DESCRIPTION	Signaling Gateway Process is Out-of-Service
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Signaling Gateway - STRING [17]
PRIMARY CAUSE	All SCTP associations between the SGP and the CA are out-of-service.
PRIMARY ACTION	See SCTP association alarm definition to determine how to rectify the problem.
SECONDARY CAUSE	The M3UA layer is down between the CA and SGP.
SECONDARY ACTION	Use Cisco snooper utility to determine why M3UA layer is down. Also see log for additional information.

SIGNALING (115)

To monitor and correct the cause of the event, refer to the "Invalid Routing Context Received - Signaling (115)" section.

DESCRIPTION	Invalid Routing Context Received
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Invalid Routing Cont - FOUR_BYTES SG from Which the In - STRING [17]
PRIMARY CAUSE	Routing context was configured improperly on CA or signaling gateway (SG).
PRIMARY ACTION	Reconfigure routing context on CA or SG so that they match in both places.

SIGNALING (116)

To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code User Part Unavailable - Signaling (116)" section.

DESCRIPTION	Destination Point Code User Part Unavailable (DPC User Part Unavailable)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	DPC ID - STRING [17]
PRIMARY CAUSE	SGP sent a destination user part unavailable (DUPU) M3UA message to CA indicating that a User Part is unavailable on at a DPC.
PRIMARY ACTION	Contact SS7 Network Administrator to report the User Part Unavailable problem of the DPC so communication can be restored.

SIGNALING (117)

To troubleshoot and correct the cause of the alarm, refer to the "Circuit Validation Test Message Received for an Unequipped Circuit Identification Code - Signaling (117)" section.

DESCRIPTION	Circuit Validation Test Message Received for an Unequipped Circuit Identification Code (CVT Message Received for an Unequipped CIC)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC - TWO_BYTES TGN-ID - EIGHT_BYTES DPC - STRING [13]
PRIMARY CAUSE	CIC is not provisioned
PRIMARY ACTION	Provision CIC.

SIGNALING (118)

To troubleshoot and correct the cause of the alarm, refer to the "Circuit Verification Response Received with Failed Indication - Signaling (118)" section.

DESCRIPTION	Circuit Verification Response Received with Failed Indication (CVR Received with Failed Indication)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC - TWO_BYTES TGN-ID - EIGHT_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	CIC mismatch.
PRIMARY ACTION	Perform internal test such as checking that the CIC is assigned to a circuit between the sending and the receiving switch.

SIGNALING (119)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Adapter Process Faulty - Signaling (119)" section.

DESCRIPTION	Signaling System 7 Adapter Process Faulty (S7A Process Faulty)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Reason - STRING [36]
PRIMARY CAUSE	OMNI or S7A exception.
PRIMARY ACTION	Check OMNI process. The S7A will restart itself if S7A maximum restart is not exceeded.

SIGNALING (120)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Module/Signaling System 7 Adapter Faulty - Signaling (120)" section.

DESCRIPTION	Signaling System 7 Module/Signaling System 7 Adapter Faulty (S7M/S7A Faulty)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Reason - STRING [36]
PRIMARY CAUSE	OMNI failure.
PRIMARY ACTION	Check OMNI status; failover will occur in a duplex configuration.

SIGNALING (121)

To troubleshoot and correct the cause of the alarm, refer to the "Message Transfer Part 3 User Adapter Cannot Go Standby - Signaling (121)" section.

DESCRIPTION	Message Transfer Part 3 User Adapter Cannot Go Standby (M3UA/SUA Cannot Go Standby)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Platform ID - STRING [17]
PRIMARY CAUSE	No INACTIVE acknowledge (ACK) messages received from any SG or SCTP Associations are probably down.
PRIMARY ACTION	Investigate other alarms to see if SGs are down or SCTP associations are down. Take corrective action according to those alarms.

SIGNALING (122)

To troubleshoot and correct the cause of the alarm, refer to the "Message Transfer Part 3 User Adapter Cannot Go Active - Signaling (122)" section.

DESCRIPTION	Message Transfer Part 3 User Adapter Cannot Go Active (M3UA/SUA Cannot Go Active)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Platform ID - STRING [17]
PRIMARY CAUSE	No ACTIVE acknowledgement messages received from any SG or SCTP associations are probably down.
PRIMARY ACTION	Investigate other alarms to see if SGs are down or SCTP associations are down. Take corrective action according to those alarms.

---

Note SIGNALING (123) is not used.

---

SIGNALING (124)

To troubleshoot and correct the cause of the alarm, refer to the "Remote Subsystem is Out Of Service - Signaling (124)" section.

DESCRIPTION	Remote Subsystem is Out Of Service
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Destination Point Co - STRING [20] Remote Subsystem Num - TWO_BYTES
PRIMARY CAUSE	Link loss or the remote subsystem out of service.
PRIMARY ACTION	Check links. Check remote location, if possible.

SIGNALING (125)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling Connection Control Part Routing Error - Signaling (125)" section.

DESCRIPTION	Signaling Connection Control Part Routing Error (SCCP Routing Error)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
PRIMARY CAUSE	Signaling connection control part (SCCP) route invalid or not available.
PRIMARY ACTION	Provision the right SCCP route.

SIGNALING (126)

To troubleshoot and correct the cause of the alarm, refer to the "Signaling Connection Control Part Binding Failure - Signaling (126)" section.

DESCRIPTION	Signaling Connection Control Part Binding Failure (SCCP Binding Failure)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Local Point Code - STRING [20] Local Subsystem Numb - ONE_BYTE
PRIMARY CAUSE	Trillium stack binding failure.
PRIMARY ACTION	Re-initialize the TCAP signaling adapter (TSA) process or remove the subsystem from the Element Management System (EMS) table and add it again.

SIGNALING (127)

To troubleshoot and correct the cause of the alarm, refer to the "Transaction Capabilities Application Part Binding Failure - Signaling (127)" section.

DESCRIPTION	Transaction Capabilities Application Part Binding Failure (TCAP Binding Failure)
SEVERITY	MAJOR
THRESHOLD	100
THROTTLE	0
PRIMARY CAUSE	Trillium stack binding failure.
PRIMARY ACTION	Re-initialize the TSA process or remove the subsystem from the EMS table and add it again.

---

Note SIGNALING (128) through SIGNALING (131) are not used.

---

SIGNALING (132)

To monitor and correct the cause of the event, refer to the "Transaction Capabilities Application Part Reaches the Provisioned Resource Limit - Signaling (132)" section.

DESCRIPTION	Transaction Capabilities Application Part Reaches the Provisioned Resource Limit (TCAP Reaches the Provisioned Resource Limit)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	Dialogue/Invoke ID - FOUR_BYTES
PRIMARY CAUSE	Transaction Capabilities Application Part (TCAP) runs out of all the pre-configured dialogue IDs or invoke IDs.

SIGNALING (133)

For additional information, refer to the "Unable to Decode Generic Transport Descriptor Message - Signaling (133)" section.

DESCRIPTION	Unable to Decode Generic Transport Descriptor Message (Unable to Decode GTD Message)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	Endpoint Name - STRING [40] GTD Content Type - STRING [40]
PRIMARY CAUSE	Issued when the generic transport descriptor (GTD) parser failed to decode a GTD message received from the specified endpoint.
PRIMARY ACTION	Verify that the version of the GTD protocol used by the device at the remote endpoint is consistent with the version expected by the call agent.
SECONDARY ACTION	Examine the associated signaling link to see if there is any interruption of the supplementary services on the link.

SIGNALING (134)

For additional information, refer to the "Signaling System 7 Message Encoding Failure - Signaling (134)" section.

DESCRIPTION	Signaling System 7 Message Encoding Failure (SS7 Message Encoding Failure)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Error in ISDN user part (ISUP) stack or signaling adapter interface (SAI) message.
PRIMARY ACTION	Capture SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (135)

For additional information, refer to the "Signaling System 7 Message Decoding Failure - Signaling (135)" section.

DESCRIPTION	Signaling System 7 Message Decoding Failure (SS7 Message Decoding Failure)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Error in ISUP stack or SAI message.
PRIMARY ACTION	Capture SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (136)

For additional information, refer to the "Signaling System 7 Message Invalid Received - Signaling (136)" section.

DESCRIPTION	Signaling System 7 Message Invalid Received (SS7 Message Invalid Received)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Invalid message was received from line in ISUP stack.
PRIMARY ACTION	Capture SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.)
SECONDARY CAUSE	Invalid message was received from line in ISUP stack.
SECONDARY ACTION	Verify the signal switching point (SSP) sending the message to the CA is correctly configured.

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (137)

For additional information, refer to the "Signaling System 7 Confusion Message Received - Signaling (137)" section.

DESCRIPTION	Signaling System 7 Confusion Message Received (SS7 Confusion Message Received)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC Number - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	An ISUP message or parameter received was not recognized or understood.
PRIMARY ACTION	Check the log for more information (including confusion (CFN) diagnostic output). Capture SS7 trace of affected circuits. If diagnostic data indicates messages/parameters that must be supported are being dropped, refer the captured data to support along with a description of the call scenario.

SIGNALING (138)

To troubleshoot and correct the cause of the alarm, refer to the "Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit - Signaling (138)" section.

DESCRIPTION	Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit (Number of Open SIP Connections is Reaching Engineered Limit)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Number of SIP Connections Open - FOUR_BYTES SIP Connection Alarm Threshold - FOUR_BYTES Open SIP Connection Limit - FOUR_BYTES
PRIMARY CAUSE	System configuration and traffic load have caused the number of open connections to approach the engineered limit. This limit will need to be increased to allow for more connections.
PRIMARY ACTION	Please contact Cisco support. (Contact Cisco TAC.)

Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

SIGNALING (139)

For additional information, refer to the "Signaling System 7 Trunk was Found to be in Erroneous State - Signaling (139) (SS7)" section.

DESCRIPTION	Signaling System 7 Trunk was Found to be in Erroneous State (SS7 Trunk was Found to be in Erroneous State)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20] Near-End State - STRING [64] Far-End State - STRING [64] Resolution Action - STRING [64]
PRIMARY CAUSE	Discrepancy between local and remote trunk states.
PRIMARY ACTION	Automatic corrective action enforced when using American National Standards Institute (ANSI) ISUP.

SIGNALING (140)

For additional information, refer to the "Unanswered Information Message - Signaling (140)" section.

DESCRIPTION	Unanswered Information Message (Unanswered INF Message)
SEVERITY	INFO
THRESHOLD	100
THROTTLE	0
DATAWORDS	CIC - TWO_BYTES TGN-ID - FOUR_BYTES DPC - STRING [20] OPC - STRING [20]
PRIMARY CAUSE	Far-end switch is not responding to information (INF) message with an information request (INR) message.
PRIMARY ACTION	Verify that far-end switch can correctly respond to an INF message.

SIGNALING (141)

To monitor and correct the cause of the event, refer to the "Address not Resolved by Domain Name System Server - Signaling (141)" section.

DESCRIPTION	Address not Resolved by Domain Name System Server (Address not Resolved by DNS Server)
SEVERITY	WARNING
THRESHOLD	100
THROTTLE	0
DATAWORDS	TSAP_Address/Hostname - STRING [256]
PRIMARY CAUSE	The transport service access point (TSAP) address/hostname is not defined in DNS.
PRIMARY ACTION	Add entry for TSAP address to DNS server, or fix Cisco BTS 10200 Softswitch provisioning.

SIGNALING (142)

To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Trunk Operationally Out-of-Service - Signaling (142)" section.

DESCRIPTION	Session Initiation Protocol Trunk Operationally Out-of-Service (SIP Trunk Operationally out of Service)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Trunk Group Description - STRING [16] Trunk TSAP Address - STRING [65]
PRIMARY CAUSE	Issued when Cisco BTS 10200 Softswitch is unable to communicate with a remote SIP party (Call-Agent or Proxy) over a SIP or SIP-T trunk.
PRIMARY ACTION	Verify DNS resolution exists, if TSAP address of the remote entity is a domain name. Verify the remote entity is reachable by Internet Control Message Protocol (ICMP) ping, using the Trunk TSAP address from the Event Report. If the same alarm is reported on all the softswitch trunk groups, then verify that the network connection is operational.
SECONDARY CAUSE	Remote SIP party is not operational.
SECONDARY ACTION	If the ping is not successful, then diagnose the issue that prevents the TSAP address from being reached. Verify the SIP application is running on the remote host and listening on the port specified in the TSAP address.

SIGNALING (143)

To troubleshoot and correct the cause of the alarm, refer to the "Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down - Signaling (143)" section.

DESCRIPTION	Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down (IP Interface Link to the SS7 Signaling Gateway is Down)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Interface Name - STRING [65] Interface IP Address - STRING [65]
PRIMARY CAUSE	Hardware problem has occurred.
PRIMARY ACTION	Check the link interfaces.

SIGNALING (144)

To troubleshoot and correct the cause of the alarm, refer to the "All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway are Down - Signaling (144)" section.

DESCRIPTION	All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway are Down (All IP Interface Links to SS7 Signaling Gateway are Down)
SEVERITY	CRITICAL
THRESHOLD	100
THROTTLE	0
DATAWORDS	Interface Name - STRING [65] Interface IP Address - STRING [65]
PRIMARY CAUSE	Hardware problem has occurred.
PRIMARY ACTION	Check the link interfaces.

SIGNALING (145)

To troubleshoot and correct the cause of the alarm, refer to the "One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down - Signaling (145)" section.

DESCRIPTION	One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down (One IP Interface to SS7 Signaling Gateway is Down)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	Interface Name - STRING [65] Interface IP Address - STRING [65]
PRIMARY CAUSE	Hardware problem has occurred.
PRIMARY ACTION	Check the link interfaces.

---

Note SIGNALING (146) through SIGNALING (149) are not used.

---

SIGNALING (150)

To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Congested - Signaling (150)" section.

DESCRIPTION	Stream Control Transmission Protocol Association Congested (SCTP Association Congested)
SEVERITY	MINOR
THRESHOLD	100
THROTTLE	0
DATAWORDS	SCTP Association ID - STRING [17] Congestion Level - ONE_BYTE
PRIMARY CAUSE	Network is congested.
PRIMARY ACTION	Clean off the network congestion caused by routing or switching issues.
SECONDARY CAUSE	Central processing unit (CPU) is throttled.
SECONDARY ACTION	May need upgrade to a more powerful platform or offload some traffic.

Monitoring Signaling Events

This section provides the information needed to monitor and correct Signaling events. Table 10-2 lists all Signaling events in numerical order and provides cross reference to each subsection in this section.

Table 10-2 Cisco BTS 10200 Softswitch Signaling Events 

Event Type	Event Name	Event Severity
SIGNALING(1)	Test Report - Signaling (1)	INFO
SIGNALING(2)	Message Encoding Error - Signaling (2)	WARNING
SIGNALING(3)	Message Decoding Error - Signaling (3)	MAJOR
SIGNALING(4)	Invalid Message Received - Signaling (4)	WARNING
SIGNALING(5)	Database Module Function Call Failure - Signaling (6)	N/A
SIGNALING(6)	Database Module Function Call Failure - Signaling (6)	WARNING
SIGNALING(7)	Socket Failure - Signaling (7)	MAJOR
SIGNALING(8)	Session Initiation Protocol Message Receive Failure - Signaling (8)	MAJOR
SIGNALING(9)	Timeout on Internet Protocol Address - Signaling (9)	MAJOR
SIGNALING(10)	Failed to Send Complete Session Initiation Protocol Message - Signaling (10)	MINOR
SIGNALING(11)	Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)	MAJOR
SIGNALING(12)	Feature Server is not Up or is not Responding to Call Agent - Signaling (12)	CRITICAL
SIGNALING(13)	Signaling System 7 Signaling Link Down - Signaling (13)	MAJOR
SIGNALING(14)	Link is Remotely Inhibited - Signaling (14)	MINOR
SIGNALING(15)	Link is Locally Inhibited - Signaling (15)	MINOR
SIGNALING(16)	Link is Congested - Signaling (16)	MINOR
SIGNALING(17)	Link: Local Processor Outage - Signaling (17)	MINOR
SIGNALING(18)	Link: Remote Processor Outage - Signaling (18)	MINOR
SIGNALING(19)	Link Set Inaccessible - Signaling (19)	MAJOR
SIGNALING(20)	Link Set Congestion - Signaling (20)	MAJOR
SIGNALING(21)	Route Set Failure - Signaling (21)	MAJOR
SIGNALING(22)	Route Set Congested - Signaling (22)	MINOR
SIGNALING(23)	Destination Point Code Unavailable - Signaling (23)	MAJOR
SIGNALING(24)	Destination Point Code Congested - Signaling (24)	MINOR
SIGNALING(25)	Unanswered Blocking Message - Signaling (25)	WARNING
SIGNALING(26)	Unanswered Unblocking Message - Signaling (26)	WARNING
SIGNALING(27)	Unanswered Circuit Group Blocking Message - Signaling (27)	WARNING
SIGNALING(28)	Unanswered Circuit Group Unblocking Message - Signaling (28)	WARNING
SIGNALING(29)	Unanswered Circuit Query Message - Signaling (29)	WARNING
SIGNALING(30)	Unanswered Circuit Validation Test Message - Signaling (30)	WARNING
SIGNALING(31)	Unanswered Reset Circuit Message - Signaling (31)	WARNING
SIGNALING(32)	Unanswered Group Reset Message - Signaling (32)	WARNING
SIGNALING(33)	Unanswered Release Message - Signaling (33)	WARNING
SIGNALING(34)	Unanswered Continuity Check Request Message - Signaling (34)	WARNING
SIGNALING(35)	Trunk Locally Blocked - Signaling (36)	N/A
SIGNALING(36)	Trunk Locally Blocked - Signaling (36)	MINOR
SIGNALING(37)	Trunk Remotely Blocked - Signaling (40)	N/A
SIGNALING(38)	Trunk Remotely Blocked - Signaling (40)	N/A
SIGNALING(39)	Trunk Remotely Blocked - Signaling (40)	N/A
SIGNALING(40)	Trunk Remotely Blocked - Signaling (40)	MAJOR
SIGNALING(42)	Continuity Testing Message Received on the Specified Circuit Identification Code - Signaling (42)	INFO
SIGNALING(43)	Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code - Signaling (43)	INFO
SIGNALING(44)	Continuity Recheck is Performed on Specified Circuit Identification Code - Signaling (44)	INFO
SIGNALING(45)	Circuit is UNEQUIPPED on Remote Side - Signaling (45)	INFO
SIGNALING(46)	Specified Circuit Identification Code is Invalid for the Operation - Signaling (46)	INFO
SIGNALING(48)	A General Processing Error Encountered - Signaling (49)	INFO
SIGNALING(49)	A General Processing Error Encountered - Signaling (49)	INFO
SIGNALING(50)	Unexpected Message for the Call State is Received: Clear Call - Signaling (50)	INFO
SIGNALING(51)	Set Trunk State as Remotely Unequipped - Signaling (51)	INFO
SIGNALING(52)	Set Trunk State as NOT Remotely Blocked - Signaling (52)	INFO
SIGNALING(53)	Set Trunk State as Remotely Blocked - Signaling (53)	INFO
SIGNALING(54)	Circuit Validation Test Aborted - Signaling (54)	INFO
SIGNALING(55)	Circuit Validation Successful - Signaling (55)	INFO
SIGNALING(56)	Continuity Recheck Failed - Signaling (57)	INFO
SIGNALING(57)	Continuity Recheck Failed - Signaling (57)	INFO
SIGNALING(58)	Continuity Recheck Successful - Signaling (58)	INFO
SIGNALING(59)	Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)	MAJOR
SIGNALING(60)	Integrated Services Digital Network STATUS Message Containing Error Indication Received - Signaling (60)	WARNING
SIGNALING(61)	Trunk Operational State Changed by Service Message - Signaling (61)	INFO
SIGNALING(62)	Received Integrated Services Digital Network RESTART Message - Signaling (62)	INFO
SIGNALING(63)	Media Gateway/Termination Faulty - Signaling (63)	MAJOR
SIGNALING(64)	Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)	CRITICAL
SIGNALING(65)	Media Gateway Adapter Running out of Heap Memory - Signaling (65)	CRITICAL
SIGNALING(66)	Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)	MAJOR
SIGNALING(68)	Media Gateway or Termination are Found Administratively Out of Service - Signaling (68)	MAJOR
SIGNALING(69)	Call Agent and Feature Server Communication Message Timeout - Signaling (69)	CRITICAL
SIGNALING(70)	Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication - Signaling (70)	WARNING
SIGNALING(71)	Integrated Services Digital Network Unable to Establish D-channel - Signaling (71)	WARNING
SIGNALING(72)	Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time - Signaling (72)	WARNING
SIGNALING(73)	Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired - Signaling (73)	WARNING
SIGNALING(74)	Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired - Signaling (74)	WARNING
SIGNALING(75)	Signaling System 7 Stack not Ready - Signaling (75)	CRITICAL
SIGNALING(76)	Timeout on Remote Instance - Signaling (76)	INFO
SIGNALING(77)	Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling - Signaling (77)	INFO
SIGNALING(78)	Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)	MINOR
SIGNALING(79)	Media Gateway Unreachable - Signaling (79)	MAJOR
SIGNALING(80)	Out of Bounds, Memory/Socket Error - Signaling (80)	CRITICAL
SIGNALING(81)	Insufficient Heap Memory - Signaling (81) (H.323)	CRITICAL
SIGNALING(82)	Insufficient Shared Memory Pools - Signaling (82) (H.323)	CRITICAL
SIGNALING(83)	Error While Binding to Socket - Signaling (83)	CRITICAL
SIGNALING(84)	Reached Maximum Socket Limit - Signaling (84) (H.323)	CRITICAL
SIGNALING(85)	Initialization Failure - Signaling (85)	CRITICAL
SIGNALING(86)	Remote H323 Gateway is not Reachable - Signaling (86) (H.323)	MAJOR
SIGNALING(87)	H323 Message Parsing Error - Signaling (87) (H.323)	MAJOR
SIGNALING(88)	H323 Message Encoding Error - Signaling (88) (H.323)	MAJOR
SIGNALING(89)	Gatekeeper not Available/Reachable - Signaling (89)	MAJOR
SIGNALING(90)	Alternate Gatekeeper is not Responding - Signaling (90)	MAJOR
SIGNALING(91)	Endpoint Security Violation - Signaling (91) (H.323)	MAJOR
SIGNALING(92)	Invalid Call Identifier - Signaling (92)	MINOR
SIGNALING(93)	Invalid Call Reference Value - Signaling (93)	MINOR
SIGNALING(94)	Invalid Conference Identifier - Signaling (94)	MINOR
SIGNALING(95)	Invalid Message from the Network - Signaling (95)	MINOR
SIGNALING(96)	Internal Call Processing Error - Signaling (96)	MINOR
SIGNALING(97)	Insufficient Information to Complete Call - Signaling (97)	MINOR
SIGNALING(98)	H323 Protocol Inconsistencies - Signaling (98) (H.323)	MINOR
SIGNALING(99)	Abnormal Call Clearing - Signaling (99)	MINOR
SIGNALING(100)	Codec Negotiation Failed - Signaling (100)	MINOR
SIGNALING(101)	Per Call Security Violation - Signaling (101)	MINOR
SIGNALING(102)	H323 Network Congested - Signaling (102) (H.323)	MINOR
SIGNALING(103)	Aggregation Connection Down - Signaling (103)	MAJOR
SIGNALING(104)	Aggregation Unable To Establish Connection - Signaling (104)	INFO
SIGNALING(105)	Aggregation Gate Set Failed - Signaling (105)	INFO
SIGNALING(106)	Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)	MINOR
SIGNALING(107)	Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)	CRITICAL
SIGNALING(108)	Current SIA Configuration only Valid for Simplex Systems - Signaling (108)	MAJOR
SIGNALING(109)	Stream Control Transmission Protocol Association Failure - Signaling (109)	MAJOR
SIGNALING(110)	Signaling Gateway Group is Out-of-Service - Signaling (110)	CRITICAL
SIGNALING(111)	Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) - Signaling (111)	MAJOR
SIGNALING(112)	Stream Control Transmission Protocol Association Configuration Error - Signaling (112)	MINOR
SIGNALING(113)	Signaling Gateway Failure - Signaling (113)	MAJOR
SIGNALING(114)	Signaling Gateway Process is Out-of-Service - Signaling (114)	MAJOR
SIGNALING(115)	Invalid Routing Context Received - Signaling (115)	WARNING
SIGNALING(116)	Destination Point Code User Part Unavailable - Signaling (116)	MAJOR
SIGNALING(117)	Circuit Validation Test Message Received for an Unequipped Circuit Identification Code - Signaling (117)	MINOR
SIGNALING(118)	Circuit Verification Response Received with Failed Indication - Signaling (118)	MINOR
SIGNALING(119)	Signaling System 7 Adapter Process Faulty - Signaling (119)	CRITICAL
SIGNALING(120)	Signaling System 7 Module/Signaling System 7 Adapter Faulty - Signaling (120)	CRITICAL
SIGNALING(121)	Message Transfer Part 3 User Adapter Cannot Go Standby - Signaling (121)	MAJOR
SIGNALING(122)	Message Transfer Part 3 User Adapter Cannot Go Active - Signaling (122)	MAJOR
SIGNALING(123)	Remote Subsystem is out of Service - Signaling (124)	MINOR
SIGNALING(124)	Remote Subsystem is out of Service - Signaling (124)	MINOR
SIGNALING(125)	Signaling Connection Control Part Routing Error - Signaling (125)	MAJOR
SIGNALING(126)	Signaling Connection Control Binding Failure - Signaling (126)	MAJOR
SIGNALING(127)	Transaction Capabilities Application Part Binding Failure - Signaling (127)	MAJOR
SIGNALING(129)	Transaction Capabilities Application Part Reaches the Provisioned Resource Limit - Signaling (132)	N/A
SIGNALING(130)	Transaction Capabilities Application Part Reaches the Provisioned Resource Limit - Signaling (132)	N/A
SIGNALING(131)	Transaction Capabilities Application Part Reaches the Provisioned Resource Limit - Signaling (132)	WARNING
SIGNALING(132)	Transaction Capabilities Application Part Reaches the Provisioned Resource Limit - Signaling (132)	WARNING
SIGNALING(133)	Unable to Decode Generic Transport Descriptor Message - Signaling (133)	INFO
SIGNALING(134)	Signaling System 7 Message Encoding Failure - Signaling (134)	INFO
SIGNALING(135)	Signaling System 7 Message Decoding Failure - Signaling (135)	INFO
SIGNALING(136)	Signaling System 7 Message Invalid Received - Signaling (136)	INFO
SIGNALING(137)	Signaling System 7 Confusion Message Received - Signaling (137)	INFO
SIGNALING(138)	Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit - Signaling (138)	WARNING
SIGNALING(139)	Signaling System 7 Trunk was Found to be in Erroneous State - Signaling (139) (SS7)	INFO
SIGNALING(140)	Unanswered Information Message - Signaling (140)	INFO
SIGNALING(141)	Address not Resolved by Domain Name System Server - Signaling (141)	WARNING
SIGNALING(142)	Session Initiation Protocol Trunk Operationally Out-of-Service - Signaling (142)	CRITICAL
SIGNALING(143)	Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down - Signaling (143)	MINOR
SIGNALING(144)	All Internet Interface Links to Signaling System 7 Signaling Gateway are Down - Signaling (144)	CRITICAL
SIGNALING(145)	One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down - Signaling (145)	MINOR
SIGNALING(146)	Stream Control Transmission Protocol Association Congested - Signaling (150)	WARNING
SIGNALING(147)	Stream Control Transmission Protocol Association Congested - Signaling (150)	WARNING
SIGNALING(148)	Stream Control Transmission Protocol Association Congested - Signaling (150)	WARNING
SIGNALING(149)	Stream Control Transmission Protocol Association Congested - Signaling (150)	MAJOR
SIGNALING(150)	Stream Control Transmission Protocol Association Congested - Signaling (150)	MINOR
SIGNALING(151)	Troubleshooting Signaling Alarms	MINOR

Test Report - Signaling (1)

The Test Report event is for testing the signaling event category. The event is informational and no further action is required.

Message Encoding Error - Signaling (2)

The Message Encoding Error event serves as a warning that a message encoding error has occurred. The event is issued when there is a message encoding error on sending an MGCP message. If the event is issued while doing interoperability testing with a gateway using MGCP, then capture the MGCP message flow and forward it to Cisco TAC technical support for analysis. When an unexpected MGCP message occurs, contact Cisco TAC technical support to identify the root cause. Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

Message Decoding Error - Signaling (3)

The Message Decoding Error event serves as a warning that a message decoding error has occurred. The event is issued when there is a message decoding error on receiving an MGCP message. If this event is issued while doing interoperability testing with a gateway using MGCP, then capture the MGCP message flow and forward it to Cisco TAC technical support for analysis. When an unexpected MGCP message occurs, call Cisco TAC technical support to identify the root cause. Refer to the "Obtaining Technical Assistance" section on page xxxviii for detailed instructions on contacting Cisco TAC and opening a service request.

Invalid Message Received - Signaling (4)

The Invalid Message Received event serves as a warning that an invalid message has been received. The primary cause of the event is that a signaling adapter has received an invalid message from the specified endpoint. To correct the primary cause of the event, monitor the associated signaling link to see if there is an interruption of service on the link. If there is a communication problem, restart the link. Verify that the version of the protocol used by the device at the endpoint is consistent with the version expected by the call agent. If there is a mismatch, then either the endpoint or call agent must be re-provisioned.

Database Module Function Call Failure - Signaling (6)

The Database Module Function Call Failure event serves as a warning that a database module function call has failed. The primary cause of the event is that a signaling adapter has detected an error while accessing a database interface. To correct the primary cause of the event, restart the associated process if the database that the adapter attempted to access is not available. If incompatible versions of the signaling adapter process and the database processes are present on the system, correct the error and restart the processes.

Socket Failure - Signaling (7)

The Socket Failure alarm (major) indicates that there is a failure in creating the UDP port used by the MGCP stacks. To troubleshoot and correct the cause of the Socket Failure alarm, refer to the "Socket Failure - Signaling (7)" section.

Session Initiation Protocol Message Receive Failure - Signaling (8)

The Session Initiation Protocol Message Receive Failure alarm (major) indicates that a SIP message receive has failed. To troubleshoot and correct the cause of the Session Initiation Protocol Message Receive Failure alarm, refer to the "Session Initiation Protocol Message Receive Failure - Signaling (8)" section.

Timeout on Internet Protocol Address - Signaling (9)

The Timeout on Internet Protocol Address alarm (major) indicates that an IP address has timed out. To troubleshoot and correct the cause of the Timeout on Internet Protocol Address alarm, refer to the "Timeout on Internet Protocol Address - Signaling (9)" section.

Failed to Send Complete Session Initiation Protocol Message - Signaling (10)

The Failed to Send Complete Session Initiation Protocol Message alarm (minor) indicates that a SIP message failure has occurred. To troubleshoot and correct the cause of the Failed to Send Complete Session Initiation Protocol Message alarm, refer to the "Failed to Send Complete Session Initiation Protocol Message - Signaling (10)" section.

Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)

The Failed to Allocate Session Initiation Protocol Control Block alarm (major) indicates that a SIP control block allocation failed. To troubleshoot and correct the cause of the Failed to Allocate Session Initiation Protocol Control Block alarm, refer to the "Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)" section.

Feature Server is not Up or is not Responding to Call Agent - Signaling (12)

The Feature Server is not Up or is not Responding to Call Agent alarm (critical) indicates that the feature server is not up or is not responding to the call agent server. To troubleshoot and correct the cause of the Feature Server is not Up or is not Responding to Call Agent alarm, refer to the "Feature Server is not Up or is not Responding to Call Agent - Signaling (12)" section.

Signaling System 7 Signaling Link Down - Signaling (13)

The Signaling System 7 Signaling Link Down alarm (major) indicates the SS7 signaling link is down. To troubleshoot and correct the cause of the Signaling System 7 Signaling Link Down alarm, refer to the "Signaling System 7 Signaling Link Down - Signaling (13)" section.

Link is Remotely Inhibited - Signaling (14)

The Link is Remotely Inhibited alarm (minor) indicates that the SS7 link is inhibited at the remote end. To troubleshoot and correct the cause of the Link is Remotely Inhibited alarm, refer to the "Link is Remotely Inhibited - Signaling (14)" section.

Link is Locally Inhibited - Signaling (15)

The Link is Locally Inhibited alarm (minor) indicates that the SS7 link is inhibited at the local end. To troubleshoot and correct the cause of the Link is Locally Inhibited alarm, refer to the "Link is Locally Inhibited - Signaling (15)" section.

Link is Congested - Signaling (16)

The Link is Congested alarm (minor) indicates that the SS7 link is congested. To troubleshoot and correct the cause of the Link is Congested alarm, refer to the "Link is Congested - Signaling (16)" section.

Link: Local Processor Outage - Signaling (17)

The Link: Local Processor Outage alarm (minor) indicates that the SS7 link has experienced a local processor outage. To troubleshoot and correct the cause of the Link: Local Processor Outage alarm, refer to the "Link: Local Processor Outage - Signaling (17)" section.

Link: Remote Processor Outage - Signaling (18)

The Link: Remote Processor Outage alarm (minor) indicates that the SS7 link has experienced a remote processor outage. To troubleshoot and correct the cause of the Link: Remote Processor Outage alarm, refer to the "Link: Remote Processor Outage - Signaling (18)" section.

Link Set Inaccessible - Signaling (19)

The Link Set Inaccessible alarm (major) indicates that the specified SS7 link in inaccessible. To troubleshoot and correct the cause of the Link Set Inaccessible alarm, refer to the "Link Set Inaccessible - Signaling (19)" section.

Link Set Congestion - Signaling (20)

The Link Set Congestion alarm (major) indicates that the specified SS7 link set is congested. To troubleshoot and correct the cause of the Link Set Congestion alarm, refer to the "Link Set Congestion - Signaling (20)" section.

Route Set Failure - Signaling (21)

The Route Set Failure alarm (major) indicates that the specified route set has a experienced a failure. To troubleshoot and correct the cause of the Route Set Failure alarm, refer to the "Route Set Failure - Signaling (21)" section.

Route Set Congested - Signaling (22)

The Route Set Congested alarm (minor) indicates that the specified route set is congested. To troubleshoot and correct the cause of the Route Set Congested alarm, refer to the "Route Set Congested - Signaling (22)" section.

Destination Point Code Unavailable - Signaling (23)

The Destination Point Code Unavailable alarm (major) indicates that the specified DPC is not available. To troubleshoot and correct the cause of the Destination Point Code Unavailable alarm, refer to the "Destination Point Code Unavailable - Signaling (23)" section.

Destination Point Code Congested - Signaling (24)

The Destination Point Code Congested alarm (minor) alarm indicates that the specified DPC is congested. To troubleshoot and correct the cause of the Destination Point Code Congested alarm, refer to the "Destination Point Code Congested - Signaling (24)" section.

Unanswered Blocking Message - Signaling (25)

The Unanswered Blocking Message event serves as a warning that a BLO message was not answered. The primary cause of the event is that a BLO message was not acknowledged before the T13 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Unblocking Message - Signaling (26)

The Unanswered Unblocking Message event serves as a warning that an UBL message was not answered. The primary cause of the event is that a UBL message was not acknowledged before the T15 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Circuit Group Blocking Message - Signaling (27)

The Unanswered Circuit Group Blocking Message event serves as a warning that a CGB message was not answered. The primary cause of the event is that a CGB message was not acknowledged before the T19 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Circuit Group Unblocking Message - Signaling (28)

The Unanswered Circuit Group Unblocking Message event serves as a warning that a CGU message was not answered. The primary cause of the event is that a CGU message was not acknowledged before the T21 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Circuit Query Message - Signaling (29)

The Unanswered Circuit Query Message event serves as a warning that a CQM message was not answered. The primary cause of the event is that a CQM message was not acknowledged before the T28 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Circuit Validation Test Message - Signaling (30)

The Unanswered Circuit Validation Test Message event serves as a warning that a CVT message was not answered. The primary cause of the event is that a CVT message was not acknowledged before the Tcvt expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Reset Circuit Message - Signaling (31)

The Unanswered Reset Circuit Message event serves as a warning that a RSC message was not answered. The primary cause of the event is that a RSC message was not acknowledged before the T17 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Group Reset Message - Signaling (32)

The Unanswered Group Reset Message event serves as a warning that a GRS message was not answered. The primary cause of the event is that a a GRS message was not acknowledged before the T23 expired for the associated CIC. To correct the primary cause of the event, Verify that the SS7 signaling adapter processes is running normally. verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Release Message - Signaling (33)

The Unanswered Release Message event serves as a warning that a REL message was not answered. The primary cause of the event is that a REL message was not acknowledged before the T5 expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Unanswered Continuity Check Request Message - Signaling (34)

The Unanswered Continuity Check Request Message event serves as a warning that a continuity check request (CCR) message was not answered. The primary cause of the event is that a LPA message was not acknowledged before the TCCR expired for the associated CIC. To correct the primary cause of the event, verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.

Trunk Locally Blocked - Signaling (36)

The Trunk Locally Blocked alarm (minor) indicates that the trunk is locally blocked. To troubleshoot and correct the cause of the Trunk Locally Blocked alarm, refer to the "Trunk Locally Blocked - Signaling (36)" section. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

Trunk Remotely Blocked - Signaling (40)

The Trunk Remotely Blocked alarm (major) indicates that the trunk is remotely blocked. To troubleshoot and correct the cause of the Trunk Remotely Blocked alarm, refer to the "Trunk Remotely Blocked - Signaling (40)" section.

Continuity Testing Message Received on the Specified Circuit Identification Code - Signaling (42)

The Continuity Testing Message Received on the Specified Circuit Identification Code event functions as an informational alert that the COT message was received on the specified CIC. The event is informational and no further action is required.

Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code - Signaling (43)

The Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code event functions as an informational alert that the RLC was received in response to the RSC message received on the specified CIC. The event is informational and no further action is required,

Continuity Recheck is Performed on Specified Circuit Identification Code - Signaling (44)

The Continuity Recheck is Performed on Specified Circuit Identification Code event functions as an informational alert that a continuity recheck was performed on the specified CIC. The event is informational and further action is required.

Circuit is UNEQUIPPED on Remote Side - Signaling (45)

The Circuit is UNEQUIPPED on Remote Side event functions as an informational alert the circuit is unequipped on the remote side. The primary cause of the event is that an unequipped circuit has been detected on the remote side. To correct the primary cause of the event, monitor the event reports at the network level to verify if an existing circuit was unequipped causing a status mismatch with the local end.

Specified Circuit Identification Code is Invalid for the Operation - Signaling (46)

The Specified Circuit Identification Code is Invalid for the Operation event functions as an informational alert that the specified CIC in invalid for the attempted operation. The primary cause of the event is that an invalid operation was performed on the specified CIC. To correct the primary cause of the event, verify that the SS7 provisioning tables are properly configured at the circuit level.

A General Processing Error Encountered - Signaling (49)

The A General Processing Error Encountered event functions as a informational alert that a general processing error has occurred. The primary cause of the event is that a general SS7 processing error occurred due to all resources being busy or an invalid event occurring. To correct the primary cause of the event, verify the status of the signaling adapter process and the SS7 signaling interface to verify proper operation.

Unexpected Message for the Call State is Received: Clear Call - Signaling (50)

The Unexpected Message for the Call State is Received: Clear Call event functions as an informational alert that an unexpected message for the call state has been received. The primary cause of the even is that an unexpected message was received for the current call state. To correct the primary cause of the event, verify the status of the signaling adapter process and the SS7 signaling interface to verify proper operation.

Set Trunk State as Remotely Unequipped - Signaling (51)

The Set Trunk State as Remotely Unequipped event functions as an informational alert that the trunk state is currently set as remotely unequipped. The primary cause of the event is that the specified CIC is marked at remotely unequipped due to the CQM response indicating that it is unequipped at the far end. To correct the primary cause of the event, equip the trunk circuit at the far end.

Set Trunk State as NOT Remotely Blocked - Signaling (52)

The Set Trunk State as NOT Remotely Blocked event functions as an informational alert that the trunk state has been set as not remotely blocked. The primary cause of the event is that the specified CIC is marked as not remotely blocked due to the CQM response indicating that it is not remotely blocked at the far end. The event is informational and no further action is required.

Set Trunk State as Remotely Blocked - Signaling (53)

The Set Trunk State as Remotely Blocked event functions as an informational alert that the trunk state is set as remotely blocked. The primary cause of the event is that the specified CIC is marked as remotely blocked due to the CQM response indicating that it is remotely blocked at the far end. To correct the primary cause of the event, clear the blocking situation at the far end based on network level event reports.

Circuit Validation Test Aborted - Signaling (54)

The Circuit Validation Test Aborted event functions as an informational alert that the circuit validation test has been aborted. The primary cause of the event is that the circuit specified failed a validation test due to an internal failure. To correct the primary cause of the event, verify the SS7 signaling adapter process and SS7 interface is operating normally.

Circuit Validation Successful - Signaling (55)

The Circuit Validation Successful event functions as an informational alert that the circuit validation was successful. The event is informational and no further actions is required.

Continuity Recheck Failed - Signaling (57)

The Continuity Recheck Failed event functions as an informational alert that the continuity recheck failed. The primary cause of the event is that a continuity recheck of the specified CIC failed. To correct the primary cause of the event, verify the SS7 signaling adapter process and SS7 interface is operating normally.

Continuity Recheck Successful - Signaling (58)

The Continuity Recheck Successful event functions as an informational alert that the continuity recheck of the specified CIC was successful. The event is informational and no further action is required.

Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)

The Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway alarm (major) indicates that specified ISDN trunk group status was changed due to a media gateway operation. To troubleshoot and correct the cause of the Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway alarm, refer to the "Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)" section.

Integrated Services Digital Network STATUS Message Containing Error Indication Received - Signaling (60)

The Integrated Services Digital Network STATUS Message Containing Error Indication Received event functions as a warning that an ISDN status message containing an error indication has been received. The primary cause of the event is that an ISDN status message was received containing an error indication for the specified termination. To correct the primary cause of the event, place the specified termination in service state if the specified termination is not operating normally.

Trunk Operational State Changed by Service Message - Signaling (61)

The Trunk Operational State Changed by Service Message event functions as an informational alert that the trunk operational state was changed by a service message. The primary cause of the event is that the specified trunk group operational status was changed via a service message from the specified gateway. To correct the primary cause of the event, monitor the event reports at the network level to verify that the specified gateway and terminations are operating normally.

Received Integrated Services Digital Network RESTART Message - Signaling (62)

The Received Integrated Services Digital Network RESTART Message event functions as an informational alert that a ISDN restart message was received. The primary cause of the event is that an ISDN restart message was received from the specified gateway. To correct the primary cause of the event, monitor the event reports at the network level to verify that the specified gateway and terminations are operating normally.

Media Gateway/Termination Faulty - Signaling (63)

The Media Gateway/Termination Faulty alarm (major) indicates that a media gateway or termination has gone faulty due to the detection of an unknown endpoint, unknown package type, and unknown event, a hardware failure, or a general call agent error. To troubleshoot and correct the cause of the Media Gateway/Termination Faulty alarm, refer to the "Media Gateway/Termination Faulty - Signaling (63)" section.

Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)

The Media Gateway Adapter Running out of Shared Memory Pools alarm (critical) indicates that the MGCP signaling adapter was unable to allocate data store for an IPC message due to a lack of resources. To troubleshoot and correct the cause of the Media Gateway Adapter Running out of Shared Memory Pools alarm, refer to the "Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)" section.

Media Gateway Adapter Running out of Heap Memory - Signaling (65)

The Media Gateway Adapter Running out of Heap Memory alarm (critical) indicates that the MGCP signaling adapter was unable to allocate data store for an IPC message from the heap due to a lack of resources. To troubleshoot and correct the cause of the Media Gateway Adapter Running out of Heap Memory alarm, refer to the "Media Gateway Adapter Running out of Heap Memory - Signaling (65)" section.

Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)

The Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) alarm (major) indicates that a call agent internal error has occurred causing the restart of the MGCP signaling adapter. To troubleshoot and correct the cause of the Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) alarm, refer to the "Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)" section.

Media Gateway or Termination are Found Administratively Out of Service - Signaling (68)

The Media Gateway or Termination are Found Administratively Out of Service alarm (major) indicates that tthe specified media gateway is going out-of-service due to being powered down, the MGCP application going faulty, or a hardware failure has occured. To troubleshoot and correct the cause of the Media Gateway or Termination are Found Administratively Out of Service alarm, refer to the "Media Gateway or Termination are Found Administratively Out of Service - Signaling (68)" section. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

Call Agent and Feature Server Communication Message Timeout - Signaling (69)

The Call Agent and Feature Server Communication Message Timeout alarm (critical) indicates that a CA and FS communications message timed out. To troubleshoot correct the cause of the Call Agent and Feature Server Communication Message Timeout alarm, refer to the "Call Agent and Feature Server Communication Message Timeout - Signaling (69)" section.

Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication - Signaling (70)

The Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication event serves as a warning that the ISDN signaling adapter is unable to restore D-channel due to a communication failure. The primary cause of the event is that the ISDN signaling adapter is unable to restore a D-channel due to incorrect backhaul provisioning at the media gateway or call agent. To correct the primary cause of the event, ensure the provisioning of the backhaul port is correct at both the call agent and media gateway.

Integrated Services Digital Network Unable to Establish D-channel - Signaling (71)

The Integrated Services Digital Network Unable to Establish D-channel event serves as a warning that the ISDN signaling adaptor is unable to establish D-channel. The primary cause of the event is that ISDN signaling adapter is unable to establish a D-channel due to layer 1 parameters not being provisioned correctly or improper provisioning of the network or user side. To correct the primary cause of the event, verify the correct provisioning at the media gateway.

Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time - Signaling (72)

The Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time event serves as a warning that calls were lost due to the D-channels being down for a period of time. The primary cause of the event is that ISDN signaling adapter has lost calls due to a D-channel being down as a result of a media gateway power loss or a loss of connection between the PBX and media gateway. To correct the primary cause of the event, resupply power to the media gateway and verify that the connection between the PBX and media gateway is intact.

Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired - Signaling (73)

The Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired event serves as a warning that the ISDN signaling adapter was unable to send a restart due to the restart timer being expired. The primary cause of the event is that the ISDN signaling adapter was unable to send a RESTART message due to the expiration of the RESTART timer. To correct the primary cause of the event, verify that the RESTART timer is set to an appropriate level.

Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired - Signaling (74)

The Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired event serves as a warning that the ISDN signal adapter was unable to send a service message due to the service timer being expired. The primary cause of the event is that the ISDN signaling adapter was unable to send a SERVICE message due to the expiration of the SERVICE timer. To correct the primary cause of the event, ensure that the RESTART timer is set to an appropriate level.

Signaling System 7 Stack not Ready - Signaling (75)

The Signaling System 7 Stack not Ready alarm (critical) indicates that the SS7 stack in not ready. To trouble and correct the cause of the Signaling System 7 Stack not Ready alarm, refer to the "Signaling System 7 Stack not Ready - Signaling (75)" section.

Timeout on Remote Instance - Signaling (76)

The Timeout on Remote Instance event functions as an informational alert that communication on a remote instance timed out. The primary cause of the event is that communication between call agent and remote instance is faulty. The event is informational and no further action is required.

Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling - Signaling (77)

The Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling event functions as an informational alert that an ISDN D-channel switchover has occurred non-facility associated signaling (NFAS). The primary cause of the event is that the operator manually switched the D-channels using the CLI. To verify the primary cause of the event, verify operator action. The secondary cause of the event is that the active D-channel was lost. To correct the secondary cause of the event, verify that gateway is operational and connection to PBX is good.

Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)

The Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling alarm (minor) indicates that one of the ISDN D-channels in the PRI is down. To troubleshoot and correct the cause of the Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling alarm, refer to the "Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)" section.

Media Gateway Unreachable - Signaling (79)

The Media Gateway Unreachable alarm (major) indicates that the media gateway is unreachable. To troubleshoot and correct the cause of the Media Gateway Unreachable alarm, refer to the "Media Gateway Unreachable - Signaling (79)" section. For additional troubleshooting information, refer to Appendix A, "System Usage of MGW Keepalive Parameters, Release 4.4.x."

Out of Bounds, Memory/Socket Error - Signaling (80)

The Out of Bounds, Memory/Socket Error alarm (critical) indicates that a memory socket out of bounds error has occurred. To troubleshoot and correct the cause of the Out of Bounds, Memory/Socket Error alarm, refer to the "Out of Bounds, Memory/Socket Error - Signaling (80)" section.

Insufficient Heap Memory - Signaling (81) (H.323)

The Insufficient Heap Memory alarm (critical) indicates that there is insufficient heap memory. To troubleshoot and correct the cause of the Insufficient Heap Memory alarm, refer to the "Insufficient Heap Memory - Signaling (81) (H.323)" section.

Insufficient Shared Memory Pools - Signaling (82) (H.323)

The Insufficient Shared Memory Pools alarm (critical) indicates that there is insufficient shared memory pools. To troubleshoot and correct the cause of the Insufficient Shared Memory Pools alarm, refer to the "Insufficient Shared Memory Pools - Signaling (82) (H.323)" section.

Error While Binding to Socket - Signaling (83)

The Error While Binding to Socket alarm (critical) indicates that an error occurred while binding to the socket. To troubleshoot and correct the cause of the Error While Binding to Socket alarm, refer to the "Error While Binding to Socket - Signaling (83)" section.

Reached Maximum Socket Limit - Signaling (84) (H.323)

The Reached Maximum Socket Limit alarm (critical) indicates that the Cisco BTS 10200 Softswitch system has reached the maximum socket limit. To troubleshoot and correct the cause of the Reached Maximum Socket Limit alarm, refer to the "Reached Maximum Socket Limit - Signaling (84) (H.323)" section.

Initialization Failure - Signaling (85)

The Initialization Failure alarm (critical) indicates that the Cisco BTS 10200 Softswitch system failed to initialize. To troubleshoot and correct the cause of the Initialization Failure alarm, refer to the "Initialization Failure - Signaling (85)" section.

Remote H323 Gateway is not Reachable - Signaling (86) (H.323)

The Remote H323 Gateway is not Reachable alarm (major) indicates that the remote H323 gateway is not reachable. To troubleshoot and correct the cause of the Remote H323 Gateway is not Reachable alarm, refer to the "Remote H323 Gateway is not Reachable - Signaling (86) (H.323)" section.

H323 Message Parsing Error - Signaling (87) (H.323)

The H323 Message Parsing Error alarm (major) indicates that a H323 message parsing error has occurred. To troubleshoot and correct the cause of the H323 Message Parsing Error alarm, refer to the "H323 Message Parsing Error - Signaling (87) (H.323)" section.

H323 Message Encoding Error - Signaling (88) (H.323)

The H323 Message Encoding Error alarm (major) indicates that a H323 message encoding error has occurred. To troubleshoot and correct the cause of the H323 Message Encoding Error alarm, refer to the "H323 Message Encoding Error - Signaling (88) (H.323)" section.

Gatekeeper not Available/Reachable - Signaling (89)

The Gatekeeper not Available/Reachable alarm (major) indicates that the gatekeeper is not available or the gatekeeper is not reachable. To troubleshoot and correct the cause of the Gatekeeper not Available/Reachable alarm, refer to the "Gatekeeper not Available/Reachable - Signaling (89)" section.

Alternate Gatekeeper is not Responding - Signaling (90)

The Alternate Gatekeeper is not Responding alarm (major) indicates that the alternate gatekeeper is not responding. To troubleshoot and correct the cause of the Alternate Gatekeeper is not Responding alarm, refer to the "Alternate Gatekeeper is not Responding - Signaling (90)" section.

Endpoint Security Violation - Signaling (91) (H.323)

The Endpoint Security Violation alarm (major) indicates that an H323 security violation has occurred. To troubleshoot and correct the cause of the Endpoint Security Violation alarm, refer to the "Endpoint Security Violation - Signaling (91) (H.323)" section.

Invalid Call Identifier - Signaling (92)

The Invalid Call Identifier alarm (minor) indicates that the Call ID was invalid or changed mid-call. To troubleshoot and correct the cause of the Invalid Call Identifier alarm, refer to the "Invalid Call Identifier - Signaling (92)" section.

Invalid Call Reference Value - Signaling (93)

The Invalid Call Reference Value alarm (minor) indicates that the Call ID was invalid or changed mid-call. To troubleshoot and correct the cause of the Invalid Call Reference Value alarm, refer to the "Invalid Call Reference Value - Signaling (93)" section.

Invalid Conference Identifier - Signaling (94)

The Invalid Conference Identifier alarm (minor) indicates that the Call ID was invalid or changed mid-call. To troubleshoot and correct the cause of the Invalid Conference Identifier alarm, refer to the "Invalid Conference Identifier - Signaling (94)" section.

Invalid Message from the Network - Signaling (95)

The Invalid Message from the Network alarm (minor) indicates that an unsupported or invalid message type was received from network. To troubleshoot and correct the cause of the Invalid Message from the Network alarm, refer to the "Invalid Message from the Network - Signaling (95)" section.

Internal Call Processing Error - Signaling (96)

The Internal Call Processing Error alarm (minor) indicates that an internal call processing error has occurred. To troubleshoot and correct the cause of the Internal Call Processing Error alarm, refer to the "Internal Call Processing Error - Signaling (96)" section.

Insufficient Information to Complete Call - Signaling (97)

The Insufficient Information to Complete Call alarm (minor) indicates that there was insufficient information to complete a call. To troubleshoot and correct the cause of the Insufficient Information to Complete Call alarm, refer to the "Insufficient Information to Complete Call - Signaling (97)" section.

H323 Protocol Inconsistencies - Signaling (98) (H.323)

The H323 Protocol Inconsistencies alarm (minor) indicates that the H323 endpoint and Cisco BTS 10200 Softswitch are running different protocol versions. To troubleshoot and correct the cause of the H323 Protocol Inconsistencies alarm, refer to the "H323 Protocol Inconsistencies - Signaling (98) (H.323)" section.

Abnormal Call Clearing - Signaling (99)

The Abnormal Call Clearing alarm (minor) indicates that an unsupported or invalid message type was received from network. To troubleshoot and correct the cause of the Abnormal Call Clearing alarm, refer to the "Abnormal Call Clearing - Signaling (99)" section.

Codec Negotiation Failed - Signaling (100)

The Codec Negotiation Failed alarm (minor) indicates that the codec negotiation has failed. To troubleshoot and correct the cause of the Codec Negotiation Failed alarm, refer to the "Codec Negotiation Failed - Signaling (100)" section.

Per Call Security Violation - Signaling (101)

The Per Call Security Violation alarm (minor) indicates that a call security violation has occurred. To troubleshoot and correct the cause of the Per Call Security Violation alarm, refer to the "Per Call Security Violation - Signaling (101)" section.

H323 Network Congested - Signaling (102) (H.323)

The H323 Network Congested alarm indicates (minor) that the H323 application process has depleted its resources and no more calls can be completed. To troubleshoot and correct the cause of the H323 Network Congested alarm, refer to the "H323 Network Congested - Signaling (102) (H.323)" section.

Aggregation Connection Down - Signaling (103)

The Aggregation Connection Down alarm (major) indicates that the aggregation (AGGR) TCP connection is down. To troubleshoot and correct the cause of the Aggregation Connection Down alarm, refer to the "Aggregation Connection Down - Signaling (103)" section.

Aggregation Unable To Establish Connection - Signaling (104)

The Aggregation Unable To Establish Connection event functions as an informational alert that the AGGR is unable to establish a connection. The primary cause of the event is that the TCP connection failed to establish. To correct the primary cause of the event, check the IP Connectivity of CA and CMTS.

Aggregation Gate Set Failed - Signaling (105)

The Aggregation Gate Set Failed event functions as an informational alert that the AGGR gate set failed. The primary cause of the event is that the gate set acknowledgement never came from the CMTS. The event is informational and no further action is required.

Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)

The Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down alarm (minor) indicates that the enhanced subscriber authentication (ESA) Cisco BTS 10200 Softswitch DF connection is down. To troubleshoot and correct the cause of the Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down alarm, refer to the "Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)" section.

Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)

The Logical Internet Protocol Addresses not Mapped Correctly alarm (critical) indicates that the logical IP addresses are not mapped correctly. To troubleshoot and correct the cause of the Logical Internet Protocol Addresses not Mapped Correctly alarm, refer to the "Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)" section.

Current SIA Configuration only Valid for Simplex Systems - Signaling (108)

The Current SIA Configuration only Valid for Simplex Systems alarm (major) indicates that the Cisco BTS 10200 Softswitch system can only operate in the simplex mode. To troubleshoot and correct the cause of the Current SIA Configuration only Valid for Simplex Systems alarm, refer to the "Current SIA Configuration only Valid for Simplex Systems - Signaling (108)" section.

Stream Control Transmission Protocol Association Failure - Signaling (109)

The Stream Control Transmission Protocol Association Failure alarm (major) indicates that the SCTP association failed. To troubleshoot and correct the cause of the Stream Control Transmission Protocol Association Failure alarm, refer to the "Stream Control Transmission Protocol Association Failure - Signaling (109)" section.

Signaling Gateway Group is Out-of-Service - Signaling (110)

The Signaling Gateway Group is Out-of-Service alarm (major) indicates that the signaling gateway group is out-of-service. To troubleshoot and correct the cause of the Signaling Gateway Group is Out-of-Service alarm, refer to the "Signaling Gateway Group Is Out-of-Service - Signaling (110)" section.

Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) - Signaling (111)

The Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) alarm (major) indicates that the SCTP association is degraded. To troubleshoot and correct the cause of the Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) alarm, refer to the "Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) - Signaling (111)" section.

Stream Control Transmission Protocol Association Configuration Error - Signaling (112)

The Stream Control Transmission Protocol Association Configuration Error alarm (minor) indicates that a SCTP association configuration error has occurred. To troubleshoot and correct the cause of the Stream Control Transmission Protocol Association Configuration Error alarm, refer to the "Stream Control Transmission Protocol Association Configuration Error - Signaling (112)" section.

Signaling Gateway Failure - Signaling (113)

The Signaling Gateway Failure alarm (major) indicates that all associated signaling gateway processes are out-of-service. To troubleshoot and correct the cause of the Signaling Gateway Failure alarm, refer to the "Signaling Gateway Failure - Signaling (113)" section.

Signaling Gateway Process is Out-of-Service - Signaling (114)

The Signaling Gateway Process is Out-of-Service alarm (major) indicates that all SCTP associations between the SGP and the CA are out-of-service. To troubleshoot and correct the cause of the Signaling Gateway Process is Out-of-Service alarm, refer to the "Signaling Gateway Process Is Out-of-Service - Signaling (114)" section.

Invalid Routing Context Received - Signaling (115)

The Invalid Routing Context Received event serves as a warning that an invalid routing context was received. The primary cause of the event is that the routing context was configured improperly on the CA or the SG. To correct the primary cause of the event, reconfigure the routing context on the CA or the SG so that the routing context matches in both places.

Destination Point Code User Part Unavailable - Signaling (116)

The Destination Point Code User Part Unavailable alarm (major) indicates that a layer 4 user part, such as ISUP, is unavailable at the DPC in the SS7 network. To troubleshoot and correct the cause of the Destination Point Code User Part Unavailable alarm, refer to the "Destination Point Code User Part Unavailable - Signaling (116)" section.

Circuit Validation Test Message Received for an Unequipped Circuit Identification Code - Signaling (117)

The Circuit Validation Test Message Received for an Unequipped Circuit Identification Code alarm (minor) indicates that a CVT message was received for an unequipped CIC. To troubleshoot and correct the cause of the Circuit Validation Test Message Received for an Unequipped Circuit Identification Code alarm, refer to the "Circuit Validation Test Message Received for an Unequipped Circuit Identification Code - Signaling (117)" section.

Circuit Verification Response Received with Failed Indication - Signaling (118)

The Circuit Verification Response Received with Failed Indication alarm (minor) indicates that a circuit verification response (CVR) message was received with a failure indication. To troubleshoot and correct the cause of the Circuit Verification Response Received with Failed Indication alarm, refer to the "Circuit Verification Response Received with Failed Indication - Signaling (118)" section.

Signaling System 7 Adapter Process Faulty - Signaling (119)

The Signaling System 7 Adapter Process Faulty alarm (critical) indicates that a S7A process is faulty. To troubleshoot and correct the cause of the Signaling System 7 Adapter Process Faulty alarm, refer to the "S7A Process Faulty - Signaling (119)" section on page 10-116.

Signaling System 7 Module/Signaling System 7 Adapter Faulty - Signaling (120)

The Signaling System 7 Module/Signaling System 7 Adapter Faulty alarm (critical) indicates that the S7M/S7A processes are faulty. To troubleshoot and correct the cause of the Signaling System 7 Module/Signaling System 7 Adapter Faulty alarm, refer to the "S7M/S7A Faulty - Signaling (120)" section on page 10-116.

Message Transfer Part 3 User Adapter Cannot Go Standby - Signaling (121)

The Message Transfer Part 3 User Adapter Cannot Go Standby alarm (major) indicates that the M3UA process cannot go into standby mode. To troubleshoot and correct the cause of the Message Transfer Part 3 User Adapter Cannot Go Standby alarm, refer to the "Message Transfer Part 3 User Adapter Cannot Go Standby - Signaling (121)" section.

Message Transfer Part 3 User Adapter Cannot Go Active - Signaling (122)

The Message Transfer Part 3 User Adapter Cannot Go Active alarm (major) indicates that the M3UA process cannot go into active mode. To troubleshoot and correct the cause of the Message Transfer Part 3 User Adapter Cannot Go Active alarm, refer to the "Message Transfer Part 3 User Adapter Cannot Go Active - Signaling (122)" section.

Remote Subsystem is out of Service - Signaling (124)

The Remote Subsystem is out of Service alarm (minor) indicates that the remote subsystem is out-of-service. To troubleshoot and correct the cause of the Remote Subsystem is out of Service alarm, refer to the "Remote Subsystem is Out Of Service - Signaling (124)" section.

Signaling Connection Control Part Routing Error - Signaling (125)

The Signaling Connection Control Part Routing Error alarm (major) indicates that the SCCP route was invalid or not available. To troubleshoot and correct the cause of the Signaling Connection Control Part Routing Error alarm, refer to the "Signaling Connection Control Part Routing Error - Signaling (125)" section.

Signaling Connection Control Binding Failure - Signaling (126)

The Signaling Connection Control Binding Failure alarm (major) indicates that the SCCP binding failed. To troubleshoot and correct the cause of the Signaling Connection Control Binding Failure alarm, refer to the "Signaling Connection Control Part Binding Failure - Signaling (126)" section.

Transaction Capabilities Application Part Binding Failure - Signaling (127)

The Transaction Capabilities Application Part Binding Failure alarm (major) indicates that the TCAP binding failed. To troubleshoot and correct the cause of the Transaction Capabilities Application Part Binding Failure alarm, refer to the "Transaction Capabilities Application Part Binding Failure - Signaling (127)" section.

Tr