Engineering Guidelines
278
The MSPLogs Viewer application communicates with MiVoice Business through port 7011. If
the MiVoice Business system is behind a firewall, then port 7011 must be opened and routed
to the system. Older versions of the switch (before MiVoice Business 7.0) will attempt to
establish a new connection back to the MSPLogs Viewer on its configured IP:Port combination
(as stated in the wire protocol at connection time) which can be modified with command line
options to traverse through firewalls and NAT. By default, the LogViewer will be listening for
connections on the first available port in the range from 49500 to 49549. (Usually 49500 unless
other Data Services apps are running on the same PC.)
Ports 9000 and 9002 are used by the legacy 5550 IP Console application only. The
MiVoice Business Console uses ports in the 50000 to 50511 range.
With extended capabilities of the E2T on certain 3300 ICP it is recommended that the full RTP
port range of 50000-50511 now be opened up. A particular controller may not use this full range,
but other devices such as the phones may. This makes the setting for all devices common.
New ports for this release are:
•
Port 6543: This is an existing port that has been included into the table of ports. It is specific
to the NSU units and used to provide upgrade via a direct PC connection.
•
Port 5320: Used by MiVoice Business to communicate with Mitel Open Integration Gateway
(OIG), Live Business Gateway (LBG), and MiTAI.
The following diagrams highlight the connections to and from the 3300 based on the above
port information as well as IP-Phone connections. The following key is used to identify the
connections:
•
Arrow direction shows initial connection direction. Arrow head points to server.
•
A double ended arrow means that connection is, or may be, established in both directions;
i.e. an end device might be both a client and a server.
•
Description above the line is the destination (server) termination point.
•
Description below the line is the source (client) origination point.
•
No description on the connection implies that any acceptable port may be used, typically
within the ephemeral range, which may be defined on a particular device, but typically in
the range 1024 to 65535.
Figure 38: 3300 Port Connections – Key
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: ... ...