CSCF Shared Initial Filter Criteria Priority Collision
Call Session Control Function

Contents


1   Alarm Description

The CSCF Shared Initial Filter Criteria Priority Collision alarm is raised when two or more Initial Filter Criteria (IFC) within a user profile have the same priority number (that is, at least one of the involved IFC is defined in a locally configured Shared Initial Filter Criteria (SiFC) set), or when an internal DBN error occurs in synchronizing modified SiFC configuration.

Many users can experience priority collisions, but only the first one detected, is reported in the alarm.

Table 1    CSCF Shared Initial Filter Criteria Priority Collision Alarm Causes

Alarm Cause

Description

Fault Reason

Fault Location

Impact

Two or more IFCs within a user profile have the same priority number, or an internal DBN error occurs in synchronizing modified SiFC configuration.

A priority collision comparing IFCs in the user profile and configured SiFC is detected, or an internal DBN error occurs in synchronizing modified SiFC configuration.

    IFC priority conflicts can occur in the following cases:

  • During an initial registration when receiving the user profile from the HSS over the Cx interface.

  • When a user profile update is initiated by the HSS.

  • During the first traffic event of a registered user following the synchronization of the SiFC definitions.


An internal DBN error can occur when there is an internal execution error in synchronizing modified SiFC configuration.

The possible cause is that the scscfIfcPriority value associated with a locally defined IFC is used twice within the same user profile (Public_Id) or that a priority among the user profile in the IFC definitions at the HSS, is incorrect.


The possible cause of DBN error is an internal execution error in synchronizing modified SiFC configuration.

The consequences for CSCF if the alarm is not solved can be that the CSCF stops providing service to users experiencing an IFC Priority Collision, or an internal DBN error in synchronizing modified SiFC configuration.


If the priority collision is detected at initial registration, the CSCF rejects the profile update message and initiates an administrative deregistration of the user. If the priority collision is detected during traffic, the traffic event is rejected.

 
 
 
Note:  
This alarm can appear as a result of maintenance activity.

Table 2    CSCF Shared Initial Filter Criteria Priority Collision Alarm Attributes

Attribute Name

Attribute Value

Major Type

193

Minor Type

6684698

Managed Object Class

CSCF-Application

Managed Object Instance

ManagedElement=<node_name>,CscfFunction=1,CSCF-Application=CSCF

Specific Problem

CSCF Shared Initial Filter Criteria Priority Collision

Event Type

processingErrorAlarm (4)

Probable Cause

x733ConfigurationOrCustomizationError (307)

Additional Text

Format: Public_Id=<tel_url> or <sip_url>, ScscfSharedIfcId=<Id_value>, ScscfSharedIfcId=<Id_value>, ScscfIfcPriority=<priority_value>


(1)(2)


or


Failed to synchronize SiFC configuration data due to [error reason]. Synchronization process is aborted..., where [error reason](3) can be ignored.

Perceived Severity

critical (3)

(1)  Example: Public_Id=tel:+4812299410000, ScscfSharedIfcId=2, ScscfSharedIfcId=1, ScscfIfcPriority=0

(2)  Only one ScscfSharedIfcId is present when the collision involves a filter criteria explicitly defined in the user profile.

(3)  Some examples of [error reason] are: " Failed to read SiFC persistent object - POT does not exist.", " Failed to read SiFC persistent object - database operation error.", " Failed to delete SiFC persistent object.", " Failed to update SiFC persistent object.", " Invalid SiFC ID. Must be of integer [0..n].", " Failed to build traffic DBN.", and " Traffic database transaction error.".


2   Procedure

2.1   Handle Alarm CSCF Shared Initial Filter Criteria Priority Collision

Prerequisites

Steps

  1. Find which IFCs and SiFCs are configured with the same priority.
  2. Make sure that all IFCs and SiFCs have different priorities.

    This ensures a predictable service behavior.

  3. Is the value of the Additional Text alarm attribute Failed to synchronize SiFC configuration data due to [error reason]. Synchronization process is aborted...?

    Yes: Proceed to Section 2.2 Handle Reason Internal DBN Error.

    No: Continue with the next step.

  4. If a change is required in the user profile of the identified user, update the information in the HSS.
  5. If a change is required in the IFC definitions at the HSS of the identified user, update the information in the HSS.
  6. If a change is required in the SiFC definitions at the CSCF, modify the scscfIfcPriority of a filter criteria defined within one of the identified SiFCs to avoid the conflict.
  7. Set scscfSharedIfcSynchronization to true.
    Note:  
    This step is also valid if the information was only updated in the HSS.

    For more information about the parameters scscfIfcPriority and scscfSharedIfcSynchronization, refer to Managed Object Model (MOM) and CSCF Configuration Management.

    Result:
    The CSCF application is notified that a new SiFC configuration must be used and the alarm ceases.
  8. Has the alarm ceased after the synchronization?

    Yes: Proceed to Step 10.

    No: Perform one of the following options:

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

    Further actions are outside the scope of this instruction.

  10. Job is completed.

2.2   Handle Reason Internal DBN Error

Steps

  1. Set the scscfSharedIfcSynchronization parameter to true.

    This is needed because it indicates an internal DBN error in synchronizing modified SiFC configuration occurs.

  2. Has the alarm ceased after the synchronization?

    Yes: Proceed with Step 4.

    No: Continue with the next step.

  3. If the alarm is not ceased, consult the next level of maintenance support.

    Further actions are outside the scope of this instruction.

  4. Job is completed.

2.3   Flowchart to CSCF Shared Initial Filter Criteria Priority Collision

Figure 1   Handle Alarm CSCF Shared Initial Filter Criteria Priority Collision Flowchart

Legal | © Ericsson AB 2016, 2018