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)
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)
Trunking Gateway Endpoints are out of Service at the Gateway—Signaling (68)
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 Non-Facility Associated Signaling—Signaling (77)
Integrated Services Digital Network Single D-channel Down for Non-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 H323 Gateway is not Reachable—Signaling (86)
H323 Message Parsing Error—Signaling (87)
H323 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)
H323 Protocol Inconsistencies—Signaling (98)
Abnormal Call Clearing—Signaling (99)
Codec Negotiation Failed—Signaling (100)
Per Call Security Violation—Signaling (101)
H323 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 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) (SS7)
Unanswered Information Message—Signaling (140)
Address not Resolved by Domain Name System Server—Signaling (141)
Session Initiation Protocol Trunk Operationally Out-of-Service—Signaling (142)
Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down—Signaling (143)
All Internet Interface Links to Signaling System 7 Signaling Gateway are Down—Signaling (144)
One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down—Signaling (145)
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 can not Go Active—Signaling (159)
Integrated Services Digital Network User Adaptation Layer can not 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)
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)
Trunking Gateway Endpoints are out of Service at the Gateway—Signaling (68)
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 Non-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 H323 Gateway is not Reachable—Signaling (86)
H323 Message Parsing Error—Signaling (87)
H323 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)
H323 Protocol Inconsistencies—Signaling (98)
Abnormal Call Clearing—Signaling (99)
Codec Negotiation Failed—Signaling (100)
Per Call Security Violation—Signaling (101)
H323 Network Congested—Signaling (102)
Aggregation Connection Down—Signaling (103)
Enhanced Subscriber Authentication 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)
Signaling Troubleshooting
Revised: March 5, 2009, OL-8723-18
Introduction
This chapter provides the information needed to monitor and troubleshoot signaling events and alarms. This chapter is divided into the following sections:
•
Signaling Events and Alarms—Provides a brief overview of each signaling event and alarm.
•Monitoring Signaling Events—Provides the information needed to monitor and correct the Signaling events.
•Troubleshooting Signaling Alarms—Provides the information needed to troubleshoot and correct 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 BTS 10200 in numerical order. Table 10-1 lists all of the signaling events and alarms by severity.
Note Click the signaling message number in Table 10-1 to display information about the event or alarm.
SIGNALING (1)
For additional information, refer to the "Test Report—Signaling (1)" section.
DESCRIPTION
|
Test Report
|
SEVERITY
|
Information (INFO)
|
THRESHOLD
|
10000
|
THROTTLE
|
0
|
SIGNALING (2)
SIGNALING (2) is not used.
SIGNALING (3)
SIGNALING (3) is not used.
SIGNALING (4)
To monitor and correct the cause of the event, refer to the "Invalid Message Received—Signaling (4)" section.
DESCRIPTION
|
Invalid Message Received
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Endpoint Name-STRING [40]
Message Type-STRING [40]
|
PRIMARY
CAUSE
|
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)
To monitor and correct the cause of the event, refer to the "Database Module Function Call Failure—Signaling (6)" section.
DESCRIPTION
|
Database Module Function Call Failure
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Endpoint Name-STRING [40]
Return Code-FOUR_BYTES
Function Name-STRING [64]
Calling Function-STRING [64]
Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
A signaling adapter has detected an error while accessing a database interface.
|
PRIMARY
ACTION
|
If the database that the adapter attempted to access is not available, restart the associated process.
|
SECONDARY
ACTION
|
If an incompatible versions of the signaling adapter process and the database processes are present on the system, correct the error and restart the processes.
|
SIGNALING (7)
To troubleshoot and correct the cause of the alarm, refer to the "Socket Failure—Signaling (7)" section.
DESCRIPTION
|
Socket Failure
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Reason Text-STRING [30]
|
PRIMARY
CAUSE
|
Issued when there is a failure in creating or binding to the User Datagram Protocol (UDP) socket.
|
PRIMARY
ACTION
|
Verify 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 Cisco Support. (Contact Cisco Technical Assistance Center (TAC).)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (8)
To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Message Receive Failure—Signaling (8)" section.
DESCRIPTION
|
Session Initiation Protocol Message Receive Failure (SIP Message Receive Failure)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Reason Text-STRING [50]
|
PRIMARY
CAUSE
|
Operating system level network errors 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.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (9)
To troubleshoot and correct the cause of the alarm, refer to the "Timeout on Internet Protocol Address—Signaling (9)" section.
DESCRIPTION
|
Timeout on Internet Protocol Address (Timeout on IP Address)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
MGW/Term Name-STRING [80]
Gateway Type-STRING [32]
Possible Cause-STRING [32]
|
PRIMARY
CAUSE
|
Issued when opticall is unable to communicate with a gateway.
|
PRIMARY
ACTION
|
Verify that the gateway is both configured for service and that it has been set in service.
|
SECONDARY
ACTION
|
Attempt to ping the gateway using the Internet Protocol (IP) address from the event report. If the ping is not successful, then diagnose the issue that prevents the address from being reached.
|
TERNARY
ACTION
|
Use the status media gateway (MGW) identification (ID) = xxx, where xxx is the IP address given in the event report. If the status is not in service (INS), then use the control mgw command to put it in service.
|
SIGNALING (10)
To troubleshoot and correct the cause of the alarm, refer to the "Failed to Send Complete Session Initiation Protocol Message—Signaling (10)" section.
DESCRIPTION
|
Failed to Send Complete Session Initiation Protocol Message (Failed to Send Complete SIP Message)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Destination Address-STRING [64]
|
PRIMARY
CAUSE
|
Notifies the user that the Session Initiation Protocol (SIP) stack failed to send an SIP message due to it exceeding the maximum length of a UDP packet.
|
PRIMARY
ACTION
|
If encountered in normal network operations, the message should be captured on passive testing equipment and sent to Cisco TAC for evaluation.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (11)
To troubleshoot and correct the cause of the alarm, refer to the "Failed to Allocate Session Initiation Protocol Control Block—Signaling (11)" section.
DESCRIPTION
|
Failed to Allocate Session Initiation Protocol Control Block (Failed to Allocate SIP Control Block)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Size-TWO_BYTES
Detail-STRING [80]
|
PRIMARY
CAUSE
|
Issued when there is not enough memory to allocate a SIP call control block.
|
PRIMARY
ACTION
|
Increase the SIP call control block (CCB) count specified in mem.cfg file.
|
SECONDARY
ACTION
|
Restart call agent for the changes to take effect.
|
SIGNALING (12)
To troubleshoot and correct the cause of the alarm, refer to the "Feature Server is not Up or is not Responding to Call Agent—Signaling (12)" section.
DESCRIPTION
|
Feature Server is not Up or is not Responding to Call Agent
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Domain Name of FS-STRING [65]
Feature Server ID-STRING [20]
|
PRIMARY
CAUSE
|
The feature server platform is down or is not operating properly.
|
PRIMARY
ACTION
|
Restart the applicable feature server.
|
SIGNALING (13)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Signaling Link Down—Signaling (13)" section.
DESCRIPTION
|
Signaling System 7 Signaling Link Down (SS7 Signaling Link Down)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link_Number-ONE_BYTE
Link_Name-STRING [25]
|
PRIMARY
CAUSE
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "Link is Remotely Inhibited—Signaling (14)" section.
DESCRIPTION
|
Link is Remotely Inhibited
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link-ONE_BYTE
Link Name-STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified Signaling System 7 (SS7) link is inhibited at the remote end.
|
PRIMARY
ACTION
|
Monitor the events at the network level for any related to the specified SS7 link. Restorative actions need to be taken on the remote end.
|
SIGNALING (15)
To troubleshoot and correct the cause of the alarm, refer to the "Link is Locally Inhibited—Signaling (15)" section.
DESCRIPTION
|
Link is Locally Inhibited
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No-ONE_BYTE
Link Name-STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link is inhibited at the local end.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter process is running and that the SS7 interface card(s) are in service.
|
SECONDARY
ACTION
|
If a component is found to be non-operational, restore it to service.
|
SIGNALING (16)
To troubleshoot and correct the cause of the alarm, refer to the "Link is Congested—Signaling (16)" section.
DESCRIPTION
|
Link is Congested
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No-ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link is experiencing congestion.
|
PRIMARY
ACTION
|
Monitor event reports at the network level to determine if the traffic load on the specified SS7 link is too high on the local end, or if the remote end is lagging in processing the traffic.
|
SECONDARY
ACTION
|
Verify that the SS7 link has not degraded in quality.
|
TERNARY
ACTION
|
Verify that the traffic load has not become unbalanced if multiple SS7 links are used.
|
SUBSEQUENT
ACTION
|
Verify that local SS7 signaling adapter process is running normally.
|
SIGNALING (17)
To troubleshoot and correct the cause of the alarm, refer to the "Link: Local Processor Outage—Signaling (17)" section.
DESCRIPTION
|
Link: Local Processor Outage
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No-ONE_BYTE
Link Name-STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link has experienced a processor outage.
|
PRIMARY
ACTION
|
Monitor the system for maintenance event reports associated with the signaling adapter or 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)
To troubleshoot and correct the cause of the alarm, refer to the "Link: Remote Processor Outage—Signaling (18)" section.
DESCRIPTION
|
Link: Remote Processor Outage
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No-ONE_BYTE
Link Name-STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link has experienced a processor outage.
|
PRIMARY
ACTION
|
Monitor the network level event reports for any events associated with the processing complex used by the specified SS7 link. Verify that the SS7 link is returned to service.
|
SIGNALING (19)
To troubleshoot and correct the cause of the alarm, refer to the "Link Set Inaccessible—Signaling (19)" section.
DESCRIPTION
|
Link Set Inaccessible
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link Set No-ONE_BYTE
Link Set Name-STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link set is inaccessible.
|
PRIMARY
ACTION
|
If the SS7 signaling adapter is not running normally and the associated call agent platform is not active, return them to service.
|
SIGNALING (20)
To troubleshoot and correct the cause of the alarm, refer to the "Link Set Congestion—Signaling (20)" section.
DESCRIPTION
|
Link Set Congestion
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link Set No-ONE_BYTE
Link Set Name-STRING [8]
Congestion Level-ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link set is experiencing congestion.
|
PRIMARY
ACTION
|
Monitor event reports at the network level to determine if the traffic load on the specified SS7 link set is too high on the local end, or if the remote end is lagging in processing the traffic.
|
SECONDARY
ACTION
|
Verify that the SS7 link set has not degraded in quality.
|
TERNARY
ACTION
|
Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used.
|
SUBSEQUENT
ACTION
|
Verify that local SS7 signaling adapter process is running normally.
|
SIGNALING (21)
To troubleshoot and correct the cause of the alarm, refer to the "Route Set Failure—Signaling (21)" section.
DESCRIPTION
|
Route Set Failure
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
200
|
THROTTLE
|
0
|
DATAWORDS
|
Route Set No-TWO_BYTES
Route Set Name-STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified route set has experienced a failure.
|
PRIMARY
ACTION
|
Verify that the processing complex supporting the route set is functional.
|
SECONDARY
ACTION
|
Monitor event reports at the network level to determine the failing component and to verify its restoral to service.
|
SIGNALING (22)
To troubleshoot and correct the cause of the alarm, refer to the "Route Set Congested—Signaling (22)" section.
DESCRIPTION
|
Route Set Congested
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Set No-TWO_BYTES
Route Set Name-STRING [8]
Congestion Level-ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified route set is experiencing congestion.
|
PRIMARY
ACTION
|
Monitor 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)
To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Unavailable—Signaling (23)" section.
DESCRIPTION
|
Destination Point Code Unavailable (DPC Unavailable)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
200
|
THROTTLE
|
0
|
DATAWORDS
|
DPC-STRING [12]
|
PRIMARY
CAUSE
|
Issued when the specified destination point code (DPC) is not available. This is usually caused by one of the following:
1) A failure in the affected DPC.
2) An unavailable route between the 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)
To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Congested—Signaling (24)" section.
DESCRIPTION
|
Destination Point Code Congested (DPC Congested)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
DPC-STRING [12]
DPC Type-ONE_BYTE
Congestion Level-ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified destination point code is congested.
|
PRIMARY
ACTION
|
Monitor 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)
To monitor and correct the cause of the event, refer to the "Unanswered Blocking Message—Signaling (25)" section.
DESCRIPTION
|
Unanswered Blocking Message (Unanswered BLO)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a blocking (BLO) message was not acknowledged before the timer 13 (T13) expired for the associated circuit identification code (CIC).
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
|
SECONDARY
ACTION
|
Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
|
TERNARY
ACTION
|
Verify that the T13 timer is set to an appropriate level.
|
SUBSEQUENT
ACTION
|
Verify that the SS7 link is not congested.
|
SIGNALING (26)
To monitor and correct the cause of the event, refer to the "Unanswered Unblocking Message—Signaling (26)" section.
DESCRIPTION
|
Unanswered Unblocking Message (Unanswered UBL)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a unblocking message (UBL) message was not acknowledged before the timer 15 (T15) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
|
SECONDARY
ACTION
|
Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
|
TERNARY
ACTION
|
Verify that the T13 timer is set to an appropriate level.
|
SUBSEQUENT
ACTION
|
Verify that the SS7 link is not congested.
|
SIGNALING (27)
To monitor and correct the cause of the event, refer to the "Unanswered Circuit Group Blocking Message—Signaling (27)" section.
DESCRIPTION
|
Unanswered Circuit Group Blocking Message (Unanswered CGB)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a circuit group blocking (CGB) message was not acknowledged before the timer 19 (T19) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
|
SECONDARY
ACTION
|
Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
|
TERNARY
ACTION
|
Verify that the T13 timer is set to an appropriate level.
|
SUBSEQUENT
ACTION
|
Verify that the SS7 link is not congested.
|
SIGNALING (28)
To monitor and correct the cause of the event, refer to the "Unanswered Circuit Group Unblocking Message—Signaling (28)" section.
DESCRIPTION
|
Unanswered Circuit Group Unblocking Message (Unanswered CGU)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a circuit group unblocking (CGU) message was not acknowledged before the timer 21 (T21) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally.
|
SECONDARY
ACTION
|
Verify that the call agent platform is active.
|
TERNARY
ACTION
|
Verify that the SS7 interface hardware is in service.
|
SUBSEQUENT
ACTION
|
Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.
|
SIGNALING (29)
To monitor and correct the cause of the event, refer to the "Unanswered Circuit Query Message—Signaling (29)" section.
DESCRIPTION
|
Unanswered Circuit Query Message (Unanswered CQM)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a circuit query message (CQM) message was not acknowledged before the timer 28 (T28) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally.
|
SECONDARY
ACTION
|
Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service.
|
TERNARY
ACTION
|
Verify that the associated SS7 signaling link is available.
|
SUBSEQUENT
ACTION
|
Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.
|
SIGNALING (30)
To monitor and correct the cause of the event, refer to the "Unanswered Circuit Validation Test Message—Signaling (30)" section.
DESCRIPTION
|
Unanswered Circuit Validation Test Message (Unanswered CVT)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a circuit validation test (CVT) message was not acknowledged before the Tcvt expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally.
|
SECONDARY
ACTION
|
Verify that the call agent platform is active.
|
TERNARY
ACTION
|
Verify that the SS7 interface hardware is in service.
|
SUBSEQUENT
ACTION
|
Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.
|
SIGNALING (31)
To monitor and correct the cause of the event, refer to the "Unanswered Reset Circuit Message—Signaling (31)" section.
DESCRIPTION
|
Unanswered Reset Circuit Message (Unanswered RSC)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a reset circuit (RSC) message was not acknowledged before the timer 17 (T17) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
|
SECONDARY
ACTION
|
Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
|
TERNARY
ACTION
|
Verify that the T13 timer is set to an appropriate level.
|
SUBSEQUENT
ACTION
|
Verify that the SS7 link is not congested.
|
SIGNALING (32)
To monitor and correct the cause of the event, refer to the "Unanswered Group Reset Message—Signaling (32)" section.
DESCRIPTION
|
Unanswered Group Reset Message (Unanswered GRS)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a group reset (GRS) message was not acknowledged before the timer 23 (T23) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally. Verify that the call agent platform is active.
|
SECONDARY
ACTION
|
Verify that the SS7 interface hardware is in service. Verify that the associated SS7 signaling link is available.
|
TERNARY
ACTION
|
Verify that the T13 timer is set to an appropriate level.
|
SUBSEQUENT
ACTION
|
Verify that the SS7 link is not congested.
|
SIGNALING (33)
To monitor and correct the cause of the event, refer to the "Unanswered Release Message—Signaling (33)" section.
DESCRIPTION
|
Unanswered Release Message (Unanswered REL)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a release (REL) message was not acknowledged before the timer 5 (T5) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally.
|
SECONDARY
ACTION
|
Verify that the call agent platform is active. Verify that the SS7 interface hardware is in service.
|
TERNARY
ACTION
|
Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level.
|
SUBSEQUENT
ACTION
|
Verify that the SS7 link is not congested.
|
SIGNALING (34)
To monitor and correct the cause of the event, refer to the "Unanswered Continuity Check Request Message—Signaling (34)" section.
DESCRIPTION
|
Unanswered Continuity Check Request Message (Unanswered CCR)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when an loop prevention acknowledgement (LPA) message was not acknowledged before the timer continuity check request (TCCR) expired for the associated CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter processes is running normally.
|
SECONDARY
ACTION
|
Verify that the call agent platform is active.
|
TERNARY
ACTION
|
Verify that the SS7 interface hardware is in service.
|
SUBSEQUENT
ACTION
|
Verify that the associated SS7 signaling link is available. Verify that the T13 timer is set to an appropriate level. Verify that the SS7 link is not congested.
|
SIGNALING (35)
SIGNALING (35) is not used.
SIGNALING (36)
To troubleshoot and correct the cause of the alarm, refer to the "Trunk Locally Blocked—Signaling (36)" section.
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)
To troubleshoot and correct the cause of the alarm, refer to the "Trunk Remotely Blocked—Signaling (40)" section.
DESCRIPTION
|
Trunk Remotely Blocked
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
500
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-STRING [40]
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
MGW-EP-NAME-STRING [64]
MGW-TSAP-ADDR-STRING [80]
|
PRIMARY
CAUSE
|
Issued when a BLO or CGB message was received on the specified CIC if it is SS7 trunk. Issued when a SERVICE OOS message is received for Integrated Services Digital Network (ISDN) trunks. Issued when Reverse Make Busy (RBZ) signal is received for channel-associated signaling (CAS) operator trunk.
|
PRIMARY
ACTION
|
No action required. Can manually recover from this condition locally by controlling the effected trunks to the unequipped (UEQP) state and back to the INS state.
|
SIGNALING (41)
SIGNALING (41) is not used.
SIGNALING (42)
For additional information, refer to the "Continuity Testing Message Received on the Specified Circuit Identification Code—Signaling (42)" section.
DESCRIPTION
|
Continuity Testing Message Received on the Specified Circuit Identification Code (COT Message Received on the Specified CIC)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a continuity testing (COT) message was received on the specified CIC.
|
PRIMARY
ACTION
|
No action required.
|
SIGNALING (43)
For additional information, refer to the "Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code—Signaling (43)" section.
DESCRIPTION
|
Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code (RLC Received in Response to RSC Message on the Specified CIC)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a release complete (RLC) message was received in response to a RSC message on the specified CIC.
|
PRIMARY
ACTION
|
No action required.
|
SIGNALING (44)
For additional information, refer to the "Continuity Recheck is Performed on Specified Circuit Identification Code—Signaling (44)" section.
DESCRIPTION
|
Continuity Recheck is Performed on Specified Circuit Identification Code (Continuity Recheck is Performed on Specified CIC)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a continuity recheck was performed on the specified CIC.
|
PRIMARY
ACTION
|
No action required.
|
SIGNALING (45)
For additional information, refer to the "Circuit is UNEQUIPPED on Remote Side—Signaling (45)" section.
DESCRIPTION
|
Circuit is UNEQUIPPED on Remote Side
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when an unequipped circuit has been detected on the remote side.
|
PRIMARY
ACTION
|
Monitor the event reports at the network level to verify if an existing circuit was unequipped causing a status mismatch with the local end.
|
SIGNALING (46)
For additional information, refer to the "Specified Circuit Identification Code is Invalid for the Operation—Signaling (46)" section.
DESCRIPTION
|
Specified Circuit Identification Code is Invalid for the Operation (Specified CIC is Invalid for the Operation)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when an invalid operation was performed on the specified CIC.
|
PRIMARY
ACTION
|
Verify that the SS7 provisioning tables are properly configured at the circuit level.
|
SIGNALING (47)
SIGNALING (47) is not used.
SIGNALING (48)
SIGNALING (48) is not used.
SIGNALING (49)
For additional information, refer to the "A General Processing Error Encountered—Signaling (49)" section.
DESCRIPTION
|
A General Processing Error Encountered
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a general SS7 processing error occurred due to all resources being busy or an invalid event occurring.
|
PRIMARY
ACTION
|
Verify the status of the signaling adapter process and the SS7 signaling interface to verify proper operation.
|
SIGNALING (50)
For additional information, refer to the "Unexpected Message for the Call State is Received: Clear Call—Signaling (50)" section.
DESCRIPTION
|
Unexpected Message for the Call State is Received: Clear Call
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when an unexpected message was received for the current call state.
|
PRIMARY
ACTION
|
The call is cleared. Verify the status of the signaling adapter process and the SS7 signaling interface to verify proper operation.
|
SIGNALING (51)
For additional information, refer to the "Set Trunk State as Remotely Unequipped—Signaling (51)" section.
DESCRIPTION
|
Set Trunk State as Remotely Unequipped
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when the specified CIC is marked at remotely unequipped due to the CQM response indicating that it is unequipped at the far end.
|
PRIMARY
ACTION
|
Equip the trunk circuit at the far end.
|
SIGNALING (52)
For additional information, refer to the "Set Trunk State as NOT Remotely Blocked—Signaling (52)" section.
DESCRIPTION
|
Set Trunk State as NOT Remotely Blocked
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when the specified CIC is marked as not remotely blocked due to the CQM response indicating that it is not remotely blocked at the far end.
|
PRIMARY
ACTION
|
No action required.
|
SIGNALING (53)
For additional information, refer to the "Set Trunk State as Remotely Blocked—Signaling (53)" section.
DESCRIPTION
|
Set Trunk State as Remotely Blocked
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when the specified CIC is marked as remotely blocked due to the CQM response indicating that it is remotely blocked at the far end.
|
PRIMARY
ACTION
|
Clear the blocking situation at the far end based on network level event reports.
|
SIGNALING (54)
For additional information, refer to the "Circuit Validation Test Aborted—Signaling (54)" section.
DESCRIPTION
|
Circuit Validation Test Aborted
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when the circuit specified failed a validation test due to an internal failure.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter process and that the SS7 interface are operating normally.
|
SIGNALING (55)
For additional information, refer to the "Circuit Validation Successful—Signaling (55)" section.
DESCRIPTION
|
Circuit Validation Successful
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when the specified circuit was successfully validated.
|
PRIMARY
ACTION
|
No action required.
|
SIGNALING (56)
SIGNALING (56) is not used.
SIGNALING (57)
For additional information, refer to the "Continuity Recheck Failed—Signaling (57)" section.
DESCRIPTION
|
Continuity Recheck Failed
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a continuity recheck of the specified CIC failed.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter process and that the SS7 interface are operating normally.
|
SIGNALING (58)
For additional information, refer to the "Continuity Recheck Successful—Signaling (58)" section.
DESCRIPTION
|
Continuity Recheck Successful
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
Issued when a continuity recheck of the specified CIC was successful.
|
PRIMARY
ACTION
|
No action required.
|
SIGNALING (59)
To troubleshoot and correct the cause of the alarm, refer to the "Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway—Signaling (59)" section.
DESCRIPTION
|
Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway (Auto State Change for ISDN Trunk Group by Media Gateway)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
Media Gateway Name-STRING [65]
Media Gateway Index-FOUR_BYTES
Service Status-FOUR_BYTES
|
PRIMARY
CAUSE
|
Issued when the specified ISDN trunk group's status was changed due to a media gateway operation.
|
PRIMARY
ACTION
|
Monitor the event reports at the network level to determine which media gateway caused the status change of the trunk group.
|
SECONDARY
ACTION
|
Verify that the gateway is reconfigured properly to support the usage of the trunk group.
|
SIGNALING (60)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network STATUS Message Containing Error Indication Received—Signaling (60)" section.
DESCRIPTION
|
Integrated Services Digital Network STATUS Message Containing Error Indication Received (ISDN STATUS Message Containing Error Indication Received)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Name-STRING [40]
Termination Index-FOUR_BYTES
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
Cause Value-ONE_BYTE
Call State-ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when an ISDN status message was received containing an error indication for the specified termination.
|
PRIMARY
ACTION
|
If the specified termination is not operating normally, place it in the service state.
|
SIGNALING (61)
For additional information, refer to the "Trunk Operational State Changed by Service Message—Signaling (61)" section.
DESCRIPTION
|
Trunk Operational State Changed by Service Message
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Name-STRING [40]
Termination Index-FOUR_BYTES
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
Service Status-FOUR_BYTES
|
PRIMARY
CAUSE
|
Issued when the specified trunk group's operational status was changed 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)
For additional information, refer to the "Received Integrated Services Digital Network RESTART Message—Signaling (62)" section.
DESCRIPTION
|
Received Integrated Services Digital Network RESTART Message (Received ISDN RESTART Message)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Name-STRING [40]
Termination Index-FOUR_BYTES
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
Flag-FOUR_BYTES
|
PRIMARY
CAUSE
|
Issued when an ISDN restart message was received from the specified gateway.
|
PRIMARY
ACTION
|
Monitor the event reports at the network level to verify that the specified gateway and terminations are operating normally.
|
SIGNALING (63)
To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway/Termination Faulty—Signaling (63)" section.
DESCRIPTION
|
Media Gateway/Termination Faulty
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Fully Qualified Name-STRING [80]
Type of Gateway-STRING [32]
Reason for Failure-STRING [80]
|
PRIMARY
CAUSE
|
Issued when a media gateway or termination has gone faulty due to the detection of an unknown endpoint, unknown package type, and unknown event, a hardware failure, or a general call agent error.
|
PRIMARY
ACTION
|
Verify the proper operation of the media gateway specified. Place the termination out-of-service and then back into service from the call agent.
|
SIGNALING (64)
To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Adapter Running out of Shared Memory Pools—Signaling (64)" section.
DESCRIPTION
|
Media Gateway Adapter Running out of Shared Memory Pools (MGA Running out of Shared Memory Pools)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Issued when the Media Gateway Control Protocol (MGCP) signaling adapter was unable to allocate data storage for an inter-process communication (IPC) message due to a lack of resources.
|
PRIMARY
ACTION
|
Call Cisco TAC technologies for assistance. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (65)
To troubleshoot and correct the cause of the alarm, refer to the "Media Gateway Adapter Running out of Heap Memory—Signaling (65)" section.
DESCRIPTION
|
Media Gateway Adapter Running out of Heap Memory (MGA Running out of Heap Memory)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Issued when the MGCP signaling adapter was unable to allocate data storage for an IPC message from the heap due to a lack of resources.
|
PRIMARY
ACTION
|
Call Cisco TAC Technologies for assistance. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (66)
To troubleshoot and correct the cause of the alarm, refer to the "Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically)—Signaling (66)" section.
DESCRIPTION
|
Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically)-(CA Internal Error (Because of Which MGA has to Start Automatically))
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Fully Qualified Name-STRING [80]
Reason-STRING [80]
Detailed Reason-STRING [80]
|
PRIMARY
CAUSE
|
Issued when a call agent internal error has occurred causing the restart of the MGCP signaling adapter.
|
PRIMARY
ACTION
|
Send the log files to Cisco TAC for analysis and corrective action. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (67)
SIGNALING (67) is not used.
SIGNALING (68)
To troubleshoot and correct the cause of the alarm, refer to the "Trunking Gateway Endpoints are out of Service at the Gateway—Signaling (68)" section.
DESCRIPTION
|
Trunking Gateway Endpoints are out of Service at the Gateway (Media Gateway Endpoints are out of Service at the GW)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Fully Qualified Name-STRING [80]
Type of MGW- STRING [32]
Failure Cause-STRING [80]
Subscriber Info-STRING [80]
ICMP Ping Status-STRING [80]
|
PRIMARY
CAUSE
|
This could have been caused by:
(1) The trunking gateway has been administratively taken to the OOS state using the CLI command in the gateway (GW).
(2) The trunk endpoint is alarmed or in the OOS state.
|
PRIMARY
ACTION
|
(1) Fix the trunking gateway state that has been administratively taken to the INS state using the CLI command in the GW.
(2) Fix the trunk endpoint alarms.
|
SIGNALING (69)
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.
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)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication—Signaling (70)" section.
DESCRIPTION
|
Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication (ISDN Unable to Restore D-channel Due to Failed Communication)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The ISDN signaling adapter is unable to restore a D-channel due to incorrect backhaul provisioning at the media gateway or call agent.
|
PRIMARY
ACTION
|
Ensure that the provisioning of the backhaul port is correct at both the call agent and media gateway.
|
SIGNALING (71)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network Unable to Establish D-channel—Signaling (71)" section.
DESCRIPTION
|
Integrated Services Digital Network Unable to Establish D-channel (ISDN Unable to Establish D-channel)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The ISDN signaling adapter is unable to establish a D-channel due to layer one parameters not being provisioned correctly or improper provisioning of the network or user side.
|
PRIMARY
ACTION
|
Verify the correct provisioning at the media gateway.
|
SIGNALING (72)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network-Calls Lost Due to D-channel Down for Period of Time—Signaling (72)" section.
DESCRIPTION
|
Integrated Services Digital Network-Calls Lost Due to D-channel Down for Period of Time (ISDN-Calls Lost Due to D-channel Down for Period of Time)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The ISDN signaling adapter has lost calls due to a D-channel being down as a result of a media gateway power loss or a loss of 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)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network-Unable to Send RESTART Due to RESTART Timer Expired—Signaling (73)" section.
DESCRIPTION
|
Integrated Services Digital Network-Unable to Send RESTART Due to RESTART Timer Expired (ISDN-Unable to Send RESTART Due to RESTART Timer Expired)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Name-STRING [40]
Termination Index-FOUR_BYTES
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
Restart Class-FOUR_BYTES
|
PRIMARY
CAUSE
|
The ISDN signaling adapter was unable to send a RESTART message due to the expiration of the RESTART timer.
|
PRIMARY
ACTION
|
Verify that the RESTART timer is set to an appropriate level.
|
SIGNALING (74)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired—Signaling (74)" section.
DESCRIPTION
|
Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired (ISDN: Unable to Send the SERVICE Due to the SERVICE Timer Expired)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Termination Name-STRING [40]
Termination Index-FOUR_BYTES
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
Service Status-FOUR_BYTES
|
PRIMARY
CAUSE
|
The ISDN signaling adapter was unable to send a SERVICE message due to the expiration of the SERVICE timer.
|
PRIMARY
ACTION
|
Ensure that the SERVICE timer is set to an appropriate level.
|
SIGNALING (75)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Stack not Ready—Signaling (75)" section.
DESCRIPTION
|
Signaling System 7 Stack not Ready (SS7 Stack not Ready)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
LogicalName-STRING [64]
|
PRIMARY
CAUSE
|
SS7 stack is not configured properly.
|
PRIMARY
ACTION
|
Check SS7 stack configuration.
|
SECONDARY
CAUSE
|
SS7 stack is not ready.
|
SECONDARY
ACTION
|
Check SS7 stack status. Execute the platform start -i omni command to bring up SS7 stack.
|
SIGNALING (76)
For additional information, refer to the "Timeout on Remote Instance—Signaling (76)" section.
DESCRIPTION
|
Timeout on Remote Instance
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Port Number-TWO_BYTES
Hostname-STRING [64]
|
PRIMARY
CAUSE
|
The communication between the call agent and the remote instance is faulty.
|
PRIMARY
ACTION
|
No action needed.
|
SIGNALING (77)
For additional information, refer to the "Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling—Signaling (77)" section.
DESCRIPTION
|
Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling (ISDN D-channel Switchover for NFAS)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group ID-FOUR_BYTES
Trunk Group Index-FOUR_BYTES
|
PRIMARY
CAUSE
|
The D-channels were manually switched using 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)
To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling—Signaling (78)" section.
DESCRIPTION
|
Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling (ISDN Single D-channel Down for NFAS)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group ID-FOUR_BYTES
Trunk Group Idx-FOUR_BYTES
IS Primary D Channel-FOUR_BYTES
|
PRIMARY
CAUSE
|
One of the ISDN D-channels in the primary rate interface (PRI) is down.
|
PRIMARY
ACTION
|
Check the gateway power and the gateway connection to the PBX.
|
SIGNALING (79)
To troubleshoot and correct the cause of the alarm, refer to the "Trunking Gateway Unreachable—Signaling (79)" section.
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 BTS Call Agent and the Trunking Gateway.
|
SIGNALING (80)
To troubleshoot and correct the cause of the alarm, refer to the "Out of Bounds, Memory/Socket Error—Signaling (80)" section.
DESCRIPTION
|
Out of Bounds, Memory/Socket Error
|
SEVERITY
|
CRITICAL
|
DATAWORDS
|
Process Name-STRING [40]
Description-STRING [40]
Extra Info-STRING [40]
|
PRIMARY
CAUSE
|
Out of heap memory.
|
PRIMARY
ACTION
|
Notify customer support. Increase the random access memory (RAM). (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.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (81)
To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Heap Memory—Signaling (81)" section.
DESCRIPTION
|
Insufficient Heap Memory
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
|
PRIMARY
CAUSE
|
Issued when the H.323 Protocol (H323) signaling adapter is unable to allocate memory from the system.
|
PRIMARY
ACTION
|
Call Cisco TAC for assistance. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (82)
To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Shared Memory Pools—Signaling (82)" section.
DESCRIPTION
|
Insufficient Shared Memory Pools
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
|
PRIMARY
CAUSE
|
Issued when the H323 signaling adapter was unable to allocate storage.
|
PRIMARY
ACTION
|
Call Cisco TAC for corrective action. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (83)
To troubleshoot and correct the cause of the alarm, refer to the "Error While Binding to Socket—Signaling (83)" section.
DESCRIPTION
|
Error While Binding to Socket
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Socket ID-FOUR_BYTES
Local TSAP Address-STRING [32]
Reason-STRING [128]
|
PRIMARY
CAUSE
|
An error has occurred while binding to a socket.
|
PRIMARY
ACTION
|
Contact Cisco TAC.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (84)
To troubleshoot and correct the cause of the alarm, refer to the "Reached Maximum Socket Limit—Signaling (84)" section.
DESCRIPTION
|
Reached Maximum Socket Limit
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Active Sockets-FOUR_BYTES
|
PRIMARY
CAUSE
|
The configuration setting of an H.323 signaling adapter (H3A) parameter in the platform.cfg file is wrong.
|
PRIMARY
ACTION
|
Reconfigure the platform.cfg file and restart the H3A process.
|
SIGNALING (85)
To troubleshoot and correct the cause of the alarm, refer to the "Initialization Failure—Signaling (85)" section.
DESCRIPTION
|
Initialization Failure
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Reason-STRING [128]
|
PRIMARY
CAUSE
|
A process initialization failure has occurred.
|
PRIMARY
ACTION
|
Check Dataword 2 (Reason) for the failure cause and take action accordingly.
|
SIGNALING (86)
To troubleshoot and correct the cause of the alarm, refer to the "Remote H323 Gateway is not Reachable—Signaling (86)" section.
DESCRIPTION
|
Remote H323 Gateway is not Reachable
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Remote GW TSAP Addr-STRING [32]
|
PRIMARY
CAUSE
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "H323 Message Parsing Error—Signaling (87)" section.
DESCRIPTION
|
H323 Message Parsing Error
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Remote GW TSAP Addr-STRING [32]
|
PRIMARY
CAUSE
|
Unable to successfully parse an incoming H323 message.
|
PRIMARY
ACTION
|
This is a result of either a software bug or bad message being received-a message with a valid message type but an invalid field within the message. Snoop the message from the endpoint and verify it's content or call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (88)
To troubleshoot and correct the cause of the alarm, refer to the "H323 Message Encoding Error—Signaling (88)" section.
DESCRIPTION
|
H323 Message Encoding Error
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Reason-STRING [128]
|
PRIMARY
CAUSE
|
Unable to encode an H323 message for sending.
|
PRIMARY
ACTION
|
This is indicative a software bug. Contact Cisco TAC.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (89)
To troubleshoot and correct the cause of the alarm, refer to the "Gatekeeper not Available/Reachable—Signaling (89)" section.
DESCRIPTION
|
Gatekeeper not Available/Reachable
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Gatekeeper ID-STRING [32]
GK TSAP Addr-STRING [32]
|
PRIMARY
CAUSE
|
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 reachable, then check to ensure that the GK is configured up.
|
SIGNALING (90)
To troubleshoot and correct the cause of the alarm, refer to the "Alternate Gatekeeper is not Responding—Signaling (90)" section.
DESCRIPTION
|
Alternate Gatekeeper is not Responding
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Gatekeeper ID-STRING [32]
GK TSAP Addr-STRING [32]
|
PRIMARY
CAUSE
|
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 reachable, then check to ensure that the alternate GK is configured up.
|
SIGNALING (91)
To troubleshoot and correct the cause of the alarm, refer to the "Endpoint Security Violation—Signaling (91)" section.
DESCRIPTION
|
Endpoint Security Violation
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Gatekeeper ID-STRING [32]
GK TSAP Addr-STRING [32]
|
PRIMARY
CAUSE
|
An H323 security violation has occurred.
|
PRIMARY
ACTION
|
The password on the BTS 10200 and/or the gatekeeper is wrong-the H323 gateway (H323GW) table may not be provisioned properly or there is a time synchronization problem between the BTS 10200 and/or gatekeeper and the Network Time Protocol (NTP) server. Ensure that both the BTS 10200 and the gatekeeper are pointing to the same NTP server.
|
SIGNALING (92)
To troubleshoot and correct the cause of the alarm, refer to the "Invalid Call Identifier—Signaling (92)" section.
DESCRIPTION
|
Invalid Call Identifier
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Remote GW TSAP Addr-STRING [32]
Call ID-EIGHT_BYTES
|
PRIMARY
CAUSE
|
The call ID was invalid or changed mid-call.
|
PRIMARY
ACTION
|
There is a software problem on the BTS 10200 or on an endpoint. Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (93)
To troubleshoot and correct the cause of the alarm, refer to the "Invalid Call Reference Value—Signaling (93)" section.
DESCRIPTION
|
Invalid Call Reference Value
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Remote GW TSAP Addr-STRING [32]
Call ID-EIGHT_BYTES
Call Ref Value-EIGHT_BYTES
|
PRIMARY
CAUSE
|
The call ID was invalid or changed mid-call.
|
PRIMARY
ACTION
|
There is a software problem on the BTS 10200 or on an endpoint. Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (94)
To troubleshoot and correct the cause of the alarm, refer to the "Invalid Conference Identifier—Signaling (94)" section.
DESCRIPTION
|
Invalid Conference Identifier
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Reason-STRING [32]
Remote GW Port-TWO_BYTES
Call ID-EIGHT_BYTES
Conference ID-EIGHT_BYTES
|
PRIMARY
CAUSE
|
The call ID was invalid or changed mid-call.
|
PRIMARY
ACTION
|
There is a software problem on the BTS 10200 or on an endpoint. Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (95)
To troubleshoot and correct the cause of the alarm, refer to the "Invalid Message from the Network—Signaling (95)" section.
DESCRIPTION
|
Invalid Message from the Network
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Remote GW TSAP Addr-STRING [32]
Call ID-EIGHT_BYTES
Conf ID-EIGHT_BYTES
Call Ref Value-EIGHT_BYTES
|
PRIMARY
CAUSE
|
An unsupported or invalid message type received from network.
|
PRIMARY
ACTION
|
Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (96)
To troubleshoot and correct the cause of the alarm, refer to the "Internal Call Processing Error—Signaling (96)" section.
DESCRIPTION
|
Internal Call Processing Error
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Call ID-EIGHT_BYTES
Reason-STRING [128]
|
PRIMARY
CAUSE
|
A software error has occurred.
|
PRIMARY
ACTION
|
Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (97)
To troubleshoot and correct the cause of the alarm, refer to the "Insufficient Information to Complete Call—Signaling (97)" section.
DESCRIPTION
|
Insufficient Information to Complete Call
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Call ID-EIGHT_BYTES
Conf ID-EIGHT_BYTES
Call Ref Value-EIGHT_BYTES
|
PRIMARY
CAUSE
|
Not enough initial call setup information was received to establish the call.
|
PRIMARY
ACTION
|
Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (98)
To troubleshoot and correct the cause of the alarm, refer to the "H323 Protocol Inconsistencies—Signaling (98)" section.
DESCRIPTION
|
H323 Protocol Inconsistencies
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Call ID-EIGHT_BYTES
Reason-STRING [128]
|
PRIMARY
CAUSE
|
The H323 endpoint and the BTS 10200 are running different protocol versions.
|
PRIMARY
ACTION
|
This is only an issue where the endpoint is running a higher version of the H323 protocol than the BTS 10200. Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (99)
To troubleshoot and correct the cause of the alarm, refer to the "Abnormal Call Clearing—Signaling (99)" section.
DESCRIPTION
|
Abnormal Call Clearing
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Call ID-EIGHT_BYTES
Reason-STRING [128]
|
PRIMARY
CAUSE
|
Unsupported or invalid message type received from network.
|
PRIMARY
ACTION
|
Call Cisco TAC. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (100)
To troubleshoot and correct the cause of the alarm, refer to the "Codec Negotiation Failed—Signaling (100)" section.
DESCRIPTION
|
Codec Negotiation Failed
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Call ID-EIGHT_BYTES
Reason-STRING [128]
|
PRIMARY
CAUSE
|
The Codec negotiation has failed.
|
PRIMARY
ACTION
|
Find a compatible set of codec settings for both sides, re-provision the endpoints of the call, and try the call again.
|
SIGNALING (101)
To troubleshoot and correct the cause of the alarm, refer to the "Per Call Security Violation—Signaling (101)" section.
DESCRIPTION
|
Per Call Security Violation
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Call ID-EIGHT_BYTES
Gatekeeper ID-STRING [32]
|
PRIMARY
CAUSE
|
This is a future trap definition.
|
PRIMARY
ACTION
|
None
|
SIGNALING (102)
To troubleshoot and correct the cause of the alarm, refer to the "H323 Network Congested—Signaling (102)" section.
DESCRIPTION
|
H323 Network Congested
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Gateway ID-STRING [32]
Gatekeeper ID-STRING [32]
|
PRIMARY
CAUSE
|
The H323 application processes has depleted 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 BTS 10200.
|
SIGNALING (103)
To troubleshoot and correct the cause of the alarm, refer to the "Aggregation Connection Down—Signaling (103)" section.
DESCRIPTION
|
Aggregation Connection Down (AGGR Connection Down)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
AGGR-ID-STRING [16]
|
PRIMARY
CAUSE
|
The Transmission Control Protocol (TCP) connection is down.
|
PRIMARY
ACTION
|
Check the associated cabling and perform a PING to test the connectivity.
|
SIGNALING (104)
For additional information, refer to the "Aggregation Unable To Establish Connection—Signaling (104)" section.
DESCRIPTION
|
Aggregation Unable To Establish Connection (AGGR Unable To Establish Connection)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
AGGR-ID-STRING [16]
|
PRIMARY
CAUSE
|
A TCP connection establish failure has occurred.
|
PRIMARY
ACTION
|
Check the IP connectivity of the CA and the cable modem termination system (CMTS).
|
SIGNALING (105)
For additional information, refer to the "Aggregation Gate Set Failed—Signaling (105)" section.
DESCRIPTION
|
Aggregation Gate Set Failed (AGGR Gate Set Failed)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
AGGR-ID-STRING [16]
Error-Code-TWO_BYTES
Sub-Error-Code-TWO_BYTES
|
PRIMARY
CAUSE
|
The gate set acknowledgement never came from the CMTS.
|
PRIMARY
ACTION
|
None
|
SIGNALING (106)
To troubleshoot and correct the cause of the alarm, refer to the "Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down—Signaling (106)" section.
DESCRIPTION
|
Enhanced Subscriber Authentication BTS 10200 Delivery Function Connection Down (ESA BTS 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)
To troubleshoot and correct the cause of the alarm, refer to the "Logical Internet Protocol Addresses not Mapped Correctly—Signaling (107)" section.
DESCRIPTION
|
Logical Internet Protocol Addresses not Mapped Correctly (Logical IP Addresses not Mapped Correctly)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Contact Domain Name-STRING [128]
Number of IP Addresses Resolved-FOUR_BYTES
Number of Virtual IP Addresses-FOUR_BYTES
|
PRIMARY
CAUSE
|
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 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.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (108)
To troubleshoot and correct the cause of the alarm, refer to the "Simplex Only Operational Mode—Signaling (108)" section.
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 -contact parameter.
|
PRIMARY
ACTION
|
The BTS 10200 is configured as a SIMPLEX system.
|
SIGNALING (109)
To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Failure—Signaling (109)" section.
DESCRIPTION
|
Stream Control Transmission Protocol Association Failure (SCTP Association Failure)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
SCTP Association ID-STRING [17]
|
PRIMARY
CAUSE
|
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 it is not operating properly.
|
SIGNALING (110)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Group Is Out-of-Service—Signaling (110)" section.
DESCRIPTION
|
Signaling Gateway Group is Out-of-Service
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
SG Group ID-STRING [17]
|
PRIMARY
CAUSE
|
All Stream Control Transmission Protocol (SCTP) associations between 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)
To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down)—Signaling (111)" section.
DESCRIPTION
|
Stream Control Transmission Protocol Association Degraded (One of Two Internet Protocol Connections Down) (SCTP Association Degraded (One of Two IP connections Down))
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
SCTP Association ID-STRING [17]
Destination IP Address-STRING [11]
|
PRIMARY
CAUSE
|
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
|
A SCTP communication problem-protocol timeout.
|
SECONDARY
ACTION
|
Use the Cisco snooper application to determine why the SCTP association is degraded.
|
SIGNALING (112)
To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Configuration Error—Signaling (112)" section.
DESCRIPTION
|
Stream Control Transmission Protocol Association Configuration Error (SCTP Association Configuration Error)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
SCTP Association ID-STRING [17]
|
PRIMARY
CAUSE
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Failure—Signaling (113)" section.
Note When a port on a ITP is removed from service using the shut command, multiple Signaling 113 and 114 alarms are raised (ON status). When the port is recovered by cycling the ITP power, all alarms raised are cleared (OFF status) and are removed from CURRENT_ALARM table. However, not all cleared alarms (OFF status) are displayed on the subscriber terminal. Only the first instance of the cleared alarms (OFF status) with a variation in TYPE, NUMBER, and COMPONENT-ID are displayed. Multiple instances of the cleared alarms (OFF status) where the TYPE, NUMBER, and COMPONENT-ID are identical are not displayed.
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)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Process Is Out-of-Service—Signaling (114)" section.
Note When a port on a ITP is removed from service using the shut command, multiple Signaling 113 and 114 alarms are raised (ON status). When the port is recovered by cycling the ITP power, all alarms raised are cleared (OFF status) and are removed from CURRENT_ALARM table. However, not all cleared alarms (OFF status) are displayed on the subscriber terminal. Only the first instance of the cleared alarms (OFF status) with a variation in TYPE, NUMBER, and COMPONENT-ID are displayed. Multiple instances of the cleared alarms (OFF status) where the TYPE, NUMBER, and COMPONENT-ID are identical are not displayed.
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)
To monitor and correct the cause of the event, refer to the "Invalid Routing Context Received—Signaling (115)" section.
DESCRIPTION
|
Invalid Routing Context Received
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Invalid Routing Cont-FOUR_BYTES
SG from Which the In-STRING [17]
|
PRIMARY
CAUSE
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code User Part Unavailable—Signaling (116)" section.
DESCRIPTION
|
Destination Point Code User Part Unavailable (DPC User Part Unavailable)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
DPC ID-STRING [17]
|
PRIMARY
CAUSE
|
A 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)
To troubleshoot and correct the cause of the alarm, refer to the "Circuit Validation Test Message Received for an Unequipped Circuit Identification Code—Signaling (117)" section.
DESCRIPTION
|
Circuit Validation Test Message Received for an Unequipped Circuit Identification Code (CVT Message Received for an Unequipped CIC)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC-TWO_BYTES
TGN-ID-EIGHT_BYTES
DPC-STRING [13]
|
PRIMARY
CAUSE
|
The CIC is not provisioned
|
PRIMARY
ACTION
|
Provision the CIC.
|
SIGNALING (118)
To troubleshoot and correct the cause of the alarm, refer to the "Circuit Verification Response Received with Failed Indication—Signaling (118)" section.
DESCRIPTION
|
Circuit Verification Response Received with Failed Indication (CVR Received with Failed Indication)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC-TWO_BYTES
TGN-ID-EIGHT_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Adapter Process Faulty—Signaling (119)" section.
DESCRIPTION
|
Signaling System 7 Adapter Process Faulty (S7A Process Faulty)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Reason-STRING [36]
|
PRIMARY
CAUSE
|
An OMNI or S7A exception has occurred.
|
PRIMARY
ACTION
|
Check the OMNI process. The S7A will restart itself if S7A maximum number of restarts is not exceeded.
|
SIGNALING (120)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Module/Signaling System 7 Adapter Faulty—Signaling (120)" section.
DESCRIPTION
|
Signaling System 7 Module/Signaling System 7 Adapter Faulty (S7M/S7A Faulty)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Reason-STRING [36]
|
PRIMARY
CAUSE
|
An OMNI failure has occurred.
|
PRIMARY
ACTION
|
Check the OMNI status; a failover will occur in a duplex configuration.
|
SIGNALING (121)
To troubleshoot and correct the cause of the alarm, refer to the "Message Transfer Part 3 User Adapter Cannot Go Standby—Signaling (121)" section.
DESCRIPTION
|
Message Transfer Part 3 User Adapter Cannot Go Standby (M3UA/SUA Cannot Go Standby)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Platform ID-STRING [17]
|
PRIMARY
CAUSE
|
No INACTIVE acknowledge (ACK) messages 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)
To troubleshoot and correct the cause of the alarm, refer to the "Message Transfer Part 3 User Adapter Cannot Go Active—Signaling (122)" section.
DESCRIPTION
|
Message Transfer Part 3 User Adapter Cannot Go Active (M3UA/SUA Cannot Go Active)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Platform ID-STRING [17]
|
PRIMARY
CAUSE
|
No ACTIVE acknowledgement messages 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)
To troubleshoot and correct the cause of the alarm, refer to the "Remote Subsystem is Out Of Service—Signaling (124)" section.
DESCRIPTION
|
Remote Subsystem is Out Of Service
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Destination Point Co-STRING [20]
Remote Subsystem Num-TWO_BYTES
|
PRIMARY
CAUSE
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling Connection Control Part Routing Error—Signaling (125)" section.
DESCRIPTION
|
Signaling Connection Control Part Routing Error (SCCP Routing Error)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
The signaling connection control part (SCCP) route is invalid or is not available.
|
PRIMARY
ACTION
|
Provision the right SCCP route.
|
SIGNALING (126)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling Connection Control Part Binding Failure—Signaling (126)" section.
DESCRIPTION
|
Signaling Connection Control Part Binding Failure (SCCP Binding Failure)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Local Point Code-STRING [20]
Local Subsystem Numb-ONE_BYTE
|
PRIMARY
CAUSE
|
A Trillium stack binding failure has occurred.
|
PRIMARY
ACTION
|
Re-initialize the TCAP signaling adapter (TSA) process or remove the subsystem from the Element Management System (EMS) table and add it again.
|
SIGNALING (127)
To troubleshoot and correct the cause of the alarm, refer to the "Transaction Capabilities Application Part Binding Failure—Signaling (127)" section.
DESCRIPTION
|
Transaction Capabilities Application Part Binding Failure (TCAP Binding Failure)
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
A Trillium stack binding failure has occurred.
|
PRIMARY
ACTION
|
Re-initialize 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)
To monitor and correct the cause of the event, refer to the "Transaction Capabilities Application Part Reaches the Provisioned Resource Limit—Signaling (132)" section.
DESCRIPTION
|
Transaction Capabilities Application Part Reaches the Provisioned Resource Limit (TCAP Reaches the Provisioned Resource Limit)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Dialogue/Invoke ID-FOUR_BYTES
|
PRIMARY
CAUSE
|
The Transaction Capabilities Application Part (TCAP) has run out of all the pre-configured dialogue IDs or invoke IDs.
|
SIGNALING (133)
For additional information, refer to the "Unable to Decode Generic Transport Descriptor Message—Signaling (133)" section.
DESCRIPTION
|
Unable to Decode Generic Transport Descriptor Message (Unable to Decode GTD Message)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Endpoint Name-STRING [40]
GTD Content Type-STRING [40]
|
PRIMARY
CAUSE
|
Issued when the generic transport descriptor (GTD) parser failed to decode a GTD message received from the specified endpoint.
|
PRIMARY
ACTION
|
Verify that the version of the GTD protocol used by the device at the remote endpoint is consistent with the version expected by the call agent.
|
SECONDARY
ACTION
|
Examine the associated signaling link to see if there is any interruption of the supplementary services on the link.
|
SIGNALING (134)
For additional information, refer to the "Signaling System 7 Message Encoding Failure—Signaling (134)" section.
DESCRIPTION
|
Signaling System 7 Message Encoding Failure (SS7 Message Encoding Failure)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
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. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (135)
For additional information, refer to the "Signaling System 7 Message Decoding Failure—Signaling (135)" section.
DESCRIPTION
|
Signaling System 7 Message Decoding Failure (SS7 Message Decoding Failure)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
An error in the ISUP stack or in a SAI message has occurred.
|
PRIMARY
ACTION
|
Capture the SS7 trace of circuit for examination by support personnel. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (136)
For additional information, refer to the "Signaling System 7 Message Invalid Received—Signaling (136)" section.
DESCRIPTION
|
Signaling System 7 Message Invalid Received (SS7 Message Invalid Received)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
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. (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.
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (137)
For additional information, refer to the "Signaling System 7 Confusion Message Received—Signaling (137)" section.
DESCRIPTION
|
Signaling System 7 Confusion Message Received (SS7 Confusion Message Received)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC Number-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
An ISUP message or a parameter received was not recognized or understood.
|
PRIMARY
ACTION
|
Check the log for more information (including confusion (CFN) diagnostic output). Capture a 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 support along with a description of the call scenario.
|
SIGNALING (138)
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.
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 support. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (139)
For additional information, refer to the "Signaling System 7 Trunk was Found to be in Erroneous State—Signaling (139) (SS7)" section.
DESCRIPTION
|
Signaling System 7 Trunk was Found to be in Erroneous State (SS7 Trunk was Found to be in Erroneous State)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
Near-End State-STRING [64]
Far-End State-STRING [64]
Resolution Action-STRING [64]
|
PRIMARY
CAUSE
|
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)
For additional information, refer to the "Unanswered Information Message—Signaling (140)" section.
DESCRIPTION
|
Unanswered Information Message (Unanswered INF Message)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
CIC-TWO_BYTES
TGN-ID-FOUR_BYTES
DPC-STRING [20]
OPC-STRING [20]
|
PRIMARY
CAUSE
|
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)
To monitor and correct the cause of the event, refer to the "Address not Resolved by Domain Name System Server—Signaling (141)" section.
DESCRIPTION
|
Address not Resolved by Domain Name System Server (Address not Resolved by DNS Server)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
TSAP_Address/Hostname-STRING [256]
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 BTS 10200 provisioning.
|
SIGNALING (142)
To troubleshoot and correct the cause of the alarm, refer to the "Session Initiation Protocol Trunk Operationally Out-of-Service—Signaling (142)" section.
DESCRIPTION
|
Session Initiation Protocol Trunk Operationally Out-of-Service (SIP Trunk Operationally out of Service)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Trunk Group Description -STRING [21]
Trunk SIP Element ID-STRING [65]
Trunk Server Group ID-STRING [65]
|
PRIMARY
CAUSE
|
Issued when the 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)
To troubleshoot and correct the cause of the alarm, refer to the "Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down—Signaling (143)" section.
DESCRIPTION
|
Internet Protocol Interface Link to the Signaling System 7 Signaling Gateway is Down (IP Interface Link to the SS7 Signaling Gateway is Down)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [65]
Interface IP Address-STRING [65]
|
PRIMARY
CAUSE
|
A hardware problem has occurred.
|
PRIMARY
ACTION
|
Check the link interfaces.
|
SIGNALING (144)
To troubleshoot and correct the cause of the alarm, refer to the "All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway are Down—Signaling (144)" section.
DESCRIPTION
|
All Internet Protocol Interface Links to Signaling System 7 Signaling Gateway are Down (All IP Interface Links to SS7 Signaling Gateway are Down)
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [65]
Interface IP Address-STRING [65]
|
PRIMARY
CAUSE
|
A hardware problem has occurred.
|
PRIMARY
ACTION
|
Check the link interfaces.
|
SIGNALING (145)
To troubleshoot and correct the cause of the alarm, refer to the "One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down—Signaling (145)" section.
DESCRIPTION
|
One Internet Protocol Interface to Signaling System 7 Signaling Gateway is Down (One IP Interface to SS7 Signaling Gateway is Down)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Interface Name-STRING [65]
Interface IP Address-STRING [65]
|
PRIMARY
CAUSE
|
A hardware problem has occurred.
|
PRIMARY
ACTION
|
Check the link interfaces.
|
SIGNALING (146)
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.
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 DNS server is up and running for the host name resolution and 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 for failures related to the SIP responses.
|
SIGNALING (147)
To monitor and correct the cause of the event, refer to the "Domain Name System Service Addresses Exhausted—Signaling (147)" section.
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 address is exhausted.
|
PRIMARY
ACTION
|
Add an entry to the SRV in the DNS server. Fix the BTS 10200 provisioning.
|
SIGNALING (148)
SIGNALING (148) is not used.
SIGNALING (149)
SIGNALING (149) is not used.
SIGNALING (150)
To troubleshoot and correct the cause of the alarm, refer to the "Stream Control Transmission Protocol Association Congested—Signaling (150)" section.
DESCRIPTION
|
Stream Control Transmission Protocol Association Congested (SCTP Association Congested)
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
SCTP Association ID-STRING [17]
Congestion Level-ONE_BYTE
|
PRIMARY
CAUSE
|
The network is congested.
|
PRIMARY
ACTION
|
Clean off the network congestion caused by the routing or switching issues.
|
SECONDARY
CAUSE
|
The central processing unit (CPU) is throttled.
|
SECONDARY
ACTION
|
You may need to upgrade to a more powerful platform or offload some traffic.
|
SIGNALING (151)
To troubleshoot and correct the cause of the alarm, refer to the "Subscriber Line Faulty—Signaling (151)" section.
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 BTS 10200 CLI command. If the problem persist after more calls, check the configuration in the BTS 10200 and the RGW. If the error codes returned by the MGW are harmless, it can be suppressed by adding a new entry in MGCP-RETCODE-ACTION table and by changing the EP-ACTION to RESET/NONE.
|
SIGNALING (152)
For additional information, refer to the "Termination Transient Error Received—Signaling (152)" section.
DESCRIPTION
|
Termination Transient Error Received
|
SEVERITY
|
INFO
|
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
|
Notify customer support. (Contact Cisco TAC.)
|
Note Refer to the "Obtaining Documentation and Submitting a Service Request" section on page lvi for detailed instructions on contacting Cisco TAC and opening a service request.
SIGNALING (153)
To troubleshoot and correct the cause of the alarm, refer to the "Emergency Trunks Become Locally Blocked—Signaling (153)" section.
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)
To troubleshoot and correct the cause of the alarm, refer to the "Emergency Trunks Become Remotely Blocked—Signaling (154)" section.
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)
For additional information, refer to the "Packet Cable Multi-Media Unsolicited Gate Delete—Signaling (155)" section.
DESCRIPTION
|
Packet Cable Multi-Media Unsolicited Gate Delete (PCMM Unsolicited Gate Delete)
|
SEVERITY
|
INFO
|
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)
To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Signaling Gateway Down—Signaling (156)" section.
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 as it is down due to a failure in the gateway. The SCTP association may 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 may be down in the gateway.
|
SECONDARY
ACTION
|
No action is needed. The IUA layer will be automatically recovered.
|
SIGNALING (157)
To troubleshoot and correct the cause of the alarm, refer to the "Integrated Services Digital Network Signaling Gateway Inactive—Signaling (157)" section.
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)
To monitor and correct the cause of the event, refer to the "Invalid Integrated Services Digital Network Interface Identification—Signaling (158)" section.
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)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network User Adaptation Layer can not Go Active—Signaling (159)" section.
DESCRIPTION
|
Integrated Services Digital Network User Adaptation Layer can not Go Active (IUA can not Go Active)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
N/A
|
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)
To monitor and correct the cause of the event, refer to the "Integrated Services Digital Network User Adaptation Layer can not Go Standby—Signaling (160)" section.
DESCRIPTION
|
Integrated Services Digital Network User Adaptation Layer can not Go Standby (IUA can not Go Standby)
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
N/A
|
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)
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.
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 BTS 10200 to send SIP UPDATE messages. The UPDATE message is mandatory in CMSS and is used exclusively by the BTS 10200 for operator service calls over SIP including BLV, emergency interrupt, and 911 ringback calls.
|
PRIMARY
ACTION
|
Upgrade or re-provision the remote switch so it can process incoming SIP UPDATE messages.
|
SIGNALING (162)
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.
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 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, then 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 listening on the port specified in the TSAP address.
|
SIGNALING (163)
To troubleshoot and correct the cause of the alarm, refer to the "Routing Key Inactive—Signaling (163)" section.
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 SG 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)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling Gateway Traffic Mode Mismatch—Signaling (164)" section.
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 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 BTS 10200.
|
SIGNALING (165)
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.
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-Info header to outgoing SIP requests and responses.
|
PRIMARY
ACTION
|
Provision the originating switch to add the P-DCS-Billing-Info header to outgoing messages.
|
SECONDARY
CAUSE
|
The header could have been stripped off by an intermediate proxy.
|
SECONDARY
ACTION
|
Determine if it has been stripped off by an intermediate proxy and 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 adjacent switch and if so, call the technical assistance center to determine a fix for the problem.
|
SIGNALING (166)
To monitor and correct the cause of the event, refer to the "No Routing Keys are Active—Signaling (166)" section.
DESCRIPTION
|
No Routing Keys are Active
|
SEVERITY
|
WARNING
|
THRESHOLD
|
0
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
Routing keys are not controlled into an ACTIVE state.
|
PRIMARY
ACTION
|
Control the routing keys to the ACTIVE state.
|
SECONDARY
CAUSE
|
The ITP provisioning is incorrect.
|
SECONDARY
ACTION
|
Check the ITP provisioning.
|
SIGNALING (167)
To monitor and correct the cause of the event, refer to the "No Signaling Gateways are Active—Signaling (167)" section.
DESCRIPTION
|
No Signaling Gateways are Active
|
SEVERITY
|
WARNING
|
THRESHOLD
|
0
|
THROTTLE
|
0
|
PRIMARY
CAUSE
|
A communication problem between the ITP and the BTS 10200 has occurred.
|
PRIMARY
ACTION
|
Check the communication path between the BTS 10200 and the ITP.
|
SIGNALING (168)
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.
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 administrative in-service is provisioned but has no child elements provisioned.
|
PRIMARY
ACTION
|
This Server Group will be considered as if it is administrative out of service. If that is acceptable, then no action required. If the server group was expected to be workable, then place the server group back out of service, resolve the provisioning problem, and place back into service.
|
SIGNALING (169)
For additional information, refer to the "Session Initiation Protocol Element Provisioned with Service Enabled is Internally Disabled—Signaling (169)" section.
DESCRIPTION
|
Session Initiation Protocol Element Provisioned with Service Enabled is Internally Disabled (SIP Element Provisioned with SRV Enabled is Internally Disabled)
|
SEVERITY
|
INFO
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
SIP Element ID-STRING [64]
|
PRIMARY
CAUSE
|
A SIP Element was provisioned with SRV enabled and is associated to 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)
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.
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 using the command at the GW.
|
PRIMARY
ACTION
|
Bring the residential gateway administratively into INS using the command at the GW.
|
SIGNALING (171)
To troubleshoot and correct the cause of the alarm, refer to the "Residential Gateway Unreachable—Signaling (171)" section.
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
|
A MGCP signaling interop error has occurred with the residential media gateway.
|
PRIMARY
ACTION
|
Check the IP connectivity status between BTS 10200 call agent and the trunking gateway. If the residential gateway is not physically connected, but controlled INS at the BTS 10200.
|
SIGNALING (172)
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.
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 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)
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.
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)
To troubleshoot and correct the cause of the alarm, refer to the "ENUM Server Unavailable—Signaling (174)" section.
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)
To troubleshoot and correct the cause of the alarm, refer to the "ENUM Server Farm Unavailable—Signaling (175)" section.
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)
To troubleshoot and correct the cause of the alarm, refer to the "No Resources Available to Launch ENUM Query—Signaling (176)" section.
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)
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.
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 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.
|
Monitoring Signaling Events
This section provides the information needed to monitor and correct signaling events. Table 10-2 lists all of the signaling events in numerical order and provides cross reference to each subsection in this section.
