Phones and Voice Applications
75
NETWORKING CONSIDERATIONS FOR MIVOICE BUSINESS
CONSOLE
The MiVoice Business Console is an application that runs on the PC on which it is installed.
This means that the Mitel-only DHCP options (e.g. VLAN, DSCP) are not available to the
application.
The MiVoice Business Console incorporates a MiAudio softphone. For details regarding
MiAudio refer to the document called Mitel Universal SDK, Installation and Maintenance Guide
Release 1.2. As of SDK Version 1.2, MiAudio supports QoS settings for voice packets.
The selection of QoS settings is made using the MiVoice Business Console Configuration
Wizard Quality of Service settings window. By default, the MiVoice Business Console will use
the Mitel setting for voice media which is a DSCP value of 46 and TOS value of 6. The
MiVoice Business Console must be run as administrator for non-default QoS settings to take
effect.
DSCP to 802.1p mapping in the Ethernet switch should be used when VLANs are applied at
the network switch to prioritize the voice traffic at the Ethernet Layer. A DSCP value of 46 should
be used so that, in networks that employ DSCP based routing, voice priority will be maintained.
IP SOCKETS AND MONITORS
File descriptors/sockets are a primitive data type that are used for numerous software
operations. These operations can be classified into two different types: processor file access
and IP communications. The limits on some of these uses are shown in the following tables.
IP communication uses file descriptors called sockets. A socket is used to create an IP
connection for communication or control purposes between the RTC and an IP connected
device. Devices that can be IP-connected to the 3300 ICP include IP telephones, certain
peripherals, and computers acting as application servers.
All phones and applications use sockets and services within the ICP. The 3300 ICP uses
different types of sockets for IP communication/control purposes. The MiNET socket and the
MiTAI socket are used for signalling. Voice sockets are also required on the smaller controllers
where the call control (RTC) and gateway functions (E2T) have a common processor.
Every device or application that the 3300 ICP communicates with using IP has different socket
requirements. Some devices or applications will use only MiNET sockets or only MiTAI sockets;
other devices or applications will require both MiNET and MiTAI sockets. Whether sockets are
needed on a permanent or temporary basis is dependent upon the particular device or
application.
Each device or application may have a different connection path with specific requirements into
the ICP. A range of devices will load the ICP system in different ways. We strongly recommended
that you contact
System/Sales Engineering
when dealing with large systems and applications
near the system limits.
Note:
The System Engineering Tool includes calculations for socket consumption.
Summary of Contents for MiVOICE BUSINESS
Page 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Page 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Page 16: ......
Page 22: ...Engineering Guidelines 8 ...
Page 23: ...Chapter 2 SYSTEM OVERVIEW ...
Page 24: ......
Page 28: ...Engineering Guidelines 14 ...
Page 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Page 30: ......
Page 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Page 74: ......
Page 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Page 100: ...Engineering Guidelines 86 ...
Page 101: ...Chapter 5 POWER ...
Page 102: ......
Page 128: ...Engineering Guidelines 114 ...
Page 129: ...Chapter 6 PERFORMANCE ...
Page 130: ......
Page 135: ...Chapter 7 APPLICATIONS ...
Page 136: ......
Page 142: ...Engineering Guidelines 128 ...
Page 143: ...Chapter 8 EMERGENCY SERVICES ...
Page 144: ......
Page 151: ...Chapter 9 IP NETWORKING ...
Page 152: ......
Page 167: ...Chapter 10 LICENSING ...
Page 168: ......
Page 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Page 184: ......
Page 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Page 210: ......
Page 244: ...Engineering Guidelines 230 ...
Page 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Page 246: ......
Page 309: ...Appendix A CAT 3 WIRING ...
Page 310: ......
Page 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Page 316: ...Engineering Guidelines 302 ...
Page 317: ...Appendix B INSTALLATION EXAMPLES ...
Page 318: ......
Page 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Page 336: ......
Page 347: ...Appendix D VOIP AND VLANS ...
Page 348: ......
Page 353: ...Appendix E VOIP SECURITY ...
Page 354: ......
Page 381: ... ...