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+.
MERLIN® /System 25 Voice Terminal Su p port — 731xH Series Issue 3 March 1996 3-887 Control Outward Restriction c o r Control Station to Station Restriction c s r Automatic Call-Back Call callback Q ACD Hunt Group Supervisor Assist sa S Control Termination Restriction c t r Emergency Call to Attendant Queue Full Redirectionqf E All Call-Ap pearances on Station are Busy BB CAS Main in Night Service n n Call Forward to CAS-Main attendant f f Service Observe agent & one other party o Held Call Timed Reminder hc Call Redirected do to coverage criteria cover c Terminate call via intercom ICOM i Terminate call via ARS ARS A Terminate call via Call-Forward forward f Terminate call via Call-Park p ark p Automatic Call Back Activate ACB Q Queued at terminator QTQ q Terminate via Call Waiting wait w Terminate to Attendant via Trunk Group control control Terminate to Attendant via Re call Call recall Terminate to Attendant via Return Call return Terminate to party with Do Not Disturb DND D Table 3-70. Merlin Terminal Codes — Continued Call Type Digital Hybrid Continued on next page
Feature Descriptions 3-888Issue 3 March 1996 Considerations The following features of the 731xH series voice terminals are affected when used with the DEFINITY switch: nACD The 731x hybrid terminals are not recommended for ACD agent applications because in heavy traffic conditions display information may be lost. nCall Ap pearance Button LEDs Both the red and green LEDs associated with the first 10 dual-LED feature buttons are supported for the 7313H, 7314H, 7315H, 7316H, and 7317H voice terminals when these buttons are administered as call or brid ged appearances: — The red ‘‘on’’ LED indicates the call appearance that is selected when the user goes off-hook. — The green ‘‘on’’ LED indicates the call at that a ppearance or at a bridged appearance. nFeature Buttons Call a ppearances or bridged ap pearances can be assigned only to feature b uttons 1 to 10 on the 731xH voice terminals. nFeature Button LEDs The 731xH voice terminals have two LEDs (one red and one green) associated with each administrable feature button. The DEFINITY switch only supports the green LEDs associated with the feature b uttons. O peration of the green LEDs is identical to operation of the 7400 series terminals. nHFAI The DEFI NI TY switch replaces the HFAI capability on System 25 with the Internal Automatic Answer (IAA) feature. When an internal call arrives at an idle 731xH series terminal that has IAA activated, the speakerphone and microphone at that terminal activate and automatically answer the call. When this occurs, the calling voice terminal receives a distinctive tone b urst, while the called voice terminal emits a distinctive tone b urst via the speaker. nMessage Button The mess a ge button is not supported for the 731xH voice terminals. As a result, pressing the Message button on one of these voice terminals has no system or local effect.
MERLIN® /System 25 Voice Terminal Su p port — 731xH Series Issue 3 March 1996 3-889 nMessage LED The Message LED is supported for the 731xH voice terminals. This LED is controlled by existing AUDIX and Leave Word Calling features on the DEFI NI TY switch. With these terminals, users cannot control the state of the Message LED by pressing the Message buttons. The Message LED operation is i dentical to that provided by the 7400 series voice terminals. The Mess a ge Retrieval and Retrieval Using Display modes are not supported for ATL terminals. As a result, these modes do not affect Message LEDs on ATL terminals. nMicrophone Microphone button operation is supported for the 731xH voice terminals. Each of these voice terminals sup p ort the following capabilities: — If the terminal is off-hook on the handset, pressing the Microphone button has no effect. — If the terminal is off-hook with the speakerphone active, pressing the Microphone b utton toggles the mi crophone between ‘‘on’’ and ‘‘off.’’ nMode Switch The DEFI NI TY switch does not support the mode switch for testing or programming. nRecall Button The Recall button is not supported for the 731xH voice terminals. As a result, the Recall button has no system or local effect when p ressed by the user. nSpeakerphone Full speakerphone and headset-adjunct operation are sup p orte d for the 731xH voice terminals. For each of these voice terminals, the DEFINITY switch supports the following capabilities: — Activation/deactivation of the terminal’s microphone via the fixed MIC button or HFAI/MIC b utton. — Activation/deactivation of the speakerphone function via the Speakerphone button. — Control of the terminal’s microphone and speaker LEDs in accordance with the states of the mi crophone and sp eakerphone. If the speakerphone function is activated while the terminal is off-hook on the handset, the handset becomes inactive and the microphone (and speaker) become active. nStop and Pause (Drop and Hold) Sub-designated buttons The Stop and Pause functions are not supported for the 731xH voice terminals.
Feature Descriptions 3-890Issue 3 March 1996 Misoperation Handling Feature Availability Misoperation Handling is available with all Generic 3 releases. G3V4 a n d later releases provide for modified misoperation alerting. Description Misoperation Handling defines the treatment of calls when a misoperation occurs. A misoperation occurs when calls are left on hold when the controlling station g oes on hook. For exam ple, a misoperation can occur under either of the following conditions: 1. When a voice terminal with a call on hold goes on-hook during a feature operation prior to completion of that operation (in some cases g oing on-hook completes the operation, as in call transfer). For example, a misoperation occurs when a user places a call on hold, begins to transfer the call, dials an invalid extension number, and then hangs up. 2. When the system enters night service while attendant consoles have calls on hold. With G3V4 a n d later releases, the system administrator can alter the standard Misoperation Handling to ensure that an external caller is not left on hold indefinitely, or dropped by the system after a misoperation with no way to reach someone for help. Misoperation Handling varies considerably depending upon system administration, and the conditions that are in effect when the call is p laced on hold. The following sections describe common Misoperation Handling scenarios. Standard Operation Standard Misoperation Handling is in effect when “Intercept Treatment on Failed Trunk Transfer” is “Y” and either: nThe “ Misoperation Alerting” field on the “ Feature-Related System Parameters” form is set to n. nThe software release is earlier than Generic 3 Version 4. Standard Misoperation Handling is dependent on the type of voice terminal in use when the misoperation occurs (analog single-line, or digital multi-ap pearance). Analog Operation The following sc enario d escribes a typical misoperation on an analog terminal.
Misoperation Handling Issue 3 March 1996 3-891 1. While connected to an incoming external call, an analog station user flashes with the intent of transferring the call to another terminal. 2. The user hears d ial tone and then dials an invalid extension and hangs up. 3. A misoperation has occurred. The analog station user will receive priority ringback indefinitely Digital Operation The following sc enario d esc ribes a typical misoperation on a di gital terminal. 1. While connected to an incoming external call, a digital station user places the call on hold with the intent of transferring the c all to another terminal b y pressing Transfer. 2. The user hears d ial tone and then dials an invalid extension and hangs up. 3. A misoperation has occurred. The held call remains on hold indefinitely with a flashing call a p pearance lamp. G3V4 and Later Releases G3V4 and later releases allow the system administrator to select Misoperation Alerting as an option for Misoperation Handling. With this option, calls receive different Misoperation Handling depending upon: the type of voice terminal in use when the misoperation occurs (digital multi-appearance, analog single-line, or attendant console); and the type of call on hold when the misoperation occurs. The following list describes the three call types used to determine Misoperation Handling. The scenarios following the Call Type list describe typ ical misoperations with Misoperation Alerting enabled. nCall Type 1: An outgoing public network call is classified as Type 1 when it is ringing or answered. An incoming call is classified as Type 1 when it is answered. nCall Type 2: An incoming external public network call that has not yet been answered is classified as Type 2. (A misoperation cannot occur with a Type 2 call because an unanswered incoming call cannot be placed on hold without being answered first.) nCall Type 3: All other calls, that is, all internal calls, conference calls, and tie trunk calls of any type are classified as Type 3. Analog Operation The following two scenarios describe typ ical misoperations on an analog terminal. Scenario 1 1. While connected to an incoming external call (Call Type 1), an analog station user flashes with the intent of transferring the call to another terminal.
Feature Descriptions 3-892Issue 3 March 1996 2. The user hears d ial tone and dials an invalid extension. The user then hears interc ept tone. 3. At any point after this, when the user hangs up, the call re-alerts the user for 15 seconds, and is then route d to the attendant. Scenario 2 1. While connected to an incoming external call (Call Type 1), an analog station user flashes with the intent of placing the current call on hold while calling another extension. 2. The user hears d ial tone and dials the CAS Remote Hold/Answer Hold/unhold access code. 3. The user hears d ial tone, d ials and talks with the second call, and then hangs up. 4. A misoperation has occurred because the first call has been left on hold. 5. The terminal is alerted for 15 se conds with normal ringing and then the c all is routed to an attendant. 6. If the first call has not been answered by the expiration of the timer, the call is dropped by the system. Digital Operation The following sc enario d escribes a typical misoperation on a di gital terminal. 1. While connected to an incoming external call (Call Type 1), a digital station user places the call on hold with the intent of transferring the c all to another terminal. 2. The user hears d ial tone and then dials an invalid extension and hangs up. 3. A misoperation has occurred. 4. The call on hold re-rings the terminal with a normal ring (not priority ringing) for the number of rings indicated by call coverage administration. 5. After ringing for the a dministered number of rings, the call is directed to the terminal’s administered coverage path, which can direct the caller to an announcement and/or disconnect them. Attendant Console A misoperation only occurs on an attendant console when the system enters night service with calls on hold at an attendant console. The following sc enario describes a typical misoperation on an attendant console. 1. The system enters night service with calls on hold at an attendant c onsole. 2. All calls on hold on the console start re-alerting (as if the held call timed reminder had expired).
Misoperation Handling Issue 3 March 1996 3-893 3. When the calls start re-alerting, a timer is started. The timer is set to the duration entered in the “Alerting (sec)” field on the “Attendant Console” form. 4. If the attendant has not answered the call by the time the timer has expired, the call is routed to the system night service destination. (If still not answered the call will be dropped by the night service disconnect timer.) Interactions nAttendant Lockout The attendant lockout feature is temporarily disa bled on calls that are re-alerting the attendant console following a misoperation. This allows the calls to be answered by the attendant. Administration To enable G3V4 and later release misoperation alerting, enter y in the Misoperation Alerting field on the “Feature-Relate d System Parameters” form. For complete instructions for administering Misoperation Handling, see Misoperation Handling in the DEFINITY Communications System Generic 3 Version 4 Imp lementation, 555-230-655, or DEFINITY Communications System Generic 3 V2/V3 Implementation , 555-230-653. See the c ountry applications notes for complete instructions for administering the Misoperation Handling feature to meet France Typ e Approval requirements. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-894Issue 3 March 1996 Modem Pooling Feature Availability This feature is available with all Generic 3 releases. Description Allows switched connections between d i gital data en d points (data modules) and analog data endpoints and acoustic coupled modems. The analog data endpoint can be either a trunk or line circuit. Data transmission between a d i gital data en d point and an analog endpoint requires a conversion resource since the DCP format used b y the d ata module is not comp atible with the mo dulated signals of an analog modem. The conversion resource translates the DCP format into modulated signals and vice versa. The Modem Pooling feature provides pools of conversion resources. Inte grated conversion resources and combined conversion resources are available with the system. The integrated type has functionality integrated on the TN758 Pooled Modem circuit pack, which provides two conversion resources and each one emulates a Trunk Data Module cabled to a 212 Modem. This integrated type is not available for countries that use A law. The combined type is a Trunk Data Module cabled to any Trunk Data Module-compatible modem to provide a conversion resourc e. Combined type applies to all system independent of system companding. When a conversion resource is required, the system queries the d i gital data module associated with the call to determine if its options are compati ble with those supported by the modem pools. If the d ata module options are not compatible, the originating user receives interc ept treatment. If the options are compatible, the system o btains a c onversion resourc e from the a p propriate pool. If a conversion resourc e is not available, the user receives reorder treatment. If all d ata calls, including analog, are not successfully established, the call will be disconnected within 15 seconds (handshake time-out). In almost all cases, the system can detect the need for a conversion resource. Data calls originated from an analog data endpoint to a d igital d ata endpoint require that the user indicate the need for a conversion resource, since the system considers an analog call origination as a voice call. This need is indicated by dialing the Data Origination Ac cess Code before dialing the digital data endpoint. Use of Data Call Preindication before One-Button Transfer To Data is recommended when establishing d ata calls that use toll network facilities. Needed conversion resources are reserved before any toll charges are incurred.
Modem Poolin g Issue 3 March 1996 3-895 The DEFI NI TY s yst em provides a ‘‘HOLD Time’’ parameter to sp ecify the maximum time any conversion resource may be held but not used (while a data call is in queue). Combined conversion resources additionally supports the following configurations: nIBM bisynchronous protocols typically used in 3270 and 2780/3780 applications. Both require 2400 bps or 4800 b ps, half-duplex, synchronous transmission. nInteractive IBM-TSO a p p lications using 1200 bps, half-duplex, asynchronous transmissions. nDATAPHONE II switched network modems supporting asynchronous and synchronous communications, and autobaud at 300, 1200, or 2400 b ps. nDEFI NI TY s yst em Generic 3 can operate up to 19.2 kbps. nDifferent pools can have different data transmission characteristics. The following modem options are supported by the integrated (only) pool: nReceiver Resp onds to Remote Loop nLoss of Carrier Disconnect nSend Space Disconnect nReceive Space Disconnect nCF-CB Common nSpeed, Duplex, and Synch (administered ) Considerations Modem Pooling offers a pool of conversion resources which increase data call flexibility. Conversion resources allow analog data endpoints, using modems, to communicate with digital data endpoints (using data modules). Also, pooling of conversion resources allows maximum use of such facilities. Data Call Preindication is recommended for off-premises data calls involving toll charges. On data calls between a d ata module and an analog data end point, Return-to-Voice releases the conversion resource and returns it to the pool. The voice terminal user is then connected to the analog data endpoint. For traffic purposes, DEFINITY system Generic 3 accumulates data on modem pooling calls separate from voice calls. Measurements on the pools are also accumulated.
Feature Descriptions 3-896Issue 3 March 1996 When a voice terminal user places a data call to d i gital data endpoint and does not transfer the call to another digital data endpoint, but uses a mo dem or acoustically coupled modem, the user must dial the Data Origination access code assigned in the system b efore dialing the distant endpoint. DEFI NI TY s yst em Generic 3i can support u p to five pools; Generic 3s can support up to two pools, and Generic 3r can support up to 63 pools. The pools may be c ombined, integrated, or any mix thereof. Each pool has a c a pacity of up to 32 conversion resources. Use of Modem Pooling cannot be restricted. Also, queuing for conversion resources is not provided, although calls queued on a hunt group retain reserved conversion resources while queued. Mixing of mo dems from different vendors within a combined pool should be avoided since a difference in transmission characteristics may exist. Mixing is possible, but satisfactory results are not g uaranteed. Data transmission characteristics (speed, d uplex, and synchronization mo de), as administered, must be i dentical to the Trunk Data Module and modem optioning by the customer. Each data call that uses Modem Pooling uses four time slots (not just two). As a result, heavy usage of Modem Pooling could affect the Trunk Data Mo dule bus blocking characteristics. Tandem Switches will not insert a pooled modem. It is the resp onsibility of the originating switch to do so. Interactions The following features interact with the Modem Pooling feature. nData Call Setu p Data calls to or from a Trunk Data Mo dule cannot use Mo dem Pooling. nData-Only Off-Premises Extensions Modem Pooling is not p ossible on calls to or from a Data-Only Off-Premises Extension, when this type of digital data endpoint uses a Trunk Data Module. nData Privacy and Data Restriction The insertion of a modem pool d oes not turn off Data Privacy and/or Data Restriction.