MERLIN LEGEND® Communications System Release 6.
Copyright © 1998, Lucent TechnologiesDocument 555-661-150 All Rights ReservedComcode 108289703 Printed in USAAugust 1998 Notice Every effort was made to ensure that the information in this book was complete and accurate at the time of printing. However, information is subject to change. See Appendix A, “Customer Support Information,” for important information.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Contents Page iii Contents New Features and Enhancements ■ Release 6.1 Enhancements (August 1998) Prior Releases: Features and Enhancements ■ 1 Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 New Features and Enhancements Release 6.1 Enhancements (August 1998) Page xv New Features and Enhancements Release 6.1 Enhancements (August 1998) 0 Release 6.1 includes all Release 6.0 functionality, plus the enhancements listed below. Private Networking 0 Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 New Features and Enhancements Release 6.1 Enhancements (August 1998) Centralized Voice Messaging Page xvi 0 One or more MERLIN LEGEND systems (Release 6.1 or later) can share the voice messaging system (VMS) of another MERLIN LEGEND system, provided the systems are directly connected to the system with the VMS. In this configuration, the system containing the VMS is known as the hub.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 New Features and Enhancements Release 6.1 Enhancements (August 1998) Page xvii ■ Calling group overflow coverage. Calling group overflow coverage can be provided by a centralized VMS, a non-local calling group, a QCC queue, a DLC, or any individual extension on the remote system. ■ Calls directed to another system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 New Features and Enhancements Release 6.1 Enhancements (August 1998) PRI Switch Type Test Page xviii 0 A new maintenance test, the PRI Switch Type Test, has been created to allow Lucent Technologies technicians or authorized dealers to automatically determine if each end of the PRI tandem trunks has been programmed correctly.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Page xix Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) 0 Release 6.0 includes all Release 5.0 functionality, plus the enhancements listed below.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Issue 1 August 1998 Page xx associates with routes, Facility Restriction Levels (FRLs), digit absorption, and digit prepending. This allows ARS-like routing of non-local dial plan calls.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) ■ Page xxi Voice Mail and Auto Attendant. Networked systems should have their own local voice mail and/or auto attendant applications as well as their own external alerts and Music On Hold sources. However, a single auto attendant can transfer calls throughout the network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Prompt-Based Overflow Page xxii 0 System managers can activate the Prompt-Based Overflow option.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Page xxiii Pause cannot be originated from a single-line telephone or a remote access user. A multiline telephone user in the local system must enter an authorization code to activate the feature. A remote access user may activate the feature without using an authorization code. Barrier code requirements do apply, however.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Prior Releases: Features and Enhancements Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 IMPORTANT SAFETY INSTRUCTIONS Page xxv IMPORTANT SAFETY INSTRUCTIONS The exclamation point in an equilateral triangle is intended to alert the user to the presence of important operating and maintenance (servicing) instructions in the literature accompanying the product.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 IMPORTANT SAFETY INSTRUCTIONS Page xxvi ■ The MERLIN LEGEND Communications System requires a supplementary ground. ■ Do not attach the power supply cord to building surfaces. Do not allow anything to rest on the power cord. Do not locate this product where the cord will be abused by persons walking on it. ■ Slots and openings in the module housings are provided for ventilation.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 About This Book Intended Audience Page xxvii About This Book The MERLIN LEGEND Communications System is an advanced digital switching system that integrates voice and data communications features. This guide provides information about the networking capabilities of MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 About This Book How to Use This Book How to Use This Book Page xxviii 0 This guide includes five chapters: ■ Chapter 1, Introduction. This chapter provides a grounding in the basic terminology and concepts that you must understand in order to manage a networked system. ■ Chapter 2, Call-Handling Scenarios.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 About This Book Terms and Conventions Used Page xxix to refer to facilities in general. Specifically, we refer to digital facilities. We also use specific terms such as personal line, ground-start trunk, DID trunk, and so on. When you talk to your local telephone company central office, ask about the terms they use for the specific facilities they connect to your system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 About This Book Security Page xxx 0 Security Certain features of the system can be protected by passwords to prevent unauthorized users from abusing the system. You should assign passwords wherever you can and limit knowledge of such passwords to three or fewer people. Nondisplaying authorization codes and marked System Speed Dial numbers provide another layer of security.
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 About This Book How to Comment on This Book How to Comment on This Book Page xxxii 0 We welcome your comments, both positive and negative. Please use the feedback form on the next page to let us know how we can continue to serve you.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Page 1-1 Introduction 1 This chapter describes the terminology and concepts that you should understand before you plan and maintain a networked system. It includes the following topics: ■ Networking Concepts. In simple terms, explains what private communications networks are, the benefits they offer organizations, and fundamental concepts such as tandem switching and tandem trunking.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Networking Concepts Networking Concepts Page 1-2 1 In today’s environment—business, academic, and governmental—many organizations are setting up multiple sites to provide customers and clients with better access to products and services.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Networking Concepts Issue 1 August 1998 Page 1-3 Communications systems are linked by special facilities called tandem trunks. These lines/trunks may be analog tandem tie trunks, T1-emulated tie trunks, or tandem Primary Rate Interface (PRI) trunks. As a group, they can be referred to as private network trunks, because they enable private networks.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Networking Concepts Page 1-4 Benefits of Networking 1 Available for Hybrid/PBX mode systems, the private network features of the MERLIN LEGEND Communications System Release 6.0 and later provide the following advantages for geographically dispersed organizational sites: ■ Toll Savings.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Networking Concepts ■ Issue 1 August 1998 Page 1-5 Improved Efficiency. In Release 6.1 and later systems, you can save on resource costs, enhance customer service, and improve productivity in the following ways: — Coverage and overflow calls can be sent to a remote system using calling groups, increasing the number of coverage points and allowing sharing of personnel and resources between systems.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Issue 1 August 1998 Page 1-6 Tandem Trunking and Tandem Switching1 The term tandem switching describes the process of routing an incoming call over an outgoing tandem trunk or PSTN facility. If the outgoing trunk is a tandem trunk, it connects to another system in a private network. When the call terminates at an extension on a non-local system, it is an intersystem call.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-7 Public Switched Telephone Network (PSTN) PRI ML A ML B Chicago, IL New York, NY Ext. 4321 Figure 1–1. PRI ML C Tie Santa Monica, CA Los Angeles, CA Ext. 5455 ML D Ext. 3699 Ext. 6233 Series Configuration To make a call from System A to System C, a user at Extension 4321 dials 3699 to reach Extension 3699.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-8 In the next sections, we will look at this and other private network configurations and examine more carefully the tandem trunks that link systems in private networks. Network Configurations 1 This topic looks at some sample private network configurations and the differences among them.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-9 In this example, system users make calls in the same way as they would in a series configuration. The primary difference between a star configuration and a series configuration is that in a star configuration all network-routed calls pass through a central hub system, in this case, a DEFINITY ECS or DEFINITY ProLogix Solutions system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-10 about private network configurations. In the next topic, we will revisit all three of these configuration diagrams. Lines and Trunks 1 The types of tandem trunks that connect systems in a private network, as well as the types of facilities that connect systems to the PSTN affect the performance and available features in a private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Table 1–1. Page 1-11 Tandem PRI Trunks versus Tandem Tie Trunks Feature Intersystem calling PRI ✔ Tie ✔ Differences PRI provides faster call setup. For intersystem calls, the caller’s extension label and extension number can be displayed at recipient’s MLX (and some DEFINITY) display telephones across the network.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Touch Tone Receivers Issue 1 August 1998 Page 1-12 None ✔ Required for all calls routed across the private network on tie trunks. (Voice messaging increases traffic in both directions.) Not required on PRI trunks.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-13 NOTE: In the following example, the PRI tandem trunks are implemented on T1 circuits provisioned for bipolar 8 zero substitution (B8ZS) line code. P S T N P R I / 2 4 P R I / 2 4 M L A N Y 4 8 lin In te r s a n d o u p to 2 B d a Figure 1–4.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-14 ■ In this configuration, System B uses more of its 80-line capacity for private network trunks than do Systems A, C, and D. ■ A centralized VMS/AA is installed on System B. Voice mail and automated attendant services can be used by extensions and calling groups on Systems A, B, and C.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Issue 1 August 1998 Page 1-15 In Figure 1–5, the 3-system star configuration that we saw earlier has been modified to bring out some additional possibilities for private network configurations. Consider the following points as you review this graphic: ■ All three systems are Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-16 PSTN PSTN ML A ML C PRI PRI DEF E PRI ML B PSTN Figure 1–6. PRI ML D PSTN Star Configuration: Five Systems Figure 1–6 again shows the star configuration we looked at earlier in this chapter.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-17 Software Defined Network (SDN) Configuration 1 Support for AT&T’s Software Defined Network (SDN) was first offered with MERLIN LEGEND in Release 2.0. Release 4.2 introduced support for VNET, MCI’s version of SDN. NOTE: Sprint offers VPN Premiere; this virtual network is not supported by MERLIN LEGEND. With Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Tandem Trunking and Tandem Switching Page 1-18 Figure 1–7 shows three MERLIN LEGEND systems in an SDN network. On System A, the SDN trunks are assigned to pool 71. A user on System A calling the user on System B dials 4013, the last four digits of the SDN number 957-4013. System A routes the call using trunk pool 71 and prepends the digits 957.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Uniform Dial Plan Page 1-20 plan has two sets of extension ranges, both of which include routing information that directs the call to the same private network trunk. This tandem PRI trunk connects the New Jersey system to the Illinois system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Centralized Voice Messaging System Page 1-21 In the next chapter, we look at planning and setting up dial plans across a private network, as well as the use of routing and other system management features. Centralized Voice Messaging System 1 In Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Centralized Voice Messaging System ■ Page 1-22 Only the following voice messaging systems are supported for centralized VMS/AA: ■ MERLIN LEGEND Mail ■ Messaging 2000 ■ Intuity AUDIX ■ IS-III AUDIX Voice Power (no longer orderable) ■ A Uniform Dial Plan (UDP) must be established for the private network. ■ All trunks within the private network should have unique trunk numbers.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Centralized Voice Messaging System Page 1-23 ■ When a user receives and outside call and the call goes to coverage by a centralized VMS/AA using either tie or PRI tandem trunks, the call information signals sent to the centralized VMS/AA indicate an outside call.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Centralized Voice Messaging System Page 1-24 For information about centralized voice message programming, please see: “Centralized Voice Messaging Programming” in Chapter 5. For information about centralized automated attendant programming, please see: “Centralized Automated Attendant Programming” in Chapter 5. Example 1 For the purposes of this example, refer to Figure 1–9.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Centralized Voice Messaging System Issue 1 August 1998 Page 1-25 NOTE: It is recommended that PRI lines, rather than tie lines, be used between MERLIN LEGEND Communications systems in a private network that utilizes the Centralized Voice Mail feature. Refer to Table 1–1, page 1-11 for advantages of PRI lines.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 1 Introduction Centralized Voice Messaging System Page 1-26 Networking Voice Messaging Systems 1 DEFINITY ECS and DEFINITY Prologix systems cannot share a MERLIN LEGEND system centralized VMS/AA, and MERLIN LEGEND systems cannot share a DEFINITY system VMS/AA. Networking voice messaging systems is an alternative that provides the appearance to users that everyone is sharing a single VMS.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Page 2-1 Call-Handling Scenarios 2 This chapter helps you plan and understand private network configurations. It includes the following two main topics: ■ Networking Guidelines. This section describes the factors that you must consider when planning a private network or managing one or more systems in an existing private network. ■ Network Configuration Scenarios.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Networking Guidelines Page 2-2 2 This topic outlines general planning and setup considerations for networked systems, providing the information that you need in order to understand the sample private network scenarios presented in the next section of this chapter.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Issue 1 August 1998 Page 2-3 When setting up your private network for intersystem calling, keep the following important points in mind: ■ You cannot program the local ARS access code or pool dial-out codes into non-local dial plan extension ranges; the system blocks this programming. Non-local extension range numbers cannot begin with the local ARS access code.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Issue 1 August 1998 Call-Handling Scenarios Networking Guidelines Page 2-4 MERLIN LEGEND Communications System extension in a private network. Although the MERLIN LEGEND Communications System can be programmed to drop digit(s), it is recommended that in networks with DEFINITY ECS or DEFINITY ProLogix Solutions use 4-digit dial plans. The next topic provides additional details.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Issue 1 August 1998 Page 2-5 — No more than three (3) analog spans should be involved in any call or volume levels may not be adequate. Multiple spans may be the result of transfers and coverage. If more than three spans may be involved in call completion, digital rather than analog spans should be used.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Non-Local DEFINITY ECS or DEFINITY ProLogix Solutions Systems Page 2-6 2 DEFINITY ECS and DEFINITY ProLogix Solutions communications systems can support either 4- or 5-digit dial plans. However, 5-digit extension ranges cannot be programmed into a MERLIN LEGEND Communications System non-local dial plan.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Page 2-7 must be prepended. Furthermore, users on your system dial only four digits to reach remote extensions while DEFINITY ECS or DEFINITY ProLogix Solutions users dial five digits for intercom calls within their local systems, so extension numbering is not consistent across the private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Page 2-8 The following general rules make ARS routing both simpler and safer: ■ Common Access Code. For proper handling of calls across the private network, all systems in the private network should use the same ARS access code.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Issue 1 August 1998 Page 2-9 SYS PROGRAM➙LINES/TRUNK➙REMOTE ACCESS➙NONTIE/TIELINES➙ RESTRICTIONS When programming the default COR, change the Calling Restriction option to unrestricted (the factory setting is outward restricted). You should assign Disallowed List 7 to include; 900, 976, and other types of calls that users should not be allowed to call.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Programming Regular Remote Access Page 2-10 2 For explicit remote access use by local system users (or by non-local users for special maintenance purposes, for example), assign PSTN trunks to remote access as you normally would, or use PRI dial-plan routed or DID trunks. Specify that users must enter barrier codes for remote access.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Issue 1 August 1998 Page 2-11 far (over 200 miles) connections and between 21 and 40 for near (under 200 miles) connections. DEFINITY ECS and DEFINITY ProLogix Solutions systems are identified by numbers between 41 and 50 for far connections and between 51 and 60 for near connections.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines Page 2-12 2 Security This topic summarizes security issues that are discussed in more detail in Chapter 4, “Security.” Some security issues have been mentioned in the previous topics, including the reasons that ARS codes are not included in the non-local dial plan.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Networking Guidelines ■ Issue 1 August 1998 Page 2-13 UDP routing applies FRLs to calls over specific routes for pools of tandem trunks. A different set of FRLs is programmed for ARS routes. However, an extension’s FRL applies to both UDP routes and ARS routes.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Page 2-14 on a tandem trunk and routed to a Remote Access code. Because the COR Calling Restriction must be set to unrestricted for private network calling, using barrier codes on these facilities is essential in order to apply security measures.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-15 organizational needs and overall feature planning. This scenario also illustrates the way systems work when they are connected by tandem tie trunks only. ■ Scenario 3: Four Systems in a Series, Tandem PRI Facilities, page 57. In this scenario, there is no hub system. Instead the systems are connected in a linear fashion.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 PRI MOH GS DID ML A New York, NY VMI Conversion Number: 7999 ————— Ext.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-18 Tandem PRI trunks provide the following benefits: ■ Faster General Performance. PRI facilities make faster connections across private networks for ARS calling over tandem trunks as well as faster intersystem call handling. ■ Faster Data Transmission.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios ■ Issue 1 August 1998 Page 2-19 Faster Message Waiting Light Updates. For centralized VMS/AA systems in Release 6.1 and later, PRI tandem trunks allow Message Waiting light updates to be sent over the signalling D-channel. With tie tandem trunks, Message Waiting light updates compete with other voice and data traffic for available trunks and touch tone receivers.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Non-Local Dial Plans and Facilities Planning Page 2-20 2 This section shows how non-local dial plans, calling groups, switch identifiers, UDP routing, ARS routing, and remote access are set up for each system. Not all details are provided for all facilities and extensions.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios ■ Issue 1 August 1998 Page 2-21 If a call should be routed over a non-local system for toll-saving purposes, the local ARS routing directs it to a tandem PRI trunk pool, prepending the ARS access code. Local PSTN pools are only used as a fallback option, and more restrictive, higher-numbered FRLs are assigned to these ARS routes.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Issue 1 August 1998 Call-Handling Scenarios Network Configuration Scenarios Table 2–1.
MERLIN LEGEND Communications System Release 6.
Component System A: New York, NY (Area Code: 212) System B: Holmdel, NJ (Area Code: 732) DS1 Switch Type MERLIN LEGEND-PBX MERLIN LEGEND-Ntwk ARS Access Code 9 9 Switch Identifiers Programmed on This System 22 for a system that is within 200 miles (System B) 21 for a system that is within 200 miles (System A) Remote Access Remote Access code: 889 Code and COR for All non-tie ARS Calls Routed Outward Unrestricted Via This System Barrier Code Required (ignored for UDP extension and non-local ARS c
System A: New York, NY (Area Code: 212) Dialed or Rec’d Digits Rte Pool Type System B: Holmdel, NJ (Area Code: 732) Abs Prep Dialed or Rec’d FRL Digits 1 Tandem 0 9 0 2 Local PSTN 0 0 1 All Local PSTN 4 0 0 1 Tandem 0 9 1 2 Local PSTN 0 0 2 All Local PSTN 0 0 2 Rte Pool Type Abs Prep FRL 1 Tandem 0 9 0 2 Local PSTN 0 0 1 All Local PSTN 4 0 0 1 Tandem 0 9 2 2 Local PSTN 0 0 3 All Local PSTN 0 0
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-26 Routing for Outside Calls This topic examines routing for hypothetical outside calls, to show how the system managers in Scenario 1 work together to maximize cost benefits from the private network.
Originating or Receiving System Dialed Digits Local Routing Non-Local Routing System A: Ext. FRL: 0 Route 1: ARS Area Code Table routes to tandem trunk pool, FRL 0, prepends 9 < Route 1, System B: Remote access default FRL 3. ARS absorbs 1732, routes to PSTN pool. | Route 2: ARS Area Code Table routes to local PSTN pool, FRL 1, call prohibited for this user. Call denied. ● System B: Ext.
Outside Calls: Scenario 1, Continued Originating or Receiving System Dialed Digits Local Routing Non-Local Routing System A: Receives outside dial-plan routed PRI data call at 64 kbps. System A: PRI dial-plan routing deletes 555, checks local dial plan, then finds number in non-local dial plan. Routes via non-local UDP Pattern 3 to PRI tandem trunk pool 3366 at 64 kbps, Data only < System B: First part of 2B data call arrives at video system, Ext. 7002.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Intersystem Calling Page 2-29 2 This topic illustrates how different types of calls are made and received in Scenario 1, using the extension numbers and extension equipment types shown in Figure 2–1. Table 2–5, page 2-30 enumerates some sample calls, showing how they are displayed at different recipients’ extensions within the private network.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios Intersystem Calling: Scenario 1 2 Table 2–5. Type of Call Caller Caller Dials Recipient Recipient Sees... Non-local extension System A: Ext. 3212 System B Ext. 6777, MLX-10D Display: Number 35, 75. Non-local extension System B: Ext. 6988 System A Ext. 3212, MLX-20L Display: Both :21* 6 Non-local extension System A: Ext.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–5. Intersystem Calling: Scenario 1, Continued Caller Dials Recipient Recipient Sees... Transfer of outside GS/LS call to non-local extension Outside to System A: Ext. 3105 Transfer System B Ext. 6871, MLX-10D Display: Number 35, 75. Transfer of outside PRI-ANI call to non-local extension.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Scenario 2: Two Systems, Tandem Tie Facilities Page 2-32 2 Scenario 2 describes a medium-sized, mail-order company that has two locations, one in Chicago and one in California. This scenario includes more system details and fuller descriptions of business needs than do the others in this chapter.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Issue 1 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-35 To simplify cost accounting and make outcalling more economical, field representatives access the West coast system remotely, then use the system to dial out to customers, make intersystem calls to headquarters in Chicago, and make ARS calls to the Midwest.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Table 2–6. Page 2-36 Work Group Needs Work Group Needs President and vice- Ability to meet frequently, face to face, without incurring travel costs presidents, W. Coast Division Mgr., Plant Mgr., Personnel Mgr.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Table 2–6. Issue 1 August 1998 Page 2-37 Work Group Needs, Continued Work Group Needs Order-Takers and Customer Service Personnel Ability for small-order customers to access an automatic ordering system in which they use their touch-tone phones to enter account numbers, product codes, and so on, without having to wait for an agent.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Table 2–6. Page 2-38 Work Group Needs, Continued Work Group Needs Order-Takers’ and Customer Service Supervisor Ability to observe and control the order agents’ calls (for example, to know who is available) and immediately see whether too many callers are waiting.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Table 2–7.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-40 In addition, each location has one 800 LS/ID line/trunk module. Loudspeaker paging and Music on Hold connect to this module; an emergency loop-start line is also connected to each system for use in the event of a power failure. It also provides needed Touch-Tone Receivers. ■ Tandem Trunks.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-41 Other system equipment includes Uninterruptible Power Supplies (UPSs) to supply backup power in the event of a commercial power failure. People in both locations use these features: ■ Covering Calls.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios ■ Issue 1 August 1998 Page 2-42 Agent Groups. When calls are routed by dial plan from outside PRI facilities with ANI, agents use a LAN-based PassageWay Telephony Services application to access customer information as calls arrive.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-43 second. No additional data communications equipment (DCE) is required. The engineers sometimes use the group videoconferencing system described earlier in this section, which requires two MLX ports. ■ Factory and Warehouse Personnel. People in the warehouse and factory hear loudspeakers from the paging system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Page 2-44 ■ Operator/Receptionist. Each operators/receptionist at headquarters uses an MLX-20L telephone programmed as a Queued Call Console (QCC). Callers to either location who wish to speak to an operator/receptionist, rather than to Intuity AUDIX, can press and are redirected to the QCC at headquarters. ■ System Manager.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 PSTN PRI PRI GS LS T1 LS MERLIN LEGEND Reporter MOH MERLIN LEGEND Reporter ML D ML C Chicago, IL Area code 312 Intuity AUDIX VMI Conversion Number: 6999 ————— Ext.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-46 Table 2–9, page 2-49 shows how the system manager sets up the systems so that users on each system can access the PSTN facilities connected to the other system. Routing details are summarized in Table 2–10, page 2-50.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-47 ■ Customer service reps use OUTWATS lines to call many customers in the U.S., and the company has a discounted pricing plan for these calls. For this reason, ARS routing does not direct all Chicago-to-California calls across the private network.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Table 2–8.
Component System C: Chicago, IL (Area Code: 312) System D: Palo Alto, CA (Area Code: 650) DS1 Switch Type MERLIN LEGEND-PBX MERLIN LEGEND-Ntwk ARS Access Code 9 9 Switch Identifiers Programmed on This System 01 for a system more than 200 miles away (System D) 02 for a system more than 200 miles away (System C) Remote Access Code and COR for UDP and ARS Calls via This System Remote Access Code: 889 Remote Access Code:326 All tie (T1-emulated voice and data) Outward Unrestricted Barrier Code Re
Dialed or Rec’d Digits Rte Pool Type System D: Palo Alto, CA (Area Code: 650) Abs Prep Dialed or Rec’d FRL Digits 1 Tandem 0 9 2 2 Local PSTN 0 0 5 1 Tandem 0 9 3 2 Local PSTN 0 0 5 1 Tandem 0 9 2 2 Local PSTN 0 0 All Local PSTN 4 All Local PSTN 0 Rte Pool Type Abs Prep FRL 1 Tandem 0 9 1 2 Local PSTN 0 0 4 1 Tandem 0 9 2 2 Local PSTN 0 0 4 All Local PSTN 4 0 1 4 All Local PSTN 0
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-51 Routing for Outside Calls This topic examines routing for hypothetical outside calls, to show how the system manager in Scenario 2 maximizes cost benefits from the private network. As you study the example call routes in Table 2–11, page 2-52, review the general setup as described in Table 2–9, page 2-49 and Table 2–10, page 2-50.
Originating or Receiving System Dialed Digits Local Routing Non-Local Routing System C: Ext. FRL: 2 Route 1: ARS Area Code Table routes to tandem trunk pool, FRL 2, prepends 9 < Route 1, System D: Remote access FRL 3. ARS absorbs 1650, routes to PSTN pool. | Route 2: If all lines in Route 1 are busy, ARS Area Code Table routes to local PSTN pool, FRL 5, call prohibited for this user. Call denied ● System C: Ext.
Originating or Receiving System Dialed Digits Local Routing System C: Ext. FRL: 1 Route 1: ARS Area Code Table routes to tandem trunk pool, FRL 3, call prohibited for this user. Call denied ● System C: Ext. FRL: 3 Route 1: ARS Area Code Table routes to tandem trunk pool, FRL 2, prepends 9. < Non-Local Routing System D: Remote access FRL 3. ARS absorbs no digits, routes to PSTN pool.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-54 Intersystem Calling This topic illustrates how different types of calls are made and received in Scenario 2, using the extension numbers and extension equipment types shown in Figure 2–3 on page 2–45. Table 2–12, page 2-55 shows how calls are made and displayed at different recipients’ extensions within the private network.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–12. Intersystem Calling: Scenario 2 Type of Call Caller Caller Dials Recipient Recipient Sees... Non-local extension System C: Ext. 4638 FRL=6 System D Ext. 7342, MLX-5D® 7,( 75. Non-local extension System D, Ext. 7377 FRL=3 System C Ext. 4638, MLX-20L 7,( 75. Intersystem Remote Access System C, Ext.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–12. Intersystem Calling: Scenario 2, Continued Type of Call Caller Caller Dials Recipient Recipient Sees... Transfer of outside PRI-ANI call to centralized VMS/AA Outside to System D: Ext.7771 Transfer System D: Call is sent to integrated VMI calling group 7771 (with VMI conversion number 6999).
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Scenario 3: Four Systems in a Series, Mixed Facilities Page 2-57 2 Like Scenario 1, this example discusses the planning and call-handling for private networking features and routing. It does not describe the business environment in any detail. In this scenario, the systems are connected in a linear fashion, creating a series configuration.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 MLX-20L Home More Menu Inspct Volume v v Feature Transfer HFAI Conf 2 ML J VMS/AA Cambridge, MA Area Code 617 Switch ID 21 LS GS Tandem Tie GS Mute Drop Speaker Hold 3 MNO 5 6 TUV WXYZ OPER # 7 * 8 0 9 Ext. 2233 MLX-20L Ext. 5564 PassageWay ClientTelephone Ext. 5544 MLX-10D Ext.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Non-Local Dial Plans and Facilities Planning Page 2-59 2 This section shows how non-local dial plans, calling groups, switch identifiers, UDP routing, ARS routing, and remote access are set up for each system. Not all details are provided for all facilities and extensions.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-60 ■ System J does not require ARS toll-saving calling for all local system users to outside facilities connected to System L. ■ A series configuration such as this one requires two tandem PRI facilities for the systems that connect to two other systems, in this case Systems K and L.
System K Local Dial Plan: 5540–5569; 5770–5799 Listed Directory Number (QCC queue): 8800 Integrated VMI calling group for routing to Centralized VMS/AA: 7771 Trunks: 5801-5880 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios System J Local Dial Plan: 2210–2259 Trunks: 8801-8880 2 Table 2–13.
System L Local Dial Plan: 6030–6049; 6240–6269 Centralized VMS/AA: 7771 Trunks: 6801-6880 System M Local Dial Plan: 3250–3269; 3410–3449 Integrated VMI calling group for routing to Centralized VMS/AA: 7771 Trunks: 3801-3880 Extension Range: 3410–3449 Pattern: 11 Extension Range: 3410–3449 Pattern: 06 Extension Range: 6030–6048 Pattern: 03 Route 01 Pool=4274, tandem PRI trunks FRL=2, Data Route 01 Pool=5336, tandem PRI trunks FRL=2, Data Route 01 Pool=8762,tandem PRI trunks FRL=0, Both Extension Rang
System K: Boston, MA (Area Code: 617) System L: Washington, DC (Area Code: 202) System M: Raleigh, NC (Area Code: 919) DS1 Switch Type Not applicable for analog tandem tie trunks MERLIN LEGEND-PBX MERLIN LEGEND–Ntwk MERLIN LEGEND-PBX Switch Identifiers Programmed on This System 22 for a system within 200 miles (System K) 21 for a system within 200 miles (System J) 02 for a system more than 200 miles away (System K) 03 for a system more than 200 miles away (System L) 03 for a system more than 20
Centralized VMS/AA System J: Cambridge, MA (Area Code: 617) System K: Boston, MA (Area Code: 617) System L: Washington, DC (Area Code: 202) System M: Raleigh, NC (Area Code: 919) Not applicable because not directly connected to System L by tandem trunks.
Dialed or Rec’d Digits Rte Pool Type System K: Boston, MA (Area Code: 617) Abs Prep Dialed or Rec’d FRL Digits 1 Tandem 0 9 1 2 Local PSTN 0 0 5 1 Tandem 0 9 1 2 Local PSTN 0 0 5 1 Tandem 0 9 2 2 Local PSTN 0 0 5 1 Tandem 0 9 2 2 Local PSTN 0 0 5 1 Tandem 0 9 0 2 Local PSTN 0 0 1 All Local PSTN 4 0 All Local PSTN 0 0 (some local exchanges) Rte Pool Type Abs Prep FRL 1 Tandem to Sys.
Dialed or Rec’d Digits Rte Pool Type System M: Raleigh, NC (Area Code: 919) Abs Prep Dialed or Rec’d FRL Digits 1 Tandem to Sys. K 0 9 1 2 Local PSTN 0 0 5 1 Tandem to Sys. K 0 9 2 2 Local PSTN 0 0 5 1 Tandem to Sys.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-67 Routing for Outside Calls This topic examines routing for hypothetical outside calls, to show how the system managers in Scenario 3 maximize cost benefits from the private network. As you study the example call routes in Table 2–17, page 2-68, review the general setup as described earlier in this section.
Originating or Receiving System Dialed Digits Local Routing Non-Local Routing System J: Ext. FRL: 1 Route 1: ARS Local Exchange Table routes to tandem trunk pool, FRL 0, prepends 9 < Route 1, System K: Call is routed here for a lower cost local call. ARS absorbs no digits, routes to PSTN pool. | Route 2: If all lines in Route 1 are busy, ARS Area Code Table routes to local PSTN line/trunk pool, FRL 1. | System J: Ext.
Originating or Receiving System Dialed Digits Local Routing Non-Local Routing Two outside dial-plan routed 64-kbps PRI 2B data calls arriving at System M dialed twice For each call System M PRI dial-plan routing deletes 555, checks local dial plan, then finds number in non-local dial plan. Routes via UDP Pattern 8 to PRI tandem trunk pool 8760, Data, at 64 kbps, FRL 3.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Intersystem Calling Page 2-70 2 This topic illustrates how different types of calls are made and received in Scenario 3, using the extension numbers and extension equipment types shown in Figure 2–4 on page 2–58. Table 2–18, page 2-71 shows how calls are made and displayed at different recipients’ extensions within the private network.
Caller Dials Routed via... Recipient Recipient Sees... System K: Ext. 5564 System L All PRI System M Ext. 3254, MLX-10D, Name display %52:1 . ([W Non-local extension System L: Ext. 6041 System K PRI and Tie System J Ext. 2252, Analog multiline display 7,( 75. Non-local extension, 2B data System L: Ext 6245 twice All PRI System K Ext. 3414, Digital data workstation Depends on video application Non-local extension System M: Ext. 3254 All PRI System K Ext.
Type of Call Caller Outside PRI-ANI dial-plan routed call to local extension on System M. Extension is busy or unavailable. centralized VMS/AA provides coverage. Outside to System M: ext 3254 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–18. Intersystem Calling: Scenario 3, Continued Caller Dials Routed via... All PRI with PRI routing Recipient Recipient Sees...
* Type of Call Caller System L Outside call transferred to non-local extension by centralized VMS/AA. The non-local extension is busy or doesn’t answer. Outside to centralized VMS/AA, transferred to ext 3254 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–18. Intersystem Calling: Scenario 3, Continued Caller Dials Routed via... Transfer System L: All PRI Recipient Recipient Sees...
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Scenario 4: Four Systems in a Star, Mixed Facilities Page 2-74 2 In this scenario, one MERLIN LEGEND Communications System acts as the hub and three systems are connected to it in a star configuration to the hub. The systems are linked by tandem PRI and analog tie facilities. Figure 2–5 on page 2–75 shows this more complex private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios LS PRI PSTN Page 2-75 VMI Conversion Number: 6999 ————— Ext. 7771 Integrated VMI Calling Group VMI Conversion Number: 6999 ————— Ext. 7771 Integrated VMI Calling Group LS GS PRI PSTN BRI DID DID ML G Austin, TX Area Code 512 Ext. 2248 ML F PassageWay Spokane, WA Client/Telephone Area Code 509 Ext.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Non-Local Dial Plans and Facilities Planning Page 2-76 2 This section explains how non-local dial plans, calling groups, switch identifiers, UDP routing, ARS routing, and remote access are set up for each system. Not all details are provided for all facilities and extensions.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios ■ Issue 1 August 1998 Page 2-77 To reach System G, the routes for intersystem voice calls direct them from Systems F and H via the hub, System E, where they are then sent to System G over tandem tie facilities. FRLs for routes to System G are slightly higher to avoid excessive call volume over the analog tandem tie trunks. NOTE: In Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-78 ■ To insure correct routing for emergency and other N11 calls, and for interexchange calls (IXC), assign PRI trunks to the main pool. ■ Using tandem PRI trunks, an additional system could be connected to either System F or System H.
System F Local Dial Plan: 2200–2259; 2400–2449 Integrated VMI calling Group for Routing to Centralized VMS/AA: 7771 Trunks 2801-2880 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios System E Local Dial Plan: 5400–5499; 5610–5669 Centralized VMS/AA: 7771 Trunks 5801-5880 2 Table 2–19.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–19.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios 2 Table 2–19.
System E: Baltimore, MD (Area Code: 410) System H: Reston, VA (Area Code: 703) DS1 Switch Type MERLIN LEGEND-Ntwk MERLIN LEGEND-PBX Switch Identifiers Programmed on This System 22 for a system within 200 miles (System H) 21 for a system within 200 miles (System E) ARS Routing: Calls to Local or Nearby Area Codes All FRLs are set to low values for these calls. Four digits are absorbed for 410 area code calls, and no digits are absorbed for 301 and 703 area code calls.
System E: Baltimore, MD (Area Code: 410) System H: Reston, VA (Area Code: 703) ARS Routing: Calls to Area Code of Non-Local System (Absorb = 0; Prepend = 9) For primary routes serving calls to area codes 509 and 512, the FRL is 0. Routing specifies pools of tandem PRI facilities, which are also used for non-local extension calling. The FRL is higher for primary routes to areas near but not in the same area code as one of the other private network systems.
System F: Spokane, WA (Area Code: 509) System G: Austin, TX (Area Code: 512) DS1 Switch Type MERLIN LEGEND-PBX Not applicable for tandem tie trunks Switch Identifiers Programmed on This System 01 for a system more than 200 miles away (System E) 01 for a system more than 200 miles away (System E) ARS Routing: Calls to Local or Nearby Area Codes Digit string: 1509: Area Code Table, Route to pool(s) of local PSTN facilities, FRL=0, Absorb=4 Digit string: 1512: Area Code Table, Route to pool(s) of loc
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-85 Routing for Outside Calls This topic examines routing for hypothetical outside calls, to show how the system managers in Scenario 4 maximize cost benefits from the private network. As you study the example call routes in Table 2–22, page 2-86, review the general setup as described in Table 2–20, page 2-82 and Table 2–21, page 2-84.
Originating or Receiving System Dialed Digits Local Routing Non-Local Routing System H: Ext. FRL: 0 ARS Local Exchange Table routes to tandem trunk pool, FRL 0, prepends 91703 < System E: ARS absorbs no digits, routes to PSTN pool. | System H: Ext. FRL: 2 Call routed to local main pool loop-start line.| Not applicable System H: Ext.
Originating or Receiving System Non-Local Routing DID call arrives at System F System F DID receives 5438, checks local dial plan, then finds number in nonlocal dial plan. Routes via UDP Pattern 1 to PRI tandem trunk pool 5260, Voice and Data < System E: Voice call arrives at Ext. 5438, PassageWay client, which does not receive ANI. ● PRI-ANI call arrives at System F System F PRI dial-plan routing deletes 555, checks local dial plan, then finds number in non-local dial plan.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Scenario 5: Large System Hub Page 2-88 2 In this scenario, two MERLIN LEGEND Communications Systems are linked to a hub DEFINITY ECS or DEFINITY ProLogix Solutions system in a star configuration. Rather than repeating points made in earlier scenarios, this section concentrates on the unique features of the Scenario 5 configuration.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Page 2-89 MLX-20L Home More Menu Volume v LS Inspct v Feature Transfer HFAI Conf Mute Drop Speaker Hold Message 1 GHI 4 PQRS 7 * ABC 2 DEF 3 JKL MNO 5 6 TUV WXYZ OPER # 8 0 Ext. 1822 2B Data 9 Ext. 1674 MLX-20L Ext. 1670 MLX-10D PRI PSTN ML O ML OGA Atlanta, PRI Ext.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Non-Local Dial Plans and Facilities Planning Page 2-90 2 This section summarizes non-local dial plans, switch identifiers, UDP routing, and ARS routing for each system. Not all details are provided for all facilities and extensions. Remote access information has been discussed in earlier scenarios.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-91 Table 2–24, page 2-93 is an overview of how the system managers set up their systems for internetwork use of PSTN facilities. To avoid repetition, details are not provided. As you review the table, keep the following points in mind: ■ Network calls going out to the PSTN are not routed through Systems N and O.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-92 Table 2–23.
DS1 Switch Type Programmed on this System System A: Atlanta, GA (Area Code: 404) System O: Atlanta, GA (Area Code: 404) System N: Denver, CO (Area Code: 303) Private Network MERLIN LEGEND-Ntwk MERLIN LEGEND-Ntwk Switch Identifiers Not applicable Programmed on This System 51 for a system that is within 200 miles 41 for a system that is more than 200 and is not a MERLIN LEGEND miles away and is not a MERLIN Communications System (System A) LEGEND Communications System (System A) ARS Access Codes 9 9
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Issue 1 August 1998 Page 2-94 Routing for Outside Calls This topic examines routing for hypothetical incoming and outgoing outside calls, to show how the system managers in Scenario 5 maximize cost benefits from the private network. As you study the example call routes in Table 2–25, page 2-95, review the general setup as described in Table 2–24, page 2-93.
Originating or Receiving System Dialed Digits Local Routing Non-Local Routing System O: Ext. FRL: 1 ARS Area Code Table routes to main pool, FRL 2, call denied. ● None System N: Ext. FRL: 3 ARS Area Code Table routes to tandem trunk pool, FRL 2.< System A: ARS Area Code Table routes to outgoing PRI lines, performing necessary digit manipulation | System A receives 2 incoming data calls at 64 kbps.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 2 Call-Handling Scenarios Network Configuration Scenarios Intersystem Calling Page 2-96 2 Table 2–26, page 2-97 illustrates dialing and recipient screen displays for calling among extensions in Scenario 5.
Caller Non-local extension System O: Ext. 1674 Non-local extension MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Call-Handling Scenarios Network Configuration Scenarios * Type of Call 2 Table 2–26. Intersystem Calling: Scenario 5 Caller Dials Routed via... Recipient Recipient Sees... System A All PRI System N Ext. 4502, MLX-20L, Name and number display 3$<52// System N: Ext.
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Account Code Entry Feature Interactions Page 3-1 3 This topic summarizes the ways that MERLIN LEGEND Communications System features work across private networks. For detailed descriptions of the features mentioned in this section, see the Feature Reference.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Allowed/Disallowed Lists Allowed/Disallowed Lists Page 3-2 3 The system manager helps prevent toll fraud by assigning a Disallowed List to the default COR for tie and/or non-tie trunks (the factory Disallowed List 7 is recommended). The Disallowed List should be programmed to include 900,976, and other types of calls that the user should not be allowed to call.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Automatic Route Selection (ARS) Automatic Route Selection (ARS) Page 3-3 3 To help prevent toll fraud, ARS access codes for other networked systems must not be assigned to the non-local dial plan; the local ARS access code cannot be assigned to the non-local dial plan. For example, if the ARS access code is 9, extension ranges such as 9000–9039 cannot be assigned.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Barge-In Page 3-4 Extension Facility Restriction Levels (FRLs) are applied only to calls while they are on the local system, and are compared both to UDP routes and to ARS routes. For example, if a UDP route FRL is 1 and the caller’s extension FRL is 0, the caller is unable to use the route, because the route FRL is higher than the extension FRL.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Caller ID Page 3-5 3 Caller ID For 6.1 and later systems, Caller ID and Automatic Number Identification (ANI) information is conveyed across the private network when PRI tandem trunks are used to route the call and under the following conditions: ■ The call is transferred using a DSS with one-touch transfer with automatic completion.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Camp-On Page 3-6 should be assigned to the main pool. In this case, IXC calls determine the number of loop-starts required. Refer to Feature Reference guide for details on the PFT feature. NOTE: VMI ports default to FRL=0. To allow the VMS/AA to transfer calls across the private network, the VMI ports’ FRL should be set to 3.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Computer Telephony Integration (CTI) Link Page 3-7 ■ To use Direct Voice Mail, the calling extension and the called extension must be on the same system. ■ Leave Word Calling only works only if the calling extension, called extension, and covering voice mail for the called extension are on the same system. For 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Conference Page 3-8 ■ For an incoming call, if the PassageWay Telephony Services application uses the presence of a trunk identifier in the delivered event to differentiate PSTN calls from UDP calls, a PassageWay Telephony Services client displays a non-local dial plan call in the same way it does a PSTN call.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Coverage Coverage Page 3-9 3 In Release 6.0, calls arriving for extensions at one system cannot be covered by extensions or calling groups on a non-local system. For Release 6.0 and later systems, non-local dial plan calls are treated as outside calls by the system and by Selective Coverage features: Coverage Inside and Coverage VMS Off. In Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Direct-Line Console (DLC) Direct-Line Console (DLC) Page 3-10 3 In Release 6.1 and later systems, a system operator with a DLC can use DSS buttons to make or transfer calls to non-local extensions. However, the LEDs associated with the DSS buttons do not go on when a non-local extension user goes off hook.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Display Page 3-11 3 Display Tandem PRI trunks can provide caller information at the destination MLX multiline display telephone. The system manager programs this capability for each MLX display extension, to allow display of the label (name), extension number, or both.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Do Not Disturb Page 3-12 Forwarding Delay to one ring. Transfer of the call must be completed before the call is forwarded. For 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Forward and Follow Me Forward and Follow Me Page 3-13 3 The use of Forward and Follow Me in networked systems is as follows: ■ For Release 6.0 and later systems, Follow Me is not supported across the private network. ■ For Release 6.1 and later systems, Call Forwarding is used to forward calls directly to a non-local extension; you do not have to enable Remote Call Forwarding.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Group Calling Issue 1 August 1998 Page 3-14 ■ Night Service coverage across a private network to a centralized Automated Attendant, non-local calling group, QCC queue, DLC, or any individual extension such as a night bell or an extension on a remote MERLIN LEGEND, DEFINITY ECS or DEFINITY ProLogix system, or to the PSTN via UDP routing.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Hands Free Answer on Intercom (HFAI) Page 3-15 ■ Calls sent to a calling group with a non-local member will never overflow locally. The calls are sent across the private network and the exact processing depends on the nature of the receiving extension on the far system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions HotLine HotLine Page 3-16 3 A HotLine extension must be on the local system. However, a HotLine telephone can dial a non-local extension number. Labeling 3 For incoming calls, the alphanumeric label and/or extension number for non-local dial plan extensions appears on local system MLX displays according to display preference programming.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Music On Hold Music On Hold Page 3-17 3 Music On Hold sources cannot be shared by networked systems. Calls between systems in a private network are treated as outside calls; for this reason, non-local callers hear Music On Hold as though they were outside callers.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Park Page 3-18 3 Park Park zones must be in the local system. Calls cannot be parked at remote park zones. Personal Lines 3 To avoid toll fraud, private networked trunks must not be assigned to extensions as personal lines. In Release 6.1 and later systems, only the principal user of a personal line can forward calls received on the personal line to a non-local extension.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Primary Rate Interface (PRI) and T1 Primary Rate Interface (PRI) and T1 Page 3-19 3 “Tandem Trunks” on page 10 and the scenarios in Chapter 2 provide details about private network routing of incoming outside calls received on PRI and T1 facilities. Programming is described in Chapter 5, “Network Management.” PRI or T1 facilities can be private tandem trunks.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Queued Call Console (QCC) Queued Call Console (QCC) Page 3-20 3 For Release 6.0 systems, an extension may not have its calls covered by a QCC on another system. For Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Remote Access Remote Access Page 3-21 3 “Remote Access” on page 8 provides details about setting up and using remote access in private networks. The scenarios in Chapter 2 provide examples of remote access setup and use in private networks. In addition, Chapter 4, “Security,” provides information about how remote access is used in private networks.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Service Observing ! Page 3-22 SECURITYlALERT: Networked systems require special attention to security issues. Follow the rules below when setting up and planning your system for private network use.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Station Message Detail Recording (SMDR) Station Message Detail Recording (SMDR) Page 3-23 3 For 6.0 systems, all private network calls are reported according to SMDR Call Report programming for reporting non-UDP incoming and outgoing calls. To log network calls, SMDR should be programmed to report both incoming and outgoing calls. In Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Station Message Detail Recording (SMDR) Page 3-24 Incoming DID call from the PSTN routed across the private network. PSTN PSTN System SystemAA ININ 555-1234 555-1234 System SystemCC System SystemBB OUT OUT 555-1234 555-1234 ININ 1234 1234 OUT OUT 1234 1234 ININ 1234 1234 Ext. Ext.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Speed Dial Page 3-25 Incoming DID call from the PSTN routed across the private network. PSTN PSTN System SystemAA ININ 555-1234 555-1234 System SystemCC System SystemBB OUT OUT 555-1234 555-1234 ININ 1234 1234 OUT OUT 1234 1234 ININ 1234 1234 Ext. Ext.1234 1234 Outgoing ARS call routed across the private network and out to the PSTN using a remote system’s PSTN facilities.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions System Renumbering System Renumbering Page 3-26 3 A separate numbering plan is provided for non-local dial plan extensions, allowing system managers to enter the ranges of extensions on remote systems. These ranges are associated with patterns that in turn allow routing over private tandem trunks or over PSTN facilities when appropriate.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Voice Announce to Busy Page 3-27 Transfers across networked systems over tandem tie trunks do not return to the transferring extension. If such a call is transferred to a busy or invalid non-local dial plan extension or one with Do Not Disturb turned on, the transferred party hears busy or fast busy tone and must hang up and call back in order to speak with someone.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 3 Feature Interactions Voice Messaging Interface (VMI) Issue 1 August 1998 Page 3-28 All remote systems in the private network can have Group Coverage for individual extensions or overflow coverage for calling groups directed to the centralized VMS/AA by creating a local integrated VMI calling group with a single non-local member (called the VMI conversion number).
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Page 4-1 Security 4 This chapter describes the security issues that you must consider as you plan and maintain a system in a private network. Most of these points have been raised in earlier chapters, and Chapter 2, “Call-Handling Scenarios,” provides examples of security considerations.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Overview Overview Page 4-2 4 Security planning and implementation, like other aspects of networking, require careful coordination among system managers. Local system business needs must be balanced with overall routing and security considerations. Network system managers must combine existing features and new networking features to safeguard against toll fraud.
Restriction, Feature, or Setting Personal Lines Pool buttons Dial Access to Pools Trunk-to-Trunk Transfer Not Allowed Yes On Yes On No An extension that is prohibited from making trunk-to-trunk transfers cannot transfer an outside call to another local system trunk connected to the PSTN that is a PSTN trunk-to-trunk transfer. However, despite prohibitions, a user can transfer a private network trunk call to a non-local extension or to an outside central office trunk.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Security Overview 4 Continued on next page Restriction, Feature, or Setting Toll Restriction Allowed and Disallowed Lists Factory Setting On Disallowed List 7 Night Service Off with Outward Restriction Extension Status Off Suspended? Yes No Yes Yes Description Despite toll restrictions, users can make calls to non-local extensions. Retain Disallowed List 7 and add to it as necessary.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access ! Page 4-5 SECURITYlALERT: Networked systems require special attention to security issues. Follow the rules below when setting up and planning your system for network use.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access Page 4-6 ■ Extensions. The factory-set FRL for extensions is 3. When an extension user attempts to use ARS or make a UDP call on his or her local system, the extension FRL is compared to the local ARS or UDP route FRL. In order for the call to go through, the extension FRL must be equal to or greater than the route FRL. ■ VMI Ports.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access Issue 1 August 1998 Page 4-7 The system manager sets the options listed below for the remote access default COR on his or her own system. If the system is linked to the network by tandem tie facilities (analog, T1-emulated voice, or data), the settings are assigned to all tie trunks.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access ■ Issue 1 August 1998 Page 4-8 Disallowed List Assignment. Disallowed Lists should be used for the default COR. You should use Disallowed List 7, which prohibits a variety of calls often made by toll fraud abusers. Review and add to this list as needed. When a Disallowed List is assigned, ARS calls cannot reach the specific numbers included on the list.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access Table 4–2. Page 4-9 Recommended Settings for Tie and Non-Tie Default COR and Callback Recommended Setting Name Setting Description Barrier Code Requirement On Requires barrier code entry for remote access calls on DID, PRI dial plan-routed, dedicated or shared remote access, or tandem facilities.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access Page 4-10 After a call is routed to another system, the extension/barrier code FRL has no effect. The remote system’s default COR FRL takes its place. For the call to go through, the default COR FRL must be equal to or higher than the remote system ARS or UDP route FRL, whichever is routing the call next.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 4 Security Facility Restriction Levels and Remote Access Table 4–3.
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Page 5-1 Network Management 5 This chapter summarizes the system programming required in order to set up and maintain a system within a private network. Full details of all procedures, including step-by-step programming instructions are included in System Programming.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks General Programming in Private Networks Page 5-2 5 This section outlines system features and programming options that may need adjustment or special planning when your system is included in a private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Automatic Route Selection (ARS) Page 5-3 5 This topic describes two aspects of ARS as it is used in private networks: ■ The general steps for setting up ARS in order to facilitate the use of PSTN facilities by non-local users ■ ARS Facility Restriction Levels (FRLs) assigned to extensions and how their operation differs in a private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Page 5-4 used for emergency or other N11 calls, it should be assigned to the main pool. In this case, IXC calls determine the number of loop-starts required. Refer to Feature Reference guide for details on the PFT feature. At the system where calls are delivered to the PSTN, digit manipulation may also be required.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Page 5-5 “Facility Restriction Levels and Remote Access” on page 5 discusses the interactions among FRLs in greater detail. For procedures that allow you to assign ARS FRLs to extensions, see System Programming.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Page 5-6 Programming. For guidelines on setting up remote access COR settings, see “Remote Access Default Class-of-Restriction Settings” on page 6. The remote access Automatic Callback setting of on or off does not apply to private network calls. Automatic Callback can be used at users’ local system when all private networked trunks are busy.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Page 5-7 source is a Digital Signal 1 (DS1) facility connected to a long-distance carrier rather than a local exchange carrier. A second choice is a Basic Rate Interface (BRI) or PRI facility connected to any PSTN carrier. The Feature Reference outlines these choices and other alternatives in its “Primary Rate Interface (PRI) and T1” section.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Page 5-8 facility. In the diagram above, notice that System B has three 100D modules (and therefore three ports) to provide synchronization. (See the diagram above.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Tie Trunks Page 5-9 5 Program analog tandem tie trunks for delay-start seizure type, two way operation, E&M signalling type (as appropriate), the factory-set default disconnect time of 300 milliseconds, and touch-tone dialing. Refer to System Programming for detailed programming instructions.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Group Calling Enhancement Page 5-10 5 In Release 6.1 and later, a calling group may have a single non-local member that is defined under the Uniform Dial Plan as existing on another MERLIN LEGEND Communications System connected by a tandem trunk. A calling group can have a single non-local member or several local extensions.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Issue 1 August 1998 Page 5-11 ■ If the pattern associated with the calling group has a route that includes PSTN trunks, each call over the PSTN has an associated cost. ■ SMDR records for calls sent across a private network may be different from what is expected. For example, UDP calling may not be logged for part of the call.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Centralized VMS/AA Page 5-12 5 Centralized VMS/AA is implemented using the Group Calling enhancement and UDP routing. Integrated VMI calling groups are defined on the VMS hub system and each remote system. From the user’s point of view, the routing is transparent.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management General Programming in Private Networks Issue 1 August 1998 Page 5-14 2. Assign an FRL of 0. 3. Specify the digit absorption parameter to absorb exactly the number of digits in the VMI conversion number. For example, if the VMI conversion number is 3738, specify 4. 4. Specify the other (prepended) Digits parameter to add the extension number for the centralized VMSAA calling group on the VMS hub.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Non-Local Dial Plan Numbering Page 5-15 Centralized Automated Attendant Programming 5 Programming for a centralized automated attendant is the same as for a local automated attendant with the following differences: ■ ! If incoming calls at remote systems are to be answered by the centralized automated attendant, establish a VMI calling group at each remote system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Non-Local Dial Plan Numbering Page 5-16 Non-local dial plan calls are routed over pools of private trunks using UDP routing. To maintain existing dial plans when systems are networked or when one system’s dial plan changes, UDP routing provides digit absorption and digit prepending, allowing dialed numbers to be modified before they are actually sent to the remote system.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Non-Local Dial Plan Numbering Issue 1 August 1998 Page 5-17 An extension number range may stipulate a single extension number. For Release 6.1 and later systems, the single non-local extension member (called the VMI conversion number) assigned to an integrated VMI calling group used to route calls to a centralized VMS/AA must be the only extension assigned to an extension range.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Non-Local Dial Plan Numbering Page 5-18 Task List: Non-Local Dial Plan Numbering 5 NOTE: Any local dial-plan changes should be made before you program the nonlocal dial plan. o Obtain Non-Local UDP Administration Form. A copy is located in the Installation Specification, Non-Local Dial Plan Numbering.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Switch Identifiers Switch Identifiers Page 5-19 5 If your system uses private tandem trunks, you must program switch identifiers. Switch identifiers are 1- or 2-digit numbers that are used by the system to identify transmission levels and check routing. Switch identifiers indicate the switch connected to the far end of a local private trunk.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Switch Identifiers Page 5-20 NOTES: 1. The Enter Switch Number screens for the switch identifier procedures include a Help option that supplies most of the information above. 2. For information about DEFINITY ECS or DEFINITY ProLogix systems, consult the documentation for the system. A switch identifier should be unique across a private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Switch Identifiers Programming Instructions Console Procedures Page 5-21 5 To enter an identifier for one trunk: /LQHV7UXQNV→More→8'3→6Z1XP 6LQJOH→Dial trunk no.→(QWHU→Dial switch no.→(QWHU→([LW→ ([LW→([LW To enter an identifier for a block of trunks: /LQHV7UXQNV→0RUH→8'3→6Z1XP %ORFN→Dial starting trunk in block→(QWHU→Dial ending trunk in block→ (QWHU→Dial switch no.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Tandem PRI Facilities Tandem PRI Facilities Page 5-22 5 This topic presents considerations for managing tandem PRI facilities connected to your local system in a private network. If your system includes PSTN PRI facilities that route calls to non-local extensions, you also need to consult the procedures in the “Dial Plan Routing” topic of “PRI Facilities,” System Programming.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Tandem PRI Facilities PRI Facilities Switch Type Page 5-23 5 In this procedure, two additional switch types allow you to specify additional switch options in order to set up a PRI tandem trunk that connects two MERLIN LEGEND Communications Systems or a MERLIN LEGEND Communications System and a DEFINITY ECS or DEFINITY ProLogix Solutions system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Tandem PRI Facilities ■ Page 5-24 The Copy Telephone Number to Send setting is set to Copy for the PRI tandem trunk B-channel group; this setting cannot be changed as long as the switch type is in effect. For more information, see “Copy Telephone Number to Send” in the “PRI Facilities” section of System Programming.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Uniform Dial Plan Routing Uniform Dial Plan Routing Page 5-25 5 This section includes programming procedures for assigning UDP routing. UDP routing is very similar to ARS, except that it is slightly simpler.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Uniform Dial Plan Routing UDP Routes Page 5-26 5 In UDP routing, routes 1–4 are associated with patterns, which are assigned first by associating non-local dial plan extension ranges with those patterns. You can use up to 20 patterns and up to 50 extension ranges. A pattern can be assigned to as many extension ranges as necessary.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Uniform Dial Plan Routing Page 5-27 NOTE: Extension outward and toll calling restrictions are ignored when a user dials a non-local dial plan extension. However, FRL extension restrictions remain in effect. For Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Uniform Dial Plan Routing Page 5-28 NOTE: Do not use this procedure to overcome conflicts between local and nonlocal extension numbering. Such conflicts can result in numerous problems with system features and should be resolved by system renumbering of the affected systems. The factory setting is 0.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Uniform Dial Plan Routing Page 5-29 Special characters such as *, Stop, and # cannot be included as extra digits. Pause is allowed in every position but the first. NOTE: Digit absorption is applied before digit prepending. The factory setting is empty.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Uniform Dial Plan Routing Page 5-30 5 Programming Instructions Console Procedures To specify routes: 7DEOHV→8'3 5RXWLQJ→Dial pattern no.→(QWHU→Dial route no.→(QWHU→3RRO→Dial pool dial-out code→ (QWHU→([LW→([LW→([LW→([LW To assign FRLs to routes: 7DEOHV→8'3 5RXWLQJ→Dial pattern no.→(QWHU→Dial route no.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 5 Network Management Display Preferences for Intersystem Calls Display Preferences for Intersystem Calls Page 5-31 5 Use this procedure to specify display preferences on MLX display telephones, for incoming PSTN calls or non-local dial plan calls that arrive on PRI tandem trunks.
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Page 6-1 Troubleshooting 6 This chapter helps you analyze and solve some common private network calling problems that users of your system may encounter. Each problem is summarized, with possible causes and solutions. Most problems listed here originate in system programming on one or more systems in a private network.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Troubleshooting Guidelines and Preparation Troubleshooting Guidelines and Preparation Page 6-2 6 Before troubleshooting problems, obtain copies of your system’s planning forms.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Troubleshooting Guidelines and Preparation Issue 1 August 1998 Page 6-3 The next topic provides specific information to help you review non-local extension ranges, patterns, and routing on your system. This information is required for several of the troubleshooting procedures in this chapter.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Verifying Switch Identifiers Page 6-4 6 Verifying Switch Identifiers For communications between switches to operate properly, the switch identifiers must be properly set: ■ The switch identifier must be appropriate for a MERLIN LEGEND or DEFINITY system. ■ The switch identifier must be appropriate for near or far distance between connected systems.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Call to a Non-Local Extension: Unexpected Busy Tone Call to a Non-Local Extension: Unexpected Busy Tone Page 6-5 6 This topic discusses unexpected busy tones that may be caused by system features. It applies not only to regular calls from one private network extension to another but also to remote access calls that are routed among private network systems.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone Call to Non-Local Extension: Silence or Fast Busy Tone Page 6-6 6 The following are likely circumstances in which silence occurs when a call is attempted: ■ A selected tie or analog facility between the caller or called extension is out of service.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone Issue 1 August 1998 Page 6-7 than routes that specify tandem facilities, you may need to adjust extension and route FRLs in order to restrict access to them. Be sure that you discuss any changes with the coordinating system manager.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone Issue 1 August 1998 Page 6-8 ■ To change the extension FRL, see System Programming, Chapter 3, “Common Administrative Procedures.” ■ To change the FRL assigned to a remote access barrier code, see “Remote Access” in System Programming, Chapter 4. Follow the guidelines in “Remote Access Default Class-of-Restriction Settings” on page 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone Issue 1 August 1998 Page 6-9 Possible Cause 6: There may be a numbering conflict in the switch identifiers for the trunks that carry the call. Within a private network, switch identifiers should be unique and unambiguous. If they are not, calls may terminate prematurely or continue to route unexpectedly.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone Issue 1 August 1998 Page 6-10 select the 3ULQW option on the System Programming menu and then choose 35, ,QIR. “PRI Facilities Switch Type” on page 23 provides summary instructions for determining the switch type programmed at your system and changing it if necessary.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Troubleshooting Call to Non-Local Extension: Warble Tone (Error Tone) Page 6-11 6 ■ If FRL settings are not the cause, go to Possible Cause 9. Possible Cause 9: If the call is a 64-kbps data call, all routing facilities may not support this data speed. What to Do: Unless you are directly connected to the destination system, the coordinating system manager must check the routes for the call.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Troubleshooting Call to Non-Local Extension: Warble Tone (Error Tone) Page 6-12 6 Possible Cause 3: The pattern does not have pools assigned to any routes. What to do: Verify that the correct pattern is assigned to the range. If the pattern is correct, assign the pools to the routes.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Troubleshooting Calls to Non-Local Extensions: Unexpected Busy Tone Page 6-13 6 ■ Check to make sure the calling restriction of the default COR is set to unrestricted. The factory setting is outward restricted, which blocks calls across the private network. ■ Check that the routes voice/data capability is correct for the type of call being made.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Troubleshooting Call to Non-Local Extension Reaches Wrong Extension Page 6-14 6 Call to Non-Local Extension Reaches Wrong Extension 6 Possible Cause: If a call to a non-local extension connects to the wrong extension, one or more non-local dial plan extension ranges and/or routes may be incorrectly programmed. Non-local dial plan numbers must be unique and unambiguous or calls can be misrouted.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Transfer Call to Non-Local Extension Does Not Return Page 6-16 Telephony Services client, only the transfer originator calling information is delivered to the extension, not information about the original caller. ■ PSTN Trunk Transfer.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Conference: Cannot Add Call Conference: Cannot Add Call Page 6-17 6 Non-local extensions are treated as outside parties for the purpose of transfer. A non-local conference participant takes up one of the two outside calls permitted in a conference. NOTE: A PassageWay Telephony Services client cannot add a non-local extension to a conference.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting DID Calls Not Completed Issue 1 August 1998 Page 6-18 ■ If not enough trunks are available, consider adding more to the system. ■ If there are sufficient trunks assigned and the problem persists, the cause of the problem may be at an intervening system between the one where the calls are received from the PSTN and the destination. Go to Possible Cause 2.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting ARS Calls Are Blocked ARS Calls Are Blocked Page 6-19 6 Verify that switch identifiers have been assigned to both ends of all private network trunks. (Switch cannot identify tandem versus central office lines. ARS is blocked from central office lines.) Possible Cause 1: The switch identifiers for the trunks that carry the cal may not be assigned or may be assigned incorrectly.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Callback Does Not Work Callback Does Not Work Page 6-20 6 Callback allows queueing for an available line/trunk connected to the local system. If a user attempts an ARS- or UDP-routed call and hears a busy signal or warble tone, the signal may be derived from a non-local system’s tandem or PSTN facilities. If this is the case, Callback does not work.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Network Call Transmission Level (Volume) Too Low or Too High Page 6-21 2. As necessary, note the switch identifier programmed on each system for the trunks that carry the calls. To review a report including the switch identifiers programmed on a system, select the 3ULQW option on the System Programming menu and then choose 7UXQN ,QIR and *HQHUDO. 3.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting MLX Displays: Network Call Display Problems Page 6-22 Possible Cause 2: More than three analog spans are involved in the call. What to Do: This may occur when calls are transferred or forwarded multiple times across analog facilities. Consider changing to digital facilities if this situation occurs frequently.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting PassageWay Call Display Problems Page 6-23 Possible Cause 4: Transfer completed too quickly. What to Do: Callers must wait at least two seconds before completing transfers. If none of these factors caused the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting ARS Calls Go to System Operator (Unassigned Extension) ARS Calls Go to System Operator (Unassigned Extension) Page 6-24 6 Possible Cause: System managers in your private network may have set up ARS and remote access to route outgoing calls to PSTN facilities on switches where these calls are most economical.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Excessive Line Noise on Voice and Data Calls Excessive Line Noise on Voice and Data Calls Page 6-25 6 Possible Cause: Clocks are not properly synchronized. What to Do: The coordinating system manager should check error logs at problem systems. If slips are occurring at a high rate or an alarm was raised, clock synchronization is a problem.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Operator Hears Tones Operator Hears Tones Page 6-26 6 Possible Cause: If the operator receives coverage calls intended for the VMS/AA because there were no ports available, the operator will hear the signalling information intended for the VMS/AA. What to Do: Repair out of service ports or add more VMS ports as necessary so that overflow does not go to operator.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Calls From a Remote System Do Not Reach the Centralized Voice Messaging Issue 1 August 1998 Page 6-27 ■ For individual extensions that will receive coverage by the centralized VMS/AA, establish a coverage group verify that the extensions are assigned as senders in the group and the VMI calling group as the receiver.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Calls From a Remote System Do Not Reach the Centralized Voice Messaging ■ Issue 1 August 1998 Page 6-28 If the routing is correct and enough routes are included in the pattern, but the problem persists, check if PRI lines are used. If they are, check the error log for D-channel inoperative and loss of signal alarms indicating lines are inoperative.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting Calls From a Remote System to Centralized Voice Messaging System Get the Issue 1 August 1998 Page 6-29 instructions for determining the switch type programmed at your system and changing it if necessary. “Switch Type” in the Chapter 4 “PRI Facilities” section of System Programming gives full details. ■ In Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting No Message Waiting Light Update ■ Page 6-30 If the switch identifiers are correct and the problem persists, do one of the following: — If the call is being routed over any tandem PRI facilities, go to Possible Cause 2.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting No Message Waiting Light Update ■ Issue 1 August 1998 Page 6-31 Some of the problems described in this section can occur when a system manager makes a change in a networked system’s local dial plan, non-local dial plan, switch identifier, or DS1 Switch Type setting. Ensure that your private network system forms are kept up to date and that changes are cleared with the coordinating system manager.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 6 Troubleshooting No Message Waiting Light Update Issue 1 August 1998 Page 6-32 ■ If more trunks are available and need to be assigned, follow the procedure in “Trunks to Pools Assignment” in Chapter 4 of System Programming to assign more tandem trunks. All the tandem trunks in a pool must be of the same type (tie or PRI). ■ If not enough trunks are available, consider adding more to your system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Support Telephone Number Page A-1 Customer Support Information A Support Telephone Number 1 In the USA only, Lucent Technologies provides a toll-tree customer Helpline (1 800 628-2888) 24 hours a day. If you need assistance when installing, programming, or using your system, call the Helpline or your Lucent Technologies representative. Consultation charges may apply.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Canadian Department of Communications (DOC) Interference Information Canadian Department of Communications (DOC) Interference Information Page A-2 1 This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference regulations of the Canadian Department of Communications.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 A Customer Support Information FCC Notification and Repair Information Page A-3 The REN (Ringer Equivalence Number) for all three systems is 1.5A. — The facility interface code (FIC) and service order code (SOC): For tie line connection, the FIC is TL31M and the SOC is 9.0F. For connection to off-premises stations, the FIC is OL13C and the SOC is 9.0F.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Installation and Operational Procedures Installation and Operational Procedures Page A-4 1 The manuals for your system contain information about installation and operational procedures. ■ Repair Instructions.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information DOC Notification and Repair Information Page A-5 This equipment returns answer supervision on all DID calls forwarded back to the Public Switched Telephone Network.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 A Customer Support Information Renseignements sur la notification du ministère des Communications du Canada Page A-6 system, if present, are connected. This precaution may be particularly important in rural areas. ! CAUTION: Users should not attempt to make such connections themselves, but should contact the appropriate electrical inspection authority or electrician, as appropriate.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 A Customer Support Information Renseignements sur la notification du ministère des Communications du Canada Page A-7 canalisations d’eau métalliques, s’il y en a, sont raccordés ensemble. Cette précaution est particuliérement importante dans les régions rurales.
MADE IN U.S.A. This digital apparatus does not exceed the Class A limits for radio noise emissions set out in the radio interference reguations of the Canadian Department of Communications. Le présent appareil numérique n’émet pas de bruits radioélectriques dépassant les limites applicables aux appareils numériques de la classe A prescrites dans le Règlement sur le brouillage radioélectrique édicté par le ministère Communications du Canada.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Security of Your System: Preventing Toll Fraud Security of Your System: Preventing Toll Fraud Page A-9 1 As a customer of a new telephone system, you should be aware that there is an increasing problem of telephone toll fraud. Telephone toll fraud can occur in many forms, despite the numerous efforts of telephone companies and telephone equipment manufacturers to control it.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Toll Fraud Prevention Page A-10 To minimize the risk of unauthorized access to your communications system: ■ Use an unpublished Remote Access number. ■ Assign access codes randomly to users on a need-to-have basis, keeping a log of all authorized users and assigning one code to one person. ■ Use random-sequence access codes, which are less likely to be easily broken.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Toll Fraud Prevention Physical Security, Social Engineering, and General Security Measures Page A-11 1 Criminals called hackers may attempt to gain unauthorized access to your communications system and voice messaging system in order to use the system features.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Toll Fraud Prevention ■ Page A-12 Customers should also take advantage of Lucent Technologies monitoring SM services and devices, such as the NetPROTECT family of fraud® detection services, CAS with HackerTracker , and CAT Terminal with Watchdog. Call 1 800 638-7233 to get more information on these Lucent Technologies fraud detection services and products.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 A Customer Support Information Toll Fraud Prevention Page A-13 In Release 3.1 and later systems, default local and default toll tables are factory-assigned an FRL of 2 and 3 respectively. This simplifies the task of restricting extensions: the FRL for an extension merely needs to be changed from the default of 3. Each extension should be assigned the appropriate FRL to match its calling requirements.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Toll Fraud Prevention ■ Page A-14 All voice messaging system users must use secure passwords known only to the user.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Toll Fraud Prevention Page A-15 NOTE: In most cases these are loop-start lines/trunks without reliable disconnect. The local telephone company must be involved in order to change the facilities used for RCF to ground start lines/trunks. Usually a charge applies for this change. Also, hardware and software changes may be necessary in the MERLIN LEGEND Communications System.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Other Security Hints ■ Page A-16 The maximum length should be used for each barrier code, and should be changed periodically. Barrier codes, like passwords, should consist of a random, hard-to-guess sequence of digits. While MERLIN LEGEND Communications System Release 3.0 permits a barrier code of up to 11 digits, systems prior to Release 3.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Other Security Hints Page A-17 ■ Be suspicious of any caller who claims to be with the telephone company and wants to check an outside line. Ask for a callback number, hang up and confirm the caller’s identity. ■ Never distribute the office telephone directory to anyone outside the company; be careful when discarding it (shred the directory).
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Other Security Hints Establishing a Policy Page A-18 1 As a safeguard against toll fraud, follow these guidelines for your MERLIN LEGEND Communications System and voice messaging system: ■ Change passwords frequently (at least quarterly). Changing passwords routinely on a specific date (such as the first of the month) helps users to remember to do so.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Other Security Hints Choosing Passwords Page A-19 1 Passwords should be the maximum length allowed by the system.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 A Customer Support Information Limited Warranty and Limitation of Liability Limited Warranty and Limitation of Liability Page A-20 1 Lucent Technologies warrants to you, the customer, that your MERLIN LEGEND Communications System will be in good working order on the date Lucent Technologies or its authorized reseller delivers or installs the system, whichever is later (“Warranty Date”).
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 A Customer Support Information Remote Administration and Maintenance ■ Page A-22 The System Administration and Maintenance capability of a Hybrid/PBX or Key system is protected by a password. — Change the default password immediately. — Continue to change the password regularly. — Give the password only to people who need it and impress upon them the need to keep it secret.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Page B-1 Sample Reports B This appendix includes samples of the print reports generated by the communications system. It only includes samples of reports that include information about private network features or affect planning for private networks. Table B–1. Sample Report Pages For... Dial Plan Report See...
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Page B-2 Table B–1. Continued For... Extension Information Report See... Direct Group Calling Information Report B–24, B–25 Error Log Report B–26 Switch 56 Data Information Report B–27 B–22 Table B–2 lists all of the system reports and includes the print menu option used to print each report, the report name, and a brief description of each report.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 B Sample Reports Page B-3 Table B–2.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 B Sample Reports Page B-4 Table B–2. Continued Menu Option Report Name ([W 'LUHFW Extension Directory Description Slot/port addresses, extensions, labels and feature-related attributes. Column headings are printed on the first page only and are not carried over to subsequent pages. Column headings 4 through 10 (and 14 through 20) should be read vertically.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 B Sample Reports Page B-5 Table B–2.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Dial Plan Report Page B-6 2 Dial Plan Report Print Menu Option: Sections: 'LDO 3ODQ Pools; Telephone Paging Zones; Direct Group Calling Group; Lines/Trunks; Stations DIAL PLAN FOR POOLS POOL.# 1: POOL.# 2: POOL.# 3: POOL.# 4: POOL.# 5: POOL.# 6: POOL.# 4: POOL.# 8: POOL.# 9: POOL.# 10: POOL.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Dial Plan Report Page B-7 Dial Plan Report—Continued 2 DIAL PLAN FOR STATIONS STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN STN . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Dial Plan Report Page B-8 2 Dial Plan Report—Continued COMPLETE DIAL PLAN FOR STATIONS AND ADJUNCTS ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID ID . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports General Trunk Information Report Page B-12 General Trunk Information Report Print Menu Option: 2 7UXQN ,QIR DQG *HQHUDO GENERAL TRUNK INFORMATION Trk SS/PP RemAccess 801 2/ 1 802 2/ 2 803 2/ 3 804 2/ 4 805 4/ 1 806 4/ 2 807 4/ 3 808 4/ 4 809 5/ 1 810 5/ 2 811 5/ 3 812 5/ 4 813 5/ 5 814 5/ 6 815 5/ 7 816 5/ 8 817 6/ 1 . . . . 912 10/1 913 10/2 . . . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Disallowed Lists Report Page B-19 2 Disallowed Lists Report Print Menu Option: Sections: 'LVDOORZ/VW Lists 1 through 7 DISALLOWED LISTS List : 0 Entry 0: Entry 1: Entry 2: Entry 3: Entry 4: Entry 5: Entry 6: Entry 7: Entry 8: Entry 9: . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Extension Directory Report Page B-21 2 Extension Directory Report ([W 'LUHFW Print Menu Option: EXTENSION DIRECTORY Port Addr Ext # Label 1/ 1 1/ 2 1/ 3 1/ 4 1/ 5 1/ 6 1/ 7 1/ 8 2/ 1 2/ 3 2/ 5 2/ 7 3/ 1 3/ 3 3/ 5 3/ 7 4/ 1 4/ 3 4/ 5 4/ 7 6/ 1 . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Extension Information Report Page B-22 Extension Information Report 2 ([W ,QIR plus extension number Print Menu Option: EXTENSION INFORMATION Extn SS/PP Type 10 1/ 1 MLX-20L + 1 DSS CTI Link Pool Access Page Group Primary Coverage Secondary Coverage Coverage Group Group Coverers NS Groups Group Calling Member Pickup Groups Allowed Lists Disallowed Lists Restrictions ESS Sup.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Direct Group Calling Information Report (Local Members Only) Direct Group Calling Information Report (Local Members Only) Print Menu Option: 2 *US&DOOLQJ DIRECT GROUP CALLING INFORMATION Group # : 770 Group Type : IntegrtdVMI Call Distribution Type : CIRCULAR PryAnn No. EXT # LABEL 1 2 . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Direct Group Calling Information Report (Single Non-Local Member) Direct Group Calling Information Report (Single Non-Local Member) Print Menu Option: 2 *US&DOOLQJ DIRECT GROUP CALLING INFORMATION Group # : 771 Group Type : IntegrtdVMI Call Distribution Type : CIRCULAR PryAnn No. EXT # LABEL 1 2 . . .
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 B Sample Reports Switch 56 Data Information Report Page B-27 Switch 56 Data Information Report Print Menu Option: 2 6ZLWFK Dial Plan Routing for Network Service Expected Digits: 3 Digits to Delete: 0 Digits to Add: 0 Trk 801 802 803 . . .
MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 C Voice/Fax Messaging Systems Page C-1 Voice/Fax Messaging Systems C This appendix provides voice/fax messaging system requirements that must be followed for the voice messaging system to route calls to non-local extensions. MERLIN LEGEND Communications System Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 C Voice/Fax Messaging Systems Supported System Considerations Supported System Considerations Page C-2 3 The following are considerations for voice messaging systems used for centralized automated attendant on MERLIN LEGEND Communications System Release 6.0 Version 11 and later systems. MERLIN LEGEND System 3 For Release 6.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 C Voice/Fax Messaging Systems Supported System Considerations Messaging 2000 Page C-3 3 ■ All local and non-local UDP extensions must be programmed as mailboxes. ■ Messaging 200 can handle 2- 3- or 4-digit dial plans but not simultaneously. All MERLIN LEGEND systems sharing the Messaging 2000 must be renumbered to the same number of digits in the dial plan.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 C Voice/Fax Messaging Systems Fax Messaging in a Centralized Voice Mail Configuration Page C-4 Fax Messaging in a Centralized Voice Mail Configuration 3 Both the Messaging 2000 and Intuity AUDIX systems have fax messaging capabilities.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 D Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Touch-Tone Receiver Requirements Page D-1 D This appendix includes information to aid in determining Touch-Tone Receiver requirements for private network systems. System Requirements for Touch-Tone Receivers 4 A voice messaging system requires a certain number of TTRs in addition to any system requirements for TTRs.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 D Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Table D–1. Page D-2 TTRs Required by VMS/AA Number of VMS Ports Number of TTRs Required 1 1 2 1 3 2 4 2 6 3 8 4 12* 6* 18 8 *If a 12-port MERLIN LEGEND Enhanced Service Center is used, 8 TTRs are required.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 D Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Table D–2. Page D-3 System Requirement for TTRs TTRs Required Calls/Hour No Account Codes Used Account Codes Used 110 2 4 180 4 6 350 4 8 420 6 8 610 6 10 710 8 10 Table D–3 shows the TTRs required for primary delay announcement devices. Table D–3.
Issue 1 August 1998 MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 D Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Page D-4 Table D–4 shows the TTRs required for secondary delay announcement devices. Table D–4.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 D Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Page D-5 The following symptoms indicate that the system needs more TTRs. ■ Single-line telephone users do not get dial tone when they lift the handset to dial out. ■ The voice messaging system fails to transfer calls. ■ Calls fail to ring or go to coverage prematurely.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Glossary Issue 1 August 1998 Page GL-1 LG Glossary Italics The use of italics in the glossary denotes multiple usage of the italicized text throughout the glossary. Numerics 2B data Digital information carried by two B-channels for better performance and quality; the bit rate is twice that of one B-channel used alone.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-2 AMI (alternate mark inversion) Line coding format in which a binary one is represented by a positive or negative pulse, a binary zero is represented by no line signal, and subsequent binary ones must alternate in polarity; otherwise, a bipolar violation occurs. AMI is used in the DS1 interface. Analog data station See modem data station.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-3 Automated Attendant IS II/III, MERLIN LEGEND MAIL, and Lucent Technologies Attendant application that automatically answers incoming calls with a recorded announcement and directs callers to a department, an extension, or the system operator. Automated Document Delivery System See ADDS.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-4 baud rate Strictly speaking, a measurement of transmission speed equal to the number of signal level changes per second. In practice, often used synonymously with bit rate and bps.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-5 BRI (Basic Rate Interface) A standard protocol for accessing Integrated Service Digital Network (ISDN) services. broadband Transmission path having a bandwidth greater than a voice-grade channel. BTMI (basic telephone modem interface) bus Multiconductor electrical path used to transfer information over a common connection from any of several sources to any of several destinations.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-6 centralized telephone programming Programming of features on individual telephones; performed at a central location by the system manager. See also system programming and extension programming. central office See CO. Centrex Set of system features to which a user can subscribe on telephone trunks from the local telephone company.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-7 codec (coder-decoder) Device used to convert analog signals such as speech, music, or television to digital form for transmission over a digital medium and back to the original analog form.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-8 CSU (channel service unit) Equipment used on customer premises to provide DS1 facility terminations and signaling compatibility. CTI link (Computer Telephony Integration) link. A hardware/software feature that is part of the PassageWay Telephony Services application.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-9 D-channel (Data-channel) 16- or 64-kbps channel that carries signaling information or data on a PRI or BRI. dedicated feature buttons The imprinted feature buttons on a telephone: Conf or Conference, Drop, Feature, HFAI (Hands Free Answer on Intercom), Hold, Message, Mute or Microphone, Recall, Speakerphone or Spkrphone, and Transfer.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-10 Digital Signal 1 See DS1. digital subscriber line See DSL. digital switch element See DSE. digital transmission Mode of transmission in which the information to be transmitted is first converted to digital form and then transmitted as a serial stream of pulses. See also analog transmission.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-11 DSL (Digital Subscriber Line) A Digital Subscriber Line provides full-duplex service on a single twisted metallic pair (2-wire) at a rate sufficient to support ISDN Basic Rate Access. DSS (Direct Station Selector) 60-button adjunct that enhances the call-handling capabilities of an MLX-20L or MLX-28D telephone used as an operator console.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-12 ExpressRoute 1000 Data communications device that allows connection between an RS-232 DTE device and the control unit using MLX extension jacks on the 008 MLX or 408 GS/LS-MLX module. extended superframe format See ESF. extension An endpoint on the internal side of the communications system. An extension can be a telephone with or without an adjunct. Also called “station.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-13 Flash ROM Beginning with Release 3.0, a type of read-only memory provided on the processor module, used to supply system features. foil shield Copper foil sheet (for power units) used to prevent excessive noise on the module. forced idle Condition of the system during certain programming or maintenance procedures; system prevents initiation of new calls. foreign exchange See FX.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-14 group videoconferencing system A system application that allows face-to-face, simultaneous video and voice communications between groups and requires high-speed data transmission facilities. See also desktop videoconferencing system. Hands Free Answer on Intercom See HFAI. hands-free unit See HFU. headset Lightweight earpiece and microphone used for hands-free telephone operation.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-15 Inspect screen Display screen on an MLX display telephone that allows the user to preview incoming calls and see a list of the features programmed on line buttons. Integrated Administration Capability of IS III that simplifies the programming of common information for the system, AUDIX Voice Power, and, if it is also installed, Fax Attendant System.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-16 ISDN terminal adapter data station A type of data station that includes an ISDN terminal adapter as its DCE. It may also include an MLX telephone for simultaneous voice and data (ISDN terminal adapter data-only station). These data stations connect to MLX extension jack modules for digital transmission of data over a DS1 facility.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-17 line/trunk jack Physical interface on a module in the control unit for connecting an outside line/trunk to the communications system. Also called “trunk jack.” line/trunk and extension module Module on which the jacks for connecting central office lines/trunks and/or the jacks for connecting the extensions are located.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-18 MFM (Multi-Function Module) Adapter that has a tip/ring mode for answering machines, modems, fax machines, and tip/ring alerts, and an SAA mode for -48 VDC alerts. It is installed inside an MLX telephone and is used to connect optional equipment to the telephone. The optional equipment and the telephone operate simultaneously and independently.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-19 module Circuit pack in the control unit that provides the physical jacks for connection of telephones and/or outside lines/trunks to the communications system. In the name of a module, the first digit indicates the number of line/trunk jacks it contains; the last digit indicates the number of extension jacks it contains.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-20 N network Configuration of communications devices and software connected for information interchange. network interface Hardware, software, or both that links two systems in an interconnected group of systems, for example, between the local telephone company and a PBX.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-21 out-of-band signaling Signaling that uses the same path as voice-frequency transmission and in which the signaling is outside the band used for voice frequencies. parity The addition of a bit to a bit string so that the total number of ones is odd or even, used to detect and correct transmission errors.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-22 power supply module Device that directs electricity to modules and telephones on the system. One power supply module is needed for each carrier, and an auxiliary power unit is added if needed. PRI (Primary Rate Interface) Standard interface that specifies the protocol used between two or more communications systems.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-23 Q QCC (Queued Call Console) MLX-20L telephone used by a system operator in Hybrid/PBX mode only.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-24 S SAA (Supplemental Alert Adapter) Device that permits alerting equipment to be connected to an analog multiline telephone jack so that people working in noisy or remote areas of a building can be alerted to incoming calls. SA buttons Telephone buttons that provide access to both inside and outside calls.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-25 star configuration A private network arrangement where either three or more communications systems are connected with one system acting as the hub system. See also series configuration. station See extension. station jack See extension jack. Station Message Detail Recording See SMDR. Supplemental Alert Adapter See SAA. switch See communications system.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-26 T T1 Type of digital transmission facility that in North America transmits at the DS1 rate of 1.544 Mbps. T1-emulated data A T1 tie trunk programmed for S56DATA for use by data calls at speeds up to 56 kbps. These trunks may be used for tandem and non-tandem operation. T1-emulated voice A T1 tie trunk programmed for Tie-PBX or Tie-Toll for use by voice calls.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-27 trunk Telecommunications path between the communications system and the telephone company central office (CO) or another switch. Often used synonymously with line. trunk jack See line/trunk jack. trunk pool See pool. TSAPI Telephony Services Application Programming Interface. An application programming interface that allows computer telephony applications to be used.
MERLIN LEGEND Communications System Release 6.1 Network Reference 555-661-150 Issue 1 August 1998 Glossary Page GL-28 UPS (uninterruptible power supply) Device that connects to the system to provide 117 VAC to the equipment when the commercial power source fails. VAC (alternating-current voltage) VDC (direct-current voltage) VMI (voice messaging interface) An enhanced tip/ring port.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
MERLIN LEGEND Communications System Release 6.
