MITELCOMMUNICATIONS DIRECTORENGINEERING GUIDELINESMITEL COMMUNICATIONS DIRECTOR RELEASE 6.0
Engineering GuidelinesxDHCP Option Reclassification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines86
Power87IntroductionThis chapter discusses the following power requirements for the 3300 ICP:• “Installation Practices” on page 87• “Controller Power I
Engineering Guidelines88Controller Power InputThe controllers have flexible power input operating over a wide range to allow global connectivity. The
Power89Mitel IP Phone PowerPoE (Power over Ethernet) is a method of providing power to the phones over the existing Ethernet wiring that the phones us
Engineering Guidelines90• Certain older Cisco Ethernet switches are capable of providing power over Ethernet cables but are not fully IEEE 802.3af com
Power91Options for IP Phone PoweringTable 33: IP Phone Power OptionsPhonesIn-Line Ethernet AC Power Adapter (48 VDC LAN)AC Power Adapter (24 VDC)Pow
Engineering Guidelines925360 Yes, but the only power supply approved for use is: Mitel Part # 51015131)No No Yes(Power Hub must support Gigabit Ethern
Power93AC Power AdaptersFor information on AC power adapters, refer to the appropriate Mitel phone data sheet. In-Line Ethernet AC Power AdaptersA spe
Engineering Guidelines94802.3af poweringPower over Ethernet technology allows devices such as IP Phones to receive power as well as data over an exist
Power95Table 36, “802.3af Power Class Advertisements,” on page 103 can be used to determine which Class a particular phone advertises.3300 CXi/CXi II
Table of ContentsxiT.38 FoIP Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines96HP (Hewlett-Packard)• HP 2650-PWR/2626-PWR• HP 5300 XL with expandable 10/100 PoE modulesCisco• Cisco 3560 series• Newer versi
Power97Planning a Power Over Ethernet InstallationWhen planning a power over Ethernet (PoE) installation, the following should be taken into considera
Engineering Guidelines98Phone Power ConsumptionThis section provides tables with information on telephone power requirements. Use the table that is re
Power995224 IP Phone 4.75230 IP Appliance 5.25235 6.25140 IP Appliance 6.85240 IP Appliance 6.85310 IP Conference Unit (for 5235/5330/5330 with backli
Engineering Guidelines100Remote PowerAs mentioned earlier in this document, there are three communication standards that phones can use to advertise t
Power101CDP Power AdvertisementsTable 35 can be used to determine which CDP power advertisement a phone will use.When using PoE to provide power to th
Engineering Guidelines102IEEE 802.3af Power Over Ethernet Standard (PoE)Table 36 can be used to determine which 802.3af power class advertisement a ph
Power103Note: The CXi controller uses 802.3af power call advertisements to determine phone power requirements, however the CXi II actually measures th
Engineering Guidelines1045235 + LIM 25140 IP Appliance 05240 IP Appliance 05302 IP Phone 25304 IP Phone 25312 IP Phone 25320 25320e 25324 IP Phone 253
Power105Some Mitel IP Phones do not support the optional classification feature, and the PSE connection defaults to Class 0 (15.4 Watts for the IP Pho
Engineering GuidelinesxiiBasic IP addressing information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines106Table 37: LLDP-MED Power Advertisements DevicePower Value AdvertisedPower Consumption (Watts)5001 IP Phone Not Supported n/
Power1075235 IP Phone + 5412 PKM 79 7.95235 IP Phone + 5448 PKM 79 7.95235 IP Phone + 5412 PKM + 5448 PKM 96 9.65235 IP Phone + 5448 PKM + 5448 PKM 96
Engineering Guidelines1085340 + 5412 PKM 71 7.15340 + 5448 PKM 75 7.55340 + LIM 62 6.25340 + Conference Unit module + saucer 108 10.85340 + Gigabit E
Power109Power Requirements for 5220 IP Phone Optional AccessoriesThe 5220 IP Phone and the 5220 IP Phone (Dual Mode) support optional accessories whic
Engineering Guidelines110An alternate way of identifying whether a phone is dual mode or not is by the “Top Engineering Number” which can be found on
Power111Uninterruptible Power Supply (UPS)Use uninterruptible power supplies when phones, the associated controllers, PC-based consoles, and the LAN i
Engineering Guidelines112
CHAPTER 6PERFORMANCE
Engineering Guidelines114
Performance115System Performance IndexIn order to calculate the performance limits of a system, different weighting values are assigned to various typ
Table of ContentsxiiiNetwork configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines116numbers. Use these graphs in conjunction with the System Engineering Tool to determine the appropriate configuration. Note th
Performance117Figure 12: Performance Limitations for Mixed Office Traffic (MXe Server)Performance in an ACD EnvironmentThere are many features of an o
Engineering Guidelines118internal calls (the IVR and the agent) and could easily be more than five calls, depending on how busy the call center is and
CHAPTER 7APPLICATIONS
Engineering Guidelines120
Applications1213300 ICP ApplicationsThe 3300 ICP supports a number of applications. This includes applications that are embedded in the product, such
Engineering Guidelines122If there is only a single EHDU associated with an internal set then the pair can use External Twinning, which operates in the
Applications123Networked Voice MailNetworked Voice Mail (NVM) for the 3300 ICP provides seamless messaging in a distributed network of 3300 ICPs. It a
Engineering Guidelines124Under performance engineering rules, the each streaming audio source can be considered to have a PI equivalent to ½ an E2T co
Applications125Application Processor CardThe Application Processor Card (APC) is an embedded PC card. The APC can only be installed in CX(i) and CX(i)
Engineering Guidelinesxiv
Engineering Guidelines126For information about programming and using software blades and services, refer to the 6000 MAS documentation at edocs.mitel.
CHAPTER 8EMERGENCY SERVICES
Engineering Guidelines128
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 ConfigurationsAutomatic 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
Engineering Guidelines136
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 Networking139• The number of IP-XNet Trunk Groups (321)Prior to Release MCD5.0, all IP-Trunk connections, or routes, had to be associated with an I
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 Guidelines142Call Handling, Routing, and BandwidthA call consists of two parts: signaling and voice streaming.Using TDM, typically over th
IP Networking143Figure 20: Signaling and voice path example 2Consider the different routing in different parts of the network when bandwidth calculati
Engineering Guidelines144The following Mitel devices and applications will support variable RTP packet rates:The 5302 SIP set will not fully support v
IP Networking145Service Provider BehaviorSome Service Providers require that a specific packet rate be used on both receive and transmit streams, in t
Engineering Guidelines2
Engineering Guidelines146Further details on installation can be found in the Technician's Handbook and in the System Administration Tool Help.Num
IP Networking147SIP TrunkingService providers and carriers offer their customers the option of connecting to the service provider via a SIP (Session I
Engineering Guidelines148Third Party Phone CompatibilityDeTeWe and SpectraLink sets support RFC 4733, NAT keep-alives, and utilize a single port for t
IP Networking149• Busy Override Security (Set to “Yes”)• External Trunk Standard Ringback (Set to “Yes”)• Return Disconnect Tone When Far End Party Cl
Engineering Guidelines150The ingate SIP Firewall is interoperable with the 3300 ICP based SIP solution. You can obtain the Ingate product documentatio
IP Networking151• Ensure that the contract with the service provider covers 911 emergency service support. If the SIP service provider passes this inf
Engineering Guidelines152
CHAPTER 10LICENSING
Engineering Guidelines154
Licensing155System LicensesRelease MCD 5.0 introduces two new switch packaging options (System Types) which are defined as follows: • Standalone • Ent
About This Document3OverviewThese guidelines will assist you in planning an installation of a 3300 IP Communications Platform. The guidelines describe
Engineering Guidelines156• IP Device licenseIn MCD 4.0, an IP device license is needed for every IP phone that is, or could be, registered with the MC
Licensing157• Multi-device Suites licenseIn MCD 5.0 it is possible to create suites whose members are collectively licensed under a single Multi-Devic
Engineering Guidelines158• Fax over IP (T.38)A T.38 license is required to allow an ICP to originate or terminate Faxes over IP or SIP trunks from TDM
Licensing159• Tenanting license In Release MCD 4.1 and earlier, a licensable option is required to enable Tenanting on the MCD. The Tenanting package
Engineering Guidelines160Device LicensingThe 3300 ICP requires a number of device licenses in order to operate. The following table lists these licens
Licensing161Digital trunk (PRI, etc.) One Network Link license per digital trunk spanFax over IP (T.38) licenses A T.38 license is required to allow T
Engineering Guidelines162Wireless phone (IP DECT - EMEA) IP user license5602 or 5606 Wireless Handset (IP DECT - Global)IP user licenseResilient phone
Licensing163X-NET over TDM One license to enable X-Net networking over TDM linksTenanting Tenanting license Note 1: The licenses described are those a
Engineering Guidelines164Licensing LimitsAvailable resources determine if license limits can be achieved. For example, if there is insufficient DSP fo
Licensing165Licensing ExampleThe following example shows how to determine the number of licenses required. For more accurate traffic calculations, con
Engineering Guidelines4About the 3300 ICP Documentation SetGo to edocs.mitel.com for access to the various Mitel® documents. You require a Mitel Onlin
Engineering Guidelines166• IP user license: IP user licenses apply to IP phones. There are 420 users on HQ1 (400 local and 20 remote) and 200 users on
Licensing167Application Management Center (AMC)The online licensing process managed by the Mitel Application Management Center (AMC) allows Solution P
Engineering Guidelines168
CHAPTER 11BANDWIDTH, CODECS AND COMPRESSION
Engineering Guidelines170
Bandwidth, Codecs and Compression171Bandwidth, Bandwidth Management, Codecs and CompressionAn IP packet carrying voice information has a number of add
Engineering Guidelines172• Wire bandwidth: 96.8 kbpsWhat is the media bandwidth?Depending upon how this is measured, this could be simply the payload
Bandwidth, Codecs and Compression173by different vendors. The values highlighted in the following tables include all the bits on the wire as would be
Engineering Guidelines174Bandwidth RequirementsBefore determining the bandwidth for particular links, it is important to consider the traffic flow and
Bandwidth, Codecs and Compression175the TCP protocol will adjust the data rate to match the available bandwidth. In this case, some data may transfer
About This Document5System Management ToolsThe System Administration Tool, the Group Administration Tool and the Desktop Tool are GUI based tools for
Engineering Guidelines176“LAN connections guidelines” reflects the maximum usable bandwidth based on the physical connection. Other factors in the net
Bandwidth, Codecs and Compression177When a WAN link is shared with other data devices there are other considerations, including the introduction of wa
Engineering Guidelines178mechanism is now being expanded across the entire installation through the use of common zone numbering. This will provide fi
Bandwidth, Codecs and Compression179• Bandwidth managers should be logically located with the bandwidth pipe to be monitored, either upstream, or down
Engineering Guidelines180This star configuration can still be described by Table 53, and is illustrated in Figure 23. The number of routes within the
Bandwidth, Codecs and Compression181Figure 24: Non-meshed WANThis non-meshed configuration is a little different, as it requires that data be forced t
Engineering Guidelines182Figure 25: Topology for non-meshed configurationThe fundamental point with this configuration is to force all internode bandw
Bandwidth, Codecs and Compression183• Maximum 6 paths per pipe• Maximum 6 levels on the configuration tree. A “perimeter node” is considered an end po
Engineering Guidelines184Example Hot Standby linkSuppose the business has two WAN links:• 1.544Mbits/s• 256kbits/sNormally, the main 1.544 Mbit/s link
Bandwidth, Codecs and Compression185An alternative method is to determine the physical wire bandwidth and define the number of voice streams, or “chan
NOTICEThe information contained in this document is believed to be accurate in all respects but is not warrantedby Mitel Networks™ Corporation (MITEL®
Engineering Guidelines6
Engineering Guidelines186Voice Quality and Codec SelectionThe voice quality of the CODECs available is usually expressed in terms of a Mean Opinion Sc
Bandwidth, Codecs and Compression187Low bit-rate CODECs send data as bursts of data, or Frames. The packet rate must be an exact multiple of the frame
Engineering Guidelines188Table 59: Codec Zone InterconnectsZone InterconnectIntraZone CompressionInterZone CompressionRoute CompressionTo Zone 1 To
Bandwidth, Codecs and Compression189Figure 26 illustrates how the preceding table and rules can be applied in a typical scenario. The following assum
Engineering Guidelines190Compression—IntroductionGenerally when compression is mentioned, it is usually mentioned with a CODEC, for example, “G.729 Co
Bandwidth, Codecs and Compression191IP Phones and CompressionSome IP phones include compression capability and licenses. If required, these devices ca
Engineering Guidelines192IP Applications and CompressionMost Mitel IP-based applications support compression. NuPoint does not support compression.To
Bandwidth, Codecs and Compression193IP Networking Routes and CompressionCompression can be enabled in IP networking routes between 3300 ICP units if t
Engineering Guidelines194• If the phone in controller A, Zone 3 wants to communicate with the phone in controller B Zone 1, it consumes an IP trunk se
Bandwidth, Codecs and Compression195• Conference calls use one compression license for each IP connection in the conference that would normally requir
CHAPTER 2SYSTEM OVERVIEW
Engineering Guidelines196
CHAPTER 12NETWORK CONFIGURATION CONCEPTS
Engineering Guidelines198
Network Configuration Concepts199IntroductionThis chapter provides a high-level overview of the network settings and configurations required for a Voi
Engineering Guidelines200Network Configuration GuidelinesTable 63 contains a list of guidelines for network configuration. In brief, these guidelines
Network Configuration Concepts201The controller should be located behind a network Layer 2 switch.“LAN architecture” on page 209Ensure that the PPS ra
Engineering Guidelines202The 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 Concepts203Voice-Over-IP Installation RequirementsIt is essential to assess and configure the network in order to maintain the v
Engineering Guidelines204• Network address translation (NAT) and firewall: Although there are emerging standards to allow VoIP through firewalls and N
Network Configuration Concepts205General Guidelines for Quality of ServiceThe main issues that affect system installation and user perceptions are• Qu
Engineering Guidelines8
Engineering Guidelines206is negligible. However, for slower WAN connections, such as a Frame Relay connection, the delay becomes significant.Extensive
Network Configuration Concepts207When specifying an SLA it is important that the guaranteed committed information rate (CIR) is specified and includes
Engineering Guidelines208With Release MCD 5.0, a new wideband audio CODEC has been added to the system capability and is supported on the IP devices.
Network Configuration Concepts209LAN architectureNetworks usually consist of different layers. Two main parts are the core network and the access netw
Engineering Guidelines210Figure 28: LAN architectureIn smaller networks, the definitions of the boundaries may become a little blurred. However, even
Network Configuration Concepts211Operating with SX-2000 and Third-Party PBXsIn situations where the 3300 ICP is going to be inter-working with an SX-2
Engineering Guidelines212Maintaining Voice Quality of ServiceAs discussed in the previous section, the following issues affect voice quality of servic
Network Configuration Concepts213Network Measurement CriteriaAssuming that jitter and packet loss are not an issue, the one parameter left that affect
Engineering Guidelines214Bandwidth management and call admission control can be used to ensure that voice quality is maintained in parts of the networ
Network Configuration Concepts215By modifying the router MTU value to approximately 500, larger packets are divided up and sent in smaller chunks. The
System Overview9System ArchitectureThe 3300 ICP is built upon Mitel’s Data Integrated Voice Applications™ architecture delivering sophisticated call m
Engineering Guidelines216Network priority mechanismsThere are two areas where priority mechanisms operate in the network to ensure that voice traffic
Network Configuration Concepts217IEEE 802.1p (Layer 2 priority) uses a field in the IEEE 802.1Q tag to provide eight levels of priority. IEEE 802.1Q i
Engineering Guidelines218• Use VLAN 1 to 999 with Cisco products. VLANS can be extended from 1000 upwards. Care in selection should be exercised in th
Network Configuration Concepts219packets with that VLAN setting. - The phone will obtain the necessary VLAN configuration in a number of ways, highlig
Engineering Guidelines220The default_vlan is VLAN1. The VLAN numbers are assigned names to help follow which function is assigned to which VLAN. The v
Network Configuration Concepts221DSCP46. The alternative is to map DSCP44 to the EF queue, but then this needs to be programmed in all routers. Note t
Engineering Guidelines222into the Expedited Forwarding class with DSCP value 46. Note also that a number of access Layer 2 switches can overwrite the
Network Configuration Concepts223Network topology with priorityThe following network diagram highlights the use of the dual-port phones and the config
Engineering Guidelines224In a Cisco based environment the recommended settings are:• Voice Packets: DSCP: 46, 802.1p:5• Signaling Packets: DSCP: 26, 8
Network Configuration Concepts225The COS values run from 0 to 7. Typically 7 is the highest value, 0 the lowest. However, newer standards and switches
Engineering Guidelines10MCD ControllerThe MCD controller provides the voice, signaling, central processing, and communications resources for the syste
Engineering Guidelines226Full Duplex Network BasicsEven though speech may be half duplex or full duplex to the user, the internal voice codecs are rec
Network Configuration Concepts227Maintaining availability of connectionsThe quality of service for signaling measures how long a user needs to wait be
Engineering Guidelines228WAN traffic working exampleIn this example, assume the following configuration:• 50 IP phones at the corporate centre.• 10 IP
Network Configuration Concepts229Solutions that come from this example can then be covered by:• Compression (G.729a) to the remote phones can be used
Engineering Guidelines230exceeded, an alternative path is tried through ARS, either through a different node connected by IP trunks, or through the PS
Network Configuration Concepts231Figure 37: IP trunk limit exampleTable 67: IP networking limit calculationsCalculation Formula ResultTraffic from I
Engineering Guidelines232Firewalls and NATFirewalls restrict unauthorized access to a network. Given the number of IP phones that may be active at the
CHAPTER 13NETWORK CONFIGURATION SPECIFICS
Engineering Guidelines234
Network Configuration Specifics235Network Configuration SpecificsThe previous chapter “Network Configuration Concepts” on page 197 covered a number of
System Overview11Supported CountriesDuring the installation process the 3300 ICP can be configured for operation in a particular country or region. Th
Engineering Guidelines236Start-Up Sequence and DHCPThe previous chapter “Network Configuration Concepts” on page 197 dealt with network conditions and
Network Configuration Specifics237Sources that can be used to obtain network policy informationTable 69 indicates which LAN Policy parameters can be o
Engineering Guidelines238VLAN setting information sources and prioritiesThe priority levels assigned to each source of VLAN setting information are sh
Network Configuration Specifics239Notes: 1. A DSCP value of 46 is recommended for newer installations using DSCP-aware routers. Value 46 will place th
Engineering Guidelines240Since these values are non-user programmable they cannot be changed by the system administrator. These values do not provide
Network Configuration Specifics241When it is desired to use separate voice and signaling priorities, Mitel recommends the following: • Voice DSCP 46,
Engineering Guidelines242The sequence above assumes that the phones get information from a DHCP server. The information can also be manually entered i
Network Configuration Specifics243LLDP-MED and Using ScopesIn many situations, especially where part of the network uses different LAN policy from oth
Engineering Guidelines244IP Phones and VLAN Programmability5224 Dual Mode "MITEL 5224 DM"5235 Dual Mode "MITEL 5235 DM"Navigator &
Network Configuration Specifics245RFC 3942, Reclassifying DHCP Options: DeTeWe and Spectralink PhonesSpectraLink phones do not offer a solution for th
Engineering Guidelines12
Engineering Guidelines2465302 startup and DHCPDHCP options will be used to inform the 5302 of servers that can be contacted to register and retrieve t
Network Configuration Specifics247conflict with other devices and manufactures that may be using the same DHCP server for optional information.The fol
Engineering Guidelines248Unused options MUST be left blank. Conflict may arise where a number of different devices exist within the same subnet or DHC
Network Configuration Specifics249The following rules apply to parsing of all tag/value pairs. The internal DHCP Server applies these tag/value parsin
Engineering Guidelines250Example: 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 Specifics2513300 TFTP serverThe 3300 ICP internal TFTP server is used to provide the IP phones with application software. This s
Engineering Guidelines252Depending on the total number of phones that require access to the common TFTP server and the time to have these in service t
Network Configuration Specifics253The individual functions of VLAN, VMPS, and Location change indication are described in the sections below.On the co
Engineering Guidelines254In order to make the QoS settings work, the following points need to be considered:• QoS must be enabled for the entire switc
Network Configuration Specifics255Switch(config-if)# switchport access vlan 2Switch(config-if)# mls qos trust cosSwitch(config-if)# mls qos cos 5Switc
CHAPTER 3TYPICAL CONFIGURATIONS
Engineering Guidelines256Applications and other Voice ServersThere are a number of other applications that reside on dedicated voice servers. An examp
Network Configuration Specifics257If not manually programmed, the Mitel IP Phones will continue to use DHCP to locate VLAN and Priority information if
Engineering Guidelines258In order to obtain VLAN information via CDP, some network port settings need to change. The ideal settings are as follows:• S
Network Configuration Specifics2594. The default priority for COS is 0, which will be assigned to untagged traffic.5. The Expedite Forwarding queue (Q
Engineering Guidelines260be controlled through the VLAN router. An example may be a hotel room with Internet access where unknown guest devices will c
Network Configuration Specifics261network switches can be used as VMPS clients. VMPS Server software is also available for Windows and Linux server pl
Engineering Guidelines262Switch(config-if)# switchport access vlan dynamicSwitch(config-if)# switchport voice vlan 2Switch(config-if)# mls qos trust c
Network Configuration Specifics263Network ConsiderationsThis section describes a number of specific items to consider for the 3300 ICP network:• “NetB
Engineering Guidelines264Wireless Phone Performance on the 3300 ICPSpectraLink Wireless PhonesMitel has partnered with SpectraLink to provide wireless
Network Configuration Specifics265The DeTeWe DECT-IP, OPS27 wireless phones can be registered as resilient phones. The OPS27 phones register with the
Engineering Guidelines14
Engineering Guidelines266However, there are additional issues, unique to wireless LANs, that must be taken into consideration when designing a wireles
Network Configuration Specifics267Other ConsiderationsDepending on the particular installation, the following issues may need to be considered:• E-911
Engineering Guidelines268G.711 FAX Pass Through Performance GuidelinesDue to the many variables involved in sending Fax data over G.711 pass-through o
Network Configuration Specifics269Because there is no guarantee that it will work, connecting Modems over IP trunks is not recommended, however If it
Engineering Guidelines270T.38 FoIP Guidelines T.38 is the protocol recommended by the ITU to allow for transmission of real-time Group 3 Fax transmiss
Network Configuration Specifics271mode to terminate the T.38 call. The call is then transferred to NuPoint via G.711. For additional information, see
Engineering Guidelines272generated on this port while a Fax transmission is in progress, then the Fax transmission will likely fail.• Campon Tone Secu
Network Configuration Specifics273• The use of compression and T.38 within a zone can be configured independent from one another.• In ESM there is for
Engineering Guidelines274• Fax transmissions are comprised of two different portions or phases, a low speed phase (300 baud) that the Fax machines use
Network Configuration Specifics275of bandwidth, then the Administrator may want to limit Fax calls between these two points to 7200 bps.• Inter-zone F
Typical Configurations15System ConfigurationsThe 3300 ICP product line includes a number of platforms, IP phones, and applications. Each platform is d
Engineering Guidelines276Voice Network Limits Fax over G.711 pass ThroughT.38 UDP, Low Speed Redundancy = 0, High Speed Redundancy = 0T.38 UDP, Low Sp
Network Configuration Specifics277T.38 UDP, Low Speed Redundancy = 8, High Speed Redundancy = 3T.38 AlarmsT.38 Load AlarmFor Release MCD 5.0 SP2 a new
Engineering Guidelines278The first numeric field indicates the number of currently active T.38 sessions. The second numeric field, in brackets indicat
Network Configuration Specifics2793300 IP PortsThe table below shows the IP port numbers used with standalone MCD and 3300 ICP units. It is not a defi
Engineering Guidelines2801606 TCP OPS Manager, telephone directory1750 TCP Software logs1751 TCP Maintenance logs1752 TCP SMDR1753 TCP PMS/Hotel logs1
Network Configuration Specifics281Ports 9000 and 9002 are only used by the console applications. All other phones now use ports in the 50000 to 50511
Engineering Guidelines282Figure 39: 3300 Port Diagram — 1
Network Configuration Specifics283Figure 40: 3300 Port Diagram — 2
Engineering Guidelines284Figure 41: 3300 Port Diagram — 3
Network Configuration Specifics285Figure 42: 3300 Port Diagram — 4
Table of ContentsiiiChapter 1: About This DocumentOverview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines16Typical Installation ConfigurationsThe 3300 ICP can be designed into different network configurations to suit the organization
Engineering Guidelines286Figure 43: 3300 Port Diagram — 5
Network Configuration Specifics287Figure 44: IP Phones Port Diagram
Engineering Guidelines288Figure 45: Console in LAN Mode
Network Configuration Specifics289Figure 46: Console in Teleworker Mode
Engineering Guidelines290Embedded Firewalls The 3300ICP/MCD product and phones include micro-firewalls to protect against unexpected levels of activit
Network Configuration Specifics291Cables and connectionsAlthough often hidden, the cable plant provides the connection between the end user and the da
Engineering Guidelines292Ethernet cable distancesCable runs for Ethernet are specified up to 100 m when the correct cable type is used. This includes
Network Configuration Specifics293Straight and crossover cablesTwo types of cable connection are used to connect between network equipment devices and
Engineering Guidelines294Figure 49: Using wire color order to identify connection cablesThe cables shown are those expected in new installations, name
Network Configuration Specifics295Interconnection SummaryThe following illustrations provide a summary of the different interconnections between the I
Typical Configurations17possesses the group controller and local phones, but the PSTN access is in a separate secure building. A different scenario is
Engineering Guidelines296
APPENDIX ACAT 3 WIRING
Engineering Guidelines298
CAT 3 Wiring299CAT 3 Wiring PracticesCategory 3 (CAT 3) refers to a type of UTP copper cabling that meets specific transmission characteristics (see C
Engineering Guidelines300• It is highly recommended not to connect PCs to the phones, and to connect these on a separate LAN infrastructure. The secon
CAT 3 Wiring301Summary of CAT 3-specific network configurationsThere are a number of different installation combinations and devices that can run with
Engineering Guidelines302Figure 52: CXi/CXi II Minimum Cable StandardNote: Selection of the network port settings differs on the CXi/CXi II platform d
CAT 3 Wiring303Figure 53: CX, MX, MXe, AX, and LX Minimum Cable Standard
Engineering Guidelines304
APPENDIX B INSTALLATION EXAMPLES
Engineering Guidelines18Hybrid SystemA Hybrid system combines both of the previous scenarios and involves a distributed system for a headquarters and
Engineering Guidelines306
Installation Examples307Using Cisco Routers and Catalyst SwitchesThe Cisco 2600 series routers tested were running Software (C2691-JS-M), Version 12.3
Engineering Guidelines308It 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 Examples309Mitel IP PhonesEach Mitel IP telephone must know (as a minimum)• its own IP address• its subnet mask• its default gateway• its
Engineering Guidelines310The WAN link shown is a serial interface but could be any technology (Frame Relay, ATM, MPLS).Ethernet Switch 1 Configuration
Installation Examples311These 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 Guidelines312Interface fa0/5 is the VLAN trunk connection between Switch 1 and Switch 2. For Ethernet priority information to be sent betw
Installation Examples313Interface fa0/2 is connected to a Mitel IP phone that is capable of sending VLAN tagged Ethernet frames. When learning the voi
Engineering Guidelines314Interface fa0/2 is connected to a Mitel IP phone that is capable of sending VLAN tagged Ethernet frames. When learning the vo
Installation Examples315Programming the IP addressesThese previous steps are probably already in place for the data network.This is the step for setti
Typical Configurations19Sample 3300 ICP ConfigurationsThe sections below describe sample configurations:• “The 3300 ICP as a Trunk Gateway” on page 19
Engineering Guidelines316Create Class MapsCreate the Policy MapsNo "priority" statement has been set in this Policy Map. This is because the
Installation Examples317Ethernet is congested for other traffic reasons then a "priority" statement will be required on the Fast Ethernet su
Engineering Guidelines318These previous steps are probably already in place for the data network.This is the step for setting the IP interface for the
Installation Examples319Router2(config-pmap-c)# exitRouter2(config-pmap)# class class-default [What to do with other traffic]Router2(config-pmap-c)# f
Engineering Guidelines320Now place the policy maps on the interfacesMiscellaneousTo add an 802.1p value to the high priority queueThis example moves 8
Installation Examples321Remember to save your configurations!option 128 ip 192.168.100.2 [IP Phone TFTP server]option 129 ip 192.168.100.2 [RTC IP add
Engineering Guidelines322Using the CXi/CXi II or MXe Internet GatewayBy default, the System IP Gateway IP address is the same as the L2 Switch IP addr
APPENDIX CLLDP AND LLDP-MED CONFIGURATION EXAMPLES
Engineering Guidelines324LLDP, LLDP-MED OverviewLLDP (Link Layer Discovery Protocol – IEEE 802.1AB) provides a standards-based Layer 2 protocol for en
LLDP and LLDP-MED Configuration Examples325The information advertised by LLDP-MED is obtained from various switch settings. These settings need to be
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 Guidelines326The information to be advertised can come from a number of sources, but follows the general flow outlined below:• Defaults fo
LLDP and LLDP-MED Configuration Examples327To ensure that the correct settings are applied, use the following sequence of commands:• Define Voice VLAN
Engineering Guidelines328Assigning a port, or range, to a particular VLAN:A range of ports would be assigned to a voice VLAN in the following manner:I
LLDP and LLDP-MED Configuration Examples329First, determine the current DSCP mapping.The DSCP value of interest is 46, or 101110 in binary format. We
Engineering Guidelines330An example of such a connection could be a softphone on a PC. The PC will run multiple applications, but will not be able to
LLDP and LLDP-MED Configuration Examples331LLDP/LLDP-MED will advertise DSCP, VLAN and Priority from an untagged access port, but the VLAN and Priorit
Engineering Guidelines332To redefine these setting the full information must be entered:To view the location configuration:Additional Useful CommandsF
LLDP and LLDP-MED Configuration Examples333The remote device can also be interrogated to determine the settings it is using. This is useful as a cross
Engineering Guidelines334The capabilities option and network policy are both needed for auto configuration of the end devices.The different services c
APPENDIX DVOIP AND VLANS
Typical Configurations21RAD sources may be embedded (using the voice mail and/or music ports) or off-board (for example, Mitel Contact Center Intellig
Engineering Guidelines336
VoIP and VLANs337VoIP Installation and VLAN ConfigurationsAlthough this section refers to VLAN configurations, it can also be used to consider whether
Engineering Guidelines338Standalone CXi, voice onlyThis is a self-contained configuration, with only the CXi unit involved in the network. There are o
VoIP and VLANs339Standalone CXi without expansion switch, dedicated voice and data portsIn this configuration, the CXi controller becomes the network,
Engineering Guidelines340Connections for the end devices, such as the phones, require VLAN to be enabled, at the access points.For the controllers, or
APPENDIX EVOIP SECURITY
Engineering Guidelines342
VoIP Security343Security Support with Mitel VoIPA number of devices in the Mitel IP product range now include additional security measures. These incl
Engineering Guidelines344When the data is encrypted, it is simply replaced with a scrambled version. This is a 1 for 1 transformation, so there are no
VoIP Security345The signaling paths with security do not take different network routes compared to those without security. The only difference is that
Engineering Guidelines22The MCD systems do NOT support: • Traditional agents and Hot Desk agents active on the same system• Traditional agents and Hot
Engineering Guidelines346Mitel's Secure MiNet protocol uses the Advanced Encryption Standard (AES) to encrypt call control packets. Using secure
VoIP Security347Voice streaming to internal voice mail, Record-a-Call and conferenceWhere there are internal features like voice mail, Record-a-Call o
Engineering Guidelines348Phones5001 No Yes Yes5005 No Yes Yes5010 No Yes Yes5020 No Yes Yes5201 No Yes Yes5205 No Yes Yes5207 No Yes Yes5212 Yes Yes
VoIP Security3495550 IP Console No Yes N/A5550-TKB Yes Yes Yes5560 IPT Yes Yes YesUCA Client Yes Yes N/AUCA Softphone Yes Yes YesUCA Server Yes Yes N
Engineering Guidelines350Authentication Protocol SupportA number of networks now support a level of access restriction to the network ports. A device
VoIP Security351• 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 Guidelines352Devices that support 802.1XTable 86 shows a list of Mitel IP phones and notes those that support SSL, Secure MiNet and IEEE 8
VoIP Security353Worm and Virus ProtectionThe 3300 ICP uses an embedded real-time operating system. This system is less susceptible to virus or worm at
Engineering Guidelines354originating extension number, time, duration, and number dialed. SMDR record access should be restricted as with any other fu
Glossary355GlossaryACD – Automatic Call Distribution. A package of advanced call processing features, relating to groups of agents who handle calls an
Typical Configurations23Network ACD Controllers For large installations, splitting the system into multiple nodes allows a higher capacity in terms of
Engineering Guidelines356Controller. Control element of ICP (see also RTC).COS – Class of Service. This refers to the priority value in the Layer 2 pa
Glossary357DSU – Digital Service Unit. A peripheral which provides digital ports for the ICP.DTMF – Dual Tone Multi-Frequency. In-voice-band tones use
Engineering Guidelines358optional subnetwork number, and a host number. The network and subnetwork numbers together are used for routing, while the ho
Glossary359MAC – Media Access Controller. This is the hardware interface that data (media) travels through. Typically this will be assigned a world-wi
Engineering Guidelines360ONS – On-Premise Line. This is a two-wire analog telephony interface, within an office environment, and not passed outside.OP
Glossary361RFC – Request For Comments. A document that is created, maintained and distributed by the Internet Engineering Task Force. An RFC is the ve
Engineering Guidelines362T1 – Primary Rate. Provides 23 or 24 channels of trunks per connection.TAPI – Telephony Applications Programming Interface. T
Index363IndexNUMERICS1400, performance 1153300 ICPcompression limitations 191configuration table 30IP ports 279multiple network connections 255overvie
Document Title - Using Variables364Commandsfor changing network port settings 258Compression 1713300 ICP controllers 191CODEC 207conference 191device
Index365Installation examplesBasic IP addressing 307Basic QoS 307Basic rules 307Catalyst switches 307Cisco routers 307Define the IP addressing 308Defi
Engineering Guidelines24Basic Call Center • Trunk to agent ratio is 1.5 (lower trunk ratios will allow increased system capacity, at the expense of mo
Document Title - Using Variables366maximum configuration 40MMailbox license 164Maintaining availability of connections 227Maximum configurationAX cont
Index3671400 LX 115ACD environment 117Hunt Groups 118Ring Groups 118Phone advertises Class 103Phone power consumptionlocal power 98PoE 98remote CDP 10
Document Title - Using Variables368TT.38 148, 158, 267–274TDM switching 55Teleworker 204devices 131Tenantinglicense 159, 164Third party 802.3af poweri
Typical Configurations25• 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
Engineering GuidelinesivMXe controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines26The System Engineering Tool deals with all of these conditions, and must be used when analyzing any ACD configuration, includi
Typical Configurations27Local Agents vs. EHD AgentsAs stated previously, when EHDA is used for some or all of the agents, the total number of agents t
Engineering Guidelines28 Figure 8: Example of Local vs. EHD Agents on ISS Agent ControllerThe 3300 ICP as a Dedicated Voice Mail ServerThe 3300 ICP c
Typical Configurations29When determining network bandwidth, consider voice mail sessions as being active 100% of the time. The number of voice mail se
Engineering Guidelines30Configuration TablesThe following tables show the maximum capacity for each feature or resource in each type of controller. Yo
Typical Configurations31Total Devices 3000/5000 The lower number is for display sets (e.g. 5330, 5340, 5360) and the higher number is for standard se
Engineering Guidelines32AX Controller Table 9: Maximum AX configuration Feature / ResourceValue / Quantity NotesRTC processor 450 MHzE2T processor N
Typical Configurations33AX Controller ONS Port LimitationYou can install up to twelve 24 Port ONSP cards in the AX Controller to provide up to 288 ONS
Engineering Guidelines34CX/CXi controller Table 10: Maximum CX/CXi configurationFeature/ Resource Value/Quantity NotesRTC processor 266 MHz This pro
Typical Configurations35MMC 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
Table of ContentsvCoverage and Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engineering Guidelines36CX II/CXi II controllerTable 11: Maximum CX II/CXi II configurationFeature/ Resource Value/Quantity NotesRTC processor 400 M
Typical Configurations37MXe controllerTable 12: Maximum MXe configurationFeature/ResourceValue/QuantityNotesBase MXe ExpandedRTC processor 450 MHz 4
Engineering Guidelines38T. 38 16Record-a-Call 12 Every Record-a-Call session uses a conference resource and a voice mail session from the available po
Typical Configurations39MXe Controller 192 Gateway LimitationsThe MXe Controller has been shipped in two different versions since it was introduced (M
Engineering Guidelines40LX controllerTable 13: Maximum LX configurationFeature/ ResourceValue/Quantity NotesRTC processor 450 MHz Prior to release 6
Typical Configurations41Record-a-Call 12 Every Record-a-Call session uses a conference resource and a voice mail session from the available pool. The
Engineering Guidelines42Other maximum limitsTable 14: Other Maximum LimitsFeature/ Resource Value/Quantity Notes5230/5235/5320/5330/5340/5360/Navig
Typical Configurations43SIP Phones and use of TLS (SIP-TLS)The use of TLS (Transport Layer Security) places additional requirements on the MCD systems
Engineering Guidelines44Paging and Background Music LimitationsUsing the speaker on IP phones for either group paging or playing of background music c
Typical Configurations45• The actual limits on licensed analog extensions and analog trunks are determined by the number of cards that can be installe
Engineering GuidelinesviPower Requirements for 5220 IP Phone Optional Accessories . . . . . . . . . . . . . . . . . . . . . . . .109System Power Requi
Engineering Guidelines46HTML Applications on Sets Certain Mitel IP phones use the Switch Application Communications (SAC) protocol which is a protocol
Typical Configurations47Upgrading the System There are two reasons to upgrade a system – to increase the line size or to improve performance.With Mite
Engineering Guidelines48Provisioning System Resources The table below shows the capacity of each system in its factory default configuration, with no
Typical Configurations49CX Hardware ConfigurationsIn addition to the two devices installed on the main board, DSP resources may be added to a CX syste
Engineering Guidelines50Refer to Table 20 and Table 21 below to determine the maximum feature availability for various hardware configurations of the
Typical Configurations51A 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 Guidelines52Programmable KeysEach of the phones, or a hot-desk user, have a number of pre-allocated programmable keys associated with them
Typical Configurations535330e 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 S
Engineering Guidelines54OpenPhone 26/27 14SpectraLink NetLink 14Telematrix 3000IP 12Note: The default number of programmable keys on the 5560IPT is 96
Typical Configurations55Provisioning for TrafficAll 3300 ICP controllers contain an internal TDM switching fabric. Calls between TDM sets, or from TDM
Table of ContentsviiVariable RTP Packet Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14
Engineering Guidelines56• Operators or attendants can typically handle up to 100 calls per hour (as long as transfer is handled quickly and number loo
CHAPTER 4PHONES AND VOICE APPLICATIONS
Engineering Guidelines58
Phones and Voice Applications59Mitel IP PhonesThe 3300 ICP supports the following Mitel IP phones:• the 50xx, the 52xx, and the 53xx range of IP phone
Engineering Guidelines60on the various systems. The servers can support a maximum of 125 devices, the MXe 32, and the CX/CXi-II only eight. The 5560 I
Phones and Voice Applications61Phones Supported on the AXAll phone sets are supported on the AX platform; there are no software restrictions on provis
Engineering Guidelines62WideBand AudioAs of MCD Release 5.0 the following sets support WideBand audio and they are based on the G.722.1 CODEC.• 5320e•
Phones and Voice Applications63NuPoint Unified MessagingAs of MCD Release 5.0, the 3300 ICP is able to provide Automatic Gain Control (AGC) on calls d
Engineering Guidelines64DECT (Digital Enhanced Cordless Telephony)When multiple DECT base station units (Radio Fixed Part (RFP)) are connected to the
Phones and Voice Applications65Phone StandsThe Gigabit Ethernet phone stand and the Wireless LAN (WLAN) phone stand can be installed in place of the r
Engineering GuidelinesviiiOperation through MBG and SRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Engineering Guidelines66Gigabit Ethernet Phone StandThe Gigabit Ethernet Phone Stand allows a 5200/5300 series IP phone to be interfaced to a Gigabit
Phones and Voice Applications67• 5330, 5340, and 5324 IP Phones with a Conference Unit Module and the Mitel Conference Unit it connects to must use a
Engineering Guidelines68Cordless (DECT) Handset and HeadsetThe Cordless (DECT) Handset and Headset are supported on the 5330, 5340 and 5360 IP phones.
Phones and Voice Applications69in the Standard DECT band of 1880 - 1900 MHz, the second is a DECT 6.0 variant that works in the frequency band of 1920
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 Guidelines72Unified Communicator Advanced and Unified Communicator Advanced SoftphoneAccess ConnectionsUnified Communicator Advanced (UCA)
Phones and Voice Applications73Unified Communicator Advanced (UCA) incorporates a MiAudio softphone. For details regarding MiAudio refer to the docume
Engineering Guidelines74IP Sockets and MonitorsFile descriptors/sockets are a primitive data type that are used for numerous software operations. Thes
Phones and Voice Applications75When many applications, or end devices, are directly attached to the 3300ICP/MCD MiTAI interface it is possible to run
Table of ContentsixNetwork priority mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Engineering Guidelines76Most external applications emulate 5220 sets and require similar resources when they connect to the 3300 ICP. They will also u
Phones and Voice Applications77 Table 30: ICP Connections to External Application ServersApplicationResourceMiNet SocketsMiTAI SocketsMiTAI Monitors
Engineering Guidelines78NuPoint Unified Messenger (UM)1 per port 1 per application server1 per port (5020 phone), OR2 per port (5240 phone)2 per appli
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 Guidelines80System Resource Notes1. The UCA and CSM servers can place a monitor for every device on the system, including TDM devices and
Phones and Voice Applications81The configuration includes a number of hot desk users (200+200) as well as mix of applications for UCA (100+100) and al
Engineering Guidelines82UCA (Monitor 5330s)UCA Server 100 0 0 0 0 100 0Standard fixed2005312 (Standard) without UC Express 200 200 200 0 400 0 400UC E
Phones and Voice Applications83Total 800 800 800 3 900 900 1602Note: As can be seen from the calculations, some additional IP Sockets are needed to co
Engineering Guidelines84
CHAPTER 5POWER
Kommentare zu diesen Handbüchern