Engineering Guidelines
58
PROVISIONING FOR TRAFFIC
All 3300 ICP controllers contain an internal TDM switching fabric. Calls between TDM sets, or
from TDM sets to trunks, will stay within this TDM switch. Calls between IP phones stream their
voice packets directly over the data network without going into the TDM domain in the 3300
ICP controller, but calls between IP sets and TDM devices (including both lines and trunks)
must go from the IP domain to the TDM switch fabric through the TDM gateway (E2T processor).
All of these calls require bandwidth or channels within the various domains and may require
specific resources (DSP tone generators and detectors, echo cancellation, etc.) within the
controller. The provisioning of these resources is done using the standard type of traffic analysis.
The TDM switching fabric in all of the 3300 ICP controllers is non-blocking, but the limitations
in the number of channels available in the number of channels available in the TDM gateway,
the fiber interfaces, and other resources mean that the system itself is not.
Under most ordinary conditions, the “rules of thumb” provisioning suggested in previous
sections gives a good estimate of the resources required for the number of lines (users) and
trunks in a system. For systems that are approaching the limits of the system, more detailed
calculations may be required through Customer Engineering Services.
Traffic analysis considerations:
•
36 CCS = 1 erlang (1 e) = 3600 call seconds during the busy hour.
•
Call rates (CPH) and duration may vary from business to business. It may be necessary to
monitor a business to get more accurate values.
•
Typical phone calls are 100 seconds in duration.
•
Typically, a normal office phone is busy 16% of the time, or 0.16 e, or 6 CCS (this is 6 CPH
@ 100 seconds, i.e. 600 call seconds or 6 centum call seconds or 10 minutes).
•
Typically, a hotel phone is busy 6% of the time, or 0.06 e, or 2 CCS.
•
Typically, a busy office phone, such as one handling dispatch orders, can be busy 33% of
the time, or 0.33 e, or 12 CCS.
•
Call volume is typically split in thirds, with 33% incoming from trunks, 33% outgoing to
trunks, and 33% handling internal calls (50% is making calls and 50% receiving calls).
•
For normal users, typically one voice mail session is needed for 20 users. Modify this number
accordingly if you expect heavier or lighter voice mail traffic per user.
•
Typically, ACD workers are busy 75% to 100% of the time. One ACD agent normally requires
one resource, such as one 1 E2T channel, one echo channel, one DSP channel (compres-
sion), and one trunk. ACD traffic ranges from 27 to 36 CCS (27 to 36 calls per hour).
•
Typically, in a given ACD group, all calls are either incoming or outgoing trunks, rarely mixed.
•
Traffic blocking is calculated using the ErlangB formula. Erlang adds a statistical blocking
factor and is always higher than the straight calculation. Add a further 10% to 20% to PI
estimates as a rough estimate, and round up.
•
Operators or attendants can typically handle up to 100 calls per hour (as long as transfer
is handled quickly and number lookup is sufficiently quick). Most incoming trunk calls arrive
at the operator station.
•
Traffic blocking probability for internal/intercom traffic is P.001 (1 in 1000 calls blocked).
•
Traffic blocking probability for trunk traffic is P.01 (1 in 100 calls blocked).
Содержание MiVOICE BUSINESS
Страница 1: ...Mitel MiVoice Business RELEASE 7 2 ENGINEERING GUIDELINES ...
Страница 15: ...Chapter 1 ABOUT THIS DOCUMENT ...
Страница 16: ......
Страница 22: ...Engineering Guidelines 8 ...
Страница 23: ...Chapter 2 SYSTEM OVERVIEW ...
Страница 24: ......
Страница 28: ...Engineering Guidelines 14 ...
Страница 29: ...Chapter 3 TYPICAL CONFIGURATIONS ...
Страница 30: ......
Страница 73: ...Chapter 4 PHONES AND VOICE APPLICATIONS ...
Страница 74: ......
Страница 95: ...Phones and Voice Applications 81 Figure 9 ICP Connection Paths and Limitations ...
Страница 100: ...Engineering Guidelines 86 ...
Страница 101: ...Chapter 5 POWER ...
Страница 102: ......
Страница 128: ...Engineering Guidelines 114 ...
Страница 129: ...Chapter 6 PERFORMANCE ...
Страница 130: ......
Страница 135: ...Chapter 7 APPLICATIONS ...
Страница 136: ......
Страница 142: ...Engineering Guidelines 128 ...
Страница 143: ...Chapter 8 EMERGENCY SERVICES ...
Страница 144: ......
Страница 151: ...Chapter 9 IP NETWORKING ...
Страница 152: ......
Страница 167: ...Chapter 10 LICENSING ...
Страница 168: ......
Страница 183: ...Chapter 11 BANDWIDTH CODECS AND COMPRESSION ...
Страница 184: ......
Страница 209: ...Chapter 12 NETWORK CONFIGURATION CONCEPTS ...
Страница 210: ......
Страница 244: ...Engineering Guidelines 230 ...
Страница 245: ...Chapter 13 NETWORK CONFIGURATION SPECIFICS ...
Страница 246: ......
Страница 309: ...Appendix A CAT 3 WIRING ...
Страница 310: ......
Страница 315: ...CAT 3 Wiring 301 Figure 55 CX MX MXe AX and LX Minimum Cable Standard ...
Страница 316: ...Engineering Guidelines 302 ...
Страница 317: ...Appendix B INSTALLATION EXAMPLES ...
Страница 318: ......
Страница 335: ...Appendix C LLDP AND LLDP MED CONFIGURATION EXAMPLES ...
Страница 336: ......
Страница 347: ...Appendix D VOIP AND VLANS ...
Страница 348: ......
Страница 353: ...Appendix E VOIP SECURITY ...
Страница 354: ......
Страница 381: ... ...