Mitel MiVOICE BUSINESS, Engineering Manualline

Page: 215 / 381

Network Configuration Concepts
201
VOICE-OVER-IP INSTALLATION REQUIREMENTS
It is essential to assess and configure the network in order to maintain the voice quality and
functionality for the user. This may require that an existing network be changed, or that
equipment with certain capabilities be installed.
The main network issues affecting voice quality are
• delay
• jitter
• packet loss
Care has been taken in the design of the IP phones and controllers to reduce echo through the
inclusion of echo cancellation devices. Jitter and a certain degree of packet loss are also taken
care of by jitter buffers. For more information on these possible network issues, see “Basic
Concepts” on page 203.
Each Mitel device uses a jitter buffer that has been optimized for the device's intended usage:
• 52xx and 53xx IP Phones use an 800 ms dynamically adjustable jitter buffer.
• The 3300 ICP controllers use an 800 ms dynamically adjustable jitter buffer.
• Teleworker uses a 1600 ms jitter buffer on the internet side.
Before implementing a network to handle VoIP, consider the following areas (these are
recommendations, and there will always be exceptions):
• QoS (Quality of Service) Quality of service is that which is provided to the user, not network
equipment settings. However, certain network equipment configurations can greatly assist
in ensuring adequate QoS to a user. These include
- IEEE 802.1p/Q (802.1Q VLAN now included as part of 802.1d) : This is also known
as VLAN tagging, priority, or COS (different from the PBX/telecom Class of Service).
IEEE 802.1p/Q operates at Layer 2 to ensure the highest priority for voice traffic.
- DiffServ (also known as DSCP) : DiffServ is a fixed field in the Layer 3 information
that is also used to define different service categories through TOS, priority, and
precedence. DiffServ and Type of Service are similar. The older Type-of-Service
values are compatible with the newer DiffServ values.
• Switched networks : Use switched networks, which then allow full-bandwidth capability to
all endpoints. Networks with hubs include shared bandwidth; no priority mechanisms are
available.
• Network topology : Networks should be designed in a hierarchical manner where band-
width between devices is controlled and understood. Simply linking switches in a long chain
will work for data, but it introduces jitter and unnecessary bottlenecks between devices.
• Network pre-installation and post-installation analysis : The network should be inves-
tigated before installation to determine suitability for VoIP. Once an installation is completed,
it should also be tested to ensure that the guideline limits have not been exceeded.
• Network address translation (NAT) and firewall : Although there are emerging standards
to allow VoIP through firewalls and NAT devices, these are still in early development. To