Engineering Guidelines
152
•
The new MiTAI driver communicates with MiVoice Business using internal
MiVoice Business component (Data Services) port 5320.
•
The Microsoft PC to Phone application uses ports 5060 and 5061 for communication be-
tween the Live Communication Server and the 3300 ICP.
RESILIENCY
Some service providers may offer service resiliency. There are two different mechanisms for
making use of service provider resiliency; IP addressing or FQDNs (Fully Qualified Domain
Names). The ICP does not support service resiliency using IP addressing, but it can use FQDNs
to make use of service resiliency. For details, refer to the
3300 ICP Resiliency Guidelines
.
Mitel resilient call state and call survivability is not supported in conjunction with SIP trunking.
911 EMERGENCY SERVICES
SIP trunking supports 911 emergency services. The System Administrator can choose whether
or not the SIP service provider should be the outgoing emergency route.
If the SIP service provider will provide support for 911 emergency services, the following
requirements must be met:
•
Ensure that the contract with the service provider covers 911 emergency service support.
If the SIP service provider passes this information to the PSTN when the call leaves the
SIP network then the PSAP will have the proper information for the emergency service.
•
Ensure that any geographical differences between the location of the phones and the
location of the service provider are addressed by the service provider.
•
Ensure that the CESID information is programmed.
The System Administrator should also provision the installation with a backup connection to
the local PSTN to maintain connectivity in the event the SIP trunk fails.
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: ... ...