Engineering Guidelines
274
T.38 UDP, Low Speed Redundancy = 8, High Speed Redundancy = 3
T.38 ALARMS
T.38 LOAD ALARM
For Release MCD 5.0 SP2 a new alarm has been added called ‘T.38 Load Alarm’. The purpose
of this alarm is to indicate if there is an issue with the T.38 software/hardware/configuration
when the system starts up. For example this alarm will be set if a DSP II card is not installed
in the system or if the DSP II card is defective and the system is unable to load software onto
the DSP II card.
DSP RESOURCE EXHAUSTION ALARM
If DSP resources are not available for a T.38 call a generic DSP resource exhaustion alarm will
be raised and the call will be handled as G.711 pass through.
T.38 FREQUENTLY ASKED QUESTIONS
The following answers to frequently asked questions are provided for persons deploying T.38
in their networks.
Q:
Why is the maximum number of T.38 Fax sessions set at 64?
A:
64 is the maximum number of T.38 Fax licenses that are allowed through AMC. In practice
for a single DSP II card, the maximum number of sessions is 56 since one of the DSP devices
is needed for V.21 FAX Tone detection.
Q:
Does this mean the 3300 can only support 64 T.38 Fax machines?
A:
No, 64 is the maximum number of T.38 CODECs supported on the ICP. Since Fax machines
are typically not busy all of the time, it is possible to support more than 64 Fax machines. This
is similar to the way that subscribers and trunks are allowed to be oversubscribed based on
traffic patterns.
Q:
How can an installer see how many active T.38 sessions are in progress?
A:
The command line entry of 'e2tShow' will cause a line to be output such as:
> 7%
> 2000 ms
> 6000 ms
Red = Stop
PACKET LOSS
JITTER
END-TO-END
DELAY
< 7%
< 1000 ms
< 6000 ms
Green = Go
< 10%
< 2000 ms
Yellow = Caution
> 10%
> 2000 ms
> 6000 ms
Red = Stop
PACKET LOSS
JITTER
END-TO-END
DELAY
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: ... ...