With Authorization Code Permissions it is possible to create authorization codes that unblock different sets of traffic types: depending on the code the user enters, some traffic types are permitted while others are blocked.
The Authorization Code Permissions approach is particularly useful in environments, where users must dial an authentication code (PIN) for billing purposes for, so it can be determined who made the call from what device.
While the standard Authorization Code feature is line-based and any valid authorization code unblocks all traffic types, with Authorization Code Permissions a line-independent, user-based authorization and billing can be implemented.
Being a late feature of Lotus Sametime Unified Telephony , its configuration is only possible via CLI (Command Line Interface) by setting the following RTP parameters:
Srx/Main/AuthTRSOverride (boolean, default=RtpFalse)
Setting its value to RtpTrue will enable the feature, setting it to RtpFalse will disable it.
Srx/Main/AuthTRSOverrideValues (string, default= "")
With this value you can define the Mapping between two-digit Authorization Codes prefixes and allowed traffic types. See the section below for details.
Furthermore, the respective subscribers (lines) have to be provisioned for the Authorization Code service with Authorization Code for off-net Traffic Types
In the application scenario presented above, all off-net traffic types should require an Authorization Code.
Finally, to take advantage of the Authorization Code Based Permissions, the subscriber must not
have the Toll and Call RestrictiUnified number service active.
Both Authorization Code and Toll and Call Restriction service can be defined on a per subscriber basis or via the subscriber's Feature Profile.
As stated above, an Authorization code's permitted traffic types are determined by its first two digits: prefix 10 can be mapped to a set of permitted traffic types P00, prefix 20 to a set of permitted traffic types P20 and so on.
The applicable prefixes along with their permitted traffic types are specified in Srx/Main/AuthTRSOverrideValues
as a semicolon-separated list of key:value
pairs, where key
is the Authorization Code prefix and value
is a nonempty sequence of letters representing permitted traffic types:
L for Local
N for National
I for International
Z for International World Zone 1 (e.g. national Cellular Numbers)
A for Long Distance Directory Assistance (e.g. International Cellular Numbers)
an Authorization Code starting with 10 unblocks Local calls onlyNote:
an Authorization Code starting with 20 unblocks Local and National calls
an Authorization Code starting with 30 unblocks Local, National and International calls
all other Authorization Codes unblock all calls
Note that is not required to map every possible two-digit prefix. An Authorization Code with unmapped prefix behaves "as usual", i.e. it unblocks all traffic types.
On the other hand, for an Authorization Code whose prefix is mapped to an empty value (i.e.. "...;99:;...
") all traffic types are blocked.
If Authorization Code Permissions are properly provisioned (as described above), the execution logic for outgoing calls is als follows:
Parent topic: Business Group Authorization Codes
- it is checked whether the traffic type T (= L, N, I, Z, or A) from translation of the Destination Code traffic type requires an Authorization Code:
if not, the Authorization Code service won't be triggered at all and the call will go through
- it is checked, whether the dialed Authorization Code is valid in the related BG:
if not, the regular Authorization Code reentering/rejection mechanism applies
- it is checked, whether the first two digits (prefix) of the dialed Authorization Code appear as a key in AuthTRSOverrideValues:
if not, the regular Authorization Code logic applies and the call goes through
- it is checked, whether the traffic type T (from step 1) is permitted for the dialed prefix (key), i.e. if T appears in the corresponding value in AuthTRSOverrideValues:
if not, the call is blocked
else it will go through
How to Provision Subscribers for the Authorization Code feature