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 1447 Night Service 20 Considerations Considerations for Hunt Group Night Service nBoth Hunt Group Night Service and Trunk Group Night Service can be active at the same time. An incoming trunk call is redirected to the trunk group’s designated NSE. If this NSE is a hunt group or split that is in Hunt Group Night Service mode, the call is redirected to the Hunt Group NSE. nCalls in progress (such as talking, on hold, or waiting in queue) on the hunt group or split are not affected when the hunt group or split is put in Hunt Group Night Service mode. nWhen a hunt-group queue becomes empty, all idle members are placed in a busy condition. nIf Night Service is activated for a hunt group or split and a power failure occurs, the hunt group or split automatically returns to the Night Service mode. Considerations for Night Console Service nThe night console must be identical to and have the same features as the primary console. A daytime console can double as the night console. nNight Console Service calls to the attendant group are still handled by an attendant, even though the primary and daytime attendant consoles are out of service. nOnly one night console is allowed in the system. The night console can be activated only when the primary and daytime consoles have been deactivated. nIf Night Console Service is active and a power failure occurs, the system automatically returns to Night Console Service mode when it is powered up. Considerations for Night Station Service nWhen Night Station Service is active but you have not established Night Station extensions, a user can activate Trunk Answer from Any Station (TAAS). nYou can assign a Night-Serv button to either an attendant extension or a phone extension. An individual trunk group or hunt group can be put into night service by either an attendant extension or a phone extension with the necessary button. When a user presses this button to activate Night Station Service, all calls to that particular trunk group or hunt group are routed to the Night Service extension assigned to that group.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1448 Night Service 20 nIf a trunk without disconnect supervision goes to Night Service, the system drops the trunk after a period of time to avoid locking up the trunk. The call is not routed to the DID-LDN night extension. Considerations for TAAS nIf Night Service is active and a power failure occurs, the system, when brought back up, automatically returns to Night Service mode. Considerations for Trunk Group Night Service nAll incoming calls on Night Service trunk groups go to the trunk group’s NSE unless the trunk group member has its own Trunk Group Member Night Destination, in which case the calls are redirected to that destination instead of the trunk group’s NSE. nCalls already in progress on a trunk group (such as talking, on hold, or waiting in queue), are not affected when the individual Trunk Group Night Service or System Night Service is activated. nTrunk Group Night Service and System Night Service work independently of one another. — When a user activates System Night Service, any trunks that are controlled by individual Trunk Group Night Service buttons remain in day service. Trunk groups that are not currently assigned to Trunk Group Night Service are assigned to System Night Service. — Trunks with individual Trunk Group Night Service can be removed from Night Service even though the rest of the system remains in Night Service. — When a user deactivates System Night Service, any trunks that have individual Trunk Group Night Service still active remain in night service. — Trunks with individual Trunk Group Night Service can be placed into Night Service even though the rest of the system remains in day service. nIf a trunk is added to a trunk group while that trunk group is in Trunk Group Night Service, the trunk is brought up in night service. nIndividual Trunk Group Night Service does not apply to DID trunk groups. nIf Night Service is activated for a trunk group, and a power failure occurs, the trunk group automatically returns to the Night Service mode. nIf for some reason, a phone with a trunk-ns button remains out-of-service after a system reboot and later comes back in service, the trunk-ns lamp shows the trunk status within 10 seconds of coming back in service. For
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1449 Night Service 20 example, a phone with a trunk-ns button may be unplugged when the system is rebooted. If the phone is plugged back in later, the trunk status is shown on the trunk-ns button within 10 seconds. Interactions Interactions for Hunt Group Night Service nACD When Hunt Group Night Service is active for a split and the night-service destination is a hunt group, the caller hears the first forced announcement for the original split. The system then redirects the call to the Night Service destination hunt group. When an agent in the Night Service hunt group becomes available, the call goes to that agent. If all agents in the hunt group are busy, the caller hears the following: forced or delayed first announcement, ringback, music-on-hold or silence, and a second announcement. nCall Coverage Coverage takes precedence over Night Service. When Hunt Group Night Service is active, the NSE’s normal coverage criteria and path apply. If the coverage path destination is AUDIX, AUDIX answers with the mail of the original hunt group. If the NSE is a hunt group or split of any type, the hunt group or split’s call coverage criteria and coverage path apply. The coverage criteria and path can be different from that assigned to the phones that are members of that hunt group or split. If a coverage point is a hunt group or split in Night Service, the system considers the point to be unavailable and does not forward the call to the coverage point’s NSE. nCall Forwarding All Calls If a hunt group or split is in Hunt Group Night Service mode and the hunt group or split’s NSE has Call Forwarding — All Calls active, the system forwards night-service calls terminating to that NSE to its designated call-forward extension. If the forwarded-to destination is a hunt group or split in Night Service mode, the system terminates the call at the forwarding extension. Interactions for Night Console Service nTrunk Group Night Service Activation of Night Console Service for the attendant consoles also puts trunk groups into night service, except those trunk groups for which you administered a Trunk Group Night Service button.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1450 Night Service 20 Interactions for Night Station Service nCall Coverage Calls routed to the night extension via Night Station Service follow the coverage path of the night extension under all coverage criteria except Send All Calls. If a night extension has a coverage path in which Cover All Calls is administered, all attendant-seeking calls redirect to coverage. Changes to the protocol for handling DID-LDN calls (that is, forwarding attendant-seeking calls on or off premise from the night extension) do not work. nCall Forwarding All Calls Calls redirected to the attendant via Call Forwarding All Calls do not route to the DID-LDN extension. nInward Restriction Inward-restricted phones can be administered for Night Station Service. Night Service features override Inward Restriction. nNight Console Service Do not provide Night Console Service with this Night Station Service. nRemote Access A Remote Access extension can be specified as the Night Station extension on an incoming, non-DID, trunk group. nTenant Partitioning Each tenant may have a designated night-service station. The system directs calls to an attendant group in night service to the night-service station of the appropriate tenant (when a night attendant is not available). When someone places an attendant group into night service, all trunk groups and hunt groups that belong to tenants served by that attendant group go into night service. In this case, the system routes incoming calls to the night-service destination of the appropriate tenant. Each tenant can have its own listed directory number (LDN) night destination, trunk answer on any station (TAAS) port, or night attendant. nTimed Reminder Timed Reminder calls returning to a console that has been placed in Night Service and has an assigned DID-LDN night extension are not redirected to the DID-LDN night extension. Rather, they are dropped. nTrunk Answer from Any Station TAAS and Night Station Service can both be assigned within the same system, but cannot be assigned to the same trunk group.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1451 Night Service 20 Interactions for TAAS nCall Coverage If Night Station Service is active, calls that are redirected to the attendant via Call Coverage can be answered via TAAS. nCall Forwarding All Calls If Night Station Service is active, calls that are redirected to the attendant via Call Forwarding All Calls can be answered via TAAS. nInward Restriction Inward-restricted phones can activate TAAS for incoming trunk calls. Night Service features override Inward Restriction. nNight Console Service Do not provide a Night Console Service with TAAS. nNight Station Service TAAS and Night Station Service can both be assigned within the same system, but cannot be assigned to the same trunk group. Activating Night Station Service also activates Night Service — Trunk Group for any trunk group without an individual trunk-group Night Service button. nTenant Partitioning Each tenant can have its own listed directory number (LDN) night destination, trunk answer on any station (TAAS) port, or night attendant. Interactions for Trunk Group Night Service nCall Forwarding All Calls If the individual Trunk Group Night Service mode and the trunk group’s NSE have Call Forwarding All Calls activated, the night service calls terminating to that NSE are forwarded to the designated extension. nForced First Announcements An interaction occurs with System Night Service and Forced First Announcement. For example, if hunt group A has a forced first announcement, assign the incoming CO trunk to terminate at hunt group A. Assign the incoming trunk’s night-service destination to be another hunt group (hunt group B). Assign a Night Service button to the attendant. With night service active on the attendant, the incoming CO call routes to the night-service destination hunt group B and does not play the Forced First Announcement of the incoming destination’s hunt group A.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1452 Night Service 20 nListed Directory Number In System Night Service mode, all incoming LDN calls (except those using DID trunks) which have activated night service are redirected to their corresponding trunk group’s NSE. Incoming LDN calls using DID trunks are directed to the Night Console Service, Night Station Service, or Trunk Answer From Any Station, respectively, whichever applies first. Non-LDN DID trunk calls terminate at the dialed extension. Related topics For Hunt Group Night Service Refer to ‘‘ Attendant Console’’ on page 484 for administering feature button assignments on an attendant console. Refer to ‘‘ Hunt Group’’ on page 696 for information on assigning the destination for calls when in a night service mode. Refer to ‘‘ Station’’ on page 882 for administering feature button assignments on stations. Refer to ‘‘ Setting up night service for hunt groups’’ on page 145 for instructions. For Night Console Service Refer to ‘‘ Attendant Console’’ on page 484 for information for administering feature button assignments on the attendant console. Refer to ‘‘ Setting up night console service’’ on page 136 for instructions. For Night Station Service Refer to ‘‘ Trunk Group’’ on page 967 for information on assigning an extension number to night service. Refer to ‘‘ Listed Directory Numbers’’ on page 800 for information on assigning an extension number to night service. Refer to ‘‘ Attendant Console’’ on page 484 for information on administering feature button assignments on an attendant console. Refer to ‘‘ Hunt Group’’ on page 696 for information on night service destination. Refer to ‘‘ Station’’ on page 882 for administering feature button assignments on stations.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1453 Off-Premises Station 20 Refer to ‘‘Setting up night station service’’ on page 137 for instructions. For Trunk Group Night Service Refer to ‘‘ Listed Directory Numbers’’ on page 800 for night service destination. Refer to ‘‘ Attendant Console’’ on page 484 for administering feature button assignments on an attendant console. Refer to ‘‘ Station’’ on page 882 for administering feature button assignments on stations. Refer to ‘‘ Setting up trunk group night service’’ on page 144 for instructions. For Trunk Answer from Any Station Refer to ‘‘ Trunk Group’’ on page 967 for assignment of a blank extension number to night service. Refer to ‘‘ Feature Access Code’’ on page 619 for information on assigning a TAAS feature access code. Refer to ‘‘ Console Parameters’’ on page 540 for information on assigning an external alerting device. Refer to ‘‘ Setting up trunk answer from any station’’ on page 139 for instructions. Off-Premises Station Off-Premises Station allows a phone located outside the building where the switch is located to be connected to the system. If central office (CO) trunk circuits are used, the voice terminal must be analog and must be FCC-registered or, outside the US, registered by the appropriate governmental agency. Digital communications protocol (DCP) sets can be used as off-premises terminals with the addition of the DEFINITY extender. Off-premises stations are useful when it is necessary to have a voice terminal located away from the main location. The maximum loop distance for off-premises stations is 20,000 feet (6093.34 meters) without repeaters. For cabling distance information for the various voice terminal types, refer to the DEFINITY ECS System Description.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1454 PC Interface 20 Detailed description Off-Premises Station requires cross-connecting capabilities and one port on a Analog Line or DS1 Tie Trunk circuit pack for each interface to be provided. Not all analog lines can support an off-premises station. For information about analog lines, refer to the DEFINITY ECS System Description. NOTE: The use of a message waiting indicator lamp on an off-premises station is not supported. Interactions The Distinctive Ringing feature might function improperly at an off-premises station due to the distance. However, the Distinctive Ringing feature can be disabled when the Off-Premises Station field is administered. If the Distinctive Ringing feature is not used with an off-premises station, the terminal receives 1-burst ringing for all calls. Related topics Refer to ‘‘ Installing home equipment’’ on page 295 for information about setting up your off-premises station. Refer to ‘‘ Configuring DEFINITY ECS for telecommuting’’ on page 285 for information about setting up telecommuting. Refer to ‘‘ Station’’ on page 882 for information about and field descriptions on the Station screen. PC Interface The personal computer (PC) Interface consists of the PC/ISDN Platform product family. These products are used with DEFINITY ECS to provide users of IBM-compatible PCs fully-integrated voice and data workstation capabilities. Detailed description Two groups of different configurations are available for PC Interface: group 1 uses Digital Communications Protocol (DCP) and group 2 uses the ISDN-BRI (Basic Rate Interface) protocol.
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1455 PC Interface 20 The group 1 configurations consist of DCP configurations that use a PC/PBX Interface card (formerly DCP expansion card) in the PC to link to the switch. Group 1 (shown in Figure 57 ) uses the following connections: nThe PC Interface card plugs into an expansion slot on the PC. The card has 2 standard 8-pin modular jacks (line and phone). nThe digital phone plugs into the phone jack on the PC Interface card. nThe line jack on the card provides a digital port connection to DEFINITY ECS. nThe distance between the PC Interface card and the PBX should be no more than 1524m for 24-gauge wire or 1219m for 26-gauge wire. Figure 57. DCP PC interface configuration (Group 1) The group 2 configurations link to the switch using a PC/ISDN Interface card installed in the PC. This group can include a stand-alone PC terminal, or up to 4 phones, handsets, or headsets. Group 2 (shown in Figure 58 ) uses PC/ISDN Interface cards (up to four cards) which plug into expansion slots on the PC. These Figure Notes 1. IBM-compatible PC with DCP Interface card 2. IBM-compatible PC with DCP Interface card 3. DCP4. DCP phone 5. DEFINITY ECS (Digital Line circuit pack) 6. Host
DEFINITY ECS Release 8.2 Administrator’s Guide 555-233-506 Issue 1 April 2000 Features and technical reference 1456 PC Interface 20 cards each provide 2 standard 8-pin modular-jack connections for both line connections (to the switch) and phone connections. A standard 4-pin modular jack is also available for use with a handset or headset. Figure 58. ISDN—BRI PC interface configuration (Group 2) PC Interface users have multiple appearances (depending on the software application used) for their assigned extension. Designate one or more of these appearances for use with data calls. With the ISDN-BRI version, you can use up to 4 separate PC/ISDN Interface cards on the same PC. Assign each card a separate extension, and assign each extension one or more appearances. The availability of Figure Notes 1. ISDN phone 2. PC with application 3. Handset or Headset 4. BRI Interface card 5. 2B + D 6. ISDN-BRI Line, 4-wire S/T-NT, interface circuit pack7. DEFINITY ECS 8. PRI trunks 9. BRI stations 10. Interworking 11. DMI 12. Switch features