Contents

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The alarm is issued when the port assigned is already in use by another Session Initiation Protocol (SIP) application. This configuration error prevents the affected application subsystem from processing traffic on that port.

The possible alarm causes and the corresponding fault reasons, fault locations, and impacts are described in Table 1.

Table 1    Alarm Causes

Alarm Cause	Description	Fault Reason	Fault Location	Impact
The SIP network interface port is already used.	Operator has tried to assign a SIP interface port for a network interface, but the given port is already assigned to another SIP network interface.	Another SIP application is already assigned to the port, which the operator attempts to allocate for the SIP interface.	Either the SIP interface is already incorrectly configured or the new SIP interface must be assigned to another port for its network interface.	The attempted configuration of the SIP network interface indicated in the alarm is not taken into service.

Note:  

The alarm can appear as a result of maintenance activity.

The alarm attributes are listed and explained in Table 2.

Table 2    Alarm Attributes

Attribute Name	Attribute Value
Major Type	193
Minor Type	6684676
Managed Object Class	IcscfNetworkInterface or PcscfNetworkInterface or ScscfNetworkInterface or BcfNetworkInterface or EcscfNetworkInterface or EatfNetworkInterfaceEntry
Managed Object Instance	ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF,CscfNwIfContainer=0,XNwIfs=0,XNetworkInterface=<protocol>:<IP-address>:<port>(1)(2) OR ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF,CscfNwIfContainer=0,EatfNwIfs=0,EatfNetworkInterfaceEntry=<protocol>:<IP-address>:<port>
Specific Problem	CSCF SIP Interface Already Used
Event Type	processingErrorAlarm (4)
Probable Cause	x733ConfigurationOrCustomizationError (307)
Additional Text	Check the conflict of XNetworkInterface with other interfaces using the port <protocol>:<IP-address>:<port>(3)(4) OR Check the conflict of EatfNetworkInterfaceEntry with other interfaces using the port <protocol>:<IP-address>:<port>
Perceived Severity	critical (3)

(1)  X represents Icscf, Pcscf, Scscf, Bcf or Ecscf

(2)  Example: ManagedElement=CSCF,CscfFunction=1,CSCF-Application=CSCF,CscfNwIfContainer=0,IcscfNwIfs=0,IcscfNetworkInterface=UDP:192.168.10.201:5060

(3)  X represents Icscf, Pcscf, Scscf, Ecscf or Bcf

(4)  Example: Check the conflict of IcscfNetworkInterface with other interfaces using the port UDP:192.168.10.201:5060

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:

• Managed Object Model (MOM)

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:

1. 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. Check if the interface issuing the alarm, indicated in the Managed Object Instance, is supposed to be configured. The currently enabled applications are configured by cscfISPBehavior, ecscfEnabled, eatfEnabled and bcfEnabled. If the corresponding CSCF application is not enabled, or not planned to be enabled, the alarm can be ignored.

2.2   Actions to Clear the Alarm

Do the following:

1. Check the Managed Object Instance information of the alarm, and find which other existing XNetworkInterfaceEntry that has the same address configured to identify the faulty NetworkInterface.
2. Correct the faulty NetworkInterface configuration by using the latest site configuration information.
3. Confirm that the alarm ceases after the NetworkInterface configuration is corrected. If not, repeat Step 1 and Step 2. Check for more missing parameters or check if the parameters were configured correctly.
4. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.
5. Job is completed.