Bandwidth, Codecs and Compression
177
BANDWIDTH MANAGEMENT
This section details the new bandwidth management solution.
BANDWIDTH MANAGEMENT AND CALL ADMISSION CONTROL
The terms “Bandwidth Management” and “Call Admission Control” are often used
interchangeably to mean the management, and potential re-routing, of calls across an IP
network between end devices. In reality these are two separate concepts. Bandwidth
management gathers information about the availability and use of bandwidth on particular
connections and links. Call Admission Control uses this information to decide whether a call
should be completed or not.
Although the IP network is often considered as a “cloud,” it is actually made up of many parts,
including LANs, MANs and WANs. There are constraints on the amounts of data that can be
handled at the transitions between the different networks, and often within the networks
themselves.
If a link is bandwidth limited, it is desirable to be able to determine the available bandwidth
across the link and manage it to ensure that it is available for voice use. Once the bandwidth
is known, it is possible to determine how many virtual channels can be established and to admit,
redirect or reject calls based on current available resources, that is, bandwidth. The latter is
the task of Call Admission Control between end nodes.
Call admission control updates
Currently, Call Admission Control is applied to calls that must pass between different controllers
and nodes, including when using IP Networking or IP Trunks. The same mechanism also applies
to SIP Trunks and TDM trunks, although the latter is predetermined through the type of trunk,
PRI, for example. In most cases, this is an appropriate way to limit and re-direct calls. This
mechanism is now being expanded across the entire installation through the use of common
zone numbering. This will provide finer control of call admission in situations including:
•
multiple nodes that use a common network connection
•
remote workers who don't use IP Networking, including hot desk users
•
resilient/redundant switchover to a backup controller at a remote site with limited bandwidth
•
identification of bandwidth usage
Call Admission Control works by:
•
knowing the network topology and identifying bottlenecks such as edge routers
•
tracking bandwidth usage at the bottleneck/gateway points
•
specifying voice limits for a connection, e.g. voice may only be allowed to use 50% of the link
•
following the media path connection, that is, the most direct path. Signalling may involve a
number of units and may follow a different path than the media does. When traversing
zones, however, the calls must go through a bandwidth controller to be counted.
The zones and network topology are defined and propagated between the controllers and the
Enterprise Manager. Some additional tuning may be required locally at controllers where
bandwidth is shared. You may need to specify alternative routes where multiple routes go
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: ... ...