CSCF User Subscribed Media Profile Id Not Defined
Call Session Control Function

Contents

1Introduction
1.1Alarm Description
1.2Prerequisites

2

Procedure

1   Introduction

This instruction concerns alarm handling.

1.1   Alarm Description

The threshold alarm CSCF User Subscribed Media Profile Id Not Defined is issued when the Subscribed Media Profile Identifier (SMP ID), included in the user profile of a user, is not configured in the Call Session Control Function (CSCF), or not correct in the Home Subscriber Server (HSS) configuration.

The alarm is associated to the Performance Management counter cscfSmpIdNotFound.

There is a counter for the number of times that the Media Authorization function in the Serving Call Session Control Function (S-CSCF) cannot find an entry in the S-CSCF configuration database for a given SMP ID. The alarm is raised when the counter cscfSmpIdNotFound has reached or exceeded its configured thresholdHigh within the time period configured by thresholdRateOfVariation and granularityPeriod.

The alarm is automatically ceased when it reaches or goes below the configured thresholdLow value.

The default values related to this alarm are: thresholdRateOfVariation=PER_GP, granularityPeriod=FIVE_MIN, thresholdHigh=2, and thresholdLow=0. This means that when the counter value is 2 or higher, the alarm is raised when the granularity period is ended. The alarm is ceased when the counter cscfSmpIdNotFound has reached a value of 0 at the end of a granularity period.

Note:  
The thresholds for raising and ceasing this alarm are configurable. The default distinguished name for the thresholds is ManagedElement=<node_name>, SystemFunctions=1, Pm=1, PmJob=CscfSessionThreshold, MeasurementReader=cscfSmpIdNotFoundMeasReader, PmThresholdMonitoring=cscfSmpIdNotFound.

It is not possible to change threshold values once they have been set. To change a threshold, first the PmThresholdMonitoring instance must be deleted and recreated with required thresholdHigh and thresholdLow.

For more information, refer to Performance Management.


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 PM counter cscfSmpIdNotFound has reached or exceeded its configured upper threshold value.

The number of times it is detected that a provisioned SMP ID, that is not configured in S-CSCF during a granularity period, has reached or exceeded the configured threshold.

The provisioned user profile data in HSS and the S-CSCF configuration data are not synchronized.

The subscriber media profile configuration is either missing in S-CSCF or incorrectly provisioned in HSS.

The optional HSS provisioned SMP ID in the user profile is not used by the Subscriber Media Profile policy handling in S-CSCF. This means that no media authorization is done for these users, resulting in that all media being granted.

Note:  
An 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

6684685

Managed Object Class

MeasurementReader

Managed Object Instance

ManagedElement=<node_name>,SystemFunctions=1, Pm=1, PmJob=CscfSessionThreshold, MeasurementReader=cscfSmpIdNotFoundMeasReader

Specific Problem

CSCF User Subscribed Media Profile Id Not Defined

Event Type

processingError (4)

Probable Cause

x733ConfigurationOrCustomizationError (307)

Additional Text

cscfSmpIdNotFound. There is no SMP Id defined. Add Subscribed Media Profile Id to the configuration database

Perceived Severity

minor (5)

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

Note:  
If the reason for the alarm has disappeared after the granularity period, the alarm automatically ceases.

Do the following:

  1. Check if the provisioning in HSS is incorrect or if the SMP ID is missing in the S-CSCF configuration.
  2. If the SMP ID is missing in the S-CSCF, add an SMP ID, which matches the HSS-SubscribedMediaProfile of the user profile in the HSS, to the CSCF configuration database:

    To do this, add a new cscfSmpAuthorizationPolicyEntry named cscfSmpAuthorizationPolicyId=<n> where <n> corresponds to the HSS-SubscribedMediaProfile, which is configured for the specific user in the HSS.

  3. If provisioned SMP ID is not to be provisioned in HSS, change or delete the SMP ID indicated in HSS-SubscribedMediaProfile so that it is aligned with the configuration in the CSCF.
  4. If the cause is that the alarm threshold is set too low, adjust the alarm threshold.
  5. Confirm that the alarm has ceased. If the alarm remains, consult the next level of maintenance support. Further actions are outside the scope of this instruction.
  6. Job is completed.


Copyright

© Ericsson AB 2016. All rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design and manufacturing. Ericsson shall have no liability for any error or damage of any kind resulting from the use of this document.

Trademark List
All trademarks mentioned herein are the property of their respective owners. These are shown in the document Trademark Information.

    CSCF User Subscribed Media Profile Id Not Defined         Call Session Control Function