Engineering Guidelines
226
•
The blocking ratio can be changed to P.01, and such a link would handle 68.8 CCS.
•
The number of remote phones or the overall number of phones can be reduced.
•
Ensure that QoS/Priority mechanisms are in place and active.
These are all potential solutions and each has to be investigated to understand the nature of
the installation. Doing this calculation before equipment is bought and installed ensures that
such issues are highlighted.
Assume that the routers have the capability of prioritizing traffic and the customer does not
want to use compression for trunk or internal calls. Thus, all calls will use the G.711 coding
scheme. The standard trunk blocking, P.01, is acceptable. The WAN link is over Frame Relay
and is a routed VPN (Layer 3).
•
ErlangB compensation will be used to estimate the maximum expected number of “chan-
nels” required to handle the expected peak rate. (An under-provisioned link could result in
voice quality degradation.)
•
56.5 CCS results in 6 channels for voice at P.01 (using standard Erlang Tables).
•
6 channels at 83 kbps requires 499 kbps.
•
Signalling adds an overhead of 10% taking the total to 550 kbps.
•
The
CIR for Frame Relay
would be 550 kbps or
576 kbps
, if rounded to the nearest 64
kbps. Rounding down to 512 kbps leaves minimum bandwidth during the busy period and
may result in slower signalling and degraded voice, as packets will be marked for discard
at the router if the CIR is exceeded.
•
Ideally, the link should not be more than 70% utilized so the
bit rate
should be 784 kbps,
or
832 kbps
when rounded to the nearest 64 kbps. Since fractional T1/E1 is often based
on larger boundaries, it is likely this would be rounded to 1.024 Mbps.
•
The calculations are all based on the expected busy hour call traffic, and CIR is specified
to ensure adequate bandwidth is guaranteed during this period should the Frame Relay
network also be busy (people tend to make phone calls and answer e-mails at the same
time). Other (smaller) values of CIR could be specified, and may well work, but during busy
periods the response to features may be slow and voice quality may be affected.
IP NETWORKING AND USE OF COMPRESSION
IP networking allows the construction of larger systems, and the combining of systems in
different geographic locations into a single system.
If LAN/WAN connections exist between nodes, this medium can be used to pass traffic. A limit
on the number of conversations for this connection is programmed at installation. If the limit is
exceeded, an alternative path is tried through ARS, either through a different node connected
by IP trunks, or through the PSTN TDM network.
The value of the IP trunk restriction is set for a particular connection. This setting relies very
much on traffic and also the bandwidth available.
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: ... ...