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+.
Audio Information Exchange (AUDIX) Interface Issue 3 March 1996 3-147 nCall Forwarding An AUDIX user can forward calls to a remote AUDIX hunt group or to the host AUDIX hunt group. The system administrator must correctly administer the AUDIX destination for the remote AUDIX hunt group. nCall Transfer A call transfer out of AUDIX can be to a UDP extension. If the destination extension is a UDP extension on a remote switch, the call is treated as a direct call. Additional trunks are used for calls transferred between DCS nodes. Calls may b e transferred into AUDIX by users handling redirected calls for principals who are AUDIX subscribers. nClass of Restriction (COR) A high FRL assigned in the COR allows c allers to transfer to long-distance numbers. To p revent toll fraud, assign a low FRL to the AUDIX system ports. nFacility Test Call Unauthorized calls may be placed using the facility test call access code. To prevent this fraud, remove the facility test call access code. nDCS Leave Word Calling (external unit only) In a DCS network, the called party may b e on a different switch than the calling p arty. If the DCS link is down, attempts to store LWC messages are denied and intercept tone is returned. Leave Word Cancel requests are Table 3-11. Transfer Out of AUDIX (Enhanced) and Coverage Interactions Source Transfer Destination Coverage Type External Local Station Remote Station (DCS) Remote Station (ISDN)Internal External Internal Internal (local) Local Station Remote Station (DCS) Remote Station (ISDN)Internal Internal Internal Internal (remote) Local Station Remote Station (DCS) Remote Station (ISDN)Internal Internal Internal
Feature Descriptions 3-148Issue 3 March 1996 always denied for principals with AUDIX LWC; in some instances, the request may appear to be activated when it actually is not (see Leave Word Calling). nLeave Word Calling (LWC) For AUDIX, the system administrator has the option of indicating that a principal’s LWC messages are kept by AUDIX. This means that an LWC message left for a principal causes the extension of the calling and called parties to be reported to AUDIX. The principal can retrieve the message by calling AUDIX. The principal cannot retrieve the message using other retrieval methods (station display, demand p rint, Message Center agent, or synthesized voice), but is notified of the existence of AUDIX messages via these methods. If the a dministrator assigns a principal’s LWC to another messaging service, AUDIX can still report the existence of waiting LWC messages for the principal, but not the message content. This means that an LWC message left for a principal causes an indication of a waiting LWC message to be sent to AUDIX. The principal can retrieve the message using other retrieval methods (station display, demand print, Message Center agent, or synthesized voice). However, the principal is still notified of the existence of AUDIX messages. If the d ata link between the system and AUDIX is down, attempts to activate LWC for an AUDIX-covered principal are denied and the reord er tone is returned. If a caller attempts to cancel a LWC message sent to AUDIX, the caller receives an intercept tone if the called party is on the same switch. If the called party is on another switch in the DCS network, then the caller receives a confirmation tone as long as the DCS data link to the called party’s switch is operational, even though the message is not actually canceled . nMessage Waiting Lamp (MWL) Activation/Deactivation The MWL interactions are the same whether the switch is a host switch or a remote switch. If a message is left for a principal on AUDIX, the switch lights the principal’s MWL when AUDIX tells it there is an AUDIX message. If the principal retrieves the message, the switch extinguishes the AUDIX MWL only if the c ombined status of LWC, Message Center Service (MCS), and AUDIX indicate there are no more messages. nPCOL A PCOL may not be covered by AUDIX. nQueuing Queuing maybe utilized with the AUDIX hunt group. This allows callers to wait for an available AUDIX system port.
Audio Information Exchange (AUDIX) Interface Issue 3 March 1996 3-149 nRingback Queuin g On direct calls to the remote AUDIX, where all trunks to the host AUDIX are busy, a busy tone is returned. On coverage calls, if all trunks to the DCS host AUDIX are busy, AUDIX is treated as a busy coverage point. If there are coverage points after AUDIX, then the call terminates there; otherwise, the call remains at the principal. In summary, Ringb a ck Queuing does not apply to AUDIX calls. nSingle-Digit Dialing and Mixed Station Numbering AUDIX is designed for use with a Uniform Dial Plan. It supports only one extension numb er length (three-, four-, or five-d i git) that is used by AUDIX subscribers. Single-Digit and Mixed Station Numbering cannot be used. However, nothing prohibits connecting a switch to AUDIX that provides these features, as long as all AUDIX subscribers have the same extension number length. nTemporary Bridged Appearance Stations that normally have a temporary bridged appearance with their coverage point do not if the coverage point is AUDIX. nU C D (f or DEFI NIT Y AUD IX onl y ) For DEFINITY AUDIX, a hunt group must be administered using a Uniform Call Distribution (UCD) split. nVoice (Synthesized) Message Retrieval If your system has the TN725B Speech Synthesis circuit pack, and if LWC Activation is enabled, then messages are retrieved from two locations: — LWC messages sent by pressing the LWC button on a voice terminal are retrieved via Voice Message Synthesized Retrieval. — All other messages are retrieved via AUDIX. If your system does not have a TN725B Speech Synthesis circuit pack, and if LWC Activation is enabled, then LWC messages sent by pressing the LWC button on a voice terminal are not retrievable by a nondisplay set.
Feature Descriptions 3-150Issue 3 March 1996 Administration The AUDIX Switch Interface is administered by the System Manager. For more information, refer to: nSwitch Administration Guide for AUDIX Voice Messaging, 585-305-505, for further details on AUDIX switch administration when AUDIX is configured external to the switc h nSwitch Ad ministration for DEFI NI TY AUDIX System R1.0, 585-300-509, and DEFINITY AUDIX System R1.0 Ad ministration, 585-300-507, for DEFINITY AUDIX nAUDIX System Desc rip tion, 585-305-201, for AUDIX Hardware and Software Requirements For DEFINITY AUDIX, you must have five contiguous slots in the switch carrier. See t he DEFI NIT Y AUDIX documentation for further details. The data link for the external AUDIX (either the one- or two-cabinet configuration) varies depending on the typ e of switch. nAn AUDIX system connected to a DEFINITY Generic 3r switch uses the TN577 Packet Gateway (PGATE) circuit pack. This board provides X.25 connectivity to support external adjuncts such as AUDIX and DCS nodes. nAn AUDIX system connected to a Generic 3i switch uses the TN765 Processor Interface (PI) circuit pack. This board has one Electronics Industries Association (EIA) port which allows direct access to one of its four d ata links. The EIA port is the recommended interface for the system. Refer to the AUDIX System Description manual, 585-305-201, for more information on AUDIX hardware and software requirements. For D CS AUDIX, DCS software is required.
Authorization Codes Issue 3 March 1996 3-151 Authorization Codes Feature Availability This is an optional feature available with all G3 releases. Description Provides the means for extending control of system users’ calling privileges and security for remote access callers. The Authorization Codes feature is optional, is closely linked to the Facility Restriction Levels (FRLs) and Traveling Class Marks (TCMs) feature, and c an b e used with the Automatic Route Selection (ARS), Automatic Alternate Routing (AAR), and Remote Ac cess (with Security Measures) features, as well as with incoming trunk calls. Authorization codes may be used for any or all of the following reasons: nTo allow a calling user to override the FRL assigned to the originating station or trunk nTo restrict individual incoming tie trunks and remote a c cess trunks from accessing an outgoing trunk nTo identify certain calls on CDR records for cost-allocation purposes nTo provide additional security control for the system When an authorization code is dialed, the FRL assigned to the extension numb er, attendant console, incoming trunk group, or remote access trunk group being used for the call is replaced by the FRL assigned to the authorization code. The new FRL functions the same as the one it replaces; however, the new FRL may represent greater or lesser calling privileges than the FRL that it replaces. Access to any given facility depends on the restrictions associated with the authorization code FRL. For exam ple, a supervisor may be at a desk of another user and want to make a call that is not normally allowed by the FRL assigned to that extension. The supervisor, however, can still make the call by dialing an authorization c o de that has been assigned an FRL that is not restricted from making that type call. For security reasons, authorization codes range from four to seven digits. The number of digits in the codes must b e a fixed length for a particular switch. Incoming trunk groups within a system may b e administered to always require an authorization code. The system app lies recall dial tone to a call when the user must dial an authorization code. If the user dials a correct authorization code within 10 seconds (inter-digit time-out), the call completes as dialed. If the user does not dial an authorization c o de or dials an incorrect authorization code, the
Feature Descriptions 3-152Issue 3 March 1996 call routes to the attendant, or routes to intercept tone, d e pending on system administration. Normally, DID trunks should not require authorization c o des. However, it can be done and care should be taken when administering DID trunks to require an authorization code, because different type calls could terminate at different endpoints, and requiring an authorization code could be confusing to the caller. A Cancellation of Authorization Code Re quest (CACR) digit may be administered. The CACR digit cancels the 10-second interval b etween dialing. When the CACR d i git is dialed, the call imme diately routes according to system administration. (Incoming trunk calls receive intercept treatment or go to the attendant.) Other calls receive intercept treatment unless the user’s FRL is high enough to route the call. A CACR digit from an off-premises extension over DID/Tie trunks use DID/Tie trunk interc ept treatment. Internal calls receive intercept tone. !CAUTION: Do not program passwords or authorization c o des onto auto dial buttons. Display telephones display the programmed buttons, providing internal abusers access to the auto dial buttons to originate unauthorized calls. If passwords or authorization codes must be programme d onto auto dial buttons, use the ~s (suppress) character to prevent the c o des from being displayed. AAR and ARS Calls Each authorization code is assigned a COR that contains an associated FRL. Within a system, access privileges are determined by the FRL assigned to the facility where the call is originated. When an AAR/ARS call is dialed, the system allows or d enies the call b ased on the FRL of the originating station. COR is used to restrict internal or non-AAR/ARS calls. Authorization codes are given to individual users and provide a method of specifying the level of calling p rivileges for that user regardless of the originating facility. Once an authorization c o de is required and dialed on an AAR/ARS call, the FRL assigned to the authorization code replaces the originating FRL and controls and defines the user’s privileges. An AAR or ARS call originated by a system user or routed over an incoming tie trunk may require a dialed authorization code to continue routing. Extreme care should be taken when administering authorization codes, so that a user d oes not have to d ial the authorization c o de more than once. For examp le, if a user makes an AAR or ARS call and the user’s FRL is not high enough to access any of the trunks in the routing pattern, the system prompts the user for an authorization code. If the FRL assigned to the authorization code is high enough to access the next trunk group in the routing pattern, the user is not prompted to dial the code again. If the call is routed through another PBX, the
Authorization Codes Issue 3 March 1996 3-153 user may be required to dial an authorization code again. This type of situation can be avoided through careful administration. When an authorization code is required on some, but not all, trunk groups, the system prompts for an authorization c o de when the originating FRL is not adequate to access the next available trunk group in the routing p attern. Remote Access Calls 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 and/or a barrier code. The authorization code defines the caller’s calling privileges within the system. If entry of an authorization c o de is required, it applies to all remote access trunk groups in the system. If a remote access user must dial an authorization code to gain access to the system facilities, an authorization c ode is not requeste d a gain even if the user places a call that routes through the Automatic Route Selection (ARS) or Automatic Alternate Routing (AAR) feature. The system may be administered for a Time-out to Attendant option. This o ption routes a remote access call to the attendant if the user fails to d ial within 10 seconds after receiving the system request for an authorization code. Also, the remote a c cess user can d ial the CACR d igit c ode, if a dministered, which cancels the 10-second time-out interval. In this case, the call routes imme diately to the attendant. If an off-premises user on a DID/tie trunk cancels an Authorization Code, DID/tie intercept treatment is received. Considerations From a remote location, all authorization codes as well as all barrier codes (if required) are normally entered using touch-tone dialing. However, rotary dialing may be used in some cases, depending on where the authorization code is forced and how the trunks are administered. A user with a rotary dial telephone can also dial the LDN for access to the attendant or, after dialing the remote access number, wait 10 seconds for Time-out to Attendant. In either case, the attendant must extend the incoming call. The Authorization Codes feature is entirely in ad d ition to, and in no way limits, other methods of call control such as Toll Restriction, Miscellaneous Trunk Restriction, and Outward Restriction. For security reasons, Authorization codes must b e assigned randomly. This also makes it difficult for one user to guess the authorization code assigned to another user. A CACR digit code, if administered, can be either the # symb ol or the di git 1. The # symbol is used when the tandem and main switches are DEFINITY system
Feature Descriptions 3-154Issue 3 March 1996 Generic 1 and Generic 3i. If a System 85, DIMENSION PBX, DEFI NI TY Generic 1 switch, or DEFINITY system Generic 3i switch is part of the network, then the digit 1 is used as the CACR digit code. If the digit one is used as the CACR d igit code, then it cannot also be used as the first d i git of an authorization code. If the Time-out to Attendant option is not administered and if a user dials the CACR digit code instead of an authorization code, the system assumes that an invalid authorization code was dialed and routes the call to intercept tone. Calling privileges are affected by the Authorization Codes feature as follows: nFor incoming trunk calls, where an authorization code is required due to administration on the ‘Trunk Grou p’ form, the authorization c o de does not change the privileges of the user in any way. nFor outgoing calls, where the FRL of the user is insufficient for accessing the routing pattern preference assigned by AAR/ARS, the authorization code changes the FRL of the user only. The FRL used is the one assigned to the COR that is associated with the authorization code entered. No other data assigned to that COR is assigned to the user. nFor remote access calls, where the user is required to enter an authorization code, the user is assigned the COR of the dialed authorization code, with all connected data, such as the FRL. This COR overrides the COR assigned to a barrier code, if a barrier code is also required. Interactions The following features interact with the Authorization Codes feature. nAAR/ARS Partitioning Since PGNs are assigned according to COR and Authorization Codes c an change a COR, PGNs can be changed on incoming Remote Access calls by the use of Authorization Codes. On originating calls, the user’s COR determines the PGN. nCOR and FRL When an internal system user dials an authorization c o de on an AAR/ARS call, the FRL associated with the authorization code overrides the FRL assigned to the system user. When a remote access user dials an authorization code, the associated COR determines the caller’s access privileges to the system’s features and services. nForced Entry of Account Codes and CDR On the 94A LSU (no longer supported) and 3B2 CDRU 18-word records, the authorization code is output only if the administered account code length is less than six digits in length. On the 59-character record, the authorization code is never recorded.
Authorization Codes Issue 3 March 1996 3-155 When an authorization code is required after the destination address is dialed, that code is recorded. Thus, all unauthorized attempts to dial an invalid authorization code is recorded, and a pattern of such calls can be traced using the CDR printouts. Administration The use of authorization c o des is optional. However, if authorization codes are used, the following items must be administered by the System Manager: nAuthorization Code Parameters — Enable the Authorization Codes feature — Authorization code length — Can be from four to seven digits, and all authorization c o des must be the same length — CACR digit — Choice is the d i git 1 or the # symb ol — Whether or not the Time-out to Attendant o ption is used — The authorization c o des themselves — This is a list of all authorization codes and their associated CORs. As many as 5,000 codes may be used. Authorization c o des should be selected randomly and cannot begin with the digit 1 if the digit 1 is used as the CACR di git c o de. nRemote Access — Whether or not an authorization code is required on a remote access call — Whether or not the system a pplies recall dial tone to request that an authorization code be dialed nAAR and ARS — If possible, assign COR FRLs and Routing Pattern FRLs so that no more than one authorization c o de is required when making an AAR/ARS call. nTrunk Groups — Whether or not each incoming or two-way trunk group requires an authorization code for incoming calls on that trunk group to complete to their destination. Hardware and Software Requirements No a d ditional hardware is required.
Feature Descriptions 3-156Issue 3 March 1996 Auto Start and Don’t Split Feature Availability This feature is available with G3i-Global, G3rV1, G3V2, and later releases, and is not available with G3vsV1/G3sV1, or G3iV1. Description The Auto Start and Don’t Split feature allows the attendant to initiate a phone c all by depressing any button on the dial keypad without having to first press the Start Button, thus reducing the number of buttons that attendant console users need to use to handle calls. This is a system-wide feature. If the attendant is on an active call and presses digits on the keypad, the system automatically splits the call and begins dialing the next call. When the Auto Start and Don’t Split feature is enabled, the Start button is disabled and end-to-end signaling is not allowed. That is, d i gits pressed on the keypad are always interpreted and are not passed to another device, such as a voice mail service. Auto Start is temporarily deactivated when the Don’t Split b utton is pressed and remains deactivated until the Don’t Split b utton is depressed again or the current call is terminated. This allows end-to-end signaling: When the Don’t split is pressed, digits pressed on the console keypad are heard by the parties on the call. For example, use Don’t split if you need to send touch-tones to the far end to pick up answering machine messages. To extend an active c all to another extension, begin dialing the digits of the other extension. The active call is automatically put on hold. Once the called party answers, press Release to extend the call. To send touch-tones on an active call, press Don’t Split. The call remains active. Press the keypad digits; the tones are sent to the far end. To d eactivate Don’t Split, press Cancel. Considerations When Auto Start is enabled and an attendant d ials an AAR numb er where the min and max in the AAR analysis table are not e qual, then the attendant must dial a ‘‘#’’ after the digit string or the call is not processed. Interactions Release, Forced Release, and Cancel deactivate the Auto Start and Don’t Split feature.