Matrix PRASAR UCS System Manual 813
• If DISA and Auto Attendant both are disabled, the incoming call will be routed as per the incoming call
routing configured. To know more, see “Auto Attendant”.
WARNING! This feature allows access to system resources to remote users, and therefore has serious
implications for your system's security. There is a risk of fraudulent calls being made from your system, if a
third party comes to know the authentication PIN or the User Password of an extension number. The cost
of such fraudulent calls will have to be borne by the owner of PRASAR UCS.
To avoid unauthorized access, we recommend you to change the PIN regularly. Make sure it is strong and
is provided to users who need to access the system using DISA only.
Feature Interaction:
• If DISA are enabled on the trunk, PRASAR UCS supports all types of DISA.
• If both, VMS Auto Attendant and DISA are enabled on the trunk, PRASAR UCS supports only PIN
Authentication-Multiple Calls. To know how the VMS handles a DISA call, see “VMS DISA Login”.
How to configure
To provide DISA to remote users you need to do the following configuration:
• Select the DISA variant for the Trunks on which you want to apply this feature in their “Trunk Feature
Template”.
• Enable DISA in the “Class of Service (COS)” of the extensions which you want to allow callers to access
using DISA. This is applicable for DISA PIN Authentication-Multiple Calls only. DISA CLI Authentication-
Single Call/Multiple Calls is not dependant on COS.
• Change the User Password of the DISA extensions, if you selected DISA PIN Authentication-Multiple
Calls. If you selected DISA PIN Authentication-Multiple Calls on a trunk, the default User Password (1111)
will not work. See “User Password” and “System Security” more information and instructions.
• Configure the DISA Idle State Timer, if required. See “System Timers and Counts” for instructions.
• If you have selected the DISA CLI Authentication-Multiple Calls or CLI Authentication-One Call on a trunk,
you must configure the CLI Authentication Table.
Configuring DISA CLI Authentication Table using Jeeves
To configure the DISA CLI Authentication Table,
• Make a list of remote users and their numbers whom you want to allow DISA.
• For each remote user’s number on your list, write the Extension number of the PRASAR UCS you want to
allow this extension user to log in.
• Login as System Engineer.
To Next Page
Loading...