MITEL 5000 Reference Manual
Part Number 580.8007 Mitel 5000 Reference Manual Issue 3.
Notice This manual is released by Mitel Networks Corporation as a guide for certified service personnel. It provides information necessary to properly configure, maintain, and operate the product. The contents of this document reflect current company standards and are subject to revision or change without notice. Some features or applications mentioned may require a future release and are not available in this release. Future product features are subject to availability and cost.
FCC Regulations FCC Regulations Important NOTICE The telephone instruments specifically designed for this system have hearing aid-compatible handsets that are in compliance with section 68.316 of the FCC Rules. For a Class A digital device or peripheral (Model 8690 Endpoint): This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules.
Safety Regulations Safety Regulations Important Safety Instructions NOTICE NRTL is a designation granted by the U.S. Occupational Health and Safety Administration (OSHA) to laboratories which have been accredited to certify products to U.S. Standards. Before installation, check the local electrical codes for important information concerning the installation of telephone and electronic equipment. The following safety information is reprinted from UL 1459.
Safety Regulations • Unplug this product from the wall outlet and refer servicing to qualified service personnel under the following conditions: o When the power supply cord or plug is damaged or frayed. o If liquid has been spilled into the product. o If the product has been exposed to rain or water. o If the product does not operate normally by following the operating instructions.
Limited Warranty Limited Warranty Mitel warrants that its products will, if delivered to the end-user in undamaged condition, be free from defects in material and workmanship under normal use and service for the period set forth on the current warranty periods as published in the US Price List from time to time and substantially in conformance with the documentation (functional and operating specifications) that Mitel publishes regarding same (end-user reference and operating manuals and guides relating to
Limited Warranty NOTICE The above express limited warranty is in lieu of all other warranties, express or implied from Mitel Networks Corporation or Inter-Tel, Inc., and there are no other warranties which extend beyond the face of this warranty. All other warranties whatsoever, including the implied warranty of merchant ability and the implied warranty of fitness for a particular purpose relating to use or performance of the product, including its parts, are hereby excluded and disclaimed.
Secure Socket Layer Secure Socket Layer Copyright (C) 1995-1998 Eric Young (eay@cryptsoft.com) All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape®’s SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc.
Network Security Statement Network Security Statement Although no telecommunications system or data network is entirely secure, as long as the appropriate security measures are put in place and properly maintained by both the customer and the installing company, the system architecture and its associated server-based applications are substantially secure against unauthorized access to the customer's data network via the telecommunications system.
Contents Contents Tables xxi Figures xxv Chapter 1: New Features 1-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 New Features and System Changes Described in This Book . . . . . . . . . . . . . . . . . . . . . . . . .1-2 New Features for Hardware and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Mitel 5000 Version 3.0 New Features . . . . . . . . .
Contents UPS Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9 Base Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9 General Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9 Power Failure Bypass Capabilities . . . . . . . . . . . . . . . . . . . . . .
Contents Record Keeping and Maintenance Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31 Call Cost Accounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-31 Station Message Detail Recording (SMDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-33 Customized System Programming Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Trunk Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6 Answer Feature Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7 Caller ID, DNIS, and ANI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-7 Day and Night Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Automatic Call Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-7 Call Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8 Call Logging Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-8 Call Logging Displays on a Six-Line Display Endpoint . . . . . . . . . . . .
Contents Hunt Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-29 Hunt Group Call Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30 Hunt Group Call Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31 Hunt Group Timers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Record-A-Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-64 Redial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-65 Redirect Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-66 Reminder Messages . . . . . . . . . . . . . . . . . . .
Contents Voice Processing System Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10 VPIM Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11 TCP/IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-11 Network Operation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Chapter 8: Diagnostics Features 8-1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5 Audio Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6 Audio Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6 Audio Direction . . . . . . . .
Contents VoIP DSP Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-43 IP Device Resource Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-44 Allocated VoIP DSPs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-45 Dump VoIP DSP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents Endpoint Physical Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-36 DSS/BLF Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-36 Speakerphones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-37 LCD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Tables Table 2-1 Time Slots for DEIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-5 Table 2-2 Expanded DEI Capacity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 Table 3-1 Pre-programmed Dial Rules Table 3-2 Caller ID Line Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table 7-4 Example Notification Cascade Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-36 Table 8-1 Audio Problems and Assigned Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6 Table 8-2 Loop Loss Measurement Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-12 Table 8-3 Dual T1/E1/PRI Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tables Table 9-29 IP Endpoint Web Client Field Names—Trace Settings . . . . . . . . . . . . . . . . . . . . . . . . .9-77 Table 9-30 Node Status Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-79 Table 9-31 Example of Exporting an Extension from One Node to Another . . . . . . . . . . . . . . . . . .9-80 Mitel ® 5000 Reference Manual – Issue 3.
Figures Figures Figure 3-1 Station Level Caller ID Forwarding Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-20 Figure 3-2 Voice Mail Level Caller ID Forwarding Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21 Figure 3-3 SIP Voice Mail Level Caller ID Forwarding Flowchart . . . . . . . . . . . . . . . . . . . . . . . . . .3-22 Figure 3-4 Remote Configuration Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Figures Figure 8-23 D-Channel Diagnostics Screen for T1M-2 Module Diagnostics. . . . . . . . . . . . . . . . . . .8-68 Figure 8-24 D-Channel Diagnostics Display Screen for T1M-2 Module Diagnostics . . . . . . . . . . . .8-69 Figure 8-25 Loopback Screen for T1M-2 Module Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-70 Figure 8-26 Echo Canceller Selection Screen for T1M-2 Module Diagnostics . . . . . . . . . . . . . . . . .
Figures Figure 8-59 E&M Timer Information Screen for T1M Module Diagnostics . . . . . . . . . . . . . . . . . . .8-105 Figure 8-60 Loop-Start/Ground-Start Timer Information Screen for T1M Module Diagnostics. . . .8-106 Figure 8-61 OPX Timer Information Screen for T1M Module Diagnostics . . . . . . . . . . . . . . . . . . .8-107 Figure 8-62 Miscellaneous Timer Information Screen for T1M Module Diagnostics. . . . . . . . . . . .8-108 Figure 8-63 Main Screen for BRM-S Module Diagnostics . . . . . . .
Chapter 1: New Features New Features Chapter 1: New Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 New Features and System Changes Described in This Book . . . . . . . . . . . . . . . . . . . . . . . . .1-2 New Features for Hardware and Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Mitel 5000 Version 3.0 New Features . . . . . . . . . . . . . . . .
Chapter 1: New Features Introduction Introduction NOTE The Inter-Tel 5000 system has been rebranded as the Mitel 5000 system. Over time, most or all of the supporting materials related to this product line will also be rebranded to reflect this name change. This chapter lists general new features related to the Mitel 5000 platform. For information about new features related to system hardware, licensing, or upgrades, refer to the Mitel 5000 Installation and Maintenance Manual, part number 580.8000.
Chapter 1: New Features Mitel 5000 Version 3.0 New Features Mitel 5000 Version 3.0 New Features NOTE Throughout the book, version 3.0 new features or options are indicated by change bars, like the one shown in the margin to the left of this text.
Chapter 1: New Features Mitel NuPoint Messenger Mitel NuPoint Messenger Mitel 5000 systems now support NuPoint Messenger, an external voice processing system that resides on the Mitel Application Suite® (MAS) server and uses Session Initiation Protocol (SIP) to communicate with the Mitel 5000 system. Mitel 5000 systems support NuPoint Messenger as the system voice processing application.
Chapter 1: New Features New Alarms New Alarms There are new alarms for v3.0. For more information, refer to the Message Print Diagnostics Manual, part number 550.8018. New Features in Administrative Web Session (AWS) The Administrative Web Session (AWS) pages include a variety of changes for v3.0. Some changes include new pages and information to support SIP peers and file-based Music-OnHold. The AWS pages provide statistical information for SIP peers and provide information about active SIP peer calls.
Chapter 1: New Features New Features in Administrative Web Session (AWS) • SIP Error Statistics o Total Error Count: The total number of errors including parse errors, transmission errors, invalid destination errors, SIP route errors, invalid state errors and SIP timer errors. o Parse Error Count: The number of errors encountered while parsing incoming SIP messages. o Transmission Error Count: The number of errors while transmitting SIP messages to peers.
Chapter 1: New Features New Features in Administrative Web Session (AWS) SIP Peer Diagnostics Page The SIP Peer Diagnostics page is new to v3.0. To locate the SIP Peer Diagnostics page, click SIP Peer Diagnostics from the IP Resource Info navigation tab. This page is available for all Mitel 5000 systems. For a Mitel CS-5600 configuration, this page is available on the Processing Server (PS-1) AWS. This page provides statistical information for a specific SIP peer, such as NuPoint Messenger.
Chapter 1: New Features New Features in Administrative Web Session (AWS) MOH Files Page To locate the MOH Files page, click MOH Files from the System Management tab. This page is available for Mitel 5000 systems. For the CS-5600, you can access the Base Server AWS to find information about this feature. From this page you can upload, download, and delete music files for Music-On-Hold.
Chapter 1: New Features New Features in Administrative Web Session (AWS) Modified AWS Pages The following pages have been modified for various reasons.
Chapter 1: New Features New Features in Administrative Web Session (AWS) Log Files Page The Log Files page now includes diagnostic log files for SIP Peers: CP SIP and CP History. The CP SIP log file includes SIP message and SIP peer information. The CP History log file includes SIP peer message information depending on the SIP View option (see “Log Files Page” on page 8-35). The Log Files page also includes Database Change Logs and System Health Report Logs.
Chapter 2: System Overview System Overview Chapter 2: System Overview Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 Operational Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2: System Overview Introduction Introduction This chapter provides a Mitel 5000 system overview, which includes operational, hardware, and software requirements. Operational Requirements To operate to its designed capability, the Mitel 5000 platform requires compliance with particular hardware, software, networking, licensing, and data storage requirements, as described in this section.
Chapter 2: System Overview IP Server and Digital Hardware Features Mitel Memory Card NOTICE The Mitel 5000 v3.0 release requires a minimum 512MB compact flash-type memory card. If this system is currently using a 256MB compact flash-type memory card, upgrade the card to either 512MB (part number 841.0274) or 1024MB (part number 841.0273) before upgrading the system to v3.0. The Mitel 5000 Base Server requires the specific compact flash-type memory card listed on the Mitel Parts List.
Chapter 2: System Overview IP Server and Digital Hardware Features Mitel CS-5600 Processing Server (PS-1) The Processing Server (PS-1) is a Linux server that hosts the Call Processing (CP) application and Basic Voice Mail (BVM) on the Mitel CS-5600 platform. The PS-1 increases processing capability to support additional system capacity and application loading. When connected, the PS-1 functions as the primary server and controls the Base Server.
Chapter 2: System Overview Digital Expansion Interface Digital Expansion Interface The Mitel 5000 platform can be expanded to support digital endpoints by installing one or two Digital Expansion Interface (DEI) units and Digital Endpoint Modules (DEM-16) to the Mitel 5000 Base Server. Each DEI unit and its associated hardware and software provides digital capability. The status of whether a Mitel 5000 platform is Equipped or Not Equipped with one or two DEIs appears on the Administrative Web Session (AWS).
Chapter 2: System Overview Digital Expansion Interface Table 2-2 shows the maximum number of IP endpoints depending on the system type and the number of licensed DEIs. Hardware requirements for the additional DEIs include: • The additional third or fourth DEI chassis. • Additional expansion modules (DEMs or SLM-8s) for the new DEIs. • Additional cabling (for example AIC, power, endpoint cables). Table 2-2.
Chapter 2: System Overview Modules Modules The Mitel 5000 platform can be equipped with a variety of modular circuits, or modules, to provide central processing, trunking, and endpoint functionality. Processor Module The Processor Module (PM-1) is the processor built-in to the Mitel 5000 Base Server. The PM-1 provides 32 IP resources for system operation. In a stand-alone mode, the PM-1 provides central processing for the Mitel CS-5200 system.
Chapter 2: System Overview Modules Digital Endpoint Module Each DEM-16 provides 16 circuits for connecting digital devices to the system. For more information about supported devices, see “Digital Endpoints” on page 9-25. Each DEM-16 is also equipped with a single Digital Signal Processor (DSP) to provide the following module and/or system resources: • Shared speakerphones: For Axxess® and Eclipse® Basic, Standard and Associate Display, and Models 8500, 8520, and 8560 endpoints.
Chapter 2: System Overview UPS Monitoring SLM-8 The eight-port Single Line Module (SLM-8), part no. 580.2101, allows the addition of up to 48 single line endpoints to a Mitel 5000 platform. A SLM-8 module may be inserted into any of the three bays of a Digital Expansion Interface (DEI) chassis. Each SLM-8 module supports up to eight single line endpoints. The Mitel 5000 Auto Equip feature supports installation of SLM-8 modules.
Chapter 2: System Overview Types of Software Features Types of Software Features This section summarizes Mitel 5000 software features—standard features that come with every system and software license features that are available at an additional cost or require additional licensing.
Chapter 2: System Overview Types of Software Features Software License Features The following features require a software license. For license part numbers, refer to the Mitel 5000 Installation and Maintenance Manual, part number 580.8000. • Category A, B, C, and D Endpoints: These licenses determine the number of multiprotocol and multimedia, multi-protocol touch screen endpoints that can operate on the system.
Chapter 2: System Overview Types of Software Features • System IP Endpoint Capacity: This feature determines the maximum capacity for IP endpoints on the system (5200 - 75, 5400 -175, 5600 -250). If you do not have the IP Endpoints Enabled license, the System IP Endpoint Capacity corresponds to the number of Enable IP Endpoint Units license in the license generator.
Chapter 3: System Features System Features Chapter 3: System Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Attendant Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-2 Attendant Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 3: System Features Introduction Introduction This chapter provides information for Mitel 5000 system-wide features. For voice processing features, see “Voice Processing Features” on page 7-1.
Chapter 3: System Features Attendant Features Network and Local Primary Attendants One attendant can be designated as the primary attendant who can receive unsupervised outside call recalls, hunt group recalls, and calls that cannot be matched to patterns in call routing tables. When installed in a network, a telecommunications system can support two types of primary attendants: • Node Attendants: Each node can support a primary attendant.
Chapter 3: System Features Automatic Route Selection Automatic Route Selection Automatice Route Selection (ARS) is a money-saving feature that allows the system to be programmed to select the least expensive route for placing outgoing calls. It can be used for placing outgoing calls and transferring or forwarding calls to outside telephone numbers. Endpoints can be restricted to using only ARS for placing outgoing calls.
Chapter 3: System Features Automatic Route Selection Table 3-1. Pre-programmed Dial Rules (Continued) Dial Rule Name Description 5 Echo Account Code Causes the system to dial the account code that is associated with the call, when the account code is available. The account code can be entered using any of the account code types, including All Calls Following, so long as the system receives the code before the end of dialing.
Chapter 3: System Features Automatic Route Selection When ARS is used, the endpoint user hears dial tone when the feature code is entered (manually or automatically using a CALL button, the ARS button, or the OUTGOING button). The user then dials the number and hears silence until the trunk is seized and dialing is completed. (The user will not hear the digits being dialed.) The call appears under an available CALL button or trunk button.
Chapter 3: System Features Automatic Route Selection ARS on a Network Each node has ARS programming. All trunk groups and nodes in a facility group must reside on the same node as the facility group. Using ARS is the only way a user can access trunks on other nodes. If the system routes an outgoing call to another node using an intermediary node, the intermediary node ARS cannot use the nodes in its facility group to move the outgoing call to another node.
Chapter 3: System Features Automatic Route Selection Attendant Recall When a call is placed on hold or is transferred from one endpoint to another, the Hold timer and the Transfer timer limit the amount of time the call may remain unattended.
Chapter 3: System Features Automatic Daylight Saving Time Adjustment Automatic Daylight Saving Time Adjustment The system automatically adjusts the time whenever Daylight Saving Time (DST) [British Summer Time in Europe] is in effect. The system time is also modified when DST ends. If disabled, the system does not recognize DST. In the default state, the DST flag is disabled.
Chapter 3: System Features Caller ID Forwarding Caller ID Forwarding Caller ID forwarding allows Call Processing (CP) to send Caller ID information from any incoming services to the public or private network using Primary Rate Interface (PRI) or Basic Rate Interface (BRI) Integrated Services Digital Network (ISDN) circuits. In the European market Caller ID is known as Calling Line Identification [CLID].
Chapter 3: System Features Caller ID Forwarding o All System and Manual Forward types apply to this feature. o This flag applies to both local and remote node calls. – When set to No, the system refers to the endpoint Calling Party Number or Calling Party Name field in System\Devices and Feature Codes\Endpoints\Local\. When the endpoint’s Calling Party Number or Calling Party Name field is programmed with a number or name, the programmed information is sent.
Chapter 3: System Features Caller ID Forwarding • Wait for ISDN Caller ID Information: This timer is used to control the amount of time the system waits for the incoming ISDN Facility message that contains the caller ID name before routing the call to the ring-in destination. This timer only applies to incoming ISDN calls that use Facility messages instead of Display messages for providing caller ID name. The default value of this timer is 0 seconds, which is no wait delay.
Chapter 3: System Features Caller ID Forwarding Caller ID for Line Type Based on the caller ID settings, the following calls are supported with the processing of the Caller ID number or name. Table 3-2.
Chapter 3: System Features Caller ID Forwarding Network Considerations Keep the following considerations in mind for networked systems: • An intercom call that routes between nodes then out through an ISDN line that is using a Display message does not send the endpoint’s user name for the caller ID name, but sends the endpoint’s calling party number instead.
Chapter 3: System Features Caller ID Forwarding Scenario #2: An extension transfers an inbound or outbound call to an outside number or to an extension that is forwarded to an outside number. Table 3-4.
Chapter 3: System Features Caller ID Forwarding Scenario #3: A Voice Mail application transfers an inbound call to an extension that is forwarded to an outside number. Table 3-5.
Chapter 3: System Features Caller ID Forwarding Scenario #4: Inbound call is immediately routed to an outside number using Single Ring-in Destination, Station Forwarding, and OAI Deflect. Table 3-6.
Chapter 3: System Features Caller ID Forwarding Scenario #5: An extension calls another extension that is routed to an outside number through endpoint forward, OAI, or Send to Destination. Same Node or remote Node intercom calls are processed the same. Table 3-7.
Chapter 3: System Features Caller ID Forwarding Call Processing Forwarding Priorities The Call Processing forwarding priorities are designed to provide maximum flexibility without burdening the calls that do not require Caller ID. If the Emergency Calling Party Number is configured, Call Processing uses the Emergency Calling Party Number as the outgoing ISDN Caller ID [CLID].
Chapter 3: System Features Caller ID Forwarding Figure 3-1.
Chapter 3: System Features Caller ID Forwarding Figure 3-2.
Chapter 3: System Features Caller ID Forwarding Figure 3-3.
Chapter 3: System Features Extension Lists Extension Lists An extension list is a group of intercom numbers or trunk numbers located on a single node. Off-node devices cannot be included in extension lists. These lists are used when programming features that use common devices. For example, a group of endpoints could belong to the same paging zone, have ring-in for the same trunk groups, and share common toll restrictions.
Chapter 3: System Features Fax Over Internet Protocol Automatic Extension Lists NOTE When using an extension list for ring-in or hunt groups, do not exceed 30 endpoints per list.
Chapter 3: System Features File-Based Music-On-Hold (MOH) File-Based Music-On-Hold (MOH) TThe File-Based Music-On-Hold (MOH) feature expands the existing MOH source beyond the built-in audio port located on the back of the Mitel 5000 chassis. That is, you do not have to connect to an external music source. This feature uses the compact flash-type memory card to store MOH audio files. This feature requires a software license.
Chapter 3: System Features File-Based Music-On-Hold (MOH) Table 3-10 lists other file formats that are used by the MOH Converter Utility. Some of these formats may need additional configuration to use (that is .gsm) or that only a subset of that file type works (that is .m3u, .hcom, .dat). Table 3-10. Other File Formats in the MOH Converter Utility Other File Formats and Extensions GSM File (*.gsm) This file requires an external library. M3U File (*.
Chapter 3: System Features House Phone House Phone This feature provides users with the ability to place a predesignated intercom or outside call simply by lifting the handset (or pressing the Speaker button, if using an endpoint) on a designated House Phone. In a network, the House Phone can be programmed to dial an offnode device.
Chapter 3: System Features House Phone The interaction of the House Phone Mode flag with the programmed Speed Dial number and system feature is shown in Table 3-11. Table 3-11.
Chapter 3: System Features Peer-to-Peer Audio for IP and SIP Devices Peer-to-Peer Audio for IP and SIP Devices The peer-to-peer (P2P) audio feature allows certain Internet Protocol (IP) and multi-protocol (SIP or ITP) devices to transmit and receive audio directly with each other. With this feature, the audio is not transmitted or received through the system chassis. This reduces delay and removes the audio stream from the Time Division Multiplex (TDM) highway.
Chapter 3: System Features Persistent Music-On-Hold Selection Persistent Music-On-Hold Selection The Mitel 5000 Call Processing manages the audio connections for incoming Public Switched Telephone Network (PSTN) calls. When a device places a call on hold, the trunk settings determine how it provides hold audio for the outside party. This determination is based on the settings at the Central Office (CO) trunk group to which the trunk resides.
Chapter 3: System Features Record Keeping and Maintenance Features Record Keeping and Maintenance Features The following sections provide information on record keeping and maintenance features. For programming instructions, refer to the “System Management” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006, or Mitel 5000 DB Programming Help.
Chapter 3: System Features Record Keeping and Maintenance Features All outgoing calls using a trunk that is not subject to toll restriction are classified as one of the following call types for call cost calculation (call cost type is programmed in the database).
Chapter 3: System Features Record Keeping and Maintenance Features Station Message Detail Recording (SMDR) Station Message Detail Recording (SMDR) is a system feature that provides a detailed record of outgoing and incoming calls. The system records only valid calls. Outgoing calls become valid when, depending on system programming, the Valid Call timer expires or polarity reversal is detected. Outgoing calls become valid immediately if placed on hold or transferred.
Chapter 3: System Features Record Keeping and Maintenance Features The system administrator can determine whether absorbed digits, equal access digits, and/or toll field digits appear in the SMDR printout. As an example, assume the following number was dialed: 89 (other system’s trunk access code) + 10288 (equal access code) + 1 (toll field) + 602 (area code) + 961-9000 (seven-digit number).
Chapter 3: System Features Record Keeping and Maintenance Features DIALED DIGITS For an outgoing call: The first 28 digits of the telephone number are shown (if ARS was used to place the call, the modified number, not the dialed digits, are shown). A “>” at the end of the number indicates that more than 28 digits were dialed. Some digits may be suppressed (see the previous page for an explanation).
Chapter 3: System Features Record Keeping and Maintenance Features Remote Configuration This feature is reserved for controlled introduction. The Remote Configuration feature provides a secure tunnel for database connectivity from a remote location to a customer’s Mitel 5000 system without making any changes to customer’s firewall. Using Remote Configuration, you can connect to and configure a Mitel 5000 system across a secure Virtual Private Network (VPN) connection.
Chapter 3: System Features System Health Report System Health Report The System Health Report is a report with Mitel 5000 system information and statistics that is emailed to the desired location daily. This feature is intended for support center personnel, not for end-customers. The information in this report helps the recipient diagnose and troubleshoot problems with the Mitel 5000 system. This feature requires a software license.
Chapter 3: System Features System Health Report • Release information: o Software release o Software version o License (system type 5200/5400/5600) o Build date o Listening port • System modules with status Call Activity (detail for the previous 24 hours): o Number of active PSTN trunks o Number of calls per hour System Events: • Memory usage, disk usage, file integrity check of main system files, and checksum check on low-level firmware files • Alarm information o o Call Processing Compon
Chapter 3: System Features System Health Report Figure 3-5. PS-1 System Health Report Information Mitel ® 5000 Reference Manual – Issue 3.
Chapter 3: System Features System Health Report Figure 3-6. Base Server System Health Report Information Page 3-40 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 4: Network Features Network Features Chapter 4: Network Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Component Compatibility for 99 Nodes Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Private IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3 IPRA Resources . . . .
Chapter 4: Network Features Introduction Introduction This chapter describes the following features that support networking capability with the Mitel 5000 platform: • “Component Compatibility for 99 Nodes Support” on page 4-2 • “Private IP Networking” on page 4-3 • “P2P Audio” on page 4-15 • “NTP Support” on page 4-16 • “System Manager Support” on page 4-16 Component Compatibility for 99 Nodes Support Table 4-1 lists component version numbers that have been validated to support the 99 Nodes system featur
Chapter 4: Network Features Private IP Networking Private IP Networking This section describes how the Mitel 5000 system handles Private IP Networking. IPRA Resources The Internet Protocol Resource Application (IPRA) supports both IP devices and private networking. IPRA supports up to 32 IP resources, including MGCP trunks, SIP gateway trunks, multi-protocol endpoints, or IP networking ports.
Chapter 4: Network Features Private IP Networking Resource Allocation System resources for Private IP Networking are allocated in the following manner: • IP Networking Resources: The system allocates IP Networking resources upon call setup. If the resources necessary to complete a call are not available, the call camps-on to the resources and the system does not deliver the call to its destination until the resources are available.
Chapter 4: Network Features Private IP Networking • Multiple Ring-In Calls: The system reserves IP Networking Resources for each leg of a complex call. However, once the call is answered, the system releases all Resources that are allocated for legs that no longer exist. For example, device A on Node 1 calls an All-Ring Hunt Group with three members on Node 2. The system reserves three IP networking resources on each node, allowing each member to receive an incoming call ring.
Chapter 4: Network Features Private IP Networking Resource Reservation The Resource Reservation Tool provides the interface for reserving IP resources for devices or applications in an oversubscribed system. After IP resources are reserved for particular purposes, the remaining resources are shared on a first-come, first-served basis. For programming instructions, refer to the “System Device and IP Settings” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006.
Chapter 4: Network Features Private IP Networking Background Music When an IP endpoint user wants to listen to Background Music and presses feature code 313 in default mode, the system must allocate required IP resources. If resources are not available, the IP endpoint camps on for IP resources and the user sees the transient display WAITING FOR RESOURCES on the display endpoint screen.
Chapter 4: Network Features Private IP Networking Emergency/911 Mitel recommends that the system be provisioned to have an appropriate number of Emergency/911 IP resources reserved for both IP endpoints and IP trunks. For instance, if an IP endpoint makes an Emergency/911 call that must go out an IP trunk, sufficient IP resources for the both the IP endpoint and IP trunk need to be reserved to ensure the call goes through.
Chapter 4: Network Features Private IP Networking Simple Hunt Groups All IP endpoint hunt group members are available to their respective hunt groups until the hunt group tries to call them once. At this point, the IP endpoint rings if it can allocate the appropriate IP resources. If IP resources are not available, the IP endpoint hunt group member changes status to Busy and camps on for an IP resource.
Chapter 4: Network Features Private IP Networking Data Connections The following data connections are maintained by the Private IP Networking feature: • Data Channels: The system maintains one data connection between each node programmed for Private IP Networking. The system uses this data connection for call control and datagram messaging. When a data connection fails, the system attempts to establish a new connection using alternative IPR application resources if they are available.
Chapter 4: Network Features Private IP Networking IP Connections and IP Connection Groups The following are IP Connection and Node IP Connection Group descriptions. • IP Connections: Contain the programming information for each IP connection in the network. The extensions associated with each connection are automatically added to this folder when local or remote IP connections are created.
Chapter 4: Network Features Private IP Networking Diagnostics The IP Networking application includes several tools for performing diagnostics when troubleshooting. These tools are separate from call processing and can display only information local to the IPR application. There are also programming displays to control how the call behaves. For programming instructions, refer to the “Troubleshooting” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006.
Chapter 4: Network Features Private IP Networking Automatic NAT Detection Automatic Network Address Translation (NAT) Detection allows Mitel IP endpoints to operate inside or outside a private network NAT or firewall without having to change the NAT Address Type field in the IP Settings folder in DB Programming every time the endpoint is relocated.
Chapter 4: Network Features Private IP Networking Figure 4-1 shows the configurations of endpoints programmed for the three NAT Types in DB Programming. Figure 4-1.
Chapter 4: Network Features P2P Audio P2P Audio This section describes Peer-to-Peer (P2P) audio, its requirements and constraints, and the role of network groups in implementing the feature. NOTICE Passing real-time streaming data, such as audio, through encrypted virtual private networks (VPN) may significantly impact network performance, router and firewall functionality, and audio quality.
Chapter 4: Network Features NTP Support P2P Network Groups Network Groups define the IP devices, SIP endpoints, MGCP endpoints, and SIP gateway trunks that can connect to each other using P2P audio. Only devices within the same Network Group can talk to each other using P2P audio. Even devices that are on separate nodes must be in the same Network Group.
Chapter 5: Trunks and Trunk Features Trunks and Trunk Features Chapter 5: Trunks and Trunk Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3 Dual T1/E1/PRI Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3 Variable T1 Span Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5: Trunks and Trunk Features Toll Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27 Trunk Groups Subject to Toll Restriction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27 Trunk Group Exemption from ARS Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-28 Area/Office Code Numbering Plans and Local Area Codes . . . . . . . . . . . . . . . . . . . . . .
Chapter 5: Trunks and Trunk Features Introduction Introduction This section provides information about trunking features available with the Mitel 5000 platform. The Mitel 5000 platform supports the following types of trunks and spans: • Loop start trunks on the Loop Start Module (LSM-2 or LSM-4): Loop start trunks support incoming and outgoing calls and the Caller ID feature. For details, see page 5-35.
Chapter 5: Trunks and Trunk Features Variable T1 Span Characteristics Variable T1 Span Characteristics When purchasing a T1 span, several variables are involved, depending on the T1 application required. For details, see page 5-36. The following variables must be considered when ordering a T1 span: • Module framing type: The type of framing scheme used by the T1 spans connected to the module can be D4 Superframe—normally used for voice transmissions—or Extended Superframe (ESF).
Chapter 5: Trunks and Trunk Features Variable T1 Span Characteristics • Operator System Access: (Used for PRI-equipped ports set for National ISDN2 only) When National ISDN 2 is used, there is an option to enable Operator System Access (OSA). OSA is required by some central offices. If this flag is enabled, the user will be allowed to request access to an operator services system.
Chapter 5: Trunks and Trunk Features Trunk Access Codes Trunk Access Codes Use the following feature codes when selecting a trunk to place an outgoing call. Table 5-2. Trunk Access Codes Feature Name Code USA [European] Definition Automatic Route Selection (ARS) 92000 Allows the system to select the desired route for placing a call, as programmed in the database. Trunk Group Access 1–208 92001–92208 Selects an available trunk from a programmed group of trunks for placing an outside call.
Chapter 5: Trunks and Trunk Features Trunk Features Answer Feature Code For calls that are ringing or holding at the endpoint, the user may enter the Answer feature code (351) or press the ANSWER button. When more than one call is ringing or holding, the following priorities determine which call is answered first: • Ringing calls (ring ins, recalls, callbacks, or transfers) are answered in the order they were received. • Calls on individual hold are answered in the order they were placed on hold.
Chapter 5: Trunks and Trunk Features Trunk Features Endpoint Displays Whether call information appears on the endpoint display, and what information appears, is determined by endpoint flags in the database. The flags are: • Expanded CO Call Information On Displays: This endpoint flag determines whether call information (trunk name or call information) is displayed at the endpoint. If it is enabled, the Outside Call Party Information Has Priority flag determines what is displayed.
Chapter 5: Trunks and Trunk Features Trunk Features Display Line 2 The following criteria are used to display the number on the bottom line of the ring-in display. This assumes that all of the necessary flags are properly set. 1. Outside Party Number provided by the Desktop Application, if available. 2. Outside Party Number provided by Caller ID, if enabled at the endpoint level. 3. Outside Party Number provided by ANI service, if enabled at the endpoint level. 4.
Chapter 5: Trunks and Trunk Features Trunk Features Day and Night Modes Separate lists exist in the database for class-of-service, outgoing-access, allowed-answer, emergency outgoing access, and ring-in assignments for day and night modes. When an administrator enters the Night Ring feature code, the system uses the night mode lists. When the system is in day mode, the day lists are used. Active calls are not affected when the mode is changed.
Chapter 5: Trunks and Trunk Features Trunk Features Using DISA NOTE If DTMF decoders are unavailable when a DISA call is received, the incoming DISA call is automatically sent to the primary attendant. To use DISA: From a DTMF telephone, the caller dials the telephone number of the DISA trunk. When the call is answered by the system, the caller hears system intercom dial tone DISA 1 SYSTEM Caller dials DISA number, hears IC dial tone, and enters DISA security password, if required.
Chapter 5: Trunks and Trunk Features Trunk Features Emergency Calls The Mitel 5000 allows immediate access to local emergency facilities whenever an endpoint user enters the Emergency Call feature code. The dialing pattern defaults to 911 on systems located in the USA and to 999 on systems located in the European market. When activated, the Emergency Call feature selects a trunk or routes the call based on the endpoint programming.
Chapter 5: Trunks and Trunk Features Trunk Features If everything is denied due to Emergency Outgoing Access, the call is routed once again to Route Group 1. The call then tries the first facility group in Route Group 1. The trunk group or node trunk group does not validate the endpoint originating the emergency call against the group’s Emergency Day/Night Outgoing Access List. If no trunks are available, the call tries the next member in the facility group.
Chapter 5: Trunks and Trunk Features Trunk Features Emergency Outgoing Access Lists The system supports two outgoing access lists called Emergency Day Outgoing Access and Emergency Night Outgoing Access. These lists, which are similar to the Day/Night Outgoing Access lists, are programmable for CO Trunk Groups and Node IP Connection Groups. These lists default to the new Auto Extension List PP051: Auto: All Endpoints.
Chapter 5: Trunks and Trunk Features Trunk Features IP Devices and Local Loop Support The system supports SIP (Session Initiated Protocol) trunks to reach the CO. SIP trunks allow the system to communicate with the CO via SIP-enabled gateways. As the SIP protocol becomes more and more popular, it is important to be able to communicate to SIP gateways in the IP-centric world.
Chapter 5: Trunks and Trunk Features Trunk Management Trunk Management This section describes the way the Mitel 5000 platform has been designed to facilitate efficient management of trunk facilities. Trunk Groups Each trunk is assigned to a trunk group. Trunk group feature codes and trunk group buttons are used to select a trunk in one of the programmed trunk groups. Each trunk must be assigned to a trunk group.
Chapter 5: Trunks and Trunk Features Trunk Management Nodes and Node Trunk Groups Node trunk groups: Are made up of PRI circuits that are programmed for private network use. When a PRI-equipped module is programmed for networking (Private Networking switch type), the system automatically creates a node trunk group. (All B-Channels residing on the same T1M or T1M-2 module are in the same node trunk group.) Node programming: Contains a list of node trunk groups used to access another node.
Chapter 5: Trunks and Trunk Features ISDN PRI Two B-Channel Transfer ISDN PRI Two B-Channel Transfer The ISDN PRI Two B-Channel Transfer (TBCT) feature is an ISDN optimization supplementary service offered by the PSTN. You must purchase support for the TBCT from the CO. The TBCT feature optimizes trunk-to-trunk calls by releasing them from the PBX and connecting them through the Central Office (CO).
Chapter 5: Trunks and Trunk Features ISDN PRI Two B-Channel Transfer • “Multiple Node, Multiple PRI Span Scenario” on page 5-20 Figure 5-1. Single Node, Single PRI Span Scenario Outside Party #1 Outside Party #2 5000 Incoming call on PRI Span-1 Subscriber Outgoing call on PRI Span-1 Request for 2B-XFR on PRI Span-1 Success Response for 2B-XFR on PRI Span-1 Disconnects for two calls on PRI Span-1 1. Outside Party #1 calls into the PBX on PRI Span-1. 2.
Chapter 5: Trunks and Trunk Features ISDN PRI Two B-Channel Transfer 4. The Mitel 5000 system sends a facility request “invoke” command with the D-channel IDs of PRI Span-1 along with the two call reference values. 5. The PSTN acknowledges 2B-Transfer request. The PSTN disconnects both B-channel calls. Figure 5-3.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Outgoing-Access, Allowed-Answer, and Ring-In Assignments Each trunk group has programmed lists of endpoints for outgoing-access, allowed-answer, and ring-in assignments for day and night modes. • Outgoing-access: Permits the endpoint user to place calls using trunks in that trunk group. Each endpoint has a default outgoing access code programmed in the database.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Call Routing Tables A trunk group can be programmed to ring in to a call routing table to use the information received from DID DNIS, ANI, and Caller ID. This added information allows the endpoint user to receive information about the callers—such as location, name, or which advertisement they saw—on the endpoint display.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments The system can have up to 15 call routing tables. There can be a total of 900 patterns in all of the call routing tables combined. Each individual trunk, not the trunk group, is programmed to collect digits using Caller ID, DID, ANI, or DNIS.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments ANI Call Routing Table Example The following is an example of an ANI table for various area codes. If the incoming ANI information begins with one of the indicated area codes, it will be routed to the designated destination and the display will show the state where the call was placed.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments DNIS Call Routing Table Example This is an example of a DNIS application pattern. If the DNIS digits match 8006695858, the call came in on the Technical Support 800 number and is sent to the Technical Help hunt group. The display will show that the call is from “Help Line.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Public Network Call Routing Example For call routing to the public network, this table is programmed to send callers who dial a special number (940-1431) to an outside line.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Toll Restriction The following features provide toll restriction on the Mitel system through Class of Service (COS) programming. Classes of Service are described in further detail in the following paragraphs. • Trunk Group Toll Restriction: Designates a trunk group as “subject to toll restriction” or “not subject to toll restriction” in database programming.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Trunk groups can be programmed as “not subject to toll restriction” to allow endpoint users to have access to reduced-cost long distance carriers, or to use ring-down lines, dictation machines, voice mail systems, and other auxiliary equipment.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Area/Office Code Numbering Plans and Local Area Codes If any office codes in the local area code have a 0 or 1 as the second digit, the local office codes are probably used as area codes elsewhere, and the system requires special programming to allow toll restriction to work properly.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Absorbed Digits Trunk groups that are subject to toll restriction can be programmed to “absorb” (ignore) the first digits so that the digits dialed are handled by the system just as they would be by the local telephone company or PBX to which the system is connected.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Equal Access Under the terms of the final divestiture agreement, Bell Operating Companies provide equal access to all long distance companies. The equal access provision requires each Bell Operating Company to modify existing switching equipment to make it possible for customers to have direct access to all available carriers serving their area code.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments • COS 03 – Deny Operator: Calls to numbers that match the dial patterns for this class of service (defaults to [Q]RN+, [Q]R0, and [Q]RE) are restricted, unless the number also matches a dial pattern in an “allowed” class of service that is assigned to the endpoint, Voice Processing application, or trunk group being used.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments In the event that the classes of service for the endpoint or Voice Processing application and the trunk group conflict, the decision to restrict or allow a number is based on the following ordered checks. The ordered checks apply to all calls to outside telephone numbers, including calls forwarded to outside telephone numbers. • Endpoint or Voice Processing application COS is checked.
Chapter 5: Trunks and Trunk Features Outgoing-Access, Allowed-Answer, and Ring-In Assignments Non-Programmable Wildcards Table 5-4 shows the special characters that may be used when specifying dialing patterns. These characters are not programmable. Table 5-4.
Chapter 5: Trunks and Trunk Features Trunk Camp On and Busy Trunk Queue Callback Trunk Camp On and Busy Trunk Queue Callback Camp On and Queue Callback requests allow the caller to wait for an available resource. An endpoint user waiting for a specific resource (a trunk or an endpoint) will be served before an endpoint user waiting for a group (trunk group or hunt group) that contains that specific resource. This includes camped on Emergency Call feature calls.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI T1/E1 Spans and PRI This section describes T1 and E1 multi-channel spans and the trunks that can be installed on the Mitel 5000 platform using T1M or T1M-2 modules. NOTE This feature requires a single-port or dual-port T1/E1/PRI module (T1M or T1M-2). The second port on the T1M-2 and the PRI feature require software licenses.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI Fractional T1 (FT1), which uses fewer than the standard 24 circuits, can be used on the Mitel system. If FT1 is used, the unused circuits of the T1M or T1M-2 port must be unequipped. Table 5-5 shows examples of T1 installations. Table 5-5. T-1 Span Applications In this application, the T1M or T1M-2 modules are connected directly to the central office. The Line Build Out (LBO) is programmed to support the distance to the CO or the nearest repeater.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI DID/DDI Trunks Direct Inward Dialing (DID) [Direct DIaling Inward, DDI, in Europe] is available on T1M or T1M-2 modules and Single-Line Adapter (SLA) interfaces. For more information about T1 modules, refer to the “Installation” chapter in the Mitel 5000 Installation and Maintenance Manual, part number 580.8000. E&M trunks on T1M or T1M-2 modules can also be designated as DID [DDI] trunks.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI The DID/E&M Receive Busy Instead Of Camp-On endpoint flag determines whether E&M and DID/DDI callers will receive busy signal or receive ringback and camp on when calling a busy endpoint. In the default state, busy tones are disabled and the callers hear ringback while camped on to the called endpoint. This flag is programmed on an endpoint-by-endpoint basis.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI Primary Rate B-Channel The Mitel 5000 platform supports Primary Rate B-channels. Each port on a T1M or T1M-2 module consists of 23 B-channels. Each B-channel is programmed as an individual trunk in the database. The system is designed to support only AT&T 4ESS Custom, AT&T 5ESS Custom, National ISDN 2, and DMS-100 switch types or Private Networking. No other switch types are currently supported by the Mitel system.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI Trunk Group PRI Call By Call Feature System trunk groups provide limited access to PRI Call By Call services. Each trunk group that contains B-channels can be assigned a PRI Call By Call feature to use for outgoing calls.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI Overlap Sending and Receiving With overlap sending, the system can send some or no called number digits in the setup message and send additional digits (or overflow digits) in subsequent information messages. You can also program the system to use the overlap sending protocol immediately. If this option is selected, the setup message contains no called number digits, and all digits are sent in subsequent information messages as the digits are dialed.
Chapter 5: Trunks and Trunk Features T1/E1 Spans and PRI The following programming is required to use the E&M feature: 1. Install and configure a T1M module. For more information about T1M modules, refer to the “Installation” chapter in the Mitel 5000 Installation and Maintenance Manual, part number 580.8000. Configure the appropriate circuits as “E&M” and assign extension numbers to the trunks. 2. Program the T1M or T1M-2 module as required. 3.
Chapter 6: End User Features End User Features Chapter 6: End User Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5 User Feature Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-5 Access to User Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6: End User Features Forwarding – Call Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19 FWD Button and Menu Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20 Forward to an Outside Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20 Manual Forwarding to Public Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6: End User Features UCD and ACD Hunt Group Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-41 Announcement and Overflow Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-41 Voice Processing Applications as Announcement or Overflow Stations . . . . . . . . . . . . .6-42 Agent Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 6: End User Features Outside Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-61 Placing Outside Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-61 Receiving Outside Calls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-62 Outside Call Endpoint Signals . . . . . . . . . . . . . . . . . .
Chapter 6: End User Features Introduction Introduction This chapter describes Mitel 5000 features that are used by or mainly affect end users. Features are listed in alphabetical order beginning on page 6-6. For voice processing features, refer to “Voice Processing Features” on page 7-1. User Feature Information The following section provides information about endpoint user features. Access to User Features Each of the endpoint features is assigned a feature code.
Chapter 6: End User Features Account Codes Account Codes Account codes are 3- to 12-digit codes that can be used in conjunction with the Station Message Detail Recording (SMDR) feature to aid record keeping. Account codes can be assigned to measure telephone use and/or to identify calls for customer billing. Types of account codes include Standard, Forced, and Optional. The account code, when used, is recorded in the SMDR report as soon as the call is completed.
Chapter 6: End User Features Automatic Call Access Automatic Call Access This feature allows a user to determine the way incoming calls are answered by entering a feature code to select the type of call access. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Call Logging Call Logging The Call Logging feature lists the following types of calls for users of Mitel digital and IP endpoints and Mitel IP softphone applications: • Missed Calls • Received Calls • Dialed Calls The Call Logging feature helps you see who called when you were away and makes it easy to redial those people. Non-display and single line endpoints do not support this feature. Six-line display endpoints are recommended for field visibility and ease of use.
Chapter 6: End User Features Call Logging Call Logging Displays on a Six-Line Display Endpoint The following examples show the Call Logging displays that appear on six-line endpoints. Idle Menu Display An option on the Idle Menu of six-line display endpoints allows you to access the logs directly. Note that the six-line administrator display endpoints no longer show “ADMIN FEATURES” on the first line.
Chapter 6: End User Features Call Logging Missed Calls The Missed Calls feature is supported only on six-line display endpoints. If an endpoint has registered missed calls that the user has not yet viewed, the MISSED <1–99> calls menu option appears on the display, as shown in the following example.
Chapter 6: End User Features Call Logging Call Logging Displays on a Two-Line Display Endpoint The following examples show Call Logging displays that appear on a two-line display endpoint. NOTE At any menu level, you can press the asterisk (*) button to cancel or return to the previous menu, or press the pound (#) button to accept. Idle Menu Display The following example shows a two-line display when the endpoint is idle.
Chapter 6: End User Features Call Screening Call Screening Calls transferred from the Automated Attendant or a Call Routing Announcement application can be screened, announced, or unannounced. Separate programming flags in the database determine the methods used for transferring calls to endpoints with mailboxes, endpoints with extension IDs, and extensions without mailboxes or IDs.
Chapter 6: End User Features Call Waiting Call Waiting While an endpoint is in use, incoming intercom and outside calls camp on until the busy endpoint is available. The busy party hears a single camp-on tone every 15 seconds (unless the Camp On Tone timer is changed or Camp On tones are disabled at the endpoint). An endpoint programming flag (Camp-On Indications) allows Camp On tones to be enabled or disabled for incoming intercom and outside calls. This flag is programmed on an endpoint-byendpoint basis.
Chapter 6: End User Features Conference Calls Conference Calls Endpoint users can establish multi-party conference calls without operator assistance. Up to four parties can be connected in a conference. In addition to the initiating endpoint, the conference can include any combination of three intercom and/or outside calls. The system provides five conferencing resources. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Default Endpoint Default Endpoint An endpoint user can enter one feature code that will return the following features to their default states.
Chapter 6: End User Features Directory of Intercom, Speed Dial, and Feature Codes Directory of Intercom, Speed Dial, and Feature Codes The Directory feature enables display endpoint users to look up intercom extension numbers and user names, System Speed Dial numbers and names, or system feature codes.
Chapter 6: End User Features Do-Not-Disturb Do-Not-Disturb Placing an endpoint in Do-Not-Disturb halts all pages, incoming intercom calls, camped-on calls, and transferred calls to that endpoint. Queue callbacks, recalls, and direct ring-in calls are not blocked. Another user calling the endpoint while it is in Do-Not-Disturb hears a repeating signal of four fast tones and a pause. Display endpoints show the Do-Not-Disturb message.
Chapter 6: End User Features Do-Not-Disturb DND on a Network DND works as follows in a network setting: • Each node has its own list of DND messages that can be used only on that node. • An intercom caller will see another user’s DND display when calling across nodes. • The network allows DND override across nodes. The system has default DND messages in both the primary and secondary languages.
Chapter 6: End User Features Forwarding – Call Forwarding Forwarding – Call Forwarding With Call Forwarding, an endpoint user can route incoming intercom and outside calls, including direct ring-in calls, to another endpoint, to a hunt group, or to an outside telephone number, if allowed by toll and trunk restrictions. In a network setting, the network allows the user to forward calls to endpoints or hunt groups on another node.
Chapter 6: End User Features Forwarding – Call Forwarding FWD Button and Menu Buttons Some endpoints use a combination of the default FWD button and forwarding menu buttons. When the default FWD button is pressed, the display shows a menu of call forwarding options. The user must then select the desired option by pressing the corresponding button next to the display.
Chapter 6: End User Features Forwarding – Call Forwarding Forward to the Message Center Endpoint users can forward calls to their message centers. Users can forward calls to their designated message center by pressing the FWD button and then the MSG button or MESSAGE CENTER menu button. Single-line users must use the call forwarding procedure and dial the extension number of the message center.
Chapter 6: End User Features Forwarding – System Forwarding Forwarding – System Forwarding System Forwarding provides the ability to program the system so that calls ringing at an endpoint follow a programmed “forwarding path” that routes the call based on the type of call and the status of the intended endpoint. The Call Forwarding endpoint feature can be used to override System Forwarding. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Forwarding – System Forwarding For an example, see the diagram below. In the example, the “principal” endpoint user wants direct ring-in or transferred calls to ring at his or her endpoint during day mode. The principal endpoint has a forwarding path with two forwarding points: a hunt group and voice mail. If the principal does not answer the call, it follows the forwarding path to forwarding point #1, a hunt group.
Chapter 6: End User Features Forwarding – System Forwarding Individual Endpoint Forwarding Points The ringing duration at each endpoint forwarding point is determined by the System Forwarding Advance timer (defaults to 15 seconds). If the endpoint forwarding point is busy, the call will camp-on until the System Forwarding Advance timer expires and then it moves to the next forwarding point.
Chapter 6: End User Features Forwarding – System Forwarding Manual Call Forwarding and System Forwarding If the principal endpoint has manual call forward enabled (using the FWD button or one of the Call Forwarding feature codes), the Call Forward feature overrides System Forwarding.
Chapter 6: End User Features Forwarding – System Forwarding If an endpoint forwarding point is manually forwarded to voice mail, the call will not follow the manual forward to Voice Processing; it will ring at the endpoint forwarding point.
Chapter 6: End User Features Forwarding – System Forwarding System Forward Enable/Disable The endpoint user has the option of entering feature codes that will disable or enable the use of System Forwarding at that endpoint. The enable/disable flag does not affect the endpoint’s appearance on any other endpoint’s call forwarding path. The flag merely determines if the endpoint will have its own calls System-Forwarded.
Chapter 6: End User Features Group Listen Group Listen The Group Listen feature allows a user to transmit a conversation over the endpoint speaker while in handset or headset mode. This allows other people in the room to listen to the conversation. However, the endpoint microphone remains disabled so that only the headset or handset user can speak. This feature cannot be used on a handsfree call. The user must be on a call using the handset or a headset before entering the feature code.
Chapter 6: End User Features Hookflash [Recall] Hookflash [Recall] A timed hookflash [recall, in Europe] may be required for endpoint and single line endpoint users to use certain telephone company or PBX features. The CO Hookflash feature code sends a timed hookflash/recall over the trunk when entered. A hookflash/recall restarts the call cost display and toll restriction, plus it starts a new line in the SMDR printout. However, the call remains under the same CALL button.
Chapter 6: End User Features Hunt Groups Hunt Group Call Distribution When an intercom or outside call is transferred or rings in to the pilot number, it circulates through the hunt group in linear or distributed order until answered, as described below. • Linear order: Incoming calls always start circulating by ringing at the first endpoint (or extension list) on the hunt group list that is stored in the database.
Chapter 6: End User Features Hunt Groups Hunt Group Call Processing Hunt group endpoints receive the following indications when a call is ringing in: • If an outside call is ringing, the endpoint designated to receive the call first shows ring flash on the associated individual trunk button (if it has one) or a CALL button until the call is answered or the No Answer Advance timer expires and the call moves to the next endpoint.
Chapter 6: End User Features Hunt Groups Hunt group programming affects the Call Forwarding feature in the following ways: • Hunt group calls follow unconditional forward: If an endpoint location in a hunt group is in the unconditional call forward mode to another endpoint, calls to the hunt group will follow the endpoint forwarding request. A forwarded hunt group call will ring at the forwarding destination until the No Answer Advance timer expires.
Chapter 6: End User Features Hunt Groups Hunt Group Timers Table 6-4 summarizes timers that can be programmed on a hunt group-by-hunt group basis. Table 6-4. Hunt Group Timer Parameters Timer Default Range Purpose No Answer Advance 18 sec 1–255 sec Determines the amount of time a call will ring at a hunt group endpoint or extension list (unanswered) before advancing to the next endpoint or extension list on the hunt group list.
Chapter 6: End User Features Hunt Groups Hunt Group Remove/Replace and Do-Not-Disturb Hunt group members can temporarily stop hunt group calls from ringing at their endpoints by entering the Hunt Group Remove feature code as described below. If an endpoint is assigned to more than one hunt group, this halts calls from all hunt groups. Hunt Group assignments cannot be removed individually. DND can also be used to halt Hunt Group and other calls to the endpoint.
Chapter 6: End User Features Hunt Groups ACD Hunt Groups Automatic Call Distribution (ACD) can be programmed to distribute hunt group calls to equalize call time or call count among the available members. Using the System OAI Events feature, ACD hunt groups can be programmed to send call information records to an external device connected to the system, such as Contact Center Suite. NOTE This feature requires the ACD Hunt Group software license.
Chapter 6: End User Features Hunt Groups ACD Agent ID ACD hunt group members are referred to as “agents.” Agents log in to the ACD hunt group to receive calls and log out to halt ACD hunt group calls. An ACD hunt group can be programmed to circulate calls to agents in two ways: • Agent IDs: Assigns each agent an Agent ID number which he or she enters during the login procedure (described below).
Chapter 6: End User Features Hunt Groups ACD Agent Wrap-Up Timer Each time an agent ends an ACD hunt group call, the endpoint goes into “wrap-up” mode, and the Wrap-Up timer is started. Until that timer expires, the agent will not receive another call through any ACD hunt group. (However, the agent can receive non-ACD hunt group calls, direct ring-in calls, and transfers.) The range of the Wrap-Up timer is 1 to 65,535 seconds. The default value is 15 seconds.
Chapter 6: End User Features Hunt Groups Remote ACD Hunt Groups The Remote Automatic Call Distribution Hunt Groups software license feature allows ACD hunt groups to span nodes. Node-spanning ACD hunt groups can have either members or ACD Agent IDs. • Members: ACD hunt group members may include off-node endpoints, off-node single lines, and Hunt Group Member extension lists. • ACD Agent IDs: Unlike members, there are no off-node Agent IDs.
Chapter 6: End User Features Hunt Groups Operational Changes The Station Monitor feature is limited to a single node. Members who are logged in to a remote node or who are logged in to the supervisor’s node from a remote node cannot be monitored. Hunt groups with remote members rely on network links between nodes.
Chapter 6: End User Features Hunt Groups • During a database restore on a node containing ACD hunt groups that use Agents IDs, all Agents IDs are placed into each hunt group’s removed list. All endpoints will be logged out during the restore. • When the extension number of a logged-in endpoint is changed, the new extension will be logged in with the same Agent ID and will not be disconnected. This applies to endpoints logged in both remotely and locally.
Chapter 6: End User Features Hunt Groups UCD and ACD Hunt Group Features The following features are available to UCD or ACD hunt groups. Announcement and Overflow Stations Announcement and overflow stations are individual endpoints that receive unanswered calls when all of the hunt group endpoints are unavailable. They are not usually included in the hunt group list. Announcement and overflow stations can be separate endpoints, or they can be the same endpoint.
Chapter 6: End User Features Hunt Groups Overflow Stations: The Overflow timer is started when the Announcement timer expires or, if there is no announcement station, when the call is received by the hunt group. If an incoming hunt group call is unanswered when the Overflow timer expires, the call is picked up by an overflow station. The overflow station is a playback device that answers the call and plays a message.
Chapter 6: End User Features Hunt Groups Agent Help The Agent Help feature allows an endpoint user to request help from a designated “Agent Help Extension” during a 2-party or 3-party call. When the request-for-help call rings, the Agent Help Extension can choose to join the call or reject the request. The Agent Help Extension can be a supervisor or other endpoint, an extension list, or a hunt group. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Hunt Groups To signal to the other parties that the Agent Help Extension has joined the call, a system-wide Agent Help Tone flag can be enabled during database programming. If the flag is disabled, there will be no alerting tone. A timer, called the Agent Help Tone Interval timer, determines how often this tone is generated.
Chapter 6: End User Features Hunt Groups Hunt Group Supervisors and Station Monitoring The Station Monitor feature allows hunt group supervisors to monitor the calls of anyone in a specified hunt group. For feature usage instructions, refer to the applicable endpoint user guide. Consider the following concepts when using the hunt group feature: • As a courtesy, hunt group members should be notified in advance that their NOTE calls may be monitored.
Chapter 6: End User Features Hunt Groups Group Call Pick-Up When the Group Call Pick-Up feature is enabled, a call ringing in to a hunt group or one of its endpoints can be picked up at any other endpoint. Users can enter the Reverse Transfer feature code (4) and dial a hunt group’s pilot number to pick up a call that is ringing in to the hunt group’s pilot number or to any endpoint within that hunt group. The system routes calls for pick-up in accordance with the following priority list.
Chapter 6: End User Features Intercom Calls Intercom Calls The intercom can be used to place endpoint-to-endpoint calls that can be answered handsfree. Or, it can be used to place private, non-handsfree, calls. An endpoint user that reaches a busy endpoint can camp on, request a callback queue, or leave a message. Additional features that apply to both outside and intercom calls include Call Waiting, Call Transfer, Reverse Transfer, Call Forwarding, and Hold.
Chapter 6: End User Features Intercom Calls Receiving Intercom Calls If the endpoint does not have an IC button, the call appears under a CALL button. For feature usage instructions, refer to the applicable endpoint user guide. Placing Intercom Calls When placing an intercom call, begin dialing before the Dial Initiation timer expires. If the timer expires, the system drops the connection and sends reorder tones.
Chapter 6: End User Features Messages Messages Intercom callers may leave a message waiting indication if a called endpoint is busy, if there is no answer, if the endpoint is in DND, or when they are connected to or placed on hold by another endpoint. Users can leave a message for and respond to messages from, users on other nodes. There are two messaging options: • Have the called party return your call: Display endpoints show the source and time of the message.
Chapter 6: End User Features Microphone Mute Alternate Message Source The Alternate Message Source feature enables a voice mail unit to leave messages through an endpoint or hunt group endpoint that is designated as its alternate message source. When a message is left on the voice mail unit for an endpoint user that has an assigned mailbox, the called endpoint receives the Message Waiting indication.
Chapter 6: End User Features Intelligent Directory Search Intelligent Directory Search With system software v1.2, The Intelligent Directory Search (IDS) feature simplifies searching for entries in a directory by significantly reducing the number of keystrokes required to find a match. However, because the dialpad has fewer buttons than the number of letters in the alphabet, each button represents several letters. For example, dialpad button 5 represents “5, J, K, L, j, k, or lower case L.
Chapter 6: End User Features Intelligent Directory Search Finding an Entry in the IC Directory The following sections show examples of display endpoint screens. You will see similar examples when using the IDS feature to retrieve an entry from the IC Directory. Also discussed are the actions you need to take when using the feature. NOTE Two-line display endpoints show only the first two lines of the six lines shown in the following examples.
Chapter 6: End User Features Intelligent Directory Search Finding Listings in the Outside Directory Upon accessing the Outside Directory, you see the first entries the entire directory. If the directory is empty, a message appears indicating that entries are not available, and you hear a fast busy signal. If desired, phone numbers can be programmed as “Private” in the database and will appear as a “PRIVATE NUMBER” in the display, as shown in the following example.
Chapter 6: End User Features Multilingual Capability Multilingual Capability The Mitel 5000 platform provides a choice among American English, British English, Spanish, and Japanese prompts and displays. The system selects the language to use for each call, as determined by the trunk, endpoint, and Voice Processing programming, as described in the following sections. Among the IP endpoints, only the Model 8660 displays Japanese prompts.
Chapter 6: End User Features Multilingual Capability Secondary Language Selection Each endpoint in the system has a programming field labelled “Secondary Language.” This field corresponds to the Change Language feature (301), which is used to toggle between the system primary language and secondary language. With this feature, the user can toggle between the system primary and secondary language, or can specify a different secondary language.
Chapter 6: End User Features Multilingual Capability Multilingual Do-Not-Disturb and Reminder Messages The system provides default Do-Not-Disturb and reminder messages in American English, British English, Japanese, and Spanish. However, the messages that use Japanese characters can be reprogrammed only through an Administrator endpoint. For more information, refer to the Mitel 5000 Endpoint and Voice Mail Administrator Guide, part number 580.8001.
Chapter 6: End User Features Multilingual Capability Multilingual Feature in Network Operation For calls across network nodes, if the language does not match between two nodes, the called voice processing system searches for the designated language in its system in the following order: 1. Primary Language 2. Secondary Language 3. American English 4. British English 5. Japanese 6. Spanish 7.
Chapter 6: End User Features Music-On-Hold and Background Music Music-On-Hold and Background Music The Music-On-Hold (MOH) feature intends to make waiting on hold as pleasant as possible, and it assures the holding party that the call is still connected. Users can choose to listen to background music by entering the Background Music feature code (313). For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Off-Hook Voice Announce (OHVA) Off-Hook Voice Announce (OHVA) The OHVA feature allows an intercom caller (either single line or digital endpoint) to establish voice contact with the called endpoint user, even though the user already has a call in progress on the handset. The called party can then talk freely on both connections, using the handset for the original call and the speakerphone for the OHVA intercom call.
Chapter 6: End User Features Off-Hook Voice Announce (OHVA) To place an OHVA call: 1. When placing an intercom call to a busy OHVA-enabled endpoint, do not hang up. You hear busy signals until the Camp On and OHVA Screening timers expire. If you hear music after the Camp On timer expires, conditions for an OHVA call were not met and you are camped-on. OFF-HOOK VOICE ANNOUNCE ENDPOINT WITH PCDPM Ext. 1103 1 Caller places a call to ext. 1002 and hears busy signal 2. Ext.
Chapter 6: End User Features On-Hook Monitoring On-Hook Monitoring An endpoint user with a speakerphone can monitor the call (listen to a recorded message, wait for the call to be answered, or wait on hold), and then speak handsfree when answered. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Outside Calls Receiving Outside Calls What you hear when you receive an outside call depends on whether you are using an endpoint with multiple lines or a single-line endpoint, as described in the following sections. Outside Call Endpoint Signals You hear one of the following signals when receiving an outside call. • Repeating long tones and a CALL button or individual trunk button is flashing at the fast rate: A call is ringing in.
Chapter 6: End User Features Paging Paging The Paging feature allows announcements to be made through endpoint internal speakers. Optional external paging equipment such as amplifiers and paging speakers may be installed using the external PAGE port on the rear of the chassis. For more information, refer to the “Installation” chapter in the Mitel 5000 Installation and Maintenance Manual, part number 580.8000. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Record-A-Call Record-A-Call If your system is programmed with a Record-A-Call application, the endpoints can be programmed to use the Record-A-Call feature. It allows users to enter a feature code whenever they want to record an ongoing call in their designated Record-A-Call mailbox. Users can retrieve the recorded messages later, just as they would any other mailbox messages. NOTE The Record-A-Call standard feature is required.
Chapter 6: End User Features Redial As with any other conference call, any inside party involved in a Record-A-Call conference can use the Transfer, Agent Help, or other features. However, if any inside party has enhanced speakerphone enabled, the enhanced mode will be disabled when the conference begins and must be re-enabled if desired. NOTICE Pressing Hold during a record-a-call will terminate the record-a-call.
Chapter 6: End User Features Redirect Call Table 6-8. Endpoint Responses with Last Number Saved, Last Number Dialed (Continued) Endpoint status when Redial feature is used Endpoint has Last Number Saved Endpoint has Last Number Dialed After selecting a trunk and dialing one or more digits Releases the current call, seizes a trunk using the saved trunk access code, and dials the saved telephone number.
Chapter 6: End User Features Reminder Messages Reminder Messages Reminder messages are set to signal an endpoint at a specified time. The user can select one of 20 different messages and set the reminder time up to 24 hours in advance. These messages can be reprogrammed by the system administrator or by using an administrator endpoint. NOTE Reminder messages are available on Mitel proprietary endpoints only. At the programmed time, the reminder message signals the endpoint with 8 short tones.
Chapter 6: End User Features Remote Programming Remote Programming The Remote Programming feature allows a user to place an endpoint in DND mode or forward the endpoint’s calls, either from another endpoint or through DISA. Each endpoint has a password to limit access to this feature. For information about DISA, see “Using DISA” on page 5-11. For feature usage instructions, refer to the applicable endpoint user guide.
Chapter 6: End User Features Speed Dial Speed Dial The system provides the following Speed Dial features: • System Speed Dial: Up to 1000 System Speed Dial numbers of 48-digits each can be stored. Endpoints programmed with access to this feature can dial any of the numbers on the list. The Administrator maintains the System Speed Dial list. • Station Speed Dial: Each endpoint user can program up to 10 Speed Dial numbers of 16digits each.
Chapter 6: End User Features Speed Dial Station Speed Dial An endpoint user can program up to 10 Station Speed Dial numbers of 16-digits each. Single line endpoints use Speed Dial location codes (0–9). Display endpoints use Speed Dial buttons, if programmed in the endpoint’s keymap, or location codes 0–9. Together, the lamps in the endpoint Station Speed Dial buttons create a busy lamp field that indicates the status of the endpoints programmed under the buttons.
Chapter 6: End User Features Transfer – Call Transfer Transfer – Call Transfer The following sections provide information on the Transfer feature. For feature usage instructions, refer to the applicable endpoint user guide. Feature Codes There are two feature codes for transferring intercom and outside calls to other endpoints, Voice Processing applications, hunt groups, off-node devices, or outside telephone numbers.
Chapter 6: End User Features Transfer – Call Transfer Transfer Timers The following five timers affect the Call Transfer feature: • Transfer Attendant: When an attendant transfers a call, this timer limits the time a transferred call rings unanswered before it recalls the attendant. The default value of this timer is 30 seconds. It can be reprogrammed to any value between 10–255 seconds.
Chapter 6: End User Features Transfer – Call Transfer Transfer to Ring Transfer to Ring transfers calls to other endpoints. Transfer to Hold A call transferred to hold at an endpoint does not ring or send a display message while holding. After the Hold timer expires, the endpoint rings or sends call waiting signals. Also, calls transferred to hold do not recall the transferring party; they recall the receiving party’s attendant if unanswered after the Hold and Recall timers expire.
Chapter 6: End User Features User-Programmable Feature Buttons User-Programmable Feature Buttons Individual endpoint buttons can be designated as “user-programmable” in the keymaps during database programming. The system administrator can program the default feature codes, and the endpoint user can reprogram the feature codes as desired. For programming instructions, refer to the “Endpoints and Devices” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006.
Chapter 7: Voice Processing Features Voice Processing Features Chapter 7: Voice Processing Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3 Mitel Voice Processing Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3 Supporting Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7: Voice Processing Features Scheduled Time-Based Application Router (STAR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-26 Voice Mail And Message Notification/Retrieval Applications . . . . . . . . . . . . . . . . . . . . . . . . .7-28 Mailboxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-29 Extension IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7: Voice Processing Features Introduction Introduction Mitel voice mail is an integrated component of the Mitel 5000 system. This chapter provides feature instructions for Basic Voice Mail (BVM) and Enterprise® Messaging (EM) voice mail systems. The Mitel 5000 also supports NuPoint Messenger. See the following section for product descriptions. Mitel Voice Processing Systems NOTICE Voice Processing Unit (VPU) end of sale. VPU is no longer supported for Mitel 5000 v3.0.
Chapter 7: Voice Processing Features Introduction Supporting Documentation Because various voice mail products work with the Mitel 5000 system, this section does not include voice mail subscriber (user) feature instructions. Refer to the appropriate voice mail user guide for your system for feature descriptions and instructions.
Chapter 7: Voice Processing Features BVM Voice Processing System BVM Voice Processing System Built-in on the Mitel 5000 platform, BVM runs on the Linux® operating system and provides voice messaging services. On Mitel CS-5200 and CS-5400 platforms, language prompts, BVM messages, system applications, and the customer database are stored on a compact flash-type memory card that resides in the base server.
Chapter 7: Voice Processing Features BVM Voice Processing System BVM Port Licensing and IP Resource Allocation IMPORTANT Because BVM ports are licensable, customers upgrading their port capacity are required to purchase the corresponding licenses. Mitel 5000 platforms support up to 16 licensed BVM ports.The ports are allocated dynamically up to the number of valid BVM licenses. Ports are licensed four at a time and may not be licensed individually.
Chapter 7: Voice Processing Features BVM Voice Processing System BVM Voice Message Storage Capacities NOTICE Mitel 5000 v3.0 systems or later require a minimum 512MB compact flash-type memory card. If this system is currently using a 256MB compact flash-type memory card, upgrade the card to either 512MB (part number 841.0274) or 1024MB (part number 841.0273). The amount of message storage, which is allocated for each user as a quota of the total storage capacity, is programmed in DB Programming.
Chapter 7: Voice Processing Features BVM Voice Processing System BVM on the Mitel CS-5600 Platform On the CS-5600, BVM supports—with appropriate licensing—up to 16 voice mail ports. With v2.x running on an Mitel 5600 platform, BVM is hosted on the PS-1. BVM on the PS-1 can be configured with 0, 4, 8, 12, or 16 ports in accordance with feature licensing. Table 7-1 shows the relationship between the number of valid BVM licenses and the maximum number of active BVM ports in a CS-5600 system.
Chapter 7: Voice Processing Features Interaction Between Systems Interaction Between Systems When using an external voice processing system, the software and hardware that control the Voice Processing applications is located in the external voice processing system. The Mitel 5000 system must be able to communicate with external voice processing systems for the applications on those systems to function.
Chapter 7: Voice Processing Features Voice Processing System Networking Voice Processing System Networking The voice processing system network is programmed separately from the phone system network. Up to 100 nodes can exist on the voice processing system network. The following programming fields provide networking support: • Node: The Network Node table contains information about each Voice Mail node in the network.
Chapter 7: Voice Processing Features Voice Processing System Networking VPIM Networking Requires EM v2.0 or later. Voice Profile for Internet Mail (VPIM) protocol communicates with other voice processing systems using the VPIM protocol. VPIM networking requires the Voice Processor Messaging Networking software license. NOTE NuPoint Messenger systems must be configured to use the G.721 codec when using VPIM to communicate with BVM or EM systems.
Chapter 7: Voice Processing Features Voice Processing System Networking Network Operation Overview The Network Node table is used to define information about each node in the Voice Mail network. Before the local node can send messages to a remote node, there must be an entry in the Network Node table for the remote node. To leave messages for mailboxes on remote nodes, you must have “network mailboxes” on the local node.
Chapter 7: Voice Processing Features Time Slot Groups Time Slot Groups BVM and EM systems only. Each application is assigned to a “Time Slot Group” which determines the maximum number of voice channels that are used by the applications in that group. Voice channels are used for processing calls between the phone system and the Voice Processing applications.
Chapter 7: Voice Processing Features Voice Processing Applications Voice Processing Applications BVM and EM systems only. Voice Processing can be used for any of the following applications: • Automated Attendant: The Automated Attendant Provides automated call answering services. Calls can be transferred, forwarded, or directly ring-in to an automated attendant.
Chapter 7: Voice Processing Features Voice Processing Applications Automated Attendant BVM and EM systems only. Automated Attendant is a programmable application that provides automated call answering services. Calls can be transferred, forwarded, or directly ring-in to an automated attendant. Calls to the automated attendant application are processed as shown in the following flow diagram. CALL TO AUTOMATED ATTENDANT Automated Attendant answers and plays a greeting followed by a menu of options.
Chapter 7: Voice Processing Features Voice Processing Applications • Use the directory: If the caller does not know the extension or mailbox number of the desired party, he or she can spell the name using the keypad buttons and “look up” the number in the directory. (This option can be disabled in the database. Or, if there are no names recorded for the individual mailboxes or for the system’s extension IDs, this option is not provided.) Directory names can be sorted by first or last name.
Chapter 7: Voice Processing Features Voice Processing Applications Automated Attendant Recall Destination When an endpoint receives a call that has been routed through the automated attendant, the call is handled as a transferred call, and the display shows TFR FROM . If the call is not answered before the Transfer Voice Processor timer expires, the call recalls the automated attendant’s recall destination.
Chapter 7: Voice Processing Features Voice Processing Applications Call Routing Announcements BVM and EM systems only. The Call Routing Announcement (CRA) application can be used as a simple playback device that plays a message and then hangs up to disconnect the call. This capability is especially useful for programming hunt group announcement and overflow stations.
Chapter 7: Voice Processing Features Voice Processing Applications Figure 7-2. Sample CRA Tree EXT 2500: “Thank you for calling X Company, if you know the party’s extension number, you may dial it now. For a company directory, press #. For Sales information press 3. For technical support, press 4.
Chapter 7: Voice Processing Features Voice Processing Applications Use the following guidelines to design an effective CRA application: • Design with the caller in mind, not just the information you want to include. • Keep menus as simple as possible, with four or fewer options per menu. • Number options sequentially and do not skip numbers. List “transfer to operator” last. • Use consistent digits for options, such as 1 for Yes, 2 for No, and 0 for the operator. • State the option before the digit.
Chapter 7: Voice Processing Features Voice Processing Applications CRA Custom Audiotex Recordings When accessed, the CRA application plays a custom audiotex recording and then hang up. CRAs are recorded using the Voice Mail System Administrator’s mailbox. For more information, refer to the Mitel 5000 Endpoint and Voice Mail Administrator Guide, part number 580.8001. Each announcement is assigned to use a “custom greeting” number in database programming.
Chapter 7: Voice Processing Features Voice Processing Applications • Select Fax Document: (Not used for Timeout and not available if there are no fax documents in the system.) Selects a specific document for faxing. Callers should be prompted to select this digit with a recording that tells them the name of the document. For example, “For a price list, press 2.” This Action must be accompanied by an End Fax Selection Action and should also be accompanied by a Cancel Fax Selection Action.
Chapter 7: Voice Processing Features Voice Processing Applications Digit Translation Nodes BVM and EM systems only. A “digit translation node” is a digit translation destination that allows further digit translation options. Unlike extension and mailbox destinations, a digit translation node does not move the call to a specific location. Instead, it offers additional dialing options. A digit translation node can use any of the Actions, including transfers to other digit translation nodes.
Chapter 7: Voice Processing Features Voice Processing Applications Multilingual Capability BVM and EM systems only. The multilingual capability provides a choice between American English, British English, Spanish, and Japanese prompts and displays. The system selects the language to use for each call, as determined by the trunk, endpoint, and Voice Processing programming.
Chapter 7: Voice Processing Features Voice Processing Applications Multilingual Features on Network Operation Nodes do not need to match languages because the Voice Mail system installs any existing language prompt, not just the languages designated as Primary or Secondary.
Chapter 7: Voice Processing Features Voice Processing Applications Scheduled Time-Based Application Router (STAR) BVM and EM systems only. Scheduled Time-Based Application Routing (STAR) allows applications with alternate greetings and/or different programming that can be set up for holidays, weekends, and other scheduled events. A STAR application is basically a “routing table” for Voice Processing applications.
Chapter 7: Voice Processing Features Voice Processing Applications There are two entries for Labor Day and Memorial Day [Summer Bank Holiday and Spring Bank Holiday in Europe], and Christmas Day and Christmas Holiday overlap. The first entry in the table is checked first, and so on, until a match is found. So it is important that you program the applications in the correct order.
Chapter 7: Voice Processing Features Voice Processing Applications Voice Mail and Message Notification/Retrieval Applications Two application types are combined to provide the Voice Mail feature: Voice Mail and Message Notification/Retrieval. • Voice Mail: This application handles all calls that are directed to Voice Mail (other than the Message Notification/Retrieval application) placed by subscribers and non-subscribers. Callers hear the main company greeting, followed by a menu of available options.
Chapter 7: Voice Processing Features Voice Processing Applications Mailboxes BVM and EM systems only. A mailbox is a storage location that stores all messages that have been directed to it (including prompts, greetings, and special programming.) Each “Subscriber” (member of the voice message system) is assigned a unique mailbox number. At system default, the passwords are the same as the mailbox numbers. (For example, the default password for mailbox 1001 is “1001.
Chapter 7: Voice Processing Features Voice Processing Applications • BVM Play-Only Mailbox: Applies to BVM unassociated mailboxes only. The BVM “playonly” mailbox option prevents the caller from leaving a message. The “play-only” mailbox is similar to an “announcement-only” application where it plays the designated greeting once and then the call automatically disconnects after the greeting finishes playing.
Chapter 7: Voice Processing Features Group Lists Extension IDs BVM and EM systems only. Extension IDs are used when transferring calls through the Automated Attendant or using the Extension Directory. The extension ID allows callers to be transferred to endpoints and applications that do not have mailboxes. It also allows the endpoint or application to have a recorded name in the directory.
Chapter 7: Voice Processing Features Transfer Methods Transfer Methods BVM and EM systems only. Calls transferred from the Automated Attendant or a CRA application can be screened, announced, or unannounced. When an automated attendant or CRA application receives a call, and the caller enters an extension number, the endpoint programmed Transfer Method determines how the call is transferred. The Transfer Method flags can be programmed in the database.
Chapter 7: Voice Processing Features Cascading Remote Message Notification Cascading Remote Message Notification BVM and EM systems only. Remote Messaging is a subscriber feature that is enabled through database programming. Subscribers may program a series of specific telephone numbers (a “cascade”) for the Voice Mail system to call when new messages are received by their mailboxes. See page 7-36 for a sample notification cascade setup.
Chapter 7: Voice Processing Features Cascading Remote Message Notification All Messages, Priority Only, and Each New Message Flags When the mailbox is being programmed for remote notification, message notification can be set to place the notification call when any message is received or only when priority messages are received. (This defaults to “All Messages.
Chapter 7: Voice Processing Features Cascading Remote Message Notification Notification Numbers Each cascade level has a programmed notification number that can be an extension number or an outside telephone number. When an outside telephone number is used, the system accesses an outgoing trunk using the code programmed for that level that contains a preprogrammed trunk access code and followed by an outgoing access termination feature code, if needed.
Chapter 7: Voice Processing Features Cascading Remote Message Notification Sample Notification Cascade Step 4d on page 7-35 shows how each level in a Primary and Alternate cascade is programmed to meet a customer’s needs. In the example, the pager dial string (9619000*MN#) includes the Voice Processing telephone number (961-9000), an asterisk to separate digits, the mailbox number (M), the number of messages in the mailbox (N), and a pager termination digit (#). Table 7-4.
Chapter 7: Voice Processing Features Cascading Remote Message Notification Table 7-4. Example Notification Cascade Entries (Continued) Customer Wants: Cascade Level: Program These Parameters: After business hours and during the week, customer wants to be notified for only priority messages, each time a priority message is received...
Chapter 7: Voice Processing Features Directories Directories BVM and EM systems only. There are two types of Voice Processing directories that can be enabled (or disabled) in the system: Mailbox and Extension. The Voice Mailbox Directory: A list of mailbox subscribers, their recorded names, and mailbox numbers. For programming instructions, refer to the “Voice Processor System Programming” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006.
Chapter 7: Voice Processing Features Directories Locating a Name This section details the following methods to locate a name: • “Entering a Name” below • “Changing the First/Last Name Search” on page 7-40 • “Listening to the Next/Previous Name” on page 7-40 For end-user instructions, refer to the Enterprise Messaging, Basic Voice Mail, and Embedded Voice Mail Card User Guide, part number 835.3205. Entering a Name There are two methods used for entering a name: Quick Spell and Exact Spell.
Chapter 7: Voice Processing Features Directories Changing the First/Last Name Search Each directory can be programmed to be organized by last name or by first name. Callers accessing a directory receive system voice prompts that ask them to enter the first or last name of the person for whom they wish to leave a message.
Chapter 7: Voice Processing Features Music-On-Hold Parameters Music-On-Hold Parameters BVM and EM systems only. The system can be programmed to determine the music source a caller hears based on the device for which the caller is waiting. By default, the system determines the music source based on the trunk group on which the call resides.
Chapter 7: Voice Processing Features Unified Messaging OSE Unified Messaging OSE EM systems only. Unified Messaging Open Standards Edition (OSE) is a client-free Unified Messaging distribution for the Mitel Enterprise Messaging voice messaging server. With Unified Messaging OSE, the e-mail client can be any Internet Message Access Protocol (IMAP) v4 compliant client that is configured to connect to the IMAP server located on Enterprise Messaging. For Unified Messaging OSE v2.
Chapter 7: Voice Processing Features SIP Peer Voice Mail Features SIP Peer Voice Mail Features SIP Peer Voice Mail provides access to a SIP messaging system. SIP Peer Voice Mail supports the features described in the following sections. SIP Peer Operating State A SIP peer has an operating state that provides its availability. The SIP peer operating states are: • In Service (INS): The SIP peer is available and in service. • Out–of–Service (OOS): The SIP peer is temporarily unavailable.
Chapter 7: Voice Processing Features SIP Peer Voice Mail Features SIP View Diagnostics Feature Code 9987 [9187] Use the existing diagnostics feature code 9987 [9187] “Diagnostics – SIP View” to view the incoming and outgoing SIP peer messages. This feature exists today for SIP trunks. This diagnostic code changes the SIP values system-wide which determines the output that appears in Message Print and diagnostic log files. To change the SIP values system-wide through the administrator endpoint: 1.
Chapter 8: Diagnostic Features Diagnostic Features Chapter 8: Diagnostics Features Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-5 Audio Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-6 Audio Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8: Diagnostic Features Administrative Web Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-30 General Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-30 IP Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-31 IP Endpoint Web Session . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8: Diagnostic Features Digital Trunk Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-49 Navigating Through the Digital Trunk Diagnostics Screens . . . . . . . . . . . . . . . . . . . . . . . . . .8-49 DMU Main Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50 Module Selection Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8: Diagnostic Features Port – Channel Selection – Channel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-95 Port – T1 Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-96 Port – Call Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-97 Port – ISDN Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8: Diagnostic Features Introduction Introduction System diagnostics are provided to assist trained personnel in monitoring and maintaining the functional health of the system. This chapter provides fundamental instruction for interpreting the output data from the utilities. Depending on the problem and the what data has been collected during troubleshooting, technical support personnel may require additional information to perform their analysis.
Chapter 8: Diagnostic Features Audio Diagnostics Audio Diagnostics The Audio Diagnostics feature (default feature code 320) allows a user to generate diagnostics information about audio problems. Once the Audio Diagnostics feature is initiated, the user is prompted to answer questions about the audio problems by pressing endpoint dialpad buttons. Based on the user’s selections, the system generates Alarm 128, which displays on the Administrator’s endpoint and on the chassis LCD panel.
Chapter 8: Diagnostic Features Audio Diagnostics Audio Direction After selecting the audio problem, the system prompts the user to choose the direction of the audio problem.
Chapter 8: Diagnostic Features Audio Diagnostics Using the Audio Diagnostics Feature Only endpoints with the Audio Diagnostics endpoint flag enabled (System\Devices and Feature Codes\Endpoints\Local\\Flags) can use the Audio Diagnostics feature. To use the Audio Diagnostics feature: NOTE 1. Only 6-line display endpoints have the menu buttons mentioned in the following instructions. The 2-line display and non-display endpoints must use the numeric entries to use the Audio Diagnostics feature.
Chapter 8: Diagnostic Features Audio Diagnostics If the Record-A-Call feature is enabled for your endpoint, the display shows WOULD YOU LIKE TO RECORD CALL? WOULD YOU LIKE TO RECORD CALL? YES NO 4. If the Record-A-Call feature is available, you have the option of recording the call. Take one of the following actions: • Press the desired menu button. • Or, press the dialpad button that corresponds to one of the following responses: o Press 1 to record the call.
Chapter 8: Diagnostic Features Diagnostics Monitor Support Diagnostics Monitor Support The Diagnostics Monitor Utility includes the following features: • Dump Extension: SIP gateway trunks is included in the Dump Extension option (System Monitor\Dump Extension).
Chapter 8: Diagnostic Features Busy Out Manager Busy Out Manager When troubleshooting, you can use the Busy Out Manager feature to busy-out ports on T1M, T1M-2, and BRM-S modules. The Busy Out Manager displays all ports on the selected module as well as what type of port is configured. For programming instructions, refer to the “System Diagnostics” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006.
Chapter 8: Diagnostic Features Loop Loss Measurement Test Loop Loss Measurement Test The Loop Loss Measurement Test measures and reports loop loss on loop start trunks by using Digital Signal Processor (DSP) firmware and Call Processing (CP) diagnostic software on the 5000 system. The test measures the level of a fixed tone, typically provided by the Central Office (CO), and reports the drop from the fixed tone.
Chapter 8: Diagnostic Features Hybrid Balance Test for Analog Loop Start Trunks Hybrid Balance Test for Analog Loop Start Trunks The Hybrid Balance Test automatically measures and assigns the best hybrid balance setting for each type of analog trunk. Mitel recommends running the HB Test when installing the system and whenever troubleshooting echo problems. To obtain and maintain optimal Hybrid Balance Settings, do the following: • Perform the test on each LSM port at initial installation of the system.
Chapter 8: Diagnostic Features System Error/Message Printing System Error/Message Printing The system has a self-diagnostic feature that monitors the system. When a system fault or other noteworthy condition is detected, the software determines the impact of the condition and classifies it as an alarm (major or minor) or other message type. If the Message Print option is enabled, the messages are available on the Diagnostics Monitor.
Chapter 8: Diagnostic Features System Error/Message Printing • Messages may not be printed in time sequence order on remote nodes. The order of an incoming message print depends on how the message print was routed to the destination node. Therefore, a message print could possibly arrive at the destination message print node out of order.
Chapter 8: Diagnostic Features System Error/Message Printing History and Message Print Queues The history queue can store up to 4 MB of information. In addition, the Message Print queue can store up to 300 KB. Because downloading 4 MB of history queue information over a modem would take too long, the 4 MB is separated into 500 KB blocks. Each of these blocks contains start and stop time/ date stamps, allowing you to determine which block contains the required information for reviewing site issues.
Chapter 8: Diagnostic Features Database Change Log Database Change Log The Database Change log provides details on user changes to DB Programming. The log details recent user changes to facilitate troubleshooting. The Database Change log is written and maintained by the Mitel 5000. It is stored on the Mitel 5000 and is accessible through the Administrative Web Session (AWS) interface. For more information about AWS functionality, refer to AWS Help.
Chapter 8: Diagnostic Features Database Change Log How to Read the Database Change Log The Database Change Log entries are categorized as follows: • “General” below • “Header and Footer” below • “Field Changes” on page 8-19 • “Other Changes” on page 8-20 • “Tools Menu” on page 8-23 • “Operations Menu” on page 8-24 • “View Menu” on page 8-29 General This section details some general information about the Database Change Log: • Every log entry begins with the date and military time: [2008-01-30 11:20:11 D
Chapter 8: Diagnostic Features Database Change Log Field Changes This section details the field changes in the Database Change Log. Many database changes are made through editing a field. When you edit a control and complete the edit, the change is saved to the database. These changes are always associated with a field in a folder hierarchy.
Chapter 8: Diagnostic Features Database Change Log Other Changes This section details other changes in DB Programming: • Device Additions and Deletions: o The device type and extension(s) always appear. o The hardware address appears when it is available. o Items added in a batch are grouped on one line only when they do not have hardware addresses. A batch item with a hardware address appears on its own line.
Chapter 8: Diagnostic Features Database Change Log • List Additions and Deletions and Drag, Drop, and Move: o The item type always appears. o The extension appears for lists that have an extension. o Added, deleted, or moved items are listed by ID or extension.
Chapter 8: Diagnostic Features Database Change Log • Copy and Paste: o The devices copied from and to are listed along with a list of attributes included in the copy.
Chapter 8: Diagnostic Features Database Change Log Tools Menu This section details the Tools Menu options of the Database Change Log: • Configuration Wizard: o Consists of a multi-line entry. o “Configuration Wizard” appears as the first entry and a header. o A line of text appears for each board and device configured and for each programming change.
Chapter 8: Diagnostic Features Database Change Log o Example of results from the T1/PRI Networking Wizard: [2008-02-06 06:33:58 DBP] Networking Wizard: Set Node to 168 [Inter-Tel 3.0.2.5] Added 97501 Set Description to Conn to Node 2 Set Username to Set Reference Clock List to 2 [Inter-Tel 3.0.2.5\02.01] Added 94004 (B-Channel) [Inter-Tel 3.0.2.5\02.02] Added 94005 (B-Channel) [Inter-Tel 3.0.2.5\02.03] Added 94006 (B-Channel) [Inter-Tel 3.0.2.5\02.04] Added 94007 (B-Channel) [Inter-Tel 3.0.2.5\02.
Chapter 8: Diagnostic Features Database Change Log • Backup Database Save: o “Begin Backup Database Save” appears as the first entry. o The following entry consists of one of the following messages: o – “Completed with Success” when the operation completes successfully. – “Terminated with Warning – ” when the operation terminates with a warning. – Terminated with Failure – ” when the operation fails.
Chapter 8: Diagnostic Features Database Change Log • Default Database: o “Begin Default Backup Database” appears as the first entry. o The next entry consists of one of the following messages: – “Completed with Success” when the operation completes successfully. – “Terminated with Warning – ” when the operation terminates with a warning. – Terminated with Failure – ” when the operation fails. o “Default Database” appears as the third entry.
Chapter 8: Diagnostic Features Database Change Log • Export/Import Devices: o “Begin Export” or “Begin Import” appears as the first entry when a device is exported or imported. o The nodes are listed next, followed by the device types. o After the list of device types, “Results” appears with a timestamp, followed by the specific results for each node. o The last entry includes one of the following messages: o – “Completed with Success” when the operation completes successfully.
Chapter 8: Diagnostic Features Database Change Log • Upload Software License: o “Begin Upload Software License” appears as the first entry along with the list of differences between the current license and the new license that will be uploaded. o The second entry includes one of the following messages: o o – “Completed with Success” when the operation completes successfully. – “Terminated with Warning – ” when the operation terminates with a warning.
Chapter 8: Diagnostic Features Database Change Log • Voice Processor Save or Restore: o “Voice Processor [Save/Restore] () [to|from] ” appears as the first entry (where is the radio button selected, for example Audiotex Recordings, Group Lists, Mailbox Information, etc.). o The second entry appears with the details about the saved or restored type of information. The example below includes Mailbox Information.
Chapter 8: Diagnostic Features Administrative Web Session Administrative Web Session NOTES For other information about the Web session that is not mentioned here, refer to AWS Help. Administrative Web Session Pages support Microsoft® Internet Explorer® (IE) through version 7. The Mitel 5000 has a Web interface that provides a comprehensive view of the communication server and enables the technician to gather diagnostic information about applications that are running on the system.
Chapter 8: Diagnostic Features Administrative Web Session IP Resources The Processor Module IP Resource pages comprise a large part of the diagnostics shown in the Web pages. These diagnostics are separate from Call Processing diagnostics found in System Manager, and display only information local to the application. IP Endpoint Web Session Click on IPT Connection to open a new window. Default username “IPT,” password “iptpassw.
Chapter 8: Diagnostic Features Administrative Web Session UPS Information The UPS Information section displays the current state of the UPS (online, on-battery, low battery) as well as additional vendor- and model-specific UPS status information. The UPS Information section is available for Mitel 5000 systems. In CS-5200 and CS-5400 configurations, the section appears on the Base Server AWS page. In a CS-5600 configuration, this information appears on the PS-1 AWS page.
Chapter 8: Diagnostic Features Administrative Web Session Channel Status In the Status page, you can select one of the ports to view the Channel Status page. This displays both the current channel type and the current status of each channel on that port. The channel status page of an “Unequipped” port is not accessible. The value displayed in the Type field varies depending on how the port is configured. Table 8-4.
Chapter 8: Diagnostic Features Administrative Web Session Echo Canceller Settings While viewing the Channel Status page for a particular port, you can view the echo canceller settings for an individual channel by clicking the channel number. The T1M-2 supports a system-side echo canceller and a span-side echo canceller. The page for a particular channel displays two lists of settings along with the currently programmed values for that setting.
Chapter 8: Diagnostic Features Administrative Web Session Session Information Page When you click one of the session IDs in the Session Information page for either the Processor Module or Expansion Module, the Session Details page appears. There is a field named “ESSL” at the end of the list. The ESSL refers to the Echo Suppression Sensitivity Level and has the possible values of 0, 1, 2, 3. These values correspond to Off, Low, Medium, or High. If the feature is disabled, the field shows “Disabled.
Chapter 8: Diagnostic Features Administrative Web Session Table 8-6. Log Files Page Logs (Continued) Category System Health Report Name alm_daily.log alm_daily_xml.log alm_status.log Description Contains Mitel 5000 system information and statistics that is e-mailed to the desired location daily. This feature is intended for support center personnel, not for endcustomers. The information in this report helps the recipient to diagnose and troubleshoot problems with the Mitel 5000 system.
Chapter 8: Diagnostic Features Diagnostics Monitor Table 8-6. Log Files Page Logs (Continued) Category Name Description Shared Resource Allocation Logs cp_sra_log Provides information about VoIP allocations, stale IP resources, and reservations. Log Archive ____.
Chapter 8: Diagnostic Features Diagnostics Monitor • File Menu: When there is no active socket connection open, the only selectable menu options are New Connection, Print Setup, and Exit. Selecting New Connection or using CTRL-N, presents the New Connection Dialog to the user. When an active socket connection exists, the Save to File, Log to File, Close Connection, and Print options are available. NOTE The Print options are currently not supported.
Chapter 8: Diagnostic Features Diagnostics Monitor ISDN Diagnostics NOTE ISDN Diagnostics configuration changes made from the Diagnostics Monitor are temporary. After a module is reset, its corresponding ISDN Diagnostics configuration defaults to the system database configuration. Therefore, permanent changes to the ISDN Diagnostics configuration should be done through DB Programming. The ISDN Diagnostics is a utility that is selected from the optional socket connections provided in Diagnostics Monitor.
Chapter 8: Diagnostic Features Message Print Message Print Message Print should always be enabled because it remains one of the main diagnostic utilities that you use when troubleshooting the system. New and modified system messages and alarms are output in the Mitel Message Print application. For complete details of affected fields, identified causes, and recommended actions, refer to the Message Print Diagnostics Manual, part no. 550.8018.
Chapter 8: Diagnostic Features Message Print In addition to the messages, the following error indications occur in the event of a system alarm: • If a major system alarm occurs, MAJOR ALARM appears on all display endpoints. If all endpoints on the system are inoperative, the alarm message is sent to call processing over IP. • A minor alarm sends a message to the primary attendant and to administrators, if programmed to receive alarms.
Chapter 8: Diagnostic Features Station Message Detail Recording (SMDR) Station Message Detail Recording (SMDR) Station Message Detail Recording (SMDR) is a system feature that provides a detailed record of outgoing and incoming calls. The system records only valid calls. Outgoing calls become valid when the Valid Call timer expires or polarity reversal is detected (depending on system programming). Outgoing calls become valid immediately if placed on hold or transferred.
Chapter 8: Diagnostic Features VoIP DSP Manager VoIP DSP Manager The VoIP DSP Manager dump, shown in Figure 8-1, shows the number of IP resources allocated according to type, along with the number of reserved IP resources according to type. The information indicates IP resource usage by devices on the system at any given point in time. Figure 8-1. Example of VoIP DSP Manager Dump Mitel ® 5000 Reference Manual – Issue 3.
Chapter 8: Diagnostic Features IP Device Resource Manager IP Device Resource Manager The IP Device Resource Manager dump shows call type information, as shown in Figure 8-2. Figure 8-2. Example of IP Device Resource Manager Dump Page 8-44 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 8: Diagnostic Features Allocated VoIP DSPs Allocated VoIP DSPs The Allocated VoIP DSPs dump, shown in Figure 8-3, details information about all allocated VoIP resources. This dump is used to find information such as the device that allocated the resource, the resource's encoding settings, and the allocation purpose. In previous versions of Diagnostics Monitor Utility, this dump information was included with the VoIP DSP Manager dump.
Chapter 8: Diagnostic Features Allocated VoIP DSPs Dump VoIP DSP The VoIP DSP dump, shown in Figure 8-4, shows a list of IP resources owned by a specified IP device. The user is prompted to enter the extension of the IP device. Figure 8-4. Example of VoIP DSP Dump IP Device Extension Page 8-46 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 8: Diagnostic Features Allocated VoIP DSPs IP Resource Statistics The IP Resource Statistics dump, shown in Figure 8-5, contains the current IP resource sharing status, max (high watermark) allocation values, and average allocation for the last 5, 20, and 60 minutes. For further information, refer to online Help. NOTE The statistics provided are calculated on an exponential running average function similar to Linux load average numbers. Figure 8-5.
Chapter 8: Diagnostic Features UPS Monitoring IPDRM Resource Statistics Figure 8-6 shows an example of the IPDRM Resource Diagnostics Dump. For more information, refer to Mitel 5000 DB Programming Help. Figure 8-6. IPDRM Resource Diagnostics Dump UPS Monitoring The Diagnostics Monitor Reset Log shows that the shutdown was caused by a UPS power failure detection. Page 8-48 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Digital Trunk Diagnostics Diagnostic data is available through the Diagnostics Management Utility (DMU) for trunks attached to the single-port T1/E1/PRI Module (T1M), the Dual T1/E1/PRI Module (T1M-2), and the Basic Rate Module (BRM-S) that supports the S/T interface of Integrated Services Digital Network (ISDN) trunks.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics DMU Main Screen The DMU Main Menu screen shows the Digital Trunk Diagnostics option, as shown in Figure 87. Figure 8-7. Diagnostics Management Utility (DMU) Main Screen Page 8-50 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Module Selection Screen Selecting the Digital Trunk Diagnostics option displays the Module Selection screen, as shown in Figure 8-8. From the Module Selection screen you select the bay of the installed digital trunk module (T1M, T1M-2, or BRM-S) you want to analyze. This screen allows you to select the Digital Trunk module (T1M, T1M-2, or BRM-S) and connect to its DMU diagnostics screens. Figure 8-8.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics The screen displays the source used as the System Reference Clock. Valid sources include: • Internal (Motherboard) • Bay x - T1M • Bay x - T1M-2 Port • Bay x - BRM-S Connecting to module diagnostics may be rejected by presenting the Module Selection Rejection screen if the maximum number of five connections has already been established with that module. See Figure 8-9. Figure 8-9.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Dual T1/E1/PRI Module (T1M-2) Diagnostics Screens The following sections describe the DMU screens that support Dual T1/E1/PRI Module diagnostics. This screen periodically refreshes options D and E. Main Screen This section describes the main screen for Dual T1/E1/PRI Module (T1M-2) diagnostics. To display the T1M-2 diagnostics main screen: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Status The following section describes the Status screen for the T1M-2 module diagnostics. This screen refreshes periodically. To display the Status screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Status. The STATUS screen appears, as shown in Figure 8-11. Figure 8-11.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Channel Number rows count to the maximum number of channels for the corresponding port type: • 23 for T1/PRI • 24 for T1 • 30 for E1/PRI In addition to the general navigation guidelines described in “Navigating Through the Digital Trunk Diagnostics Screens” on page 8-49, the following controls apply: Pressing the S key or the s key transfers control to the SYNC Status screen. Mitel ® 5000 Reference Manual – Issue 3.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Status – Sync Status The following section describes the SYNC STATUS screen for T1M-2 modules. The SYNC STATUS screen shows the same information that the M8000 and M8001 System Message Print messages show but in a real-time format instead of a log format. For descriptions of the various Initial-Trouble/Red-Alarm conditions, refer to the Message Print Diagnostics Manual, part no. 550.8018. This screen refreshes periodically.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Busy Out The following section describes the Busy Out screen for the T1M-2 module diagnostics. This screen refreshes periodically. To display the Busy Out screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Busy Out. The BUSY-OUT screen appears, as shown in Figure 8-13. Figure 8-13.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics The Busy Out screen for T1M-2 module diagnostics shows the following elements: • Port 1 is highlighted and flashing upon entry to this screen. • The Channel Number identifies the channels available with the trunk programmed for the module port. • The Status line identifies the status of the channel above it. • The Busy-out Tag line identifies the Busy Out condition of the channel above it.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Version Information The following section describes the Version Information screen for T1M-2 module diagnostics. To display the Version Information screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Version. The Version Information screen appears, as shown in Figure 8-14. Figure 8-14.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] The following section describes the Port screen for T1M-2 module diagnostics. To display the Port screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Port. The Port screen appears, as shown in Figure 8-15. Figure 8-15. Port Screen for T1M-2 Module Diagnostics The Layer 1 option is highlighted upon entry to this screen.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Layer 1 The following section describes the Open Systems Interconnect (OSI) model Layer 1 screen for T1M-2 module diagnostics. This screen is useful to get a glance at a T1/E1/PRI port Layer-1 status and the channel activity on that port, all in one screen. This screen refreshes periodically. To display the LAYER-1 screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Channel Selection The following section describes the port Channel Selection screen for T1M-2 module diagnostics. When diagnosing a T1M-2 module, the Channel Selection screen presents underlined port-number fields. To display the Channel Selection screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Port. 4. Select Channels.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Channel Selection – Channel The following section describes the port Channel screen on T1M-2 module diagnostics. This screen refreshes periodically. To display a port Channel screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Port. 4. Select Channels. 5. Select the channel you want to diagnose.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – T1 Performance The following section describes the port T1 PERFORMANCE screen supporting T1M-2 module diagnostics. This screen is useful to view the same Hourly and Daily error counts that are available through the DB Programming. This screen refreshes periodically. To display a port T1 PERFORMANCE screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Call Statistics The following section describes the port CALL STATISTICS screen supporting T1M-2 module diagnostics. This screen refreshes periodically. To display a port CALL STATISTICS screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Port 1 or Port 2, as applicable. 4. Select Call Statistics.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – ISDN Diagnostics The following section describes the port ISDN Diagnostics screen supporting T1M-2 module diagnostics. To display a port Call Statistics screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Port 1 or Port 2, as applicable. 4. Select ISDN Diagnostics.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – ISDN Diagnostics – Data Link Status The following section describes the port ISDN Data Link Status screen supporting T1M-2 module diagnostics. This screen is useful to troubleshoot OSI model Layer 2 problems on an ISDN connection. The screen refreshes periodically. To display a port ISDN Data Link Status screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – ISDN Diagnostics – D-Channel Diagnostics The following section describes the port D-Channel Diagnostics screen supporting T1M-2 module diagnostics. The D-Channel Diagnostics screen allows you to enable or disable the DChannel Diagnostics for the current port. This screen refreshes periodically. To display a port ISDN Data Link Status screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – ISDN Diagnostics – D-Channel Diagnostics – Display The following section describes the port D-Channel Diagnostics Display screen supporting T1M2 module diagnostics. The D-Channel Diagnostics Display screen allows you to view the DChannel Diagnostics in real-time. To display a port D-Channel Diagnostics Display screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Loopback The following section describes the port Loopback screen supporting T1M-2 module diagnostics. The LOOPBACK screen allows you to put the current port into one of four loopback modes and to transmit and detect specific bit patterns. This screen refreshes periodically. To display a port Loopback screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Echo Canceller Selection The following section describes the port Echo Canceller Selection screen supporting T1M-2 module diagnostics. To display a port Echo Canceller Selection screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Port. 4. Select Port 1 or Port 2, as applicable. 5. Select Echo Canceller Channels.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port [1 or 2] – Echo Canceller Selection – Echo Canceller Status The following section describes the port Echo Canceller Status screen supporting T1M-2 module diagnostics. The Echo Canceller Status screen displays the status information for the selected echo canceller. This screen refreshes periodically. To display a port Echo Canceller Status screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics DSP Audio Diagnostics The following section describes the DSP (Digital Signal Processor) Audio Diagnostics Capture screen supporting T1M-2 module diagnostics. To display the DSP Audio Diagnostics screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select DSP Audio Diagnostics. The Diagnostics Capture screen appears, as shown in Figure 8-28. Figure 8-28.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics To obtain a DSP audio diagnostics capture: 1. Identify the extension of the endpoint on which an active call has poor quality audio, such as echo. See Figure 8-29. 2. Identify the extension of the trunk on which the call exists. See Figure 8-29. a. Using Diagnostics Monitor, generate a Manual Dump of Call Diagnostics. Connect a System Monitor to the Mitel 5000 system in question. b.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics 5. Select the bay identified in step 2 on page 8-73. In the example shown in Figure 8-31, this is bay 3. Only the T1M-2 (Dual T1/E1/PRI Module) can perform a DSP Diagnostics Capture. BRM-S, LSM-2, LSM-4, and T1M do not have this functionality. Figure 8-31. Digital Trunk Diagnostics Module Selection Screen 6. Select the DSP Audio Diagnostics option from the T1M-2 main menu, as shown in Figure 8-32. Figure 8-32.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics 9. Retrieve the capture. There are two ways to retrieve the capture -- either by downloading it from the Mitel 5000 system Web page, or by doing an ADD freeze. Assuming you have ADD setup, do a freeze from DB Programming, Diagnostics Monitor, or from an administrator endpoint. To retrieve the DSP diagnostics capture from the Web page, log into the Web page and navigate to Logging – Log Files.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics To set up DSP Audio Diagnostics: 1. In the Selection prompt, type 1 or 2 for each of the following five questions, and then type “.” and press Enter. Pressing Enter without typing a selection confirms the current setting. The program updates and returns to the Diagnostics Capture screen after you answer each question.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Clock Frequency The following section describes the Clock Frequency screen supporting T1M-2 module diagnostics. This screen refreshes periodically. To display the DSP Audio Diagnostics screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Clock Frequency. The CLOCK FREQUENCY screen appears, as shown in Figure 8-34. Figure 8-34.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection The following section describes the Timers Selection screen supporting T1M-2 module diagnostics. To display the Timers Selection screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Timers. The Timers Selection screen appears, as shown in Figure 8-35. Figure 8-35.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – DID Timers The following section describes the DID Timer Information screen that supports T1M-2 module diagnostics. This screen refreshes periodically. To display the DID Timer Information screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Timers. 4. Select DID Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – E&M Timers The following section describes the E&M Timer Information screen that supports T1M-2 module diagnostics. This screen refreshes periodically. To display the E&M Timer Information screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Timers. 4. Select E&M Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – Loop-Start/Ground-Start Timers The following section describes the Loop-Start/Ground-Start Timer Information screen that supports T1M-2 module diagnostics. This screen refreshes periodically. To display the Loop-Start/Ground-Start Timer Information screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Timers. 4.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – OPX Timers The following section describes the OPX (Off-Premises Extension) Timer Information screen that supports T1M-2 module diagnostics. This screen refreshes periodically. To display the OPX Timer Information screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2 module. 3. Select Timers. 4. Select OPX Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – Miscellaneous Timers The following section describes the Miscellaneous Timer Information screen that supports T1M2 module diagnostics. This screen refreshes periodically. To display the Miscellaneous Timer Information screen for T1M-2 diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M-2module. 3. Select Timers. 4. Select Miscellaneous Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics T1/E1/PRI Module (T1M) Diagnostics Screens The following sections describe the DMU screens that support the single-port T1E1/PRI Module diagnostics. This screen periodically refreshes option D. Main This section describes the main screen for single-port T1/E1/PRI Module (T1M) diagnostics. To display the T1M main screen: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Status The following section describes the STATUS screen for the T1M module. This screen refreshes periodically. To display the Status screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. From the Module Selection Screen select a Bay containing a T1M module. 3. From the T1M main screen, select A. Status. The STATUS screen appears, as shown in Figure 8-42. Figure 8-42.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics The SYNC Status field displays one of the following values: • RED-ALARM • SYNC • INIT-TRBL • Blank, if the port is unequipped • INIT-TRBL/RED-ALARM NOTE The RED-ALARM, INIT-TRBL, INIT-TRBL/RED-ALARM values blinks to gain the user's attention. The REF LED and BUSY LED fields display a value of OFF, ON, or blank, if the port is unequipped.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Sync Status The following section describes the SYNC STATUS screen for T1M (or T1M-2) modules. The SYNC STATUS screen shows the same information that the M8000 and M8001 System Message Print messages show but in a real-time format instead of a log format. For descriptions of the various Initial-Trouble/Red-Alarm conditions, refer to the Message Print Diagnostics Manual, part no. 550.8018. This screen refreshes periodically.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Busy Out The following section describes the BUSY-OUT screen for the T1M module diagnostics. This screen refreshes periodically. To display the BUSY-OUT screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. From the Module Selection Screen select a Bay containing a T1M module. 3. From the T1M main screen, select Busy Out. The BUSY-OUT screen for T1M appears, as shown in Figure 8-44. Figure 8-44.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics • Pressing the RIGHT ARROW from the last channel moves the cursor to the first channel in the port. • Pressing the UP ARROW or DOWN ARROW while a channel is selected selects the port. • If a port is selected, pressing the T key or the t key tags all channels in the port for busyout. • If a port is selected, pressing the U key or the u key untags all channels in the port for busy-out.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Version Information The following section describes the Version Information screen for T1M module diagnostics. To display the Version Information screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. From the Module Selection Screen select a Bay containing a T1M module. 3. From the T1M main screen, select Version. The Version Information screen appears, as shown in Figure 8-45. Figure 8-45.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port The following section describes the Port screen for T1M module diagnostics. To display the Port screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. From the Module Selection Screen select a Bay containing a T1M module. 3. From the T1M main screen, select Port. The Port screen appears, as shown in Figure 846. Figure 8-46.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – Layer 1 The following section describes the Open Systems Interconnect (OSI) model Layer 1 screen for T1M module diagnostics. The LAYER-1 screen is useful to get a glance at a T1/E1/PRI port Layer-1 status and the channel activity on that port, all in one screen. This screen refreshes periodically. To display the Layer 1 screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – Channel Selection The following section describes the port Channel Selection screen on T1M module diagnostics. To display the Channel Selection screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. From the Module Selection Screen select a Bay containing a T1M module. 3. From the T1M main screen, select Port. 4. From the Port screen, select Channels.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – Channel Selection – Channel The following section describes the port Channel screen that supports T1M module diagnostics. This screen refreshes periodically. To display the port Channel screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Port. 4. Select Channels. 5. Select the channel you want to diagnose.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – T1 Performance The following section describes the port T1 PERFORMANCE screen supporting T1M module diagnostics. This screen is useful to view the same Hourly and Daily error counts that are available through the DB Programming. This screen refreshes periodically. To display a port T1 PERFORMANCE screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Port.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – Call Statistics The following section describes the port CALL STATISTICS screen supporting T1M module diagnostics. This screen refreshes periodically. To display a port CALL STATISTICS screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Port. 4. Select Call Statistics. The CALL STATISTICS screen for the port appears, as shown in Figure 8-51.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – ISDN Diagnostics The following section describes the port ISDN Diagnostics screen supporting T1M module diagnostics. To display a port ISDN Diagnostics screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Port. 4. Select ISDN Diagnostics. The ISDN Diagnostics screen for the selected port appears, as shown in Figure 8-52. Figure 8-52.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – ISDN Diagnostics – Data Link Status The following section describes the port ISDN Data Link Status screen supporting T1M module diagnostics. This screen is useful to troubleshoot OSI model Layer 2 problems on an ISDN connection. The screen refreshes periodically. To display a port ISDN Data Link Status screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – ISDN Diagnostics – D-Channel Diagnostics The following section describes the port D-Channel Diagnostics screen supporting T1M module diagnostics. The D-Channel Diagnostics screen allows you to enable or disable the D-Channel Diagnostics for the current port. This screen refreshes periodically. To display the D-Channel Diagnostics screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – ISDN Diagnostics – D-Channel Diagnostics – Display The following section describes the port D-Channel Diagnostics Display screen supporting T1M module diagnostics. The D-Channel Diagnostics Display screen allows you to view the DChannel Diagnostics in real-time. To display a port D-Channel Diagnostics Display screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Port – Loopback The following section describes the port Loopback screen supporting T1M module diagnostics. The LOOPBACK screen allows you to put the current port into one of four loopback modes and to transmit and detect specific bit patterns. This screen refreshes periodically. To display a port Loopback screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection The following section describes the Timers Selection screen that supports T1M module diagnostics. This screen refreshes periodically. To display the Timers Selection screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Timers. The Timers Selection screen appears, as shown in Figure 8-57. Figure 8-57.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – DID Timers The following section describes the DID Timers Information screen that supports T1M module diagnostics. This screen refreshes periodically. To display the DID Timers Information screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Timers. 4. Select DID Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – E&M Timers The following section describes the E&M Timer Information screen that supports T1M module diagnostics. This screen refreshes periodically. To display the E&M Timer Information screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Timers. 4. Select E&M Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – Loop-Start/Ground-Start Timers The following section describes the Loop-Start/Ground-Start Timer Information screen that supports T1M module diagnostics. This screen refreshes periodically. To display the Loop-Start/Ground-Start Timer Information screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Timers. 4.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – OPX Timers The following section describes the OPX (Off-Premises Extension) Timer Information screen that supports T1M module diagnostics. This screen refreshes periodically. To display the OPX Timer Information screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Timers. 4. Select OPX Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Timers – Timers Selection – Miscellaneous Timers The following section describes the Miscellaneous Timer Information screen that supports T1M module diagnostics. This screen refreshes periodically. To display the Miscellaneous Timer Information screen for T1M diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a T1M module. 3. Select Timers. 4. Select Miscellaneous Timers.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Basic Rate Module (BRM-S) Diagnostics Screens The following sections describe the DMU screens that support the Basic Rate Module (BRM-S) diagnostics. Main This section describes the main screen for Basic Rate Module (BRM-S) diagnostics. This screen periodically refreshes options D and E. To display the BRM-S main screen: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a BRM-S module.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Status The following section describes the STATUS screen for the BRM-S module. This screen refreshes periodically. To display the Status screen for BRM-S diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a BRM-S module. 3. Select Status. The STATUS screen appears, as shown in Figure 8-64. Figure 8-64.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Busy Out The following section describes the BUSY-OUT screen for the BRM-S module diagnostics. This screen refreshes periodically. To display the BUSY-OUT screen for BRM-S diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a BRM-S module. 3. Select Busy Out. The BUSY-OUT screen for the selected BRM-S module appears, as shown in Figure 8-65. Figure 8-65.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics • Pressing the LEFT ARROW or RIGHT ARROW moves the cursor between channels in the same port. • Pressing the LEFT ARROW key from Channel 1moves the cursor to Channel 2 in the same port. • Pressing the RIGHT ARROW from the Channel 2 moves the cursor to Channel 1 in the same port. • Pressing the UP ARROW while a channel is selected selects the channel’s port. • Pressing the DOWN ARROW while a channel is selected select the other port.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics Version Information The following section describes the Version Information screen for BRM-S module diagnostics. To display the Version Information screen for BRM-S diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a BRM-S module. 3. Select Version. The Version Information screen appears, as shown in Figure 8-66. Figure 8-66.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics ISDN Diagnostics Port [1 or 2] The following section describes the ISDN Diagnostics screen supporting BRM-S module diagnostics. To display an ISDN Diagnostics screen for a BRM-S port: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2. Select a Bay containing a BRM-S module. 3. Select ISDN Diagnostics Port 1 or ISDN Diagnostics Port 2, as applicable. The ISDN Diagnostics screen for the selected port appears, as shown in Figure 8-67.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics ISDN Diagnostics Port [1 or 2] – Data Link Status The following section describes the port ISDN Data Link Status screen supporting BRM-S module diagnostics. The Data Link Status screen is useful to troubleshoot OSI model Layer 2 problems on an ISDN connection. This screen refreshes periodically. To display a port ISDN Data Link Status screen for BRM-S diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics ISDN Diagnostics Port [1 or 2] – D-Channel Diagnostics The following section describes the port D-Channel Diagnostics screen supporting BRM-S module diagnostics. The D-Channel Diagnostics screen allows you to enable or disable the DChannel Diagnostics for the current port. This screen refreshes periodically. To display a port ISDN Data Link Status screen for BRM-S diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 8: Diagnostic Features Digital Trunk Diagnostics ISDN Diagnostics Port [1 or 2] – D-Channel Diagnostics – Display The following section describes the port D-Channel Diagnostics Display screen supporting BRM-S module diagnostics. The D-Channel Diagnostics Display screen allows you to view the D-Channel Diagnostics in real-time. To display a port D-Channel Diagnostics Display screen for BRM-S diagnostics: 1. From the DMU Main Menu select Digital Trunk Diagnostics. 2.
Chapter 9: Endpoints Endpoints Chapter 9: Endpoints Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4 IP Endpoints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-4 Hard IP Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 9: Endpoints Analog Single Line Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34 Feature Access Using Single Line Endpoints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34 Ring Zones and Extended Ring Cadences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34 Off Premises Extensions (OPX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 9: Endpoints Endpoint-Supporting Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-55 Peer-to-Peer Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-55 Data Port Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-56 Self-Programming Mode (Models 8620/8622 and 8662 Only) . . . . . . . . . . . . . .
Chapter 9: Endpoints Introduction Introduction This chapter describes the endpoints and features supported on Mitel 5000 systems. Mitel IP systems support the following endpoint types: • “IP Endpoints” below • “Digital Endpoints” on page 9-25 • “SIP Mode Endpoints” on page 9-32 • “Analog Single Line Endpoints” on page 9-34 IP Endpoints The Mitel 5000 supports various Internet Protocol (IP) endpoints.
Chapter 9: Endpoints IP Endpoints The IP device interface to the telephone system is an Ethernet IEEE 802.3 100 Mbps unshielded twisted pair (UTP) interface (RJ-45). The hard IP and multi-protocol endpoints use flash memory and their software can be updated over the Local Area Network (LAN). Hard IP Endpoints The following hard IP endpoints are supported: NOTE Refer to the appropriate user guide for more information about endpoints.
Chapter 9: Endpoints IP Endpoints Administrator Endpoints Any endpoint, attendant or non-attendant, can be assigned for administrator use through DB Programming. However, only display phones should be designated for administrators so they can see system alarms and to make programming easier. For adminstrator endpoint feature descriptions and instructions, refer to the Mitel 5000 Endpoint and Voice Mail Administrator Guide, part number 580.8001.
Chapter 9: Endpoints IP Endpoints ITP Mode and SIP Mode The Models 8600, 8620/8622, 8662, and 8690 multi-protocol endpoints support ITP mode or SIP mode. Details about each of the modes is described below. For complete information about supported features, buttons, and light-emitting diode (LED) indications for multi-protocol endpoints in ITP or SIP mode, refer to the Multi-Protocol Endpoints: Supported Features, Buttons, and LED Indications, part no. 835.2840.
Chapter 9: Endpoints IP Endpoints SIP Mode When the multi-protocol endpoints are in SIP mode, the endpoints use SIP to connect to the Mitel SIP Server (v1.1 or later). The advantage of running in SIP mode is the use of the Shared Extension feature. A shared extension allows up to five SIP endpoints to use the same extension number on the system. Incoming calls to a shared extension are sent to SIP endpoints simultaneously.
Chapter 9: Endpoints IP Endpoints For details about system features, refer to the appropriate endpoint User Guide for SIP mode. To support multi-protocol endpoints in SIP mode, a SIP Server software license is required. To change the modes on Models 8600, 8620/8622, and 8662, do one of the following procedures: • Dialpad: To switch to SIP mode, power up the endpoint with 1 and 2 pressed on the dialpad. To switch back to ITP mode, hold down 5 and 6 on the dialpad while powering up.
Chapter 9: Endpoints IP Endpoints IP Endpoint NAT Options Automatic NAT Detection: The Automatic Network Address Translation (NAT) Detection feature allows Mitel IP endpoints to operate inside or outside a private network NAT or firewall without having to change the IP Settings\NAT Address Type field every time the endpoint is relocated. The feature enables Mitel hard IP endpoints and the Mitel Model 8602 IP SoftPhone to place and receive calls either from inside or outside an Mitel private network.
Chapter 9: Endpoints IP Endpoints IP Endpoints and Features Figure 9-6 through Figure 9-14 show IP endpoints and endpoint features supported on the Mitel 5000 platforms. Model 5212 Figure 9-1 shows the Model 5212 endpoint and features. For more information about the endpoint and system features, refer to the Model 5212/5224 IP Endpoint User Guide, part number 550.8122. Figure 9-1.
Chapter 9: Endpoints IP Endpoints Model 5224 Figure 9-2 shows the Model 5224 endpoint and features. For more information about the endpoint and system features, refer to the Model 5212/5224 IP Endpoint User Guide, part number 550.8122. Figure 9-2. Mitel Model 5224 Handset Display buttons LCD Ring/Message Indicator Feature buttons Speaker Dialpad buttons Programmable buttons Page 9-12 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 9: Endpoints IP Endpoints Model 5330 Figure 9-3 shows the Model 5330 endpoint and features. For more information about the endpoint and system features, refer to the Model 5330/5340 IP Endpoint User Guide, part number 550.8123. Figure 9-3. Mitel Model 5330 Handset Programmable buttons LCD Ring/Message Indicator Feature buttons Dialpad buttons Speaker Mitel ® 5000 Reference Manual – Issue 3.
Chapter 9: Endpoints IP Endpoints Model 5340 Figure 9-4 shows the Model 5340 endpoint and features. For more information about the endpoint and system features, refer to the Model 5330/5340 IP Endpoint User Guide, part number 550.8123. Figure 9-4. Mitel Model 5340 Handset LCD Menu buttons Ring/Message Indicator Feature buttons Dialpad buttons Speaker Page 9-14 Navigation page buttons Programmable buttons Mitel ® 5000 Reference Manual – Issue 3.
Chapter 9: Endpoints IP Endpoints Mitel Cordless Devices The Mitel 5000 supports the cordless handset and headset for the Mitel Models 5330 and 5340 IP endpoints. Both cordless devices connect to the Mitel IP endpoints through the cordless module, which attaches to the back of the endpoint. The cordless headset recharges in a headset cradle that attaches to the side of the endpoint. The cordless handset recharges in the handset cradle.
Chapter 9: Endpoints IP Endpoints Model 8600 Figure 9-6 shows the Model 8600 endpoint and features. For more information about the endpoint and system features, refer to the Model 8600 Endpoint User Guide, part number 550.8115. Figure 9-6.
Chapter 9: Endpoints IP Endpoints Model 8620/8622 Figure 9-7 shows the Model 8620/8622 endpoint and features. For more information about the endpoint and system features, refer to the Model 8620/8622 Endpoint User Guide, part number 550.8119. Figure 9-7.
Chapter 9: Endpoints IP Endpoints Model 8660/8662 Figure 9-8 shows the Model 8660/8662 endpoint and features. For more information about the endpoint and system features, refer to the Model 8560/8660 Endpoint User Guide, part number 550.8112 or the Model 8662 Endpoint User Guide, part number 550.8117. Figure 9-8.
Chapter 9: Endpoints IP Endpoints Model 8690 Figure 9-9 shows the Model 8690endpoint and features. For more information about the endpoint and system features, refer to the Model 8690 Endpoint User Guide, part number 550.8116. Figure 9-9. Model 8690 Endpoint SPEAKER MESSAGE LAMP SPEAKER HEARING AID COMPATIBLE (HAC) HANDSET DEDICATED HEADSET JACK UNDERNEATH STYLUS TOUCH SCREEN MICROPHONE Mitel ® 5000 Reference Manual – Issue 3.
Chapter 9: Endpoints IP Endpoints Axxess IP PhonePlus Figure 9-10 shows an illustration of the Axxess IP PhonePlus and features. For more information about the endpoint and system features, refer to the Executive Display and IP PhonePlus Endpoint User Guide, part number 560.8108. Figure 9-10.
Chapter 9: Endpoints IP Endpoints IP PhonePlus Figure 9-11 shows an illustration of the IP PhonePlus and features. For more information about the endpoint and system features, refer to the Professional Display and IP PhonePlus Endpoint User Guide, part number 560.8002. Figure 9-11.
Chapter 9: Endpoints IP Endpoints Wireless IP Endpoints Figures 9-12 and 9-13 shows the Models 8664 and 8665 wireless endpoints. For more information about the endpoint and system features, refer to the Model 8664/8665/8668 User Guide, part number 935.4522. Figure 9-12.
Chapter 9: Endpoints IP Endpoints Figure 9-13. Model 8665 Wireless Endpoint EARPIECE VOLUME BUTTONS UP SELECT DOWN DISPLAY MENU BUTTONS POWER ON/START CALL POWER OFF/END CALL MENU 12-KEY PUSHBUTTON KEYPAD FUNCTION LINE MICROPHONE CHARGING CONTACTS Mitel ® 5000 Reference Manual – Issue 3.
Chapter 9: Endpoints IP Endpoints Model 8602 IP SoftPhone Figure 9-14 shows the Model 8602 SoftPhone. For more information, refer to the Model 8602 User Guide, part number 835.3109. Figure 9-14. Model 8602 SoftPhone Main Display Calls on Hold Slider Programmable Buttons Slider Dialpad Slider Page 9-24 Mitel ® 5000 Reference Manual – Issue 3.
Chapter 9: Endpoints Digital Endpoints Digital Endpoints Digital endpoints supported on Mitel 5000 systems include the following: • Model 8500. The Model 8500 hardware is the same as the model 8600 (see page 9-16). For more information about the endpoint and system features, refer to the Model 8500 Endpoint User Guide, part number 550.8114. • Model 8520. The Model 8520 hardware is the same as the model 8620/8622 (see page 9-17).
Chapter 9: Endpoints Digital Endpoints Associate Display Figure 9-15 shows the Associate Display endpoint and features. For more information about the endpoint and system features, refer to the Associate Display and Basic Endpoint User Guide, part number 560.8003. Figure 9-15.
Chapter 9: Endpoints Digital Endpoints Executive Display Figure 9-16 shows the Executive Display endpoint and features. For more information about the endpoint and system features, refer to the Executive Display and IP PhonePlus Endpoint User Guide, part number 550.8108. Figure 9-16.
Chapter 9: Endpoints Digital Endpoints Professional Display Figure 9-17 shows the Professional Display endpoint and features. For more information about the endpoint and system features, refer to the Professional Display and IP PhonePlus Endpoint User Guide, part number 560.8002. Figure 9-17.
Chapter 9: Endpoints Digital Endpoints Standard Display Figure 9-17 shows an illustration of the Standard Display endpoint and features. For more information about the endpoint and system features, refer to the Standard Display and Basic Digital Endpoint User Guide, part number 550.8109.
Chapter 9: Endpoints Digital Endpoints Basic Digital Figure 9-18 shows an illustration of the Basic Display endpoint and features. For more information about the endpoint and system features, refer to the Standard Display and Basic Digital Endpoint User Guide, part number 550.8109. Figure 9-18.
Chapter 9: Endpoints Digital Endpoints Wireless Digital Endpoints Figure 9-19 shows the Models 8524/8525/8526 Wireless Digital Endpoints. For more information about the endpoint and system features, refer to the Model 8524/8525/8526 User Guide, part number 935.4529. Figure 9-19.
Chapter 9: Endpoints SIP Mode Endpoints SIP Mode Endpoints The following sections describe SIP endpoints supported on Mitel 5000 systems. See “SIP Mode” on page 9-8 for SIP mode features supported on Mitel 5000 systems. SIP Hard Endpoints The following Mitel endpoints also work in Session Initiation Protocol (SIP) mode: • Model 8600 (see page 9-16). • Model 8620/8622 (see page 9-17). • Model 8662 (see page 9-18).
Chapter 9: Endpoints SIP Mode Endpoints Table 9-2. Model 8601 SoftPhone Icons and Menus No# Icon Menu Description 1 TALK Places a call. This icon changes to HOLD or RESUME, depending on the Softphone status. 2 CALL LOG Opens the Call Log that shows the call history of up to 30 calls. This icon changes to MUTE or RESUME, depending on the Softphone status. 3 MSG Plays the message that was left on the user’s voice mail. This icon changes to END during a call.
Chapter 9: Endpoints Analog Single Line Endpoints Analog Single Line Endpoints Analog single line endpoints are connected to Single Line Modules (SLM-4 or SLM-8), to IP Single-Line Adapter (SLA) circuits, or to SLA circuits, which in turn are connected to available Digital Endpoint Module (DEM-16) circuits. Also, one or two single line endpoints can be connected to the built-in ports on the back of the Mitel 5000 Base Server. OPXs can be connected to SLAs or T1M or T1M-2 modules.
Chapter 9: Endpoints Analog Single Line Endpoints Table 9-3 summarizes the differences between standard and extended ring cadences for the various types of single line endpoints used on the Mitel system in the United States. Table 9-3. Standard and Extended Ring Cadences for Single Line Endpoints Single Line Device SLA or T1 OPX Cadence Type Description Standard IC Ring This is a repeating 2-second cadence that rings twice. Each ring lasts 200 ms and is separated from the next ring by 400 ms of silence.
Chapter 9: Endpoints Endpoint Physical Features Endpoint Physical Features The following sections describe physical features of endpoints that operate on the Mitel 5000 platform. DSS/BLF Unit The Mitel 5000 platform supports two 60-button Direct Station Select/Busy Lamp Field (DSS/BLF) Units and one 50-button model. Although you can use either type of DSS/BLF Unit on any of the endpoints, the type of endpoint determines which is the more appropriate unit to use.
Chapter 9: Endpoints Endpoint Physical Features Speakerphones NOTE The network allows handsfree intercom calls when calling from one node to another, unless the call camps on to the node before being sent to the other node. Executive Display and Professional Display Speakerphone Each Executive Display and Professional Display endpoint has a built-in, integrated speakerphone that allows on-hook dialing and handsfree operation on outside calls and inside (intercom) calls.
Chapter 9: Endpoints Endpoint Physical Features Enhanced Speakerphones for Digital Endpoints To use an enhanced speakerphone on a digital endpoint, the user establishes a call and presses the Special button and then the Speaker button. Or, the user presses the Special button and enters the Enhanced Speakerphone feature code, 310. About one second of white noise is heard at this point. Both parties should avoid speaking during this white noise because it is used to calibrate the echo-canceling circuitry.
Chapter 9: Endpoints Endpoint Physical Features If an enhanced speakerphone call is placed on hold and then taken off hold on an Executive and Professional Display endpoint, the call remains an enhanced speakerphone call. However, if a call is placed on hold at a Standard or Associate Display endpoint, an Axxess or Eclipse Basic Digital endpoint, or a Model 8500, 8520, or 8560 endpoint, the call returns to standard speakerphone mode. A station can support only one enhanced speakerphone call.
Chapter 9: Endpoints Endpoint Physical Features Keep in mind the following guidelines when using the enhanced mode: • Follow the same guidelines as those listed for the “standard” speakerphone, and, in addition to the guidelines for an enhanced speakerphone. • Inform the far-end party about the burst of white noise before you enter the enhanced mode. • Use volume levels 1–3 for full-duplex operation. • Avoid using the enhanced mode on calls with significant delay.
Chapter 9: Endpoints Endpoint Physical Features Extension Number, Username, Time and Date Display When a display endpoint is idle, the extension number, username, time, and date are displayed. While on a call, in DND, or unconditionally forwarded, other displays are shown. In these circumstances, use the following procedure to re-display the date, time, user name, and extension number for 5 seconds.
Chapter 9: Endpoints Endpoint Physical Features Feature Keys The following sections provide information on the endpoint feature keys. “Hot” Keypad Keys vs. “SPCL Key Required for Feature Code Entry” Flag Unless programmed to use the Special button when entering a feature code, all endpoints have “hot” keypad buttons that allow dialing of feature codes, extension numbers, and trunk access codes without pressing the Special button or lifting the handset.
Chapter 9: Endpoints Endpoint Physical Features If there are more calls in progress than there are CALL buttons (e.g., if another call rings in to the endpoint in the example), the new call will not have an available call button and will camp on to the endpoint until a CALL button becomes available; it will then appear under the available button. Pressing an idle CALL button will enter the programmed Outgoing Call feature for that endpoint.
Chapter 9: Endpoints Endpoint Physical Features Endpoints and Button Locations The Model 8500, 8520, and 8560 endpoints have additional buttons and lamps. The following figures provide a cross-reference guide for button locations. For Mitel IP endpoint keymap assignments, refer to the “Endpoints and Devices” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006. Figure 9-21.
Chapter 9: Endpoints Endpoint Physical Features Standard/Alternate Keymap Switching In database programming, each endpoint is assigned a standard keymap and can also have an alternate keymap. The user can switch between the keymaps by entering a feature code. The maps can also be switched in the database using the Alternate Keymap endpoint flag. For more information about keymaps, refer to the “Endpoints and Devices” chapter in the Mitel 5000 Features and Programming Guide, part number 580.8006.
Chapter 9: Endpoints Endpoint Physical Features Default Feature Buttons – 8000-Series Endpoints When the system is in the default state, all endpoints are in the same keymap group and have the following feature buttons. The Special button is represented by buttons with ∞ or SPCL on the endpoint. Table 9-5. Default Inter-Tel Endpoint Feature Buttons Button Page 9-46 Function CALL BUTTONS 1–4 Selects an outgoing trunk, if idle, or answers a call on the button.
Chapter 9: Endpoints Endpoint Physical Features Secondary Extension Appearances The Secondary Extension Appearances feature allows calls ringing or on individual hold at one “primary” endpoint to appear on a “secondary extension key” at another endpoint. For example, a secretary or assistant can have a secondary extension button for a supervisor’s endpoint, or one endpoint can have several secondary extension buttons, each associated with a different primary endpoint.
Chapter 9: Endpoints Endpoint Physical Features After answering a call on the secondary extension button, the endpoint user can transfer it back to the primary endpoint using one of the following methods: • Transfer to hold: Press the secondary extension button, announce the call, if desired, and then hang up. • Transfer to ring: Press TRANSFER and then the secondary extension button. You can announce the call, if desired, before hanging up to complete the transfer.
Chapter 9: Endpoints Endpoint Physical Features SIP and ITP Mode Endpoints This section describes characteristics of endpoints that operate in Inter-Tel Protocol (ITP) mode or in Session Initiation Protocol (SIP) mode. Introduction With the exception of the Model 8660, the Model 8000 Multi-Protocol endpoints operate in ITP mode or in SIP mode. Except for the identified limitations, ITP mode supports most system features.
Chapter 9: Endpoints Endpoint Physical Features Headsets For convenience, an electret headset can be used at any endpoint. The Speaker button is used to connect and disconnect calls when the headset is attached. For more information about headset use, refer to the applicable endpoint user guide. Headset Power Saver Mode Some headsets have a power-saver mode that disables the headphone after a period of silence.
Chapter 9: Endpoints Endpoint Physical Features Phantom Devices Phantom device functionality has been enhanced in v2.2. The new phantoms are fully functional virtual devices on the system. Phantoms can function with Unified Communicator (UC) to perform advanced call routing tasks without the need for a real desk phone. They can also have a true status, such as idle, Do-Not-Disturb (DND), ringing, etc. so that they could be placed in hunt groups and actually ring.
Chapter 9: Endpoints Endpoint Physical Features Phantoms in DB Programming are defaulted to the not-in-DND status. When upgrading an old database, if there were phantom devices in the old database, their DND statuses will not be changed after the conversion. The following scenarios describe phantom configuration uses: • A phantom can be configured as a stand-alone device. An employee could have a cell phone to use when they are not in the office but still need to be on the office switch.
Chapter 9: Endpoints Signals and Tones Signals and Tones Mitel 5000 platforms provide auditory signals and tones that convey particular messages to users. This section describes the meanings of system sounds and graphically depicts what is heard by the user when the endpoint rings and what is heard over the handset during system operation. Ringing Signals The following table depicts the system signals and tones that are generated by the ringer or endpoint speaker, as shown in Table 9-7. Table 9-7.
Chapter 9: Endpoints Signals and Tones Call Processing Signals Table 9-8 shows the signals and tones that are heard through the handset or endpoint speaker. Table 9-8. Call Processing Signals SIGNAL ACTION Intercom dial tone Handset lifted or Speaker or IC button pressed. Double tones (called endpoint receives the same signal) Intercom call—repeats for private call or call to non-handsfree endpoint; one double tone for handsfree call.
Chapter 9: Endpoints Endpoint-Supporting Features Endpoint-Supporting Features The following sections describe the network and platform capabilities that support endpoint operation on the Mitel 5000 platform. Peer-to-Peer Audio Peer-to-Peer (P2P) audio allows IP and SIP devices to transmit and receive audio directly with each other. The P2P feature reduces delay and packet loss for IP and SIP devices.
Chapter 9: Endpoints Endpoint-Supporting Features Data Port Modules The following Data Port Modules can be connected to Executive, Professional, Standard, or Associate Display endpoints or to Models 8520 or 8560 endpoints: • PC Data Port Module (PCDPM): A digital device that is connected to the Executive Display, Professional Display, Standard Display, Associate Display, Model 8520, or Model 8560 Phones and supports data transmission between the endpoint and the phone system for DSS/BLF, off-hook voice an
Chapter 9: Endpoints Self-Programming Mode (Models 8620/8622 and 8662 Only) Self-Programming Mode (Models 8620/8622 and 8662 Only) Use the self-programming mode to configure the Models 8620/8622 and 8662 endpoints. This self-programming mode is similar to the Model 8660 IP endpoint. It allows you to set all the basic settings required for ITP mode. The following endpoints do not support self-programming mode: • Model 8600: This endpoint does not have a display.
Chapter 9: Endpoints Self-Programming Mode (Models 8620/8622 and 8662 Only) Program Database Follow the displays and complete the programming. For details about REVERT, EXIT, <<, and >>, see page 9-59. Unlike the previous endpoints, such as the Model 8600, multi-protocol endpoints do not support some configuration fields, such as hostnames and BOOTP. These endpoints, however, have additional fields like the software image information. Table 9-9.
Chapter 9: Endpoints Self-Programming Mode (Models 8620/8622 and 8662 Only) To program the IP address: 1. Press a dialpad button to enter the IP address. The entire second line, except the dots, disappears, and the number you entered appears in the first space. The following options are available: 2. • Revert: Reverts to the old value found in the current database, and the endpoint updates the display accordingly.
Chapter 9: Endpoints IP Endpoint Web Interface IP Endpoint Web Interface The Web interface, IP Endpoint Web Client Administrative Session, for the multi-protocol endpoints allows you to set the most frequently used options. The Web interface also allows you to reset the device and synchronize its configuration with the configuration files on the TFTP server. Clicking Synch in the Configuration page synchronizes with the TFTP server only and not with the system. See page 9-68.
Chapter 9: Endpoints IP Endpoint Web Interface Table 9-10. IP Endpoint Web Client Field Descriptions (Continued) ITP Mode Page # SIP Mode License 9-67 License N/A 9-67 Volume Image Upgrade 9-68 Image Upgrade RTP/RTCP 9-68 RTP/RTCP Command Configuration 9-68 Configuration Reset 9-68 Reset Device Configuration The Device Configuration field allows you to configure network, audio and call control, firmware, and trace settings.
Chapter 9: Endpoints IP Endpoint Web Interface Table 9-11. IP Endpoint Web Interface: Network Configuration Page (Continued) Field Name Use DHCP for TFTP Server and Path Default Enabled Indicates (Continued) Whether to overwrite the TFTP URL in the TFTP Server IP Address field, listed above, with the TFTP server IP address and path from the DHCP server. Audio & Call Control: This Audio & Call Control Configuration page shows specific information about a call in progress.
Chapter 9: Endpoints IP Endpoint Web Interface Table 9-13. IP Endpoint Web Interface: Current Call Control Status Fields (Continued) Field Name Default Indicates RTP Receive State OFF Whether the endpoint is currently receiving RTP audio packets. Session Description 2025 (GW) 1000 A description that indicates the two endpoints on the current connection along with the connection type.
Chapter 9: Endpoints IP Endpoint Web Interface Phone: The Endpoint Configuration page shows information related to the endpoint setup and whether the endpoint is currently in SIP mode. This page contains the fields described in Table 9-15. To apply the changes, click Update. Table 9-15.
Chapter 9: Endpoints IP Endpoint Web Interface Trace: The Trace Configuration page allows you to setup a remote trace capture for UDP debug information. The available fields vary depending on the mode the endpoint is in. This page contains the fields described in Table 9-16. To apply the changes, click Update. Table 9-16. IP Web Interface—Trace Options Field Name Default Indicates Trace Host 0.0.0.0 The address of the remote device where trace output should be sent.
Chapter 9: Endpoints IP Endpoint Web Interface Table 9-17. SIP Call Client Configuration Page Descriptions (Continued) Field Name Default Indicates Register Server Port 5060 The port of the primary SIP registration Server. Register Period 3600 seconds (one hour) The time between synchronizations (in progress). Voice Mail VOICEMAIL The voice mail string that is displayed when the MSG button is pressed or the Message feature code is entered.
Chapter 9: Endpoints IP Endpoint Web Interface Status Network: The Network Status page shows network information. Both SIP and ITP modes have the same fields. The page contains the fields shown in Table 9-19. Table 9-19. Network Status Indications Field Name Indicates Physical Address Endpoint MAC address. IP Address Endpoint IP address. Subnet Mask Network subnet mask. Default Gateway Network gateway. DHCP Server DHCP server IP address the endpoint obtains.
Chapter 9: Endpoints IP Endpoint Web Interface Image Upgrade: The Image Upgrade page shows current image version information and download status. This page contains the fields described in Table 9-22. Both ITP and SIP modes has the same fields. Table 9-22. Image Upgrade Page Descriptions Field Name Indicates Image Version Image version of the endpoint-specific code. Configuration Image Version Version of the configuration image. Download Status Status of the TFTP download.
Chapter 9: Endpoints Endpoint Configuration Files Endpoint Configuration Files This section describes all of the parameters that are available in the global and device-specific configuration files. You may add or edit any of the parameters in the configuration files.
Chapter 9: Endpoints Endpoint Configuration Files Network Settings The configuration files contain the network parameters as described in Table 9-23. Some of the parameters can also be programmed in the IP Endpoint Web Client Administrative Session. The IP Endpoint Web Client field names and their reference pages that correspond to the parameters are also shown in Table 9-23. Table 9-23.
Chapter 9: Endpoints Endpoint Configuration Files Table 9-23. IP Endpoint Web Client Field Names—Network Settings (Continued) Parameter Default Indicates (Continued) IP Endpoint WEB Client (Page #) update_interval 3600 sec (1 hour) The time, in seconds, between automatic configurations updates from the TFTP server. The interval should vary among endpoints to prevent massive simultaneous updates. The range of the values are 0-4294967295. A zero value disables the automatic update.
Chapter 9: Endpoints Endpoint Configuration Files Table 9-23. IP Endpoint Web Client Field Names—Network Settings (Continued) Parameter lan_pq_port Default 0x0000 IP Endpoint WEB Client (Page #) Indicates (Continued) Specifies which of the Ethernet ports support 802.1P/Q. A “1” bit indicates that the port supports 802.1P/Q. NOTE VLAN Configuration (see page 9-66) This parameter does not apply to endpoints with v1.1.x or later firmware.
Chapter 9: Endpoints Endpoint Configuration Files ITP Mode Settings The configuration files contain the ITP mode-related parameters as described inTable 9-24. Some of the parameters can also be programmed in the IP Endpoint Web Client Administrative Session. The IP Endpoint Web Client field names and their reference pages that correspond to the parameters are also shown in Table 9-24. Table 9-24.
Chapter 9: Endpoints Endpoint Configuration Files Table 9-25. IP Endpoint Web Client Field Names—SIP Mode Settings (Continued) Parameter Default IP Endpoint WEB Client (Page #) Indicates sip_reg_period 3600 sec (1 hr) The time between synchronizations (in progress). See “Register Period” on page 9-66 sip_voicemail VOICEMAIL The voice mail string that is displayed when the MSG button is pressed or the Message feature code is entered.
Chapter 9: Endpoints Endpoint Configuration Files SIP Audio Settings The configuration files contain the audio parameters as described in Table 9-27. Some of the parameters can also be programmed in the IP Endpoint Web Client Administrative Session. The IP Endpoint Web Client field names and their reference pages that correspond to the parameters are also shown in Table 9-27. Table 9-27.
Chapter 9: Endpoints Endpoint Configuration Files Software Images The configuration files contain the endpoint parameters as described in Table 9-28. Some of the parameters can also be programmed in the IP Endpoint Web Client Administrative Session. The IP Endpoint Web Client field names and their reference pages that correspond to the parameters are also shown in Table 9-28. Table 9-28.
Chapter 9: Endpoints Endpoint Configuration Files Table 9-28. IP Endpoint Web Client Field Names—Software Images (Continued) Parameter Default 8690_gui_ image_url N/A IP Endpoint WEB Client (Page #) Indicates (Continued) (For the Model 8690 only) The IP address or URL of the image TFTP server of the user interface firmware image. Required if the DHCP does not provide the TFTP address. N/A You can also include the path to the profile file, if desired.
Chapter 9: Endpoints Endpoint Configuration Files Export and Import Devices When another node adds a new extension or changes an existing extension, username, or description, the network broadcasts the new extension information to the other nodes in the network. Or, system administrators can choose to export local device information to other nodes, or import devices from the other nodes to the local node, using the Export/Import option in this menu.
Chapter 9: Endpoints Endpoint Configuration Files 2. Select the following information, then click Start. Or, click Exit to cancel the operation without exporting any information. • Operation: Select the desired option to determine whether you will be importing devices into the local node or exporting local devices to a remote node. • Remote Node Number: Select the node(s) you want to export the information to or import the information from, by placing checks in the appropriate boxes.
Chapter 9: Endpoints Endpoint Configuration Files 4. After attempting to export or import information, check Message Print output for error messages: • If a programming session is active on the remote node, you cannot export information to that node until the programming session has been terminated. Also, if the remote node has a Voice Processor and the link is down, the export will fail on the remote node.
Chapter 9: Endpoints Model 8690 Programming Model 8690 Programming The following sections describe how to install the Model 8690 endpoint. Windows CE .NET Programming (Model 8690 Only) This section provides information about Model 8690 programming using the Model 8690 client application on Windows CE .NET. For complete information about how to use the 8690 client application, refer to the Model 8690 Administrator’s Guide (document part no. 550.
Chapter 9: Endpoints Model 8690 Programming Upgrading the Model 8690 The 8690 client application can be upgraded automatically or manually. If an upgrade fails, or if the application is partially installed, you must reformat the flash file system on the endpoint. See page 9-84 for instructions on how to reformat the Model 8690 flash file system.
Chapter 9: Endpoints Model 8690 Programming Upgrade the Model 8690 Manually Although the Model 8690 automatically checks for upgrades, you can manually upgrade the Model 8690 by running the Auto Upgrade feature. If there are no new upgrades available, you will not be notified, and your endpoint will function normally. If there is an upgrade available, the Software Upgrade dialog box opens, and you are prompted to install the upgrade.
Chapter 9: Endpoints Model 8690 Programming Reformatting the Model 8690 Flash File System Installing the client application on the Model 8690 may fail if the endpoint does not have sufficient memory resources or if the endpoint loses power before the upgrade is complete. If the upgrade fails, or if the application is partially installed (see the dialog boxes below), it is strongly recommended that you reformat the flash file system on the endpoint. NOTICE Data Loss Hazard.
Chapter 9: Endpoints Model 8690 Programming 8. Click Properties. The Partition Properties dialog box opens. 9. Click Dismount, and then press Format. The Format dialog box opens. 10. Verify that the Quick Format option is selected and click Start. 11. Click Yes to format. 12. Click OK to close the Format dialog box. 13. In the Partition Properties dialog box click Mount and then OK. 14. Close the Storage Properties dialog box and then exit the Control Panel. 15.
Index Index Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Symbols Administrator endpoints 3-2 Agent Help 6-45 8690 Client Application 9-85 network extension 6-43 Resource Reservation 4-6 tone interval timer 6-43 A using 6-43 Absorbed Digits 5-30 Absorbed digits 5-30 repeatable 5-30 toll restriction 5-27, 5-30 Accept Button 9-42 Accepting a Name 7-40 Account codes 6-6 all calls following 6-6 database-programmed 6-6 optional 6-6 SMDR 6-6 Accounting, Call Cost 3-31 ACD All Messages 7-34 All Mes
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X ARS (Automatic Route Selection) Audio Stream analog voice mail exempt from ARS only 5-28 receive port 9-63 ARS-Only Class of Service 5-31 transmit IP address 9-63 dial rules 3-4 transmit port 9-63 emergency calls 3-5, 5-14 Audio, peer-to-peer (P2P) 3-29 exempt from ARS-only toll restriction 5-27 Audiotex Recordings 7-16, 7-21 facility groups 3-4 on a network 3-7 Automated Attendant 7-5, 7-14, 7-15 applications 7-16 Route groups 3-4 custom a
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Barge-in, Resource Reservation 4-7 Base Number For DID 5-38 Basic Digital Phones BVM Port Licensing and IP Resource Allocation 7-6 C speakerphone 9-37 Basic Voice Mail 7-3, 7-5 eight ports 7-6 Cadences extended ring 9-34 forward to e-mail 6-21 Call Buttons 9-42 IP resource allocation 7-6 Call Center Suite 6-35 port licensing 7-6 Call Cost accounting 3-31 sixteen ports 7-6 Call forwarding 6-19 storage capacities 7-7 all calls 6-19 Basic Voic
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Call routing ANI 5-22 ANI example 5-24 call routing key (button) 5-22 CID example 5-24 DID example 5-23 DID, using 5-22 DNIS call routing table example 5-25 DNIS, using in 5-22 on an network 5-23 pattern strings 5-22 public network example 5-26 ring destination 5-22 Calls Camp-on, using 6-48 conference placing 6-14 transferring 6-14 emergency 5-12 forwarding 6-19 network 6-19 hold, placing calls on 6-28 intercom 6-47 Callback, using 6-48 Camp-on, using 6
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Codec Type 9-63 Codes account 6-6 all calls following 6-6 database-programmed 6-6 optional 6-6 outside calls 6-6 SMDR 6-6 D Data channels 4-10 Data collection 8-7 Data connections 4-10 Data link status 8-67 BRM 8-115 feature 6-5 directory 6-16 Data Port Modules 9-56 Office codes numbering plan 5-29 Database Programming, additions 6-38 trunk access 5-6 Command 9-68 Database Change Log 8-17 Date and Time, display 9-41 Date/Time 9-67 configuration 9-
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Diagnostics audio 8-6 DID (Direct Inward Dialing) call routing table example 5-23 data collection 8-7 in call routing 5-22 direction 8-7 in SMDR 3-33 Audio Diagnostics feature, using 8-8 in T1/E1 spans 5-36 BRM timer, diagnostic 8-80 busy out 8-111 trunks 5-38 screens 8-109 trunks, programming outline 5-39 status 8-110 Diffserv 9-63 version information 8-113 Digit Translation 7-21 Dual T1/E1/PRI ModuleSee T1M-2 nodes 7-23 IP Device Reso
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X DTMF Sets Directory See Single-Line Sets automated attendant 7-16 feature codes 6-16 Dual T1/E1/PRI module features 5-3 IDS 6-51 Dump VoIP DSP 8-46 intercom 6-16 Duplex 9-67 speed dial 6-16 E Voice Processing 7-5, 7-14, 7-16, 7-31, 7-38 DISA (Direct Inward System Access) description 5-10 E&M (Ear and Mouth) factors affecting quality 5-10 ring-in to hunt group pilot number 5-10 security codes 5-10 Display Endpoint Self-Programming Prompts and
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Enable account codes for all calls following feature 6-6 digital phones 9-38 Enable TFTP Configuration Update 9-61 Enhanced Speakerphone Mode 4-11 Enabling the Account Code for All Calls Following Feature 6-6 Enhanced speakerphone mode 9-38 Endpoint 9-36 Enhanced Speakerphones for Digital Endpoints 9-38 return to default settings 6-15 Enhanced Speakerphones for Digital Phones 9-38 Endpoint Features 6-47 Entering a Name 7-39 Endpoint IP and MAC
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X F Flags all messages 7-34 Digital/IP alternate transient display 9-41 Facility groups, ARS 3-4 each new message 7-34 Fax over Internet Protocol (FOIP) 3-24 Expanded CO Call Information on Displays 5-8 Faxes, Fax over Internet 3-24 headset connect tone station 9-50 Fax-On-Demand 7-14, 7-42 Outside Party Call Information Has Priority 5-8 priority only 7-34 audiotex recordings 7-21 restart ACD idle time upon login 6-35 digit translation 7-22 Sp
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Hardware Type 9-67 remove/replace 6-34 Headset Call 9-67 remove/replace and Do-Not-Disturb 6-34 Headset Connect Tone Endpoint Flag 9-50 Hunt Groups (Continued) Headset Connect Tone Station Flag 9-50 ring in 6-31 Headset Tone 9-67 station lists 6-29 Headset, cordless 9-15 supervisor 6-45 Headsets 9-50 timers 6-33 using extension lists 6-30 Hold Hybrid Balance test 8-13 alternate hold timer 6-28 Consultation, description 6-28 Individual, des
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Internet Protocol (IP) Audio and Call Control - SIP Mode endpoint Resource Reservation 4-9 Current Call Control Status Fields private networking Network Configuration Page compatibility 4-3 9-63 9-62 9-61 IP Endpoint Web Interface Configuration Page servers, digital hardware features 2-3 9-64 IP endpoint Web session 8-31 Internet Protocol (IP) Networking IP Endpoints, basic speakerphone 9-37 resource allocation 4-4 IP Phone Web Client 9-60
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X L message indications 6-49 Lamp, Message 9-45 LAN QoS 9-66 Language 6-55 message notification endpoint 7-32 Mailboxes (Continued) operator destination 7-30 passwords 7-29 receive only 7-29 Do-Not-Disturb messages 6-56 remote messaging 7-29 multilingual capability 6-54, 7-24 standard 7-29 Reminder Messages 6-67 Reminder messages 6-56 selecting secondary 6-55 selection 6-54 voice processing 6-56 Last Download Error Page 9-68 Last number dialed or s
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X single line 2-8 Mitel 5000 CS-5200 2-3 SLM-4 2-8 CS-5400 2-3 trunk 2-7 CS-5600 types 2-7 Processing Server (PS-1) 2-4 memory card 2-3 Mitel IP Endpoints 9-11 MSG Button 6-49 Multi-Language Feature on Network Operation 7-25 Multilingual Mitel Model 5224 9-12 directories 6-57 Mitel Model 5330 9-13 DND settings 6-18 Mitel Model 5340 9-13 on networked system Network Model 8600 Endpoint 9-16 multilingual usage 6-57 message lamp 9-45 Model 8601
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Nodes 7-14, 7-23 Network 9-61, 9-67 agent help extension 6-43 and IP address on power-up 9-41 ARS calls 5-27 attendant 3-3 external Voice Processing system 7-10 ARS, using 3-7 network mailbox 7-10 call forward 6-19 node trunk groups 5-17 call routing to another system example 5-26 number on endpoint display 9-41 camp on 5-35 programming 5-17 distributed order 5-17 conference calls 6-14 linear order 5-17 DND configuration 6-18 Notification
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Operator Destination Peer-to-Peer (P2P) audio 3-29, 4-15, 5-3, 8-5 mailbox 7-30 description 4-15 Voice Processing 7-16, 7-21 requirements 4-15 Optional External Voice Processing 7-5 Peer-to-Peer Audio 9-55 Optionalaccount codes 6-6 Persistent Music-On-Hold 3-30 OPX (off-premise extension) Personal Number 7-33 in T1/E1 spans 5-36 Phantom Devices 9-51 Other Digital Endpoint Speakerphones 9-37 Phantom Devices Default Capacities Outgoing Acces
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Problems, audio 8-6 Register Processing Server (PS-1), description 2-4 period 9-66 Processor module 2-7 server IP address 9-65 Professional Display Phone, speakerphone 9-37 Program Database 9-58 Programming 1-1 communication with external voice processing 7-9 database 9-58 the IP address 9-59 Prompts, Japanese 6-54 Proxy Server server port 9-66 Reminder Messages 6-67 Japanese language 6-67 multilingual 6-67 Remote IPC IP 9-58 server IP address 9-62
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Ring Intercom Always, using 6-47 Secondary Extension Keys 9-43, 9-47 Ring Signals 9-53 appearances 9-47 Ring When X Calls At Extension 9-42, 9-47 ring when x calls 9-42, 9-47 transient call indication 9-47 Ring Zones 9-34 Ring Zones and Extended Ring Cadences 9-34 Self-Programming Mode (Models 8620/8622 and 8662 Only) 957 Ringer 9-67 Self-Programming Mode for Models 8620 and 8662 9-57 Ring-In Send Alert Burst to Headset 9-50 day/night 5-10 Se
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X SMDR information storage and retrieval 7-42 SMDR (Station Message Detail Recording) 8-42 points 9-35 Standard Display Phone speakerphone 9-37 absorbed digits 5-30 Standard features description 3-33 Standard Keymap 9-42, 9-44, 9-45 DID/DDI 3-33 Standard Speakerphone 9-38 options 3-33 Standard/Alternate Keymap Switching 9-45 suppressed digits 3-34 Static (Default) IP Address 9-61 SMDR Information Storage And Retrieval 7-42 Static IP 9-58 SMDR
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X System Forwarding 6-22 advance timer 6-22 T1/E1 trunks applications 5-37 day or night mode status 6-22 T1/E1/PRI Module See T1M enabling or disabling 6-27 T1M (T1/E1/PRI Module) endpoint status 6-22 forwarding path 6-22 forwarding point 6-22 handsfree announce 6-24 Manual Call Forwarding overrides 6-25 recalls 6-27 ring principal once 6-23 to analog voice mail 6-40 unanswered calls 6-27 System Health Report 3-37 System Hold description 6-28 System M
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X T1M-2 module diagnostics 8-61 T1M-2 modules diagnostics layer 1 8-61 toll strings 5-27 Toll restriction absorbed digits 5-27 ARS 3-5 Tables, call routing 5-22 COS 5-31 TCP/IP description 5-27 network 7-10 emergency calls for trunk groups 5-27 networking 7-11 exempt from ARS-only 5-27 TCP/IP Networking 7-11 speed-dial override 5-32 Telnet/Serial Trace Log 9-65 trunk groups 5-27 Template, Keymap 9-42 Toll string, dialing pattern wildcards 5-3
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X Trunk, access codes 5-6 Trunks (Continued) Camp-on 5-35 language settings 6-55 dial plan 9-64 loop start 5-3, 5-35 management 5-16 queue callback 5-35 modules 2-7 Two-stage Caller ID (*ANI*DNIS*) 5-7 Trunk Groups absorbed digits 5-30 U allowed answer 5-21 keys 9-42, 9-43 outgoing access 5-21 Trunk groups UCD Hunt Groups 6-34, 6-41 announcement stations 6-41 overflow stations 6-41 absorbed digits 5-30 UDP (User Datagram Protocol) Trace Log 9-6
Index A-B-C-D-E-F-G-H-I-J-L-M-N-O-P-Q-R-S-T-U-V-W-X V Voice Processing (Continued) operator destination 7-16, 7-21 Version information, T1M, diagnostics 8-91 Record-A-Call 7-14, 7-25 Version information, T1M-2 modules 8-59 SMDR buffering 7-5 voice channels 7-13 Voice Activity Detection 9-63 voice mail 7-5, 7-14 Voice Channels, Voice Processing 7-13 Voice Mail 7-28, 9-66 and message notification/retrieval applications 7-28 directory 7-38 mailboxes 7-29 subscribers 7-29 system administrator 7-29 Voi
Part No. 580.8007 Issue 3.
