Home > ATT > Communications System > ATT DEFINITY Communications System Generic 3 Instructions Manual

ATT DEFINITY Communications System Generic 3 Instructions Manual

    Download as PDF Print this page Share this page

    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+.

    Page
    of 1584
    							Loudspeaker Paging Access — Deluxe
    Issue  3   March 1996
    3-867
    5. Press the Transfer button before the administered loudspeaker paging 
    timeout interval expires and go on-hook. (The p aging equipment is 
    released, the call is parked and is now waiting to be answered, and the 
    timer for the Call Park Time-out interval starts.)
    If another party was on the call and was placed on hold in Step 1, that 
    party is parked on the call and is connected to the paged party when he 
    or she answers the call (answer-b ack). The Conference button can be 
    pressed instead of the Transfer button to allow both the p aging and held 
    parties to be connected to the paged party on answer-back. (This is 
    known as Meet-Me Conferencing.)
    If the loudspeaker paging time-out interval expires before the Transfer 
    button is pressed, the paging user receives confirmation tone, the paging 
    equipment is released, the call is automatically parked on your extension, 
    and the calling party hears music (if provided). When the p ag e d party 
    answers the call, he or she is connected to the paging party.  The paging 
    party can then transfer the call to the calling party.
    If the Call Park Time-out interval expires, the c all returns to the p aging user 
    with the proper distinctive alerting (One-burst for internal calls and 
    conference calls with both internal and external p arties; Two-burst for 
    external calls).  If unanswered, the call follows the coverage path of the 
    p a ging user.
    If no answer-b ack is required on the call, hang up instead of pressing the 
    Transfer or Conference button. The parked call is dropped and the paging 
    equipment is released.
    Activation of Deluxe Paging by an Attendant for Another Party
    1. Press the Start button. The other p arty is placed on hold and the attendant 
    gets dial tone.
    2. Dial the trunk access code for the desired paging zone. (The attendant 
    gets dial tone.)
    3. Dial the extension number where the call is to be parked. (Confirmation 
    tone is heard and the call is temporarily parked.) The attendant can also 
    dial a ‘‘#’’ instead of the extension number to park the call on his or her 
    individual attendant extension (if assigned).
    4. Make the announcement. (The loudspeaker paging timer starts.)
    5. Press the Release b utton before the a dministered loudspeaker p a ging 
    timeout interval expires. (The pa ging equipment is released, the parked 
    call is now waiting to b e answered, and the timer for the Call Park Time-out 
    interval starts. If the Split button is pressed, the timer for the Call Park 
    Time-out interval starts, and  both the held party and the attendant are 
    parked and is connected to the call upon answer-back.)
    If the loudspeaker paging time-out interval expires before the Release 
    button is pressed, the attendant receives confirmation tone, the paging 
    equipment is released, and the call is automatically parked on the 
    console. 
    						
    							Feature Descriptions
    3-868Issue  3   March 1996 
    If the loudspeaker paging timeout interval expires before the Release 
    button is pressed, the attendant receives confirmation tone, the paging 
    equipment is released, the call is automatically parked on the console, 
    and the calling party hears music (if provided). When the p ag e d party 
    answers the call, he or she is connected to the paging party.  The paging 
    party can then transfer the call to the calling party.
    Activation of Deluxe Paging Answer-Back by the Paged Party
    1. Go off-hook to get dial tone.
    2. Dial the answer-back feature access code. (Dial tone is heard.)
    3. Dial the extension number where the call is parked, or dial ‘‘#’’ if the call is 
    parked on the extension you are using. (Music-on-Hold, if provided, is 
    removed from the p arked call, all parties associated with the parked call 
    receive confirmation tone, and the answer-back and parked parties are 
    connected.)
    Unparking a Loudspeaker Paging Call
    If a user wishes to unpark a loudspeaker paging call that is parked on his or her 
    extension, this can be accomplished by pressing the lighted Call Park  b utton.
    Considerations
    With Loudspeaker Paging Access — Deluxe, a user can be paged at any 
    location with loudspeaker paging equipment. Integrated Call Park capabilities 
    allow the p a ging party to p ark the call without dialing a separate Call Park feature 
    access code. When a user is away from his or her location and receives a c all, an 
    incoming call can be answered by another user.  The called party can then b e 
    p a ged and told what extension number the call is parked on.  The called party 
    can then answer the parked call from a nearb y voice terminal.
    The system can have up to nine individual zones plus one zone to activate all 
    zones simultaneously. A PagePac p a ging system can be used to provide up to 
    39 paging zones.
    An LDN or DID call cannot be connected to the paging facility.  However, the 
    attendant can make the page and park the incoming call.
    For non-local access of Deluxe Paging (such as Remote A c cess users, tie trunk 
    users, and so on) the ‘‘#’’ cannot be used to park the call on your own extension. 
    						
    							Loudspeaker Paging Access — Deluxe
    Issue  3   March 1996
    3-869
    Interactions
    The following features interact with the Loudspeaker Paging Access — Deluxe 
    feature.
    nBrid ged Call Ap pearance
    If the p arked  call includes a shared TEG, a shared PCOL, and/or a 
    redirected call with a Temporary Bridged Ap pearance the maximum 
    number of off-hook parties on the call is five, instead of six.  The sixth 
    position is reserved for the answer- back call.
    nCall Coverage
    If a coverage call is parked by Deluxe Paging, the Temporary Bridged 
    Appearance at the principal extension is maintained as long as the 
    covering user remains off-hook or places the call on hold.
    nCall Park
    A call cannot be parked on more than one extension at the same time.
    More than one call cannot be parked at the same extension at any given 
    time. If a user tries to park a Deluxe Paging call on an extension that 
    already has a parked call, that user receives intercept treatment.
    The Call Park feature provides up to 10 (40 for G3r) common shared 
    extensions  for use by attendants or by voice terminal extensions with 
    console permissions. These extension numbers are not assigned to a 
    voice terminal, but are stored in system translations and used to p ark a 
    call. These extension numbers are particularly useful when one party is 
    paged at the request of another party. The calling party is parked by 
    Deluxe paging and the extension number is announced. Common shared 
    extensions should be assigned to the optional selector console in the 00 
    through 09 (00 through 39 for G3r) block (bottom row) in any hundreds 
    group that the attendant can easily identify.  The lam p associated with the 
    extension number identifies call parked or no call parked (instead of 
    active or idle status).
    If the Call Park Time-out interval exp ires during Deluxe Paging, the call 
    normally returns to the originator of the Deluxe Paging call.  However, with 
    Remote Access and Tie Trunk Ac cess, the call goes to the attendant. If 
    unanswered, the call follows the coverage path of the paging user.
    nCall Pickup
    If a Call Pickup call is parked by Deluxe Paging, the Temporary Bridg e d 
    Appearance at the principal extension is maintained as long as the 
    answering pickup group member remains off-hook or places the call on 
    hold.
    nCall Waiting Termination
    Normally, a  call to a b usy single-line voice terminal results in a call waiting 
    tone being heard by the called voice terminal user.  If that user is in the 
    process of paging, the call waiting tone is not heard . 
    						
    							Feature Descriptions
    3-870Issue  3   March 1996 
    nCode Calling Access
    It is not possible to use a PagePac p a ging system for Code Calling 
    Access when multizone paging is desired. The PagePac systems exp ect 
    a two-digit code to access a particular zone. The system, however, 
    immediately plays the chime code once a connection is established.
    nConference — Attendant
    The maximum number of conferees on a p arked Deluxe Paging call is five.  
    The sixth conferee position is reserved for the answer-back call.
    A Deluxe paging call cannot b e conferenced unless a party was placed 
    on hold and parked with the call.  The reason for this is that p a ging 
    equipment cannot be placed on hold.
    nConference — Terminal
    For multiap p earance voice terminals, the maximum number of conferees 
    on a parked Deluxe Paging call is five.  The sixth conferee position is 
    reserved for the answer- back call.
    Single-line voice terminals can have a maximum of two conferees on a 
    parked Deluxe Paging call.
    A Deluxe paging call cannot b e conferenced unless a party was placed 
    on hold and parked with the call.  The reason for this is that p a ging 
    equipment cannot be placed on hold.
    nData Call Setu p
    If the Data button has been pressed as a pre-indication for modem 
    pooling, access to Deluxe paging is denied.
    nData Privacy
    If a call, with Data Privacy activated, is parked by Deluxe Paging, Data 
    Privacy for that call is automatically deactivated.
    nDID 
    A DID  call cannot be connected to a Deluxe Paging facility.
    nHold
    Deluxe Paging facilities cannot be placed on hold.
    nHunt Groups
    If a hunt group member parks a call using Deluxe Paging, the call is 
    parked on the member’s own individual extension, not the hunt group 
    extension.
    nLW C  
    If a user parks a call for his or her extension with the Conference button, 
    any parking or parked parties cannot activate LWC because that party 
    cannot be uniquely identified. 
    						
    							Loudspeaker Paging Access — Deluxe
    Issue  3   March 1996
    3-871
    nManual Originating Line Service
    Users assigned Manual Originating Line Service cannot access Deluxe 
    Paging.
    nMusic-On-Hold Access
    Music-On-Hold, if provided, is connected to the parked party when there 
    is only one conferee left on the parked call. Music-On-Hold is not 
    connected to a parked call with more than one conferee.
    nMultiple LDNs
    An LDN call cannot be connected to a Deluxe Paging facility.
    nNight Service
    If a night station user parks a Night Service call with Deluxe Paging, the 
    call is parked on the night station’s p rimary extension.
    nPCOL 
    If a PCOL call is parked by Deluxe Paging, the Temporary Brid ged 
    Appearance of the call is maintained at the PCOL extension until the call is 
    disconnected.
    nRemote Access
    Remote Access users can access Deluxe Paging unless they are 
    restricte d by COR from doing so.
    nRingback Queuin g
    Ringback Queuing is not provided for Deluxe Paging.
    nTEG  
    If a TEG member parks a call using Deluxe Paging, the call is parked on 
    the member’s own individual extension not the TEG extension.
    nTransfer
    A Deluxe paging call cannot b e transferred unless a party was placed on 
    hold and parked with the call.  The reason for this is that p aging 
    equipment cannot be placed on hold.
    Administration
    Deluxe Paging is administered by the System Manager.  The following items 
    require administration:
    nThe “Deluxe Paging” and “Call Park Timeout to Originator” field on the 
    “ Feature Related System Parameters”  form must be ad ministered as yes.
    nUp to 10 (one p er zone) Deluxe Paging buttons (per multiappearance 
    voice terminal and attendant console). Buttons are assigned through the 
    Attendant Direct Trunk Group Selection, Abbreviated Dialing, and Facility 
    Busy Indication features. 
    						
    							Feature Descriptions
    3-872Issue  3   March 1996 
    nTrunk access codes and Class of Restriction (per zone provided).
    nAnswer-b ack access code.
    nPaging expiration interval (from 10 seconds to 10 minutes).
    nCall Park expiration interval (from 1 to 90 minutes in intervals of one 
    minute).
    nCDR activation.
    nConsole p ermissions to allow voice terminal extensions to park calls on 
    common shared extensions (assigned via COS).
    nUp to 10 common shared extension numbers.
    If a PagePac p a ging system is to be used, it must be assigned a trunk access 
    code or extension number (PagePac 50/100/200 only).
    Hardware and Software Requirements
    Requires loudspeaker paging equipment and one port on a TN763 Auxiliary 
    Trunk circuit pack (TN763D supports A-law) for each individual zone. Paging 
    interface equipment, consisting of a 278A ad a pter and a 24-volt p ower supply, is 
    also required for each individual zone.  (This hardware can be shared with the 
    Code Calling Access feature.  Each feature is activated by the assigned trunk 
    access code.) A TN417 is also required in Italy, the United Kingdom, and 
    Australia.
    No a d ditional software is required. 
    						
    							Malicious Call Trace (MCT)
    Issue  3   March 1996
    3-873
    3
    Malicious Call Trace (MCT)
    Feature Availability
    This feature is available with Generic 3r V1 and optional with Generic 3 V2 and 
    later releases.
    Description
    MCT provides a way for terminal users to notify a predefined set of users that 
    they may be party to a malicious call. This set of users may then retrieve certain 
    information related to the call. Based on this information, it is possible to identify 
    the source of the malicious call or be capable of providing useful information to 
    personnel at an adjacent switch to aid in the tracking down of the call’s source. 
    This feature also provides a method of generating an audio recording of the call.
    Airlines, utility companies, g overnment offices and major corporations are a few 
    examples of customers that may experience malicious calls. A c cess to a feature 
    such as MCT may allow them to deter or respond appropriately to bomb threats, 
    product tampering, threats or other p ossible malicious calls.
    MCT enables a user to collect information which could be used to identify the 
    calling party. There are three different sets of MCT information that are collected 
    (and subsequently displayed) depending on whether the malicious call 
    originated within the system or outside of it.
    nIf the call originates within the system (the same node or DCS 
    subnetwork), the calling number is displayed on the controlling terminal.
    nIf an ISDN calling number identification is available on the incoming trunk, 
    then the calling number is displayed.
    nOtherwise, the incoming trunk equipment location is displayed.
    In the latter case it will be necessary for the customer to call the appropriate 
    connecting switch. For all three types of calls, the controlling terminal will also 
    display other information including the called number, activating number, 
    whether the call is active or not, and, if a p propriate, identification of any 
    a d ditional parties that may be on the call.
    During the alerting of a MCT-Controller, that controller’s disp lay will show the 
    message ‘‘MALICIOUS CALL TRACE REQUEST .’’  Incoming calls to the station 
    while this message is being displayed will not provide the incoming caller’s 
    display information as it normally would.
    Any action from the set itself that normally would impact the station’s display will 
    still be valid. For exam ple, when a user goes off-hook to dial a number, the 
    display may read ‘‘a=’’ then it will display the digits the person enters. This still 
    operates in this manner. Provided there is a call to trace (or that is actively being  
    						
    							Feature Descriptions
    3-874Issue  3   March 1996 
    traced), when the user’s display is in NORMAL mode, pushing the MCT-Control 
    button will display the next page of MCT-information for the controller regardless 
    of the previous state of the display.
    A station becomes the official controller of a particular trace by being the first 
    person to push the MCT-Control button when its display reads ‘‘MALICIOUS 
    CALL TRACE REQUEST’’. Once this has happened, the subsequent depressions 
    of this button will cause the following p a ges of MCT-information to be displayed:
    Page 1 ‘‘MALICIOUS CALL TRACE REQUEST’’
    Page 2 ‘‘MCT activated b y: 1002 for: 51001’’
    Page 3 ‘‘original call redirected from: 52001’’
    Page 4 ‘‘voice recorder port: 01C0104:
    Page 5 ‘‘party2: 01C1505 ’’ or ‘‘party2: 01C1505 ’’
    Page 6 ‘‘party3: 52001  : ’’ o r  ‘‘party3: 52001 < ISDN PORT ID>’’
    Page 7 ‘‘END OF TRACE INFORMATION’’
    The complete trace activity for MCT can be divided into three distinct phases:
    nFeature activation
    nFeature control
    nFeature deactivation
    Feature Activation
    While the recipient of the malicious call is actively talking on a suspected 
    malicious call, there are four ways that the MCT feature can be activated:
    1. The Recipient pushes a MCT-Activate button previously administered on 
    his or her set.
    2. The MC-Recipient p laces the call on HOLD, g ets a second call 
    appearance, then dials the MCT-Activate feature access code. Upon 
    hearing second dialtone, the MC-Recipient d ials the extension number 
    assigned to their set, a # sign, or they wait for timeout (10 seconds). For 
    obvious reasons, this is not the recommended activation a p proach.
    3. The Recipient signals a coworker to activate the feature for them on 
    another set. The coworker would push the MCT-Activate button to dial the 
    feature access code. Upon hearing dialtone, the coworker dials the 
    extension on which the Recipient is talking.
    4. Under certain c irc umstances, a MCT-Controller on switch A may request a 
    controller on switch B to continue tracing a call that was tandemed 
    through switch B. In this case the controller on switch A would supply the  
    						
    							Malicious Call Trace (MCT)
    Issue  3   March 1996
    3-875
    controller on switch B with the trunk member port id they wish to have 
    traced. The controller on switch B would then activate the feature by 
    pushing a MCT-Activate button or dialing the FAC and upon hearing 
    second dialtone, enter a ‘‘*’’ character followed by the trunk port i d. For 
    example, trunk port id 01C0401 would be entered as 0130401. The letters 
    A through E of a port i d are entered as 1 through 5 on the station keyp a d.
    Once the MCT feature has been activated, information associated with the 
    call is stored. Also, a group of previously administered extensions will 
    b e gin alerting. Each should have been previously administered with an 
    MCT-Control button. In a d dition, if a MCT-Record er has been 
    administered for your system and is available, it will b e attached to the 
    suspected malicious call.
    Feature Control
    After being alerted of an MCT activation, the first controlling terminal to resp ond 
    by pushing an administered MCT-Control button will be considered the 
    controlling p arty for the c all. Alerting on the rest of the set of c ontrolling terminals, 
    if any, will stop.
    The initial MCT-Control button push generates a display identifying the called 
    party b ecause both the called extension is displayed. Subsequent button pushes 
    will cycle through the MCT information. The c omplete set of MCT information may 
    be disp layed repeatedly by continued pushes of the button.
    In the case of a malicious call involving a non-ISDN trunk, the controlling party 
    would call the personnel at the connecting switch during the feature control 
    stage to request that a trace b e performed. For this to be feasible, the controlling 
    party should have the telephone number for the connecting switch available as 
    well as a cross-reference of the system’s trunk-port numbers (including DS1 
    channel number, if appropriate) versus the trunk equipment locations at the 
    connecting switch.
    Feature Deactivation
    The controlling party may at any time (but usually after completing the trace) 
    complete the MCT feature activity by dialing the MCT-Deactivate FAC. This 
    deactivation frees any resources involved in the current trace activity that were 
    blocked by the MCT feature and, if a ppropriate, disconnects the MCT Voice 
    Recorder from the call.
    The following are the steps in the MCT sequence:
    nMCT-Activate FAC — When followed by the extension receiving the 
    malicious call, this initiates the MCT sequence. When followed by p ressing 
    the asterisk button on the dial p ad followed by the port id, this makes the 
    user the MCT Controller for a call that may involve this particular trunk 
    member. 
    						
    							Feature Descriptions
    3-876Issue  3   March 1996 
    nMCT-Activate Button Push — This initiates an MCT sequence with the 
    assumption that a malicious call is currently active on the terminal 
    generating the MCT-Activate button push.
    nMCT-Control Button Push — When generated from a terminal with a 
    display, this tracks the progress of the trace information during an MCT 
    sequence.
    nMCT-Deactivate FAC — When entered from a controlling terminal, this 
    ends an MCT sequence. This FAC will be accepted only when entered 
    from a currently active controlling terminal.
    Considerations
    An MCT feature activation does not generate a call within the system to alert the 
    controlling terminals. Since the alerting is not a call, it is not impacted by the 
    existence or length queues associated with the controlling terminals.
    There are, however, still interactions with real calls at the alerted terminals and 
    these are noted in the next section. If a trunk is involved in the MCT, this resource 
    will be blocked from being drop ped from the switch-side to facilitate the tracing 
    activity. Any terminal involved in the call will not be blocked from dropping.
    Display Information
    Although this is not a feature in and of itself, it is included here to point out that 
    display information may be affected by MCT. With the exception of Emergency 
    Access to the Attendant, any feature that would normally provide display 
    information will not do so on a terminal acting as the controlling terminal. The 
    remainder of that feature’s functionality would remain the same only its a bility to 
    display information will be blocked. This remains in effect until the terminal 
    performs an MCT-Deactivate.
    Switch Failure
    MCT information relating to a currently active malicious call is lost during a switch 
    failure.
    Interactions
    The following is a d esc ription of how certain features b ehave differently when 
    used in conjunction with an MCT activity.
    nAttendant Interposition Calling and Transfer
    Provided that the console is not busy, an attendant who is acting as a MCT 
    controller may receive alerting call, but that attendant will not receive the 
    display information. 
    						
    All ATT manuals Comments (0)

    Related Manuals for ATT DEFINITY Communications System Generic 3 Instructions Manual