Network Configuration Concepts
229
FIREWALLS AND NAT
Firewalls restrict unauthorized access to a network. Given the number of IP phones that may
be active at the same time, it is necessary to open up a number of ports on a firewall in order
to facilitate access. In such scenarios, the firewall is much less effective against network
intrusion.
Network Address Translation (NAT) reduces the number of addresses seen by the Internet
from a particular business. However, such devices need to understand the underlying protocol
to work effectively. If a MiVoice IP Phone is used on the Internet through NAT, there is a high
possibility that the voice streaming will not work. Users who use MiVoice IP Phones over the
Internet should use the Teleworker Solution.
Note:
• Seven channels are needed for internal traffic and ten are needed for external traffic, but
together the total is only 13. The reason is that a number of channels have shared use: in this
case, it is 4 (10+7-13). The higher G.711 rate is used to ensure adequate bandwidth at all
times.
• This data rate is close to a T1 rate. Options are to increase the available link rate by upgrading
to an E1 link or to multiple T1 links, or to accept a lower quantity of IP trunk calls (a slight
reduction in inter-node traffic).
• The bandwidth calculations should also include signalling and link utilization factors.
• With IP networking, it is possible to restrict the number of conversations on a connection, so
although calculations suggest 13 channels, the link settings could be set to only 10 channels
to reduce bandwidth usage. ARS will then come into play when this number is exceeded,
resulting in the call being routed elsewhere, e.g. TDM, if possible, or presentation of
re-order/busy tone to the user.
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: ... ...