Mitel 5560 IPT none Specifications Page 1

MITELMIVOICE BUSINESSENGINEERING GUIDELINESMITEL MIVOICE BUSINESS RELEASE 7.0

Engineering GuidelinesxChapter 13: Network Configuration SpecificsNetwork Configuration Specifics. . . . . . . . . . . . . . . . . . . . . . . . . . .

Power87IntroductionThis chapter discusses the following power requirements for the 3300 ICP:• “Installation Practices” on page 87• “Controller Power I

Engineering Guidelines88are auto-sensing. NSU cabinets also have universal (auto-sensing) power inputs. Migrated SX 2000 DSU cabinets each have a swit

Power89To determine which standard(s) a particular phone supports refer to Table 33.Phones can be powered remotely with the following methods:• If the

Engineering Guidelines90Options for IP Phone PoweringTable 33: IP Phone Power OptionsPhonesIn-Line Ethernet AC Power Adapter (48 VDC LAN)AC Power Ad

Power915360 Yes, but the only power supply approved for use is: Mitel Part # 51015131)No No Yes(Power Hub must support Gigabit Ethernet and must be 80

Engineering Guidelines92AC Power adaptersFor information on AC power adapters, refer to the appropriate Mitel phone data sheet. In-Line Ethernet AC po

Power93There are two methods of providing power in the standard:• “Phantom” power across existing Ethernet wires (RJ-45 pins 1, 2, 3 and 6). This is t

Engineering Guidelines94The CXi/CXi II controller’s Layer 2 switch can provide 100 Watts of power to 802.3af-compatible devices according to the follo

Power95OthersAs the IEEE 802.3af standard becomes more widely adopted, additional vendors are offering IEEE 802.3af compliant products.Mitel 3300 powe

Table of ContentsxiNetwork Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines96Cable Power Loss Some power loss will occur over the Ethernet cable used to connect the phone to the L2 switch or the mid-span

Power97• what size UPS would be required to maintain power to the phones in the event of a main power outage• if a L2 switch that uses a proprietary P

Engineering Guidelines985302 3.845304 3.455312 3.87 5324 3.87 5320 5.35320e 5.55330 with back light 5.85330e 6.15340 5.85340e 6.15360 (see Note 4) 9

Power99Remote powerAs mentioned earlier in this document, there are three communication standards that phones can use to advertise their power require

Engineering Guidelines100Table 35: CDP Power AdvertisementsDeviceCDP Power Advertisements(see Note)5001 IP Phone 4.5 W5005 IP Phone 4.5 W5010 IP Pho

Power101IEEE 802.3af Power Over Ethernet standard (PoE)Table 36 can be used to determine which 802.3af power class advertisement a phone will transmit

Engineering Guidelines1025020 IP Phone 05020 IP Phone + 5310 Conference Unit (Conference unit is powered with AC adapter 24 VDC)05020 IP Phone + PKM(s

Power1035320 25320e 25324 IP Phone 25324 IP Phone + 5310 Conference Unit (Conference unit is powered with AC adapter 24 VDC)35324 IP Phone + PKM(s) (P

Engineering Guidelines104Some MiVoice IP Phones do not support the optional classification feature, and the PSE connection defaults to Class 0 (15.4 W

Power1055201 IP Phone Not Supported n/a5205 IP Phone Not Supported n/a5207 IP Phone Not Supported n/a5212 IP Phone 47 4.75215 IP Phone Not Supported n

Engineering GuidelinesxiiIP Address Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines1065240 IP Appliance Not Supported n/a5302 Not supported n/a5304 IP Phone 37 3.75312 IP Phone 47 4.75320 35 3.55320e 55 5.55324

Power1075360 + Conference Unit 128 12.85360 + Cordless OM/Handset + Headset 120 12.05360 + Bluetooth module 120 12.05360 + LIM 99 9.95505 39 3.9Navig

Engineering Guidelines108Power Requirements for 5220 IP Phone Optional AccessoriesThe 5220 IP Phone and the 5220 IP Phone (Dual Mode) support optional

Power109Uninterruptible Power Supply (UPS)Use uninterruptible power supplies when phones, the associated controllers, PC-based consoles, and the LAN i

Engineering Guidelines110

CHAPTER 6PERFORMANCE

Performance113System Performance IndexIn order to calculate the performance limits of a system, different weighting values are assigned to various typ

Engineering Guidelines114attached, the maximum performance may only be obtained by using the ICP as a group controller in conjunction with other units

Performance115Figure 12: Performance Limitations for Mixed Office Traffic (MXe Server)Performance in an ACD EnvironmentThere are many features of an o

Table of ContentsxiiiAppendix C: LLDP and LLDP-MED Configuration ExamplesLLDP, LLDP-MED Overview. . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines116internal calls (the IVR and the agent) and could easily be more than five calls, depending on how busy the call center is and

Performance117type—for example, Voice, VoiceMail, RAD, etc.—also has performance implications, especially with respect to auto attendant and IVR opera

Engineering Guidelines118

CHAPTER 7APPLICATIONS

Applications1213300 ICP ApplicationsThe 3300 ICP supports a number of applications. This includes applications that are embedded in the product, such

Engineering Guidelines122Voice MailThe 3300 ICP includes an integrated, fully featured voice mail system. Up to 30 ports are available for voice mail

Applications123• EHLO – greeting that announces support for extended messaging options.• MAIL FROM – specifies the originating mailbox.• RCPT TO – ide

Engineering Guidelines124Application Processor CardThe Application Processor Card (APC) is an embedded PC card. The APC can only be installed in CX(i)

Applications125The APC hosts the 6000 Managed Application Server (MAS).The MAS can run the following applications: • Unified Communicator Mobile - Ena

Engineering GuidelinesxivDual Port Phones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines126

CHAPTER 8EMERGENCY SERVICES

Emergency Services129Emergency ServicesEmergency services such as 911 are available from most phone devices according to how the class of service and

Engineering Guidelines130The IP phones determine the MAC addresses of the L2 ports to which they are connected by using Spanning Tree Protocol (STP)/R

Emergency Services131Figure 13 contains three panels. For the configuration in the left panel (CDP), the administrator must set the preferred protocol

Engineering Guidelines132CESID auto updates, unsupported cConfigurationsAutomatic updating of CESID when a phone moves to a new location will not work

Emergency Services133Other considerations• The Spanning Tree Protocol allows multiple ethernet connections to be made between a device and the network

Engineering Guidelines134• Using RSTP reduces disconnection time to approximately 3 seconds, which has a much smaller effect on IP phone operation and

CHAPTER 9IP NETWORKING

CHAPTER 1ABOUT THIS DOCUMENT

IP Networking137IP Networking ConsiderationsThis chapter discusses how IP networking and IP trunks affect the 3300 ICP. The terms “IP networking” and

Engineering Guidelines138ClusteringClustering and networking between units introduces additional performance overhead and limitations on the individua

IP Networking139IP-Trunk Connection LimitationsPrior to Release MCD 5.0 there were some IP-Trunk limitations to consider. These include:• The number o

Engineering Guidelines140IP trunking models Examples of fully-meshed and hierarchical network configuration networks are shown Figure 17 and Figure 18

IP Networking141Figure 18: Hierarchical Network Further details on setting up a cluster can be found in the “3300 ICP Multi-Node Management Clustering

Engineering Guidelines142Figure 19: Signalling and Voice Path Example 1In the tandem case, a virtual IP trunk is used from A to B and another virtual

IP Networking143Variable RTP Packet RatesMCD 4.0 introduced capabilities to support the use of variable RTP packet rates between specific phones, appl

Engineering Guidelines144The MiVoice Border Gateway (Release 6.0 onwards) can provide packet rate adaptation between the internal and external address

IP Networking145When used in a cluster environment, the network ID must equal the Cluster Routing digits. When not in a cluster environment, the netwo

Engineering Guidelines146IP Networking and Product Release CompatibilityProduct improvement is part of an important and ongoing process and it include

IP Networking147Applications compatibilityTo ensure applications compatibility with an ICP that is using SIP trunking, the System Administrator needs

Engineering Guidelines148For correct operation, ports that are used to connect to Fax machines must have the following COS option enabled:• Fax Capabl

IP Networking149Figure 21: Enterprise Site with SIP Aware FirewallThe ingate SIP Firewall is interoperable with the 3300 ICP based SIP solution. You c

Engineering Guidelines150• The new MiTAI driver communicates with MiVoice Business using internal MiVoice Business component (Data Services) port 5320

CHAPTER 10LICENSING

Licensing153System LicensesRelease MCD 5.0 introduces two new switch packaging options (System Types) which are defined as follows: • Standalone • Ent

Engineering Guidelines154• IP Device licenseIn MCD 4.0, an IP device license is needed for every IP phone that is, or could be, registered with the Mi

Licensing155• Multi-device Users licenseIn MCD 5.0 it is possible to create Personal Ring Groups (PRGs) whose members are collectively licensed under

About This Document3OverviewThese guidelines will assist you in planning an installation of a 3300 IP Communications Platform. The guidelines describe

Engineering Guidelines156commercial servers, compression resources are provided in software by the Media Server component (software blade). Compressio

Licensing157• Embedded Voice Mail PMS license An embedded voice mail PMS (Property Management System) license is needed to enable access to hospitalit

Engineering Guidelines158Device LicensingThe 3300 ICP requires a number of device licenses in order to operate. The following table lists these licens

Licensing159Fax 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. The T.38 li

Engineering Guidelines1605602 or 5606 Wireless Handset (IP DECT - Global)IP user licenseResilient phone on secondary controllerNone neededHot Desk use

Licensing161Licensing LimitsAvailable resources determine if license limits can be achieved. For example, if there is insufficient DSP for voice mail,

Engineering Guidelines162Licensing ExampleThe following example shows how to determine the number of licenses required. For more accurate traffic calc

Licensing163Taking each of the licenses in turn, the above information results in the following calculations and resulting licenses:• IP device Licens

Engineering Guidelines164needed for trunks. A further two channels are needed for internal calls, making a total of 26 IP trunks (200 X 2/36 X 15% (ne

CHAPTER 11BANDWIDTH, CODECS AND COMPRESSION

Engineering Guidelines4• Updated IP port usage (Table 80 on page 272)• Clarified bandwidth requirements for SRTP encrypted voice streams (page 339). E

Bandwidth, Codecs and Compression167Bandwidth, Bandwidth Management, Codecs and CompressionAn IP packet carrying voice information has a number of add

Engineering Guidelines168What is the media bandwidth?Depending upon how this is measured, this could be simply the payload bandwidth, which is similar

Bandwidth, Codecs and Compression169time do not carry user information, they do consume bandwidth, which is unusable by any other connected device.Tab

Engineering Guidelines170Before determining the bandwidth for particular links, it is important to consider the traffic flow and where devices are loc

Bandwidth, Codecs and Compression171Bandwidth availabilityThe advertised rate for a particular link is the speed at which the data travels; it is not

Engineering Guidelines172The LAN connection guidelines table also shows the maximum capability of a LAN link assuming that the link is used purely for

Bandwidth, Codecs and Compression173Bandwidth ManagementThis section details the new bandwidth management solution.Bandwidth management and call admis

Engineering Guidelines174bandwidth is shared. You may need to specify alternative routes where multiple routes go through a common bottleneck, or wher

Bandwidth, Codecs and Compression175Figure 22: Fully Meshed WAN Connections - Deployment ExampleIn a multi-node installation, it is also possible to l

About This Document5• Current Product Briefs: Notes on current releases• White Papers: Reliability (MTTF and MTBF) and Availability information

Engineering Guidelines176Figure 23: Fully-meshed WAN Connections - Star ConfigurationNon-meshed WAN connectionsIf all VPNs terminate at the HQ access

Bandwidth, Codecs and Compression177This non-meshed configuration is a little different, as it requires that data be forced to travel back through the

Engineering Guidelines178The configuration table will look similar to that in Table 54.Deployment boundariesThere are limitations that apply to the cu

Bandwidth, Codecs and Compression179Redundant WAN links and load sharingThe usable bandwidth to be counted on such links (by number of calls using the

Engineering Guidelines180Inter-zone bandwidth settingsAs well as defining the zones and links between locations, the available bandwidth also needs to

Bandwidth, Codecs and Compression181Other coding laws also exist. One that gives good voice quality and is also efficient at coding is G.729. This als

Engineering Guidelines182• Network Zone Topology - Bandwidth Limits• ARS Routes - Compression On/Off/Auto. Compression 'On' may override zon

Bandwidth, Codecs and Compression183Assuming that the end devices are capable of supporting the available CODECs, then the following table will highli

Engineering Guidelines184Figure 26 illustrates how the preceding table and rules can be applied in a typical scenario. The following assumptions are m

Bandwidth, Codecs and Compression185Figure 26: Codec Zone Interconnect ExampleOperation through MiVoice Border Gateway and SRC At Release MCD 5.0 and

NOTICEThe information contained in this document is believed to be accurate in all respects but is not warrantedby Mitel Networks™ Corporation (MITEL®

Engineering Guidelines6System Management ToolsThe System Administration Tool, the Group Administration Tool and the Desktop Tool are GUI based tools f

Engineering Guidelines186although there is a reduction in required bandwidth, the gain isn’t always as much as might be expected.Other forms of data c

Bandwidth, Codecs and Compression1873300 ICP controllers and compressionA single controller has the following limitations:• If the controller has one

Engineering Guidelines188Trunking gateway working exampleIn terms of considering network bandwidth, it should be based on the 120 channels and where t

Bandwidth, Codecs and Compression189Figure 27: IP Networking Compression Zones ExampleAlthough the network shown in the figure above is not a real net

Engineering Guidelines190IP trunk routes and compressionThe IP trunk route is a virtual path from one 3300 ICP to another 3300 ICP. One of the paramet

CHAPTER 12NETWORK CONFIGURATION CONCEPTS

Network Configuration Concepts193IntroductionThis chapter provides a high-level overview of the network settings and configurations required for a Voi

Engineering Guidelines194Network Configuration GuidelinesTable 62 contains a list of guidelines for network configuration. In brief, these guidelines

Network Configuration Concepts195The controller should be located behind a network Layer 2 switch.“LAN architecture” on page 202Ensure that the PPS ra

CHAPTER 2SYSTEM OVERVIEW

Engineering Guidelines196The controller uses some internal IP addresses in the range 169.254.10.0/15 to 169.254.30.0/15. Communication to the 3300 ICP

Network Configuration Concepts197Voice-Over-IP Installation RequirementsIt is essential to assess and configure the network in order to maintain the v

Engineering Guidelines198• Network address translation (NAT) and firewall: Although there are emerging standards to allow VoIP through firewalls and N

Network Configuration Concepts199General Guidelines for Quality of ServiceThe main issues that affect system installation and user perceptions are• Qu

Engineering Guidelines200Extensive use of hubs rather than switches also introduces jitter. Hub use for larger networks and where connections are shar

Network Configuration Concepts201Some carriers may also offer an SLA that honours and provides queuing for incoming (download to the customer) data as

Engineering Guidelines202Wideband audio is not supported over the analogue PSTN. The G.722.1 CODEC is also not easily supported over the digital PSTN

Network Configuration Concepts203The IP phones are in constant communication with the 3300 ICP. All signalling traffic, as well as traffic to and from

Engineering Guidelines204In smaller networks, the definitions of the boundaries may become a little blurred. However, even in these smaller networks,

Network Configuration Concepts205Maintaining Voice Quality of ServiceAs discussed in the previous section, the following issues affect voice quality o

Engineering Guidelines206Network Measurement CriteriaAssuming that jitter and packet loss are not an issue, the one parameter left that affects the vo

Network Configuration Concepts207Bandwidth management and call admission control can be used to ensure that voice quality is maintained in parts of th

Engineering Guidelines208By modifying the router MTU value to approximately 500, larger packets are divided up and sent in smaller chunks. The result

Network Configuration Concepts209Network Priority MechanismsThere are two areas where priority mechanisms operate in the network to ensure that voice

Engineering Guidelines210IEEE 802.1p (Layer 2 priority) uses a field in the IEEE 802.1Q tag to provide eight levels of priority. IEEE 802.1Q is the op

Network Configuration Concepts211• Use VLAN 1 to 999 with Cisco products. VLANS can be extended from 1000 upwards. Care in selection should be exercis

Engineering Guidelines212packets with that VLAN setting. - The phone will obtain the necessary VLAN configuration in a number of ways, highlighted lat

Network Configuration Concepts213The default_vlan is VLAN1. The VLAN numbers are assigned names to help follow which function is assigned to which VLA

Engineering Guidelines214DSCP46. The alternative is to map DSCP44 to the EF queue, but then this needs to be programmed in all routers. Note that the

Network Configuration Concepts215into the Expedited Forwarding class with DSCP value 46. Note also that a number of access Layer 2 switches can overwr

System Overview9System ArchitectureThe 3300 ICP is built upon Mitel’s Data Integrated Voice Applications™ architecture delivering sophisticated call m

Engineering Guidelines216Network topology with priorityThe following network diagram highlights the use of the dual-port phones and the configuration

Network Configuration Concepts217In a Cisco based environment the recommended settings are:• Voice Packets: DSCP: 46, 802.1p:5• Signalling Packets: DS

Engineering Guidelines218The COS values run from 0 to 7. Typically 7 is the highest value, 0 the lowest. However, newer standards and switches define

Network Configuration Concepts219Each LAN connection includes both a transmit pair of cables as well as a receive pair of cables. In a full duplex Eth

Engineering Guidelines220Maintaining Availability of ConnectionsThe quality of service for signalling measures how long a user needs to wait before a

Network Configuration Concepts221WAN traffic working exampleIn this example, assume the following configuration:• 50 IP phones at the corporate centre

Engineering Guidelines222Solutions that come from this example can then be covered by:• Compression (G.729a) to the remote phones can be used to incre

Network Configuration Concepts223exceeded, an alternative path is tried through ARS, either through a different node connected by IP trunks, or throug

Engineering Guidelines224Figure 37: IP trunk limit exampleTable 66: IP networking limit calculationsCalculation Formula ResultTraffic from IP sets N

Network Configuration Concepts225Firewalls and NATFirewalls restrict unauthorized access to a network. Given the number of IP phones that may be activ

Engineering Guidelines10MiVoice Business ControllerThe MiVoice Business controller provides the voice, signalling, central processing, and communicati

Engineering Guidelines226

CHAPTER 13NETWORK CONFIGURATION SPECIFICS

Network Configuration Specifics229Network Configuration SpecificsThe previous chapter “Network Configuration Concepts” on page 191 covered a number of

Engineering Guidelines230Start-Up Sequence and DHCPThe previous chapter “Network Configuration Concepts” on page 191 dealt with network conditions and

Network Configuration Specifics231Sources that can be used to obtain network policy informationTable 68 indicates which LAN Policy parameters can be o

Engineering Guidelines232VLAN setting information sources and prioritiesThe priority levels assigned to each source of VLAN setting information are sh

Network Configuration Specifics233Notes: 1. A DSCP value of 46 is recommended for newer installations using DSCP-aware routers. Value 46 will place th

Engineering Guidelines234Since these values are non-user programmable they cannot be changed by the system administrator. These values do not provide

Network Configuration Specifics235When it is desired to use separate voice and signalling priorities, Mitel recommends the following: • Voice DSCP 46,

System Overview11Supported CountriesDuring the installation process the MiVoice Business system can be configured for operation in a particular countr

Engineering Guidelines236The sequence above assumes that the phones get information from a DHCP server. The information can also be manually entered i

Network Configuration Specifics237LLDP-MED and using scopesIn many situations, especially where part of the network uses different LAN policy from oth

Engineering Guidelines238IP Phones and VLAN programmability5220 Dual Mode "MITEL 5220 DM"5224 Dual Mode "MITEL 5224 DM"5235 Dual M

Network Configuration Specifics239RFC 3942, reclassifying DHCP options: DeTeWe and Spectralink PhonesSpectraLink phones do not offer a solution for th

Engineering Guidelines2405302 Startup and DHCPDHCP options will be used to inform the 5302 of servers that can be contacted to register and retrieve t

Network Configuration Specifics241DHCP Option ReclassificationMitel’s legacy IP device configuration approach, using DHCP options 128 – 135 is still s

Engineering Guidelines242Unused options MUST be left blank. Conflict may arise where a number of different devices exist within the same subnet or DHC

Network Configuration Specifics243Vendor information data format (options 125 and 43)For vendor information returned in either options 125 or 43, the

Engineering Guidelines244Example: id:ipphone.mitel.com;sw_tftp=10.37.20.11;call_srv=10.37.18.11,10.37.10.11; vlan=1056;l2p=6;dscp=46Support of solutio

Network Configuration Specifics245DHCP Lease TimeTo allow users to move off the local subnet, or to let new users join a subnet, a method is needed to

Engineering Guidelines12

Engineering Guidelines246Block size is not user configurable on either the 3300 or the phone, however TFTP block size could be user configurable on so

Network Configuration Specifics247VMPS, CDP, and Location Change Indication (E911)The MiVoice IP Phones at Release MCD 4.0 and higher include:• Suppor

Engineering Guidelines248• To use dual port phone functionality when using VMPS then CDPv2 with the auxiliary VLAN set must be used.• Location Change

Network Configuration Specifics249In a Cisco based environment the recommended settings are:• Voice Packets: DSCP: 46, 802.1p:5• Signalling Packets: D

Engineering Guidelines250be equally configured. The Ethernet switch ports must not be set to portfast because the 3300 ICP is an active device in this

Network Configuration Specifics251MiVoice IP PhoneThe MiVoice IP Phones are compatible with CDP and are able to utilize this information for VLAN and

Engineering Guidelines2521. Manual Entry at boot time2. LLDP-MED3. CDP4. DHCP.The ability to provide partial information at each stage allows these mo

Network Configuration Specifics253The commands required to change the network port settings are:Switch(config)# interface fastethernet0/1Switch(config

Engineering Guidelines254messaging compatibility with CDP overcomes this limitation. Thus, an IP phone that is compatible with the Auxiliary_VLAN sett

Network Configuration Specifics255• Static secure ports cannot become dynamic ports. Security on the static, secure port must be turned off before it

CHAPTER 3TYPICAL CONFIGURATIONS

Engineering Guidelines256• It can specifically deny access to certain recognized devices, e.g. most unknown devices might go to a guest VLAN, but cert

Network Configuration Specifics257Network ConsiderationsThis section describes a number of specific items to consider for the 3300 ICP network:• “NetB

Engineering Guidelines258Wireless Phone Performance on the 3300 ICPSpectraLink wireless phonesMitel has partnered with SpectraLink to provide wireless

Network Configuration Specifics259The DeTeWe DECT-IP, OPS27 wireless phones can be registered as resilient phones. The OPS27 phones register with the

Engineering Guidelines260However, there are additional issues, unique to wireless LANs, that must be taken into consideration when designing a wireles

Network Configuration Specifics261Other considerationsDepending on the particular installation, the following issues may need to be considered:• E-911

Engineering Guidelines262G.711 Fax pass through performance guidelinesDue to the many variables involved in sending Fax data over G.711 pass-through o

Network Configuration Specifics263• 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

Engineering Guidelines264T.38 is not supported on any of the server platforms, since it is a conversion between TDM and IP transmission, and these pla

Network Configuration Specifics265• Placing a voice call and then switching to Fax will work as long as the Fax call is initiated within 60 seconds of

Engineering Guidelines266Resources required • T.38 is a licensable option. Licenses can be purchased in increments of four.• A maximum of 56 T.38 sess

Network Configuration Specifics267• The SI Tool, AMC and the MiConfig Wizard can be used for T.38 license configuration.Inter-zone default profile• Th

Engineering Guidelines268• For most applications, the default values of 3 for the low speed portion of the Fax call and 1 for the high speed portion s

Network Configuration Specifics269Voice Network Limits Fax over G.711 pass ThroughT.38 UDP, Low Speed Redundancy = 0, High Speed Redundancy = 0T.38 UD

Engineering Guidelines270T.38 UDP, Low Speed Redundancy = 8, High Speed Redundancy = 3T.38 AlarmsT.38 load alarmFor Release MCD 5.0 SP2 a new alarm ha

Network Configuration Specifics271Q: What QoS settings are used for T.38 packets and signalling?A: T.38 packets are transmitted using the same QoS set

Engineering Guidelines272Although the list can be used to open access across a firewall, where a firewall and NAT are used (for example, at the Intern

Network Configuration Specifics273Ports 9000 and 9002 are only used by the console applications. All other phones now use ports in the 50000 to 50511

Engineering Guidelines274connections on the first available port in the range from 49500 to 49549. (Usually 49500 unless other Data Services apps are

Network Configuration Specifics275Figure 39: MiVoice Business Port Diagram 1MiVBMiVBIP PhoneDNSAMC(Licenses)UserApplication/PCTCP / 20,21 (FTP)TCP / 2

Typical Configurations15System ConfigurationsThe MiVoice Business product line includes a number of platforms, IP phones, and applications. Each platf

Engineering Guidelines276Figure 40: MiVoice Business Port Diagram 2 MiVB6140Agent Portal6110Contact CenterManagementTCP / 1752 (SMDR)TCP / 8000, 8001

Network Configuration Specifics277Figure 41: MiVoice Business Port Diagram 3MiVBNuPointTCP / 80, 443 (HTTP, HTTPS – Web Services)TCP / 443 (HTTPS)TCP

Engineering Guidelines278Figure 42: MiVoice Business Port Diagram 4 MiVBVoice First(VCON)TCP / 8000, 8001 (MiTai, Secure MiTai)SoftwareInstallerYA Ser

Network Configuration Specifics279Figure 43: MiVoice Business Port Diagram 5 MiVBUCA ServerTCP / 80, 443 (MiXML, Secure MiXML)UCASoftphone(SIP)TCP / U

Engineering Guidelines280Figure 44: IP Phones Port Diagram IP PhoneDNSTCP / 80, 443 (HTTP, HTTPS)UDP / 67 (DHCP)UDP / 69, 20001 (TFTP)TCP / 6800, 6801

Network Configuration Specifics281Figure 45: 5550 IP Console in LAN ModeIP Console(PC)MS-LCSUDP / 53 (DNS)TCP / 1606 (CSMSG)TCP / 7011 (Data Services)

Engineering Guidelines282Figure 46: 5550 IP Console in Teleworker ModeIP Console(PC)UDP / 53 (DNS)TCP / 6806 (SSL CSMSG)DNSDHCPTeleworkerMiVoiceBorder

Network Configuration Specifics283Figure 47: MiVoice Business Console in LAN ModeIP Console(PC)UDP / 53 (DNS)TCP / 5432 (SQL DB)DNSDHCPMiVBTCP / 18100

Engineering Guidelines284Figure 48: MiVoice Business Console in WAN modeUDP / 53 (DNS)DNSDHCPMiVBUDP / 67 (DHCP)UDP / 68 (DHCP)UDP/50000...50511 (Voic

Network Configuration Specifics285Embedded firewallsThe 3300ICP/MiVoice Business product and phones include micro-firewalls to protect against unexpec

Table of ContentsiiiChapter 1: About This DocumentOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines16Typical Installation ConfigurationsThe MiVoice Business platorm can be designed into different network configurations to suit

Engineering Guidelines286Cables and ConnectionsAlthough often hidden, the cable plant provides the connection between the end user and the data servic

Network Configuration Specifics287wiring schemes are always preferred as they can be connected in star and ring configurations with little change with

Engineering Guidelines288Straight and crossover cablesTwo types of cable connection are used to connect between network equipment devices and also fro

Network Configuration Specifics289Figure 51: Using Wire Color Order to Identify Connection CablesThe cables shown are those expected in new installati

Engineering Guidelines290Interconnection SummaryThe following illustrations provide a summary of the different interconnections between the ICP and as

APPENDIX ACAT 3 WIRING

CAT 3 Wiring293CAT 3 Wiring PracticesCategory 3 (CAT 3) refers to a type of UTP copper cabling that meets specific transmission characteristics (see C

Engineering Guidelines294• It is highly recommended not to connect PCs to the phones, and to connect these on a separate LAN infrastructure. The secon

CAT 3 Wiring295Summary of CAT 3-specific Network ConfigurationsThere are a number of different installation combinations and devices that can run with

Typical Configurations17possesses the group controller and local phones, but the PSTN access is in a separate secure building. A different scenario is

Engineering Guidelines296Figure 54: CXi/CXi II Minimum Cable StandardNote: Selection of the network port settings differs on the CXi/CXi II platform d

CAT 3 Wiring297Figure 55: CX, MX, MXe, AX, and LX Minimum Cable Standard

Engineering Guidelines298

APPENDIX BINSTALLATION EXAMPLES

Installation Examples301Using Cisco Routers and Catalyst SwitchesThe Cisco 2600 series routers tested were running Software (C2691-JS-M), Version 12.3

Engineering Guidelines302It is important that QoS be set up in the network end to end, not just in a few places. Internet VPN connections (for example

Installation Examples303MiVoice IP Phone Each MiVoice IP Phone must know (as a minimum)• its own IP address• its subnet mask• its default gateway• its

Engineering Guidelines304The WAN link shown is a serial interface but could be any technology (Frame Relay, ATM, MPLS).Ethernet Switch 1 configuration

Installation Examples305These steps are to set up QoS on the Catalyst 3550 and create the Voice VLAN.Interface fa0/2 is connected to the 3300 ICP whic

Engineering Guidelines18Hybrid SystemA Hybrid system combines both of the previous scenarios and involves a distributed system for a headquarters and

Engineering Guidelines306Interface fa0/5 is the VLAN trunk connection between Switch 1 and Switch 2. For Ethernet priority information to be sent betw

Installation Examples307Interface fa0/2 is connected to a MiVoice IP Phone that is capable of sending VLAN tagged Ethernet frames. When learning the v

Engineering Guidelines308Interface fa0/2 is connected to a MiVoice IP Phone that is capable of sending VLAN tagged Ethernet frames. When learning the

Installation Examples309Programming the IP addressesThese previous steps are probably already in place for the data network.This is the step for setti

Engineering Guidelines310Create Class MapsCreate the Policy MapsNo "priority" statement has been set in this Policy Map. This is because the

Installation Examples311Now place the policy maps on the interfacesRouter 2 configurationThere are two physical interfaces on the Router 2 and an addi

Engineering Guidelines312Programming the IP addressesThese previous steps are probably already in place for the data network.This is the step for sett

Installation Examples313Create Class MapsCreate the Policy MapsRouter2(config)# class-map match-all MitelClassMapInRouter2(config-cmap)# match access-

Engineering Guidelines314Now place the policy maps on the interfacesMiscellaneousTo add an 802.1p value to the high priority queueThis example moves 8

Installation Examples315Remember to save your configurations!Using the CXi/CXi II or MXe Internet GatewayBy default, the System IP Gateway IP address

Typical Configurations19Sample 3300 ICP ConfigurationsThe sections below describe sample configurations:• “The 3300 ICP as a Trunk Gateway” on page 19

Engineering Guidelines316other networks. The PCs and IP phones use DHCP Option 3 (which equals the L2 Switch IP address) to reach known intranet, and

APPENDIX CLLDP AND LLDP-MED CONFIGURATION EXAMPLES

LLDP and LLDP-MED Configuration Examples319LLDP, LLDP-MED OverviewLLDP (Link Layer Discovery Protocol – IEEE 802.1AB) provides a standards-based Layer

Engineering Guidelines320The information advertised by LLDP-MED is obtained from various switch settings. These settings need to be configured in orde

LLDP and LLDP-MED Configuration Examples321The information to be advertised can come from a number of sources, but follows the general flow outlined b

Engineering Guidelines322To ensure that the correct settings are applied, use the following sequence of commands:• Define Voice VLAN and assigned port

LLDP and LLDP-MED Configuration Examples323Assigning a port, or range, to a particular VLAN:A range of ports would be assigned to a voice VLAN in the

Engineering Guidelines324First, determine the current DSCP mapping.The DSCP value of interest is 46, or 101110 in binary format. We recommend assignin

LLDP and LLDP-MED Configuration Examples325An example of such a connection could be a softphone on a PC. The PC will run multiple applications, but wi

Engineering Guidelines20The 3300 ICP as a Trunk TandemWhen the 3300 ICP acts as a Trunk Tandem, it functions similar to that described for the gateway

Engineering Guidelines326LLDP/LLDP-MED will advertise DSCP, VLAN and Priority from an untagged access port, but the VLAN and Priority values are only

LLDP and LLDP-MED Configuration Examples327To redefine these setting the full information must be entered:To view the location configuration:Additiona

Engineering Guidelines328The remote device can also be interrogated to determine the settings it is using. This is useful as a cross check that LLDP/L

LLDP and LLDP-MED Configuration Examples329The capabilities option and network policy are both needed for auto configuration of the end devices.The di

Engineering Guidelines330

APPENDIX DVOIP AND VLANS

VoIP and VLANs333VoIP Installation and VLAN ConfigurationsAlthough this section refers to VLAN configurations, it can also be used to consider whether

Engineering Guidelines334Standalone CXi, voice onlyThis is a self-contained configuration, with only the CXi unit involved in the network. There are o

VoIP and VLANs335Standalone CXi without expansion switch, dedicated voice and data portsIn this configuration, the CXi controller becomes the network,

Typical Configurations21RAD sources may be embedded (using the voice mail and/or music ports) or off-board (for example, Mitel Contact Center Intellig

Engineering Guidelines336For the controllers, or servers, VLAN and priority is also needed. However, this can be configured in different places. The V

APPENDIX EVOIP SECURITY

VoIP Security339Security Support with Mitel VoIPA number of devices in the Mitel IP product range now include additional security measures. These incl

Engineering Guidelines340When the data is encrypted, it is simply replaced with a scrambled version. This is a 1 for 1 transformation, so there are no

VoIP Security341phones on two controllers will require the establishment of three secure signalling channels, that is, a secure connection at each con

Engineering Guidelines342Mitel's Secure MiNET protocol uses the Advanced Encryption Standard (AES) to encrypt call control packets. Using secure

VoIP Security343Voice streaming to internal voice mail, Record-a-Call and conferenceWhere there are internal features like voice mail, Record-a-Call o

Engineering Guidelines344Phones5001 No Yes Yes5005 No Yes Yes5010 No Yes Yes5020 No Yes Yes5201 No Yes Yes5205 No Yes Yes5207 No Yes Yes5212 Yes Yes

VoIP Security3455550 IP Console No Yes N/A5550-TKB Yes Yes Yes5560 IPT Yes Yes YesMiCollab Client Yes Yes N/AMiCollab Client Softphone Yes Yes YesMiC

Engineering Guidelines22The MiVoice Business systems do NOT support: • Traditional agents and Hot Desk agents active on the same system• Traditional a

Engineering Guidelines346Authentication Protocol SupportA number of networks now support a level of access restriction to the network ports. A device

VoIP Security347• the port could be opened to a guest VLAN• the port could be shut down.When a PC is connected to a port, it will be interrogated in t

Engineering Guidelines348Devices that support 802.1XTable 85 shows a list of MiVoice IP Phones and notes those that support SSL, Secure MiNET and IEEE

VoIP Security349Worm and virus protectionThe 3300 ICP uses an embedded real-time operating system. This system is less susceptible to virus or worm at

Engineering Guidelines350Secure management interfacesThe 3300 ICP includes a fully integrated set of management tools designed to install, manage, and

Glossary351GlossaryACD – Automatic Call Distribution. A package of advanced call processing features, relating to groups of agents who handle calls an

Engineering Guidelines352Controller. Control element of ICP (see also RTC).COS – Class of Service. This refers to the priority value in the Layer 2 pa

Glossary353routers at Layer 3 to direct the data to an appropriate queue. Value 46 is recommended for voice and will use the Expedited Forwarding queu

Engineering Guidelines354ICP – IP Communications Platform. Includes gateway function, call control, plus a number of other features, such as voice mai

Glossary355information such as Voice VLAN and QoS. It is designed to provide enhanced VoIP deployment and management.LS – Loop Start. This is a partic

Typical Configurations23Network ACD Controllers For large installations, splitting the system into multiple nodes allows a higher capacity in terms of

Engineering Guidelines356NAT – Network Address Translation. A means of translating internal IP addresses to a defined limited range of internet IP add

Glossary357RAD – Recorded Announcement Device.RAID – Redundant Array of Independent Disks. Array of hard drives on which the information is duplicated

Engineering Guidelines358Subnet – A subnet (short for “subnetwork”) is an identifiably separate part of an organization's network. Typically, a s

Glossary359VM – Voice Mail.WAN – Wide Area Network. A network connection to a network that could be global, e.g. via Frame Relay.Wi-Fi – Wi-Fi Allianc

Engineering Guidelines360

Index361IndexNUMERICS1400, performance 1133300 ICPcompression limitations 186configuration table 30IP ports 271multiple network connections 249overvie

Engineering Guidelines362codec selection 181Commandsfor changing network port settings 253Compression 1673300 ICP controllers 187CODEC 201conference 1

Index363IEEE PoE power advertisements 101In Line Ethernet AC power adapters 92Installation examplesBasic QoS 301Basic rules 301Catalyst switches 301Ci

Engineering Guidelines364LX 113default configuration 50maximum configuration 41MMailbox license 161Maintaining availability of connections 220Maximum

Index365Options for IP phone powering 90Other maximum limits 43PPaging, limits on number of E2T channels available for 45PC settings 257Performance li

Engineering Guidelines24Basic Call Center • Trunk to agent ratio is 1.5 (lower trunk ratios will allow increased system capacity, at the expense of mo

Engineering Guidelines366calculating 113multiple processors 113processor load, factors 113single processor 113System upgrades 49TT.38 147, 156, 261–26

Typical Configurations25Advanced Call Center • Trunk to agent ratio is 1.5 (lower trunk ratios will allow increased system capacity, at the expense of

Engineering GuidelinesivAX Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines26In the standalone configuration, adding more groups for the agents or allowing overflow on the paths will both add a processin

Typical Configurations27Active agents vs. trafficThe maximum number of agents shown in the above tables is based on each agent handling an average of

Engineering Guidelines28Local agents vs. EHD agentsAs stated previously, when EHDA is used for some or all of the agents, the total number of agents t

Typical Configurations29 Figure 8: Example of Local vs. EHD Agents on ISS Agent ControllerThe 3300 ICP as a Dedicated Voice Mail ServerThe 3300 ICP c

Engineering Guidelines30When determining network bandwidth, consider voice mail sessions as being active 100% of the time. The number of voice mail se

Typical Configurations31MXe Server, Virtual MiVoice Business, MiVoice Business for ISS, and MiVoice Business Multi-instanceNote: Other limits besides

Engineering Guidelines32Voice Mail 0 Voice mail must be an external application on MXe Server and MiVoice Business for ISS.Compression channels256 G.7

Typical Configurations33AX Controller Table 9: Maximum AX configuration Feature / ResourceValue / Quantity NotesRTC processor 450 MHzE2T processor N

Engineering Guidelines34AX Controller ONS port limitationYou can install up to twelve 24 Port ONSP cards in the AX Controller to provide up to 288 ONS

Typical Configurations35CX/CXi Controller Table 10: Maximum CX/CXi configurationFeature/ Resource Value/Quantity NotesRTC processor 266 MHz This pro

Table of ContentsvCordless (DECT) Handset and Headset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Syste

Engineering Guidelines36MMC modules(installed slots)Dual DSP (3)Quad DSP (3)DSP II (2,3)T1/E1 Combo (1,2)Quad BRI (1,2)Quad CIM (1,2)The CX is the onl

Typical Configurations37CX II/CXi II ControllerTable 11: Maximum CX II/CXi II configurationFeature/ Resource Value/Quantity NotesRTC processor 400 M

Engineering Guidelines38MXe ControllerTable 12: Maximum MXe configurationFeature/ResourceValue/QuantityNotesBase MXe ExpandedRTC processor 450 MHz 4

Typical Configurations39Compression channels64 192 G.729a compression is not a standard offering on base systems. Additional DSP resources are needed

Engineering Guidelines40MXe Controller 192 Gateway limitationsThe MXe Controller has been shipped in two different versions since it was introduced (M

Typical Configurations41LX ControllerTable 13: Maximum LX configurationFeature/ ResourceValue/Quantity NotesRTC processor 450 MHz Prior to release 6

Engineering Guidelines42CIM ports 4 These ports may be used to connect ASU cabinets only.ASU supported 4LS trunks (in ASU) 16 (32) Up to four Universa

Typical Configurations43Other Maximum LimitsTable 14: Other Maximum LimitsFeature/ Resource Value/Quantity Notes5230/5235/5320/5330/5340/5360/Navig

Engineering Guidelines44SIP Phones and use of TLS (SIP-TLS)The use of TLS (Transport Layer Security) places additional requirements on the MiVoice Bus

Typical Configurations45For deployments with more than 100 nodes in a cluster where SIP-TLS will be deployed, it is highly recommended that Profession

Engineering GuidelinesviOptions for IP Phone Powering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines46Summary of Device and User LimitsThe numbers in the following table indicate the number of IP, SIP, and analog devices that ca

Typical Configurations47Table 17: Device and User LimitsActive System TypeLimits CX/CXi CX II/CXi II AX MXe Base MXe Exp MXe ServerTotal Devices 150

Engineering Guidelines48HTML Applications on Sets Certain MiVoice IP Phones use the Switch Application Communications (SAC) protocol which is a protoc

Typical Configurations49Upgrading the System There are two reasons to upgrade a system – to increase the line size or to improve performance.With Mite

Engineering Guidelines50Provisioning System ResourcesThe table below shows the capacity of each system in its factory default configuration, with no a

Typical Configurations51CX Hardware ConfigurationsIn addition to the two devices installed on the main board, DSP resources may be added to a CX syste

Engineering Guidelines52.Table 20: Maximum CX Feature Availability Without DSP IISystem Hardware Configuration1Lines Trunks#DSPDSP Usage H/WVECE C H

Typical Configurations53A system with two Quad BRI does not have enough DSP resources without a dual or Quad 21161 DSP MMC. A slot is not available fo

Engineering Guidelines54Programmable KeysEach phone (or hot desk user) has a number of pre-allocated programmable keys associated with them. When thes

Typical Configurations555330e IP 245340 IP 485340e IP 485360 IP 485401 IP N/A5505 SIP 65560 IPT 96, or 192 (See Note below)5603 SIP 25604 SIP 25607 SI

Table of ContentsviiChapter 8: Emergency ServicesEmergency Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines56Provisioning for TrafficAll 3300 ICP controllers contain an internal TDM switching fabric. Calls between TDM sets, or from TDM

Typical Configurations57• Call volume is typically split in thirds, with 33% incoming from trunks, 33% outgoing to trunks, and 33% handling internal c

Engineering Guidelines58

CHAPTER 4PHONES AND VOICE APPLICATIONS

Phones and Voice Applications61MiVoice IP PhonesThe 3300 ICP supports the following MiVoice IP Phones:• the 50xx, the 52xx, and the 53xx range of IP p

Engineering Guidelines625560 IPT LimitsThe 5560 IPT is supported on three platform types, the CX/CXi II, the MXe (both the MXe II and MXe III expanded

Phones and Voice Applications63Phones Supported on the AXAll phone sets are supported on the AX platform; there are no software restrictions on provis

Engineering Guidelines64The Micro Firewall will filter the packets and allow bursts up to the “credit” limit shown above. After a protocol type has ex

Phones and Voice Applications65Accuracy can be achieved using a Stratum 3 clock source (± 4.6 ppm), which is standard on all 3300 controllers.DECT RFP

Engineering GuidelinesviiiChapter 10: LicensingSystem Licenses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines665212 Yes Yes No5215 No No No5220 Dual Mode Yes Yes No5215 Dual Mode Yes Yes No5220 No No No5224 Yes Yes No5230 No No No5235 Ye

Phones and Voice Applications67Gigabit Ethernet Phone StandThe Gigabit Ethernet Phone Stand allows a 5200/5300 series IP phone to be interfaced to a G

Engineering Guidelines68Cordless (DECT) Handset and HeadsetThe Cordless (DECT) Handset and Headset are supported on the 5330, 5340 and 5360 IP phones.

Phones and Voice Applications69See http://www.dect.org to determine which variant is appropriate for the country of operation. For operation in the Un

Engineering Guidelines70Typical operating rangeBased on the building material and the number and type of obstructions within the operating space, you

Phones and Voice Applications71RF Site SurveyFor installations that call for only a small quantity of cordless accessories a simple trial and error te

Engineering Guidelines72MiCollab Client and MiCollab Client SoftphoneAccess ConnectionsMiCollab Client and MiCollab Client Softphone use a number of a

Phones and Voice Applications73Networking Considerations for MiCollab ClientThe MiCollab Client Softphone is an application that runs on the PC on whi

Engineering Guidelines74Networking Considerations for MiVoice Business ConsoleThe MiVoice Business Console is an application that runs on the PC on wh

Phones and Voice Applications75Some of the connection paths and limitations are shown in Figure 9 and tables below. In analyzing the resources used by

Table of ContentsixBasic Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Engineering Guidelines765230/52355330/5330e/5340/5340e/5360Navigator (with or without UC Express)1 per device 1 per device 1 per system (via internal

Phones and Voice Applications77Most external applications emulate 5220 sets and require similar resources when they connect to the 3300 ICP. They will

Engineering Guidelines78Mitel OIG ServerNone 1 per server 1 per monitored device1 per server (Mitel OIG)Limited by Mitel OIG sockets and monitorsAppli

Phones and Voice Applications79Use of Record-a-Call with NuPoint UM requires that the phone type is changed from 5020 to 5240 for both NuPoint UM and

Engineering Guidelines80an additional 500 sockets for these internal services. The System Engineering Tool counts socket usage for internal and extern

Phones and Voice Applications81System Resource Notes1. The MiCollab Client and MiContact Center Office servers can place a monitor for every device on

Engineering Guidelines82The configuration includes a number of hot desk users (200+200) as well as mix of applications for MiCollab Client (100+100) a

Phones and Voice Applications83 Table 32: Worked Example - Standard and Resilient Operation Standard Operation QuantityMiNET SocketsSAC SocketsMiTAI

Engineering Guidelines84UC Express added 50 UC Express50000 050 0User 400Hot Desk (SAC) Hot desk users2000002000 0Standard fixed included with phone2

CHAPTER 5POWER