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+.
Malicious Call Trace (MCT) Issue 3 March 1996 3-877 nBrid ged Appearance — Temporary If a covering user has activated a trace, the original called party may bridge on to the call provided the normal rules governing such. nBrid ged Call Ap pearance If the user of a primary extension is the Recipient of the indication call, then a station with a bridged appearance of this extension may bridge onto the call according to the normal rules g overning such. For an MCT-Activate button push, if the currently active extension is a bridged appearance, the system will record the primary extension as the MCT recipient. For an MCT-Ac tivate FAC, the user should dial the numb er of the terminal with the bridged appearance that is actually on the call, instead of the bridged number. However, the system will log the primary extension as the Recipient. Likewise, for self-originated MCT activations via the FAC, the system will log the primary extension as the MCT Recipient provided that the recently ‘‘held’’ appearance is a bridged appearance. (When performing an MCT-Activate operation for one’s self, the ability to dial ’#’ or wait for interdigit timeout is still valid.) nBusy Verification of Terminals and Trunks Sometimes while tracing a malicious call, the MCT Controller may need to contact a potential MCT Controller on an adjacent switch through which the call may have tandeme d. That person, once involved in the call, would then perform an MCT activation. This introduces potential problems: — The malicious caller would hear a warning tone as a result of the intrusion. — The person performing the MCT Activate is not guaranteed to be the same person that will perform the associated MCT Control operation thereby, losing the ‘‘continuity’’ of tracing this call because of a trace on another switch. For G3r, this will be handled by allowing a user to enter an asterisk on the dial pad followed by the p ort id, during the second dialtone after an MCT Activate. In such a case, in order for the controller on the adjacent switch to get the appropriate MCT information, that person will have to enter onto the c all via the Busy Verification feature. Furthermore, such an intrusion via busy verification results in a warning tone being a p plied which alerts all members on the call of the intrusion. The intrusion tone will not be a p plied if the MCT Controller on the adjacent switch activates b usy verification immediately after generating a MCT Activate but before the routing timeout occurs. nCall Waiting A call may not wait on the line of a Recipient indication call. Instead, the MCT Recipient’s line will a p pear busy.
Feature Descriptions 3-878Issue 3 March 1996 nConference The conference operation can be used by an MC-recipient to temporarily place a malicious caller on hold. The MC-recipient may choose to d o this in order for MCT-Activate to generate a stimulus via a FAC. This is done by the user initiating the conference operation, receiving the second dialtone, entering the MCT-Ac tivate FAC then halting the remainder of the conference operation and simply returning to the malicious caller’s appearance. MCT-Activate can be generated for a member of a conference. As a point of clarification, the MCT-Activate is not affected by the number of parties involved in the conference. nDCS If a voice terminal within the DCS network is involved in a malicious call, then the extension number will b e record ed and subsequently disp layed with the MCT information as appropriate. Beyond this functionality, DCS transparency is not provided for MCT. MCT-Activate, MCT-Control and MCT-Deactivate a ctivities must b e p erformed by terminals within the same DCS n o de. nEmergency Access to the Attendant This feature continues to operate as expected however, it can affect how an MCT-Control operation works. Ordinarily, during an MCT-Control operation, no other feature may access the display of the terminal acting as the controlling terminal. However, if an Emergency Access call terminates at a console acting as the controlling set, MCT will relinquish control of the display until this call has been completed then MCT will again maintain exc lusive control over the display. nIndividual Attendant Access An attendant acting as a controlling terminal (provided the attendant has unbusied the console) may receive alerting for a call to the individual attendant access extension b ut, the display information will not be displayed. nMake-Busy Make-Busy activations are attemp ted by the switch for any station or console generating an MCT-Control stimulus. The attempt will b e made for Make-Busy button(s) administered on the station or console. The success or failure of the attem pt is determined by the normal rules g overning Make-Busy activation. When this station generates an MCT-Deactivate stimulus, the state of the Make-Busy feature for this set will be returned to whatever the state was prior to the MCT-Control stimulus. nPersonal Central Office Line (PCOL) If a PCOL is involved in an MCT, then that trunk may be held up by the switch until the MCT-Deactivate has been processed.
Malicious Call Trace (MCT) Issue 3 March 1996 3-879 nPosition Busy A Position Busy activation will be attemp ted by the switch for any attendant in the role of MC-recipient activating PB. The success or failure of the attempt will be determined by the normal rules governing a Position Busy activation. When this station generates an MCT-Deactivate stimulus, the state of the Position Busy feature for this set will be returned to whatever the state was prior to the MCT-Control stimulus. nPriority Calling A priority call attempt towards the MCT Recipient will be denied. nCentralized Attendant Service An MCT-Ac tivate p rocessed on a branch PBX cannot b e controlled by an attendant at the main PBX. The MCT controlling activity will have to b e processed by a controlling terminal at the branch PBX. MCT-Activate, MCT-Control, and MCT-Deactivate activities must b e performe d by terminals within the same PBX. nR2 Multi-Frequency Code MCT does not use R2 Multi-Frequency Code (MFC) signaling. nSend All Calls If users’ stations activating MCT-Control have a Send-All-Calls (SAC) button administered on their sets, then the SAC will be activated. This provides consistenc y with the automatic Position Busy activation that occurs when an attendant activates the MCT-Control button. Like the Position Busy, the SAC will be an activation attempt whose success or failure is dependent on the normal rules governing such. When this station-user generates an MCT-Deactivate stimulus, the state of the Send All Calls feature for this set will be returned to whatever the state was prior to the MCT-Control stimulus. nTransfer If the MC-Recipient transfers a malicious call, the MCT information (displayed on the controlling terminal and saved in the MCT history) will still identify the transferring party as the MCT Recipient. Also, the Transfer operation can be used by an MC-Recipient to temp orarily place a malicious caller on hold. The MCT Re cipient may choose to do this in order to send an MCT-Activate stimulus via a FAC. This is done by the user initiating the Transfer operation, receiving the second dialtone, entering the MCT-Ac tivate FAC, then halting the remainder of the Transfer operation and simply returning to the malicious caller’s appearance.
Feature Descriptions 3-880Issue 3 March 1996 Administration The following describes administration. nCOR Administration This provides a user access to MCT features. nFAC Ad ministration This provides Feature Access Codes with which MCT-Activate and MCT-Deactivate may be performed. nStation Administration This provides a user access to the MCT-Activate and/or MCT-Control buttons. nSystem Parameters Ad ministration This determines a p plication of a tone audible to all parties during the recording of a malicious call and trunk group where the port id of the recorders are listed. Also, with this administration, the administrator is provided with the set of controlling terminals and the assignment of ports for MCT voice recorders. This is done on the “MCT Groups — Extension” form. nMCT History Ad ministration A user may see a history of the last 16 trace activities. nSystem-initiated Operations For completeness, the following are the system initiated operations for MCT: — Conversation Recording — After processing a MCT-Activate button push or FAC, the system will attach a MCT Voice Record er to record the conversation. — Historical Recording — After processing a MCT-Activate b utton push or FAC, the system will record the MCT-information to allow subsequent retrieval of the data via the “ MCT History Ad ministration” form.
Malicious Call Trace (MCT) Issue 3 March 1996 3-881 nCapacities Number of Malicious Calls being Traced: — Up to 16 MCTs may be active in the system at any given time. This maximum includes currently controlled calls and calls in queue for being controlled. Number of Voice Recorders: — Only one MCT Voice Re corder may be used for each malicious c all being controlled or queued for being controlled. (This also implies that the system maximum for MCT Voice Recorders is 16 since that is the maximum number of allowable active MCTs). Number of Controlling Terminals: — Up to100 terminals may be identified as controlling terminals. Hardware/Software Requirements Below is listed the set of hardware which may be used to support the MCT feature: nStations with displays nAttendant consoles nMCT voice recorders nAuxiliary trunks (278A Ad apter in conjunction with a TN763 or SN231) nTrunks
Feature Descriptions 3-882Issue 3 March 1996 Manual Message Waiting Feature Availability This feature is available with all Generic 3 releases. Description Enables multiap p earance voice terminal users, by pressing a designated button on their own terminals, to light the status lamp associated with the Manual Message Waiting button at another multiappearance voice terminal. Activating the feature causes the lamp to light on both the originating and receiving voice terminals. Either terminal user can cause the lamp to g o dark by pressing the button. Considerations This feature can be administered only to p airs of voice terminals such as a secretary and an executive. The secretary might press the designated button to signal the executive that a call needs answering. The executive might press the button to indicate Do Not Disturb or Not Available to the secretary. (The button can be marked to reflect the intended use.) Interactions None. Administration Manual Messa ge Waiting is administered on a per-voice terminal b asis by the System Manager. The only administration required is the assignment of the Manual Messa ge Waiting buttons to the voice terminals. Hardware and Software Requirements No a d ditional hardware or software is required.
Manual Originating Line Service Issue 3 March 1996 3-883 Manual Originating Line Service Feature Availability This feature is available with all Generic 3 releases. Description Connects single-line voice terminal users to the attendant automatically when the user lifts the handset. The attendant code is stored in an Ab breviated Dialing list. When the Manual Originating Line Service voice terminal user lifts the handset, the system automatically routes the call to the attendant using the Hot Line Service feature. A Manual Originating Line Service user can receive calls allowed by the assigned COR. Call reception is not affected by Manual Originating Line Service. Considerations Manual Originating Line Service is useful in any application where all call originations are screened by the attendant. The user simply lifts the handset and is connected to the attendant. The number of single-line voice terminals that can be assigned Manual Originating Line Service is not limite d. Interactions A Manual Originating Line Service call is a Hot Line Service call to the attendant. A voice terminal user cannot activate features that require dialing. When a Night Service feature is activated, the Manual Originating Line Service call is redirected. Administration Manual Originating Line Service is administered on a p er-voice terminal basis by the System Manager. The following items require administration: nAbbreviated Dialing Lists (the attendant code must b e a list entry) nHot Line Destination Hardware and Software Requirements No a d ditional hardware or software is required.
Feature Descriptions 3-884Issue 3 March 1996 Manual Signaling Feature Availability This feature is available with all Generic 3 releases. Description Allows a voice terminal user to signal another voice terminal user. The receiving voice terminal user hears a two-second burst of tone. The signal is sent each time the b utton is pressed. If the receiving voice terminal is already being alerted with an incoming call, Manual Signaling is denied. The status lamp associated with the Manual Signaling button at the originating voice terminal flutters briefly to indicate the denial. Considerations With Manual Signaling, one voice terminal user can signal another voice terminal user. The meaning of the signal is prearranged between the sender and the receiver. When a voice terminal user presses the Manual Signaling button, the associated status lamp lights for two seconds. Interactions None. Administration Manual Signaling is assigned on a per-voice terminal basis by the System Manager. The only administration required is the assignment of the Manual Signaling button to the originating voice terminal. Hardware and Software Requirements No a d ditional hardware or software is required.
MERLIN® /System 25 Voice Terminal Su p port — 731xH Series Issue 3 March 1996 3-885 MERLIN®/System 25 Voice Terminal Support — 731xH Series Feature Availability This feature is available with all Generic 3 releases except G3i-Global and G3rV1. Description The feature allows MERLIN/System 25 customers to reuse the 7309H and the following 731xH series ATL (hybrid) voice terminals with the DEFI NI TY Communications System G3vsV1/G3sV1, G3iV1, G3V2, and later releases: n7313H n7314H n7315H (with built-in display) n7316H n7317H (with built-in display) All of the above voice terminals connect to the DEFINITY switch via existing TN762B hybrid circuit pack and are sup p orte d in native mode. However, not all fixed-feature b uttons on these terminals function comp letely when connected to the DEFINITY switch. Both the 7315H and 7317H are e quipped with integrated 16-character LCD displays nUse the disp-norm button to toggle between normal call display mode (to d isp lay incoming and outgoing call data) and local voice terminal mode (to d isp lay the voice terminal supplied date and time). NOTE: When in local mode, the voice terminal can receive incoming calls or you can go ‘‘off hook’’ and dial an outgoing call. In these cases, the voice terminal automatically changes to normal call display mode. nDisplayed Messages c onsist of one or two 16-character lines. The ‘‘scroll’’ button is used to toggle between the two lines of a display. (For one-line displays, pressing the ‘‘scroll’’ b utton has no effect.) NOTE: For redirected calls sometimes the name is truncated at 14 characters and is followed by a space and ‘‘
Feature Descriptions 3-886Issue 3 March 1996 to this station (for examp le, using call forward ing or call coverage). Scroll to the second line of the disp lay to view the name of the calling party. The 7315H and 7317H voice terminals display information differently from other voice terminal displays. For example, the 7315H and 7317H d o not identify which call appearance is in use. Another example is that reason codes for calls direct or redirected to the station are restricte d to one character codes. These codes may be different from what is seen on digital displays. Multiple character reason codes are changed to one character reason codes for call redirection. Table 3-70 lists the redirection reason codes for the two different terminal typ es: Any that is blank means that there is no flag that a p plies and/or the feature does not route the call to the respective voice terminal. Table 3-70. Merlin Terminal Codes Call Type Digital Hybrid Send-All-Calls to Coverage s s Coverage Path Criteria: Cover-All c C Coverage Path Criteria: Don’t-Answer d d Coverage Path Criteria: Busy/Active b b Return-Call to Attendant rt Recall-Call r c Redir Attendant Control Trunk Group Access tc Redir by intercept treatment to Attendant ic Priority Call priority ! Call Forward f f Intercom Call ICOM i Night Station Service Call n n Call Pick-up p P DID Trunk Calls to LDN l d # Call-Park Time-Out i c p Transfer Call Time-Out rt Consult to Covered Principle-Station priority ! Continued on next page