Mitel MiVOICE BUSINESS, Инструкция по инженерии

Страница: 351 / 381

VoIP and VLANs
337
With this reduced configuration, there is no requirement for VLAN settings .
EXPANDED CXI, DEDICATED VOICE AND DATA PORTS
This is similar in configuration to the standalone CXi with dedicated voice and data ports. The
biggest difference is the connection between the CXi controller and the expansion Layer 2
switch. This link will be shared between voice and data devices. In practice, if the data
requirements are low, then there should be sufficient bandwidth to run without priority queuing.
However, data demands can vary, and there is a potential for congestion. In this case the voice
traffic should be tagged with the higher priority.
The link between the CXi and expansion Layer 2 switch should have VLAN enabled .
The individual end devices can have VLAN and priority assigned at the ingress point of the
network switches, and may use a common VLAN (and subnet). The priority will obviously be
different. However, this is a physical implementation and requires ports to be reconfigured every
time a device is moved. A general setting can be applied, with the data devices going to the
default VLAN and the voice devices being assigned to the voice VLAN, such as through DHCP,
or manual settings.
In this case the individual access ports should have VLAN enabled .
COMMON NETWORK CONNECTION FOR BOTH VOICE AND DATA
DEVICES
Where voice and data devices share a common connection to the network, there is a mix of
data possible on the connection. On ingress to the network port, the phone will prioritize data.
However, on egress, at the far end connection, this will not occur. Priority marking is needed
to allow the egress priority to be carried through the network.
For this configuration VLAN should be enabled at access and network device
interconnections .
CONNECTION TO CORPORATE NETWORK
In this case the end devices are likely physically connected to network devices that are remote
from the controller, e.g. different floors, separate building, etc. The connections through the
network will carry a wide range of information, both data and voice. The controller is likely to
be connected to the network at a point normally associated with other server devices. In this
case it will be a voice server, be it a group controller, a voice gateway, or combination thereof.
Connections for the end devices, such as the phones, require VLAN to be enabled , at the
access points.
For the controllers, or servers, VLAN and priority is also needed . However, this can be
configured in different places. The VLAN, and priority, information can be added at the network
access point. In this case all information will carry the voice VLAN, but will also carry equal
priority for all services. It is also possible to differentiate services and overwrite the VLAN priority
by mapping the type of service (Layer 3) priority field into the VLAN priority field. This is
sometimes described as ‘TOS to COS’ or ‘DSCP to COS’ conversion.