Contents

1   Alarm Description

The alarm is raised 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.

Table 1    CSCF SIP Interface Already Used 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:  

This alarm can appear as a result of maintenance activity.

Table 2    CSCF SIP Interface Already Used 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

2   Procedure

2.1   Handle Alarm CSCF SIP Interface Already Used

Prerequisites

• This instruction references the following document:
  • Managed Object Model (MOM)
• No tools are required.
• The following condition must apply:
  • The alarm is raised.

Steps

1. Is a reconfiguration planned on the node that requires to take the node out of service?

   Yes: Ignore this alarm until the reconfiguration has been completed and proceed to Step 8.

   No: Continue to the next step.

2. Write down which interface issues the alarm, indicated in the Managed Object Instance alarm attribute.
3. Is the corresponding CSCF application disabled and not planned to be enabled?

   Refer to attributes cscfISPBehavior, ecscfEnabled, eatfEnabled, and bcfEnabled.

   Yes: Proceed to Step 8.

   No: Continue to the next step.

4. Find which other existing XNetworkInterfaceEntry has the same address configured to identify the faulty NetworkInterface in the Managed Object Instance alarm attribute.
5. Update the faulty NetworkInterface configuration with the latest site configuration information.
6. Has the alarm ceased after correcting the NetworkInterface configuration?

   Yes: Proceed to Step 8.

   No: Perform one of the following options:

   • Repeat Step 4 and Step 5. Check for more missing parameters, or make sure that the parameters were configured correctly.
   • Continue to the next step.
7. If the alarm is not ceased, consult the next level of maintenance support.

   Further actions are outside the scope of this instruction.

8. Job is completed.