Table Of Contents

Signaling Troubleshooting

Introduction

Signaling Events and Alarms

Signaling (1)

Signaling (2)

Signaling (3)

Signaling (4)

Signaling (5)

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 (35)

Signaling (36)

Signaling (37)

Signaling (38)

Signaling (39)

Signaling (40)

Signaling (41)

Signaling (42)

Signaling (43)

Signaling (44)

Signaling (45)

Signaling (46)

Signaling (47)

Signaling (48)

Signaling (49)

Signaling (50)

Signaling (51)

Signaling (52)

Signaling (53)

Signaling (54)

Signaling (55)

Signaling (56)

Signaling (57)

Signaling (58)

Signaling (59)

Signaling (60)

Signaling (61)

Signaling (62)

Signaling (63)

Signaling (64)

Signaling (65)

Signaling (66)

Signaling (67)

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 (123)

Signaling (124)

Signaling (125)

Signaling (126)

Signaling (127)

Signaling (128)

Signaling (129)

Signaling (130)

Signaling (131)

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 (146)

Signaling (147)

Signaling (148)

Signaling (149)

Signaling (150)

Signaling (151)

Signaling (152)

Signaling (153)

Signaling (154)

Signaling (155)

Signaling (156)

Signaling (157)

Signaling (158)

Signaling (159)

Signaling (160)

Signaling (161)

Signaling (162)

Signaling (163)

Signaling (164)

Signaling (165)

Signaling (166)

Signaling (167)

Signaling (168)

Signaling (169)

Signaling (170)

Signaling (171)

Signaling (172)

Signaling (173)

Signaling (174)

Signaling (175)

Signaling (176)

Signaling (177)

Signaling (178)

Signaling (179)

Monitoring Signaling Events

Test Report—Signaling (1)

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)

Call Agent Is Not Up or Is Not Responding to the Feature Server—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 Not Facility Associated Signaling—Signaling (77)

Integrated Services Digital Network Single D-Channel Down for Not Facility Associated Signaling—Signaling (78)

Trunking Gateway Unreachable—Signaling (79)

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

Insufficient Heap Memory—Signaling (81)

Insufficient Shared Memory Pools—Signaling (82)

Error While Binding to Socket—Signaling (83)

Reached Maximum Socket Limit—Signaling (84)

Initialization Failure—Signaling (85)

Remote H.323 Gateway Is Not Reachable—Signaling (86)

H.323 Message Parsing Error—Signaling (87)

H.323 Message Encoding Error—Signaling (88)

Gatekeeper Not Available/Reachable—Signaling (89)

Alternate Gatekeeper Is Not Responding—Signaling (90)

Endpoint Security Violation—Signaling (91)

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)

H.323 Protocol Inconsistencies—Signaling (98)

Abnormal Call Clearing—Signaling (99)

Codec Negotiation Failed—Signaling (100)

Per Call Security Violation—Signaling (101)

H.323 Network Congested—Signaling (102)

Aggregation Connection Down—Signaling (103)

Aggregation Unable to Establish Connection—Signaling (104)

Aggregation Gate Set Failed—Signaling (105)

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

Logical Internet Protocol Addresses Not Mapped Correctly—Signaling (107)

Simplex Only Operational Mode—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)

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)

All Retransmission Attempts of Session Initiation Protocol Request or Response Failed—Signaling (146)

Domain Name System Service Addresses Exhausted—Signaling (147)

Stream Control Transmission Protocol Association Congested—Signaling (150)

Subscriber Line Faulty—Signaling (151)

Termination Transient Error Received—Signaling (152)

Emergency Trunks Become Locally Blocked—Signaling (153)

Emergency Trunks Become Remotely Blocked—Signaling (154)

Packet Cable Multi-Media Unsolicited Gate Delete—Signaling (155)

Integrated Services Digital Network Signaling Gateway Down—Signaling (156)

Integrated Services Digital Network Signaling Gateway Inactive—Signaling (157)

Invalid Integrated Services Digital Network Interface Identification—Signaling (158)

Integrated Services Digital Network User Adaptation Layer Cannot Go Active—Signaling (159)

Integrated Services Digital Network User Adaptation Layer Cannot Go Standby—Signaling (160)

Session Initiation Protocol Update Not Allowed for Operator Service Position System Calls—Signaling (161)

Session Initiation Protocol Server Group Element Operationally Out of Service—Signaling (162)

Routing Key Inactive—Signaling (163)

Signaling Gateway Traffic Mode Mismatch—Signaling (164)

No Session Initiation Protocol P-DCS Billing Information Header Received—Signaling (165)

No Routing Keys Are Active—Signaling (166)

No Signaling Gateways Are Active—Signaling (167)

A Session Initiation Protocol Server Group Has No Child Elements Provisioned—Signaling (168)

Session Initiation Protocol Element Provisioned With Service Enabled Is Internally Disabled—Signaling (169)

Residential Gateway Endpoints Are Out of Service at the Gateway—Signaling (170)

Residential Gateway Unreachable—Signaling (171)

Multimedia Terminal Adapter Effective-Aggr-Id Becomes Unavailable Due to Its IP Address—Signaling (172)

ENUM Server Domain Cannot be Resolved Into Any IP Address —Signaling (173)

ENUM Server Unavailable—Signaling (174)

ENUM Server Farm Unavailable—Signaling (175)

No Resources Available to Launch ENUM Query—Signaling (176)

ISDN Unable to Restore D-Channel Into In-Service Active State—Signaling (177)

Possible Overlap Dialing Misconfiguration—Signaling (178)

Trunk Group Registration Expired—Signaling (179)

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)

Call Agent Is Not Up or Is Not Responding to the Feature Server—Signaling (69)

Signaling System 7 Stack Not Ready—Signaling (75)

Integrated Services Digital Network Single D-Channel Down for Not Facility Associated Signaling—Signaling (78)

Trunking Gateway Unreachable—Signaling (79)

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

Insufficient Heap Memory—Signaling (81)

Insufficient Shared Memory Pools—Signaling (82)

Error While Binding to Socket—Signaling (83)

Reached Maximum Socket Limit—Signaling (84)

Initialization Failure—Signaling (85)

Remote H.323 Gateway Is Not Reachable—Signaling (86)

H.323 Message Parsing Error—Signaling (87)

H.323 Message Encoding Error—Signaling (88)

Gatekeeper not Available/Reachable—Signaling (89)

Alternate Gatekeeper Is Not Responding—Signaling (90)

Endpoint Security Violation—Signaling (91)

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)

H.323 Protocol Inconsistencies—Signaling (98)

Abnormal Call Clearing—Signaling (99)

Codec Negotiation Failed—Signaling (100)

Per Call Security Violation—Signaling (101)

H.323 Network Congested—Signaling (102)

Aggregation Connection Down—Signaling (103)

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

Logical Internet Protocol Addresses Not Mapped Correctly—Signaling (107)

Simplex Only Operational Mode—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)

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)

Subscriber Line Faulty—Signaling (151)

Emergency Trunks Become Locally Blocked—Signaling (153)

Emergency Trunks Become Remotely Blocked—Signaling (154)

Integrated Services Digital Network Signaling Gateway Down—Signaling (156)

Integrated Services Digital Network Signaling Gateway Inactive—Signaling (157)

Session Initiation Protocol Server Group Element Operationally Out of Service—Signaling (162)

Routing Key Inactive—Signaling (163)

Signaling Gateway Traffic Mode Mismatch—Signaling (164)

Residential Gateway Endpoints Are Out of Service at the Gateway—Signaling (170)

Residential Gateway Unreachable—Signaling (171)

Multimedia Terminal Adapter Effective-Aggr-Id Becomes Unavailable Due to Its IP Address—Signaling (172)

ENUM Server Domain Cannot be Resolved Into Any IP Address —Signaling (173)

ENUM Server Unavailable—Signaling (174)

ENUM Server Farm Unavailable—Signaling (175)

No Resources Available to Launch ENUM Query—Signaling (176)

Trunk Group Registration Expired—Signaling (179)

Signaling Troubleshooting

---

Revised: July 22, 2009, OL-15636-07

Introduction

This chapter provides the information needed for monitoring and troubleshooting 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 for monitoring and correcting the Signaling events

•Troubleshooting Signaling Alarms—Provides the information needed for troubleshooting and correcting the 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; the event and alarms are arranged in numerical order. Table 10-1 lists all of the signaling events and alarms by severity.

---

Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page l for detailed instructions on contacting Cisco TAC and opening a service request.

---

---

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	Information	Not Used
Signaling (12)	Signaling (7)	Signaling (10)	Signaling (4)	Signaling (1)	Signaling (2)
Signaling (64)	Signaling (8)	Signaling (14)	Signaling (6)	Signaling (42)	Signaling (3)
Signaling (65)	Signaling (9)	Signaling (15)	Signaling (25)	Signaling (43)	Signaling (5)
Signaling (69)	Signaling (11)	Signaling (16)	Signaling (26)	Signaling (44)	Signaling (35)
Signaling (75)	Signaling (13)	Signaling (17)	Signaling (27)	Signaling (45)	Signaling (37)
Signaling (80)	Signaling (19)	Signaling (18)	Signaling (28)	Signaling (46)	Signaling (38)
Signaling (81)	Signaling (20)	Signaling (22)	Signaling (29)	Signaling (49)	Signaling (39)
Signaling (82)	Signaling (21)	Signaling (24)	Signaling (30)	Signaling (50)	Signaling (41)
Signaling (83)	Signaling (23)	Signaling (36)	Signaling (31)	Signaling (51)	Signaling (47)
Signaling (84)	Signaling (40)	Signaling (78)	Signaling (32)	Signaling (52)	Signaling (48)
Signaling (85)	Signaling (59)	Signaling (92)	Signaling (33)	Signaling (53)	Signaling (56)
Signaling (107)	Signaling (63)	Signaling (93)	Signaling (34)	Signaling (54)	Signaling (67)
Signaling (110)	Signaling (66)	Signaling (94)	Signaling (60)	Signaling (55)	Signaling (123)
Signaling (119)	Signaling (68)	Signaling (95)	Signaling (70)	Signaling (57)	Signaling (128)
Signaling (120)	Signaling (79)	Signaling (96)	Signaling (71)	Signaling (58)	Signaling (129)
Signaling (142)	Signaling (86)	Signaling (97)	Signaling (72)	Signaling (61)	Signaling (130)
Signaling (144)	Signaling (87)	Signaling (98)	Signaling (73)	Signaling (62)	Signaling (131)
Signaling (153)	Signaling (88)	Signaling (99)	Signaling (74)	Signaling (76)	Signaling (148)
Signaling (154)	Signaling (89)	Signaling (100)	Signaling (115)	Signaling (77)	Signaling (149)
Signaling (162)	Signaling (90)	Signaling (101)	Signaling (132)	Signaling (104)
Signaling (173)	Signaling (91)	Signaling (102)	Signaling (138)	Signaling (105)
Signaling (174)	Signaling (103)	Signaling (106)	Signaling (141)	Signaling (133)
Signaling (175)	Signaling (108)	Signaling (112)	Signaling (146)	Signaling (134)
Signaling (176)	Signaling (109)	Signaling (117)	Signaling (147)	Signaling (135)
	Signaling (111)	Signaling (118)	Signaling (158)	Signaling (136)
	Signaling (113)	Signaling (124)	Signaling (159)	Signaling (137)
	Signaling (114)	Signaling (143)	Signaling (160)	Signaling (139)
	Signaling (116)	Signaling (145)	Signaling (161)	Signaling (140)
	Signaling (121)	Signaling (150)	Signaling (165)	Signaling (152)
	Signaling (122)	Signaling (151)	Signaling (166)	Signaling (155)
	Signaling (125)	Signaling (170)	Signaling (167)	Signaling (169)
	Signaling (126)	Signaling (171)	Signaling (168)	Signaling (178)
	Signaling (127)		Signaling (177)
	Signaling (156)
	Signaling (157)
	Signaling (163)
	Signaling (164)
	Signaling (172)
	Signaling (179)

Signaling (1)

Table 10-2 lists the details of the Signaling (1) informational event. For additional information, refer to the "Test Report—Signaling (1)" section.

Table 10-2 Signaling (1) Details 

Description	Test Report
Severity	Information
Threshold	10000
Throttle	0

Signaling (2)

Signaling (2) is not used.

Signaling (3)

Signaling (3) is not used.

Signaling (4)

Table 10-3 lists the details of the Signaling (4) warning event. To monitor and correct the cause of the event, refer to the "Invalid Message Received—Signaling (4)" section.

Table 10-3 Signaling (4) Details 

Description	Invalid Message Received
Severity	Warning
Threshold	100
Throttle	0
Datawords	Endpoint Name—STRING [40] Message Type—STRING [40]
Primary Cause	This event is 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 reprovisioned.

Signaling (5)

Signaling (5) is not used.

Signaling (6)

Table 10-4 lists the details of the Signaling (6) warning event. To monitor and correct the cause of the event, refer to the "Database Module Function Call Failure—Signaling (6)" section.

Table 10-4 Signaling (6) Details 

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 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)

Table 10-5 lists the details of the Signaling (7) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Socket Failure—Signaling (7)" section.

Table 10-5 Signaling (7) Details 

Description	Socket Failure
Severity	Major
Threshold	30
Throttle	0
Datawords	Reason Text—STRING [30]
Primary Cause	Issued when there is a failure in creating or binding to the User Datagram Protocol (UDP) socket.
Primary Action	Verify that there is no conflict in the port assignment with other processes in the system and ensure that no previous instance of the same process is still running.
Secondary Cause	A software logic problem has occurred.
Secondary Action	Contact the Cisco Technical Assistance Center (TAC).

Signaling (8)

Table 10-6 lists the details of the Signaling (8) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Message Receive Failure—Signaling (8)" section.

Table 10-6 Signaling (8) Details 

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 have occurred or an invalid network configuration exists.
Primary Action	Have your network administrator resolve the network errors. Contact Cisco TAC if you need assistance. Manually clear the alarm. Restart this call agent instance using the platform start command.

Signaling (9)

Table 10-7 lists the details of the Signaling (9) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Timeout on Internet Protocol Address—Signaling (9)" section.

Table 10-7 Signaling (9) Details 

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 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 the control mgw command to put it in service.

Signaling (10)

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

Table 10-8 Signaling (10) Details 

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 a SIP message because the message exceeded 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.

Signaling (11)

Table 10-9 lists the details of the Signaling (11) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Failed to Allocate Session Initiation Protocol Control Block—Signaling (11)" section.

Table 10-9 Signaling (11) Details 

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 for the changes to take effect.

Signaling (12)

Table 10-10 lists the details of the Signaling (12) critical alarm. 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.

Table 10-10 Signaling (12) Details 

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	The feature server platform is down or is not operating properly.
Primary Action	Restart the applicable feature server.

Signaling (13)

Table 10-11 lists the details of the Signaling (13) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Signaling Link Down—Signaling (13)" section.

Table 10-11 Signaling (13) Details 

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	The Signaling System 7 (SS7) trunk group may be out-of-service (OOS).
Primary Action	Use the control ss7-trunk-grp command 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	The SS7 link may be disconnected or faulty.
Ternary Action	Check the Ulticom local configuration.
Subsequent Cause	The remote SS7 signaling site may be down or incorrectly configured.
Subsequent Action	Check the Ulticom remote configuration.

Signaling (14)

Table 10-12 lists the details of the Signaling (14) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link Is Remotely Inhibited—Signaling (14)" section.

Table 10-12 Signaling (14) Details 

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 the events at the network level for any that are related to the specified SS7 link. Restorative actions need to be taken on the remote end.

Signaling (15)

Table 10-13 lists the details of the Signaling (15) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link Is Locally Inhibited—Signaling (15)" section.

Table 10-13 Signaling (15) Details 

Description	Link is Locally Inhibited
Severity	Minor
Threshold	100
Throttle	0
Datawords	Link Number—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 nonoperational, restore it to service.

Signaling (16)

Table 10-14 lists the details of the Signaling (16) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link Is Congested—Signaling (16)" section.

Table 10-14 Signaling (16) Details 

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)

Table 10-15 lists the details of the Signaling (17) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link: Local Processor Outage—Signaling (17)" section.

Table 10-15 Signaling (17) Details 

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 the underlying platform instances that support the specified SS7 link. Verify that the process and or platform are restarted and returned to service.

Signaling (18)

Table 10-16 lists the details of the Signaling (18) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link: Remote Processor Outage—Signaling (18)" section.

Table 10-16 Signaling (18) Details 

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)

Table 10-17 lists the details of the Signaling (19) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link Set Inaccessible—Signaling (19)" section.

Table 10-17 Signaling (19) Details 

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)

Table 10-18 lists the details of the Signaling (20) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Link Set Congestion—Signaling (20)" section.

Table 10-18 Signaling (20) Details 

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)

Table 10-19 lists the details of the Signaling (21) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Route Set Failure—Signaling (21)" section.

Table 10-19 Signaling (21) Details 

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 to verify its restoral to service.

Signaling (22)

Table 10-20 lists the details of the Signaling (22) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Route Set Congested—Signaling (22)" section.

Table 10-20 Signaling (22) Details 

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 the 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)

Table 10-21 lists the details of the Signaling (23) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Unavailable—Signaling (23)" section.

Table 10-21 Signaling (23) Details 

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 and the affected DPC.
Primary Action	Verify that an alternate routing has been assigned for traffic destined to the affected DPC.

Signaling (24)

Table 10-22 lists the details of the Signaling (24) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Congested—Signaling (24)" section.

Table 10-22 Signaling (24) Details 

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 the 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)

Table 10-23 lists the details of the Signaling (25) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Blocking Message—Signaling (25)" section.

Table 10-23 Signaling (25) Details 

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 are 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)

Table 10-24 lists the details of the Signaling (26) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Unblocking Message—Signaling (26)" section.

Table 10-24 Signaling (26) Details 

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 an 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 are 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)

Table 10-25 lists the details of the Signaling (27) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Circuit Group Blocking Message—Signaling (27)" section.

Table 10-25 Signaling (27) Details 

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 are 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)

Table 10-26 lists the details of the Signaling (28) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Circuit Group Unblocking Message—Signaling (28)" section.

Table 10-26 Signaling (28) Details 

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 are 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)

Table 10-27 lists the details of the Signaling (29) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Circuit Query Message—Signaling (29)" section.

Table 10-27 Signaling (29) Details 

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 are 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)

Table 10-28 lists the details of the Signaling (30) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Circuit Validation Test Message—Signaling (30)" section.

Table 10-28 Signaling (30) Details 

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 are 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)

Table 10-29 lists the details of the Signaling (31) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Reset Circuit Message—Signaling (31)" section.

Table 10-29 Signaling (31) Details 

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 are 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)

Table 10-30 lists the details of the Signaling (32) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Group Reset Message—Signaling (32)" section.

Table 10-30 Signaling (32) Details 

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 are 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)

Table 10-31 lists the details of the Signaling (33) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Release Message—Signaling (33)" section.

Table 10-31 Signaling (33) Details 

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 are 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)

Table 10-32 lists the details of the Signaling (34) warning event. To monitor and correct the cause of the event, refer to the "Unanswered Continuity Check Request Message—Signaling (34)" section.

Table 10-32 Signaling (34) Details 

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 are 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 (35)

Signaling (35) is not used.

Signaling (36)

Table 10-33 lists the details of the Signaling (36) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Trunk Locally Blocked—Signaling (36)" section.

Table 10-33 Signaling (36) Details 

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	No action required.

Signaling (37)

Signaling (37) is not used.

Signaling (38)

Signaling (38) is not used.

Signaling (39)

Signaling (39) is not used.

Signaling (40)

Table 10-34 lists the details of the Signaling (40) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Trunk Remotely Blocked—Signaling (40)" section.

Table 10-34 Signaling (40) Details 

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 an 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. You can manually recover from this condition locally by controlling the affected trunks to the unequipped (UEQP) state and back to the INS state.

Signaling (41)

Signaling (41) is not used.

Signaling (42)

Table 10-35 lists the details of the Signaling (42) informational event. For additional information, refer to the "Continuity Testing Message Received on the Specified Circuit Identification Code—Signaling (42)" section.

Table 10-35 Signaling (42) Details 

Description	Continuity Testing Message Received on the Specified Circuit Identification Code (COT Message Received on the Specified CIC)
Severity	Information
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)

Table 10-36 lists the details of the Signaling (43) informational event. For additional information, refer to the "Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code—Signaling (43)" section.

Table 10-36 Signaling (43) Details 

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	Information
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 an RSC message on the specified CIC.
Primary Action	No action required.

Signaling (44)

Table 10-37 lists the details of the Signaling (44) informational event. For additional information, refer to the "Continuity Recheck Is Performed on Specified Circuit Identification Code—Signaling (44)" section.

Table 10-37 Signaling (44) Details 

Description	Continuity Recheck is Performed on Specified Circuit Identification Code (Continuity Recheck is Performed on Specified CIC)
Severity	Information
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)

Table 10-38 lists the details of the Signaling (45) informational event. For additional information, refer to the "Circuit Is Unequipped on Remote Side—Signaling (45)" section.

Table 10-38 Signaling (45) Details 

Description	Circuit is Unequipped on Remote Side
Severity	Information
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 find out if an existing circuit was unequipped causing a status mismatch with the local end.

Signaling (46)

Table 10-39 lists the details of the Signaling (46) informational event. For additional information, refer to the "Specified Circuit Identification Code Is Invalid for the Operation—Signaling (46)" section.

Table 10-39 Signaling (46) Details 

Description	Specified Circuit Identification Code is Invalid for the Operation (Specified CIC is Invalid for the Operation)
Severity	Information
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.

Signaling (47)

Signaling (47) is not used.

Signaling (48)

Signaling (48) is not used.

Signaling (49)

Table 10-40 lists the details of the Signaling (49) informational event. For additional information, refer to the "A General Processing Error Encountered—Signaling (49)" section.

Table 10-40 Signaling (49) Details 

Description	A General Processing Error Encountered
Severity	Information
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 ensure proper operation.

Signaling (50)

Table 10-41 lists the details of the Signaling (50) informational event. For additional information, refer to the "Unexpected Message for the Call State Is Received: Clear Call—Signaling (50)" section.

Table 10-41 Signaling (50) Details 

Description	Unexpected Message for the Call State is Received: Clear Call
Severity	Information
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 ensure proper operation.

Signaling (51)

Table 10-42 lists the details of the Signaling (51) informational event. For additional information, refer to the "Set Trunk State as Remotely Unequipped—Signaling (51)" section.

Table 10-42 Signaling (51) Details 

Description	Set Trunk State as Remotely Unequipped
Severity	Information
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 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)

Table 10-43 lists the details of the Signaling (52) informational event. For additional information, refer to the "Set Trunk State as Not Remotely Blocked—Signaling (52)" section.

Table 10-43 Signaling (52) Details 

Description	Set Trunk State as Not Remotely Blocked
Severity	Information
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)

Table 10-44 lists the details of the Signaling (53) informational event. For additional information, refer to the "Set Trunk State as Remotely Blocked—Signaling (53)" section.

Table 10-44 Signaling (53) Details 

Description	Set Trunk State as Remotely Blocked
Severity	Information
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)

Table 10-45 lists the details of the Signaling (54) informational event. For additional information, refer to the "Circuit Validation Test Aborted—Signaling (54)" section.

Table 10-45 Signaling (54) Details 

Description	Circuit Validation Test Aborted
Severity	Information
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 failed a validation test due to an internal failure.
Primary Action	Verify that the SS7 signaling adapter process and the SS7 interface are operating normally.

Signaling (55)

Table 10-46 lists the details of the Signaling (55) informational event. For additional information, refer to the "Circuit Validation Successful—Signaling (55)" section.

Table 10-46 Signaling (55) Details 

Description	Circuit Validation Successful
Severity	Information
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.

Signaling (56)

Signaling (56) is not used.

Signaling (57)

Table 10-47 lists the details of the Signaling (57) informational event. For additional information, refer to the "Continuity Recheck Failed—Signaling (57)" section.

Table 10-47 Signaling (57) Details 

Description	Continuity Recheck Failed
Severity	Information
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 that the SS7 signaling adapter process and the SS7 interface are operating normally.

Signaling (58)

Table 10-48 lists the details of the Signaling (58) informational event. For additional information, refer to the "Continuity Recheck Successful—Signaling (58)" section.

Table 10-48 Signaling (58) Details 

Description	Continuity Recheck Successful
Severity	Information
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)

Table 10-49 lists the details of the Signaling (59) major alarm. 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.

Table 10-49 Signaling (59) Details 

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)

Table 10-50 lists the details of the Signaling (60) warning event. 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.

Table 10-50 Signaling (60) Details 

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 the service state.

Signaling (61)

Table 10-51 lists the details of the Signaling (61) informational event. For additional information, refer to the "Trunk Operational State Changed by Service Message—Signaling (61)" section.

Table 10-51 Signaling (61) Details 

Description	Trunk Operational State Changed by Service Message
Severity	Information
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 by 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)

Table 10-52 lists the details of the Signaling (62) informational event. For additional information, refer to the "Received Integrated Services Digital Network Restart Message—Signaling (62)" section.

Table 10-52 Signaling (62) Details 

Description	Received Integrated Services Digital Network Restart Message (Received ISDN Restart Message)
Severity	Information
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)

Table 10-53 lists the details of the Signaling (63) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway/Termination Faulty—Signaling (63)" section.

Table 10-53 Signaling (63) Details 

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, an unknown package type, an 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)

Table 10-54 lists the details of the Signaling (64) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Adapter Running Out of Shared Memory Pools—Signaling (64)" section.

Table 10-54 Signaling (64) Details 

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 storage for an inter-process communication (IPC) message due to a lack of resources.
Primary Action	Contact Cisco TAC for assistance.

Signaling (65)

Table 10-55 lists the details of the Signaling (65) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Adapter Running Out of Heap Memory—Signaling (65)" section.

Table 10-55 Signaling (65) Details 

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 storage for an IPC message from the heap due to a lack of resources.
Primary Action	Contact Cisco TAC for assistance.

Signaling (66)

Table 10-56 lists the details of the Signaling (66) major alarm. 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.

Table 10-56 Signaling (66) Details 

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 the log files to Cisco TAC for analysis and corrective action.

Signaling (67)

Signaling (67) is not used.

Signaling (68)

Signaling (68) is not used.

Signaling (69)

Table 10-57 lists the details of the Signaling (69) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Call Agent Is Not Up or Is Not Responding to the Feature Server—Signaling (69)" section.

Table 10-57 Signaling (69) Details 

Description	Call Agent is not Up or is not Responding to the Feature Server
Severity	Critical
Threshold	100
Throttle	0
Datawords	Configured CA Name—STRING [70]
Primary Cause	The Call Agent (CA) to Feature Server (FS) link has had a communication failure due to wrong system configuration; or the CA or FS is down.
Primary Action	Check the configuration related to the CA to FS communication link. Check the FS table entries and the CA entry.

Signaling (70)

Table 10-58 lists the details of the Signaling (70) warning event. 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.

Table 10-58 Signaling (70) Details 

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 that the provisioning of the backhaul port is correct at both the call agent and media gateway.

Signaling (71)

Table 10-59 lists the details of the Signaling (71) warning event. To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network Unable to Establish D-Channel—Signaling (71)" section.

Table 10-59 Signaling (71) Details 

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 1 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)

Table 10-60 lists the details of the Signaling (72) warning event. 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.

Table 10-60 Signaling (72) Details 

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 the connection between the private branch exchange (PBX) and the media gateway.
Primary Action	Resupply power to the media gateway and verify that the connection between the PBX and the media gateway is intact.

Signaling (73)

Table 10-61 lists the details of the Signaling (73) warning event. 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.

Table 10-61 Signaling (73) Details 

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)

Table 10-62 lists the details of the Signaling (74) warning event. 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.

Table 10-62 Signaling (74) Details 

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 service timer is set to an appropriate level.

Signaling (75)

Table 10-63 lists the details of the Signaling (75) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Stack Not Ready—Signaling (75)" section.

Table 10-63 Signaling (75) Details 

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 is not configured properly.
Primary Action	Check SS7 stack configuration.
Secondary Cause	SS7 stack is not up and functioning.
Secondary Action	Check SS7 stack status. Execute the platform start -i omni command to bring up SS7 stack.

Signaling (76)

Table 10-64 lists the details of the Signaling (76) informational event. For additional information, refer to the "Timeout on Remote Instance—Signaling (76)" section.

Table 10-64 Signaling (76) Details 

Description	Timeout on Remote Instance
Severity	Information
Threshold	100
Throttle	0
Datawords	Port Number—TWO_BYTES Hostname—STRING [64]
Primary Cause	The communication between the call agent and the remote instance is faulty.
Primary Action	No action needed.

Signaling (77)

Table 10-65 lists the details of the Signaling (77) informational event. For additional information, refer to the "Integrated Services Digital Network D-Channel Switchover for Not Facility Associated Signaling—Signaling (77)" section.

Table 10-65 Signaling (77) Details 

Description	Integrated Services Digital Network D-channel Switchover for Not Facility Associated Signaling (ISDN D-channel Switchover for NFAS)
Severity	Information
Threshold	100
Throttle	0
Datawords	Trunk Group ID—FOUR_BYTES Trunk Group Index—FOUR_BYTES
Primary Cause	The D-channels were manually switched through use of the command line interface (CLI).
Primary Action	Verify the operator action.
Secondary Cause	The active D-channel is lost.
Secondary Action	Verify that the gateway is operational and that the connection to the PBX is good.

Signaling (78)

Table 10-66 lists the details of the Signaling (78) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Single D-Channel Down for Not Facility Associated Signaling—Signaling (78)" section.

Table 10-66 Signaling (78) Details 

Description	Integrated Services Digital Network Single D-channel Down for Not 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 the primary rate interface (PRI) is down.
Primary Action	Check the gateway power and the gateway connection to the PBX.

Signaling (79)

Table 10-67 lists the details of the Signaling (79) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Trunking Gateway Unreachable—Signaling (79)" section.

Table 10-67 Signaling (79) Details 

Description	Trunking 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	The Trunking Gateway is not responding to keep-alive Audit Endpoint messages.
Primary Action	Check the IP connectivity status between Cisco BTS 10200 Call Agent and the Trunking Gateway.

Signaling (80)

Table 10-68 lists the details of the Signaling (80) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Out of Bounds, Memory/Socket Error—Signaling (80)" section.

Table 10-68 Signaling (80) Details 

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	Increase the random access memory (RAM) and contact Cisco TAC.
Secondary Cause	Out of IPC pool memory.
Secondary Action	Resize the IPC pool size in the platform configuration file.
Ternary Cause	A socket error has occurred. An inappropriate or already bound socket is in use.
Ternary Action	Check the UDP port supplied with the media gateway adapter (MGA) command-line for validity and prior use.

Signaling (81)

Table 10-69 lists the details of the Signaling (81) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Heap Memory—Signaling (81)" section.

Table 10-69 Signaling (81) Details 

Description	Insufficient Heap Memory
Severity	Critical
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32]
Primary Cause	Issued when the H.323 Protocol (H.323) signaling adapter is unable to allocate memory from the system.
Primary Action	Contact Cisco TAC for assistance.

Signaling (82)

Table 10-70 lists the details of the Signaling (82) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Shared Memory Pools—Signaling (82)" section.

Table 10-70 Signaling (82) Details 

Description	Insufficient Shared Memory Pools
Severity	Critical
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32]
Primary Cause	Issued when the H.323 signaling adapter was unable to allocate storage.
Primary Action	Contact Cisco TAC for corrective action.

Signaling (83)

Table 10-71 lists the details of the Signaling (83) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Error While Binding to Socket—Signaling (83)" section.

Table 10-71 Signaling (83) Details 

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 the system was binding to a socket.
Primary Action	Contact Cisco TAC.

Signaling (84)

Table 10-72 lists the details of the Signaling (84) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Reached Maximum Socket Limit—Signaling (84)" section.

Table 10-72 Signaling (84) Details 

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 the platform.cfg file is wrong.
Primary Action	Reconfigure the platform.cfg file and restart the H3A process.

Signaling (85)

Table 10-73 lists the details of the Signaling (85) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Initialization Failure—Signaling (85)" section.

Table 10-73 Signaling (85) Details 

Description	Initialization Failure
Severity	Critical
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32] Reason—STRING [128]
Primary Cause	A process initialization failure has occurred.
Primary Action	Check Dataword 2 (Reason) for the failure cause and take action accordingly.

Signaling (86)

Table 10-74 lists the details of the Signaling (86) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Remote H.323 Gateway Is Not Reachable—Signaling (86)" section.

Table 10-74 Signaling (86) Details 

Description	Remote H.323 Gateway is not Reachable
Severity	Major
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32] Remote GW TSAP Addr—STRING [32]
Primary Cause	A loss of communication with a remote gateway has occurred.
Primary Action	Perform the standard connectivity tests—both the physical checks and the IP tests. Also, ensure that the gateway is not out of service.

Signaling (87)

Table 10-75 lists the details of the Signaling (87) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "H.323 Message Parsing Error—Signaling (87)" section.

Table 10-75 Signaling (87) Details 

Description	H.323 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 H.323 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 its content or contact Cisco TAC.

Signaling (88)

Table 10-76 lists the details of the Signaling (88) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "H.323 Message Encoding Error—Signaling (88)" section.

Table 10-76 Signaling (88) Details 

Description	H.323 Message Encoding Error
Severity	Major
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32] Reason—STRING [128]
Primary Cause	Unable to encode an H.323 message for sending.
Primary Action	This is indicative of a software bug. Contact Cisco TAC.

Signaling (89)

Table 10-77 lists the details of the Signaling (89) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Gatekeeper not Available/Reachable—Signaling (89)" section.

Table 10-77 Signaling (89) Details 

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	The gatekeeper is not available or is unreachable.
Primary Action	Check network connectivity. Check to ensure that the gatekeeper (GK) is reachable by trying to ping GK IP address. If the GK is reachable, check to ensure that the GK is configured up.

Signaling (90)

Table 10-78 lists the details of the Signaling (90) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Alternate Gatekeeper Is Not Responding—Signaling (90)" section.

Table 10-78 Signaling (90) Details 

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	The alternate gatekeeper is not responding.
Primary Action	Check network connectivity. Check to ensure that the alternate GK is reachable by trying to ping the alternate GK IP address. If the GK is reachable, check to ensure that the alternate GK is configured up.

Signaling (91)

Table 10-79 lists the details of the Signaling (91) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Endpoint Security Violation—Signaling (91)" section.

Table 10-79 Signaling (91) Details 

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 H.323 security violation has occurred.
Primary Action	The password on the Cisco BTS 10200 and/or the gatekeeper is wrong—the H.323 gateway (H.323GW) table may not be provisioned properly or there is a time synchronization problem between the Cisco BTS 10200 and/or gatekeeper and the Network Time Protocol (NTP) server. Ensure that both the Cisco BTS 10200 and the gatekeeper are pointing to the same NTP server.

Signaling (92)

Table 10-80 lists the details of the Signaling (92) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Invalid Call Identifier—Signaling (92)" section.

Table 10-80 Signaling (92) Details 

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	There is a software problem on the Cisco BTS 10200 or on an endpoint. Contact Cisco TAC.

Signaling (93)

Table 10-81 lists the details of the Signaling (93) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Invalid Call Reference Value—Signaling (93)" section.

Table 10-81 Signaling (93) Details 

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	There is a software problem on the Cisco BTS 10200 or on an endpoint. Contact Cisco TAC.

Signaling (94)

Table 10-82 lists the details of the Signaling (94) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Invalid Conference Identifier—Signaling (94)" section.

Table 10-82 Signaling (94) Details 

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	There is a software problem on the Cisco BTS 10200 or on an endpoint. Contact Cisco TAC.

Signaling (95)

Table 10-83 lists the details of the Signaling (95) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Invalid Message from the Network—Signaling (95)" section.

Table 10-83 Signaling (95) Details 

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	An unsupported or invalid message type received from network.
Primary Action	Contact Cisco TAC.

Signaling (96)

Table 10-84 lists the details of the Signaling (96) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Internal Call Processing Error—Signaling (96)" section.

Table 10-84 Signaling (96) Details 

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	Contact Cisco TAC.

Signaling (97)

Table 10-85 lists the details of the Signaling (97) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Information to Complete Call—Signaling (97)" section.

Table 10-85 Signaling (97) Details 

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	Contact Cisco TAC.

Signaling (98)

Table 10-86 lists the details of the Signaling (98) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "H.323 Protocol Inconsistencies—Signaling (98)" section.

Table 10-86 Signaling (98) Details 

Description	H.323 Protocol Inconsistencies
Severity	Minor
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32] Call ID—EIGHT_BYTES Reason—STRING [128]
Primary Cause	The H.323 endpoint and the Cisco BTS 10200 are running different protocol versions.
Primary Action	This is only an issue where the endpoint is running a higher version of the H.323 protocol than the Cisco BTS 10200. Contact Cisco TAC.

Signaling (99)

Table 10-87 lists the details of the Signaling (99) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Abnormal Call Clearing—Signaling (99)" section.

Table 10-87 Signaling (99) Details 

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	Contact Cisco TAC.

Signaling (100)

Table 10-88 lists the details of the Signaling (100) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Codec Negotiation Failed—Signaling (100)" section.

Table 10-88 Signaling (100) Details 

Description	Codec Negotiation Failed
Severity	Minor
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32] Call ID—EIGHT_BYTES Reason—STRING [128]
Primary Cause	The codec negotiation has failed.
Primary Action	Find a compatible set of codec settings for both sides, reprovision the endpoints of the call, and try the call again.

Signaling (101)

Table 10-89 lists the details of the Signaling (101) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Per Call Security Violation—Signaling (101)" section.

Table 10-89 Signaling (101) Details 

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)

Table 10-90 lists the details of the Signaling (102) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "H.323 Network Congested—Signaling (102)" section.

Table 10-90 Signaling (102) Details 

Description	H.323 Network Congested
Severity	Minor
Threshold	100
Throttle	0
Datawords	Gateway ID—STRING [32] Gatekeeper ID—STRING [32]
Primary Cause	The H.323 application process has depleted its 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.

Signaling (103)

Table 10-91 lists the details of the Signaling (103) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Aggregation Connection Down—Signaling (103)" section.

Table 10-91 Signaling (103) Details 

Description	Aggregation Connection Down (AGGR Connection Down)
Severity	Major
Threshold	100
Throttle	0
Datawords	AGGR-ID—STRING [16]
Primary Cause	The Transmission Control Protocol (TCP) connection is down.
Primary Action	Check the associated cabling and perform a ping to test the connectivity.

Signaling (104)

Table 10-92 lists the details of the Signaling (104) informational event. For additional information, refer to the "Aggregation Unable to Establish Connection—Signaling (104)" section.

Table 10-92 Signaling (104) Details 

Description	Aggregation Unable To Establish Connection (AGGR Unable To Establish Connection)
Severity	Information
Threshold	100
Throttle	0
Datawords	AGGR-ID—STRING [16]
Primary Cause	A TCP connection establish failure has occurred.
Primary Action	Check the IP connectivity of the call agent (CA) and the cable modem termination system (CMTS).

Signaling (105)

Table 10-93 lists the details of the Signaling (105) informational event. For additional information, refer to the "Aggregation Gate Set Failed—Signaling (105)" section.

Table 10-93 Signaling (105) Details 

Description	Aggregation Gate Set Failed (AGGR Gate Set Failed)
Severity	Information
Threshold	100
Throttle	0
Datawords	AGGR-ID—STRING [16] Error-Code—TWO_BYTES Sub-Error-Code—TWO_BYTES
Primary Cause	The gate set acknowledgement never came from the CMTS.
Primary Action	None

Signaling (106)

Table 10-94 lists the details of the Signaling (106) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Enhanced Subscriber Authentication Cisco BTS 10200 Delivery Function Connection Down—Signaling (106)" section.

Table 10-94 Signaling (106) Details 

Description	Enhanced Subscriber Authentication Cisco BTS 10200 Delivery Function Connection Down (ESA Cisco BTS 10200 DF Connection Down)
Severity	Minor
Threshold	100
Throttle	0
Primary Cause	The delivery function (DF) server is not responding.
Primary Action	Check the encryption key or the IP connectivity to the DF server.

Signaling (107)

Table 10-95 lists the details of the Signaling (107) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Logical Internet Protocol Addresses Not Mapped Correctly—Signaling (107)" section.

Table 10-95 Signaling (107) Details 

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	A contact name in the configuration file is not configured in the domain name system (DNS).
Primary Action	Verify that the name in the DNS matches the name in the platform.cfg and opticall.cfg files.
Secondary Cause	A contact could not be resolved to an IP address on the host.
Secondary Action	Verify that the DNS resolves to the IP addresses reserved for the process on the Cisco BTS 10200.
Ternary Cause	The IP address manager is not running.
Ternary Action	Verify that the Internet Protocol Manager (IPM) process is running and check for alarms from the IPM.
Subsequent Cause	A mis-configuration occurred during installation or manual changes were made after installation.
Subsequent Action	Contact Cisco TAC for support.

Signaling (108)

Table 10-96 lists the details of the Signaling (108) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Simplex Only Operational Mode—Signaling (108)" section.

Table 10-96 Signaling (108) Details 

Description	Simplex Only Operational Mode
Severity	Major
Threshold	30
Throttle	0
Datawords	Host Domain Name—STRING [128]
Primary Cause	The hostname parameter is specified in the platform.cfg file instead of being specified in the -contact parameter.
Primary Action	Check to see if the Cisco BTS 10200 is configured as a simplex system.

Signaling (109)

Table 10-97 lists the details of the Signaling (109) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Failure—Signaling (109)" section.

Table 10-97 Signaling (109) Details 

Description	Stream Control Transmission Protocol Association Failure (SCTP Association Failure)
Severity	Major
Threshold	100
Throttle	0
Datawords	SCTP Association ID—STRING [17]
Primary Cause	The Ethernet cables for the signaling gateway process (SGP) are unplugged or severed.
Primary Action	Plug Ethernet cables in or fix the severed connection.
Secondary Cause	SGP is not operational.
Secondary Action	Check the SGP alarms to determine why SGP is not operating properly.

Signaling (110)

Table 10-98 lists the details of the Signaling (110) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Group Is Out of Service—Signaling (110)" section.

Table 10-98 Signaling (110) Details 

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 the CA and the SGs are out-of-service.
Primary Action	Make sure all Ethernet connections on the CA and the SGs are plugged in. Also make sure all of the associated IP routers are operational.
Secondary Cause	The MTP3 user adapter (M3UA) layer is down between the CA and the SGs.
Secondary Action	Use the Cisco snooper application to determine why the M3UA layer is down.

Signaling (111)

Table 10-99 lists the details of the Signaling (111) major alarm. 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.

Table 10-99 Signaling (111) Details 

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	A single Ethernet connection on the CA or the SGP is unplugged or severed.
Primary Action	Plug in all of the Ethernet connections or repair if severed.
Secondary Cause	An SCTP communication problem—protocol timeout.
Secondary Action	Use the Cisco snooper application to determine why the SCTP association is degraded.

Signaling (112)

Table 10-100 lists the details of the Signaling (112) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Configuration Error—Signaling (112)" section.

Table 10-100 Signaling (112) Details 

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	The destination IP address is invalid.
Primary Action	Input a new destination IP address—see log for additional details.
Secondary Cause	The local IP address is invalid.
Secondary Action	Input new local IP address information.
Ternary Cause	The IP Routing table is not configured properly.
Ternary Action	Have the system administrator configure the IP Routing table.

Signaling (113)

Table 10-101 lists the details of the Signaling (113) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Failure—Signaling (113)" section.

Table 10-101 Signaling (113) Details 

Description	Signaling Gateway Failure
Severity	Major
Threshold	100
Throttle	0
Datawords	Signaling Gateway ID—STRING [17]
Primary Cause	All of the associated signaling gateway processes are out-of-service.
Primary Action	Determine why each of the associated SGP processes is out-of-service (see the SGP alarm definition).

Signaling (114)

Table 10-102 lists the details of the Signaling (114) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Process Is Out of Service—Signaling (114)" section.

Table 10-102 Signaling (114) Details 

Description	Signaling Gateway Process is Out-of-Service
Severity	Major
Threshold	100
Throttle	0
Datawords	Signaling Gateway—STRING [17]
Primary Cause	All of the SCTP associations between the SGP and the CA are out-of-service.
Primary Action	See the SCTP association alarm definition to determine how to rectify the problem.
Secondary Cause	The M3UA layer is down between the CA and the SGP.
Secondary Action	Use the Cisco snooper utility to determine why M3UA layer is down. Also see the log for additional information.

Signaling (115)

Table 10-103 lists the details of the Signaling (115) warning event. To monitor and correct the cause of the event, refer to the "Invalid Routing Context Received—Signaling (115)" section.

Table 10-103 Signaling (115) Details 

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	The routing context was configured improperly on the CA or the signaling gateway (SG).
Primary Action	Reconfigure the routing context on the CA or the SG so that it matches in both places.

Signaling (116)

Table 10-104 lists the details of the Signaling (116) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code User Part Unavailable—Signaling (116)" section.

Table 10-104 Signaling (116) Details 

Description	Destination Point Code User Part Unavailable (DPC User Part Unavailable)
Severity	Major
Threshold	100
Throttle	0
Datawords	DPC ID—STRING [17]
Primary Cause	An SGP sent a destination user part unavailable (DUPU) M3UA message to the CA indicating that a User Part is unavailable on a DPC.
Primary Action	Contact the SS7 Network Administrator to report the User Part Unavailable problem on the DPC so that communication can be restored.

Signaling (117)

Table 10-105 lists the details of the Signaling (117) minor alarm. 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.

Table 10-105 Signaling (117) Details 

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	The CIC is not provisioned
Primary Action	Provision the CIC.

Signaling (118)

Table 10-106 lists the details of the Signaling (118) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Circuit Verification Response Received With Failed Indication—Signaling (118)" section.

Table 10-106 Signaling (118) Details 

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	A CIC mismatch occurred.
Primary Action	Perform an internal test such as checking that the CIC is assigned to a circuit between the sending and the receiving switch.

Signaling (119)

Table 10-107 lists the details of the Signaling (119) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Adapter Process Faulty—Signaling (119)" section.

Table 10-107 Signaling (119) Details 

Description	Signaling System 7 Adapter Process Faulty (S7A Process Faulty)
Severity	Critical
Threshold	100
Throttle	0
Datawords	Reason—STRING [36]
Primary Cause	An OMNI or S7A exception has occurred.
Primary Action	Check the OMNI process. The S7A will restart itself if the S7A maximum number of restarts is not exceeded.

Signaling (120)

Table 10-108 lists the details of the Signaling (120) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Module/Signaling System 7 Adapter Faulty—Signaling (120)" section.

Table 10-108 Signaling (120) Details 

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	An OMNI failure has occurred.
Primary Action	Check the OMNI status; a failover will occur in a duplex configuration.

Signaling (121)

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

Table 10-109 Signaling (121) Details 

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 are received from any SG or SCTP. The associations are probably down.
Primary Action	Investigate any other alarms to see if SGs are down or the SCTP associations are down. Take corrective action according to those alarms.

Signaling (122)

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

Table 10-110 Signaling (122) Details 

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 are being received from any SG or SCTP. The associations are probably down.
Primary Action	Investigate any other alarms to see if the SGs are down or the SCTP associations are down. Take corrective action according to those alarms.

Signaling (123)

Signaling (123) is not used.

Signaling (124)

Table 10-111 lists the details of the Signaling (124) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Remote Subsystem is Out Of Service—Signaling (124)" section.

Table 10-111 Signaling (124) Details 

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	A link loss has occurred or the remote subsystem is out of service.
Primary Action	Check the links. Check the remote location, if possible.

Signaling (125)

Table 10-112 lists the details of the Signaling (125) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling Connection Control Part Routing Error—Signaling (125)" section.

Table 10-112 Signaling (125) Details 

Description	Signaling Connection Control Part Routing Error (SCCP Routing Error)
Severity	Major
Threshold	100
Throttle	0
Primary Cause	The signaling connection control part (SCCP) route is invalid or is not available.
Primary Action	Provision the right SCCP route.

Signaling (126)

Table 10-113 lists the details of the Signaling (126) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling Connection Control Part Binding Failure—Signaling (126)" section.

Table 10-113 Signaling (126) Details 

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	A Trillium stack binding failure has occurred.
Primary Action	Reinitialize the TCAP signaling adapter (TSA) process or remove the subsystem from the Element Management System (EMS) table and add it again.

Signaling (127)

Table 10-114 lists the details of the Signaling (127) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Transaction Capabilities Application Part Binding Failure—Signaling (127)" section.

Table 10-114 Signaling (127) Details 

Description	Transaction Capabilities Application Part Binding Failure (TCAP Binding Failure)
Severity	Major
Threshold	100
Throttle	0
Primary Cause	A Trillium stack binding failure has occurred.
Primary Action	Reinitialize the TSA process or remove the subsystem from the EMS table and add it again.

Signaling (128)

Signaling (128) is not used.

Signaling (129)

Signaling (129) is not used.

Signaling (130)

Signaling (130) is not used.

Signaling (131)

Signaling (131) is not used.

Signaling (132)

Table 10-115 lists the details of the Signaling (132) warning event. To monitor and correct the cause of the event, refer to the "Transaction Capabilities Application Part Reaches the Provisioned Resource Limit—Signaling (132)" section.

Table 10-115 Signaling (132) Details 

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	The Transaction Capabilities Application Part (TCAP) has run out of all the preconfigured dialogue IDs or invoke IDs.

Signaling (133)

Table 10-116 lists the details of the Signaling (133) informational event. For additional information, refer to the "Unable to Decode Generic Transport Descriptor Message—Signaling (133)" section.

Table 10-116 Signaling (133) Details 

Description	Unable to Decode Generic Transport Descriptor Message (Unable to Decode GTD Message)
Severity	Information
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)

Table 10-117 lists the details of the Signaling (134) informational event. For additional information, refer to the "Signaling System 7 Message Encoding Failure—Signaling (134)" section.

Table 10-117 Signaling (134) Details 

Description	Signaling System 7 Message Encoding Failure (SS7 Message Encoding Failure)
Severity	Information
Threshold	100
Throttle	0
Datawords	CIC Number—TWO_BYTES TGN-ID—FOUR_BYTES DPC—STRING [20] OPC—STRING [20]
Primary Cause	An error in the ISDN user part (ISUP) stack or in a signaling adapter interface (SAI) message has occurred.
Primary Action	Capture the SS7 trace of circuit for examination by support personnel and contact Cisco TAC.

Signaling (135)

Table 10-118 lists the details of the Signaling (135) informational event. For additional information, refer to the "Signaling System 7 Message Decoding Failure—Signaling (135)" section.

Table 10-118 Signaling (135) Details 

Description	Signaling System 7 Message Decoding Failure (SS7 Message Decoding Failure)
Severity	Information
Threshold	100
Throttle	0
Datawords	CIC Number—TWO_BYTES TGN-ID—FOUR_BYTES DPC—STRING [20] OPC—STRING [20]
Primary Cause	An error in the ISUP stack or in an SAI message has occurred.
Primary Action	Capture the SS7 trace of circuit for examination by support personnel and contact Cisco TAC.

Signaling (136)

Table 10-119 lists the details of the Signaling (136) informational event. For additional information, refer to the "Signaling System 7 Message Invalid Received—Signaling (136)" section.

Table 10-119 Signaling (136) Details 

Description	Signaling System 7 Message Invalid Received (SS7 Message Invalid Received)
Severity	Information
Threshold	100
Throttle	0
Datawords	CIC Number—TWO_BYTES TGN-ID—FOUR_BYTES DPC—STRING [20] OPC—STRING [20]
Primary Cause	An invalid message was received from the line in the ISUP stack.
Primary Action	Capture the SS7 trace of circuit for examination by support personnel and contact Cisco TAC.
Secondary Cause	An invalid message was received from the line in the ISUP stack.
Secondary Action	Verify that the signal switching point (SSP) sending the message to the CA is correctly configured.

Signaling (137)

Table 10-120 lists the details of the Signaling (137) informational event. For additional information, refer to the "Signaling System 7 Confusion Message Received—Signaling (137)" section.

Table 10-120 Signaling (137) Details 

Description	Signaling System 7 Confusion Message Received (SS7 Confusion Message Received)
Severity	Information
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 a parameter received was not recognized or understood.
Primary Action	Check the log for more information (including confusion (CFN) diagnostic output). Capture an SS7 trace of the affected circuits. If the diagnostic data indicates that messages or parameters that must be supported are being dropped, refer the captured data to Cisco TAC along with a description of the call scenario.

Signaling (138)

Table 10-121 lists the details of the Signaling (138) warning event. To monitor and correct the cause of the event, refer to the "Number of Open Session Initiation Protocol Connections Is Reaching Engineered Limit—Signaling (138)" section.

Table 10-121 Signaling (138) Details 

Description	Number of Open Session Initiation Protocol Connections is Reaching Engineered Limit (Number of Open SIP Connections is Reaching Engineered Limit)
Severity	Warning
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	A call failure has occurred or a feature is unavailable.
Primary Action	The system configuration and the 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. Please contact Cisco TAC.

Signaling (139)

Table 10-122 lists the details of the Signaling (139) informational event. For additional information, refer to the "Signaling System 7 Trunk was Found to be in Erroneous State—Signaling (139)" section.

Table 10-122 Signaling (139) Details 

Description	Signaling System 7 Trunk was Found to be in Erroneous State (SS7 Trunk was Found to be in Erroneous State)
Severity	Information
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	A discrepancy between the local and the remote trunk states has occurred.
Primary Action	Automatic corrective action is enforced when using American National Standards Institute (ANSI) ISUP.

Signaling (140)

Table 10-123 lists the details of the Signaling (140) informational event. For additional information, refer to the "Unanswered Information Message—Signaling (140)" section.

Table 10-123 Signaling (140) Details 

Description	Unanswered Information Message (Unanswered INF Message)
Severity	Information
Threshold	100
Throttle	0
Datawords	CIC—TWO_BYTES TGN-ID—FOUR_BYTES DPC—STRING [20] OPC—STRING [20]
Primary Cause	The far-end switch is not responding to an information (INF) message with an information request (INR) message.
Primary Action	Verify that the far-end switch can correctly respond to an INF message.

Signaling (141)

Table 10-124 lists the details of the Signaling (141) warning event. To monitor and correct the cause of the event, refer to the "Address Not Resolved by Domain Name System Server—Signaling (141)" section.

Table 10-124 Signaling (141) Details 

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] Reason—STRING [64]
Primary Cause	The transport service access point (TSAP) address or hostname is not defined in the DNS.
Primary Action	Add an entry for the TSAP address to the DNS server, or fix the Cisco BTS 10200 provisioning.

Signaling (142)

Table 10-125 lists the details of the Signaling (142) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Trunk Operationally Out-of-Service—Signaling (142)" section.

Table 10-125 Signaling (142) Details 

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 [21] Trunk SIP Element ID—STRING [65] Trunk Server Group ID—STRING [65]
Primary Cause	Issued when the Cisco BTS 10200 is unable to communicate with a remote SIP party (Call-Agent or Proxy) over a SIP or a SIP-T trunk.
Primary Action	Verify that the DNS resolution exists, if TSAP address of the remote entity is a domain name. Verify that 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, verify that the network connection is operational.
Secondary Cause	The 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 that the SIP application is running on the remote host and is listening on the port specified in the TSAP address.

Signaling (143)

Table 10-126 lists the details of the Signaling (143) minor alarm. 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.

Table 10-126 Signaling (143) Details 

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	A hardware problem has occurred.
Primary Action	Check the link interfaces.

Signaling (144)

Table 10-127 lists the details of the Signaling (144) critical alarm. 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.

Table 10-127 Signaling (144) Details 

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	A hardware problem has occurred.
Primary Action	Check the link interfaces.

Signaling (145)

Table 10-128 lists the details of the Signaling (145) minor alarm. 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.

Table 10-128 Signaling (145) Details 

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	A hardware problem has occurred.
Primary Action	Check the link interfaces.

Signaling (146)

Table 10-129 lists the details of the Signaling (146) warning event. To monitor and correct the cause of the event, refer to the "All Retransmission Attempts of Session Initiation Protocol Request or Response Failed—Signaling (146)" section.

Table 10-129 Signaling (146) Details 

Description	All Retransmission Attempts of Session Initiation Protocol Request or Response Failed (All Retransmission Attempts of SIP Request or Response Failed)
Severity	Warning
Threshold	100
Throttle	0
Datawords	SIP Request Type—STRING [15] Sender IP—STRING [20]
Primary Cause	SIP request: All retransmission attempts for a SIP request failed for the DNS or the IP address of request uniform resource identifier (URI). SIP response: All retransmission attempts for a SIP response failed for the received socket IP address of the request and the DNS (or the IP address) listed in the header.
Primary Action	Ensure that if the DNS server is up and running for the host name resolution and ensure that the DNS server is provisioned properly to resolve the correct order of the IP addresses. Ensure that the previous hop network component is alive and in a healthy state.

Signaling (147)

Table 10-130 lists the details of the Signaling (147) warning event. To monitor and correct the cause of the event, refer to the "Domain Name System Service Addresses Exhausted—Signaling (147)" section.

Table 10-130 Signaling (147) Details 

Description	Domain Name System Service Addresses Exhausted (DNS SRV Addresses Exhausted)
Severity	Warning
Threshold	100
Throttle	0
Datawords	SRV Hostname—STRING [256]
Primary Cause	The DNS service (SRV) hostname resolution to the IP addresses is exhausted.
Primary Action	Add an entry to the SRV in the DNS server. Fix the Cisco BTS 10200 provisioning.

Signaling (148)

Signaling (148) is not used.

Signaling (149)

Signaling (149) is not used.

Signaling (150)

Table 10-131 lists the details of the Signaling (150) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Congested—Signaling (150)" section.

Table 10-131 Signaling (150) Details 

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	The network is congested.
Primary Action	Clean off the network congestion caused by routing or switching issues.
Secondary Cause	The central processing unit (CPU) is throttled.
Secondary Action	You might need to upgrade to a more powerful platform or offload some traffic.

Signaling (151)

Table 10-132 lists the details of the Signaling (151) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Subscriber Line Faulty—Signaling (151)" section.

Table 10-132 Signaling (151) Details 

Description	Subscriber Line Faulty
Severity	Minor
Threshold	100
Throttle	0
Datawords	End Point /Termination - STRING [54] Media Gateway Type - STRING [54] Error Details - STRING [54]
Primary Cause	The residential gateway returned an error code in response to a command from the MGW.
Primary Action	Try controlling subscriber termination to OOS and back to INS using the Cisco BTS 10200 CLI command. If the problem persist after more calls, check the configuration in the Cisco BTS 10200 and the RGW. If the error codes returned by the MGW are harmless, the error codes can be suppressed by adding a new entry in the MGCP-RETCODE-ACTION table and by changing the EP-ACTION to reset/none.

Signaling (152)

Table 10-133 lists the details of the Signaling (151) informational event. For additional information, refer to the "Termination Transient Error Received—Signaling (152)" section.

Table 10-133 Signaling (152) Details 

Description	Termination Transient Error Received
Severity	Information
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 errors have occurred.
Primary Action	Contact Cisco TAC.

Signaling (153)

Table 10-134 lists the details of the Signaling (153) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Emergency Trunks Become Locally Blocked—Signaling (153)" section.

Table 10-134 Signaling (153) Details 

Description	Emergency Trunks Become Locally Blocked
Severity	Critical
Threshold	100
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 an emergency trunk (CAS, SS7, or ISDN) gets locally blocked.
Primary Action	No action is required.

Signaling (154)

Table 10-135 lists the details of the Signaling (154) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Emergency Trunks Become Remotely Blocked—Signaling (154)" section.

Table 10-135 Signaling (154) Details 

Description	Emergency Trunks Become Remotely Blocked
Severity	Critical
Threshold	100
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 an emergency trunk (CAS, SS7, or ISDN) gets remotely blocked.
Primary Action	No action is required.

Signaling (155)

Table 10-136 lists the details of the Signaling (155) informational event. For additional information, refer to the "Packet Cable Multi-Media Unsolicited Gate Delete—Signaling (155)" section.

Table 10-136 Signaling (155) Details 

Description	Packet Cable Multi-Media Unsolicited Gate Delete (PCMM Unsolicited Gate Delete)
Severity	Information
Threshold	100
Throttle	0
Datawords	AGGR-ID—STRING [16] Subscriber-IP-Address—STRING [32] Gate-Direction—STRING [16]
Primary Cause	An error condition has been encountered by the CMTS.
Primary Action	Check the alarms and warnings from the CMTS.

Signaling (156)

Table 10-137 lists the details of the Signaling (156) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Signaling Gateway Down—Signaling (156)" section.

Table 10-137 Signaling (156) Details 

Description	Integrated Services Digital Network Signaling Gateway Down (ISDN Signaling Gateway Down)
Severity	Major
Threshold	100
Throttle	0
Datawords	Media Gateway ID—STRING [16] Media Gateway TSAP Address—STRING [64]
Primary Cause	Cannot communicate to the ISDN gateway because it is down due to a failure in the gateway. The SCTP association might be down.
Primary Action	Check to see if the SCTP association is down due to an issue on the network.
Secondary Cause	The IUA layer might be down in the gateway.
Secondary Action	No action is needed. The IUA layer will be automatically recovered.

Signaling (157)

Table 10-138 lists the details of the Signaling (157) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Signaling Gateway Inactive—Signaling (157)" section.

Table 10-138 Signaling (157) Details 

Description	Integrated Services Digital Network Signaling Gateway Inactive (ISDN Signaling Gateway Inactive)
Severity	Major
Threshold	100
Throttle	0
Datawords	Media Gateway ID—STRING [16]
Primary Cause	A shutdown command was executed in the application server on the ISDN gateway side.
Primary Action	No action is needed. The ISDN gateway will be automatically recovered.

Signaling (158)

Table 10-139 lists the details of the Signaling (158) warning event. To monitor and correct the cause of the event, refer to the "Invalid Integrated Services Digital Network Interface Identification—Signaling (158)" section.

Table 10-139 Signaling (158) Details 

Description	Invalid Integrated Services Digital Network Interface Identification (Invalid ISDN Interface ID)
Severity	Warning
Threshold	100
Throttle	0
Datawords	Received Interface ID—TWO_BYTES
Primary Cause	The interface ID is not configured correctly on the ISDN gateway side.
Primary Action	Configure the D-channel correctly on the gateway side. The D-channel configuration on the call-agent side should match with that on the gateway side.

Signaling (159)

Table 10-140 lists the details of the Signaling (159) warning event. To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network User Adaptation Layer Cannot Go Active—Signaling (159)" section.

Table 10-140 Signaling (159) Details 

Description	Integrated Services Digital Network User Adaptation Layer Cannot Go Active (IUA Cannot Go Active)
Severity	Warning
Threshold	100
Throttle	0
Datawords	Not applicable.
Primary Cause	No active acknowledgement messages are being received from any signaling gateway. The ISDN signaling gateway or the SCTP associations are probably down.
Primary Action	Investigate other alarms to see if the signaling gateways are down or the SCTP associations are down. Take corrective action according to those alarms.

Signaling (160)

Table 10-141 lists the details of the Signaling (160) warning event. To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network User Adaptation Layer Cannot Go Standby—Signaling (160)" section.

Table 10-141 Signaling (160) Details 

Description	Integrated Services Digital Network User Adaptation Layer Cannot Go Standby (IUA Cannot Go Standby)
Severity	Warning
Threshold	100
Throttle	0
Datawords	Not applicable.
Primary Cause	No UP acknowledgement messages are being received from any signaling gateway. The ISDN signaling gateway or the SCTP associations are probably down.
Primary Action	Investigate other alarms to see if the signaling gateways are down or the SCTP associations are down. Take corrective action according to those alarms.

Signaling (161)

Table 10-142 lists the details of the Signaling (161) warning event. To monitor and correct the cause of the event, refer to the "Session Initiation Protocol Update Not Allowed for Operator Service Position System Calls—Signaling (161)" section.

Table 10-142 Signaling (161) Details 

Description	Session Initiation Protocol Update not Allowed for Operator Service Position System Calls (SIP Update not Allowed for OSPS Calls)
Severity	Warning
Threshold	100
Throttle	0
Datawords	Trunk Group Description—STRING [21] TSAP Address—STRING [65]
Primary Cause	The remote switch does not allow the Cisco BTS 10200 to send SIP UPDATE messages. The update message is mandatory in CMSS and is used exclusively by the Cisco BTS 10200 for operator service calls over SIP including BLV, emergency interrupt, and 911 ringback calls.
Primary Action	Upgrade or reprovision the remote switch so it can process incoming SIP update messages.

Signaling (162)

Table 10-143 lists the details of the Signaling (162) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Server Group Element Operationally Out of Service—Signaling (162)" section.

Table 10-143 Signaling (162) Details 

Description	Session Initiation Protocol Server Group Element Operationally Out of Service (SIP Server Group Element Operationally out of Service)
Severity	Critical
Threshold	100
Throttle	0
Datawords	Server Group Description—STRING [64] TSAP Address of the SIP-Element.—STRING [64]
Primary Cause	Issued when the Cisco BTS 10200 is unable to communicate with a remote SIP party (Call-Agent or Proxy) over a SIP server group element.
Primary Action	If the TSAP address of the remote entity is a domain name, verify that the DNS resolution exists. Verify that the remote entity is reachable by ICMP ping, using the TSAP address from the Event Report. If the same alarm is reported for other TSAP addresses on several softswitch trunk groups and/or server-group elements, verify that the network connection is operational.
Secondary Cause	The remote SIP party is not operational.
Secondary Action	If the ping is not successful, diagnose the issue that prevents the TSAP address from being reached. Verify that the SIP application is running on the remote host and listening on the port specified in the TSAP address.

Signaling (163)

Table 10-144 lists the details of the Signaling (163) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Routing Key Inactive—Signaling (163)" section.

Table 10-144 Signaling (163) Details 

Description	Routing Key Inactive
Severity	Major
Threshold	100
Throttle	0
Datawords	Routing Key ID—STRING [17] Routing Context—STRING [17] Signaling Gateway ID—STRING [17]
Primary Cause	Inactive ACK messages were received from a Signaling Gateway. The SGs or the SCTP associations are probably down.
Primary Action	Investigate other alarms to see if the SGs are down or the SCTP associations are down. Take corrective action according to those alarms. Also check the AS status for the routing context on ITP.

Signaling (164)

Table 10-145 lists the details of the Signaling (164) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Traffic Mode Mismatch—Signaling (164)" section.

Table 10-145 Signaling (164) Details 

Description	Signaling Gateway Traffic Mode Mismatch
Severity	Major
Threshold	100
Throttle	0
Datawords	Signaling Gateway ID—STRING [17] Signaling Gateway Process ID—STRING [17]
Primary Cause	The traffic mode does not match on the Cisco BTS 10200 and the Signaling Gateway.
Primary Action	Verify the AS traffic-mode configuration in the Signaling Gateway. Check that the SG internal redundancy mode for the traffic-mode setting has been set correctly in the Cisco BTS 10200.

Signaling (165)

Table 10-146 lists the details of the Signaling (165) warning event. To monitor and correct the cause of the event, refer to the "No Session Initiation Protocol P-DCS Billing Information Header Received—Signaling (165)" section.

Table 10-146 Signaling (165) Details 

Description	No Session Initiation Protocol P-DCS Billing Information Header Received (No SIP P-DCS Billing Info Hdr Rcvd)
Severity	Warning
Threshold	10
Throttle	0
Datawords	Trunk Group ID—STRING [21] TSAP Address—STRING [65]
Primary Cause	The originating switch is not provisioned to add the P-DCS Billing Information header to outgoing SIP requests and responses.
Primary Action	Provision the originating switch to add the P-DCS Billing Information header to outgoing messages.
Secondary Cause	The header could have been stripped off by an intermediate proxy.
Secondary Action	Determine if the header has been stripped off by an intermediate proxy and, if it has, configure for corrective action if so.
Ternary Cause	There was a SIP message encode error at the sending switch.
Ternary Action	Determine if a SIP message encode error occurred at the sending switch and if so, call the technical assistance center to determine a fix for the problem.

Signaling (166)

Table 10-147 lists the details of the Signaling (166) warning event. To monitor and correct the cause of the event, refer to the "No Routing Keys Are Active—Signaling (166)" section.

Table 10-147 Signaling (166) Details 

Description	No Routing Keys are Active
Severity	Warning
Threshold	0
Throttle	0
Primary Cause	Routing keys are not set to the active state.
Primary Action	Set the routing keys to the active state.
Secondary Cause	The ITP provisioning is incorrect.
Secondary Action	Check the ITP provisioning.

Signaling (167)

Table 10-148 lists the details of the Signaling (167) warning event. To monitor and correct the cause of the event, refer to the "No Signaling Gateways Are Active—Signaling (167)" section.

Table 10-148 Signaling (167) Details 

Description	No Signaling Gateways are Active
Severity	Warning
Threshold	0
Throttle	0
Primary Cause	A communication problem between the ITP and the Cisco BTS 10200 has occurred.
Primary Action	Check the communication path between the Cisco BTS 10200 and the ITP.

Signaling (168)

Table 10-149 lists the details of the Signaling (168) warning event. To monitor and correct the cause of the event, refer to the "A Session Initiation Protocol Server Group Has No Child Elements Provisioned—Signaling (168)" section.

Table 10-149 Signaling (168) Details 

Description	A Session Initiation Protocol Server Group has no Child Elements Provisioned (A SIP Server Group has no Child Elements Provisioned)
Severity	Warning
Threshold	100
Throttle	0
Datawords	Server Group ID—STRING [64]
Primary Cause	Issued when a SIP Server Group is provisioned as in-service but has no child elements provisioned.
Primary Action	This server group is considered administratively out of service. If that is acceptable, no action is required. If the group was expected to be workable, place the server group back out of service, resolve the provisioning problem, and place the group back in service.

Signaling (169)

Table 10-150 lists the details of the Signaling (169) informational event. For additional information, refer to the "Session Initiation Protocol Element Provisioned With Service Enabled Is Internally Disabled—Signaling (169)" section.

Table 10-150 Signaling (169) Details 

Description	Session Initiation Protocol Element Provisioned with Service Enabled is Internally Disabled (SIP Element Provisioned with SRV Enabled is Internally Disabled)
Severity	Information
Threshold	100
Throttle	0
Datawords	SIP Element ID—STRING [64]
Primary Cause	A SIP element was provisioned with SRV enabled and is associated with at least one or more Server Groups.
Primary Action	The SRV flag will be assumed disabled. However, to resolve this informational message, provision the SRV flag disabled on the SIP element.

Signaling (170)

Table 10-151 lists the details of the Signaling (170) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Residential Gateway Endpoints Are Out of Service at the Gateway—Signaling (170)" section.

Table 10-151 Signaling (170) Details 

Description	Residential Gateway Endpoints are out of Service at the Gateway (Residential Gateway Endpoints are out of Service at the GW)
Severity	Minor
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	The residential gateway has been administratively taken OOS through use of the command at the GW.
Primary Action	Bring the residential gateway administratively into INS using the command at the GW.

Signaling (171)

Table 10-152 lists the details of the Signaling (171) minor alarm. To troubleshoot and correct the cause of the alarm, refer to the "Residential Gateway Unreachable—Signaling (171)" section.

Table 10-152 Signaling (171) Details 

Description	Residential Gateway Unreachable
Severity	Minor
Threshold	100
Throttle	0
Datawords	Entity Name—STRING [40] General Context—STRING [40] Specific Context—STRING [40] Failure Context—STRING [40]
Primary Cause	An MGCP signaling interop error has occurred with the residential media gateway.
Primary Action	Check the IP connectivity status between Cisco BTS 10200 call agent and the trunking gateway. Check to see if the residential gateway is not physically connected, but controlled INS at the Cisco BTS 10200.

Signaling (172)

Table 10-153 lists the details of the Signaling (172) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Multimedia Terminal Adapter Effective-Aggr-Id Becomes Unavailable Due to Its IP Address—Signaling (172)" section.

Table 10-153 Signaling (172) Details 

Description	Multimedia Terminal Adapter Effective-Aggr-Id Becomes Unavailable Due to its IP Address (MTA Effective-Aggr-Id Becomes Unavailable Due to its IP Address)
Severity	Major
Threshold	100
Throttle	0
Datawords	MTA IP Address—STRING [64]
Primary Cause	The MTA has been moved to a new subnet which is not provisioned, or provisioned with the aggr-id=null.
Primary Action	Provision the subnet aggr-id for the MTA.

Signaling (173)

Table 10-154 lists the details of the Signaling (173) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "ENUM Server Domain Cannot be Resolved Into Any IP Address —Signaling (173)" section.

Table 10-154 Signaling (173) Details 

Description	ENUM Server Domain Cannot be Resolved into Any IP Address
Severity	Critical
Threshold	100
Throttle	0
Datawords	ENUM Server Domain - STRING [128] ENUM Profile ID - STRING [64]
Primary Cause	Misconfiguration in the DNS.
Primary Action	Fix the configuration in the DNS according to the documentation.

Signaling (174)

Table 10-155 lists the details of the Signaling (174) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "ENUM Server Unavailable—Signaling (174)" section.

Table 10-155 Signaling (174) Details 

Description	ENUM Server Unavailable
Severity	Critical
Threshold	100
Throttle	0
Datawords	ENUM Server IP Address - STRING [16] ENUM Server Farm Name - STRING [128] ENUM Profile ID - STRING [64]
Primary Cause	A network or server problem has occurred.
Primary Action	Fix the network or server problem.

Signaling (175)

Table 10-156 lists the details of the Signaling (175) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "ENUM Server Farm Unavailable—Signaling (175)" section.

Table 10-156 Signaling (175) Details 

Description	ENUM Server Farm Unavailable
Severity	Critical
Threshold	100
Throttle	0
Datawords	ENUM Server Farm Name - STRING [128] ENUM Profile ID - STRING [64]
Primary Cause	A network or server problem has occurred.
Primary Action	Fix the network or server problem.

Signaling (176)

Table 10-157 lists the details of the Signaling (176) critical alarm. To troubleshoot and correct the cause of the alarm, refer to the "No Resources Available to Launch ENUM Query—Signaling (176)" section.

Table 10-157 Signaling (176) Details 

Description	No Resources Available to Launch ENUM Query
Severity	Critical
Threshold	100
Throttle	0
Datawords
Primary Cause	Internal or network congestion or slow server response has occurred.
Primary Action	Fix the network congestion or improve the server response.

Signaling (177)

Table 10-158 lists the details of the Signaling (177) warning event. To monitor and correct the cause of the event, refer to the "ISDN Unable to Restore D-Channel Into In-Service Active State—Signaling (177)" section.

Table 10-158 Signaling (177) Details 

Description	ISDN Unable to Restore D-Channel into In-Service Active State
Severity	Warning
Threshold	100
Throttle	0
Datawords	D-Chan ID - STRING [20] D-Chan Index - FOUR_BYTES D-Chan Type - STRING [10]
Primary Cause	The Cisco BTS 10200 does not receive the Service Ack from the remote end in response to Service message to make the D-Channel active.
Primary Action	Verify that the NFAS provisioning at the PBX/media gateway is correct.

Signaling (178)

Table 10-159 lists the details of the Signaling (178) informational event. For additional information, refer to the "Possible Overlap Dialing Misconfiguration—Signaling (178)" section.

Table 10-159 Signaling (178) Details 

Description	Possible Overlap Dialing Misconfiguration
Severity	Information
Threshold	100
Throttle	0
Datawords	TGN-ID - FOUR_BYTES DIALED-DIGIT - STRING [20]
Primary Cause	The Cisco BTS 10200 sent out an invite with an overlap flag, and has received one or more additional digits to be forwarded. However, the call attempt fails while the Cisco BTS 10200 is still waiting to send out the first additional digit. A possible cause is a misconfiguration of the Overlap Dialing feature between the local and peer switch.
Primary Action	Make sure that the peer switch is configured to support the Overlap Dialing feature. Check that the feature is enabled and that the dial-plan is configured correctly. Also make sure that the Destination/Route/Trunk group on the peer switch is marked to support the Overlap Sending feature.

Signaling (179)

Table 10-160 lists the details of the Signaling (179) major alarm. To troubleshoot and correct the cause of the alarm, refer to the "Trunk Group Registration Expired—Signaling (179)" section.

Table 10-160 Signaling (179) Details 

Description	Trunk Group Registration Expired
Severity	Major
Threshold	100
Throttle	0
Datawords	TGN-ID - FOUR_BYTES SIP Reg Contact - STRING [256] Reg Expiry Time - STRING [32]
Primary Cause	The trunk group did not register in time before the contact expiry.
Primary Action	The receipt of a subsequent registration will clear the alarm.

Monitoring Signaling Events

This section provides the information you need for monitoring and correcting signaling events. Table 10-161 lists all of the signaling events in numerical order and provides cross-references to each subsection.

---

Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page l for detailed instructions on contacting Cisco TAC and opening a service request.

---

Table 10-161 Cisco BTS 10200 Signaling Events 

Event Type	Event Name	Event Severity
Signaling (1)	Test Report—Signaling (1)	Information
Signaling (4)	Invalid Message Received—Signaling (4)	Warning
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—Signa