Features may be applied directly to individual subscribers and those direct subscriptions override feature settings from the associated Feature Profile (if any). Overrides may be performed for an entire feature or for just a specific attribute of a feature.
The following actions are possible for a feature during subscriber management:
Add this feature at the subscriber level and/or replace any existing definition of the feature that the subscriber might have at the feature profile level or directly at the subscriber level.
As a result, the feature is in Assigned
state on subscriber level (see below).
The feature must already exist from either being previously provisioned at the Feature Profile Level (inherited) or provisioned directly at the subscriber level.
The administrator can "locally" overwrite the feature data using this operation.
"Local" feature data modifications do not change the assignment state of the feature.
The result of this action depends on the feature's Assignment State
(see below) at the time it is executed:
Assignment State = AssignedSet Feature Profile
In this case the subscriber-level settings are deleted and reverted to the settings from the associated feature profile (if any).
If there is no associated feature profile or if the feature is Not Assigned to the associated feature profile, it will be Not Assigned to the subscriber as well. Otherwise it will be Inherited from the associated Feature Profile.
Assignment State = Inherited
In this case the feature is put to the Denied state (see below).
The result of this action depends on the features' Assignment States (see below) at the time it is executed:
Assignment State = Assigned or Denied
In this case all subscriber-level settings - including state - are preserved.
Assignment State = Inherited or Not Assigned
If the feature is Not Assigned to the newly selected profile, it will be Not Assigned at the subscriber-level. Subscriber-level feature data (if any) are dropped.
If the feature is Assigned to the newly selected profile, it will be Inherited at the subscriber-level. Subscriber-level feature data (if any) are preserved if the "Preserve Subscriber Settings" option is passed to the action.
In subscriber feature settings, the Assignment
state of a feature can be one of the following:
Parent topic: Subscriber Features
This setting indicates that the feature is directly assigned to the subscriber. That is, feature status and feature attributes do not depend on the relationship of the subscriber with a Feature Profile and are not affected by changes at Feature Profiles.
This setting indicates that the subscriber is not allowed to inherit the feature from any feature profile.
Note that in OpenScope Assistant currently both the Denied
and Not Assigned
state are represented as the absence of the feature in the subscriber's list of assigned features.
The feature is not explicitely assigned to the subscriber but is inherited from the associated feature profile. If it is removed from the profile, it will automatically be removed from all "Members" (i.e. associated subscribers).
The inherited feature configuration data can be modified at the subscriber level (for some features even by the subscriber) without changing the assignment state.
For example, if the subscriber inherits a Call Forwarding Don't Answer feature, the subscriber can set its own forwarding number. The locally changed feature data will override the inherited Feature Profile feature data but the Assingment state will remain "inherited".
This value indicates that the feature is set switch wide and thus all subscribers have access to it.
Switch Wide assignment is controlled via RTP parameter, and affects all subscribers.
Currently, only the feature MCT (Malicious Call Trace) is by default assigned to all users at switch level.
How to Set a Subscriber's Feature Profile
This procedure describes how to set a subscriber's feature profile.
How to Explicitely Assign a Feature to a Subscriber
This procedure describes how to explicitely assign a feature at the subscriber level.
How to Explicitely Deny a Feature for a Subscriber
This procedure describes how to explicitely deny a feature for a subscriber.
RTP Management via Telephony Control Server Assistant