The TRS (Toll and Call Restrictions) feature provides the capability to block an endpoint's or a subscriber's access to certain traffic types and/or to a configurable list of destinations. The corresponding entity can be provisioned with a Standard
and an Alternate
Class of Restriction, with the possibility of scheduled switchovers and manual switchovers via feature access codes and PIN (the latter for subscribers only).
Traffic Types and Classes of Restriction
Since V5 of Lotus Sametime Unified Telephony, the restricted traffic types 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
The administrator configures the feature at the endpoint profile, the feature profile or the subscriber level by specifying the following parameters:
A Standard Class of Restriction, i.e. the set of traffic types that is blocked "by default" for the related endpoints or subscribers. The Standard Class of Restriction may be "null", which means "no restriction".
A Blocked Call List, which may comprise DNs (Directory Numbers) or partial DNs such as area codes. Those codes may also comprise wild cards representing "any digit".
An Alternate Class of Restriction for both scheduled switchover and manual switchover with access code and PIN. Typically, the Alternate Class of Restriction will be a superset of the Standard Class of Restriction.
The Switchover Duration parameter determines the duration of a manual switchover. This applies to subscribers only.
A Day Schedule specifying the planned intraweek switchovers between Standard and Alternate Class of Restriction for regular calendar weeks. This schedule comes in handy for daily closings and weekends.
A Date Schedule specifying the planned switchovers for particular date ranges such as bank holidays or annual closings.
If specified, this will over-ride the Day Schedule for those dates.
In order to enable subscribers or CSTA applications to perform a manual COSS (Class of Service Switchover), the administrator has to provision the corresponding feature access codes.
The switchover duration by dialing an access code takes precedence over the Day and Date Schedules. That is, if a subscriber initiates a switchover, then it is valid for the specified switchover duration, irrespective of the configured Day/Date Schedule. After the Switchover Duration is expired, the Day/Date Schedule (if any) takes effect.
When Lotus Sametime Unified Telephony detects that a restricted subscriber or endpoint is attempting to originate a call, it determines if the dialed digits represent a permitted destination:
if the dialed digits are permitted, the call proceeds normally.
if the dialed digits are prohibited, the system routes the call to an announcement or to reorder tone. The treatment can be assigned on a per-subscriber or per-group basis.
If provisioned, a subscriber can dial the COSS access codes and his/her authorization PIN at any time to switch its Class of Restriction from Standard to Alternate profile and vice versa. The PIN can be dialed en-block or can be entered after receiving the announcement from the media server.
Dialing a COSS feature access code if no Alternate Class of Restriction is defined is rejected with an announcement.
Subscriber Rerouting and Toll and Call Restrictions
A system-wide option Srx/Main/InvokeTRSOnRerouting
determines, whether toll restrictions shall be bypassed (RtpFalse
) or not (RtpTrue
) on the subscriber rerouting call leg. Its default value is RtpFalse
, i.e. Toll and Call restrictions won't be applied.
The Authorization Code feature allows the subscriber to dial authorization code in order to unblock certain restricted traffic types.
If both TRS and Authorization Code feature are active, the TRS takes precedence.
How to Provision Toll and Call Restrictions for EndpointsParent topic: Station Restriction Features
Classes of Restriction
In order to provision the Toll and Call Restrictions
feature at an endpoint, the Toll and Call Restriction
service has to be enabled and configured at the assigned Endpoint Profile. This is described in the following procedure.
How to Provision Toll and Call Restrictions for Subscribers
This procedure describes how to provision the Toll and Call Restriction service at the feature profile or subscriber level. Feature profiles, in turn, can be created at the switch level and 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.