Engineering Guidelines
268
DSP II
The DSP II card contains eight DSP devices and is required to support T.38.
An individual DSP device on the DSP II can be loaded with eight T.38 sessions; however,
licensing limits dictate how many overall T.38 sessions can be supported. Also, one DSP device
needs to be loaded with Tone/V.21 detectors to support Fax machine detection.
T.38 is a licensable option. Licenses can be purchased in increments of four up to a maximum
of 64. The recommended maximum number of T.38 licenses supported on various platforms are:
•
3300 CX/CXi – 8 T.38 sessions
•
3300 CX/CXi II, AX, MXe base – 16 T.38 sessions
•
3300 MXe expanded – 48 T.38 sessions
SIGNALLING
•
The open standard signalling protocol used for establishing T.38 calls is SIP Version 2.0,
which is based on RFC-3261.
•
A T.38 call from a 3300 ICP to a 3300 ICP over an IP trunk will use Mitel's proprietary IP
Trunk signalling protocol.
•
The T.38 engine uses UDP to transport packets. TCP/IP is not supported.
•
T.38 data is not encrypted.
•
T.38 is not supported over the MiNET protocol.
•
NuPoint Messenger does not support T.38 Fax. T.38 operation with NuPoint will only be
possible with the same workaround that NuPoint Unified Messenger uses for G.729 com-
pression. Operation with NuPoint is achieved by placing a T1 card on the 3300 into loopback
mode to terminate the T.38 call. The call is then transferred to NuPoint via G.711. For
additional information, see “T.38 Frequently Asked Questions” on page 274.
OPERATION
•
T.38 will support T.30 operating modes 2 and 4, which means the calling Fax can operate
in automatic or manual mode and the called Fax operates in automatic mode.
•
Placing a voice call and then switching to Fax will work as long as the Fax call is initiated
within 60 seconds of the set going off-hook.
•
Switching to voice after a Fax transmission has completed is not recommended.
•
The T.38 solution supports V.17 Fax calls at 14,400 bps or lower.
•
Mitel's T.38 solution does not support V.34 (Super G3) Fax calls, however if a V.34 capable
machine is set to operate in V.17 mode then the call can be handled as a T.38 call.
Note:
For details on how to use a 3300 ICP as a Fax gateway for NuPoint, please refer
to the
NuPoint Unified Messaging Engineering Guidelines
.
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: ... ...