Home
>
Lucent Technologies
>
Communications System
>
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual
Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual
Have a look at the manual Lucent Technologies DEFINITY Enterprise Communications Server Release 8.2 Instructions Manual 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.1 June 2000 Features and technical reference 1557 Tenant Partitioning 20 nEmergency Access to the Attendant When a tenant dials emergency access, it accesses its own assigned attendant group. nExpert Agent Selection (EAS) For agents in an EAS system, the Class of Restriction assigned to the logical agent ID (not the physical extension) determines whether callers on hold can hear music. nHunt groups The tenant number assigned to the hunt group extension determines the music source callers to the hunt group hear while they’re in queue or on hold. nIntercept Treatment When access to the attendant is designated as intercept treatment, the caller accesses their assigned attendant group. nMalicious Call Trace By default, Malicious Call Trace extensions are assigned to tenant partition 1. Therefore, if Malicious Call Trace is enabled, any telephone with permission to call tenant partition 1 can use it. nMultiple Listed Directory Numbers Each Listed Directory Number is assigned to a tenant partition. nMultiple Audio/Music Sources for Vector Delay When an audio source is specified by a wait-time hearing vector step, the audio source assigned to the tenant number of the active VDN is the one that plays. If you use a wait-time hearing then command where the is an audio source (assigned on the Announcements/Audios Sources form), that audio source will play instead of the one associated with the active VDN. For information on administering multiple audio sources see the DEFINITY ECS Call Vectoring/EAS Guide. nMusic-on-Hold Access When Tenant Partitioning is enabled, you can assign a unique source for music to each tenant. If Tenant Partitioning on the System-Parameters Customer-Options form is set to y, you must use the Music Sources form to administer music-on-hold. nNight Service Each tenant can have its own Listed Directory Number (LDN) night destination, Trunk Answer on Any Station (TAAS) port, or night attendant.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1558 Terminal Translation Initialization 20 nPC Interfaces You must assign each PC interface to a tenant partition. nPC/PBX Connections You must assign each PC/PBX Connection to a tenant partition. nPC/ISDN You must assign each PC/ISDN to a tenant partition. nRemote Access You must assign each Remote Access barrier code to a tenant. nTraffic Studies Traffic studies do not report the tenant partition number of the extension or trunk group used. You must infer the tenant partition number must be inferred from the extension or trunk-group number. nUniform Dial Plan If a Uniform Dial Plan is in place between switches, tenant partition identification is not passed between the switches, and so tenant-partition restrictions are not enforced between the switches without special administration. NOTE: Tenant Partitioning restrictions do not override COR restrictions. COR restrictions are independent of tenant partitions. Terminal Translation Initialization Terminal Translation Initialization (TTI) allows you to merge an x-ported extension to a valid port by dialing a system-wide TTI security code and the extension from a telephone connected to that port. TTI also allows you to separate an extension from its port by dialing a similar separate digit sequence. This action causes the extension to be administered as an X port. When TTI is enabled for voice, all voice ports (except Basic Rate Interface (BRI) ports) become TTI ports or ports from which a TTI merge sequence can occur. TTI is usually used to move phones, however, it also supports connecting and moving attendants, data modules, voice/data telephones, and ISDN-BRI telephones.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1559 Terminal Translation Initialization 20 Attendants In order for attendants to use TTI, you must assign an extension to the attendant console. TTI port translations are the same for digital telephones and attendant consoles. To merge a digital TTI voice port and an attendant, you must first administer the attendant as an X port. Then a digital telephone must be plugged into the jack assigned to the attendant console, and the TTI merge digit sequence must be entered on the digital telephone. Once the TTI merge has been completed for the attendant console, the digital telephone must be unplugged and the attendant plugged into the jack. An attendant console can be separated from its port only through administration. A TTI separate request from an attendant console gives the user intercept treatment. Data modules Data modules have different tones and digit sequences. In the merge and separate control flow, different tones are given to the telephone user to give the current status of the TTI operation. Instead of audible tones, status messages are displayed on a telephone connected to a data module when activating the TTI sequence through keyboard dialing. If the TTI State field is set to data, you see the data display messages. If the TTI State field is set to voice, you hear the tones. For a stand alone data module, the TTI merge/separate digit sequence is entered in one line at a dial prompt: nDIAL: Separate prompts are not given for the TTI security code and extension. Voice/data telephones A telephone with a data terminal (DTDM) is treated as a telephone in the TTI merge and separation sequence. The DTDM is merged with and separated from its hardware translation at the same time the telephone is merged or separated. The TTI merge and separate sequence can only be initiated through the telephone for DTDMs; it cannot be initiated through the data port.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1560 Terminal Translation Initialization 20 ISDN BRI telephones The TTI separation sequence for Automatic-TEI SPID-initializing BRI telephones is identical to the sequence used for telephones. However, the merge sequence is different. nSeparation sequence 1. Feature Access Code 2. Security Code 3. Extension nMerge sequence 1. Connect the telephone to any port to get power. 2. Program the SPID to the extension with which it will be merged. 3. Unplug the telephone (this is necessary even if the telephone is connected to its intended port). 4. Connect the telephone to its intended port (this port should indicate Equipment Type: TTI Port). 5. Receive dial tone. — If there is dial tone, the merge is complete. — If there is no dial tone, the telephone’s SPID is not an available extension. You can dial the TTI merge sequence for BRI sets only if a user separates a BRI extension from its set and then wants to undo the process by reassociating the set to the same extension. Note that you cannot use the SAT to put an X in the port field of a BRI set that is still connected to the switch. You must use the TTI separation sequence from the set. Analog Queue Warning Ports and External Alert Ports The analog queue warning port (used for hunt groups) and the external alert port may be administered with an X in the Port field. These extensions can be merged to an analog port via TTI. The merge must be done by an analog set, and then the analog set is unplugged from the port. These extensions cannot be separated from their port location with the TTI feature. A TTI separate request from one of these ports gives you intercept treatment.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1561 Terminal Translation Initialization 20 Security measures !SECURITY ALERT: If you do not manage this feature carefully, its unauthorized use may cause you security problems. For example, someone who knows the TTI security code could disrupt normal business functions by separating telephones or data terminals. You can help protect against this action by frequently changing the TTI security code. You can further enhance system security by removing the Feature Access Code (FAC) from the system when it does not need to be used (for example, there are no moves going on at present). Consult the BCS Systems Security Handbook for additional steps to secure your system and find out about obtaining information regularly about security developments. Interactions n10-MET, 20-MET, 30-MET phones You cannot use TTI to change 10-MET, 20-MET, or 30-MET phones. nAttendant It is possible to have the attendant in Position Available Mode and still separate. Any calls queued, held, or seen as active for the attendant prevent separation. nAttendant Night Service The night service station cannot be separated while in night service. nAttendant Release Loop Operation If the attendant separates before the attendant-timed reminder-interval expires, all calls held with the release loop operation by the attendant are reclassified as attendant group calls. nAutomatic Callback If a telephone has Automatic Callback active for another telephone, executing TTI separate for either telephone breaks the automatic callback sequence. nCall Coverage If a telephone separates while Send All Calls or Goto Coverage is active, these features remain active while the telephone has no associated hardware. You can separate a telephone that is the target of Send All Calls or Goto Coverage; the features function as if the telephone were busy.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1562 Terminal Translation Initialization 20 nCall Coverage Answer Group If a extension was an X port, then rejoins the group as a result of a TTI merge, a PSA associate, or a port assignment, that telephone is excluded from all transactions already active in the call coverage answer group. nCall Forwarding A telephone can separate while Call Forwarding is active. If a destination extension for call forwarding separates, Call Forwarding to that extension remains active. Calls forwarded while the telephone is separated hear a busy signal. nCall Pickup If a line appearance is available, a member of a call pickup group may separate at any time. If a call is attempting to terminate, and a member of a group associates, that member does not join the group for the call that is currently in progress, but is available for all subsequent calls to that group. nExpert Agent Selection Station user records cannot be shared between TTI ports and EAS login ID extensions. This reduces the number of possible TTI ports your system provides, depending on the number of administered EAS login IDs. For example, if you administer 2,000 EAS login IDs, the maximum number of TTI ports that the system can provide is reduced by 2,000. nHunt Group Uniform Call Distribution/Direct Department Calling The system excludes telephones previously X-ported as a result of a TTI separate, a PSA dissociate, or administration from all transactions already active in the hunt group when the telephone is merged. nSite Data If Terminal Translation Initialization is enabled, a warning message displays when you tab off the Site Data fields. If Terminal Translation Initialization is enabled, and you change the Port field on the Station screen from “x” to a real port number and change the Room, Jack, or Cable fields in the Site Data section, a warning message displays when you tab off the fields. nTerminating Extension Group If any member of the TEG (that was previously an X port as a result of TTI, PSA or telephone administration) is merged, that member is excluded from all transactions already taking place in the TEG when that member is merged. The member is able to join in all subsequent calls to the group.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1563 Terminating Extension Group 20 Related topics For more information about configuring the TTI system-wide fields, refer to ‘‘ Feature-Related System Parameters’’ on page 646. For more information about setting the TTI feature access codes, refer to ‘‘ Feature Access Code’’ on page 633. Terminating Extension Group A Terminating Extension Group (TEG) allows an incoming call to ring as many as 4 phones at one time. Any user in the group can answer the call. Detailed description You can administer any phone as a TEG member; however, only a multiappearance phone can be assigned a TEG button with merged-status lamp. The TEG button allows the user to select a TEG call appearance for answering or bridging onto an existing call but not for call origination. When a TEG members answers an incoming call, a temporary bridged appearance is maintained at the multiappearance phones in the group. However, this appearance is not visible. Any TEG members can bridge onto the call by pressing the TEG button. Considerations nA phone user can be a member of more than one TEG, but can have only one TEG button for each group. nA TEG can handle only one TEG call at a time. Additional calls do not reach the TEG. If a coverage path is assigned to the TEG, the additional calls route accordingly. Interactions nAutomatic Callback This feature cannot be active for a TEG. nBridged Call Appearance Calls to a TEG cannot be bridged, except via a Temporary Bridged Appearance.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1564 Terminating Extension Group 20 nCall Coverage A TEG can have a Call Coverage path assigned, but cannot be a point in a Call Coverage path. A Send Term button for the TEG can be assigned to group members who have multiappearance phones. When a user presses Send Term, calls to the TEG redirect to coverage. The merged status lamp lights on all phones with a Send Term button. Any member with a Send Term button can deactivate Send Term by pressing the button. Incoming calls are directed to the group. nCall Park A TEG call cannot be parked on the group extension. However, a group member answering a call can park a TEG call on their own extension. nDirect Department Calling and Uniform Call Distribution A TEG cannot be a member of a DDC or UCD group. nInternal Automatic Answer TEG calls are not eligible for Internal Automatic Answer; however, calls placed to an individual extension are eligible. nLeave Word Calling Leave Word Calling messages can be stored for a TEG and can be retrieved by a member of the group, a covering user of the group, or a system-wide message retriever. Phone Display and proper authorization can be assigned to the message retriever. Also, a remote Automatic Message Waiting lamp can be assigned to a group member to provide a visual indication that a message has been stored for the group. One indicator is allowed per TEG. nPrivacy — Manual Exclusion Privacy — Manual Exclusion can be assigned to any of the phones in a TEG to prohibit bridging by other group members. A TEG member who attempts to bridge onto a call with Privacy — Manual Exclusion active is dropped. nTemporary Bridged Appearance At multiappearance phones in the TEG, a temporary bridged appearance is maintained after a call is answered. Thus, other members of the group can bridge onto the call. Related topics Refer to ‘‘ Terminating Extension Group’’ on page 971 for information about and fields descriptions on the Terminating Extension Group screen. Refer to ‘‘ Station’’ on page 894 for information on button assignments. Refer to ‘‘ Assigning a terminating extension group’’ on page 183 for instructions.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1565 Time of Day Routing 20 Time of Day Routing You can use Time of Day Routing to select route patterns for calls according to the time of day and day of the week. You need to define the route pattern you want to use before you set up time of day routing. You can route calls based on the least expensive route, and you can deny outgoing long-distance calls after business hours to help prevent toll fraud. You can use partition groups to assign different time of day route plans for different groups of users. Automatic Alternate Routing (AAR) or Automatic Route Selection (ARS) must be administered on your switch before you use Time of Day Routing. Time of Day Routing applies to all AAR or ARS outgoing calls and trunks used for call forwarding to external numbers. Interactions nDCS Be careful when you make Time of Day Routing assignments in a DCS environment. The user’s COR Time of Day Plan Number determines whether or not the call is routed to a DCS trunk group. The call loses feature transparency if it is not routed to a DCS trunk group. When a call routes over a DCS trunk, the switch at the far end routes the call according to the COR Time of Day Plan Number of the incoming trunk. nRemote Access When remote access is used and an authorization code or barrier code is dialed for an AAR or ARS call, the COR Time of Day Plan Number of the barrier code or authorization code is used to route the call. Related topics nRefer to ‘‘Setting up time of day routing’’ on page 207 for information on setting up Time of Day routing. nRefer to ‘‘Defining ARS Partitions’’ on page 204 if you want to set up different Time of Day routing for different partition groups. nRefer to ‘‘Automatic routing — general’’ on page 1178 for information on AAR and ARS
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1.1 June 2000 Features and technical reference 1566 Transfer 20 Transfer Transfer allows telephone users to transfer trunk or internal calls to other telephones or trunks without attendant assistance. Considerations nYou can administer transferred-trunk calls to receive either music or silence if the first part of the transfer places the call on hold. nMulti-appearance telephones must have an idle appearance to transfer a call. nSingle-line telephone users momentarily flash the switchhook or press the RECALL button, dial the desired extension, and hang up. Multi-appearance telephone users press the TRANSFER button, dial the desired extension, and press the TRANSFER button again. nIf, on the Feature-Related System Parameters screen, the Transfer Upon Hang-up field is y, users can transfer a call by pressing the TRANSFER button, dialing the desired extension, and then hanging up. The user can hang up while the desired extension is ringing or after the party has picked up. The user also can still press the TRANSFER button a second time to complete the transfer process. nIf, on the Feature-Related System Parameters screen, the Abort Transfer field is y, users can abort the transfer a call by pressing the TRANSFER button, dialing the desired extension, and then hanging up or selecting any non-idle call appearance. The user must press the Transfer button again to complete the process (see Note). If the user selects an idle call appearance, the transfer still is active. NOTE: If both the Abort Transfer and Transfer Upon Hang-Up fields are y and you press the TRANSFER button and then dial the complete transfer-to number, hanging up the phone transfers the call. nUsers of DCP, Hybrid, and wireless phones can transfer a call on hold without removing the call from hold. If there is only one call on hold, no active call appearances, and an available call appearance for the transfer, the user can transfer the call simply by pressing the Transfer button. DEFINITY ECS assumes the transfer is for the call on hold, and the transfer feature works as usual.