Detailed description of Remote Access

Last Updated : Oct 30, 2012 |
Prolog information
Metadata
Keywords:
Other:
Avaya has designed the Remote Access feature incorporated in this product, when properly administered by the customer, to enable the customer to minimize the ability of unauthorized people to gain access to the network. It is the responsibility of you to take the appropriate steps to properly implement the features, evaluate and administer the various restriction levels, protect access codes, and distribute the access codes only to people whom you advise of the sensitive nature of the access information. Instruct each authorized user to use access codes properly.
In rare instances, unauthorized individuals use the Remote Access feature to make connections to a telecommunications network. In such an event, applicable tariffs require that you pay all network charges for traffic. Avaya cannot be responsible for such charges, and does not make any allowance or give any credit for charges that result from unauthorized access.
The Remote Access caller must access your system from the public network and use a touch tone telephone or equivalent equipment. When a user uses Remote Access, the system does not have access to the calling number, because the calling number is outside the system. Thus, some features and capabilities, such as Ringback Queuing and Automatic Callback, cannot be used on a Remote Access call. Also, the user cannot use any feature that requires recall dial tone, such as, the Hold and Transfer features, from the remote location.
Remote Access provides users with access to the system and system features from the public network. Uses can use Remote Access to make business calls from home or use the Recorded Telephone Dictation Access to dictate a letter. An authorized user can also access system features from any onsite extension.
With Remote Access, you can dial into the system over direct inward dialing (DID), central office (CO), foreign exchange (FX), or 800 service trunks. When a call comes in on a trunk group that is dedicated to Remote Access, the system routes the call to the Remote Access extension that you assigned. If DID is provided, and the Remote Access extension is within the range of numbers that can be accessed by DID, the system uses DID for Remote Access.
You can administer your system so that a user must enter a barrier cod, an authorization code, or both to use Remote Access.
Use barrier codes to secure and define calling privileges through the Class of Restriction (COR) that you administer to users and trunk groups. You can administer as many as 10 barrier codes. Each barrier codes has a different COR and Class of Service (COS). Barrier codes can be from 4 to 7 digits, but all barrier codes that you define must be the same length.