1-5
Table 1-2 Matching relationship between port types and voice devices capable of acquiring IP address
and voice VLAN automatically
Voice VLAN
assignment
mode
Voice
traffic
type
Port type Supported or not
Access Not supported
Trunk
Supported
Make sure the default VLAN of the port exists and is not
a voice VLAN, and the access port permits the traffic of
the default VLAN.
Tagged
voice
traffic
Hybrid
Supported
Make sure the default VLAN of the port exists and is not
a voice VLAN, and the default VLAN is in the list of the
VLANs whose traffic is permitted by the access port.
Access
Trunk
Automatic
Untagge
d voice
traffic
Hybrid
Not supported, because the default VLAN of the port
must be a voice VLAN and the access port is in the voice
VLAN. This can be done by adding the port to the voice
VLAN manually.
Access Not supported
Trunk
Supported
Make sure the default VLAN of the port exists and is not
a voice VLAN, and the access port permits the traffic of
the default VLAN and the voice VLAN.
Tagged
voice
traffic
Hybrid
Supported
Make sure the default VLAN of the port exists and is not
a voice VLAN, the traffic of the default VLAN is permitted
to pass through the port, and the voice VLAN is in the list
of the tagged VLANs whose traffic is permitted by the
port.
Access
Supported
Make sure the default VLAN of the port is a voice VLAN.
Trunk
Supported
Make sure the default VLAN of the port is a voice VLAN
and the port permits the traffic of the VLAN.
Manual
Untagge
d voice
traffic
Hybrid
Supported
Make sure the default VLAN of the port is a voice VLAN
and is in the list of untagged VLANs whose traffic is
permitted by the port.
IP phones acquiring IP address and voice VLAN through manual configuration can forward only tagged
traffic, so the matching relationship is relatively simple, as shown in
Table 1-3:
To Next Page
Loading...
