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: December 11, 2008, OL-15636-05

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