Engineering Guidelines
266
•
The IP trunk link must use G.711 only.
•
The rate of packet loss on the link must be less than 0.1%.
•
The link delay must be below 200 ms.
•
Jitter must be less than 30 ms (ideally less than 20 ms).
With these settings, G3 FAX at V.17 speeds has been found to work with good reliability as
compared to standard TDM connections, however without error correction mechanisms such
connections should only be considered as best effort. Use of T.38 for transporting Faxes over
IP networks is strongly recommended.
T.38 – RELIABLE FAX OVER IP TRANSPORT
Under normal circumstances, transmitting Fax over IP should not be considered without
appropriate interfaces to provide signal redundancy and error correction. The two most
prominent protocols are T.37 and T.38, which allow a standard T.30 fax to be connected over
an IP network, T.37 is a store and forward protocol and T.38 is a real time protocol. These are
generally point-to-point connections and provide a means of toll bypass. Fax within a pure IP
environment makes little financial sense, considering that e-mail is far less sensitive to timing
issues, and generally uses an error-correcting IP protocol to ensure delivery.
Since G.711 Fax cut through can only be used successfully on very high quality networks it is
recommended that T.38 be used to support the transmission of FoIP. If the IP network introduces
too much latency, jitter or almost any packet loss Fax transmissions using G.711 pass through
will be error prone.
The T.38 protocol provides mechanisms to deal with network latency, jitter and packet loss.
Information pertaining to the use of T.38 for fax transmission can be found in “T.38 FoIP
Guidelines” on page 267.
G.711 MODEM PASS THROUGH
Sending tones between IP end devices can be problematic as the voice stream data rates will
not be synchronized. This may result in gaps in the voice channel. Normally, these gaps are
infrequent and have little effect on speech. However, they do affect tones and therefore they
affect DTMF and MODEM tones. DTMF and MODEM devices can handle some data loss but
IP networks can introduce more than expected, resulting in poor performance of these services.
Because there is no guarantee that it will work, connecting Modems over IP trunks is not
recommended, however If it is necessary to transport Modem data across an IP trunk then the
following guidelines should be adhered to:
•
The IP trunk link must use G.711 only.
•
The rate of packet loss on the link must be less than 0.1%.
•
The link delay must be below 200 ms.
•
Jitter must be less than 30 ms (ideally less than 20 ms).
Do not expect MODEM speeds to exceed 22.8 kbps.
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: ... ...