Table Of Contents
Signaling Troubleshooting
Introduction
Signaling Events and Alarms
SIGNALING (1)
SIGNALING (4)
SIGNALING (6)
SIGNALING (7)
SIGNALING (8)
SIGNALING (9)
SIGNALING (10)
SIGNALING (11)
SIGNALING (12)
SIGNALING (13)
SIGNALING (14)
SIGNALING (15)
SIGNALING (16)
SIGNALING (17)
SIGNALING (18)
SIGNALING (19)
SIGNALING (20)
SIGNALING (21)
SIGNALING (22)
SIGNALING (23)
SIGNALING (24)
SIGNALING (25)
SIGNALING (26)
SIGNALING (27)
SIGNALING (28)
SIGNALING (29)
SIGNALING (30)
SIGNALING (31)
SIGNALING (32)
SIGNALING (33)
SIGNALING (34)
SIGNALING (36)
SIGNALING (40)
SIGNALING (42)
SIGNALING (43)
SIGNALING (44)
SIGNALING (45)
SIGNALING (46)
SIGNALING (49)
SIGNALING (50)
SIGNALING (51)
SIGNALING (52)
SIGNALING (53)
SIGNALING (54)
SIGNALING (55)
SIGNALING (57)
SIGNALING (58)
SIGNALING (59)
SIGNALING (60)
SIGNALING (61)
SIGNALING (62)
SIGNALING (63)
SIGNALING (64)
SIGNALING (65)
SIGNALING (66)
SIGNALING (68)
SIGNALING (69)
SIGNALING (70)
SIGNALING (71)
SIGNALING (72)
SIGNALING (73)
SIGNALING (74)
SIGNALING (75)
SIGNALING (76)
SIGNALING (77)
SIGNALING (78)
SIGNALING (79)
SIGNALING (80)
SIGNALING (81)
SIGNALING (82)
SIGNALING (83)
SIGNALING (84)
SIGNALING (85)
SIGNALING (86)
SIGNALING (87)
SIGNALING (88)
SIGNALING (89)
SIGNALING (90)
SIGNALING (91)
SIGNALING (92)
SIGNALING (93)
SIGNALING (94)
SIGNALING (95)
SIGNALING (96)
SIGNALING (97)
SIGNALING (98)
SIGNALING (99)
SIGNALING (100)
SIGNALING (101)
SIGNALING (102)
SIGNALING (103)
SIGNALING (104)
SIGNALING (105)
SIGNALING (106)
SIGNALING (107)
SIGNALING (108)
SIGNALING (109)
SIGNALING (110)
SIGNALING (111)
SIGNALING (112)
SIGNALING (113)
SIGNALING (114)
SIGNALING (115)
SIGNALING (116)
SIGNALING (117)
SIGNALING (118)
SIGNALING (119)
SIGNALING (120)
SIGNALING (121)
SIGNALING (122)
SIGNALING (124)
SIGNALING (125)
SIGNALING (126)
SIGNALING (127)
SIGNALING (132)
SIGNALING (133)
SIGNALING (134)
SIGNALING (135)
SIGNALING (136)
SIGNALING (137)
SIGNALING (138)
SIGNALING (139)
SIGNALING (140)
SIGNALING (141)
SIGNALING (142)
SIGNALING (143)
SIGNALING (144)
SIGNALING (145)
SIGNALING (146)
SIGNALING (147)
SIGNALING (148)
SIGNALING (150)
SIGNALING (151)
SIGNALING (152)
SIGNALING (166)
SIGNALING (167)
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 - Signaling (25)
Unanswered Unblocking Message - Signaling (26)
Unanswered Circuit Group Blocking - Signaling (27)
Unanswered Circuit Group Unblocking - Signaling (28)
Unanswered Circuit Query Message - Signaling (29)
Unanswered Circuit Validation Test - Signaling (30)
Unanswered Reset Circuit - Signaling (31)
Unanswered Group Reset - Signaling (32)
Unanswered Release - Signaling (33)
Unanswered Continuity Check Request - Signaling (34)
Trunk Locally Blocked - Signaling (36)
Trunk Remotely Blocked - Signaling (40)
Continuity Testing Message Received on the Specified Circuit Identification Code - Signaling (42)
Release Complete Received in Response to Reset Circuit Message on the Specified Circuit Identification Code - Signaling (43)
Continuity Recheck is Performed on Specified Circuit Identification Code - Signaling (44)
Circuit is UNEQUIPPED on Remote Side - Signaling (45)
Specified Circuit Identification Code is Invalid for the Operation - Signaling (46)
A General Processing Error Encountered - Signaling (49)
Unexpected Message for the Call State is Received: Clear Call - Signaling (50)
Set Trunk State as Remotely Unequipped - Signaling (51)
Set Trunk State as NOT Remotely Blocked - Signaling (52)
Set Trunk State as Remotely Blocked - Signaling (53)
Circuit Validation Test Aborted - Signaling (54)
Circuit Validation Successful - Signaling (55)
Continuity Recheck Failed - Signaling (57)
Continuity Recheck Successful - Signaling (58)
Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)
Integrated Services Digital Network STATUS Message Containing Error Indication Received - Signaling (60)
Trunk Operational State Changed by Service Message - Signaling (61)
Received Integrated Services Digital Network RESTART Message - Signaling (62)
Media Gateway/Termination Faulty - Signaling (63)
Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)
Media Gateway Adapter Running out of Heap Memory - Signaling (65)
Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)
Media Gateway Endpoints are out of Service at Gateway - Signaling (68)
Call Agent and Feature Server Communication Message Timeout - Signaling (69)
Integrated Services Digital Network Unable to Restore D-channel Due to Failed Communication - Signaling (70)
Integrated Services Digital Network Unable to Establish D-channel - Signaling (71)
Integrated Services Digital Network - Calls Lost Due to D-channel Down for Period of Time - Signaling (72)
Integrated Services Digital Network - Unable to Send RESTART Due to RESTART Timer Expired - Signaling (73)
Integrated Services Digital Network: Unable to Send the SERVICE Due to the SERVICE Timer Expired - Signaling (74)
Signaling System 7 Stack not Ready - Signaling (75)
Timeout on Remote Instance - Signaling (76)
Integrated Services Digital Network D-channel Switchover for Non-Facility Associated Signaling - Signaling (77)
Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)
Media Gateway Unreachable - Signaling (79)
Out of Bounds, Memory/Socket Error - Signaling (80)
Insufficient Heap Memory - Signaling (81) (H.323)
Insufficient Shared Memory Pools - Signaling (82) (H.323)
Error While Binding to Socket - Signaling (83)
Reached Maximum Socket Limit - Signaling (84) (H.323)
Initialization Failure - Signaling (85)
Remote H323 Gateway is not Reachable - Signaling (86) (H.323)
H323 Message Parsing Error - Signaling (87) (H.323)
H323 Message Encoding Error - Signaling (88) (H.323)
Gatekeeper not Available/Reachable - Signaling (89)
Alternate Gatekeeper is not Responding - Signaling (90)
Endpoint Security Violation - Signaling (91) (H.323)
Invalid Call Identifier - Signaling (92)
Invalid Call Reference Value - Signaling (93)
Invalid Conference Identifier - Signaling (94)
Invalid Message from the Network - Signaling (95)
Internal Call Processing Error - Signaling (96)
Insufficient Information to Complete Call - Signaling (97)
H323 Protocol Inconsistencies - Signaling (98) (H.323)
Abnormal Call Clearing - Signaling (99)
Codec Negotiation Failed - Signaling (100)
Per Call Security Violation - Signaling (101)
H323 Network Congested - Signaling (102) (H.323)
Aggregation Connection Down - Signaling (103)
Aggregation Unable To Establish Connection - Signaling (104)
Aggregation Gate Set Failed - Signaling (105)
Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)
Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)
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)
Softswitch Audit Released Stale Memory - Signaling (148)
Stream Control Transmission Protocol Association Congested - Signaling (150)
Termination Permanent Error Code Received - Signaling (151)
Termination Transient Error Received - Signaling (152)
No Routing Keys are Active - Signal (166)
No Signaling Gateways are Active - Signaling (167)
Troubleshooting Signaling Alarms
Socket Failure - Signaling (7)
Media Gateway Control Protocol
Session Initiation Protocol
Session Initiation Protocol Message Receive Failure - Signaling (8)
Session Initiation Protocol
Timeout on Internet Protocol Address - Signaling (9)
Media Gateway Control Protocol
Session Initiation Protocol
Failed to Send Complete Session Initiation Protocol Message - Signaling (10)
Failed to Allocate Session Initiation Protocol Control Block - Signaling (11)
Feature Server is not Up or is not Responding to Call Agent - Signaling (12)
Signaling System 7 Signaling Link Down - Signaling (13)
Signal System 7 and Call Agent Fail-over Interaction
Link is Remotely Inhibited - Signaling (14)
Link is Locally Inhibited - Signaling (15)
Link is Congested - Signaling (16)
Link: Local Processor Outage - Signaling (17)
Link: Remote Processor Outage - Signaling (18)
Link Set Inaccessible - Signaling (19)
Link Set Congestion - Signaling (20)
Route Set Failure - Signaling (21)
Route Set Congested - Signaling (22)
Destination Point Code Unavailable - Signaling (23)
Destination Point Code Congested - Signaling (24)
Trunk Locally Blocked - Signaling (36)
Trunk Remotely Blocked - Signaling (40)
Auto State Change for Integrated Services Digital Network Trunk Group by Media Gateway - Signaling (59)
Media Gateway/Termination Faulty - Signaling (63)
Media Gateway Adapter Running out of Shared Memory Pools - Signaling (64)
Media Gateway Adapter Running out of Heap Memory - Signaling (65)
Call Agent Internal Error (Because of Which Media Gateway Adapter has to Start Automatically) - Signaling (66)
Media Gateway Endpoints are out of Service at Gateway - Signaling (68)
Call Agent and Feature Server Communication Message Timeout - Signaling (69)
Signaling System 7 Stack not Ready - Signaling (75)
Integrated Services Digital Network Single D-channel Down for Non-Facility Associated Signaling - Signaling (78)
Media Gateway Unreachable - Signaling (79)
Out of Bounds, Memory/Socket Error - Signaling (80)
Insufficient Heap Memory - Signaling (81) (H.323)
Insufficient Shared Memory Pools - Signaling (82) (H.323)
Error While Binding to Socket - Signaling (83)
Reached Maximum Socket Limit - Signaling (84) (H.323)
Initialization Failure - Signaling (85)
Remote H323 Gateway is not Reachable - Signaling (86) (H.323)
H323 Message Parsing Error - Signaling (87) (H.323)
H323 Message Encoding Error - Signaling (88) (H.323)
Gatekeeper not Available/Reachable - Signaling (89)
Alternate Gatekeeper is not Responding - Signaling (90)
Endpoint Security Violation - Signaling (91) (H.323)
Invalid Call Identifier - Signaling (92)
Invalid Call Reference Value - Signaling (93)
Invalid Conference Identifier - Signaling (94)
Invalid Message from the Network - Signaling (95)
Internal Call Processing Error - Signaling (96)
Insufficient Information to Complete Call - Signaling (97)
H323 Protocol Inconsistencies - Signaling (98) (H.323)
Abnormal Call Clearing - Signaling (99)
Codec Negotiation Failed - Signaling (100)
Per Call Security Violation - Signaling (101)
H323 Network Congested - Signaling (102) (H.323)
Aggregation Connection Down - Signaling (103)
Enhanced Subscriber Authentication Cisco BTS 10200 Softswitch Delivery Function Connection Down - Signaling (106)
Logical Internet Protocol Addresses not Mapped Correctly - Signaling (107)
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)
Termination Permanent Error Code Received - Signaling (151)
Signaling Troubleshooting
Revised: December 2, 2008, OL-8000-30
Introduction
This chapter provides the information needed to monitor and troubleshoot Signaling events and alarms. This chapter is divided into the following sections:
•
Signaling Events and Alarms - Provides a brief overview of each Signaling event and alarm.
•Monitoring Signaling Events - Provides the information needed to monitor and correct Signaling events.
•Troubleshooting Signaling Alarms - Provides the information needed to troubleshoot and correct Signaling alarms.
Caution The use of the
UNIX ifconfig down command on any signaling interface to test or troubleshoot network or interface failures of the Cisco BTS 10200 Softswitch Signaling Interface may lead to undesirable consequences or conditions.
Note The following billing records are created when a call is rejected due to overload conditions:
· SS7 termination cause code 42
· Cable signaling stop event cause code "resource unavailable"
Calls rejected by the signaling adapter will not generate a billing record.
Signaling Events and Alarms
This section provides a brief overview of the Signaling events and alarms for the Cisco BTS 10200 Softswitch in numerical order. Table 10-1 lists all signaling events and alarms by severity.
Note Click the Signaling message number in Table 10-1 to display information about the event or alarm.
SIGNALING (1)
For additional information, refer to the "Test Report - Signaling (1)" section.
DESCRIPTION
|
Test Report
|
SEVERITY
|
Information (INFO)
|
THRESHOLD
|
10000
|
THROTTLE
|
0
|
Note SIGNALING (2) and SIGNALING (3) are 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
|
Issued when a signaling adapter has received an invalid message from the specified endpoint.
|
PRIMARY
ACTION
|
Monitor the associated signaling link to see if there is an interruption of service on the link.
|
SECONDARY
ACTION
|
If there is a communication problem, restart the link.
|
TERNARY
ACTION
|
Verify that the version of the protocol used by the device at the endpoint is consistent with the version expected by the call agent.
|
SUBSEQUENT
ACTION
|
If there is a mismatch, then either the endpoint or call agent must be re-provisioned.
|
Note SIGNALING (5) is not used.
SIGNALING (6)
To monitor and correct the cause of the event, refer to the "Database Module Function Call Failure - Signaling (6)" section.
DESCRIPTION
|
Database Module Function Call Failure
|
SEVERITY
|
WARNING
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Endpoint Name - STRING [40]
Return Code - FOUR_BYTES
Function Name - STRING [64]
Calling Function - STRING [64]
Index - FOUR_BYTES
|
PRIMARY
CAUSE
|
A signaling adapter has detected an error while accessing a database interface.
|
PRIMARY
ACTION
|
If the database that the adapter attempted to access is not available, restart the associated process.
|
SECONDARY
ACTION
|
If an incompatible versions of the signaling adapter process and the database processes are present on the system, correct the error and restart the processes.
|
SIGNALING (7)
To troubleshoot and correct the cause of the alarm, refer to the "Socket Failure - Signaling (7)" section.
DESCRIPTION
|
Socket Failure
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Reason Text - STRING [30]
|
PRIMARY
CAUSE
|
Issued when there is a failure in creating/binding to the User Datagram Protocol (UDP) socket.
|
PRIMARY
ACTION
|
Verify there is no conflict in port assignment with other processes in the system and ensure no previous instance of the same process is still running.
|
SECONDARY
CAUSE
|
Software logic problem.
|
SECONDARY
ACTION
|
Contact Cisco Support. (Contact Cisco Technical Assistance Center (TAC).)
|
Refer to the "Obtaining Technical Assistance" section on page liv 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
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Reason Text - STRING [50]
|
PRIMARY
CAUSE
|
Operating system level network errors or invalid network configuration.
|
PRIMARY
ACTION
|
Have your network administrator resolve network errors. Contact Cisco TAC if you need assistance. Manually clear alarm. Restart this call agent instance using the platform start command.
|
Refer to the "Obtaining Technical Assistance" section on page liv 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
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
MGW/Term Name - STRING [80]
Gateway Type - STRING [32]
Possible Cause - STRING [32]
|
PRIMARY
CAUSE
|
Issued when opticall is unable to communicate with a gateway.
|
PRIMARY
ACTION
|
Verify that the gateway is both configured for service and that it has been set in service.
|
SECONDARY
ACTION
|
Attempt to ping the gateway using the Internet Protocol (IP) address from the event report. If the ping is not successful, then diagnose the issue that prevents the address from being reached.
|
TERNARY
ACTION
|
Use the status media gateway (MGW) identification (ID) = xxx, where xxx is the IP address given in the event report. If the status is not in service (INS), then use control mgw command to put it in service.
|
SIGNALING (10)
To troubleshoot and correct the cause of the alarm, refer to the "Failed to Send Complete Session Initiation Protocol Message - Signaling (10)" section.
DESCRIPTION
|
Failed to Send Complete Session Initiation Protocol Message
|
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.
|
Refer to the "Obtaining Technical Assistance" section on page liv 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
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Size - TWO_BYTES
Detail - STRING [80]
|
PRIMARY
CAUSE
|
Issued when there is not enough memory to allocate a SIP call control block.
|
PRIMARY
ACTION
|
Increase the SIP call control block (CCB) count specified in mem.cfg file.
|
SECONDARY
ACTION
|
Restart call agent to take effect.
|
SIGNALING (12)
To troubleshoot and correct the cause of the alarm, refer to the "Feature Server is not Up or is not Responding to Call Agent - Signaling (12)" section.
DESCRIPTION
|
Feature Server is not Up or is not Responding to Call Agent
|
SEVERITY
|
CRITICAL
|
THRESHOLD
|
30
|
THROTTLE
|
0
|
DATAWORDS
|
Domain Name of FS - STRING [65]
Feature Server ID - STRING [20]
|
PRIMARY
CAUSE
|
Feature server platform is down or is not operating properly.
|
PRIMARY
ACTION
|
Restart the applicable feature server.
|
SIGNALING (13)
To troubleshoot and correct the cause of the alarm, refer to the "Signaling System 7 Signaling Link Down - Signaling (13)" section.
DESCRIPTION
|
Signaling System 7 Signaling Link Down
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link_Number - ONE_BYTE
Link_Name - STRING [25]
|
PRIMARY
CAUSE
|
Signaling System 7 (SS7) trunk group may be out-of-service (OOS).
|
PRIMARY
ACTION
|
Use control ss7-trunk-grp to place the trunk group in service (INS).
|
SECONDARY
CAUSE
|
The local Ulticom stack may be down.
|
SECONDARY
ACTION
|
Run the Ulticom stack again.
|
TERNARY
CAUSE
|
SS7 link may be disconnected or faulty.
|
TERNARY
ACTION
|
Check the Ulticom local configuration.
|
SUBSEQUENT
CAUSE
|
Remote SS7 signaling site may be down or incorrectly configured.
|
SUBSEQUENT
ACTION
|
Check the Ulticom remote configuration.
|
SIGNALING (14)
To troubleshoot and correct the cause of the alarm, refer to the "Link is Remotely Inhibited - Signaling (14)" section.
DESCRIPTION
|
Link is Remotely Inhibited
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link - ONE_BYTE
Link Name - STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified Signaling System 7 (SS7) link is inhibited at the remote end.
|
PRIMARY
ACTION
|
Monitor events at the network level for any related to the specified SS7 link. Restorative actions needs to be taken on the remote end.
|
SIGNALING (15)
To troubleshoot and correct the cause of the alarm, refer to the "Link is Locally Inhibited - Signaling (15)" section.
DESCRIPTION
|
Link is Locally Inhibited
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No - ONE_BYTE
Link Name - STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link is inhibited at the local end.
|
PRIMARY
ACTION
|
Verify that the SS7 signaling adapter process is running and that the SS7 interface card(s) are in service.
|
SECONDARY
ACTION
|
If a component is found to be non-operational, restore it to service.
|
SIGNALING (16)
To troubleshoot and correct the cause of the alarm, refer to the "Link is Congested - Signaling (16)" section.
DESCRIPTION
|
Link is Congested
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No - ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link is experiencing congestion.
|
PRIMARY
ACTION
|
Monitor event reports at the network level to determine if the traffic load on the specified SS7 link is too high on the local end, or if the remote end is lagging in processing the traffic.
|
SECONDARY
ACTION
|
Verify that the SS7 link has not degraded in quality.
|
TERNARY
ACTION
|
Verify that the traffic load has not become unbalanced if multiple SS7 links are used.
|
SUBSEQUENT
ACTION
|
Verify that local SS7 signaling adapter process is running normally.
|
SIGNALING (17)
To troubleshoot and correct the cause of the alarm, refer to the "Link: Local Processor Outage - Signaling (17)" section.
DESCRIPTION
|
Link: Local Processor Outage
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No - ONE_BYTE
Link Name - STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link has experienced a processor outage.
|
PRIMARY
ACTION
|
Monitor the system for maintenance event reports associated with the signaling adapter or underlying platform instance that support the specified SS7 link. Verify that the process and or platform are restarted and returned to service.
|
SIGNALING (18)
To troubleshoot and correct the cause of the alarm, refer to the "Link: Remote Processor Outage - Signaling (18)" section.
DESCRIPTION
|
Link: Remote Processor Outage
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link No - ONE_BYTE
Link Name - STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link has experienced a processor outage.
|
PRIMARY
ACTION
|
Monitor the network level event reports for any events associated with the processing complex used by the specified SS7 link. Verify that the SS7 link is returned to service.
|
SIGNALING (19)
To troubleshoot and correct the cause of the alarm, refer to the "Link Set Inaccessible - Signaling (19)" section.
DESCRIPTION
|
Link Set Inaccessible
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link Set No - ONE_BYTE
Link Set Name - STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link set is inaccessible.
|
PRIMARY
ACTION
|
If the SS7 signaling adapter is not running normally and the associated call agent platform is not active, return them to service.
|
SIGNALING (20)
To troubleshoot and correct the cause of the alarm, refer to the "Link Set Congestion - Signaling (20)" section.
DESCRIPTION
|
Link Set Congestion
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Link Set No - ONE_BYTE
Link Set Name - STRING [8]
Congestion Level - ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified SS7 link set is experiencing congestion.
|
PRIMARY
ACTION
|
Monitor event reports at the network level to determine if the traffic load on the specified SS7 link set is too high on the local end, or if the remote end is lagging in processing the traffic.
|
SECONDARY
ACTION
|
Verify that the SS7 link set has not degraded in quality.
|
TERNARY
ACTION
|
Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used.
|
SUBSEQUENT
ACTION
|
Verify that local SS7 signaling adapter process is running normally.
|
SIGNALING (21)
To troubleshoot and correct the cause of the alarm, refer to the "Route Set Failure - Signaling (21)" section.
DESCRIPTION
|
Route Set Failure
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
200
|
THROTTLE
|
0
|
DATAWORDS
|
Route Set No - TWO_BYTES
Route Set Name - STRING [8]
|
PRIMARY
CAUSE
|
Issued when the specified route set has experienced a failure.
|
PRIMARY
ACTION
|
Verify that the processing complex supporting the route set is functional.
|
SECONDARY
ACTION
|
Monitor event reports at the network level to determine the failing component and verify its restoral to service.
|
SIGNALING (22)
To troubleshoot and correct the cause of the alarm, refer to the "Route Set Congested - Signaling (22)" section.
DESCRIPTION
|
Route Set Congested
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
Route Set No - TWO_BYTES
Route Set Name - STRING [8]
Congestion Level - ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified route set is experiencing congestion.
|
PRIMARY
ACTION
|
Monitor event reports at the network level to determine if the traffic load on the specified SS7 link set is too high on the local end, or if the remote end is lagging in processing the traffic.
|
SECONDARY
ACTION
|
Verify that the SS7 link set has not degraded in quality.
|
TERNARY
ACTION
|
Verify that the traffic load has not become unbalanced if multiple SS7 link sets are used.
|
SUBSEQUENT
ACTION
|
Verify that local SS7 signaling adapter process is running normally.
|
SIGNALING (23)
To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Unavailable - Signaling (23)" section.
DESCRIPTION
|
Destination Point Code Unavailable
|
SEVERITY
|
MAJOR
|
THRESHOLD
|
200
|
THROTTLE
|
0
|
DATAWORDS
|
DPC - STRING [12]
|
PRIMARY
CAUSE
|
Issued when the specified destination point code (DPC) is not available. This is usually caused by one of the following:
1) A failure in the affected DPC.
2) An unavailable route between the Cisco BTS 10200 Softswitch and the affected DPC.
|
PRIMARY
ACTION
|
Verify that alternate routing has been assigned for traffic destined to the affected DPC.
|
SIGNALING (24)
To troubleshoot and correct the cause of the alarm, refer to the "Destination Point Code Congested - Signaling (24)" section.
DESCRIPTION
|
Destination Point Code Congested
|
SEVERITY
|
MINOR
|
THRESHOLD
|
100
|
THROTTLE
|
0
|
DATAWORDS
|
DPC - STRING [12]
DPC Type - ONE_BYTE
Congestion Level - ONE_BYTE
|
PRIMARY
CAUSE
|
Issued when the specified destination point code is congested.
|
PRIMARY
ACTION
|
Monitor event reports at the network level to determine if the traffic load to the specified DPC is too high on the local end, or if the remote end is lagging in processing the traffic.
|
SIGNALING (25)
To monitor and correct the cause of the event, refer to the "Unanswered Blocking - Signaling (25)" section.
DESCRIPTION
|
Unanswered Blocking
|
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
|
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 - Signaling (27)" section.
DESCRIPTION
|
Unanswered Circuit Group Blocking
|
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.
|
|
