Engineering Guidelines
270
•
At the start of a call a Fax Tone/V.21 detector is used to determine if the call is a fax call.
After 60 seconds the detector is relinquished.
DSP PROVISIONING
•
At start up, the system provisions the DSP II card with T.38 first, and then G.729.
•
More T.38 or G.729 licenses can be purchased than the system hardware configuration
supports. This allows licenses to be purchased prior to the installation of the DSP II card.
•
A system reboot is required for licensing changes to take effect.
ZONES
•
Zones are used to control where compression and Bandwidth Management are used.
•
Zones can also be used to control where T.38 will be used. For instance, in some cases
there may not be enough T.38 resources available for all Fax calls, in these situations the
Administrator may want some Fax calls to be handled as G.711 Pass Through so that other
specific routes can be guaranteed the use of T.38 resources.
•
As a general rule, T.38 should be used to transport Faxes between different zones.
•
Networks and endpoints that communicate with each other over a WAN should be config-
ured in different zones to allow for the use of T.38.
•
The use of compression and T.38 within a zone can be configured independent from one
another.
•
In ESM there is form called the "Fax Service Profiles". This form allows the administrator
to define how inter-zone (between zones) and intra-zone (within a zone) faxes will be
handled.
•
There is a pre-programmed default profile for both inter-zone and intra-zone traffic.
•
The Administrator has the ability to create custom profiles for intra-zone traffic. Custom
profiles cannot be created for inter-zone traffic.
•
If two 3300s are located in the same zone and have different Intra-zone T.38 settings
configured. The system will attempt to place the call with the T.38 profile that uses the least
amount of bandwidth.
•
The Fax Service Profiles form can be shared via SDS. Sharing restrictions do not apply to
this form.
•
The SI Tool, AMC and the MiConfig Wizard can be used for T.38 license configuration.
INTER-ZONE DEFAULT PROFILE
•
There is only one profile available for inter-zone Fax traffic.
•
This profile determines how Faxes will be handled when transmitted between devices
located in different zones.
Note:
T.38 licenses are only required to allow an ICP to originate or to terminate Faxes
sent over IP or SIP trunks, T.38 licenses are not required on an intermediate or tandem
ICP.
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: ... ...