| 1 | Introduction |
| 1.1 | Alarm Description |
| 1.2 | Prerequisites |
2 | Procedure |
| 2.1 | Analyze the Alarm |
| 2.2 | Actions to Clear the Alarm |
1 Introduction
This instruction concerns alarm handling.
1.1 Alarm Description
The alarm indicates that the Emergency CSCF (E-CSCF) does not have sufficient configuration to process traffic and the ecscfOperationalState is DISABLED. This configuration error prevents the application subsystem from processing traffic.
The possible causes are as follows:
- The E-CSCF interface is not configured.
- One or more critical parameters are not set.
The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.
|
Alarm Cause |
Description |
Fault Reason |
Fault Location |
Impact |
|---|---|---|---|---|
|
The E-CSCF does not have sufficient mandatory configuration to process traffic. |
The E-CSCF is misconfigured, or not configured, and is therefore prevented from processing traffic. |
The E-CSCF mandatory data (interface or domain information) is misconfigured or missing. |
The attribute ecscfNetworkInterfaceEntry is placed in the MOC EcscfNetworkInterface, and the attribute ecscfDomainNameEntry is placed in the MOC CscfEmergencyClass. One or both attributes contain erroneous or missing configuration data. |
The E-CSCF interface is not configured to receive or send traffic, resulting in the E-CSCF being unreachable for other nodes, such as P-CSCF, which means that emergency calls fail. |
- Note:
- The alarm can appear as a result of maintenance activity.
The alarm attributes are listed and explained in Table 2.
|
Attribute Name |
Attribute Value |
|---|---|
|
Major Type |
193 |
|
Minor Type |
6684687 |
|
Managed Object Class |
Ecscf |
|
Managed Object Instance |
ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF,Ecscf=0 |
|
Specific Problem |
E-CSCF Mandatory Data Not Configured |
|
Event Type |
processingErrorAlarm (4) |
|
Probable Cause |
x733ConfigurationOrCustomizationError (307) |
|
Additional Text |
Check: EcscfNetworkInterface and/or ecscfDomainNameEntry |
|
Perceived Severity |
critical (3) |
1.2 Prerequisites
This section provides information on the documents, tools, and conditions that apply to the procedure.
1.2.1 Documents
This instruction references the following documents:
1.2.2 Tools
No tools are required.
1.2.3 Conditions
No conditions.
2 Procedure
This section describes the procedure to follow when this alarm is received.
2.1 Analyze the Alarm
Do the following:
- Check if there is a reconfiguration planned on the node requiring that the node must be taken out of service. If so, ignore this alarm until the reconfiguration has been completed.
2.2 Actions to Clear the Alarm
Do the following:
- If the E-CSCF application is not to be used, disable it by setting ecscfEnabled=false.
- Check that the E-CSCF network interface is properly configured in the configuration parameter ecscfNetworkInterfaceEntry.
- Check that the E-CSCF domain name is properly configured in the configuration parameter ecscfDomainNameEntry. For more information about configuration management parameters, refer to Managed Object Model (MOM) and CSCF Configuration Management.
- Confirm that the alarm ceases after the configuration is corrected. If not, repeat Step 2 to Step 4. Check for more missing parameters, or check that the parameters were configured correctly.
- If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.
- Job is completed.

Contents