Lucent Technologies MERLIN LEGEND Release 6.1 Network Reference Manual
  1. Manuals
  2. Brands
  3. Lucent Technologies Manuals
  4. Conference System
  5. MERLIN LEGEND Release 6.1
  6. Network reference manual

Lucent Technologies MERLIN LEGEND Release 6.1 Network Reference Manual

Release 6.1
Hide thumbs Also See for MERLIN LEGEND Release 6.1:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Installation Manual
MERLIN LEGEND
Communications System
Release 6.1
Network Reference
®
555-661-150
Comcode 108289703
Issue 1
August 1998

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the MERLIN LEGEND Release 6.1 and is the answer not in the manual?

Questions and answers

Related Manuals for Lucent Technologies MERLIN LEGEND Release 6.1

Summary of Contents for Lucent Technologies MERLIN LEGEND Release 6.1

  • Page 1 MERLIN LEGEND ® Communications System Release 6.1 Network Reference 555-661-150 Comcode 108289703 Issue 1 August 1998...
  • Page 2 Lucent Technologies does not warrant that this product is immune from or will prevent unauthorized use of common-carrier telecommunication services or facilities accessed through or connected to it. Lucent Technologies will not be responsible for any charges that result from such unau- thorized use.

  • Page 3: Table Of Contents

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Contents Page iii Contents New Features and Enhancements Release 6.1 Enhancements (August 1998) Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) IMPORTANT SAFETY INSTRUCTIONS About This Book xxvii Intended Audience xxvii...
  • Page 4 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Contents Page iv Call-Handling Scenarios 2–1 Networking Guidelines 2–2 Network Configuration Scenarios 2–14 Feature Interactions 3–1 Account Code Entry 3–1 Alarm 3–1 Allowed/Disallowed Lists 3–2 Authorization Code 3–2 Auto Answer All 3–2...
  • Page 5 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Contents Page v HotLine 3–16 Labeling 3–16 Messaging 3–16 Music On Hold 3–17 Night Service 3–17 Paging 3–17 Park 3–18 Personal Lines 3–18 Pickup 3–18 Pools 3–18 Primary Rate Interface (PRI) and T1 3–19 Queued Call Console (QCC)
  • Page 6 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Contents Page vi Display Preferences for Intersystem Calls 5–31 Troubleshooting 6–1 Troubleshooting Guidelines and Preparation 6–2 Verifying Switch Identifiers 6–4 Call to a Non-Local Extension: Unexpected Busy Tone 6–5 Call to Non-Local Extension: Silence or Fast Busy Tone 6–6...
  • Page 7 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Contents Page vii Customer Support Information A–1 Support Telephone Number A–1 Federal Communications Commission (FCC) Electromagnetic Interference Information A–1 Canadian Department of Communications (DOC) Interference Information A–2 FCC Notification and Repair Information A–2 Installation and Operational Procedures...
  • Page 8 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Contents Page viii Direct Group Calling Information Report (Single Non-Local Member) B–25 Error Log Report B–26 Switch 56 Data Information Report B–27 Voice/Fax Messaging Systems C–1 Supported System Considerations C–2 Fax Messaging in a Centralized Voice Mail Configuration...
  • Page 9 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Figures Page ix Figures Introduction 1–1 1–1 Series Configuration 1–7 1–2 Star Configuration: Five Systems 1–8 1–3 Star Configuration: Three Systems 1–9 1–4 Series Configuration: Four Systems 1–13 1–5 Star Configuration: Three Systems...
  • Page 10 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Figures Page x...
  • Page 11 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Tables Page xi Tables Introduction 1–1 Tandem PRI Trunks versus Tandem Tie Trunks 1-11 Call-Handling Scenarios 2–1 UDP Extension Ranges: Scenario 1 2-22 2–2 Scenario 1: Facilities Planning, Calls Originating within the private network and Going to the PSTN 2-24 2–3 Scenario 1: ARS Routing Summary, Calls...
  • Page 12 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Tables Page xii 2–20 Scenario 4: Facilities Planning, Calls Originating within the Network and Going to the PSTN, Systems E and H 2-82 2–21 Scenario 4: Facilities Planning, Calls Originating within the Network and Going to the PSTN, Systems F and G 2-84...

  • Page 13: Issue

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Tables Page xiii Touch-Tone Receiver Requirements D–1 TTRs Required by VMS/AA D–2 System Requirement for TTRs D–3 TTRs Required for Primary Delay Announcement Devices When Using Prompt-Based Overflow D–4 TTRs Required for Secondary Delay Announcement Devices When Using Prompt-Based Overflow...
  • Page 14 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Tables Page xiv...

  • Page 15: New Features And Enhancements

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 New Features and Enhancements Release 6.1 Enhancements (August 1998) Page xv New Features and Enhancements Release 6.1 Enhancements (August 1998) Release 6.1 includes all Release 6.0 functionality, plus the enhancements listed below.
  • Page 16 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 New Features and Enhancements Release 6.1 Enhancements (August 1998) Page xvi Centralized Voice Messaging 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.
  • Page 17 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 18 PRI Switch Type Test 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. Service Observing Service Observing allows one extension to listen in on (observe) a call at another extension.

  • Page 19: Prior Releases: Features And Enhancements

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Page xix Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Release 6.0 includes all Release 5.0 functionality, plus the enhancements listed below.
  • Page 20 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 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.
  • Page 21 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 22 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Page xxii Prompt-Based Overflow System managers can activate the Prompt-Based Overflow option. This option allows callers waiting in queue and listening to a delay announcement to press the # key in order to reach the overflow receiver for the group, which may be the QCC queue or another calling group (including a calling group assigned for a voice mail system).
  • Page 23 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 24 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Prior Releases: Features and Enhancements Release 6.0 Enhancements (February, 1998) Page xxiv...

  • Page 25: Important Safety Instructions

    Never touch uninsulated telephone wires or terminals unless the telephone wiring has been disconnected at the network interface. Use caution when installing or modifying telephone lines. Use only Lucent Technologies-manufactured MERLIN LEGEND Communications System circuit modules, carrier assemblies, and power units in the MERLIN LEGEND Communications System control unit.

  • Page 26: Save These Instructions

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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.

  • Page 27: About This Book

    See “Related Documents” on page xxx for a list of these guides. This guide is also helpful to MERLIN LEGEND Communications System distributors and to Lucent Technologies employees working with networked systems.

  • Page 28: How To Use This Book

    In the USA only, Lucent Technologies provides a toll-free customer Helpline 24 hours a day. Call the Helpline at 1 800 628-2888 (consultation charges may apply), or call your Lucent Technologies representative, if you need assistance when installing, programming, or using your system.
  • Page 29 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 30: Security

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 About This Book Security Page xxx 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.
  • Page 31 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 About This Book Related Documents Page xxxi MDC and MDW Telephones User’s Guide 555-661-138 555-631-150 MLX-10D Display Telephone Tray Cards (5 cards) 555-631-155 MLX-16DP Display Telephone Tray Cards (5 cards) 555-631-152 MLX-28D and MLX-20L Telephone Tray Cards (5 cards) 555-631-151...

  • Page 32: How To Comment On This Book

    If the feedback form is missing, write directly to: Documentation Manager Lucent Technologies 211 Mount Airy Road, Room 2W226 Basking Ridge, NJ 07920...

  • Page 33: Introduction

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Page 1-1 Introduction 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.

  • Page 34: Networking Concepts

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Networking Concepts Page 1-2 Networking Concepts 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. Branch offices, operations centers, and specialized campuses are supported by technological advances such as local area networks (LANs) and wide area networks (WANs), intranets, the Internet, videoconferencing, and protocols that enable high-speed data communications.
  • Page 35 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Networking Concepts 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.
  • Page 36 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Networking Concepts Page 1-4 Benefits of Networking 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.
  • Page 37 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Networking Concepts 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: —...
  • Page 38 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching 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.

  • Page 39: Tandem Trunking And Tandem Switching

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching Page 1-7 Public Switched Telephone Network (PSTN) ML C ML A ML B ML D Santa Monica, CA New York, NY Chicago, IL Los Angeles, CA Ext.

  • Page 40: Star Configuration: Five Systems

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 41: Star Configuration: Three Systems

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 42 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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 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.

  • Page 43: Tandem Pri Trunks Versus Tandem Tie Trunks

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching Page 1-11 Table 1–1. Tandem PRI Trunks versus Tandem Tie Trunks Feature Differences Intersystem calling PRI provides faster call setup. For intersystem calls, the caller’s Calls that cross tandem tie trunks are extension label and extension number displayed as outside calls.
  • Page 44 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching Page 1-12 Touch Tone Receivers 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.
  • Page 45 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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. Figure 1–4.

  • Page 46: Star Configuration: Three Systems

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 47 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching Page 1-15 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.

  • Page 48: Star Configuration: Five Systems

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching Page 1-16 PSTN PSTN ML A ML C DEF E ML B ML D PSTN PSTN Figure 1–6. Star Configuration: Five Systems Figure 1–6 again shows the star configuration we looked at earlier in this chapter.

  • Page 49: Software Defined Network (Sdn) Configuration

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Tandem Trunking and Tandem Switching Page 1-17 Software Defined Network (SDN) Configuration 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.
  • Page 50 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 51: Uniform Dial Plan

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Uniform Dial Plan Page 1-19 Uniform Dial Plan The private network benefits that we looked at earlier in this chapter are possible through the combination of core system features—primarily Automatic Route Selection (ARS), Remote Access, and PRI support—and two additional features designed specifically for private networks: the non-local dial plan, which is part of the Uniform Dial Plan (UDP).

  • Page 52: Uniform Dial Plans

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 53: Centralized Voice Messaging System

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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 In Release 6.1 and later, MERLIN LEGEND Communications Systems connected in a private network by tandem trunks may share a centralized voice and fax...
  • Page 54 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 55 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 56: Centralized Voice Mail With One Vms/Aa For Entire Network

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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”...
  • Page 57 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Introduction Centralized Voice Messaging System 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.

  • Page 58: Networked Voice Mail Systems

    DEFINITY system VMS/AA. Networking voice messaging systems is an alternative that provides the appearance to users that everyone is sharing a single VMS. Lucent Technologies messaging systems that support networking are Intuity AUDIX and Messaging 2000. Please see the messaging system documentation for more information about networking capabilities.

  • Page 59: Call-Handling Scenarios

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Page 2-1 Call-Handling Scenarios 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.

  • Page 60: Networking Guidelines

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines Page 2-2 Networking Guidelines 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.
  • Page 61 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines 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;...
  • Page 62 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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.

  • Page 63: Call-Handling Scenarios

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines 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.
  • Page 64 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines Page 2-6 Non-Local DEFINITY ECS or DEFINITY ProLogix Solutions Systems 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.
  • Page 65 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 66 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 67 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines 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;...
  • Page 68 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines Page 2-10 Programming Regular Remote Access 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.
  • Page 69 In Release 6.1 and later systems, the PRI Switch Type Test requests the system at the other end to verify that the correct PRI switch type is programmed. This test should be run only by Lucent Technologies technicians or authorized representatives.
  • Page 70 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines Page 2-12 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.
  • Page 71 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Networking Guidelines 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.

  • Page 72: Network Configuration Scenarios

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 73 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 74 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-16 Remote access planning for private network usage by people who are calling in either from outside the private network or from an extension that is non-local to their home system PRI dial-plan routed and DID calling across the private network UDP routing for centralized VMS/AA...

  • Page 75: Scenario 1: Overview

    PSTN ML A ML B Tandem PRI New York, NY Holmdel, NJ Facilities VMS/AA VMI Conversion Area Code 212 Area Code 732 Number: 7999 Switch ID 21 Switch ID 22 ————— Ext. 771 Integrated VMI Calling Group MLX-20L Home More Local Members: Menu Inspct...
  • Page 76 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 77 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 78 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-20 Non-Local Dial Plans and Facilities Planning 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.
  • Page 79 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 80: Udp Extension Ranges: Scenario

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-22 Table 2–1. UDP Extension Ranges: Scenario 1 System A Local Dial Plan: 3100–3299; System B Local Dial Plan: 6700–7199 3400–3499 Remote Access Code: 122 Remote Access Code: 889 Centralized VMS/AA: 771...
  • Page 81 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-23 System A Local Dial Plan: 3100–3299; System B Local Dial Plan: 6700–7199 3400–3499 Remote Access Code: 122 Remote Access Code: 889 Centralized VMS/AA: 771 Integrated VMI Calling Group for Routing Trunks: 8001-8080...

  • Page 82: Scenario 1: Facilities Planning, Calls Originating Within The Private Network And Going To The Pstn

    Table 2–2. Scenario 1: Facilities Planning, Calls Originating within the private network and Going to the PSTN 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 Switch Identifiers 22 for a system that is within 200 miles (System B)

  • Page 83: Scenario 1: Ars Routing Summary, Calls Originating Within The Private Network And Going To The Pstn

    Table 2–3. Scenario 1: ARS Routing Summary, Calls Originating within the private network and Going to the PSTN System A: New York, NY (Area Code: 212) System B: Holmdel, NJ (Area Code: 732) Dialed or Rec’d Dialed or Rec’d Digits Rte Pool Type Prep Digits...
  • Page 84 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 85: Outside Calls: Scenario

    Table 2–4. Outside Calls: Scenario 1 Originating or Receiving System Dialed Digits Local Routing Non-Local Routing ( &"!$$$ ! " System A: Ext. FRL: 0 Route 1: ARS Area Code Table routes to Route 1, System B: Remote access < tandem trunk pool, FRL 0, prepends 9 default FRL 3.

  • Page 86: Outside Calls: Scenario

    Table 2–4. Outside Calls: Scenario 1, Continued Originating or Receiving System Dialed Digits Local Routing Non-Local Routing $$$&! System A: Receives System A: PRI dial-plan routing deletes System B: First part of 2B data call outside dial-plan routed 555, checks local dial plan, then finds arrives at video system, Ext.
  • Page 87 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-29 Intersystem Calling This topic illustrates how different types of calls are made and received in Scenario 1, using the extension numbers and extension equipment types shown Figure 2–1.

  • Page 88: Intersystem Calling: Scenario

    Table 2–5. Intersystem Calling: Scenario 1 Type of Call Caller Caller Dials Recipient Recipient Sees... Non-local extension System A: Ext. 3212 System B Ext. 6777, MLX-10D Display: Number Non-local extension System B: Ext. 6988 System A Ext. 3212, MLX-20L Display: Both Non-local extension System A: Ext.

  • Page 89: Intersystem Calling: Scenario

    Table 2–5. Intersystem Calling: Scenario 1, Continued Type of Call Caller Caller Dials Recipient Recipient Sees... Transfer of outside GS/LS call to Outside to Transfer System B Ext. 6871, non-local extension System A: Ext. 3105 MLX-10D Display: Number Transfer of outside PRI-ANI call Outside to Transfer System B Ext.
  • Page 90 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-32 Scenario 2: Two Systems, Tandem Tie Facilities 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.

  • Page 91: Scenario 2: Company Floor Plans

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-33 System C Headquarters (Chicago) VMS Hub Chief VP Sales/ VP Product Chief Operating Financial Marketing Design Officer President Officer Equipment Supplies MIS/ Personnel...
  • Page 92 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-34 General Needs The company has several broad areas of concern: Connectivity Cost-effective calling Customer service Toll fraud and calling restrictions In addition, the company would like to provide these features to all or many employees: Easy dialing of non-local extensions and frequently called numbers...
  • Page 93 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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.

  • Page 94: Work Group Needs

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-36 Table 2–6. Work Group Needs Work Group Needs President and vice- Ability to meet frequently, face to face, without incurring travel costs presidents, W.
  • Page 95 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-37 Table 2–6. Work Group Needs, Continued Work Group Needs Order-Takers and Ability for small-order customers to access an automatic ordering Customer Service system in which they use their touch-tone phones to enter account Personnel...

  • Page 96: Individual Needs

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-38 Table 2–6. Work Group Needs, Continued Work Group Needs Order-Takers’ and Ability to observe and control the order agents’ calls (for example, to Customer Service know who is available) and immediately see whether too many callers Supervisor...
  • Page 97 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-39 Table 2–7. Individual Needs, Continued Staff Members Needs Operator/ Ability to page certain groups or all staff members Receptionist Answering of all calls, except those that go directly to agents or (Headquarters) executive secretaries, by an automated operator who directs calls according to the touch-tones entered by callers;...
  • Page 98 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 99 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 100 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 101 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 102 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 103: Scenario 2: Overview

    PSTN MERLIN LEGEND Reporter MERLIN LEGEND ML D VMI Conversion ML C Reporter Number: 6999 Palo Alto, CA ————— Chicago, IL T1 Tandem Tie Intuity Ext. 771 Area code 650 Area code 312 Facilities AUDIX Integrated Switch ID 01 Switch ID 02 VMI Calling Group Home Menu...
  • Page 104 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 105 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 106: Udp Extension Ranges: Scenario

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-48 Table 2–8. UDP Extension Ranges: Scenario 2 System D Local Dial Plan: 7340–7379; 7460- System C Local Dial Plan: 4630–4699; 7499;...

  • Page 107: Scenario 2: Facilities Planning, Calls Originating Within The Private Network And Going To The Pstn

    Table 2–9. Scenario 2: Facilities Planning, Calls Originating within the private network and Going to the PSTN 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 Switch 01 for a system more than 200 miles away...

  • Page 108: Scenario 2: Ars Routing Summary, Calls Originating Within The Private Network And Going To The Pstn

    Table 2–10. Scenario 2: ARS Routing Summary, Calls Originating within the private network and Going to the PSTN System C: Chicago, IL (Area Code: 312) System D: Palo Alto, CA (Area Code: 650) Dialed or Rec’d Dialed or Rec’d Digits Rte Pool Type Prep Digits...
  • Page 109 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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...

  • Page 110: Outside Calls: Scenario

    Table 2–11. Outside Calls: Scenario 2 Originating or Receiving System Dialed Digits Local Routing Non-Local Routing ( %$$$$ ! ' System C: Ext. FRL: 2 Route 1: ARS Area Code Table routes to Route 1, System D: Remote access FRL <...

  • Page 111: Outside Calls: Scenario

    Table 2–11. Outside Calls: Scenario 2, Continued Originating or Receiving System Dialed Digits Local Routing Non-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.
  • Page 112 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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 Figure 2–3 on page 2–45.

  • Page 113: Intersystem Calling: Scenario

    Table 2–12. Intersystem Calling: Scenario 2 Type of Call Caller Caller Dials Recipient Recipient Sees... &"#! UD@USFÃ Non-local extension System C: Ext. 4638 System D Ext. 7342, ® FRL=6 MLX-5D #%"' UD@USF Non-local extension System D, Ext. 7377 System C Ext. 4638, FRL=3 MLX-20L "!%Ã...

  • Page 114: Intersystem Calling: Scenario

    Table 2–12. Intersystem Calling: Scenario 2, Continued Type of Call Caller Caller Dials Recipient Recipient Sees... Transfer of outside PRI-ANI call Outside to Transfer System D: Call is sent to Not Applicable to centralized VMS/AA System D: Ext.7771 integrated VMI calling group 7771 (with VMI conversion number 6999).
  • Page 115 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-57 Scenario 3: Four Systems in a Series, Mixed Facilities Like Scenario 1, this example discusses the planning and call-handling for private networking features and routing.

  • Page 116: Scenario 3: Overview

    MLX-20L Home More VMI Conversion Menu Inspct Number: 6999 ————— Ext. 7771 Volume Message Feature Transfer HFAI Conf PQRS WXYZ Mute Drop OPER Integrated VMI Speaker Hold Ext. 2210 Calling Group Ext. 2252 MLX-10D Ext. 2233 Analog Display MLX-20L ML J VMS/AA Ext.
  • Page 117 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-59 Non-Local Dial Plans and Facilities Planning 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.
  • Page 118 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 119: Udp Extension Ranges: Scenario

    Table 2–13. UDP Extension Ranges: Scenario 3 System J Local Dial Plan: System K Local Dial Plan: System L Local Dial Plan: System M Local Dial Plan: 2210–2259 5540–5569; 5770–5799 6030–6049; 6240–6269 3250–3269; 3410–3449 Trunks: 8801-8880 Listed Directory Number Centralized VMS/AA: 7771 Integrated VMI calling (QCC queue): 8800 Trunks: 6801-6880...
  • Page 120 System J Local Dial Plan: System K Local Dial Plan: System L Local Dial Plan: System M Local Dial Plan: 2210–2259 5540–5569; 5770–5799 6030–6049; 6240–6269 3250–3269; 3410–3449 Trunks: 8801-8880 Listed Directory Number Centralized VMS/AA: 7771 Integrated VMI calling (QCC queue): 8800 Trunks: 6801-6880 group for routing to Integrated VMI calling...

  • Page 121: Scenario 3: Facilities Planning, Calls Originating Within The Private Network And Going To The Pstn

    Table 2–14. Scenario 3: Facilities Planning, Calls Originating within the private network and Going to the PSTN System J: Cambridge, System K: Boston, MA System L: Washington, System M: Raleigh, NC Component MA (Area Code: 617) (Area Code: 617) DC (Area Code: 202) (Area Code: 919) Not applicable for analog MERLIN LEGEND-PBX...
  • Page 122 Table 2–14. Scenario 3: Facilities Planning, Calls Originating within the private network and Going to the PSTN, Continued System J: Cambridge, System K: Boston, MA System L: Washington, System M: Raleigh, NC Component MA (Area Code: 617) (Area Code: 617) DC (Area Code: 202) (Area Code: 919) Not applicable because not...

  • Page 123: Scenario 3 Ars Routing Summary: Calls Originating Within The Network And Going To The Pstn: Systems J & K

    Table 2–15. Scenario 3 ARS Routing Summary: Calls Originating within the Network and Going to the PSTN: Systems J & K System J: Cambridge, MA (Area Code: 617) System K: Boston, MA (Area Code: 617) Dialed or Rec’d Dialed or Rec’d Digits Rte Pool Type Prep...

  • Page 124: Scenario 3 Ars Routing Summary: Calls Originating Within The Network And Going To The Pstn: Systems L & M

    Table 2–16. Scenario 3 ARS Routing Summary: Calls Originating within the Network and Going to the PSTN: Systems L & M System L: Washington, DC (Area Code: 202) System M: Raleigh, NC (Area Code: 919) Dialed or Rec’d Dialed or Rec’d Digits Rte Pool Type Prep...
  • Page 125 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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...

  • Page 126: Outside Calls: Scenario 3

    Table 2–17. Outside Calls: Scenario 3 Originating or Receiving System Dialed Digits Local Routing Non-Local Routing ($$$!!$' System J: Ext. FRL: 1 Route 1: ARS Local Exchange Table routes Route 1, System K: Call is routed here for a < to tandem trunk pool, FRL 0, prepends 9 lower cost local call.
  • Page 127 Table 2–17. Outside Calls: Scenario 3, Continued Originating or Receiving System Dialed Digits Local Routing Non-Local Routing $$$$&' Ã dialed twice Two outside dial-plan System L: Routes each call to PRI For each call System M PRI dial-plan routed 64-kbps PRI 2B tandem trunk pool 5335 via Pattern 5 and routing deletes 555, checks local dial <...
  • Page 128 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-70 Intersystem Calling This topic illustrates how different types of calls are made and received in Scenario 3, using the extension numbers and extension equipment types shown Figure 2–4 on page 2–58.

  • Page 129: Intersystem Calling: Scenario 3

    Table 2–18. Intersystem Calling: Scenario 3 Caller Routed Type of Call Caller Dials via... Recipient Recipient Sees... Non-local extension System K: System L System M Ext. 3254, Ext. 5564 All PRI MLX-10D, Name display Non-local extension System L: System K System J Ext.
  • Page 130 Table 2–18. Intersystem Calling: Scenario 3, Continued Caller Routed Type of Call Caller Dials via... Recipient Recipient Sees... Outside PRI-ANI dial-plan Outside to All PRI with System M: Call is sent to Not applicable routed call to local extension System M: ext 3254 PRI routing integrated VMI calling on System M.
  • Page 131 Table 2–18. Intersystem Calling: Scenario 3, Continued Caller Routed Type of Call Caller Dials via... Recipient Recipient Sees... System L Outside call Outside to Transfer System L: System L, ext 3254 not transferred to non-local centralized All PRI responding. After extension by centralized VMS/AA, timeout, call is sent to...
  • Page 132 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-74 Scenario 4: Four Systems in a Star, Mixed Facilities 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.

  • Page 133: Scenario 4: Overview

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-75 VMI Conversion VMI Conversion Number: 6999 Number: 6999 ————— ————— Ext. 7771 Ext. 7771 Integrated VMI Integrated VMI Calling Group Calling Group PSTN PSTN...
  • Page 134 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-76 Non-Local Dial Plans and Facilities Planning 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.
  • Page 135 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.
  • Page 136 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 137: Udp Extension Ranges: Scenario

    Table 2–19. UDP Extension Ranges: Scenario 4 System E Local Dial Plan: System F Local Dial Plan: System G Local Dial Plan: System H Local Dial Plan: 5400–5499; 5610–5669 2200–2259; 2400–2449 4530–4599; 4600–4601 1230–1299; 1450–1499 Centralized VMS/AA: 7771 Integrated VMI calling Group Integrated VMI calling Group Integrated VMI calling Group Trunks 5801-5880...
  • Page 138 Table 2–19. UDP Extension Ranges: Scenario 4, Continued System E Local Dial Plan: System F Local Dial Plan: System G Local Dial Plan: System H Local Dial Plan: 5400–5499; 5610–5669 2200–2259; 2400–2449 4530–4599; 4600–4601 1230–1299; 1450–1499 Centralized VMS/AA: 7771 Integrated VMI calling Group Integrated VMI calling Group Integrated VMI calling Group Trunks 5801-5880...
  • Page 139 Table 2–19. UDP Extension Ranges: Scenario 4, Continued System E Local Dial Plan: System F Local Dial Plan: System G Local Dial Plan: System H Local Dial Plan: 5400–5499; 5610–5669 2200–2259; 2400–2449 4530–4599; 4600–4601 1230–1299; 1450–1499 Centralized VMS/AA: 7771 Integrated VMI calling Group Integrated VMI calling Group Integrated VMI calling Group Trunks 5801-5880...

  • Page 140: Scenario 4: Facilities Planning, Calls Originating Within The Network And Going To The Pstn, Systems E And H

    Table 2–20. Scenario 4: Facilities Planning, Calls Originating within the Network and Going to the PSTN, Systems E and H Component System E: Baltimore, MD (Area Code: 410) System H: Reston, VA (Area Code: 703) MERLIN LEGEND-Ntwk MERLIN LEGEND-PBX DS1 Switch Type Switch Identifiers 22 for a system within 200 miles (System H) 21 for a system within 200 miles (System E)
  • Page 141 Table 2–20. Scenario 4: Facilities Planning, Calls Originating within the Network and Going to the PSTN: System E and H, Continued Component System E: Baltimore, MD (Area Code: 410) System H: Reston, VA (Area Code: 703) ARS Routing: For primary routes serving calls to area codes 509 and Routing specifies pools of tandem PRI facilities, which are Calls to Area Code 512, the FRL is 0.

  • Page 142: Scenario 4: Facilities Planning, Calls Originating Within The Network And Going To The Pstn, Systems F And G

    Table 2–21. Scenario 4: Facilities Planning, Calls Originating within the Network and Going to the PSTN, Systems F and G Component System F: Spokane, WA (Area Code: 509) System G: Austin, TX (Area Code: 512) MERLIN LEGEND-PBX Not applicable for tandem tie trunks DS1 Switch Type Switch Identifiers 01 for a system more than 200 miles away (System E)
  • Page 143 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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...

  • Page 144: Outside Calls: Scenario

    Table 2–22. Outside Calls: Scenario 4 Originating or Receiving System Dialed Digits Local Routing Non-Local Routing ($$$!!$' System H: Ext. FRL: 0 ARS Local Exchange Table routes to System E: ARS absorbs no digits, routes tandem trunk pool, FRL 0, prepends to PSTN pool.
  • Page 145 Table 2–22. Outside Calls: Scenario 4, Continued Originating or Receiving System Dialed Digits Local Routing Non-Local Routing $$$$#"' DID call arrives at System F DID receives 5438, checks System E: Voice call arrives at Ext. 5438, System F local dial plan, then finds number in non- PassageWay client, which does not local dial plan.
  • Page 146 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-88 Scenario 5: Large System Hub 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.

  • Page 147: Scenario 5: Overview

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-89 MLX-20L Home More Menu Inspct Message Volume Feature Transfer HFAI Conf PQRS WXYZ Ext. 1822 Mute Drop OPER Speaker Hold Ext.
  • Page 148 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-90 Non-Local Dial Plans and Facilities Planning 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.
  • Page 149 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 150: Udp Extension Ranges: Scenario

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-92 Table 2–23. UDP Extension Ranges: Scenario 5 System A Local Dial Plan: System O Local Dial Plan: System N Local Dial Plan: 54400–54499;...

  • Page 151: Scenario 5: Facilities Planning, Calls Originating Within The Private Network And Going To The Pstn

    Table 2–24. Scenario 5: Facilities Planning, Calls Originating within the Private Network and Going to the PSTN System A: Atlanta, GA System O: Atlanta, GA System N: Denver, CO Component (Area Code: 404) (Area Code: 404) (Area Code: 303) DS1 Switch Type Private Network MERLIN LEGEND-Ntwk MERLIN LEGEND-Ntwk...
  • Page 152 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios 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.

  • Page 153: Outside Calls: Scenario 5

    Table 2–25. Outside Calls: Scenario 5 Originating or Receiving System Dialed Digits Local Routing Non-Local Routing ( ""$$$"""" System O: Ext. FRL: 1 ARS Area Code Table routes to main pool, None FRL 2, call denied. ( ##$$$!!$' System N: Ext. FRL: 3 ARS Area Code Table routes to tandem System A: ARS Area Code Table routes <...
  • Page 154 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-96 Intersystem Calling Table 2–26, page 2-97 illustrates dialing and recipient screen displays for calling among extensions in Scenario 5. Note the following facts about intersystem calling in this scenario: The full 5-digit DEFINITY ECS or DEFINITY ProLogix Solutions extension numbers display at recipient extensions on the MERLIN LEGEND...

  • Page 155: Intersystem Calling: Scenario 5

    Table 2–26. Intersystem Calling: Scenario 5 Caller Type of Call Caller Dials Routed via... Recipient Recipient Sees... Non-local extension System O: System A System N Ext. 4502, Ext. 1674 All PRI MLX-20L, Name and number display Non-local extension System N: All PRI, digits System A: Telephone Depends upon...
  • Page 156 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Call-Handling Scenarios Network Configuration Scenarios Page 2-98...

  • Page 157: Feature Interactions

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Account Code Entry Page 3-1 Feature Interactions 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 .

  • Page 158: Allowed/Disallowed Lists

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Allowed/Disallowed Lists Page 3-2 Allowed/Disallowed Lists 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).

  • Page 159: Automatic Route Selection (Ars)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Automatic Route Selection (ARS) Page 3-3 Automatic Route Selection (ARS) 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.

  • Page 160: Barge-In

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 161: Caller Id

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Caller ID Page 3-5 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.

  • Page 162: Network Reference 555

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 163: Computer Telephony Integration (Cti) Link

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 164: Conference

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 165: Coverage

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Coverage Page 3-9 Coverage 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.

  • Page 166: Direct-Line Console (Dlc)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Direct-Line Console (DLC) Page 3-10 Direct-Line Console (DLC) 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.

  • Page 167: Display

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Display Page 3-11 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.

  • Page 168: Do Not Disturb

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.0 and later systems, Caller ID and ANI information is not conveyed across the private network and at MLX display telephones the trunk label only is displayed under the following conditions: The call is routed over T-1-emulated tie trunks or analog (E&M) tie trunks.

  • Page 169: Forward And Follow Me

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Forward and Follow Me Page 3-13 Forward and Follow Me 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.
  • Page 170 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Group Calling 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.

  • Page 171: Hands Free Answer On Intercom (Hfai)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 172: Hotline

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions HotLine Page 3-16 HotLine A HotLine extension must be on the local system. However, a HotLine telephone can dial a non-local extension number. Labeling 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.

  • Page 173: Music On Hold

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Music On Hold Page 3-17 Music On Hold 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.

  • Page 174: Park

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Park Page 3-18 Park Park zones must be in the local system. Calls cannot be parked at remote park zones. Personal Lines To avoid toll fraud, private networked trunks must not be assigned to extensions as personal lines.

  • Page 175: Primary Rate Interface (Pri) And T1

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Primary Rate Interface (PRI) and T1 Page 3-19 Primary Rate Interface (PRI) and T1 “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.

  • Page 176: Queued Call Console (Qcc)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Queued Call Console (QCC) Page 3-20 Queued Call Console (QCC) For Release 6.0 systems, an extension may not have its calls covered by a QCC on another system.

  • Page 177: Remote Access

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Remote Access Page 3-21 Remote Access “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.

  • Page 178: Service Observing

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 179: Station Message Detail Recording (Smdr)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Station Message Detail Recording (SMDR) Page 3-23 Station Message Detail Recording (SMDR) For 6.0 systems, all private network calls are reported according to SMDR Call Report programming for reporting non-UDP incoming and outgoing calls.

  • Page 180: Udp Calls Recorded At All Systems

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Station Message Detail Recording (SMDR) Page 3-24 Incoming DID call from the PSTN routed across the private network. System C System A System B System C System A System B PSTN...

  • Page 181: Speed Dial

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Speed Dial Page 3-25 Incoming DID call from the PSTN routed across the private network. System C System A System B System C System A System B PSTN PSTN...

  • Page 182: System Renumbering

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions System Renumbering Page 3-26 System Renumbering 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.

  • Page 183: Voice Announce To Busy

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 184 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Feature Interactions Voice Messaging Interface (VMI) 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).

  • Page 185: Security

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Page 4-1 Security 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,”...

  • Page 186: Overview

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Overview Page 4-2 Overview 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.

  • Page 187: Calling Restrictions And Security Feature Planning In Networks

    Table 4–1. Calling Restrictions and Security Feature Planning in Networks Restriction, Feature, or Factory Setting Setting Suspended? Description Personal Lines Not Applicable Private network trunks must never be assigned as personal lines or extensions. Applicable Pool buttons Not Applicable Users (including DSS users) must never be given Pool button access to pools Applicable of tandem trunks.
  • Page 188 Continued on next page Restriction, Feature, or Factory Setting Setting Suspended? Description Toll Restriction Despite toll restrictions, users can make calls to non-local extensions. Allowed and Disallowed Retain Disallowed List 7 and add to it as necessary. Non-local extension Disallowed Lists List 7 numbers can be added to the Disallowed Lists to prevent a user from calling a non-local extension.

  • Page 189: Facility Restriction Levels And Remote Access

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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. Ensure that barrier codes are required for incoming remote access calls received on PSTN dial-plan routed facilities and tandem facilities that route to the local system by dialing the Remote Access...
  • Page 190 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 191 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Facility Restriction Levels and Remote Access 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.
  • Page 192 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Facility Restriction Levels and Remote Access 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.

  • Page 193: Recommended Settings For Tie And Non-Tie Default Cor And Callback

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Facility Restriction Levels and Remote Access Page 4-9 Table 4–2. Recommended Settings for Tie and Non-Tie Default COR and Callback Recommended Setting Name Setting Description Barrier Code Requires barrier code entry for remote access calls on DID, Requirement PRI dial plan-routed, dedicated or shared remote access, or...

  • Page 194: Facility Restriction Levels Applied To Network Calls

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 195: Facility Restriction Levels

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Facility Restriction Levels and Remote Access Page 4-11 Table 4–3. Facility Restriction Levels Local Extension/Barrier Local ARS or UDP Route Code Default COR/FRL Call Allowed? 0 only 0, 1...
  • Page 196 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Security Facility Restriction Levels and Remote Access Page 4-12...

  • Page 197: Network Management

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Page 5-1 Network Management 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 .

  • Page 198: General Programming In Private Networks

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-2 General Programming in Private Networks This section outlines system features and programming options that may need adjustment or special planning when your system is included in a private network. This section includes the following topics: Pool Assignment Automatic Route Selection (ARS)
  • Page 199 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-3 Automatic Route Selection (ARS) 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...
  • Page 200 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 201 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 202 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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 The remote access Automatic Callback setting of on or off does not apply to private network calls.
  • Page 203 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 204: System Date And Time

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.) NOTE: If a DEFINITY ECS or DEFINITY ProLogix Solutions system is...
  • Page 205 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-9 Tie Trunks 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.
  • Page 206 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-10 Group Calling Enhancement 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.

  • Page 207: Cross-Network Display Information

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks 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.
  • Page 208 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-12 Centralized VMS/AA 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.
  • Page 209 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-13 Centralized Voice Messaging Programming Allowing the user to dial the same extension number to reach the centralized voice messaging system to retrieve messages regardless of location requires special programming that is described below: Select a calling group number to be used at the VMS hub systems and all remote systems sharing the centralized VMS/AA and renumber all...
  • Page 210 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management General Programming in Private Networks Page 5-14 Assign an FRL of 0. 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.

  • Page 211: Non-Local Dial Plan Numbering

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Non-Local Dial Plan Numbering Page 5-15 Centralized Automated Attendant Programming 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.
  • Page 212 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 213 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Non-Local Dial Plan Numbering 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.
  • Page 214 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Non-Local Dial Plan Numbering Page 5-18 Task List: Non-Local Dial Plan Numbering NOTE: Any local dial-plan changes should be made before you program the non- local dial plan.

  • Page 215: Switch Identifiers

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Switch Identifiers Page 5-19 Switch Identifiers 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.
  • Page 216 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 217 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Switch Identifiers Page 5-21 Programming Instructions To enter an identifier for one trunk: Console Procedures More Dial trunk Dial switch no. To enter an identifier for a block of trunks: Dial starting trunk in block Dial ending trunk in block...

  • Page 218: Tandem Pri Facilities

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Tandem PRI Facilities Page 5-22 Tandem PRI Facilities 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”...
  • Page 219 In Release 6.1 and later systems, the PRI Switch Type Test requests the system at the other end to respond with information about the PRI Switch Type specification. Lucent Technologies technicians or authorized representatives can run this test to determine the PRI Switch Type at the other end.
  • Page 220 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 221: Uniform Dial Plan Routing

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Uniform Dial Plan Routing Page 5-25 Uniform Dial Plan Routing This section includes programming procedures for assigning UDP routing. UDP routing is very similar to ARS, except that it is slightly simpler. UDP routing allows system users to reach non-local extensions at a remote DEFINITY ECS or DEFINITY ProLogix Solutions or MERLIN LEGEND Communications System that is networked to your system.

  • Page 222: Facility Restriction Levels

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Uniform Dial Plan Routing Page 5-26 UDP Routes 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.
  • Page 223 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 224 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Uniform Dial Plan Routing Page 5-28 NOTE: Do not use this procedure to overcome conflicts between local and non- local extension numbering. Such conflicts can result in numerous problems with system features and should be resolved by system renumbering of the affected systems.
  • Page 225 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 226 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Uniform Dial Plan Routing Page 5-30 Programming Instructions To specify routes: Console Procedures Dial pattern no. Dial route no. Dial pool dial-out code To assign FRLs to routes: Dial pattern no.

  • Page 227: Display Preferences For Intersystem Calls

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Display Preferences for Intersystem Calls Page 5-31 Display Preferences for Intersystem Calls 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. Non-local dial plan calls that arrive on private networked tie or T1 trunks are not affected;...
  • Page 228 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Network Management Display Preferences for Intersystem Calls Page 5-32...

  • Page 229: Troubleshooting

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Page 6-1 Troubleshooting 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.

  • Page 230: Troubleshooting Guidelines And Preparation

    However, some problems require the intervention of a Lucent Technologies technician. In the USA only, Lucent Technologies provides a toll-free customer Helpline (1 800 628-2888) 24 hours a day. You may want to...
  • Page 231 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Troubleshooting Guidelines and Preparation 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.

  • Page 232: Verifying Switch Identifiers

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Verifying Switch Identifiers Page 6-4 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.

  • Page 233: Call To A Non-Local Extension: Unexpected Busy Tone

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to a Non-Local Extension: Unexpected Busy Tone Page 6-5 Call to a Non-Local Extension: Unexpected Busy Tone This topic discusses unexpected busy tones that may be caused by system features.

  • Page 234: Call To Non-Local Extension Silence Or Fast Busy Tone

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone Page 6-6 Call to Non-Local Extension: Silence or Fast Busy Tone 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.
  • Page 235 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone 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.
  • Page 236 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone 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”...
  • Page 237 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to Non-Local Extension: Silence or Fast Busy Tone 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.
  • Page 238 — If the call is a data call, go to Possible Cause 8. — If the call is not a data call, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply. Possible Cause 8: The FRL for the default COR for tie trunks (T1-emulated voice or data, or analog) on the remote system may be blocking tandem calls.

  • Page 239: Call To Non-Local Extension: Warble Tone (Error Tone)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to Non-Local Extension: Warble Tone (Error Tone) Page 6-11 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.
  • Page 240 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Call to Non-Local Extension: Warble Tone (Error Tone) Page 6-12 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.

  • Page 241: Calls To Non-Local Extensions Unexpected Busy Tone

    COR FRL. The route FRL must be equal to or lower than the default COR value or the call is blocked. The factory setting is 3. If FRL settings are not the cause, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 242: Call To Non-Local Extension Reaches Wrong Extension

    However, conflicts can still arise due to digit prepending or absorption as a call is routed across the private network. If this is not the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 243: Call To Non-Local Extension: Message From Co

    UDP tables for proper digit manipulation. He or she can determine whether the routing problem is on that system. If this is not the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 244: Transfer Call To Non-Local Extension Does Not Return

    PSTN facilities, or if an operator is using a DSS programmed for transfer for automatic completion over PRI trunks, you have solved the problem. If the call is routed only over tandem PRI facilities, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 245: Conference: Cannot Add Call

    If this is not the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply. DID Calls Not Completed There are several reasons why Direct Inward Dialing (DID) calls across a private network may not complete, either due to busy facilities or to faulty programming.
  • Page 246 COR FRL. The route FRL must be equal to or lower than the default COR value or the call is blocked. The factory setting is 3. If FRL settings are not the cause, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 247: Ars Calls Are Blocked

    Disallowed List, see “Disallowed Lists” in Chapter 3 of System Programming . Check the ARS programming to verify that the remote machine’s ARS code is being prepended. If this does not solve the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 248: Callback Does Not Work

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Callback Does Not Work Page 6-20 Callback Does Not Work 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.
  • Page 249 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Network Call Transmission Level (Volume) Too Low or Too High Page 6-21 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 option on the System Programming menu and then choose...

  • Page 250: Mlx Displays: Network Call Display Problems

    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. Contact your Lucent Technologies representative or Local Authorized Dealer for instructions. If the problem is not solved with the above instructions, call the Lucent Technologies Helpline at 1 800 628-2888;...

  • Page 251: Passageway Call Display Problems

    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.

  • Page 252: Ars Calls Go To System Operator (Unassigned Extension)

    The problem is caused when one or more tandem trunks has no switch identifier (the factory setting). If this is not the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 253: Excessive Line Noise On Voice And Data Calls

    If the clock source is correct, ensure that the specified port is functioning properly and has an in-service facility connected to it. If this does not solve or explain the problem, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.

  • Page 254: Operator Hears Tones

    A selected tandem facility between the caller or called VMI extension is out of service. Check the error logs and if the error indicates an out of service condition, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.
  • Page 255 Check the error logs for out of service (such as 4c03, Pool Busy &/or OOS). Call your service provider if errors are present, and/or call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply If you’re not sure of the pattern number being used to route calls in your local system, see “Reviewing the Non-Local Dial Plan and Routing”...
  • Page 256 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting Calls From a Remote System Do Not Reach the Centralized Voice Messaging 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.

  • Page 257: Centralized Voice Messaging System Get The Wrong Message Or Go To Operator

    In Release 6.1 and later systems, the PRI Switch Type Test requests the system at the other end to respond with information about the system mode specification. Lucent Technologies technicians or authorized representatives can run this test to determine the mode of the system at the other end.

  • Page 258: No Message Waiting Light Update

    A selected tandem facility between the caller or called VMI extension is out of service. Check the error logs and if the error indicates an out of service condition, call the Lucent Technologies Helpline at 1 800 628-2888; consultation charges may apply.
  • Page 259 If there is an alarm on the CPU board and Message Waiting light updates not delivered is the only obvious problem, check the possible causes in this section before calling the Lucent Technologies helpline. Possible Cause 1: The UDP at the VMI hub system for voice messaging subscribers is programmed incorrectly.
  • Page 260 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Troubleshooting No Message Waiting Light Update 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.

  • Page 261: A Customer Support Information

    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.

  • Page 262: Canadian Department Of Communications (Doc Interference Information

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Customer Support Information Canadian Department of Communications (DOC) Interference Information Page A-2 Canadian Department of Communications (DOC) Interference Information 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.
  • Page 263 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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): ...

  • Page 264: Installation And Operational Procedures

    FCC. In the event repairs are needed on this equipment, contact your authorized Lucent Technologies dealer or, in the USA only, contact the National Service Assistance Center (NSAC) at 1 800 628-2888.

  • Page 265: Doc Notification And Repair Information

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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. Permissible exceptions are when: —...

  • Page 266: Ministère Des Communications Du Canada Et La Réparation

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 267 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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. AVERTISSEMENT: L’utilisateur ne doit pas tenter de faire ces raccordements lui- même;...
  • Page 268 PF: AS5USA-65646-PF-E REN: 1.5A MADE IN U.S.A. Use only Lucent Technologies manufactured MERLIN LEGEND circuit modules, carrier assemblies, and power units, as specified in WARNING: If equipment is used for the Installation Manual, in this product. There are no user out–of–building...

  • Page 269: Security Of Your System: Preventing Toll Fraud

    Lucent Technologies cannot be responsible for such charges and will not make any allowance or give any credit for charges that...

  • Page 270: Toll Fraud Prevention

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 271 . In any event, it is not advisable to give anyone access to network facilities or operators, or to dial a number at the request of the caller. Any time a call appears to be suspicious, call the Lucent Technologies BCS Fraud Intervention Center at 1 800 628-2888 (fraud intervention for System ®...
  • Page 272 Network Reference 555-661-150 August 1998 Customer Support Information Toll Fraud Prevention Page A-12 Customers should also take advantage of Lucent Technologies monitoring services and devices, such as the NetPROTECT family of fraud- ® detection services, CAS with HackerTracker , and CAT Terminal with Watchdog.
  • Page 273 1809, 1900, and 976 or 1(wildcard)976. In Release 3.1 and later systems, Disallowed List number 7 does not include 800 and 1800 and 411 and 1411, but Lucent Technologies recommends that you add them. Assign all voice mail port extensions to this Disallowed List. Lucent Technologies recommends assigning Disallowed List number 7.
  • Page 274 If Remote Call Forwarding is required, MERLIN LEGEND Communications System owners should coordinate with their Lucent Technologies Account Team or authorized dealer to verify the type of central office facility used for RCF.
  • Page 275 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.

  • Page 276: Other Security Hints

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 277 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 278 Change the access password regularly and issue it only to authorized personnel. Disconnect the maintenance port when not in use. (However, this eliminates Lucent Technologies’ 24-hour maintenance surveillance capability and may result in additional maintenance costs.) Create a communications system management policy concerning employee turnover and include these suggestions: —...
  • Page 279 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Customer Support Information Other Security Hints Page A-19 Choosing Passwords Passwords should be the maximum length allowed by the system. Passwords should be hard to guess and should not contain: All the same numbers (for example, 1111, 666666) Sequential characters (for example 123456) Numbers that can be associated with you or your business, such as your...

  • Page 280: Limited Warranty And Limitation Of Liability

    Warranty Date that your system is not in good working order, Lucent Technologies will without charge to you repair or replace, at its option, the system components that are not in good working order. Repair or replacement parts may be new or refurbished and will be provided on an exchange basis.

  • Page 281: Remote Administration And Maintenance

    Page A-21 Limitation of Liability Except as provided below, the liability of Lucent Technologies and its affiliates and suppliers for any claims, losses, damages, or expenses from any cause whatsoever (including acts or omissions of third parties), regardless of the form of action, whether in contract, tort, or otherwise, shall not exceed the lesser of: (1) the direct damages proven;...
  • Page 282 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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. —...

  • Page 283: Sample Report Pages

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Page B-1 Sample Reports 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.

  • Page 284: B Sample Reports

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Page B-2 Table B–1. Continued For... See... Extension Information Report B–22 Direct Group Calling Information Report B–24, B–25 Error Log Report B–26 Switch 56 Data Information Report B–27 Table B–2 lists all of the system reports and includes the print menu option used...
  • Page 285 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Page B-3 Table B–2. Continued Menu Option Report Name Description DS1 information Options (line, signal, and so on) assigned to T1 trunks or lines. PRI Information PRI trunks assigned to B-channel groups.
  • Page 286 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Page B-4 Table B–2. Continued Menu Option Report Name Description Extension Directory 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.
  • Page 287 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Page B-5 Table B–2. Continued Menu Option Report Name Description Non-Local Dial Plan Ranges of extension numbers for non-local dial plan extensions connected to a networked external switch;...

  • Page 288: Dial Plan Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Dial Plan Report Page B-6 Dial Plan Report Print Menu Option: Sections: Pools; Telephone Paging Zones; Direct Group Calling Group; Lines/Trunks; Stations DIAL PLAN FOR POOLS POOL.# POOL.# POOL.#...
  • Page 289 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Dial Plan Report Page B-7 Dial Plan Report—Continued DIAL PLAN FOR STATIONS STN #: OPERATR STN #: STN #: STN #: EXT 13 STN #: EXT 14 STN #: STN #:...
  • Page 290 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Dial Plan Report Page B-8 Dial Plan Report—Continued COMPLETE DIAL PLAN FOR STATIONS AND ADJUNCTS ID #: 4000 7300 ID #: 4001 7301 ID #: 4002 7302 ID #:...

  • Page 291: Non-Local Dial Plan Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Non-Local Dial Plan Report Page B-9 Non-Local Dial Plan Report Print Menu Option: (Release 6.0 and later systems only) Sections: Ranges; Patterns Range Ptn Dgt Range Ptn Dgt Range...

  • Page 292: Tie Trunk Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Tie Trunk Information Report Page B-10 Tie Trunk Information Report Print Menu Option: TIE TRUNK INFORMATION TRUNK Slot/Port : 14/ 1 TIE-PBX Direction: 2 Way E&M Signal: Type1S Dialtone : Remote...

  • Page 293: Did Trunk Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports DID Trunk Information Report Page B-11 DID Trunk Information Report Print Menu Option: TRUNK INFORMATION Trk SS/PP Blk DiscTime Type ExpDig DelDig AddDig Signal InvDest 841 13/ 1 500ms Wink...

  • Page 294: General Trunk Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports General Trunk Information Report Page B-12 General Trunk Information Report Print Menu Option: GENERAL TRUNK INFORMATION Trk SS/PP RemAccess Pool TlPrfx HldDisc Principal QCC Extern Prty Oper Switch 801 2/ 1...

  • Page 295: Ds1 Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports DS1 Information Report Page B-13 DS1 Information Report DS1 SLOT ATTRIBUTES Slot Type Format Supp Signal LineComp ClkSync Active B8ZS Rob Bit Prim Loop B8ZS Rob Bit None Local...

  • Page 296: Pri Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports PRI Information Report Page B-14 PRI Information Report Print Menu Option: Sections: Network Selection, Special Service, Call-by-Call and Dial Plan Routing Tables; PRI Information Slot Switch: DMS-100 Slot 11 Switch: Legend-PBX...
  • Page 297 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports PRI Information Report Page B-15 PRI Information Report—Continued BchnlGrp #: Slot: TestTelNum: NtwkServ: Incoming Routing: ElecTandNtwkRoute Directly to UDP Channel ID: 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 Line PhoneNumber...
  • Page 298 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports PRI Information Report Page B-16 PRI Information Report—Continued Network Selection Table Entry Number: Pattern to Match: 101**** 10*** Special Service Table Entry Number: Pattern to Match: Operator: none OP/P...
  • Page 299 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports PRI Information Report Page B-17 PRI Information Report—Continued Pattern Call Type: BOTH BOTH BOTH BOTH BOTH NtwkServ: DMS-Private DMS-Private DeleteDigits: 0 Entry Number: 5 Call Type: BOTH BOTH BOTH...

  • Page 300: Remote Access (Disa) Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Remote Access (DISA) Information Report Page B-18 Remote Access (DISA) Information Report Print Menu Option: Sections: General Options; System Default Class of Restrictions (Non-TIE); System Default Class of Restrictions (TIE); Barrier Code Administration GENERAL OPTIONS (ACCESS CODE 889) Barrier Code required for Non-TIE DISA lines...

  • Page 301: Disallowed Lists Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Disallowed Lists Report Page B-19 Disallowed Lists Report Print Menu Option: Sections: Lists 1 through 7 DISALLOWED LISTS List : Entry 0: ------------ Entry 1: ------------ Entry 2: ------------...

  • Page 302: Automatic Route Selection Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Automatic Route Selection Report Page B-20 Automatic Route Selection Report Print Menu Option: Sections: Tables AUTOMATIC ROUTE SELECTION ARS IS: ACTIVE ACCESS CODE: 9 TABLE 17: Default Toll Output Table Pool Absorb Other Digits...

  • Page 303: Extension Directory Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Extension Directory Report Page B-21 Extension Directory Report Print Menu Option: EXTENSION DIRECTORY Port Ext # Label F H R M V R A 2 Port Ext # Label...

  • Page 304: Extension Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Extension Information Report Page B-22 Extension Information Report Print Menu Option: plus extension number EXTENSION INFORMATION Extn SS/PP Type 1/ 1 MLX-20L + 1 DSS CTI Link Alarms: ACTIVE...
  • Page 305 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Extension Information Report Page B-23 Extension Information Report— Continued EXTENSION INFORMATION Extn SS/PP Type 1/ 1 MLX-20L + 1 DSS Button Blank Status None Button Blank Status None Button...

  • Page 306: Direct Group Calling Information Report (Local Members Only)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Direct Group Calling Information Report (Local Members Only) Page B-24 Direct Group Calling Information Report (Local Members Only) Print Menu Option: DIRECT GROUP CALLING INFORMATION Group # : 770 Group Type : IntegrtdVMI...

  • Page 307: Report (Single Non-Local Member)

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Direct Group Calling Information Report (Single Non-Local Member) Page B-25 Direct Group Calling Information Report (Single Non-Local Member) Print Menu Option: DIRECT GROUP CALLING INFORMATION Group # : 771 Group Type : IntegrtdVMI...

  • Page 308: Error Log Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Error Log Report Page B-26 Error Log Report Print Menu Option: ERROR LOG Last 30 System Errors: Message ss/pp First Last Code PRI SVC AUDIT TIMEOUT 00/00 01/08 00:00:53 7001...

  • Page 309: Switch 56 Data Information Report

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Switch 56 Data Information Report Page B-27 Switch 56 Data Information Report Print Menu Option: Dial Plan Routing for Network Service Expected Digits: Digits to Delete: 0 Digits to Add: ss/pp Dirction...
  • Page 310 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Sample Reports Switch 56 Data Information Report Page B-28...

  • Page 311: C Voice/Fax Messaging Systems

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Voice/Fax Messaging Systems Page C-1 Voice/Fax Messaging Systems 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.0 Version 11 or later software must be used when the customer’s configuration includes an automated attendant that will be used to route calls across a private network.

  • Page 312: Supported System Considerations

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Voice/Fax Messaging Systems Supported System Considerations Page C-2 Supported System Considerations 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.
  • Page 313 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Voice/Fax Messaging Systems Supported System Considerations Page C-3 Messaging 2000 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.

  • Page 314: Fax Messaging In A Centralized Voice Mail Configuration

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Voice/Fax Messaging Systems Fax Messaging in a Centralized Voice Mail Configuration Page C-4 Fax Messaging in a Centralized Voice Mail Configuration Both the Messaging 2000 and Intuity AUDIX systems have fax messaging capabilities.

  • Page 315: System Requirements For Touch-Tone Receivers

    MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Page D-1 Touch-Tone Receiver Requirements This appendix includes information to aid in determining Touch-Tone Receiver requirements for private network systems. System Requirements for Touch-Tone Receivers A voice messaging system requires a certain number of TTRs in addition to any...
  • Page 316 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Page D-2 Table D–1. TTRs Required by VMS/AA Number of VMS Ports Number of TTRs Required *If a 12-port MERLIN LEGEND Enhanced Service Center is used, 8 TTRs are required. Table D–2 estimates the total number of TTRs required in the system, based on call volume and whether the system uses account codes.
  • Page 317 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Page D-3 Table D–2. System Requirement for TTRs TTRs Required Calls/Hour No Account Codes Used Account Codes Used Table D–3 shows the TTRs required for primary delay announcement devices.
  • Page 318 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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. TTRs Required for Secondary Delay Announcement Devices When Using Prompt-Based Overflow Number of Devices Number of TTRs Required...
  • Page 319 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 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.
  • Page 320 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Touch-Tone Receiver Requirements System Requirements for Touch-Tone Receivers Page D-6...
  • Page 321 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-1 Glossary Italics The use of italics in the glossary denotes multiple usage of the italicized text throughout the glossary. Numerics Digital information carried by two B-channels for better 2B data performance and quality;...
  • Page 322 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-2 (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;...
  • Page 323 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-3 IS II/III , MERLIN LEGEND MAIL , and Lucent Technologies Automated Attendant Attendant application that automatically answers incoming calls with a recorded announcement and directs callers to a department, an extension, or the system operator.
  • Page 324 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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 . B-channel (Bearer-channel) 64- or 56-kbps channel that carries a variety of digital information streams, such as voice at...
  • Page 325 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-5 (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) Multiconductor electrical path used to transfer information...
  • Page 326 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-6 centralized Programming of features on individual telephones; telephone performed at a central location by the system manager. programming See also system programming and extension programming.
  • Page 327 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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.
  • Page 328 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-8 (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.
  • Page 329 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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 The imprinted feature buttons on a telephone: Conf or buttons Conference, Drop, Feature, HFAI (Hands Free Answer on Intercom), Hold, Message, Mute or Microphone, Recall,...
  • Page 330 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-10 See DS1 . Digital Signal 1 digital subscriber See DSL . line digital switch See DSE . element digital Mode of transmission in which the information to be transmission transmitted is first converted to digital form and then transmitted as a serial stream of pulses.
  • Page 331 (193 bits) in a 24-frame extended superframe. (Electronic Switching System) Class of central office ( CO ) switching systems developed by Lucent Technologies in which the control functions are performed principally by electronic data processors operating under the direction of a stored program.
  • Page 332 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-12 ExpressRoute Data communications device that allows connection 1000 between an RS-232 DTE device and the control unit using MLX extension jacks on the 008 MLX or 408 GS/LS-MLX module.
  • Page 333 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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.
  • Page 334 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-14 group A system application that allows face-to-face, videoconferencing simultaneous video and voice communications between system groups and requires high-speed data transmission facilities. See also desktop videoconferencing system. Hands Free See HFAI .
  • Page 335 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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.
  • Page 336 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-16 ISDN terminal A type of data station that includes an ISDN terminal adapter data adapter as its DCE. It may also include an MLX telephone station for simultaneous voice and data (ISDN terminal adapter data-only station).
  • Page 337 (T/R) extension jacks and automatically answers Attendant incoming calls with a recorded announcement; directs calls in response to touch tones. Magic on Hold A Lucent Technologies Music On Hold enhancement that promotes a company’s products or services. Mbps (megabits per second) Megacom The AT&T tariffed digital WATS offering for outward calling.
  • Page 338 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-18 (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.
  • Page 339 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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;...
  • Page 340 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-20 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.
  • Page 341 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-21 out-of-band Signaling that uses the same path as voice-frequency signaling 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...
  • Page 342 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-22 power supply Device that directs electricity to modules and telephones on module the system. One power supply module is needed for each carrier, and an auxiliary power unit is added if needed. (Primary Rate Interface) Standard interface that specifies the protocol used between two or more communications systems.
  • Page 343 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-23 (Queued Call Console) MLX-20L telephone used by a system operator in Hybrid/PBX mode only. Used to answer outside calls (directed to a system operator position) and inside calls, direct inside and outside calls to an extension or an outside telephone number, serve as a message center, make outside calls for users with outward calling...
  • Page 344 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-24 (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.
  • Page 345 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-25 A private network arrangement where either three or more star configuration communications systems are connected with one system acting as the hub system . See also series configuration . station See extension .
  • Page 346 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-26 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.
  • Page 347 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 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 .
  • Page 348 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Glossary Page GL-28 (uninterruptible power supply) Device that connects to the system to provide 117 VAC to the equipment when the commercial power source fails. (alternating-current voltage) (direct-current voltage) (voice messaging interface) An enhanced tip/ring port.
  • Page 349 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-1 Index Numerics 008 OPT modules 012 T/R modules touch-tone receivers (TTRs) 016 T/R modules touch-tone receivers (TTRs) 100D module clock source 6-25 2B data troubleshooting 6-25 400 GS/LS modules...
  • Page 350 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-2 Basic Rate Interface (BRI) clock source B-channels 5-23 Benefits improved efficiency service cost savings toll saving Bipolar 8 zero substitution (B8ZS) line coding 5-22 Busy tone troubleshooting 6-11...
  • Page 351 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-3 Considerations for voice messaging Intuity AUDIX MERLIN LEGEND Mail Messaging 2000 Copy Telephone Number to Send setting 5-24 Coverage feature interactions troubleshooting 6-13 CTI link, see Computer Telephony Integration (CTI) link D4 framing 5-22 D-channels...
  • Page 352 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-4 Efficiency Error Log Report B-26 Extended Station Status feature interaction 3-12 Extended superframe (ESF) format 5-22 Extension Directory Report B-21 Extension Information Report B-22 Extension ranges, see Non-local Uniform Dial Plan (UDP) Extension Status security...
  • Page 353 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-5 Implementation centralized voice messaging system 1-23 Interexchange (IXC) calls Intersystem calling call reaches wrong extension 6-14 display preference programming 5-31 feature interactions 3-28 scenario 2-29 2-54 2-70...
  • Page 354 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-6 Network configuration introduction sample scenarios 2-14 Network planning scenario 2-44 Network service 5-23 Networking benefits Networking concepts introduction Networking guidelines scenarios Networking voice messaging systems Centralized voice messaging system 1-26 Night Service...
  • Page 355 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-7 Pickup feature interactions 3-18 Pools feature interactions 3-18 security Power failure 6-26 6-30 PRI Information Report B-14 Primary Rate Interface (PRI) dial-plan routing 6-24 feature interactions 3-19 programming...
  • Page 356 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-8 Report Access to Disallowed List B-19 Automatic Route Selection B-20 Dial Plan DID Trunk Information B-11 Direct Group Calling Information (Local Members Only) B-24 (Single Non-Local Member) B-25 Disallowed Lists...
  • Page 357 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-9 Security Allowed/Disallowed Lists callback calling restrictions Extension Status Night Service overview Personal Lines planning Pools Remote Access routing outside calls scenarios 2-12 transfer, trunk-to-trunk trunk-to-trunk transfer Series configuration illustration...
  • Page 358 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-10 Tandem PRI trunks ordering circuit for 5-22 pools 5-26 programming 5-22 troubleshooting 6-10 6-28 voice and/or data service 5-29 Tandem switching definition introduction Tandem tie trunks programming troubleshooting 6-26...
  • Page 359 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-11 Troubleshooting, (continued) silence 6-26 6-29 6-30 Station Message Detail Recording (SMDR) 6-25 switch identifiers 6-19 6-20 6-29 switch type 6-10 6-28 tandem PRI trunks 6-10 6-28 tandem tie trunks...
  • Page 360 MERLIN LEGEND Communications System Release 6.1 Issue 1 Network Reference 555-661-150 August 1998 Index Page IN-12...

This manual is also suitable for:

Merlin legend

Table of Contents