Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide
Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communication Server Release 8.2 Administrators Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 413 Lucent Technologies manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1307 Class of Restriction 20 Interactions nAAR/ARS Originating FRLs are assigned via a COR. Termination and Miscellaneous Restrictions do not apply to ARS/AAR calls. nAAR/ARS Partitioning Partition Group Numbers are assigned via a COR. nBridged Call Appearance The COR assigned to a telephone’s primary extension also applies to calls originated from a bridged call appearance of that extension on another terminal. nCall Coverage Users who normally are restricted from calls can still receive calls directed to them via Call Coverage. When a call goes to coverage, the called party’s (not the covering party’s) restrictions are used. nCall Forwarding All Calls If a call is restricted between the forwarding and forwarded-to extensions, Call Forwarding is denied. Restrictions are always checked when Call Forwarding is activated, but not when a call is forwarded. nCall Vectoring When a call is directed to a VDN extension, the COR of the caller and the VDN are compared to determine if the caller can access the associated call vector. nClass of Service In some cases, the COR can be overridden by the COS. See the Trk-to-Trk Restriction Override field documented with the ‘‘ Class of Service’’ on page 532. nControlled Restriction Restrictions assigned via Controlled Restriction override COR restriction. nEmergency Access to Attendant Emergency Access to Attendant calls are not restricted by COR. Interactions for called-party and calling-party restrictions nNight Service Night Service and Night Station — Trunk Answer From Any Station override Inward, Manual Terminating Line, and Public Restrictions.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1308 Class of Restriction 20 nTie-Trunk Access Incoming dial-repeating tie-trunk calls can be completed directly to an inward-restricted or public-restricted extension but cannot be extended by an attendant to an inward-restricted telephone. nTransfer Incoming trunk calls cannot be transferred to an inward-restricted extension when a 3-way COR check is made. Incoming trunk calls can be transferred from an unrestricted extension to an inward-restricted or public-restricted extension if the 3-way COR check on Conference is overridden. Interactions for fully restricted service restrictions nCentralized Attendant Service Since COR information is not passed over Release Link Trunks (RLT), fully restricted service allows all CAS calls. Therefore, CAS allows a public network call to complete to a fully-restricted station. nDistributed Communications System Fully Restricted Service allows all DCS calls because COR information is not transparent for DCS. DCS can allow a public network call to be completed to a Fully Restricted station. nPower Failure Transfer All authorization features are bypassed when the switch is in Emergency Transfer Mode. nHunt Group The COR assigned to the Hunt Group is checked on calls redirected by the DDC or UCD of the hunt group. Extensions in the hunt group that have Fully Restricted Service can receive calls from the public network (via the hunt group) if the COR of the Hunt Group does not have Fully Restricted Service. nPersonal Central Office Line Do not assign fully restricted service to users who have a personal CO line. If you do, you will be paying for a CO line that no one can use! nRemote Access If a barrier code is entered during connection to remote access, the code’s associated COR is used for authorization checks. If remote access does not require a barrier code, then the default barrier code’s COR is used. Remote Access can require an authorization code instead of or in addition to the barrier code. If an authorization code is required, the authorization code’s associated COR overrides the barrier code’s COR.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1309 Conference 20 Do not assign fully restricted service to a station with the following features or conditions: nAbbreviated Dialing nBridged Call Appearance nAttendant stations nNight Service stations nStations that are Call Coverage or Send All Calls points nStations that are Call Forward destinations nStations that are Call Pickup points Interactions for miscellaneous terminal and trunk restrictions nAAR/ARS AAR or ARS access to a trunk group overrides miscellaneous trunk restrictions. nAbbreviated Dialing Privileged Group Number List A telephone user with authorization to access an Abbreviated Dialing Privileged Group Number List can place calls to any number on that list. COR assignments are not checked. nPrivileged System Number List A telephone user with authorization to access a Privileged System Number List can place calls to any number on that list. COR assignments are not checked. Conference The Conference button allows multiappearance telephone users to make up to six party conference calls without attendant assistance. This button also allows single-line telephone users to make up to three party conference calls without attendant assistance. Considerations nA single-line telephone can have up to 6 parties on a conference call, if each conferee adds another conferee. For example, one user can add a party, who then adds a third party, and so on. nIf you do not allow trunk-to-trunk connections and a telephone releases from a conference call (where all of the other parties were connected to the conference via trunks), then all parties are disconnected.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1310 Conference 20 nIf an analog single-line set has Call Wait active and creates a conference call, Call Wait is rendered inactive as long as the single-line set is on the call. For example, caller A on an analog set talks to caller B, flashes to talk to caller C, and flashes to conference B and C. Then, if caller D calls caller A, Call Wait is denied. nUsers of DCP, Hybrid, and wireless phones can conference a call on hold. If there is only one call on hold, no active call appearances, and an available call appearance for the conference, a user can initiate the conference process without taking the call out of hold. When the Conference button is pressed, DEFINITY ECS assumes the conference is for the call on hold, and the conference feature works as usual. If there is more than one call on hold, the user must make a call active in order to include it in a conference. If the user presses the Conference button with two or more calls on hold, DEFINITY ECS will ignore the conference attempt since it will not know which call the user wants to conference. If there are calls on hold and an active call, pressing the Conference button will start the conference process for the active call. nYou can allow users to abort a conference operation that is in progress by hanging up the phone. You set this parameter with the Abort Conference on Hang-Up field on the Feature-Related System Parameters screen. When a user hangs up the phone while trying to conference a call, the existing call is placed on hold, and the conference operation is aborted. Interactions nBridged Call Appearance A bridged call appearance can be used to make conference calls. A bridged appearance can bridge onto a conference call only if there were never 6 parties on the conference. nCall Vectoring A call to a VDN can be included as a party in a conference call only after vector processing terminates for that call (for example, after a successful route-to command). nClass of Restriction If the Restriction Override field is set to all, the COR of the party being added is always checked against the COR of the party controlling the add-on, but the new party’s COR is not checked against any other conferee’s CORs.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1311 Restriction — Controlled 20 nTrunk-to-Trunk Transfer When a multifunction telephone (BRI/Digital/Hybrid) dials sufficient digits to route a call, but could route differently if additional digits were dialed, the telephone does not recognize the Conference or Transfer buttons. The user must delay dialing for 3 seconds or dial # to indicate that the call can be routed based on the digits already dialed. The Conference or Transfer buttons are then recognized and the switch completes the call. nVDN in a Coverage Path Calls in an established conference will not cover to a VDN. Once a call covers to a VDN, a conference cannot be established until the call is delivered to an extension and vector processing ends. Related Topics Refer to the ‘‘ Feature-Related System Parameters’’ on page 632 screen for the following conference-related fields: Public Network Trunks on Conference Call Conference Parties With Public Network Trunks Conference Parties Without Public Network Trunks Conference Tone Abort Conference Upon Hang-Up Restriction — Controlled Controlled Restrictions allow a telephone user with console permission to activate or deactivate specific restrictions. Detailed description Use Controlled Restriction to administer the following restrictions: nOutward — The telephone cannot place calls to the public network. nTotal — The telephone cannot place or receive calls. (Allowed calls include calls to a remote-access extension, terminating-trunk transmission tests, and Emergency Access to Attendant calls.) Direct Inward Dialing (DID) calls are routed to the attendant or a recorded announcement. All other calls receive intercept tone.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1312 Restriction — Controlled 20 nTermination — The telephone cannot receive any calls. Incoming calls are routed to the attendant, are redirected via Call Coverage, or receive intercept treatment. nStation-to-Station — The telephone cannot place or receive station-to-station calls. nToll — The telephone cannot place toll calls but can place free local calls. NOTE: Toll Restriction may be substituted for either the outward or station-to-station restrictions. Administer this option on the ‘‘ Feature-Related System Parameters’’ on page 632. To activate Controlled Restriction: 1. Dial the group or extension feature access code. 2. Dial the number for the type of restriction desired: — 1 for outward/toll — 2 for total — 3 for termination — 4 for station-to-station/toll 3. Dial the extension (Attendant Control — Extension) or the Class of Restriction (COR) for a group of telephones (Attendant Control — COR). Interactions nCall Coverage Controlled Restrictions are not checked for covering users. nCall Forwarding Controlled Restrictions for the forwarded-to extension are checked when Call Forwarding All Calls is active. nClass of Restriction All telephones with the same COR are affected by a group restriction. When a call is placed, both individual and group restrictions are checked. nPriority Call If a a station user or a Station-to-Station Restricted user activates priority calling before they dial another station, they receive intercept tone. They receive this tone whether you set Controlled Station to Station Restriction on the Feature-Related System Parameters form to y or to n.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1313 Crisis Alert 20 nUniform Call Distribution Calls dialed through the UDP are not restricted by Outward Restriction. Crisis Alert Crisis Alert notifies designated extensions when an emergency call is made, and indicates the origin of the emergency call. This information allows the attendant or other user to direct emergency-service response to the caller. When a user places an emergency call, the system notifies the designated extensions with audible and visual alerting. Audible alerting sounds like an ambulance siren. Visual alerting consists of flashing of the CRSS-ALER T button lamp and display of the caller name and extension. When crisis alerting is active at the attendant console, the console is in position-busy mode so that no other incoming calls interfere with the emergency call. The console can still originate calls. The attendant must press the POSITION-BUSY button to unbusy the console and then the CRSS-ALER T button to deactivate audible and visual alerting. Multiple emergency calls If an emergency call is made while another crisis alert is still active, the call will be placed in queue. If you have administered the system so that all users must respond, then every user must respond to every call. The calls may not necessarily queue in the order in which they were made. If you have administered the system so that only one user must respond, the first crisis alert remains active at the phone where it was acknowledged. Any subsequent calls are queued to the next available station in the order in which they were made. Alerting a digital pager Crisis Alert to a Digital Pager allows users to receive crisis alert messages on a pager. When a crisis alert call is originated in an emergency situation, a message of 7 to 22 digits is sent to the pager and displays a crisis alert code, an extension or room number, and a main number (if one is entered) so the pagee knows the location from which the emergency call originated. At the same time, an emergency call connects over a CAMA trunk. To receive a crisis alert message, you need to administer at least one attendant or digital set with a CRSS-ALRT button. With the Alert Pager field set to y, any station with a CRSS-ALRT button and a pager receives the correct alert.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1314 Crisis Alert 20 NOTE: The crisis alert call uses 2-4 trunks; 1 trunk for the actual call and 1-3 trunks to notify the pager(s) depending on the number of administered pagers. Information about the alert can be viewed on the history report printed at the journal printer and the emergency log. Considerations nOnly one crss-alert button is allowed per attendant console or digital station. nConsoles without a crss-alert button do not receive emergency notification. nIf a user attempts to make an emergency call, but all trunks are busy, this call will not generate an alert. If Outgoing Trunk Queuing is enabled for a trunk group, the call will queue, but will not generate an alert. Interactions nCentralized Attendant Service If CAS is enabled, the alert still goes to the local attendant. nTenant Partitioning If tenant partitioning is active, attendants only receive emergency notification from callers within their partition. If there is no attendant assigned to a partition from which an emergency call originates, the switch still sends a record of the call to the journal printer. nTerminal Self Administration Those users who have the ability to administer their own phones do not have the ability to disable a crisis alert button.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1315 Dial Plan 20 Dial Plan This is the system’s guide to digit translation. When the system receives dialed digits, it must know what to expect next based on the digits received so far. For example, if a user dials 4, the system must know how many more digits to expect before the call is processed. All feature access codes, extensions and trunk access codes must be consistent with the dial plan. Detailed description The dial plan provides information to the switch on what to do with dialed digits. Tables define the intended use of a code beginning with a specific first digit or pair of digits. These digits tell the system how many digits to collect before processing the full digit string. For example, a digit string beginning with 8 may tell the system to wait for 4 more digits because this is the first digit of a 5-digit internal extension. The choices of a first digit are 0– 9, *, and #. Permissible codes and the allowable number of digits are listed below. You can also administer a Uniform Dial Plan (UDP) as part of the dial plan to be shared among a group of switches. If you establish a UDP, make all extensions the same length (4 or 5 digits). So that calls route to the desired switch, a UDP requires the following information: nA PBX code, which represents the first 1 to 5 digits of a 4-digit or 5-digit extension and can range from 0 to 9xxxx with a maximum of 50,000 PBX codes on G3r or 20,000 PBX codes on G3si/csi. nAn RNX, which is associated with the PBX code and is used to select an AAR pattern for the call. This information is required for each PBX code. The 3-digit RNX can be an AAR location code or, for ENP calls, an ENP code. nA PBX ID (1 to 63), which represents a specific switch (optional). nWhether or not the PBX code is local to this system (optional). Considerations nYou cannot assign prefixed extensions longer than five digits (including prefix) to intercom lists. nA trunk access code (TAC) and an extension can share a first digit only if the extension is shorter than the TAC.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1316 Dial Plan 20 nAlthough extensions with the same first digit can have different lengths, data-channel extensions must have the maximum number of digits to avoid timeout problems for data calls that the switch automatically sets up, for example, the Call Detail Recording (CDR) link. nAn extension and a Feature Access Code (FAC) can share the same first digit only if the extension is longer as long as they are not used for Automatic Alternate Routing/Automatic Route Selection (AAR/ARS) faxes. These extensions work only within the switch; they do not work as remote uniform dialing plan (UDP) extensions. Interactions All dial-access features and services provided by the system require the dial plan. nAttendant Display and Telephone (Voice Terminal) Display Prefixed extensions display without the prefix. The return call button causes the prefix to dial, even though it does not display. nISDN-BRI When an ISDN-BRI station dials sufficient digits to route a call, but the call could route differently if additional digits were dialed, the station does not recognize the Conference or Transfer buttons. The user must delay dialing for 3 seconds or dial # to indicate that the call can be routed based on the digits already dialed. The Conference or Transfer buttons then are recognized and the switch completes the operation. nMF Signaling Flexible numbering is supported in countries using R2-MFC trunk signaling without Group II tones. Different-length extensions can exist as long as the extensions have different first digits. nProperty Management System (PMS) Remove prefixes before messages containing the extension are sent to the PMS. Five-digit extensions do not exchange with PMS until modifications are made to the PMS interface. nUniform Dial Plan The following limitations apply to a distributed communications system (DCS) environment: — Extensions that differ in length from the UDP do not distribute to other switches. — If the first two digits of an extension correspond to the floor number, floors cannot be serviced by more than one switch.