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
    							Class of Restriction (COR)
    Issue  3   March 1996
    3-547
    restrictions, calling party restrictions, called p arty restrictions, and miscellaneous 
    restrictions. CORs can be established, as required, to provide the needed 
    combinations.
    Interactions
    The following features interact with the Class of Restriction feature.
    nAAR/ARS Partitioning
    Partition Group Numbers are assigned via a COR.
    nAAR/ARS
    Originating FRLs are assigned via a COR. Termination and Misc ellaneous 
    Restrictions do not a p ply to ARS/AAR calls.
    nBrid ged Call Ap pearance
    The COR assigned to a voice terminal’s primary extension also a p plies to 
    calls originated from a bridged call appearance of that extension on 
    another terminal.
    nCall Coverage
    Users who may normally be restricted from calls can still receive calls 
    directed to them via Call Coverage. 
    When a call goes to coverage, it is the called party’s (not the covering 
    party’s) restrictions that are used.
    nCall Forwarding All Calls
    If a call would normally be restricted between the forwarding and 
    forwarded-to extensions, Call Forward ing activation is denied.   
    Restrictions are always checked when Call Forwarding is activate d, but 
    not when a call is actually forwarded.
    nControlled Restriction
    Restrictions assigned via the Controlled Restriction feature override the 
    calling and called party restrictions via a COR. Activate and deactivate 
    controlled restrictions for another extension or group of extensions.
    nEmergency Access to Attendant
    Emergency Access to Attendant calls are not restricted by COR.
    nForced Entry of Account Code
    This feature can be assigned via a COR.
    nInward Restriction
    This feature is assigned via a COR.
    nManual Terminating Line Restriction
    This feature is assigned via a COR. 
    						
    							Feature Descriptions
    3-548Issue  3   March 1996 
    nOrigination Restriction
    This feature is assigned via a COR. 
    						
    							Class of Restriction (COR)
    Issue  3   March 1996
    3-549
    nOutward Restriction
    This feature is assigned via a COR.
    nPrivate Network Access and Public Network Access
    Access to the public network via the private network is allowed or denied 
    via a COR (assuming the private network provides the capability to 
    access the public network).
    nTermination Restriction
    This feature is assigned via a COR.
    nAll-Toll Restriction, TAC-Toll Restriction
    This feature is assigned to an originating facility via a COR. (Toll 
    Restriction is assigned to an outgoing trunk group on the trunk group 
    form.) TAC-toll restriction can be disabled for specific outgoing trunk 
    groups on the trunk group form.
    Administration
    COR is administered by the System Manager. For each COR which is assigned, 
    the following items must b e administered:
    nAccess to Malicious Call Trace
    nCOR Number
    nFR L
    nPermission to access EPSCS  o r  CCS A off-net facilities
    nCalling Party Restriction
    nCalled Party Restriction
    nPermission to call other CORs
    nForced Entry of account codes for CDR (yes or no)
    nPartitioned Group Number
    nPriority Queuing (yes or no)
    nCan Be Service Observed (yes or no)
    nCan Be A Service O bserver (yes or no)
    nTime of Day Plan Numb er
    nDirect Agent Calling 
    nFacility Access Trunk Test
    nFully Restricted Service
    nRestricted Call List
    nUnrestricted Call List  
    						
    							Feature Descriptions
    3-550Issue  3   March 1996 
    Assignment of Restrictions
    A COR is assigned to each of the following:
    Voice Terminals
    All voice terminals must b e assigned a COR. The same COR may b e assigned to 
    all voice terminals or a unique COR may be assigned to a particular voice 
    terminal or group of voice terminals. This COR a pplies individually to each voice 
    terminal and is independent of all other COR a p plications, such as 
    Misc ellaneous Restriction groups or UCD  groups.
    The main items of concern for individual voice terminals are calling party 
    restrictions and called party restrictions (discussed previously under ‘‘Use of 
    CORs’’). If no restrictions are needed for a certain group of voice terminals, 
    ‘‘none’’ can b e specified for b oth calling party and called party restrictions. If it is 
    desired to restrict a group of voice terminals from making outside calls, a COR 
    specifying a calling party restriction of ‘‘outward’’ should be established.
    Add itionally, miscellaneous restrictions, restrictions to CCSA and EPSCS 
    off-network calling capabilities, and FRLs also apply. A separate COR must be 
    established for each unique set of restrictions.
    Trunk Groups
    Each trunk group is assigned a COR. Trunk groups are assigned CORs mainly 
    for the use of miscellaneous restrictions.
    Calling p arty and c alled party restrictions should be ‘‘none.’’ Whether or not a CO 
    or FX trunk group is restricted is specified on the trunk group form used during 
    implementation.
    CO and FX trunk groups default to being toll restricted for TAC calls. Toll 
    Restriction for TAC calls can be disabled for certain CO/FX trunk groups on the 
    trunk form.
    Attendant Consoles (as a group) and Individual
    Attendant Extensions
    Attendants are normally allowed full access to the system’s capabilities. 
    Therefore, calling and called party restrictions are usually set to 
    none. Also, 
    access to the attendant is normally allowed to all CORs. This is a c complished via 
    a 
    y (yes) for the attendant’s COR in the “CALLING PERMISSION” field on the 
    screen form for each assigned COR.
    Tenant restriction are usually assigned to permit:
    — Attendant and served tenants to call each other
    — Attendant to call trunks, etc. that served tenants can access. 
    						
    							Class of Restriction (COR)
    Issue  3   March 1996
    3-551
    Data Module, Loudspeaker Paging Access Zone,
    Code Calling Access Zone, and Remote Access
    Barrier Code
    Each data module, Loudspeaker Paging Access zone, Code Calling Access 
    zone, and Remote Access barrier code is assigned a COR. Through 
    Misc ellaneous Restriction groups certain users are allowed access to certain 
    facilities, while other users are denied access. For example, if a Loudspeaker 
    Paging Access zone has a COR of 3, then a voice terminal with a COR marked 
    Calling Restriction = N for COR 3 c annot access that Loudspeaker Paging 
    Access zone.
    Terminating Extension Group, Automatic Call 
    Distribution Split, Uniform Call Distribution 
    Group, and Direct Department Calling Group
    These groups are set up to receive calls. A COR is assigned to each group. This 
    COR is distinct and separate from CORs assigned to the individual group 
    members.  The group COR allows or denies calls to the group. Since 
    Misc ellaneous Restriction groups are normally used to restrict calling, called 
    party restrictions should be specified as ‘‘none.’’  Since a group cannot originate 
    a call, calling party restrictions do not apply.  However, for simplicity, ‘‘none’’ is 
    normally specified. For calls by group members or calls to individual group 
    members, the COR assigned to the voice terminal ap p lies.  The group COR has 
    no effect on calls directly to or from a group member.
    The imp ortant aspect of these CORs is that they allow the called party restrictions 
    of the group (normally none) to be different from the called party restrictions of 
    the individual g roup members (Inward, Manual Terminating Line, or Termination).
    Hardware and Software Requirements
    No a d ditional hardware or software is required. 
    						
    							Feature Descriptions
    3-552Issue  3   March 1996 
    Class of Service (COS)
    Feature Availability
    Class of Service is available with all Generic 3 releases.
    Description
    Defines whether or not voice terminal users may access the following features 
    and functions:
    nAutomatic Callback
    nCall Forwarding 
    nData Privacy
    nPriority Calling
    nOff-Hook Alert 
    nConsole Permission 
    nClient Room
    There are only two choices for each feature; a voice terminal user or individual 
    attendant 
    can or cannot access the feature.
    There are 16 possible COSs. Each COS is used to allow or d eny access to seven 
    features and functions. The parameters can be changed to meet individual COS 
    needs. To assign a COS, administer the d esired allowed/denied combination of 
    features and functions for one of the 16 COSs, and indicate that COS number 
    when implementing voice terminals. Which COS  numb ers represent which 
    combination of allowed/denied features are given in the 
    DEFI NIT Y 
    Communications System Generic 3 Version 4 Implementation
    , 555-230-655, or 
    DEFI NI TY Com munications System Generic 3 V2/V3 Implementation, 
    555-230-653.
    In a ddition to Automatic Callback, Call Forward ing, Data Privacy, and Priority 
    Calling, the DEFINITY system Generic 3 offers the following functions:
    nOff-Hook Alert
    Can be administered only if the optional Emergency Access to the 
    Attendant feature is provided. The  Off-Hook Alert function lets the 
    customer administer yes/no to each of the 16 established COS 
    parameters according to the allowed/denied capability to access this 
    feature. 
    						
    							Class of Service (COS)
    Issue  3   March 1996
    3-553
    nConsole Permission
    Allows multi-appearance voice terminal users to control the same features 
    the attendant controls. This feature is usually available to front desk 
    personnel in a hotel/motel. With console permission, you can do the 
    following:
    — Activate Automatic Wakeup for another extension.
    — Activate and d eactivate controlled restrictions for another extension 
    or group of extensions. 
    — Activate and deactivate Do Not Disturb for another extension or 
    group of extensions.
    — Activate Call Forwarding for another extension.
    nClient Room
    This function can be administered when Hosp itality Services are provided. 
    This function allows the Check-in, Check-out, Room Change/Swap, and 
    Maid Status features. In addition, it is required at consoles or terminals 
    that are to receive Message Waiting Notification.
    Other than to allow/deny access to the described features, COS has no other use 
    in the system. Restriction groups and call origination/reception privileges are 
    defined and assigned by a COR, not a COS.
    Considerations
    COS is used to assign as many as seven features. Each voice terminal and 
    individual attendant is assigned one of 16 COSs to determine whether or not it 
    has any or all of these features. COS serves no other purpose than to assign 
    these features.
    Interactions
    None.
    Administration
    A COS is assigned to each voice terminal extension by the System Manager. The 
    parameters for each COS can be changed. The only other administration 
    required is the assignment of a COS to each individual attendant and voice 
    terminal.
    A COS should be assigned on ‘Data Module’ and ‘Access Endpoint’ forms. A 
    separate COS should be used for data applications.
    A COS can also be assigned to a remote access barrier code. 
    						
    							Feature Descriptions
    3-554Issue  3   March 1996 
    Hardware and Software Requirements
    No a d ditional hardware or software is required. 
    						
    							Code Calling Access
    Issue  3   March 1996
    3-555
    Code Calling Access
    Feature Availability
    Code Calling Access is available with all Generic 3 releases.
    Description
    Allows attendants, voice terminal users, and tie trunk users to page with coded 
    chime signals.
    As many as nine individual p aging zones can be p rovided. (A zone is the location 
    of the loudspeakers, for example, conference rooms, warehouses, etc.) In 
    a d dition, one zone can be provided to activate all zones simultaneously. Each 
    p a ging zone requires a separate Code Calling A c cess c o de.
    A paging party dials the Code Calling Ac cess c o de and the extension numb er 
    assigned to the person to be paged. The p a ging party is automatically parked 
    (through the Call Park feature) on the p a ged p arty’s extension number. The 
    system translates the number to a chime code and then plays the c o de over 
    loudspeakers. The  paged party, recognizing the chime code, can answer the 
    call from any voice terminal within the system by dialing the Call Park Answer 
    Back access code and his or her own extension number.
    Considerations
    With Code Calling Ac cess, users do not have to b e at their own voice terminal in 
    order to answer calls. Users who are frequently away from their voice terminal or 
    at a location where a ringing voice terminal might be disturb ing can be assigned 
    a chime code. When a user’s chime c o de is heard , that user can answer the 
    parked call from a nearby voice terminal.
    The system can have up to nine individual zones plus one zone to activate all 
    zones simultaneously.
    As many as 125 three-digit chime codes can be provided. Only one extension 
    number can be assigned to each chime code.
    Interactions
    The following features interact with the Code Calling Access feature.
    nAbbreviated Dialing
    If Abbreviated Dialing is used for Code Calling Access, special characters 
    should not be used. If they are used, the call is denied. 
    						
    							Feature Descriptions
    3-556Issue  3   March 1996 
    nCall Park
    This feature is automatically provided with Code Calling Access.
    nConference — Attendant
    A call cannot be conferenced while accessing paging equipment. The 
    attendant can, however, release the call after paging the called party.
    nConference — Terminal
    A call cannot be conferenced while accessing paging equipment.
    nControlled Restriction
    Controlled Total restriction prohibits use of Code Calling Access.
    nLoudspeaker Paging Access
    It is not possible to use a PagePac. paging system for Code Calling 
    Access when multi-zone p aging is desired. The PagePac paging systems 
    expect a two-digit code to access a particular zone. The system, however, 
    immediately plays the chime code once a connection is established.
    nMisc ellaneous Trunk Restriction
    Voice terminals and tie trunks with this restriction cannot use Code Calling 
    Access.
    nOrigination Restriction
    This restriction prohibits use of Code Calling Access.
    nTransfer
    A call cannot be transferred while accessing paging equipment.
    Administration
    Code Calling Access is administered by the System Manager. The following 
    items can be administered:
    nTrunk access code and COR for each of the nine individual paging zones 
    and for the zone used to activate all zones simultaneously.
    nNumber of times (one to three) the chime code plays. If the chime code is 
    set to play more than once, the paging  party must remain on the call until 
    the chime code is repeated the desired number of times.
    nLoudspeaker locations (name of zone).
    nThree-Digit chime codes for extensions. The c o des are combinations of 
    the digits one through five. 
    						
    All ATT manuals Comments (0)

    Related Manuals for ATT DEFINITY Communications System Generic 3 Instructions Manual