With the Call Forwarding Restrictions feature, certain traffic types can be excluded from being used during Call Forwarding execution. System-wide and subscriber specific restrictions can be enforced and apply to both Lotus Sametime Unified Telephony-based and endpoint-based call forwardings.
Traffic Types and Classes of Restriction
Since V5 of Lotus Sametime Unified Telephony, traffic type restrictions are declared in so-called Classes of Restriction
that are used in the Toll and Call Restrictions feature, the Call Forwarding Restrictions feature, the Account Code feature and the BG Authorization Code feature.
The procedure to set up a Class of Restriction can be roughly described in the following way:
- Define custom Traffic Types, if necessary
- Assign Traffic Types to new and existing Destination Codes and Code Indexes
- Create the required Classes of Restriction, comprising those traffic types that shall be restricted in any of the related features
Classes of Restriction for Call Forwarding can be configured globally (system-wide) and for individual subscribers.
Upon execution of Call Forwarding, the destination number is validated and the call may not be forwarded due to existing Call Forwarding Restrictions.
Only the Administrator is able to control Call Forwarding Restriction provisioning and not the station user.
When a subscriber attempts to set a call forwarding destination in the Lotus Sametime Unified Telephony, the system validates the destination number to see if the subscriber is allowed to forward calls to this destination. If no call forwarding restrictions are specifically assigned to the subscriber, Lotus Sametime Unified Telephony checks for a system-wide default Class of Restriction and a default restriction for call forwarding to emergency traffic types.
Activation of call forward local in the SIP endpoint or in the Lotus Sametime Unified Telephony via non-validating mechanisms (e.g. the Media Server) can occur. It is suggested the user should initiate a test call after forwarding is active to validate that call forwarding is working.
How to Provision System-wide Call Forwarding RestrictionsParent topic: Lotus Sametime Unified Telephony-based Call Forwarding Features
Call Forwarding - Unconditional (Station-controllable)
Call Forwarding on Busy (Station-controllable)
Call Forwarding on No Reply (Station-controllable)
Selective Call Forwarding (Station-controllable)
Call Forwarding - Unreachable
Enhanced Call Forwarding
Call Forwarding - Voice Mail
Call Forwarding System-Internal/External (CFSIE)
CFSIE - All Calls
CFSIE - Busy
CFSIE - Don't Answer
This procedure describes how to configure Call Forwarding Restrictions at system (i.e. switch) level. These restrictions apply to all subscribers that are not provisioned for Call Forwarding Restrictions.
How to Provision Call Forwarding Restrictions for Subscribers
This procedure describes how to configure Call Forwarding Restrictions at the feature profile or subscriber level. Feature profiles, in turn, can be created and configured at the switch level or the BG (Business Group) level. At the subscriber level, the previously assigned feature profile can be overwritten to selectively enable, disable or modify the feature configuration for the particular subscriber. Those subscriber-level modifications effectively disconnect the individual service configuration from the underlying feature profile: a subsequent Reset Subscriber Lines on the feature profile will not influence a disconnected subscriber's service configuration.
Classes of Restriction