Home
>
ATT
>
Communications System
>
ATT DEFINITY Communications System Generic 3 Instructions Manual
ATT DEFINITY Communications System Generic 3 Instructions Manual
Have a look at the manual ATT DEFINITY Communications System Generic 3 Instructions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 164 ATT manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Remote Access (with Security Measures) Issue 3 March 1996 3-1027 Remote Access (with Security Measures) Feature Availability This feature is available with all G3 releases. Logoff Notification and the status remote-access command are available with G3V4 and later releases. Description Permits authorized callers from remote locations to access the system via the public network and then use its features and services. Remote Access users can dial into the system using DID, CO, FX, or 800 Service trunks. The Remote Access feature is assigned an extension number, as any voice terminal. When a call is received on a trunk group dedicated to Remote Access, the system routes the call to the assigned extension number. If DID is provided and if the Remote Access number is within the range of numbers that can be accessed by DID, then the Remote Ac c ess feature can be accessed through the DID feature. After access to the feature, the user hears system dial tone, and, for system security, may be required to dial a Barrier code. If a valid Barrier code is dialed, the user may a gain hear dial tone, and can place local or long-distance calls as allowed. An authorization c o de may be required to place calls. The destination of incoming, non-DID, trunk calls can be an attendant or an extension number. The destination is specified on each individual trunk group. When the trunk group is dedicated to Remote Ac cess, the Remote Access extension number is specified. In this case, the user does all dialing. If an attendant is needed on a call, the user dials the public network telephone number assigned, the Barrier code, and attd (the attendant access code). To provide attendant-assisted calling, service can be arranged so the attendant handles calls during the d ay, but Remote Ac cess a p plies after normal business hours. This is accomplished by setting the trunk group destination as ‘‘attd’’ (the attendant), and specifying the Remote Access extension number as the Night Station number. Incoming calls route to the attendant unless the Night button on the primary console is pressed. When Night Service is in effect, incoming calls route to Remote Access. Setting up an Abbreviated Dialing List on Remote Access Trunks Users can a c cess the system, group, and enhanced Ab breviated Dialing lists via the remote access trunk. To set u p an Ab breviated Dialing list on a remote access trunk, perform the following steps: 1. Set up the Ab breviated Dialing list on the “Console” form.
Feature Descriptions 3-1028Issue 3 March 1996 2. Administer the Abbreviated Dialing list entries. 3. Dial into the system over the remote access trunk. 4. Dial the feature access code followed by the dial code of the list entry. NOTE: If a barrier code and authorization code are administered, dial them first. Remote Access Status (G3V4 and later releases) G3V4 provides the ability to check the status of the remote access feature and barrier codes. The status remote-access command displays information that can help in determining why and when use of the remote access feature or a particular barrier code was denied. The display indicates if the remote access feature is: nNot administered nEnabled nDisabled nDisabled following detection of a security violation It also gives the d ate and time that the remote access feature was last modified. For each barrier code the command displays: nThe date the c o de was administered, reactivated or modified nExpiration date nThe number of calls that can be placed with the code nThe number of calls that have been placed using the code nWhether the c o de is active or expired nThe date and reason a code expired For a detailed description of the status remote-access command and display, see the GBCS Products Security Handbook, 555-025-600. Security Measures The Remote Access feature has inherent risks, it can lead to large scale unauthorized long-distance use. For security purposes, a 7-digit barrier code with Remote Ac cess Barrier Code Aging should be used. The Remote Access Barrier Code Aging feature limits the length of time an access code remains valid, and/or the numb er of times an access code can be used. The ability to define the life s pan and number of times a barrier code can be used reduces the o p portunity for unauthorized use of the Remote Ac c ess feature.
Remote Access (with Security Measures) Issue 3 March 1996 3-1029 Following are security measures for remote a c cess. Barrier Codes Remote Access Barrier Code Aging gives the customer the a bility to specify, through the administrative interface, both the time interval a code is valid, and/or the number of times a code can be used to access the Remote Access feature. A barrier code automatically expires if an expiration date or number of accesses has exceeded the limits set b y the switch administrator. If b oth a time interval and access limits are administered for a barrier code, the barrier code expires when one of the conditions is satisfied. Expiration dates and access limits must b e administered for each barrier code. There are 10 possible barrier codes. Each one can be from 4 to 7 digits long. If there are more than 10 users of the Remote Access feature, the codes have to be shared. When a barrier c o de is no longer needed it should be removed from the system. Barrier codes should be safeguarded by the user and stored in a secure place by the switch administrator. If barrier codes are administered, a sp ecial answer-b ack tone is provided that causes a calling modem to leave dial mo de. A modem’s dialer is sometimes used to gain access (this tone also cancels echo suppressors in the network preventing DTMF tones from breaking dial tone from a switch.) Barrier c odes can be used alone or together with authorization codes. Use the status remote-access comma n d (G3V4 a n d later releases) to view the status of a remote access barrier code. NOTE: Barrier codes are not tracked by the CDR. Barrier codes are “incoming” access codes. Whereas, authorization codes are primarily “outgoing” access codes. Authorization Codes Authorization codes are also used to manage system access. CDR can track use of authorization c o des. There are four areas involving authorization c o de management. nAssigning codes - Codes should be randomly generated, following no pattern. Assign one each to an individual responsible for protecting the code. nPeriodic change - If codes are changed regularly, they are harder to break. nDeleting codes - Delete when no longer needed. nMonitor use - Performe d via CDR output analysis. Maximum length authorization c o des should be used to prevent unauthorized access.
Feature Descriptions 3-1030Issue 3 March 1996 Alternate Facility Restriction Levels (AFRL) For G3rV1 and G3V2 and later releases, consider changing FRLs with the AFRL feature after normal business hours to restrict where calls can be made over your facilities. Take care however, not to restrict callers from summoning emergency services after hours. See the Alternate Facility Restriction Levels (AFRL) feature. Class of Restriction The COR of an authorization c o de supersedes that of a barrier code. Time of Day Routing This is controlled by the time-of-d ay entries in COR or by the partition. See the Time of Day Routing feature for more details. Toll Restriction and Analysis Also controlled by COR. See the Restriction — Toll feature d esc ription in this document for more details. Trunk Access Code This interacts with toll restriction. A customer can translate the switch so that users can make toll calls via ARS b ut not using a TAC. Trunk Administration Trunks can be restricted that are assigned to Remote Access. Consult the GBCS Products Security Handbook, 555-025-600, for additional steps to secure your system and to find out about obtaining information regularly about security developments. Logoff Notification Logoff Notification, available with G3V4 and later releases, is recommende d for use in cases where Remote Access is enabled, but is not b eing actively used. Logoff Notification notifies the system administrator at logoff that the Remote Access feature is enabled. It guards against inadvertently leaving Remote Access active and can also alert the system administrator to unauthorized feature activation. Logoff Notification is administered on a login ID basis.
Remote Access (with Security Measures) Issue 3 March 1996 3-1031 Considerations Remote Access provides a caller with access to the system and its features from the public network. An executive can make business calls from home or use the Recorded Telephone Dictation Access feature to dictate a letter. Remote Access may also b e used from any extension on the switch. This allows authorized users to a c cess system features from any voice terminal extension. Ten barrier c o des, each with a different COR and COS, can be administered. The barrier c o des can be from 4 to 7 digits, b ut all c o des must be the same length. Barrier codes not only provide system security but also define the calling privileges through the administered COR. Ringback Queuing and Automatic Callback cannot be used on a Remote Access call since the system does not have access to the calling (outside) number. Any feature requiring recall dial tone (for example, Hold and Transfer) cannot be accessed remotely. The Remote Access caller must use a touch-tone voice terminal, or equivalent. After a DTDM’s baud rate is changed from 9600 to 1200, the DTDM cannot be accessed by Remote Access until an internal call is made to the DTDM. A Remote Access user attempting the call before an internal call is ma de receives intercept treatment. NOTE: AT&T has designed the Remote Access feature incorporated in this product that, when properly administered by the customer, enables the customer to minimize the ability of unauthorized persons to gain access to the network. It is the c ustomer’s responsibility to take the ap propriate steps to properly implement the features, evaluate and administer the various restriction levels, protect access codes and distribute them only to individuals who have been advised of the sensitive nature of the access information. Each authorized user should be instructed concerning the proper use and handling of access codes. In rare instances, unauthorized individuals make connections to the telecommunications network through use of remote access features. In such an event, a p plicable tariffs require that the customer pay all network charges for traffic. AT&T cannot be responsible for such charges, and does not make any allowance or g ive any credit for charges that result from unauthorize d access.
Feature Descriptions 3-1032Issue 3 March 1996 Interactions The following features interact with the Remote Access feature. nAuthorization Codes When a remote access caller dials the assigned remote access number and establishes a connection to the system, the system may request the caller to dial an authorization code in addition to a barrier code. Dial Tone between the barrier code and authorization code is optional. Calling privileges associated with the COR assigned to the authorization code supersede those assigned to the barrier code. nClass of Restriction (COR) COR restrictions do not block access to the Remote Access feature. nNight Service — Night Station Service The Remote Access extension numb er can be specified as the Night Station extension number on an incoming, non-DID, trunk group. nIntegrated Services Digital Network Primary Rate Interface (ISDN-PR)I A problem may exist when attempting to make a Remote Access call via a public and private trunk. For example, a caller dials 957-5730. The caller receives the beep-beep tones for Remote A ccess, and dials the b arrier code. At this point, the caller may still hear the system dial tone, indicating the digits are not being received by PBX#1. To correct the problem, change the UDP table on PBX#2 to give the extension its own RNX of 555. Administration Remote Access is administered by the System Manager. The following items require administration: nExtension number nBarrier code length (from four to seven digits or b lank [no barrier codes]) nBarrier codes nCOR/COS (per Barrier code) nAuthorization Codes nWhether or not Dial Tone is a p plied between the b arrier code and authorization c o de nBarrier Code expiration d ate and number of access attempts (per barrier code) (G3V3 and later releases) nLogoff Notification (G3V4 a n d later releases)
Remote Call Coverage Issue 3 March 1996 3-1033 Remote Call Coverage Feature Availability This feature is available with Generic 3 Version 2 and later releases. Description Provides automatic redirection of certain calls to alternate answering positions in a Remote Call Coverage path for any valid dialed number up to 16 digits that b e gins with an Automatic Alternate Routing (AAR) or Automatic Route Selection (ARS) feature access c o de (FAC), outgoing trunk dial access code (TAC), or UDP/DCS extension. Once a remote call coverage point is administered for a user, calls to that user are directed to the remote coverage point when the user and any other coverage points are unavailable. The call may have been previously directed to up to two alternate answer points before being redirected to the remote call coverage point. Once a call is directed to the remote call coverage point, it cannot be picked up by the principal user and that user’s bridged appearance lamp is extinguished. Calls redirected to a remote call coverage point do not time out and g o to a subsequent coverage point. NOTE: A vector directory numb er (VDN) can be administered as the last point in a coverage path. Hardware Requirements None.
Feature Descriptions 3-1034Issue 3 March 1996 Report Scheduler and System Printer Feature Availability This feature is available with all Generic 3 releases. Description Allows the System Manager to sc hedule selected administration commands to be printed by an asynchronous printer. Reports are scheduled at 15-minute intervals for any combination of days of the week. Most list, display, or test commands may be scheduled. Reports may be scheduled, changed, listed, and removed via the system’s Management Terminal. Scheduling (Adding) Reports The System Manager can schedule a report on the Report Scheduler by using the schedule command line option on the Management Terminal (for example, list configuration all [schedule]). The system then verifies the command to be scheduled, and the ‘Report Scheduler’ screen is displayed as shown in Screen 3-35. By setting the “Print Interval” field (described below) to scheduled or deferred, the a dditional fields ap pear as shown in the screens below. If the Report Scheduler is full (already has 50 jobs scheduled), the error message Maximum number of reports scheduled; cannot schedule new report is displayed on the G3 Management Terminal. When using the schedule command line option to schedule a report, the Report Scheduler contains the following fields. nJob Id: (display only) Shows the report identification number (1 through 50), provided by the system. nCommand: (display only) Shows the command to be executed. nPrint interval: This field has three options: immediate, scheduled and deferred. Screen 3-35 shows a ‘Report Scheduler’ screen with the immediate option. Screen 3-36 shows a ‘Re port Scheduler’ screen with the scheduled option. Screen 3-37 shows a ‘Report Scheduler’ screen with the deferred o ption. The scheduled option is used to schedule a report to be printed at a later time. The deferred option is used to schedule a report to be printed once at a later time.
Report Scheduler and System Printer
Issue 3 March 1996
3-1035
The immediate option is used if the System Manager would like to print
the report immediately. If the printer link is not up, the scheduler will
attempt to b ring up the link and print the report. If the link is already up, the
scheduler will mark the report for printing during the current 15-minute
time interval. If the printer link cannot be established, the report will be
placed at the head of the queue and will b e printed the next time the link is
established.
If the printer link fails before the report has completed printing, no attempt
will be ma de to print the report when the link is finally established.
The immediate option allows one-shot printing of reports.
nDays of Week: If the scheduled or deferred option of the “ Print Interval”
field is chosen, the System Manager will be prompted for the days of the
week and time of day for the report to b e printed. A maximum of one d ay
of the week may be selected for deferred reports.
nPrint time: Re ports may be scheduled at 15-minute intervals within a
given hour (0, 15, 30, 45).
Screen 3-35. Report Scheduler Example 1
See the another examp le below in Screen 3-36
Screen 3-36. Report Scheduler Example 2
list configuration all Page 1 of 1
REPORT SCHEDULER
Job Id: 10 Job Status: none
Command: list configuration all
Print Interval: immediate
list configuration all Page 1 of 1
REPORT SCHEDULER
Job Id: 10 Job Status: none
Command: list configuration all
Print Interval: scheduled
Print Time: __21:__15
Sun:___n Mon:___y Tue:___n Wed:___y Thu:___n Fri:___y Sat:___n
Feature Descriptions
3-1036Issue 3 March 1996
Screen 3-37 provides a third examp le.
Screen 3-37. Report Scheduler Example 3
Changing Scheduled Reports
The System Manager may change a scheduled report using the change
report-scheduler command. When this command is entered, the ‘Re port
Scheduler’ sc reen is d isplayed, as shown in Screen 3-38. This screen is similar to
the ‘Report Scheduler’ screen displayed with the schedule command line option,
but has an a dditional field. This is the “ Job Status” field which shows one of the
following:
nprint-next — Indicates that the report is scheduled to be printed in the
current time interval.
nprinting — Indicates that the report is currently being printed.
nprinted — Means that the report has been successfully printed.
nwaiting — Means that the report is not scheduled for any activity during
the current 15-minute time interval.
If the Print Interval of a report is changed so that its scheduled time now falls
inside the current 15-minute time interval, the report will not be printed in the
interval. Instead, the report will be printed during its next scheduled time interval.
If a report is scheduled for a given time period, other than the current 15-minute
interval, and has its “ Print Interval” field changed from scheduled to immediate,
the report will be printed immediately.
list configuration all Page 1 of 1
REPORT SCHEDULER
Job Id: 10 Job Status: none
Command: list configuration all
Print Interval: deferred
Print Time: __21:__15
Sun:___n Mon:___y Tue:___n Wed:___n Thu:___n Fri:___n Sat:___n