Mitel mivoice business Engineering Manualline
  1. Manuals
  2. Brands
  3. Mitel Manuals
  4. Telephone
  5. MiVOICE BUSINESS
  6. Engineering manualline

Mitel mivoice business Engineering Manualline

Hide thumbs Also See for mivoice business:
Table of Contents

Advertisement

Quick Links

Download this manual See also: User Manual, Manual
Mitel MiVoice Business
RELEASE 7.2
ENGINEERING GUIDELINES

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the mivoice business and is the answer not in the manual?

Questions and answers

Related Manuals for Mitel mivoice business

Summary of Contents for Mitel mivoice business

  • Page 1 Mitel MiVoice Business RELEASE 7.2 ENGINEERING GUIDELINES...
  • Page 2 ). The information is subject to change without notice and should not be construed in any way as a commitment by Mitel or any of its affiliates or subsidiaries. Mitel and its affiliates and subsidiaries assume no responsibility for any errors or omissions in this document. Revisions of this document or new editions of it may be issued to incorporate such changes.

  • Page 3: Table Of Contents

    What’s New in this Release? ..........3 Changes to the Mitel MiVoice Business Engineering Guidelines ..... . 3 About the MiVoice Business Documentation Set .
  • Page 4 Engineering Guidelines AX Controller ............. . . 35 AX Controller ONS port limitation .
  • Page 5 Access Connections ............74 Networking Considerations for MiVoice Business Console ......75 IP Sockets and Monitors.
  • Page 6 Mitel 3300 power dongle (Cisco compliant) ........
  • Page 7 Table of Contents CHAPTER 8: EMERGENCY SERVICES Emergency Services............131 Location Information .
  • Page 8 Engineering Guidelines CHAPTER 10: LICENSING System Licenses............. 155 Device Licensing.
  • Page 9 Table of Contents Basic Concepts ............203 Delay .
  • Page 10 Mitel Communication Director ........
  • Page 11 MiVoice Business and 3300 IP Ports ........
  • Page 12 Engineering Guidelines IP Address Restrictions ............289 Cables and Connections .
  • Page 13 Security Support with Mitel VoIP ........
  • Page 14 Engineering Guidelines Dual Port Phones ............348 IEEE 802.1X .

  • Page 15: Chapter 1 About This Document

    Chapter 1 ABOUT THIS DOCUMENT...

  • Page 17: Overview

    Mitel MiVoice Business is the brand name of the call-processing software that runs on hardware platforms such as the 3300 ICP. The 3300 ICP name is the brand name for Mitel hardware platforms that run MiVoice Business. 3300 ICP Release 9.0 was the last software release under the original branding scheme. It was replaced by the Mitel Communications Director (MCD) brand and released as "Release 4.0."...
  • Page 18 Engineering Guidelines for these older releases are still available on the Mitel eDocs web site. See the next section for details...

  • Page 19: About The Mivoice Business

    System Administration Tool Help for MiVoice Business: programming, maintenance, and troubleshooting. • 3300 ICP Resiliency guide: overview of the Mitel Resiliency solution and the tools to understand, plan, and implement a resilient network. • General Information Guide: General product overview including deployments, architecture, products and features.

  • Page 20: System Management Tools

    For MCD Release 6.0 Internet Explorer (IE) Version 8.0 is supported, other web browsers (such as Firefox, Navigator, Google Chrome) are not supported. For MiVoice Business Release 7.0 IE 9 or later and Mozilla Firefox 36.0.4 are supported. 10 For MiVoice Business Release 7.2 the minimum browser requirements are IE 10 and Firefox 36.0.4.

  • Page 21: About The Mivoice Business System

    Most systems can be engineered, in terms of their hardware components, from the fairly simple rules presented in these guidelines. The Mitel Sales Workbench (MSW) builds in most of these rules. When an installation requires a system that is complex or close to some operating limits, contact Mitel's Customer Engineering Service.
  • Page 22 Engineering Guidelines...

  • Page 23: Chapter 2 System Overview

    Chapter 2 SYSTEM OVERVIEW...

  • Page 25: System Architecture

    TDM-based telephony for legacy devices and PSTN connectivity. Mitel’s architecture uses the IP network to connect IP telephony devices and provides a supplementary TDM (time division multiplexing) subsystem to switch calls between traditional telephone devices (Figure 1). The 3300 ICP has the advantage of being able to optimally switch both types of traffic, IP or TDM.

  • Page 26: Mivoice Business Controller

    MIVOICE BUSINESS CONTROLLER The MiVoice Business controller provides the voice, signalling, central processing, and communications resources for the system. There are several controller configurations supported for release MiVoice Business 7.0 including 3300 ICP Controllers and industry standard servers: • AX controller with 512 MB memory •...

  • Page 27: Supported Countries

    Spain • In some cases MiVoice Business can be deployed in countries that are not included in the above list. In these cases, regional office personnel will be able to suggest the country selection that will provide the best transmission performance.
  • Page 28 Engineering Guidelines...

  • Page 29: Chapter 3: Typical Configurations

    Chapter 3 TYPICAL CONFIGURATIONS...

  • Page 31: System Configurations

    It also allows for a more distributed architecture and dispersal of equipment compared to a more traditional central TDM PBX system. MiVoice Business has a reliable, mature call control with a large feature set enabling multiple integration possibilities with an existing installation.

  • Page 32: Typical Installation Configurations

    Engineering Guidelines TYPICAL INSTALLATION CONFIGURATIONS The MiVoice Business platorm can be designed into different network configurations to suit the organization of the enterprise. See the following examples for an illustration of how the organization of the enterprise affects the overall network and unit configurations: •...

  • Page 33: Hybrid System

    Typical Configurations Each would have distributed trunk units and could be considered multiple copies of the campus scenario. Figure 3: Example of a Campus Environment Configuration Figure 4: Example of a Corporate Configuration with Multiple HQs HYBRID SYSTEM A Hybrid system combines both of the previous scenarios and involves a distributed system for a headquarters and combined units for remote branch offices.
  • Page 34 Engineering Guidelines to corporate PSTN access as well as local access through the local group controller. In the event the WAN link is lost, the separate sites can still operate as independent units. Figure 5: Example of a Hybrid Configuration...

  • Page 35: Sample 3300 Icp Configurations

    ACD configurations, where RADs would be set up on the trunk gateway (see “MiVoice Business, 3300 ICP and ACD” on page 22). See “Trunking gateway working example” on page 191 for an example of the calculations needed.

  • Page 36: Mivoice Business, 3300 Icp And Acd

    E2T channels will be critical to the number of agents and/or trunks that can be supported. It is expected that most MiVoice Business and 3300 ICP installations will use IP phones for the agents but it is also possible with some 3300 ICP controllers to use TDM phones (DNIC or ONS).
  • Page 37 MiVoice IP Phones directly connected to the system, or via a MiVoice Border Gateway Traditional agents only are supported on: • TDM digital phones as extensions to the MiVoice Business systems, e.g. DNIC or ISDN External Hot Desking Agents are supported on: •...

  • Page 38: Standalone Acd Controller

    Engineering Guidelines STANDALONE ACD CONTROLLER Smaller ACD installations will use a single controller with all trunks, agents, groups and paths on it. The IVR and Call Centre Manager are both connected to this controller (through the local network), as are the agents. The calls will come into the call centre from the PSTN through either TDM or SIP trunks, will be routed through the IVR system and queued to a path.

  • Page 39: Network Acd Controllers

    A specific installation may be able to support more or less agents and traffic depending on whether conditions are more or less stressful than these assumptions. For ACD installations on MiVoice Business Virtual or installations outside the parameters specified below, contact Mitel Professional Services.
  • Page 40 Note: Because the AX is primarily an ONS and LS gateway, it would not normally be used in an ACD application. The MXe Server is limited by E2T and conference resources compared to MiVoice Business for ISS with its attached Media Server. The AX, CX II, and MXe base are also limited by E2T and other DSP resources.Mitel proprietary voice encryption is supported in ACD deployments.
  • Page 41 Traffic per agent is at 27 CCS and 120 sec call handling time, i.e. 30 CPH per agent. • Mitel Contact Center Solutions 6.0 is used to provide call handling and reporting. • There is an IVR system handling incoming calls. With no IVR, calls will ring directly to the path(s) with less overhead, but there is less functionality in terms of call handling.
  • Page 42 TDM trunks SIP trunks Note: Mitel proprietary voice encryption is supported in ACD deployments. However, due to the increased load SRTP places on the solution SRTP voice encryption is not supported in ACD configurations and must be disabled via ESM.
  • Page 43 • additional or alternate applications attached. • any requirement for call centers with MiVoice Business Multi-instance or MiVoice Business Virtual. Active agents vs. traffic The maximum number of agents shown in the above tables is based on each agent handling an average of 30 CPH, corresponding to an average total call handling time (CHT) of 120 seconds, including work timer.
  • Page 44 Figure 8 shows how the number of local and external hot desk agents must be balanced on an agent controller (example shown is for MiVoice Business for ISS. The same principle must be used for any other controller configuration.

  • Page 45: The 3300 Icp As A Dedicated Voice Mail Server

    Typical Configurations Figure 8: Example of Local vs. EHD Agents on ISS Agent Controller THE 3300 ICP AS A DEDICATED VOICE MAIL SERVER The 3300 ICP can be used as a dedicated voice mail server with or without additional end devices attached.

  • Page 46: Configuration Tables

    MXE SERVER, MIVOICE BUSINESS VIRTUAL, MIVOICE BUSINESS FOR ISS, AND MIVOICE BUSINESS MULTI-INSTANCE Note: Other limits besides those in the following table may apply to MiVoice Business Virtual and MiVoice Business for ISS depending on the deployment. Consult the MiVoice Business Virtual and MiVoice Business for ISS Engineering Guidelines for more...
  • Page 47 Typical Configurations Table 8: Maximum MXe Server / MiVoice Business Virtual / MiVoice Business for ISS / MiVoice Business Multi-instance Configuration FEATURE / RESOURCE VALUE / QUANTITY NOTES Call Control 2.0 GHz (MXe Server) This processor runs only call control and passes other real time Processor (x86) functions and E2T to the other processors.
  • Page 48 VALUE / QUANTITY NOTES CIM ports The 4 CIM ports on the front panel of the MXe Server are not enabled, and they do not exist on MiVoice Business for ISS, VMware Virtual Appliance, and Multi-instance platforms. ASUs supported LS trunks...

  • Page 49: Ax Controller

    Typical Configurations AX CONTROLLER Table 9: Maximum AX configuration FEATURE / RESOURCE VALUE / QUANTITY NOTES RTC processor 450 MHz E2T processor The AX uses a single processor for both RTC and E2T functions. Memory (RAM) 512MB IP Users and 100/300 Maximum IP devices or users.

  • Page 50: Ax Controller Ons Port Limitation

    Engineering Guidelines Table 9: Maximum AX configuration (continued) FEATURE / RESOURCE VALUE / QUANTITY NOTES MMC modules Quad DSP (int, ext) Modules may be installed in the internal or external locations (installed slots) Echo Canceller (int, ext) as shown. Dual T1/E1 (ext) T1/E1 Combo (ext) Quad BRI (ext) Dual FIM (ext)

  • Page 51: Cx/Cxi Controller

    Typical Configurations CX/CXI CONTROLLER FEATURE/ RESOURCE VALUE/QUANTITY NOTES RTC processor 266 MHz This processor is listed as 300 MHz in the Engineering Tool. Memory (RAM) 512 MB IP Users and Up to 16 IP devices may be connected directly to the powered Devices (Including Ethernet ports on the front of the CXi cabinet.
  • Page 52 Engineering Guidelines FEATURE/ RESOURCE VALUE/QUANTITY NOTES MMC modules Dual DSP (3) The CX is the only member of the 3300 ICP family that uses the Dual (installed slots) Quad DSP (3) DSP module. DSP II (2,3) Note that the Dual FIM and the Dual T1/E1 modules are NOT T1/E1 Combo (1,2) supported on the CX.

  • Page 53: Cx Ii/Cxi Ii Controller

    Typical Configurations CX II/CXI II CONTROLLER Table 10: Maximum CX II/CXi II configuration FEATURE/ RESOURCE VALUE/QUANTITY NOTES RTC processor 400 MHz This processor is listed as 450 MHz in the Engineering Tool. E2T processor The CX II uses a single processor for both RTC and E2T functions. Memory (RAM) 512 MB Expandable to 1024 MB...

  • Page 54: Mxe Controller

    Engineering Guidelines MXE CONTROLLER Table 11: Maximum MXe configuration VALUE/QUANTITY FEATURE/ RESOURCE BASE MXE EXPANDED NOTES RTC processor 450 MHz 450 MHz The base MXe uses a single processor for both RTC and E2T functions. See Note, below. E2T processor 450 MHz Optional, to increase capacity.
  • Page 55 Typical Configurations Table 11: Maximum MXe configuration (continued) VALUE/QUANTITY FEATURE/ RESOURCE BASE MXE EXPANDED NOTES T. 38 Record-a-Call Every Record-a-Call session uses a conference resource and a voice mail session from the available pool. The maximum number of simultaneous sessions supported is 12, but may be limited to less than this by the available resources.

  • Page 56: Mxe Controller 192 Gateway Limitations

    Engineering Guidelines MXE CONTROLLER 192 GATEWAY LIMITATIONS The MXe Controller has been shipped in two different versions since it was introduced (MXe and MXe II). In MCD 4.2 a third version, the MXe III, is released. The original version has four AD21262 DSP devices on the main board, and the later MXe II has four AD21363 DSP devices.

  • Page 57: Lx Controller

    Typical Configurations LX CONTROLLER Table 12: Maximum LX configuration FEATURE/ RESOURCE VALUE/QUANTITY NOTES RTC processor 450 MHz Prior to release 6.0, all LX systems used 450 MHz processors with 256 MB of memory. From release 6.0 the RTC module uses 512 MB E2T processor 450 MHz of memory.
  • Page 58 Engineering Guidelines Table 12: Maximum LX configuration (continued) FEATURE/ RESOURCE VALUE/QUANTITY NOTES ASU supported LS trunks (in ASU) 16 (32) Up to four Universal ASUs may be added with 4 LS trunks each. Four ASU II cabinets can support 8 ONS/LS cards for a total of 32 LS trunks.

  • Page 59: Other Maximum Limits

    Please refer to the following documents for MiTAI limits • Mitel OIG 2.0 Engineering Guidellines HCI (MiTAI) monitors (Mitel OIG 2.0 supports MiVoice Business 6.0 SP3 and 7.0) • SDK 6.0 (MiTAI Driver) Engineering Guidelines for the new MiTAI Driver that replaces legacy MiTAI client (SDK 6.0 (MiTAI Driver) is only supported on MiVoice...

  • Page 60: Sip Phones And Use Of Tls (Sip-Tls)

    The table below is to be used in conjunction with other standard limitation tables in these Guidelines. The lower value of each of these is to be used. In practice, the SIP-TLS numbers mainly impact the MiVoice Business for ISS, whereas the 3300 ICPs already have limitations in place.

  • Page 61: Use Of Srtp

    Typical Configurations USE OF SRTP SRTP allows voice encryption between Mitel and supported third party devices. It requires additional resource above Mitel encryption and therefore is only supported on the following platforms and with the limitation described below: • MXe III expanded (Note: Maximum E2T channels is reduced from 192 to 150 in gateway configuration) •...

  • Page 62: Summary Of Device And User Limits

    Engineering Guidelines Note: In the CX/CXi and AX systems the number of available echo cancellers might be less than the numbers shown here, depending on the specific combination of modules installed. In the commercial servers the actual maximum will be dependent on the CPU availability and/or allocation for the Media Server.
  • Page 63 Typical Configurations Table 16: Device and User Limits SYSTEM TYPE ACTIVE LIMITS CX/CXI CX II/CXI II MXE BASE MXE EXP SERVER SIP Sets (Note 3) 1000 3000 ONS (licensed) ONS (peripheral cab) 1152 ONS (extended per) 1536 2304 Analog Trunks Hot Desk Users 1400 5000...

  • Page 64: Html Applications On Sets

    IP phones to support graphics-based software applications. Phones that employ SAC present more of a processing load to the ICP or MiVoice Business than phones that do not use the SAC protocol. There are two varieties of SAC phones, SAC heavy and SAC light which, as the names imply, present differing processing loads to the ICP or MiVoice Business.

  • Page 65: Upgrading The System

    There are two reasons to upgrade a system – to increase the line size or to improve performance. With Mitel the network is the system, so it can also be expanded (and resiliency added) by adding more controllers into a clustered "virtual system". Individual controllers can be upgraded as shown below, or new controllers can be added into a cluster to create a larger virtual system.

  • Page 66: Provisioning System Resources

    Engineering Guidelines PROVISIONING SYSTEM RESOURCES The table below shows the capacity of each system in its factory default configuration, with no additional MMC modules or other upgrades purchased. Notes: 1. No compression is possible in the base configurations. 2. The AX must have a 4GB flash card installed to support Voice Mail. Table 18: Standard 3300 ICP Configurations FEATURE/ RESOURCE...

  • Page 67: Cx Hardware Configurations

    Typical Configurations CX HARDWARE CONFIGURATIONS In addition to the two devices installed on the main board, DSP resources may be added to a CX system using the Dual DSP Module (2 devices), the Quad DSP Module (4 devices), or the T1/E1 Combo Module (1 device).
  • Page 68 Engineering Guidelines Table 19: Maximum CX Feature Availability Without DSP II LINES TRUNKS DSP USAGE SYSTEM HARDWARE T1/E CONFIGURATION 1 2 3 4 5 6 7 8 Base 2 E T 0 10 Base + 1 T1/E1 Combo 24/30 3 E T T 1 42 10x3 16 24/30...

  • Page 69: Cx/Cxi Ii Hardware Configurations

    Typical Configurations Table 20: Maximum CX Feature Availability With DSP II LINES TRUNKS DSP USAGE SYSTEM HARDWARE T1/E CONFIGURATION 1 2 3 4 5 6 7 8 Base + Dual DSP + 100 150 4 E E T T 0 20 10x3 16 DSP II + Quad CIM Base + Quad DSP +...

  • Page 70: Programmable Keys

    When these devices, or users, are made resilient to other nodes, data for these keys has to be shared. Before MiVoice Business 7.0 there was a limit of 150,000 keys that could be synchronized from an SDS sync master to its slave(s).
  • Page 71 Typical Configurations Table 21: Programmable Key Capacity by Device Type PHONE TYPE PROGRAMMABLE KEYS 5401 IP 5505 SIP 5560 IPT 96, or 192 (See Note below) 5603 SIP 5604 SIP 5607 SIP 5610 SIP 5624 SIP Generic SIP Navigator NetVision UC Endpoint Superset 4001 Superset 401...

  • Page 72: Provisioning For Traffic

    Engineering Guidelines PROVISIONING FOR TRAFFIC All 3300 ICP controllers contain an internal TDM switching fabric. Calls between TDM sets, or from TDM sets to trunks, will stay within this TDM switch. Calls between IP phones stream their voice packets directly over the data network without going into the TDM domain in the 3300 ICP controller, but calls between IP sets and TDM devices (including both lines and trunks) must go from the IP domain to the TDM switch fabric through the TDM gateway (E2T processor).

  • Page 73: Chapter 4: Phones And Voice Applications

    Chapter 4 PHONES AND VOICE APPLICATIONS...

  • Page 75: Mivoice Ip Phones

    The number of IP consoles (5540, 5550, and MiVoice Business Console) that can be connected to a system is determined by the absolute maximum number of IP consoles that can be configured on the system and number of IP User licenses.

  • Page 76: 5560 Ipt Limits

    MXe III expanded versions), and the MXe Server (and all commercial servers, including MiVoice Business for ISS and MiVoice Business Virtual). Because of the typical use of this device, in an extremely high traffic environment, there are restrictions on the number of these appliances which can be deployed on the various systems.

  • Page 77: Phones Supported On The Ax

    Phones and Voice Applications Table 22: Impact of Shared Line Appearances and Traffic Rates on Number of 5560 IPT Supported EQUIVALENT CONTROLLER NUMBER OF SETS SHARED LINE CALL HOLD TYPE (USERS) APPEARANCES CPH PER USER TIME (SEC) MXe II CX II Page 2 of 2 PHONES SUPPORTED ON THE AX All phone sets are supported on the AX platform;...

  • Page 78: Wideband Audio

    Engineering Guidelines Table 23: Packet Rates PACKET TYPE RATE (PACKET/SECOND) BURST HANDLING (PACKETS) CDP, STP, LLDP ARP, ICMP RTP (per stream) The Micro Firewall will filter the packets and allow bursts up to the “credit” limit shown above. After a protocol type has exhausted its credits with a burst that reached the prescribed limit, the credits are added back at prescribed rates.

  • Page 79: Dect (Digital Enhanced Cordless Telephony)

    Phones and Voice Applications DECT (DIGITAL ENHANCED CORDLESS TELEPHONY) When multiple DECT base station units (Radio Fixed Part (RFP)) are connected to the 3300 ICP using ISDN (BRI or PRI), the reference clock source in the ICP must be accurate to better than ±...
  • Page 80 Engineering Guidelines Table 24 indicates which phones support the Gigabit Ethernet and Wireless LAN Stands. Table 24: Phone Stand Support GIGABIT ETHERNET WLAN STAND IP DECT STAND PHONE STAND SUPPORT SUPPORT SUPPORT 5001 5005 5010 5020 5201 5205 5207 5212 5215 5220 Dual Mode 5215 Dual Mode...
  • Page 81 Table 24: Phone Stand Support (continued) GIGABIT ETHERNET WLAN STAND IP DECT STAND PHONE STAND SUPPORT SUPPORT SUPPORT 5540 5550-TKB 5560 IPT MiVoice Business Console Not Applicable Not Applicable Not Applicable Navigator UC360 Not Applicable Not Applicable Not Applicable Page 2 of 2...

  • Page 82: Gigabit Ethernet Phone Stand

    Stand. • The Side Control Unit used to connect a Mitel Conference Unit to a 5220/ 5224 will still need its own 24Vdc power supply and should be connected to the IP Phone as usual. It also requires that the phone and stand be powered using a power adapter that is sold separately and connects directly to this Stand.

  • Page 83: Cordless (Dect) Handset And Headset

    Many factors affect the coverage and capacity performance of the Cordless (DECT) Handset and Headset. First, is the RF spectrum allocated for DECT, which differs based on geographic area. The Mitel Cordless Module and Accessories (Handset and Headset) come in two variants. The first works in the Standard DECT band of 1880 - 1900 MHz, the second is a DECT 6.0 variant that works...
  • Page 84 To maintain performance and use all available channels, the maximum total number of active Mitel Cordless (DECT) Handsets and Headsets in a specific area (phones with Cordless Modules evenly distributed in the area) is shown below. The last column in the table provides a density guideline for deploying Mitel Cordless (DECT) Handsets and Headsets.

  • Page 85: Typical Operating Range

    (300' to 900'). The operating range in a typical office environment will be reduced due to obstructions and interference to approximately 50 m (150') for the Mitel Cordless (DECT) Handset and 30m (100') for the Mitel Cordless Headset. RANGE EXAMPLE The radio cell can penetrate only one brick wall.

  • Page 86: Other Considerations

    The site survey should also indicate how far the user can move away from the 5330/5340/5360 IP phone and still maintain a connection. The Mitel document IP-DECT Wireless Solution … Site Survey Instructions For Mitel Systems covers how to conduct a site survey for a complete DECT wireless system. This document can be found on Mitel OnLine under Support/Technical Support/Product Documentation then look in the Documentation Library.

  • Page 87: Micollab Client And Micollab Client Softphone

    The MiCollab Client Softphone uses either SIP or MiNET to communicate with MiVoice Business via one IP socket. The MiCollab Client server will place a monitor on this set, the same as with any other user device. A MiCollab Client will normally be associated with the MiCollab Client Softphone.

  • Page 88: Networking Considerations For Micollab Client

    40, the equivalent of a precedence of 5 for legacy TOS based routers. If the setting is unchecked (the default setting), MiCollab Client will use the Mitel setting which is a DSCP value of 46, and provides marking into the Expedited Forwarding queue for DSCP based routers.

  • Page 89: Networking Considerations For Mivoice Business Console

    Wizard Quality of Service settings window. By default, the MiVoice Business Console will use the Mitel setting for voice media which is a DSCP value of 46 and TOS value of 6. The MiVoice Business Console must be run as administrator for non-default QoS settings to take effect.
  • Page 90 When many applications, or end devices, are directly attached to the 3300ICP/MiVoice Business MiTAI interface it is possible to run out of both MiTAI monitors and MiTAI sockets. Use of a consolidation server, such as the MiCollab Client Server, where the MiCollab Clients attach to the server rather than to the 3300 ICP/MiVoice Business, will reduce the possibility of over subscription of monitors and sockets.
  • Page 91 Phones and Voice Applications Table 28: (continued)ICP Connections (continued) RESOURCE MIVOICE BUSINE TELEPHONE OR MINET MITAI MITAI SS IP APPLICATION SOCKETS SOCKETS SOCKETS MONITORS CONNECTIONS 5304/5312/5324 1 per device 1 per device None None 2 per device (without attached (MiNET & SAC) application) 5304/5312/5324 1 per device...
  • Page 92 Included with Limited by Application Client device, MiCollab monitors specific included in Client server the MiCollab Client Server Mitel OIG None 1 per server 1 per 1 per server Limited by Application Server monitored (Mitel OIG) Mitel OIG specific device...
  • Page 93 Phones and Voice Applications Table 29: ICP Connections to External Application Servers (continued) RESOURCE MAXIMUM MAXIMUM MINET MITAI MITAI TOTAL IP PORTS PER PORTS PER APPLICATION SOCKETS SOCKETS MONITORS SOCKETS SERVER MiContact None 1 per 1 per 1 per Limited by Application Center Office application...
  • Page 94 Note that although the table above gives a good view of what services are consuming sockets, MiVoice Business also uses sockets for internal working. A good rule of thumb would be to add an additional 500 sockets for these internal services. The System Engineering Tool counts socket usage for internal and external devices, and it is recommended to use this tool, especially if the calculations from the tables plus overhead suggest that a limit will be reached.
  • Page 95 Phones and Voice Applications Figure 9: ICP Connection Paths and Limitations...

  • Page 96: System Resource Notes

    Engineering Guidelines Table 30: Application Socket Limits for Release MCD 5.0 and Later MXE SERVER, MIVOICE BUSINESS FOR ISS, MIVOICE BUSINESS VIRTUAL (ALL), MIVOICE BUSINESS MULTI-INSTANCE (X86 RESOURCE AX, CX, MX, MXE BASE MXE EXPANDED CPU) MiNET Sockets 1400 5600...
  • Page 97 Phones and Voice Applications Figure 10: Worked Example The configuration includes a number of hot desk users (200+200) as well as mix of applications for MiCollab Client (100+100) and also UC Express (50+50) on the non-hot desk user phones. In this example it is assumed that the MiCollab Client and UC Express applications are only monitoring themselves, and so the number of MiTAI monitors is equal to the number of applications.
  • Page 98 Engineering Guidelines Table 31: Worked Example - Standard and Resilient Operation MINET MITAI TOTAL MITAI STANDARD OPERATION QUANTITY SOCKETS SOCKETS SOCKETS SOCKETS MONITORS CONNECTIONS PHONE TOTAL HOT DESK 5330 (Hot Desk) 100 phones 5312 (Hot Desk) 100 phones MiCollab Client MiCollab (Monitor 5330s) Client...
  • Page 99 Phones and Voice Applications Table 31: Worked Example - Standard and Resilient Operation (continued) MINET MITAI TOTAL MITAI STANDARD OPERATION QUANTITY SOCKETS SOCKETS SOCKETS SOCKETS MONITORS CONNECTIONS Standard fixed included with phone TOTAL 1602 Note: As can be seen from the calculations, some additional IP Sockets are needed to cover the SAC connection to MiTAI (one per system) and also the MiCollab Client Server (one per application).
  • Page 100 Engineering Guidelines...

  • Page 101: Chapter 5 Power

    Chapter 5 POWER...

  • Page 103: Introduction

    Power INTRODUCTION This chapter discusses the following power requirements for the 3300 ICP: • “Installation Practices” on page 90 • “Controller Power Input” on page 91 • “MiVoice IP Phone Power” on page 92 • “Planning a Power Over Ethernet Installation” on page 100 •...

  • Page 104: Installation Practices

    MItel strongly recommends using Uninterruptible Power Supply (UPS) units or similar power backup systems to protect the 3300 controllers against AC power outages. For more information on this subject, see “Uninterruptible Power Supply (UPS)”...

  • Page 105: Controller Power Input

    Power CONTROLLER POWER INPUT The controllers have flexible power input operating over a wide range to allow global connectivity. The units operate with standard supplies of 60/50 Hz and 110/230 VAC input, and are auto-sensing. NSU cabinets also have universal (auto-sensing) power inputs. Migrated SX 2000 DSU cabinets each have a switch on the power supply to select 120 VAC or 230 VAC power.

  • Page 106: Mivoice Ip Phone Power

    • With a special in-line Ethernet power adapter that provides a local power feed to the Mitel 5000, 5200, and 5300 series of IP phones. This adapter converts mains voltage into -48 VDC and supplies power to the phone over the Ethernet cable.

  • Page 107: Recommended Phone Powering

    Power Note: The CXi and CXi II support the IEEE 802.3.af communication standard. Table 35 can be referenced to determine what the phones will advertise as their PoE power requirements. The CXi uses IEEE 802.3af power advertisements sent from the phones to determine what the power consumption will be, where as the CXi II actually measures the current being drawn from the phones.

  • Page 108: Options For Ip Phone Powering

    5340e 5360 Yes, but the Yes (Notes only power 2 and 3) (Power Hub supply must approved for support use is: Mitel Gigabit Part # Ethernet 51015131) and must be 802.3af compliant) 5505 5485 IP Pager 5540 Page 1 of 2...

  • Page 109: Ac Power Adapters

    Page 2 of 2 AC POWER ADAPTERS For information on AC power adapters, refer to the appropriate Mitel phone data sheet. Note: The standard 24 VDC power adapter has a 10 ft. (3 m) output power cord. If a longer output power cord is required, you can use Part Number 57004243 (universal...

  • Page 110: In-Line Ethernet Ac Power Adapters

    802.3af Ethernet switch and the end device. Note: Mitel phones can be powered from equipment that uses phantom powering or spare pair powering. Devices that provide power by either method are called are called “Power Sourcing Equipment”...

  • Page 111: 3300 Cxi/Cxi Ii Icp 802.3Af Power Over Ethernet Capabilities

    Power Once the “signature” or impedance has been detected, the voltage is increased and current draw is monitored. The amount of current drawn allows the PSE to classify the device for Power over Ethernet requirements. Classification is an optional part of the standard and allows the end device to “inform”...

  • Page 112: Third Party 802.3Af Powering

    The 3300 Power Dongle (Cisco-compliant) may not be required when powering Mitel phones behind a Cisco Catalyst 4500/6500. For this to be the case, you must ensure you are using an 802.3af-compliant version of the 4500/6500 switch.
  • Page 113 Power The following methods can be used to provide PoE to the 5560 IPT: • Non-Redundant PoE: The 5560 IPT can be powered from a single PoE compliant L2 switch through either of the two ethernet ports. • Redundant PoE: Providing redundant PoE supplies is accomplished by connecting both of the 5560 IPT's ethernet ports to PoE compliant L2 switches.

  • Page 114: Planning A Power Over Ethernet Installation

    Some innovative vendors of IEEE 802.3af compliant switches, such as Hewlett Packard and Mitel, provide power management features that can help to manage a situation where a group of phones might require more total power than the L2 switch can provide. For example: •...

  • Page 115: Phone Power Consumption

    Power PHONE POWER CONSUMPTION This section provides tables with information on telephone power requirements. Use the table that is relevant to your particular installation. LOCAL POWER Table 33 below lists the actual power required by the various telephones. The values in this table can be used to determine: •...
  • Page 116 5412 PKM + 5448 PKM (see Note 3) 5448 PKM (see Note 3) 5448 PKM + 5448 PKM (see Note3) 5485 Paging Unit 5540 5505 5550-TKB (Used with the 5550 IP Console) MITEL 3300 power dongle Navigator TeleMatrix 3000IP Page 2 of 3...

  • Page 117: Remote Power

    Power Table 33: Actual Telephone Power Consumption (continued) POWER CONSUMPTION (W) DEVICE (WORST CASE MAXIMUM) Gigabit Ethernet Phone Stand Version 1. Note: This power is for the stand only, the phone power is not included. Gigabit Ethernet Phone Stand Version 2. Note: This power is for the stand only, the phone power is not included.
  • Page 118 Engineering Guidelines CDP power advertisements Table 34 can be used to determine which CDP power advertisement a phone will use. Note: Depending on the particular PoE protocol used, the phone may advertise a power requirement that is different from the actual phone power consumption shown in Table 33.
  • Page 119 Power Table 34: CDP Power Advertisements (continued) CDP POWER ADVERTISEMENTS DEVICE (SEE NOTE) 5312 6.1 W 5320 6.1 W 5320e 6.1 W 5324 6.1 W 5324 IP Phone + 5310 Conference Unit 6.1 W 5324 + PKMs 6.1 W 5330 with backlight 6.1 W 5330 6.1 W...
  • Page 120 Engineering Guidelines Table 35: 802.3af Power Class Advertisements CLASS DEVICE ADVERTISED 5001 IP Phone 5005 IP Phone 5010 IP Phone 5020 IP Phone 5020 IP Phone + 5310 Conference Unit (Conference unit is powered with AC adapter 24 VDC) 5020 IP Phone + PKM(s) (PKMs are powered with AC adapter 24 VDC) 5201 IP Phone 5205 IP Phone 5207 IP Phone...
  • Page 121 Power Table 35: 802.3af Power Class Advertisements (continued) CLASS DEVICE ADVERTISED 5302 IP Phone 5304 IP Phone 5312 IP Phone 5320 5320e 5324 IP Phone 5324 IP Phone + 5310 Conference Unit (Conference unit is powered with AC adapter 24 VDC) 5324 IP Phone + PKM(s) (PKMs are powered with AC adapter 24 VDC) 5324 IP Phone (Dual Mode) + 5412 PKM 5324 IP Phone (Dual Mode) + 5448 PKM...
  • Page 122 Engineering Guidelines Table 35: 802.3af Power Class Advertisements (continued) CLASS DEVICE ADVERTISED TeleMatrix 3000IP Gigabit Ethernet Phone Stand Version 1 Gigabit Ethernet Phone Stand Version 2 5540 5560 IPT UC360 See Note 2. Note 1: See “Power Restrictions” on page 68. for information about power restrictions related to the Gigabit Ethernet Phone Stand.
  • Page 123 Power Table 36: LLDP-MED Power Advertisements (continued) POWER POWER VALUE CONSUMPTIO DEVICE ADVERTISED N (WATTS) 5020 IP Phone + 5310 Conference Unit (Conference Unit is powered with Not Supported AC adapter 24 VDC) 5020 IP Phone + PKM(s) (PKMs are powered with AC adapter 24 VDC) Not Supported 5201 IP Phone Not Supported...
  • Page 124 Engineering Guidelines Table 36: LLDP-MED Power Advertisements (continued) POWER POWER VALUE CONSUMPTIO DEVICE ADVERTISED N (WATTS) 5235 + Gigabit Ethernet stand 11.5 5235 IP Phone + LIM 5140 IP Appliance Not Supported 5240 IP Appliance Not Supported 5302 Not supported 5304 IP Phone 5312 IP Phone 5320...
  • Page 125 Power Table 36: LLDP-MED Power Advertisements (continued) POWER POWER VALUE CONSUMPTIO DEVICE ADVERTISED N (WATTS) 5340 + Bluetooth module 5360 5360 + Conference Unit 12.8 5360 + Cordless OM/Handset + Headset 12.0 5360 + Bluetooth module 12.0 5360 + LIM 5505 Navigator TeleMatrix 3000IP...

  • Page 126: Power Requirements For 5220 Ip Phone Optional Accessories

    SYSTEM POWER REQUIREMENTS ICP power requirements are detailed in the 3300 ICP Hardware Technical Reference Manual. This document is available via Mitel On Line. Note: During a local power failure, data being written to a disk or FLASH module may not be completely stored and therefore could become corrupted.

  • Page 127: Uninterruptible Power Supply (Ups)

    APC web site: http://www.apc.com/tools/ups_selector/index.cfm Mitel products are listed under “VoIP Solutions.” (Although information appeared correct when this publication was written, Mitel cannot take responsibility for incorrect information entered or supplied from this tool.)
  • Page 128 Engineering Guidelines...

  • Page 129: Chapter 6 Performance

    Chapter 6 PERFORMANCE...

  • Page 131: System Performance Index

    Performance SYSTEM PERFORMANCE INDEX In order to calculate the performance limits of a system, different weighting values are assigned to various types of calls. Typically an ONS-to-ONS call is considered to have a loading factor of 1.0, and an IP phone-to-IP phone, a loading factor of 3.2. Other call types (ONS to PSTN trunk, IP phone to IP trunk, etc.) are assigned different values based on actual performance tests.
  • Page 132 Engineering Guidelines controller in conjunction with other units providing functions such as TDM gateways and voice mail services. Normal operation is within the P.99 region. The system may be pushed into the P.95 region, for short duration, for example during a resilient failover condition. However, certain call parameters, such as delay to dial tone, may be extended beyond the normal expected timings.

  • Page 133: Performance In An Acd Environment

    Performance Figure 12: Performance Limitations for Mixed Office Traffic (MXe Server) PERFORMANCE IN AN ACD ENVIRONMENT There are many features of an office telephone system which are always present and which individually use a large amount of CPU performance, but since they are rarely used in an office or hospitality environment, they are insignificant to the overall performance numbers of the system.

  • Page 134: Performance With Ring Groups

    For further information on ring group configuration to optimize performance and resources, see the System Engineering Tool and the System Administration Tool Help for MiVoice Business. PERFORMANCE WITH HUNT GROUPS The method of searching hunt groups can have a significant effect on the overall performance of a system.

  • Page 135: Chapter 7 Applications

    Chapter 7 APPLICATIONS...

  • Page 137: 3300 Icp Applications

    Applications 3300 ICP APPLICATIONS The 3300 ICP supports a number of applications. This includes applications that are embedded in the product, such as voice mail, through to providing DSP resource to allow connections to external devices, for example a remote central voice mail in another unit. Other interfaces include MiTAI for MiCollab Client Softphone operation.

  • Page 138: Voice Mail

    Engineering Guidelines VOICE MAIL The 3300 ICP includes an integrated, fully featured voice mail system. Up to 30 ports are available for voice mail calls with support for a maximum of 750 mailboxes and 130 hours of storage time. Notes: 1.

  • Page 139: Embedded Music On Hold

    Applications • MAIL FROM – specifies the originating mailbox. • RCPT TO – identifies the recipient's mailbox. • DATA – start of data. • QUIT – connection is to be closed. The receiver will send an OK reply. • NOOP – no action. It can be used at any time during a connection session. •...

  • Page 140: Application Processor Card

    CX(i) and CX(i) II controllers that meet the minimum hardware requirements as shown in the following table. The APC can only be installed in CX(i) and CX(i) II controllers that meet the minimum hardware requirements as shown in the following table. MITEL PART NUMBER DESCRIPTION 50005096 50005097...
  • Page 141 Teleworker Solution - A secure teleworking solution for remote and home-based employees. It supports standard Mitel Networks IP Phones. Refer to the Teleworker docu- mentation for a listing of supported Mitel phones, as not all Mitel phones are supported by the Teleworker application.
  • Page 142 Engineering Guidelines...

  • Page 143: Chapter 8: Emergency Services

    Chapter 8 EMERGENCY SERVICES...

  • Page 145: Emergency Services

    Emergency Services EMERGENCY SERVICES Emergency services such as 911 are available from most phone devices according to how the class of service and restrictions for the phone are set. The default is to enable 911 emergency service access. Currently, the following devices do not fully support Enhanced 911 (E911) operation: •...
  • Page 146 Engineering Guidelines Protocol (CDP). The IP phones then report to the ICP, sending the MAC address of the L2 switch port to which they are connected. Note: The network port MAC addresses and physical locations must be known before the IP phones are deployed. Automatic CESID updating is designed to work in a homogeneously configured network where all the access L2 switches in a particular subnet (to which IP phones are connected) report MAC address information by one, and only one, of the following methods:...

  • Page 147: Teleworker Devices

    • a properly programmed Mitel 3300 ICP • a properly programmed Mitel 5220 or 5235 IP Phone equipped with a properly configured Mitel Line Interface Module (LIM) For information about LIM configuration refer to the LIM Installation Guide. For information about programming the 3300 ICP for emergency call routing, refer to the System Administration Tool Help for MiVoice Business.

  • Page 148: Cesid Auto Updates, Unsupported Configurations

    Engineering Guidelines CESID AUTO UPDATES, UNSUPPORTED CONFIGURATIONS Automatic updating of CESID when a phone moves to a new location will not work under the following circumstances: • If the IP phone is connected to an Ethernet hub • If the IP phone is connected to an L2 switch that does not have CDP or STP/RSTP enabled •...

  • Page 149: Other Considerations

    Emergency Services Figure 15: Non-compatible Network Configuration - L2 Switch with both CDP and STP Disabled Figure 16: Non-compatible Network Configuration - Devices Connected to L2 via Hub OTHER CONSIDERATIONS • The Spanning Tree Protocol allows multiple ethernet connections to be made between a device and the network without introducing a network loop.
  • Page 150 In the event that an L2 switch vendor does not adhere to the STP/RSTP or CDP protocols correctly, there could be issues that prevent E911 from functioning as required. At the time of writing, Mitel is not aware of any specific L2 switches that fail to comply with STP/RSTP or CDP.

  • Page 151: Chapter 9 Ip Networking

    Chapter 9 IP NETWORKING...

  • Page 153: Ip Networking Considerations

    IP Networking IP NETWORKING CONSIDERATIONS This chapter discusses how IP networking and IP trunks affect the 3300 ICP. The terms “IP networking” and “IP trunks” have become synonymous. However, “IP networking” covers the whole picture, while “IP trunks” refers to the individual call connections. See the following topics for more information: •...

  • Page 154: Clustering

    • User Controller: This is a 3300ICP or MiVoice Business system that only deals with IP Phones and users. It does not have direct connectivity to TDM PSTN trunks, although it will have access to IP-Trunks to other MiVoice Business systems and 3300ICPs.

  • Page 155: Ip-Trunk Connection Limitations

    IP Networking IP-TRUNK CONNECTION LIMITATIONS Prior to Release MCD 5.0 there were some IP-Trunk limitations to consider. These include: • The number of IP-Trunk channels per connection, or route - 200 per route • The total number of IP-Trunk channels on the node, gateway or controller is limited to a total 2000 provisioned channels •...

  • Page 156: Ip Trunking Models

    Engineering Guidelines IP TRUNKING MODELS Examples of fully-meshed and hierarchical network configuration networks are shown Figure 17 and Figure 18. Figure 17: Fully-meshed Network In a fully-meshed network, every node is connected to every other node. The benefit of a fully-meshed network arrangement is that one, or even more than one, link can go down, and nodes can still reach each other—there are many alternative routes.

  • Page 157: Call Handling, Routing, And Bandwidth

    Figure 18: Hierarchical Network Further details on setting up a cluster can be found in the “3300 ICP Multi-Node Management Clustering” document under the 3300 product documentation on Mitel-on-Line. CALL HANDLING, ROUTING, AND BANDWIDTH A call consists of two parts: signalling and voice streaming.
  • Page 158 Engineering Guidelines Figure 19: Signalling and Voice Path Example 1 In the tandem case, a virtual IP trunk is used from A to B and another virtual IP trunk is used from B to C. These trunks are counted against the routing limit. In certain networks, especially external WANs that use VPNs, the most direct path from A to C may actually be through the IP router at site B.

  • Page 159: Variable Rtp Packet Rates

    Network Configuration Concepts, provides specific details under the CODEC Selection heading of CODEC frame rates. MiVoice Business supports packet rates from 10ms to 80ms in steps of 10ms. MiVoice Border Gateway goes up to 60ms (also in 10ms increments). The following Mitel devices and applications will support variable RTP packet rates: •...

  • Page 160: Service Provider Behavior

    RTP packet rates. Special attention should be paid to Mitel applications that operate on a release schedule that is independent from the 3300 ICP release schedule, such as NuPoint Unified Messenger.

  • Page 161: Automatic Route Selection

    No (within same subnet mask range) Further details on installation can be found in the Technician's Handbook and in the System Administration Tool Help for MiVoice Business. NUMBER PLANNING AND RESTRICTIONS The length of number plans for clustering and resiliency should be consistent among all units to prevent confusion in routing.

  • Page 162: Sip Trunking

    To minimize such instances, ensure that networked units operate with the same software release numbers or at least minimal differences between release levels. Please contact Mitel Technical Support to determine if such issues are likely when planning your upgrade.

  • Page 163: Third-Party Phone Compatibility

    IP Networking THIRD-PARTY PHONE COMPATIBILITY DeTeWe and SpectraLink sets support RFC 4733, NAT keep-alives, and utilize a single port for transmit and receive streams. As a result, these sets are compatible with an ICP that is using SIP trunking. SUPPORT FOR FAX OVER IP When using SIP trunks to connect the 3300 ICP to the service provider, G.711 FAX pass through and T.38 Fax over IP are both supported.

  • Page 164: Sip Aware Firewall

    Instead, a firewall that understands SIP can open up the ports for the right protocols just when the SIP traffic needs it. The 3300 ICP supports integration with SIP Firewalls. Mitel recommends that a SIP aware Firewall be configured as the Outbound Proxy through the Network Elements form. Then the SIP Peer Profiles can reference the Outbound Proxy Server and route all signalling via the Firewall.

  • Page 165: Tcp/Ip Port Usage

    The Live Communication Server uses ports 5060 and 5061 to communicate with the Live Business Gateway. • The Mitel Open Integration Gateway communicates with MiVoice Business using internal MiVoice Business component (Data Services) port 5320. • The Live Business Gateway (LBG) communicates with MiVoice Business using internal...

  • Page 166: Resiliency

    Names). The ICP does not support service resiliency using IP addressing, but it can use FQDNs to make use of service resiliency. For details, refer to the 3300 ICP Resiliency Guidelines. Mitel resilient call state and call survivability is not supported in conjunction with SIP trunking. 911 EMERGENCY SERVICES SIP trunking supports 911 emergency services.

  • Page 167: Chapter 10 Licensing

    Chapter 10 LICENSING...

  • Page 169: System Licenses

    In MCD 4.1 and later, an IP user license is needed for every user and device connected to the MiVoice Business system as their primary controller. IP user licenses are not required on secondary (resilient) controllers or on "userless" devices that provide basic functionality (emergency/attendant calls and hot desk login).
  • Page 170 Engineering Guidelines In MiVoice Business Release 7.2 and later, if no IP User (IPU) license is available (none is allocated or all are consumed), the system automatically consumes an available Multi-device User (MDU) license on behalf of the following IPU users: Full Service IP User, IP Console, External Twin Multi-device User Group.
  • Page 171 Multi-Device License instead of being individually licensed as users. In MiVoice Business Release 7.2 and later, MDU licenses are automatically consumed on behalf of the following IPU license users if no IPU license is available: Full Service IPU User, IP Console, External Twin Multi-device User Group.
  • Page 172 In the systems using dedicated MiVoice Business/3300 ICP hardware, additional DSP hardware must be added in order to enable compression. For MiVoice Business in commercial servers, compression resources are provided in software by the Media Server component (software blade).
  • Page 173 In Release MCD 4.1 and earlier, a licensable option is required to enable Tenanting on the MiVoice Business system. The Tenanting package allows the MiVoice Business system to be configured to look like a separate system to each participating tenant. The functionality...

  • Page 174: Device Licensing

    Engineering Guidelines DEVICE LICENSING The 3300 ICP requires a number of device licenses in order to operate. The following table lists these licenses. Table 42: Devices and licenses - MCD Release 4.0 and Earlier DEVICE LICENSE IP phone IP device license User on IP phone IP user license User on SIP phone...
  • Page 175 Licensing Table 42: Devices and licenses - MCD Release 4.0 and Earlier (continued) DEVICE LICENSE Fax over IP (T.38) licenses A T.38 license is required to allow T.38 transmission or reception of Fax over an IP or SIP trunk when the call path may encounter TDM interfaces—for example, T1/E1 trunks, analog loop start trunks, or ONS ports.
  • Page 176 Engineering Guidelines Table 43: Devices and licenses - Release 4.1 and later DEVICE LICENSE IP phone IP user license User on IP phone IP user license User on SIP phone IP user license Resilient User on SIP Phone No user license required on resilient controller User on ONS Phone Analog line license CITELink phone...
  • Page 177 Licensing Table 43: Devices and licenses - Release 4.1 and later (continued) DEVICE LICENSE Compression (TDM/IP) A Compression license is needed for TDM to IP or IP to TDM calls that require the use of the DSP compression. One Compression license can handle up to 8 calls Teleworker Solution (6010) One IP user license per phone...

  • Page 178: Licensing Limits

    Engineering Guidelines LICENSING LIMITS Available resources determine if license limits can be achieved. For example, if there is insufficient DSP for voice mail, the operational limit may be reached before the license limit. Be very careful with large numbers of licenses for voice mail and compression. Because DSP resources are allocated at initialization based on license numbers, not traffic requirements, it is possible to allocate all DSP resources and have nothing left for telecom tone receivers and generators, so calls cannot be made on the system.

  • Page 179: Licensing Example

    Licensing LICENSING EXAMPLE The following example shows how to determine the number of licenses required. For more accurate traffic calculations, contact Customer Engineering Services. Please note that the numbers below are approximations. Consider an installation with two headquarters and one remote office connected to the first headquarters.
  • Page 180 Engineering Guidelines • IP phone License In MCD Release 4.0: This is a package number and is covered by the number of IP device and IP user licenses. It is also possible to buy 620 IP phone licenses and additional 600 IP device licenses for resiliency.
  • Page 181 Licensing Note: The numbers and calculations are a rough estimation. More accurate results can be obtained by using the System Engineering Tool.

  • Page 182: Application Management Center (Amc)

    Engineering Guidelines APPLICATION MANAGEMENT CENTER (AMC) The online licensing process managed by the Mitel Application Management Center (AMC) allows Solution Providers who have accounts on the AMC to manage software licenses online. Each company is able to supply customers instantly if new licenses are required. Refer to “Requirements for AMC Connection”...

  • Page 183: Chapter 11: Bandwidth, Codecs And Compression

    Chapter 11 BANDWIDTH, CODECS AND COMPRESSION...

  • Page 185: Bandwidth, Bandwidth Management, Codecs And Compression

    CALCULATING AND MEASURING BANDWIDTH Notes: 1. To calculate and measure bandwidth, use the Mitel calculator rather than a third-party tool. The Mitel calculator uses 802.1p/Q (8100) frames, which ensure the highest degree of accuracy. Many third-party tools use standard Ethernet (0800) frames, which are less accurate and do not account for VLANs.
  • Page 186 Engineering Guidelines Note: Some network analyzers will not monitor the full Ethernet frame, excluding checksums and synchronization data, and therefore they give a bandwidth somewhere between wire and IP bandwidth. For the example shown, this would typically be 87.2 kbps, including VLAN. What is the media bandwidth? Depending upon how this is measured, this could be simply the payload bandwidth, which is similar to TDM, or it could be the bandwidth of the packet carried across the network.
  • Page 187 Bandwidth, Codecs and Compression Table 46: Ethernet/LAN IP and On-the-wire Bandwidth CODEC: G. 711 G.729 G.722.1 PAYLOAD: 64 KBITS/S 8 KBITS/S 32 KBITS/S LINK PACKET TYPE RATE (MS) WIRE WIRE WIRE Ethernet 10ms 96.0kbits/s 129.6kbits/ 40.0kbits/s 73.6kbits/s 64.0kbits/s 97.6kbits/s 20ms 80.0kbits/s 96.8kbits/s 24.0kbits/s...

  • Page 188: Bandwidth Availability

    Engineering Guidelines Table 47: Other Protocols: On-the-wire Bandwidth (continued) CODEC: G.711 G.729 G.722.1 PAYLOAD: 64KBITS/ 8KBIT/S 32KBIT/S LINK TYPE PACKET RATE (MS) WIRE (KBITS/S) WIRE (KBITS/S) WIRE (KBITS/S) VoATM (AAL5, IP) 10ms 127.2 84.8 84.8 20ms 106.0 42.4 63.6 30ms 98.9 28.3 56.5...
  • Page 189 Bandwidth, Codecs and Compression synchronous telecom link, these issues are resolved through mechanisms such as framing data into fixed timeslots. The following table contains some simple guidelines for LAN and WAN links. Table 48: LAN and WAN Link Guidelines PERCENTAGE OF DATA CONNECTION TYPE BANDWIDTH AVAILABLE EXAMPLE...
  • Page 190 Engineering Guidelines the 40% available bandwidth is reduced to 30% for a half duplex link, and the number of voice channels is reduced accordingly. The ratio from half duplex to full duplex is four (not two) because conversations need both a talk path and a listen path.

  • Page 191: Bandwidth Management

    Bandwidth, Codecs and Compression BANDWIDTH MANAGEMENT This section details the new bandwidth management solution. BANDWIDTH MANAGEMENT AND CALL ADMISSION CONTROL The terms “Bandwidth Management” and “Call Admission Control” are often used interchangeably to mean the management, and potential re-routing, of calls across an IP network between end devices.
  • Page 192 More details on programming and defining zones are highlighted in the System Administration Tool Help for MiVoice Business. Some typical network deployments are shown below, along with how they would be realized using the tree topology information.
  • Page 193 Bandwidth, Codecs and Compression Figure 22: Fully Meshed WAN Connections - Deployment Example Table 51: Fully-meshed Network with WAN as the Root ZONE PARENT Root (WAN) Root (WAN) Root (WAN) In a multi-node installation, it is also possible to link a single VPN back to headquarters at another site using a star configuration.
  • Page 194 Engineering Guidelines Figure 23: Fully-meshed WAN Connections - Star Configuration Non-meshed WAN connections If all VPNs terminate at the HQ access router in a star configuration, then connections between remote nodes will use bandwidth twice on the access link to HQ, and this needs to be counted. An example of a business configuration like this is a franchise where internode traffic is either limited in volume or regulated by call control.
  • Page 195 Bandwidth, Codecs and Compression Table 52: Non-meshed WAN ZONE PARENT Root (1) Root (1) Root (1) This non-meshed configuration is a little different, as it requires that data be forced to travel back through the central control node. This configuration requires that the “Media Anchor” function be used, and that all outlying nodes be treated as independent units.
  • Page 196 Engineering Guidelines The configuration table will look similar to that in Table 53. Table 53: Non-meshed Configuration ZONE PARENT PERIMETER ANCHOR MANAGER BANDWIDTH none none none Unit A in Zone 1 1024 kbps Unit B in Zone 2 256 kbps Unit C in Zone 3 256 kbps Deployment boundaries...
  • Page 197 MPLS, or xDSL. Although the payload (IP) is common to these WAN protocols, the bandwidth on the physical wire link may not be. The MiVoice Business system considers the throughput, or payload bandwidth, with some minor overhead and is defined in...

  • Page 198: Codec - Introduction

    Engineering Guidelines Table 54: CODEC Throughput CODEC TYPE IP PAYLOAD + %OVERHEAD G.711 G.722.1 (32k) G.729 Therefore, define the link bandwidth based on the IP throughput. An alternative method is to determine the physical wire bandwidth and define the number of voice streams, or “channels”, that are required or achievable across the link, using the physical wire bandwidth per connection.

  • Page 199: Voice Quality And Codec Selection

    Bandwidth, Codecs and Compression The wideband codec used by Mitel is G.722.1 at 32kbits/s/ (which is not to be confused with the G.722 wideband codec, or the G.722.1C codec, or the G.722.1 at 24kbits/s). Mitel currently uses the following CODECs in IP Telephony: •...
  • Page 200 For software releases prior to MCD Release 5.0 SP2, the AddCodecFilter and Remove- CodecFilter maintenance commands allowed the Administrator to specify which CODECS would be offered for negotiation by devices at each end of a call within the MiVoice Business network.
  • Page 201 Bandwidth, Codecs and Compression Table 57: Codec Zone Interconnects ZONE INTRAZONE INTERZONE ROUTE INTERCONNE COMPRESSI COMPRESSI COMPRESSI TO ZONE 1 TO ZONE 2 G.729 G.722.1 G.722.1 G.711 G.711 G.729 G.729 G.722.1 G.722.1 G.711 G.711 Auto* G.729 G.722.1 G.722.1 G.711 G.711 Zone 1 Yes** G.729...

  • Page 202: Operation Through Mivoice Border Gateway And Src

    The SIP Gateway is capable of G.722.1 and G.711 • The SIP Gateway is associated with Zone1 • The MiVoice Business controllers are capable of G.711 and G.729 • The default settings for inter and intra-zone codec selection are in operation Figure 26: Codec Zone Interconnect Example OPERATION THROUGH MIVOICE BORDER GATEWAY AND SRC At Release MCD 5.0 and MBG 6.1, there is no transcoding support for the wideband G.722.1...

  • Page 203: Compression - Introduction

    Bandwidth, Codecs and Compression COMPRESSION – INTRODUCTION Generally when compression is mentioned, it is usually mentioned with a CODEC, for example, “G.729 Compression.” This just refers to the ability to reduce the amount of data that needs to be carried across the IP infrastructure. In the case of CODEC compression, this works by reducing the amount of data that needs to be carried in the voice payload.
  • Page 204 If the controller has DSP-II fitted, this is capable of up to 64 compression sessions per module. • No more than 999 compression zones are possible from a single MiVoice Business/ICP system. • E2T compression is used primarily to deal with TDM devices such as ONS phones or PSTN connections.

  • Page 205: Trunking Gateway Working Example

    Bandwidth, Codecs and Compression IP applications and compression Most Mitel IP-based applications support compression. NuPoint does not support compression. To get the best voice quality performance from devices such as Speak@Ease™ and IP voice mail, allocate them in a common compression zone with other devices not running compression, e.g.

  • Page 206: Ip Networking Routes And Compression

    Engineering Guidelines IP NETWORKING ROUTES AND COMPRESSION Compression can be enabled in IP networking routes between 3300 ICP units if the end devices are capable of this operation. For more details see “Compression zones” on page 192. Compression zones This section briefly describes compression zones, IP trunk routes, and network issues to consider when planning the location of different devices.

  • Page 207: Ip Trunk Routes And Compression

    Bandwidth, Codecs and Compression the two phones stream directly within the LAN. This call could also be blocked if there are insufficient IP trunk sessions or channels allocated. • A controller can have a maximum of 999 compression zones. More details on zones and setup can be found in the Technician’s Handbook and the installation documentation.
  • Page 208 Engineering Guidelines • Compression can be used with calls to voice mail. Each of these calls consumes a com- pression license if the call would normally use compression when connected to a TDM device. • Music-on-Hold (MOH) that is passed to a device that normally uses compression consumes a compression license.

  • Page 209: Chapter 12: Network Configuration Concepts

    Chapter 12 NETWORK CONFIGURATION CONCEPTS...

  • Page 211: Introduction

    Network Configuration Concepts INTRODUCTION This chapter provides a high-level overview of the network settings and configurations required for a Voice-over-IP (VoIP) installation with the 3300 ICP when used in a business or Enterprise environment. The concepts below will help you understand more about network configurations. Table 60 shows a list of the topics in this chapter and a description of what you will find in each one.

  • Page 212: Network Configuration Guidelines

    Automatic configuration is “VLAN Membership Policy Server (VMPS)” on the simplest and preferred operating mode. page 257 “MiVoice Business and 3300 IP Ports” on page 275 TOS/DSCP to COS conversion can provide additional priority “Network Priority Mechanisms” on page 212 marking when PCs are used as voice devices.
  • Page 213 Network Configuration Concepts Table 61: Network Configuration Guidelines (continued) GUIDELINE FOR MORE INFORMATION The controller should be located behind a network Layer 2 “LAN architecture” on page 206 switch. Ensure that the PPS rate of the routers and switches is “WAN layer 3 priority”...
  • Page 214 Note: None of these reserved addresses can be used by devices that need to communicate with the 3300 ICP (e.g. MITEL Phones, E2TMiVoice Business Virtual). These reserved IP address ranges can be used elsewhere in an IP network (i.e. network not connected to the 3300 ICP).

  • Page 215: Voice-Over-Ip Installation Requirements

    For more information on these possible network issues, see “Basic Concepts” on page 203. Each Mitel device uses a jitter buffer that has been optimized for the device's intended usage: • 52xx and 53xx IP Phones use an 800 ms dynamically adjustable jitter buffer.
  • Page 216 Where encryption is used, additional delay may also be added to the data. • Teleworker: The Mitel Teleworker Solution is for remote workers who need to connect to the Internet and send traffic through a business firewall and NAT combination.

  • Page 217: General Guidelines For Quality Of Service

    Network Configuration Concepts GENERAL GUIDELINES FOR QUALITY OF SERVICE The main issues that affect system installation and user perceptions are • Quality of service (voice quality during the call) • Availability of the service (setting up and clearing voice connections or signalling) The challenge is to engineer the network to ensure that these quality requirements are met.

  • Page 218: Packet Loss

    Engineering Guidelines Extensive use of hubs rather than switches also introduces jitter. Hub use for larger networks and where connections are shared with data devices is not advised. Use of multiple WAN connections and load-sharing can also introduce jitter due to different path delays.

  • Page 219: Transcoding And Compression

    Network Configuration Concepts Some carriers may also offer an SLA that honours and provides queuing for incoming (download to the customer) data as well. There may be an additional charge, but this will provide the added queuing on the far end of the often bandwidth limited connection between the customer and the carrier.

  • Page 220: Hub Network Versus Switched Network

    Engineering Guidelines to point connections. For these reasons the G.722.1 CODEC is only supported on IP end devices. The G.722.1 wideband codec is also supported by some 3rd party SIP products, so allowing for interoperability of this feature between different vendor end devices. HUB NETWORK VERSUS SWITCHED NETWORK The best network configuration is one that is entirely switched.
  • Page 221 Network Configuration Concepts If there are physically separate networks for voice and data traffic, you may still need to link these networks together and to manage the 3300 ICP from within the data portion of the network. In this case, a router is required. Core network The core network potentially carries data on dedicated links at 1 Gbps or higher.

  • Page 222: Operating With Sx-2000 And Third-Party Pbxs

    SX-2000 or third-party PBX should be connected to the 3300 ICP via digital trunks. Mitel's Line Measurement Tool should be run during installation so that the 3300 ICP employs the correct analog trunk parameters. This will ensure proper matching between the 3300 ICP and the analog trunk and result in optimum audio quality.

  • Page 223: Maintaining Voice Quality Of Service

    Integrator services could carry out an evaluation. The Mitel Consultants and Integrators can be contacted through the following pages on Mitel On Line: • http://domino1.mitel.com/mol/servsol.nsf/ServSolApp?OpenForm • Or log on to Mitel On Line, > Services > Professional Services > Request a Quote...

  • Page 224: Network Measurement Criteria

    Although ping can be used as a quick check or as a backup method, it is recommended that networks be fully evaluated before installation. Mitel Consultants and Integrators, can provide Professional Services to perform a full VoIP network pre-installation evaluation.

  • Page 225: Serialization Delay

    Network Configuration Concepts Bandwidth management and call admission control can be used to ensure that voice quality is maintained in parts of the network where there may be bandwidth constraints. For details, refer to “Bandwidth, Bandwidth Management, Codecs and Compression” on page 171. Refer to the 3300 ICP Resiliency guide for detailed calculations and breakdown of signalling messages for different connections.

  • Page 226: Network Priority Mechanisms

    Engineering Guidelines By modifying the router MTU value to approximately 500, larger packets are divided up and sent in smaller chunks. The result of this is that there are three times as many opportunities to send the voice data. Thus the data rate link could be reduced to 300 kbps. Note: Some routers do not function with an MTU as low as 500.

  • Page 227: Lan Layer 2 Priority

    Network Configuration Concepts • Layer 2 in the LAN through use of IEEE 802.1p/Q • Layer 3 in the WAN through use of DiffServ/TOS/Precedence CAUTION: If a PC is introduced into the same subnet as the IP phones, whether it is behind a phone or even connected to a Layer 2 device within the subnet, the Quality of Service cannot be guaranteed without the use of VLAN and careful network engineering.
  • Page 228 Engineering Guidelines ports that need to convey multiple VLANs/802.1p priorities must use tagging. This includes ports used between LAN switches and ports connected to dual-port phones. With dual-port phones, it is important to configure the LAN switch to use tagging for the voice VLAN and no tagging for the default VLAN, to ensure that voice packets are properly prioritized over data applications from the PC.
  • Page 229 Network Configuration Concepts • Hubs don’t support priority queuing, so use managed Layer 2 switches with 802.1p/Q support. • Do not use VLAN 4095 with HP products; this is reserved for inter-switch use. • Do not use VLAN 4094 with the CXi controller. Cisco port examples The following data is collected from the command line interface (RS232 connection).
  • Page 230 Engineering Guidelines this range. As a general rule, VLAN 0 is treated in different ways by different vendors. The recommendation is not to use VLAN 0. Cisco also reserves VLAN 1000 and upward for Cisco purposes, so ensure there is not a conflict when using these higher VLAN numbers.

  • Page 231: Wan Layer 3 Priority

    The DSCP value is programmed using DHCP server option (see “DHCP Option Reclassification” on page 245). This is picked up by the IP phones. The default Mitel values for DSCP was previously fixed at 44 to allow backward compatibility with older TOS based routers.
  • Page 232 Once a TOS value, or DSCP, is chosen, it generally never changes. The voice application sets the appropriate values before data is sent. For networks based around legacy TOS and Precedence routers, the Mitel voice applications should use the TOS value of 0xB0, or 176 decimal, or 0xB8 (184 decimal), for the Type-of-Service field, providing a precedence of five with minimum delay (the D-bit is set).

  • Page 233: Network Topology With Priority

    Network Configuration Concepts phones, only 50 PPS goes one way and 50 PPS in the return direction. Throughput is 100 PPS. In the following figure, the router has a port handling capacity of 15,000 PPS. Throughput is half this number; i.e. 7500PPS. Figure 34: Packet-per-second throughput example NETWORK TOPOLOGY WITH PRIORITY The following network diagram highlights the use of the dual-port phones and the configuration...

  • Page 234: Lan Qos Policies

    Engineering Guidelines tagged, but traffic from the data VLAN must be sent untagged for the devices that are not able to handle VLAN information. The requirement to use VLAN and priority queuing becomes obvious when both data and voice information must share a link between units within the network. It is important that the deterministic voice information gets priority over the non-deterministic data traffic.

  • Page 235: Use Of Subnets And Subnet Size

    DSCP values based on data type, such as UDP or RTP, or use of TCP and UDP ports. See “MiVoice Business and 3300 IP Ports” on page 275 for more details on ports used by the phone.

  • Page 236: Full Duplex And Half Duplex Settings

    Engineering Guidelines FULL DUPLEX AND HALF DUPLEX SETTINGS It is recommended that all LAN connections use full duplex settings. This ensures maximum bandwidth and minimum delay. WAN links are typically specified as full duplex. Note: The terms “full duplex” and “half duplex” are often used at the phone to describe the hands-free operation.
  • Page 237 Network Configuration Concepts • It appears as though a phone connected via a half duplex link takes up more bandwidth, but in reality it takes up more time. Conclusion: Use full duplex Ethernet connections for maximum performance. Configure any 3300 ICP network port for auto-negotiation so that the network devices can select the best quality settings.

  • Page 238: Maintaining Availability Of Connections

    Engineering Guidelines MAINTAINING AVAILABILITY OF CONNECTIONS The quality of service for signalling measures how long a user needs to wait before a service becomes available, or whether the user becomes blocked from using a function. For example, delays in receiving dial tone, or blocking that occurs if there are insufficient PSTN trunks degrade the quality of service.
  • Page 239 Network Configuration Concepts • 10 IP phones over a T1 link at a remote site. • Trunk traffic is 65% of all traffic. • Traffic between remotely located IP phones stays local to the remote site (it does not traverse the WAN link). Figure 36: WAN traffic example Table 64: CCS calculation example CALCULATION...

  • Page 240: Ip Networking And Use Of Compression

    Engineering Guidelines • The blocking ratio can be changed to P.01, and such a link would handle 68.8 CCS. • The number of remote phones or the overall number of phones can be reduced. • Ensure that QoS/Priority mechanisms are in place and active. These are all potential solutions and each has to be investigated to understand the nature of the installation.

  • Page 241: Ip Networking Limit Working Example

    Network Configuration Concepts Since the bandwidth is derived from the number of conversations, it is important to understand which CODEC is used across the link (G.729a, G.711, or a combination of both). Note: Music On Hold and messages to and from Voice Mail can be handled with G.729a, if available.
  • Page 242 Engineering Guidelines Figure 37: IP trunk limit example Table 65: IP networking limit calculations CALCULATION FORMULA RESULT Traffic from IP sets Number of sets (250) x 6 CCS 1500 CCS Percentage networked Total traffic x 15% 225 CCS Percentage traffic intercom Networked traffic x 35% 79 CCS Percentage traffic trunk to PSTN...

  • Page 243: Firewalls And Nat

    Network Configuration Concepts Note: • Seven channels are needed for internal traffic and ten are needed for external traffic, but together the total is only 13. The reason is that a number of channels have shared use: in this case, it is 4 (10+7-13). The higher G.711 rate is used to ensure adequate bandwidth at all times.
  • Page 244 Engineering Guidelines...
  • Page 245 Chapter 13 NETWORK CONFIGURATION SPECIFICS...

  • Page 247: Network Configuration Specifics

    Through” on page 265 “Fax and modem connections over IP using G.711 Pass Through” on page 265 “MiVoice Business and 3300 IP Ports” on page 275 “IP Address Restrictions” on page 289 “Cables and Connections” on page 290 “IP Phone LAN Speed Restrictions” on page 293...

  • Page 248: Start-Up Sequence And Dhcp

    Diffserv Codepoint (DSCP, Layer 3 priority) STARTUP SEQUENCE FOR PHONES Note: The 5302 start up sequence differs from the method used by other Mitel phones. Refer to “5302 Startup and DHCP” on page 243 for information about the 5302 phone.

  • Page 249: Sources That Can Be Used To Obtain Network Policy Information

    Network Configuration Specifics SOURCES THAT CAN BE USED TO OBTAIN NETWORK POLICY INFORMATION Table 67 indicates which LAN Policy parameters can be obtained from each of the different sources of information. Table 67: Sources of Network Policy Information DEFAULT GATEWAY VLAN L2 QOS TFTP...

  • Page 250: Vlan Setting Information Sources And Priorities

    Engineering Guidelines Note: If a phone has obtained network configuration information via manual programming, this information will be held by the phone permanently, i.e. other methods cannot overwrite these values and the values will be maintained even if the phone is rebooted.

  • Page 251: Potential Issues With Using Lldp-Med In Cisco Environments

    Network Configuration Specifics Table 69: Priority levels for the Various Sources of L2/L3 QoS Settings SOURCE OF L2 & PRIORITY L3 QOS SETTINGS LEVEL NOTES Manual Entry (Static) Programmed by installer DHCP The first time a phone receives DHCP information it must contain an IP address for the RTC and the TFTP server.

  • Page 252: Lan Policy Values For Media, Signalling And Other

    Engineering Guidelines Since these values are non-user programmable they cannot be changed by the system administrator. These values do not provide the correct priority levels for voice media at either L2 or L3, therefore the use of these values will potentially cause severe voice quality issues. The Solutions: 1.

  • Page 253: Dscp Settings For Call Signalling In Cisco Environments

    Network Configuration Specifics When it is desired to use separate voice and signalling priorities, Mitel recommends the following: • Voice DSCP 46, 802.1p '6' • Signalling DSCP 26, 802.1p '3' • Other DSCP 0, 802.1p ‘0’ The new Cisco LAN Policy defaults pre-defined in AutoQoS are: •...

  • Page 254: Lldp-Med And Ip Phone Network Policy

    Engineering Guidelines The sequence above assumes that the phones get information from a DHCP server. The information can also be manually entered into a phone as it starts to boot up, to make sure the information is fixed and requires little DHCP intervention. This method is particularly useful if a phone is used on a remote WAN link and the router cannot forward DHCP requests, or if a local DHCP server does not exist.
  • Page 255 VLAN). With this method, it may also be easier to use the 3300 embedded DHCP server to provide only the remaining configuration values, with LAN policy coming from LLDP-MED, removing the need for any Mitel-specific configuration in 3rd party DHCP servers.

  • Page 256: Ip Phones And Vlan Programmability

    Engineering Guidelines Table 70: Phones and LLDP-MED Names(continued) PHONE MODEL NAME REPORTED IN LLDP-MED 5312 IP Phone "MITEL 5312 IP" 5320 Dual Mode "MITEL 5320 DM" 5320e "MITEL 5320e IP" 5324 IP Phone "MITEL 5324 IP"; 5330 Dual Mode "MITEL 5330 DM"...

  • Page 257: Rfc 3942, Reclassifying Dhcp Options: Detewe And Spectralink Phones

    DeTeWe has provided a solution for their DECT phones regarding the DHCP options reclassification, however, it is not aligned with the Mitel solution and will require custom configuration of the ICP internal DHCP server or 3rd party DHCP servers. For details, refer to DeTeWe documentation.

  • Page 258: Startup Sequence For The Controller

    MITEL COMMUNICATION DIRECTOR The Mitel Communication Director does not support an integral DHCP server. The 3300 internal DHCP server can be used if a 3300 ICP is included in the installation. Otherwise a third party DHCP server must be provided.

  • Page 259: Dhcp Option Reclassification

    Network Configuration Specifics DHCP OPTION RECLASSIFICATION Mitel’s legacy IP device configuration approach, using DHCP options 128 – 135 is still supported, but the preferred methods based on either DHCP options 124/125 or 60/43 are recommended. The standards based options (124/125 and 60/43) will remove potential DHCP conflict with other devices and manufactures that may be using the same DHCP server for optional information.

  • Page 260: Ip Phone Behavior

    Note: The “Encapsulated vendor-specific options” formatting as defined in RFC 2132 and RFC 3925 is not normally used in the Mitel-specific exchange, however it is accommodated by the IP Phone in order to support 3rd party DHCP severs that require it.

  • Page 261: Vendor Information Data Format (Options 125 And 43)

    “id:<mitel_id><separator><tag/value> <separator><tag/value>... “ where: <mitel_id> is the Mitel discrimination string “ipphone.mitel.com”, <separator> is a separator special character ';' For each <tag/value> pair, encoding is in the form: “<tag>=<value>” The following rules apply to parsing of all tag/value pairs. The internal DHCP Server applies these tag/value parsing rules.

  • Page 262: Support Of Solution By External Dhcp Servers

    Note: If the customer DHCP servers are not able to support either option 60/43 or option 124/125 exchanges, then the customer must either configure their external DHCP servers using the old option 128-135 range, or use the Mitel ICP-embedded DHCP servers.

  • Page 263: Dhcp Lease Time

    Note: It is possible to run out of IP addresses with permanent leases, so Mitel recommends minimizing use of these addresses. For example, a laptop user who roams from office to office plugs in the laptop, receives a permanent address, and then disconnects the device.
  • Page 264 Engineering Guidelines Block size is not user configurable on either the 3300 or the phone, however TFTP block size could be user configurable on some 3'rd party external TFTP servers. In situations where phones are accessing an external TFTP server over a very slow connection reduce, if possible, the transmitted block size from 4096 to a smaller number;...

  • Page 265: Vmps, Cdp, And Location Change Indication (E911)

    Network Configuration Specifics VMPS, CDP, AND LOCATION CHANGE INDICATION (E911) The MiVoice IP Phones at Release MCD 4.0 and higher include: • Support of dual-port IP phone operation in the presence of Cisco VLAN Membership Policy Server (VMPS) security and dynamic VLAN configuration. •...

  • Page 266: Stp

    Some additional tuning may be needed to the settings to get full operation. MiVoice Business can apply different LAN QoS policies to voice packets, signalling packets and other packets. The LAN Policy (QoS) form in ESM is used for setting the LAN QoS policy...

  • Page 267: Port Settings

    Network Configuration Specifics In a Cisco based environment the recommended settings are: • Voice Packets: DSCP: 46, 802.1p:5 • Signalling Packets: DSCP: 26, 802.1p:3 *(see note, below) • Other Packets: DSCP:0 802.1p:0 * Note: Newer Cisco installations will support DSCP 24 especially if Autqos is used. Older Cisco installations may be configured for DSCP 26.

  • Page 268: Applications And Other Voice Servers

    Engineering Guidelines be equally configured. The Ethernet switch ports must not be set to portfast because the 3300 ICP is an active device in this protocol. Table 76: Multiple Network Connections MULTIPLE NETWORK PRODUCT RELEASE CONNECTIONS LOOP HANDLING IN 3300 ICP Release MCD 4.0 and Basic STP higher...

  • Page 269: Mivoice Ip Phone

    Network Configuration Specifics MIVOICE IP PHONE The MiVoice IP Phones are compatible with CDP and are able to utilize this information for VLAN and location change discovery, when available. In order to ensure that these work as expected, it is recommended that ports connected to MiVoice IP Phones and using CDP have the cdp timer and cdp holdtime values left at their default values of 60 and 180 seconds respectively.
  • Page 270 Engineering Guidelines 2. LLDP-MED 3. CDP 4. DHCP. The ability to provide partial information at each stage allows these modes to be used together to ease installation. For example, the IP phone’s IP address may be supplied manually, but the RTC address could be picked up via DHCP.

  • Page 271: Vlan Membership Policy Server (Vmps)

    Network Configuration Specifics The commands required to change the network port settings are: Switch(config)# interface fastethernet0/1 Switch(config-if)# switchport mode access Switch(config-if)# switchport access vlan 100 Switch(config-if)# mls qos trust cos Switch(config-if)# mls qos cos 0 Switch(config-if)# wrr-queue cos-map 4 5 Switch(config-if)# priority-queue out Switch(config-if)# switchport voice vlan 2 Switch(config-if)# spanning-tree portfast...
  • Page 272 Engineering Guidelines compatible with the Auxiliary_VLAN setting in CDP can be used with another attached device, such as a PC. An IP phone that cannot determine the Auxiliary_VLAN setting will be treated as a single end device, and require an entry in the VMPS database. When the VMPS (Server) is enabled, a MAC address to VLAN mapping database is downloaded from a TFTP server and VMPS begins to accept client (access switch) requests.

  • Page 273: Vmps And Network Switch Software Revisions

    Network Configuration Specifics • A port that enters the “shutdown” state blocks all access. This includes a connected IP phone, if the attaching PC is not accepted. • The VTP management domain of the VMPS client and the VMPS server must be the same. •...
  • Page 274 Engineering Guidelines Shutting down a port is a good way to restrict access, but it will also affect the operation of the phone, or any other device, attached to this port. CAUTION: Shutting down a port could be considered a form of denial of service. Simply plugging a rogue PC into a number of network ports could disable access to legitimate users.

  • Page 275: Network Considerations

    “T.38 FoIP Guidelines” on page 267 • “Bandwidth Management” on page 272 • “T.38 Frequently Asked Questions” on page 274 • “MiVoice Business and 3300 IP Ports” on page 275 • “IP Address Restrictions” on page 289 • “Cables and Connections” on page 290 •...

  • Page 276: Wireless Phone Performance On The 3300 Icp

    A TFTP server for the SVP server (which, by default, will be the 3300 ICP). MITEL WLAN PHONES The Mitel WLAN Stand can be configured as an IEEE 802.11b/g (Wi-Fi) compliant Access Point and as a Wi-Fi compliant Client. A number of 5200 and 5300 series phones can be connected to the WLAN Stand when it is configured as a client.

  • Page 277: Dect Wireless Phones For Deployment In Europe And North America

    Network Configuration Specifics The DeTeWe DECT-IP, OPS27 wireless phones can be registered as resilient phones. The OPS27 phones register with the ICP as Mitel 5220 IP Phones and the Resiliency Guidelines for MiVoice IP Phones are also applicable to these DECT-IP phones.

  • Page 278: Coverage And Capacity

    Spectralink web site. The URL is http://support.spectralink.com/SpectralinkService/support/us/support/voice/index.html. Additional information can be found on the Mitel On Line Web Site, under "Products and Services", then under “Applications”, and then finally, "Wireless". COVERAGE AND CAPACITY...

  • Page 279: Fax And Modem Connections Over Ip Using G.711 Pass Through

    Network Configuration Specifics • Transmission of data and voice over an RF link presents potential security issues that system administrators and users should be aware of. For example, it is recommended that encryption be enabled. • Electro-Magnetic Interference generated by wireless phones and PCs might need to be considered in sensitive environments such as health care facilities, research laboratories and some industrial sites since this interference could affect the operation of critical equip- ment in the facility.

  • Page 280: T.38 - Reliable Fax Over Ip Transport

    Engineering Guidelines • The IP trunk link must use G.711 only. • The rate of packet loss on the link must be less than 0.1%. • The link delay must be below 200 ms. • Jitter must be less than 30 ms (ideally less than 20 ms). With these settings, G3 FAX at V.17 speeds has been found to work with good reliability as compared to standard TDM connections, however without error correction mechanisms such connections should only be considered as best effort.

  • Page 281: Dtmf Signalling Over Ip Networks

    T.38 is the protocol recommended by the ITU to allow for transmission of real-time Group 3 Fax transmission over IP networks. Mitel's T.38 implementation support V.17 speeds. Fax calls that are v.34 based will be handled at V.17 speeds by the 3300 ICPs.

  • Page 282: Dsp Ii

    The open standard signalling protocol used for establishing T.38 calls is SIP Version 2.0, which is based on RFC-3261. • A T.38 call from a 3300 ICP to a 3300 ICP over an IP trunk will use Mitel's proprietary IP Trunk signalling protocol. •...

  • Page 283: Line Circuits And Cos Options

    This setting is a global setting; the setting is applied to all ports on a system. This setting can be found under "Fax Advanced Settings"; for details see the System Administration Tool Help for MiVoice Business. RESOURCES REQUIRED •...

  • Page 284: Dsp Provisioning

    Engineering Guidelines • At the start of a call a Fax Tone/V.21 detector is used to determine if the call is a fax call. After 60 seconds the detector is relinquished. Note: T.38 licenses are only required to allow an ICP to originate or to terminate Faxes sent over IP or SIP trunks, T.38 licenses are not required on an intermediate or tandem ICP.

  • Page 285: Intra-Zone Default Profile

    (14,400 baud) that the fax machines use to transmit the actual Fax data. • Mitel's T.38 solution uses UDP to transport ethernet packets. UDP does not have the ability to re-send packets if packets are lost, so packet redundancy is supported. This allows the Administrator to select the level of redundancy required for both the high speed and low speed portions of a fax call.

  • Page 286: What Happens If There Are Insufficient Dsp Resources Or T.38 Licenses

    G.711 pass through, however the success of the call cannot be guaranteed. BANDWIDTH MANAGEMENT • Mitel's Bandwidth Management solution will keep track of the Bandwidth consumed by Fax calls and Call Admission Control decisions will be made according to the system's configuration.
  • Page 287 Network Configuration Specifics Voice Network Limits END-TO-END PACKET LOSS JITTER DELAY < 0.5% < 20 ms < 50 ms Green = Go < 2% < 60 ms < 80 ms Yellow = Caution > 2% > 60 ms > 80 ms Red = Stop Fax over G.711 pass Through END-TO-END...

  • Page 288: T.38 Alarms

    Engineering Guidelines END-TO-END PACKET LOSS JITTER DELAY > 7% > 2000 ms > 6000 ms Red = Stop T.38 UDP, Low Speed Redundancy = 8, High Speed Redundancy = 3 END-TO-END PACKET LOSS JITTER DELAY < 7% < 1000 ms <...

  • Page 289: Mivoice Business And 3300 Ip Ports

    MIVOICE BUSINESS AND 3300 IP PORTS The table below shows the IP port numbers used with standalone MiVoice Business and 3300 ICP systems. It is not a definitive list, but is sufficient to identify voice connectivity. New features and applications may result in additions to this list.
  • Page 290 Engineering Guidelines MiVoice Business Release 7.2 improves telnet ports security by providing the ability to • change the security settings for the selected service; • add a trusted IP address for logging ports (this change is permanent); • close (or open) all Call Control (CC) services (by default, all CC telnet and log services are open).
  • Page 291 Network Configuration Specifics Table 79: MiVoice Business and 3300 ICP port numbers (continued) IP PORT NUMBER TRANSPORT FUNCTION 1754 Printer port 3300 VoiceFirst Videoconferencing (server connection) 3997 SAC-High Security SSL 3998 SAC-SSL 3999 PDA, Application communication 5009 Telephone Directory (eManager)
  • Page 292 The MSPLogs Viewer application communicates with MiVoice Business through port 7011. If the MiVoice Business system is behind a firewall, then port 7011 must be opened and routed to the system. Older versions of the switch (before MiVoice Business 7.0) will attempt to...
  • Page 293 TCP / 10990 (JavaRMI/Multi-Node Mngmt) TCP / 1066, 1067 (IP Networking) TCP / 1066, 1067 (IP Networking) UDP / 50000...50511 (Voice Media/RTP/SRTP) UDP / 50000...50511 (Voice Media/RTP/SRTP) UDP / 50000...50511 (Voice Media/RTP/SRTP) UDP / 50000...50511 (Voice Media/RTP/SRTP) Figure 39: MiVoice Business Port Diagram 1...
  • Page 294 TCP / 6830 (VM-CPMS) TCP / 15374 (IP-PMS) IP-PMS TCP / 23 (Telnet) TCP / 161 (SNMP) Netally Voila TCP / 4445 (Voice Reporting) Voice Quality TCP / 8181 (HTTP/Voice Statistics) TCP / 8182 (HTTPS/Voice Statistics) Figure 40: MiVoice Business Port Diagram 2...
  • Page 295 TCP / 443 (HTTPS) Enterprise Manager TCP / 5009 (Teldir/UDT) TCP / 5009 (Teldir/UDT) TCP / 7050 (SDS) TCP / 7011 (Data Servuces) TCP / 49500...49599 (Data Services) Port defined through port 7011) Figure 41: MiVoice Business Port Diagram 3...
  • Page 296 UDP / 5000...50511 UDP / 2000...30999 (RTP, SRTP) UDP / 2000...30999 (RTP, SRTP) UDP / 5000...50511 Destination Port Source Port No defined port number means anything is possible in the range 0 to 65535 Figure 42: MiVoice Business Port Diagram 4...
  • Page 297 TCP / 7011 (Data Services) Data Services Client TCP / 49500...49599 (Data Services) Port defined through port 7011 Destination Port Source Port No defined port number means anything is possible in the range 0 to 65535 Figure 43: MiVoice Business Port Diagram 5...
  • Page 298 Engineering Guidelines Internet TCP / 80, 443 (HTTP, HTTPS) Access TCP / 8080 (HTTP) Web Proxy TCP / 6880 (HTTPS) UDP / 53 (DNS) UDP / 67 (DHCP) DHCP UDP / 68 (DHCP) TCP / UDP / 5060 (SIP) PC/UCX UDP / 67 (DHCP) UDP / 68 (DHCP) UDP / 69, 20001 (TFTP)
  • Page 299 Network Configuration Specifics UDP / 53 (DNS) UDP / 67 (DHCP) DHCP UDP / 68 (DHCP) TCP / 5060 (SIP/Presence) MS-LCS UDP / 67 (DHCP) UDP / 68 (DHCP) TCP / 1606 (CSMSG) IP Console TCP / 6800, 6801, 6802 (MiNet, Secure MiNet) (PC) TCP / 6900 (MiNet) TCP / 7011 (Data Services)
  • Page 300 Engineering Guidelines UDP / 53 (DNS) UDP / 67 (DHCP) DHCP UDP / 68 (DHCP) TCP / 5060 (SIP/Presence) TCP / 6806 (SSL CSMSG) IP Console (PC) TCP / 6801, 6802 (MiNet, Secure MiNet) TCP / 6900...6999 (MiNet) TCP / 6807 (Secure MiXML) TCP / 10000, 10002 (MiNet, Secure MiNet) UDP / 50000...50511 (TX Recording) Teleworker...
  • Page 301 UDP / Ephemeral (Voice Media) IP End UDP / 50098...50508 (Voice Media) Device UDP / 50098...50508 (Voice Media) (IP Phone UDP / Ephemeral (Voice Media) Application) 5550 Console (soft) - Page 1 of 2 (Non-Teleworker Mode) Figure 47: MiVoice Business Console in LAN Mode...
  • Page 302 IP End UDP / 50098...50508 (Voice Media) UDP/1024...65535 (Voice Media) Device (IP Phone App) UDP/20000...30999 (Voice Media) UDP / 50098...50508 (Voice Media) 5550 Console (soft) - Page 2 of 2 (Teleworker Mode) Figure 48: MiVoice Business Console in WAN mode...

  • Page 303: Embedded Firewalls

    The 3300/MiVoice Business system will limit traffic based on current operating conditions and traffic expected to be handled. The phones use a “credit” system to limit unexpected packet rates and will discard if these limits are exceeded.

  • Page 304: Cables And Connections

    Engineering Guidelines CABLES AND CONNECTIONS Although often hidden, the cable plant provides the connection between the end user and the data service (the IP phone and 3300 ICP). Because data is sent at high speed, there are requirements that need to be met in order to get the best performance. Once sent, voice packets cannot be recovered, and so it is important to ensure that the cable plant is capable of handling the data without loss, or at worst a factor of 10 better than the guidelines for “green”...

  • Page 305: Ethernet Cable Distances

    Note: If connecting an ethernet device at distances of more the 100 metres, then a unit such as the Mitel Streamline should be used. The Streamline is a long haul ethernet switch that can provide ethernet connectivity with power over distances of up to 360 metres.

  • Page 306: Straight And Crossover Cables

    Engineering Guidelines STRAIGHT AND CROSSOVER CABLES Two types of cable connection are used to connect between network equipment devices and also from the network equipment to the end equipment: • Straight connection, used to connect end users to the network (for example, an IP phone to a switch) •...

  • Page 307: Ip Phone Lan Speed Restrictions

    Network Configuration Specifics Figure 51: Using Wire Color Order to Identify Connection Cables The cables shown are those expected in new installations, namely, a T568A connection to a T568A for a straight cable, and a T568B connection to a T568A for a crossover cable. It is also possible to get straight cables that have a T568B connection to a T568B, but these are more likely in older installations.
  • Page 308 Engineering Guidelines connections to these interfaces are made with RJ-45 connectors and the cable pairs used are compatible with CAT 5 wiring. In a structured wiring infrastructure, it is possible to mix both data and digital telecom and use common CAT 5 cable throughout. Only at the MDF/Termination point will the cables be routed in different directions.

  • Page 309: Appendix Acat 3 Wiring

    Appendix A CAT 3 WIRING...

  • Page 311: Cat 3 Wiring Practices

    CAT 3 Wiring CAT 3 WIRING PRACTICES Category 3 (CAT 3) refers to a type of UTP copper cabling that meets specific transmission characteristics (see CAT3/EIA/TIA-568 wiring standards). CAT 3 also refers to the installation practices observed when routing these cables as well as the interconnection and end point termination methods used.
  • Page 312 SX-200 ICP through option 131 and COS setting 280. The second port on the IP Phones can be disabled in the 3300ICP/MiVoice Business Class of Service (COS) form, option 193, under the heading “PC Port On IP Device – Disable”. Note that although the second port may be disabled for access, it may still be used for monitoring.

  • Page 313: Summary Of Cat 3-Specific Network Configurations

    CAT 3 Wiring SUMMARY OF CAT 3-SPECIFIC NETWORK CONFIGURATIONS There are a number of different installation combinations and devices that can run with CAT 3 cables. There are also many exceptions and variations that prevent this from working. The underlying principles in making the installation work are: •...
  • Page 314 Engineering Guidelines Figure 54: CXi/CXi II Minimum Cable Standard Note: Selection of the network port settings differs on the CXi/CXi II platform depending upon whether it is configured as an SX-200 ICP product or a 3300 ICP product. On the SX-200 ICP product a single port setting applies to all ports.
  • Page 315 CAT 3 Wiring Figure 55: CX, MX, MXe, AX, and LX Minimum Cable Standard...
  • Page 316 Engineering Guidelines...

  • Page 317: Appendix Binstallation Examples

    Appendix B INSTALLATION EXAMPLES...

  • Page 319: Using Cisco Routers And Catalyst Switches

    2. Layer 3 – IP priority is set using 6 bits within the IP header called Differentiated Services Code Point (DSCP). DSCP is used by routers to prioritize traffic. The Mitel default value was 44. This value is programmable to any value. Many IP networks expect a value of 46 - also called Expedited Forwarding (EF).

  • Page 320: Define The Ip Addressing

    Engineering Guidelines Note: MiVoice IP Phones set the 802.1q bits as they are using VLAN tagged traffic. However the ICP controller does not send VLAN tagged traffic and so cannot set Ethernet priority. The switch port the controller connects to should set the Ethernet priority. This also applies to other non-VLAN aware VoIP devices, such as NuPoint Unified Messenger Rel.

  • Page 321: Mivoice Ip Phone

    Installation Examples MIVOICE IP PHONE Each MiVoice IP Phone must know (as a minimum) • its own IP address • its subnet mask • its default gateway • its VLAN (not required by a PC) • its controller (not required by a PC). Note: A PC will also have other settings such as DNS and WINS that the MiVoice IP Phone does not require.

  • Page 322: Ethernet Switch 1 Configuration

    Engineering Guidelines The WAN link shown is a serial interface but could be any technology (Frame Relay, ATM, MPLS). Figure 56: Example Network Topology ETHERNET SWITCH 1 CONFIGURATION There are four physical connections in the example topology for Ethernet Switch 1. 1.
  • Page 323 Ethernet frames. When learning the voice VLAN via CDP (as configured) an 802.1p value of 5 is initially assumed. However, if the Mitel proprietary DHCP option 133 is used then this will overwrite the initial value. Mitel recommends an 802.1p value of 6 (unless using Cisco auto-qos).

  • Page 324: Ethernet Switch 2 Configuration

    Engineering Guidelines Switch1(config-if)# priority-queue out [makes queue 4 a strict priority queue] Switch1(config-if)# exit Interface fa0/5 is the VLAN trunk connection between Switch 1 and Switch 2. For Ethernet priority information to be sent between the switches the VLAN trunk must be configured. Switch1(config)# interface fa0/24 [connection to Router 1 fa0/0] Switch1(config-if)# description "Connection to Router 1...

  • Page 325: Ethernet Switch 3 Configuration

    Ethernet frames. When learning the voice VLAN via CDP (as configured), an 802.1p value of 5 is initially assumed. However, if the Mitel proprietary DHCP option 133 is used then this will overwrite the initial value. Mitel recommends an 802.1p value of 6 (unless using Cisco auto-qos).

  • Page 326: Router 1 Configuration

    Ethernet frames. When learning the voice VLAN via CDP (as configured) an 802.1p value of 5 is initially assumed. However, if the Mitel proprietary DHCP option 133 is used then this will overwrite the initial value. Mitel recommends an 802.1p value of 6 (unless using Cisco auto-qos).

  • Page 327: Setting Up Qos For Router1 Using Low Latency Queuing

    Create an Extended Access Control List (ACL) Router1(config)# ip access-list extended Mitel [Sets up a filter that matches Mitel VoIP traffic only] Router1(config-ext-nacl)# permit udp 192.168.100.0 0.0.0.255 192.168.200.0 0.0.0.255 ACLs have an implicit deny at the end so no other traffic meets the criteria listed.
  • Page 328 Create the Policy Maps Router1(config)# policy-map MitelPolicyIn [Only required if default DSCP is being changed] Router1(config-pmap)# class MitelClassMapIn [Matches the class map looking for Mitel traffic] Router1(config-pmap-c)# set ip dscp ef [Overwrite DSCP bits with a value of 46] Router1(config)# policy-map MitelPolicyOut...

  • Page 329: Router 2 Configuration

    Installation Examples Ethernet is congested for other traffic reasons then a "priority" statement will be required on the Fast Ethernet sub-interface Policy Map as well. Now place the policy maps on the interfaces Router1(config)# interface fa0/0 Router1(config-if)# service-policy input MitelPolicyIn [applying the inbound policy map] Router1(config)# interface fa0/0.100 Router1(config-subif)# service-policy output...

  • Page 330: Setting Up Qos For Router2 Using Low Latency Queuing

    Create an Extended Access Control List (ACL) ip access-list extended Mitel [Sets up a filter that matches Mitel VoIP traffic only] permit udp 192.168.200.0 0.0.0.255 192.168.100.0 0.0.0.255 ACLs have an implicit deny at the end so no other traffic meets the criteria listed. This can be programmed with more detail if preferred by the customer, e.g.
  • Page 331 Create the Policy Maps Router2(config)# policy-map MitelPolicyIn [Only required if default DSCP is being changed] Router2(config-pmap)# class MitelClassMapIn [Matches the class map looking for Mitel traffic] Router2(config-pmap-c)# set ip dscp ef [Overwrite DSCP bits with a value of 46] Router2(config)# policy-map MitelPolicyOut...

  • Page 332: Miscellaneous

    [still an access port - just using VLAN 10] Setting up Router 2 to be a local DHCP server ip dhcp excluded-address 192.168.200.1 (the router address - add any others that can’t be used) ip dhcp pool Mitel network 192.168.200.0 255.255.255.0 domain-name customername.com dns-server ip addresses default-router 192.168.200.1...
  • Page 333 128 ip 192.168.100.2 [IP Phone TFTP server] option 129 ip 192.168.100.2 [RTC IP address] option 130 ascii "MITEL IP PHONE" [required for the Mitel phones to accept] option 132 hex 0000.0064 [VLAN 100 in hex] option 133 hex 0000.0006 [802.1p priority 6]...

  • Page 334: Using The Cxi/Cxi Ii Or Mxe Internet Gateway

    Engineering Guidelines USING THE CXI/CXI II OR MXE INTERNET GATEWAY By default, the System IP Gateway IP address is the same as the L2 Switch IP address. The CXi/CXi II/MXe Internet Gateway can be used to provide the following functionality: •...

  • Page 335: Appendix C: Lldp And Lldp-Med Configuration Examples

    Appendix C LLDP AND LLDP-MED CONFIGURATION EXAMPLES...

  • Page 337: Lldp, Lldp-Med Overview

    LLDP and LLDP-MED Configuration Examples LLDP, LLDP-MED OVERVIEW LLDP (Link Layer Discovery Protocol – IEEE 802.1AB) provides a standards-based Layer 2 protocol for enabling network switches to advertise themselves and learn about adjacent connected LLDP devices. LLDP-MED (LLDP Media specific – ANSI/TIA-1057) is an extension to LLDP to provide auto-configuration and exchange of media related information, such as Voice VLAN and QoS, and is designed to provide enhanced VoIP deployment and management.
  • Page 338 Engineering Guidelines that some of these commands are used for other functions, which includes the policy enforcement, some of which operate on a VLAN or switch level, not just at the port. These areas are highlighted in the diagram below, and described in more detail in the following sections.

  • Page 339: Quick Start - Getting Lldp-Med Running Quickly

    LLDP and LLDP-MED Configuration Examples • The lowest value voice VLAN ID that is enabled at the port will be used. If a voice VLAN is not identified, LLDP-MED will not be advertised. • If the voice VLAN is assigned as "untagged", then the default priority is sent over LLDP-MED.

  • Page 340: Defining Voice Vlan And Ports

    Engineering Guidelines DEFINING VOICE VLAN AND PORTS First, determine which VLANs are configured and which are configured for voice: HP ProCurve Switch 5304XL (config)# show vlan Status and Counters - VLAN Information Maximum VLANs to support : 8 Primary VLAN : DEFAULT_VLAN Management VLAN : 802.1Q VLAN ID Name...

  • Page 341: Defining Dscp To Priority (Cos) Mapping (Optional)

    LLDP and LLDP-MED Configuration Examples VLAN63 Port-based Note: ProCurve switches will only advertise LLDP-MED for ports that are members of VLANs with the "voice" attribute, as shown above. A range of ports would be assigned to a voice VLAN in the following manner: HP ProCurve Switch 5304XL(vlan-63)# vlan 63 tagged a1,a3,b1-b16 In this example, ports A1, A3 and a range of B1 to B16 are assigned to the voice VLAN 63.

  • Page 342: Applying Dscp To Priority Qos Policy Enforcement At The Access Port (Optional)

    Engineering Guidelines 111111 No-override The DSCP value of interest is 46, or 101110 in binary format. We recommend assigning a priority of 6 for this DSCP value and assigning a policy name to identify that it is for use with voice.

  • Page 343: Applying Per Vlan Priority And Dscp Qos (Optional)

    LLDP and LLDP-MED Configuration Examples APPLYING PER VLAN PRIORITY AND DSCP QOS (OPTIONAL) A VLAN can be assigned a Priority value or a DSCP with associated Priority values, on a per VLAN basis. Note that all packets on this VLAN will have their QoS parameters adjusted as defined by the VLAN settings.

  • Page 344: Lldp-Med For Location Information

    The subcategories used are those highlighted in the ProCurve Networking manual. Note: Mitel Phones do not currently support the LLDP-MED location ID feature. Instead, Mitel Phones use a proprietary implementation to support emergency call service in conjunction with the Mitel Emergency Response Adviser.

  • Page 345: Additional Useful Commands

    : mac-address PortId : 08 00 0f 12 2a 7a SysName : regDN 63022,MITEL 5220 DM System Descr : regDN 63022,MITEL 5220 DM,LIM,h/w rev 0,ASIC rev 0,f/w Bo... PortDescr : LAN port System Capabilities Supported : bridge, telephone System Capabilities Enabled...
  • Page 346 Engineering Guidelines MED Information Detail EndpointClass :Class3 Media Policy Vlan id :100 Media Policy Priority Media Policy Dscp Media Policy Tagged :True Poe Device Type Power Requested Power Source :Unknown Power Priority :High To determine which LLDP-MED options are operational on a particular port, the following command can be used: HP ProCurve Switch 5304XL(config)# sh lldp config b2 LLDP Port Configuration Detail...

  • Page 347: Appendix Dvoip And Vlans

    Appendix D VOIP AND VLANS...

  • Page 349: Voip Installation And Vlan Configurations

    VoIP and VLANs VOIP INSTALLATION AND VLAN CONFIGURATIONS Although this section refers to VLAN configurations, it can also be used to consider whether or not VLANs are needed for a particular installation. There are, currently, six configurations that have been identified. These are not expected to cover all possible configurations, there will always be exceptions, but as a guideline for the more general installations.

  • Page 350: Physical Segregation Of Voice And Data Networks

    Engineering Guidelines There is only a single device at each egress point of the Layer 2 switch, and so there are no contention issues with data. There are also no data devices, so assigning priority to voice is meaningless, since all voice devices will have equal priority. The network switch internal bandwidth is in excess of the port capabilities, and much higher than the voice devices need to handle.

  • Page 351: Expanded Cxi, Dedicated Voice And Data Ports

    VoIP and VLANs With this reduced configuration, there is no requirement for VLAN settings. EXPANDED CXI, DEDICATED VOICE AND DATA PORTS This is similar in configuration to the standalone CXi with dedicated voice and data ports. The biggest difference is the connection between the CXi controller and the expansion Layer 2 switch.
  • Page 352 Engineering Guidelines Alternatively, the VLAN can be added at the server/controller and the network access point configured to accept VLAN information.

  • Page 353: Appendix Evoip Security

    Appendix E VOIP SECURITY...

  • Page 355: Security Support With Mitel Voip

    VoIP Security SECURITY SUPPORT WITH MITEL VOIP A number of devices in the Mitel IP product range now include additional security measures. These include: • Encryption of voice and signalling payload data • Network Access Authentication (802.1X) Encryption is used to “hide” the information that is carried in the payload from unauthorized users and applications.

  • Page 356: Signalling And Media Paths

    Figure 59: Unsecured vs Secured Connection SIGNALLING AND MEDIA PATHS Media and signalling path encryption is supported for all of Mitel's IP phones on the 3300 ICP. Media path encryption is accomplished with Secure RTP using 128-bit Advanced Encryption Standard (AES). Encryption is backwards compatible to support both currently shipping desktops and previously deployed Mitel IP desktops.

  • Page 357: Voice Streaming Security (Srtp)

    Media (voice) streaming between Mitel sets and controllers will use a version of SRTP with a predefined algorithm (Mitel SRTP), so that negotiation of the secure connection is very quick.

  • Page 358: Voice Streaming To External Gateway Pstn Connection

    Engineering Guidelines IP phones and the 3300 ICP are protected from eavesdropping. Using secure MiNET also protects the 3300 ICP from unauthorized control packets. Secure MiNET uses a predefined algorithm to encode the signalling messages. Negotiation of the encryption method is not needed, so this provides a simpler and faster method to establish secure connections with third party applications.

  • Page 359: Voice Streaming To Applications

    IM traffic encrypted and inside the network. The SpectraLink wireless phones and the Mitel WLAN stands may use security on the air access interface (radio link) such as WEP or WPA2. However, this only covers the wireless connection and not necessarily the remaining connection across the remaining network infrastructure.
  • Page 360 Engineering Guidelines Table 83: Security Support by Device (continued) SECURE SECURE SIGNALLING VOICE DEVICE SIGNALLING (SSL) (SECURE MINET) ENCRYPTION 5020 5201 5205 5207 5212 5215 5215 (Dual Mode) 5220 5220 (Dual Mode) 5224 5230 5235 (Dual Mode) 5140 5240 5302 5304 5312 5320...
  • Page 361 VoIP Security Table 83: Security Support by Device (continued) SECURE SECURE SIGNALLING VOICE DEVICE SIGNALLING (SSL) (SECURE MINET) ENCRYPTION MiCollab Client Softphone MiCollab Client Server SpectraLink wireless DECT wireless Yes (TLS) Teleworker Server Int Teleworker Server Ext Speak@Ease (6500) NuPoint (6510) UC360 Note: The MiTAI connection from the MiTAI client or server to the ICP is secure with SSL only.

  • Page 362: Authentication Protocol Support

    DUAL PORT PHONES A number of Mitel's IP phones are dual port, meaning that there are two ethernet ports on the phone. One ethernet port is used to connect to the LAN. The other ethernet port can be used to connect a PC to the network via the phone, this capability is useful in environments where the phone and the PC need to share a single ethernet connection.
  • Page 363 Features. This menu also allows you to delete any stored usernames and passwords. For details on 802.1X, refer to the "802.1X EAP - MD5 Authentication Protocol Support" Knowledge Base article on Mitel OnLine. Note: Some vendors, Hewlet Packard, for example, manufacture switches that support multiple instances of 802.1X for devices that are connected to the same port.

  • Page 364: Devices That Support 802.1X

    Engineering Guidelines DEVICES THAT SUPPORT 802.1X Table 84 shows a list of MiVoice IP Phones and notes those that support SSL, Secure MiNET and IEEE 801.2X Extensible Authentication Protocol (EAP) - Message Digest 5 (MD5) challenge authentication protocol. Table 84: 802.1X support by device DEVICE 802.1X SUPPORT 5001...

  • Page 365: Worm And Virus Protection

    Once a user logs into the 3300 ICP, the system displays a menu of the specific tools to which they have been granted access. Mitel also offers the Management Access Point to provide secure remote administration for VPN or dial-up access.

  • Page 366: Multi-Level Precedence And Preemption (Mlpp)

    In the default state all IP ports are unblocked so access is unrestricted. SIP SECURITY Mitel has a number of phones that support the Session Initiation Protocol (SIP). SIP is a signalling protocol used for establishing and terminating IP phone calls. SIP signalling is not encrypted;...

  • Page 367: Glossary

    AMC – Applications Management Center. Used to activate new hardware and software licenses for Mitel products. ARP – Address Resolution Protocol. Used to identify a MAC address against an IP address.
  • Page 368 Engineering Guidelines COS – Class of Service. This refers to the priority value in the Layer 2 part of an IP packet when IEEE 802.1p is used. CPH – Calls Per Hour. For example, 6 CPH means 6 calls per hour. CSM –...
  • Page 369 DSU – Digital Service Unit. A peripheral which provides digital ports for the ICP. DTMF – Dual Tone Multi-Frequency. In-voice-band tones used by telephones to signal a particular dialed digit. Also known as touch tone. E – Erlang. A measure of usage of a resource, e.g. 0.75e = 75%. 1 e = 36 CCS. E1 –...
  • Page 370 Engineering Guidelines IP – Internet Protocol. An encapsulation protocol that allows data to be passed from one end user to another. Typically this was over the Internet, but the same protocol is now used within businesses. IrDA – Infrared Data Association. The IrDA is an industry-sponsored organization set up in 1993 to create international standards for the hardware and software used in infrared communication links.
  • Page 371 May also be written as Mbits/s or Mb/s. Mbps is not to be confused with MBps (megabytes per second). MFRD – Mitel Feature Resources Dimensions. This is a definition of the number of features that can be used on a particular unit.
  • Page 372 PCM – Pulse Code Modulation. The digital representation of analog signals. PDA – Personal Digital Assistant. A handheld personal organizer that can interface to a PC or a Mitel PDA Phone. Permanent IP – An IP address that has been leased (from DHCP) on a permanent basis.
  • Page 373 Typically, a subnet may represent all the machines at one geographic location, in one building, or on the same local area network (LAN). SWB – Mitel Sales Workbench. T.37 – Internet Protocol for FAX (Store and Forward). A means of taking a TDM FAX, converting it to data, passing it via IP and reconverting it back to TDM.
  • Page 374 Engineering Guidelines TDM – Time Division Multiplex. A means of combining a number of digitally encoded data or voice channels onto a common digital stream, e.g. T1. TFTP – Trivial File Transfer Protocol. A simplified version of FTP used to transfer data with minimal overhead.

  • Page 375: Index

    Index Index default configuration 52 flash card capacity 31 maximum configuration 35 NUMERICS voice mail server 31 1400, performance 117 3300 ICP compression limitations 189 Bandwidth configuration table 32 advertised rate 174 IP ports 275 calculating and measuring 171 multiple network connections 253 IP 171 overview 11 LAN 175...
  • Page 376 Engineering Guidelines codec selection 185 default configuration 52 Commands maximum configuration 37 for changing network port settings 257 maximum feature availability 53 Compression 171 voice mail server 31 3300 ICP controllers 190 CODEC 205 conference 190 DECT 65 device license requirements 193 Dedicated voice mail server 31 E2T compression 190 Default configuration...
  • Page 377 Index IEEE PoE power advertisements 105 limit 228 In Line Ethernet AC power adapters 96 routes 147 Installation examples IP user license 155, 164, 165 Basic QoS 305 Basic rules 305 Catalyst switches 305 Cisco routers 305 bandwidth considerations 175 Define the IP addressing 306 Licensing Define the VLAN 306...
  • Page 378 203 MiVoice Business Console hub network 206 access connections 74 issues 201 maximum number suipported 61 jitter 203 MiVoice Business IP Ports 275 LAN architecture 206 MLPP license 159 limit MSPLogs Viewer 278 working example 227 Multi-device license, suites 157...
  • Page 379 Index 5220 IP phone 112 Powering Open Integration Gateway 278 802.3af 96 Options for IP phone powering 94 local phone 92 Other maximum limits 45 options for IP phone 94 recommended phone 93 remote phone 92 Paging, limits on number of E2T channels available third party 802.3af 98 for 47 Priority...
  • Page 380 Engineering Guidelines System Management Tools 6 Voice mail System performance index advanced license 159, 164 calculating 117 capacities 124 multiple processors 117 encoding formats 125 processor load, factors 117 license 164 single processor 117 network bandwidth 32 System upgrades 51 networked 124 networking license 158, 164 using ICP as dedicated voice mail server 31...

Table of Contents