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+.
Timed Reminder and Attendant Timers Issue 3 March 1996 3-1165 Interactions The following features interact with the Timed Reminder feature. nAttendant Call Waiting An attendant-extended call to a busy single-line voice terminal returns to an attendant c onsole if the Time d Reminder Interval expires before the c all is answered, or redirects to coverage. nAttendant No Answer When a “dial 0” call is made to the attendant, after the No Answer Timer expires, the secondary alerting tone operates as described in the Attendant No Answer section on the previous p a ge. However, if a call alerts an attendant as a coverage call (unanswered station-to-station call with the “attd” (attendant) as an entry in the c alled station’s coverage path form) the secondary alerting tone does not o perate. nCall Coverage After a voice terminal user transfers a call to an on-p remises voice terminal, the call, if unanswered at the expiration of the Timed Reminder Interval, redirects to an attendant console. Redirection to an attendant occurs even if the c all has redirected via Call Coverage or Call Forwarding from the transferred-to voice terminal. An attendant-extended call redirects to coverage instead of returning to an attendant console, if the coverage criteria are met before the Timed Reminder Interval expires. However, unanswered c alls return to a c onsole at the exp iration of the Timed Reminder Interval. When a “dial 0” call is made to the attendant, after the No Answer Timer expires, the secondary alerting tone operates as described in the Call Coverage section on the previous p a ge. However, if a call alerts an attendant as a coverage call (unanswered station-to-station call with the “attd” (attendant) as an entry in the called station’s coverage path form) the secondary alerting tone does not operate. nCAS If an attendant at the main location transfers a call from a branch location to an extension at the main location, the timed reminder does not apply and the call does not return to the attendant if unanswered. nTransfer A call that is transferred times out and redirects to the attendant after an interval equal to the attendant return call timer.
Feature Descriptions 3-1166Issue 3 March 1996 Administration Timed Reminder and Attendant Timers are administered on a p er-system basis by the System Manager. The screen required is ‘Console Parameters’; the fields required to change the default timers are ‘No Answer Timeout’ and ‘Alertin g’ under the heading ‘Incoming Call Reminders’ as well as the ‘Time Reminder on Hold’ and ‘Return Call Timeout’ fields. Hardware and Software Requirements No a d ditional hardware or software is required.
Touch-Tone Dialin g Issue 3 March 1996 3-1167 Touch-Tone Dialing Feature Availability This feature is available with all Generic 3 releases. Description Provides quick and easy pushbutton dialing. Touch-Tone Dialing is always provided with the system. In a ddition to the 0 through 9 buttons, the * and # buttons have special functions, such as forming a p art of a feature access code. A distinctive tone is generated when each button is pressed. If a distant switching system can accept only dial pulse signals, the system converts the touch-tone signals to the required dial pulses for transmission to the distant end. This feature is referred to as Dual-Tone-Multi-Frequency dialing (DTMF) outside the US. Considerations With Touch-Tone Dialing, users are more efficient when placing and handling calls. Interactions None. Administration None required. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-1168Issue 3 March 1996 Transfer Feature Availability This feature is available with all Generic 3 releases. Description Allows voice terminal users to transfer trunk or internal calls to other voice terminals within the system without attendant assistance. Single-line voice terminal users momentarily flash the switchhook or press the Recall button, dial the desired extension numb er, and hang up. Multiappearance voice terminal users press the Transfer button, dial the desired extension number, and press the Transfer b utton again. Transfer is also known as Push Transfer. Please see the Pull Transfer feature for a description of a type of transfer that can b e used by voice terminal users to ‘‘pull’’ a held call to their own extension. Considerations The Transfer feature p rovides a c onvenient way to c onnect a party with someone better q ualified to handle the call. Attendant assistance is not required and the call does not have to be redialed. Transferred trunk calls can be administered to receive either music or silence. Multiappearance voice terminals must have an idle call appearance in order to transfer a call. Interactions nTransferred calls are elig i ble to b e automatically answered via the Internal Automatic Answer (IAA) feature. nWhen a multi-function station (BRI/Digital/Hybrid) dials sufficient digits to route a call, but could route differently if a d ditional digits were dialed, the station will not recognize the Conference or Transfer buttons. The user must delay dialing for three seconds or dial a # to indicate the call can be routed based on the digits already dialed. The Conference or Transfer buttons are then recognized and the operation is c ompleted by the switch. nStation users cannot transfer the attendant.
Transfer Issue 3 March 1996 3-1169 nIntegrated Services Digital Network Basic Rate Interface (ISDN BRI) When an ISDN-BRI station assigned with the “Select Last Used Appearance?” field of the “Station” form set to yes completes a transfer while off-hook using the handset, the user will be left hearing a dial tone on the last-used appearance, rather than the silence heard in the same situation by an user of other station types. nAttendant Conferencing may not operate properly if the CO d oes not provide answer supervision. If your CO does not provide answer supervision, the “Answer Supervision Timeout” field must b e set to a non-zero number and the “Receive Answer Supervision” must be set to “n.” If the CO does provide answer supervision, the “Answer Supervision Timeout” must be set to “0” and the “Receive Answer Supervision” must be set to “y.” Administration The Transfer feature is a dministered on a per-system basis by the System Manager. The only administration required is the treatment received on transferred trunk calls. Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-1170Issue 3 March 1996 Transfer — Outgoing Trunk to Outgoing Trunk (with Security Measures) Feature Availability This feature is available with Generic 3rV1 and all Generic V2 and later releases. Description Outgoing trunk to outgoing trunk transfer (OTTOTT) is a f eature that permits a controlling party, such as a station user or attendant, to initiate two or more outgoing trunk calls and then transfer the trunks together. The transfer operation removes the controlling party from the connection and conferences the outgoing trunks. Alternatively, the controlling p arty c an establish a c onference call with the outgoing trunks and then drop out of the conference, leaving only the outgoing trunks on the conference connection. This is a perilous enhancement of trunk to trunk transfer. OTTOTT allows calls to b e established in which the only parties involved are external to the switch and are on outg oing trunks. This type of call can result in locked-up trunks, for example, trunks which cannot b e disconnected except by busying out and releasing the affected trunk circuit. To clear the lock-up, a Service Technician must reseat the trunk board, or busy-out and release the affected trunk port. At least one outgoing trunk must have b een administered to support this type of transfer, and must have p rovid e d network answer supervision. The answer supervision test increases the probability, but does not guarantee, that a disconnect signal is received from the remote end of the trunk. To mitigate problems associated with its accidental use, this feature is only administrable on trunk groups on the “Trunk Group” form and is not a system o ption. DCS networks p rovide a similar but more restrictive version of this feature, called ‘‘DCS Trunk Turn Around’’, which permits two outgoing trunks to be transferred together when the switch at the remote end of at least one of the trunks agrees to ‘‘turn around’’ the logical direction of the trunk. DCS trunk turn around is permitted, in general terms, when some other p arty involved in the call (at the remote switch) can provide disconnect supervision. Without the use of OTTOTT, switches in a DCS network provide transfer between outgoing trunks through DCS Trunk Turnaround. Trunk Turnaround is attempted after a transfer or drop operation when no remaining parties can provide disconnect supervision. A message is sent to all remote switches that are connected to the local switch via an outgoing DCS trunk. If any of the signaled switches can provide disconnect supervision, they reverse their sense of the type of the trunk at their end from incoming to outgoing and respond with a positive acknowledgment. When the local switch receives the positive acknowled gment, it reverses the sense of its end of the trunk from outgoing to
Transfer — Outgoing Trunk to Outgoing Trunk (with Security Measures) Issue 3 March 1996 3-1171 incoming. If no response is received by the local node within four seconds, the call is aborted. Without OTTOTT or DCS, a c onference involving two or more outgoing trunks is only permitted when at least one remaining conference party is an attendant, incoming trunk, or station. Considerations OTTO TT is n ot int e n d e d for use in DCS networks, since DCS Trunk Turnaround provides comparable capabilities in a much safer way. However, use of OTTO TT with DCS is not prohibited, and may b e useful when one or more of the trunks go off the DCS network. Security Measures Administrators and System Managers are c autioned that this feature can b e used to transfer an outside party to a trunk over which toll calls might b e made. Since trunks have to b e s pecifically administered for OTTO TT, the CO R a n d FR L of th at trunk group should be examined to determine if it is a p propriate. OTTOTT is n ot a system-wide parameter. It is administered on a trunk group basis. There is however, a systemwide parameter which has to be enabled for this feature to work. If the a dministrator deems that the feature is not relevant to the business practices for the location the switch serves, the feature need not b e enabled. Alternately, if a temporary need presents itself, the feature can be temporarily enabled and then turned off. Interactions The following are feature interactions with OTTOTT . DCS Trunk Turnaround OTTO TT increases the set of cases in which DCS Trunk Turnaround may be accepted. However, use of OTTO TT in c o mbination with a DCS network is strongly discouraged. The following algorithm sp ecifies the fate of a request for DCS Trunk Turnaround. The checks are done in the order specified: nIf any of the p arties on the call are receiving local dial, busy, intercept, or reorder tone, d eny turnaround. nIf any remaining party is an answered station or attendant, then accept turnaround. nThe following a p plies if any remaining party is on an incoming trunk. For the purposes of this check, an outgoing DCS trunk that has previously been turned around (an odd number of times) via DCS trunk turnaround is
Feature Descriptions 3-1172Issue 3 March 1996 considered an incoming trunk with disconnect supervision. Similarly, an incoming DCS trunk that has previously b een turned around (an o d d number of times) is considered an outgoing trunk. nIf any remaining party is an outgoing trunk a dministered for OTTO TT operation that has received answer supervision, accept turnaround. nIf any remaining parties are outgoing DCS trunks, forward the turnaround request for each. nOtherwise, deny turnaround. Incoming Disconnect Supervision Outside of the US, incoming disconnect supervision is a switch capability that restricts transfers or conferences for certain incoming trunks. In the Unite d States, all incoming trunks are assume d to provide disconnect supervision. In some countries this assumption can not be made, so whether an incoming trunk provides disconnect supervision is administered for each trunk group. Release Link Trunks (RLT) This type of trunk is use d by Centralized Attendant Service (CAS). An outg oing RLT at a remote PBX, the CAS Branch, is used to access an attendant at the CAS Main. The attendant (at the Main) can transfer the incoming caller to a destination (station or trunk) at the Branch. The RLT is typically used only for a short p eriod of time and is usually idled after the transfer is established. A station at a branch can transfer an outgoing trunk to the CAS attendant (at the Main). This transfer could be viewed as an outgoing-trunk-to-outgoing-trunk transfer (the attendant is accessed via an outgoing RLT), although it is not blocked in G3vsV1/G3sV1 and G3iV1. Since administering outg oing disconnect supervision for RLT trunks provides no additional c a pability, this a dministration is not provid e d for RLT trunks. Restriction Restrictions on the transferring party may block a transfer or drop operation even when Outg oing Disconnect Supervision is provided. Trunk-to-Trunk Transfer If this feature-related system parameter is set to ‘‘restricted,’’ all trunk-to-trunk transfer/release/drop operations for p u blic trunks (CO, CPE, CAS, DID, DIOD, FX, and WATS) have calls terminated or receive denial. If the parameter is set to ‘‘none,’’ all trunk-to-trunk transfers (except CAS and DCS) have calls terminate d or receive denial. Hence, this option must b e set to ‘‘y’’ to enable OTTOTT operation for these types of trunks. The number of public network trunks allowed on a conference call is an administrable system p arameter. This numb er defaults to ‘‘1,’’ so if OTTOTT is
Transfer — Outgoing Trunk to Outgoing Trunk (with Security Measures) Issue 3 March 1996 3-1173 being used to connect two or more p u blic network trunks this limit must be increased. PCOL Interactions Transfer of personal CO lines (PCOLs) are not subject to the normal restrictions applied to transfer of other trunks. These transfers are allowed since the PCOL appearance remains on one or more stations as a feature button. The user must be aware that the DROP button cannot be used to disconnect the transferred-to party from the call. Hence, if an outgoing PCOL is transferred to an outgoing trunk and if neither of the trunks can supply a disconnect signal, then the two trunks lock up. Administration OTTO TT is enabled for all trunks in a particular trunk group by setting the ‘‘Disconnect Supervision - Out?’’ field on the “Trunk Group Ad ministration” form to the value ‘‘y.’’ This field specifies whether trunks in this trunk group provide disconnect supervision when used on an outgoing basis. OTTO TT is allowed if the system-wide Trunk-to-Trunk Transfer feature is assigned on the ‘‘Feature-Related System Parameters’’ forms and at least one of the outgoing trunks remaining on the call has its ‘‘Disconnect Supervision - Out’’ field set to ‘‘y.’’ This field is set independently of the trunk-to-trunk transfer system parameter, although both options must be set a p propriately if outg oing trunk to outgoing trunk transfers are desired. This field a p pears on the “Trunk Grou p” form for the following trunk group types: nAccess nAplt nCo (also for G3r) nDmi-bos (DID for G3r) nFx (also for G3r) nIsdn-pri (also for G3r) nTandem nTie nWA TS The field a p pears on the form, but cannot be changed when the “ Direction” field is set to incoming. If the field has a value of y when an incoming only trunk group is added or changed, the field value is changed (by the system) to n when the form is submitted, because the next time the trunk group is displayed the field value is n.
Feature Descriptions 3-1174Issue 3 March 1996 The allowable values are: n(o) y(es) The default is n. The following warning message is generated whenever this field is changed to the value y. !WARNING: Setting this field to ‘‘y’’ may result in trunk lock-ups. Hardware/Software Requirements OTTO TT can be activated for trunk groups with trunks assigned to the following trunk board s: nCentral Office Trunk b oard (TN747B) nAnalog Tie trunk Board (TN760C) nDS1 board (TN722B & TN767 & TN464C [Universal DS1] )