Engineering Guidelines
146
packet rate to a carrier compared to a local packet rate, thus allowing internal devices and
applications to run at a common rate that may be different from the carrier.
SERVICE PROVIDER BEHAVIOR
Some Service Providers require that a specific packet rate be used on both receive and transmit
streams, in these situations the 3300 ICP will attempt to comply with the Service Provider's
requirements.
In cases where the 3300 ICP cannot meet the Service Provider's requirements, some Service
Providers will allow the call to proceed with unacceptable packet rates, only to block the media
stream. Other Service Providers might fail the negotiation entirely, and the call will never be
connected.
For correct operation it is necessary that calls to or from a Service Providers contain, in the
original SDP (Session Description Protocol) negotiation, the packet rate (or "ptime" parameter)
that the Service Provider is willing to accept. The 3300 ICP will communicate this requirement
to the eventual endpoint.
ROUTE OPTIMIZATION
Route optimization improves signalling and response times in handling a call. For example, a
call from ICP A transferred from ICP B to ICP C continues directly between ICP A and ICP C,
bypassing the initial ICP B. This prevents ICP B from being kept in an unnecessary tandem
signalling connection. Hand-over between controllers occurs within 10 seconds of the call
transfer. The voice streaming automatically switches paths based on IP address information.
CAUTION: If some applications and/or phones that do not support variable RTP
packet rates are combined into a solution which requires variable RTP packet
rates it will result in undefined behaviors.
Specifically, the users may experience scenarios where there is no audio in one
direction or both directions. These types of audio problems can be difficult to
isolate and resolve.
Before deploying any phones or applications that employ variable RTP packet
rates, the administrator or installer should review all sets and applications that
comprise a particular solution to determine if they are all compatible with
variable RTP packet rates.
Special attention should be paid to Mitel applications that operate on a release
schedule that is independent from the 3300 ICP release schedule, such as
NuPoint Unified Messenger.
It should be noted that NuPoint is not initially compatible with variable RTP at
MCD 4.0.
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: ... ...