a port from the voice VLAN if no packet is received from the port during the aging time. Assigning ports to and removing ports from a voice VLAN are automatically performed.
∙In manual mode, you need to manually assign an IP phone accessing port to a voice VLAN. Then, the system matches the source MAC addresses carried in the packets against the device’s OUI addresses. If a match is found, the system issues ACL rules and configures the packet precedence. In this mode, assigning ports to and removing ports from a voice VLAN are performed manually.
Both modes forward tagged packets according to their tags.
1 lists the relationships between the voice assignment VLAN mode, the voice traffic type of an IP phone, and the port link type.
1.
Voice VLAN | Voice traffic | Port link type |
|
| |
assignment |
|
|
| ||
type | Access | Trunk | Hybrid | ||
mode | |||||
|
|
| Supported, but you must | Supported, but you must | |
|
|
| ensure that the PVID of | ||
|
|
| ensure that the PVID of the | ||
|
|
| the port has been | ||
| Tagged voice |
| port has been created and is | ||
| Not supported | created and is not the | |||
Automatic | traffic | not the voice VLAN and the | |||
| voice VLAN and the | ||||
|
| traffic of the PVID can pass | |||
mode |
|
| traffic of the PVID can | ||
|
| through the port tagged. | |||
|
|
| pass through the port. | ||
|
|
|
| ||
|
|
|
|
| |
| Untagged | Not supported | Not supported | Not supported | |
| voice traffic | ||||
|
|
|
| ||
|
|
|
|
| |
|
|
| Supported, but you must | Supported, but you must | |
|
|
| ensure that the PVID of | ensure that the PVID of the | |
| Tagged voice |
| the port has been | port has been created and is | |
| Not supported | created and is not the | not the voice VLAN and the | ||
| traffic | ||||
|
| voice VLAN and the | traffic of the voice VLAN can | ||
|
|
| |||
|
|
| traffic of the PVID can | pass through the port | |
Manual |
|
| pass through the port. | tagged. | |
|
|
|
| ||
mode |
|
| Supported, but you must | Supported, but you must | |
|
|
| |||
|
| Supported, but | configure the PVID of | ||
|
| configure the PVID of the port | |||
|
| you must | the port as the voice | ||
| Untagged | as the voice VLAN and | |||
| configure the PVID | VLAN and configure the | |||
| voice traffic | configure the port to allow | |||
| of the port as the | port to allow the traffic | |||
|
| the traffic of the voice VLAN | |||
|
| voice VLAN. | of the voice VLAN to | ||
|
| to pass through untagged. | |||
|
|
| pass through. | ||
|
|
|
| ||
|
|
|
|
| |
|
|
|
|
|
NOTE:
If an IP phone sends tagged voice traffic and its accessing port is configured with 802.1X authentication and guest VLAN, you must assign different VLAN IDs for the voice VLAN, the port VLAN ID (PVID) of the accessing port, and the 802.1X guest VLAN.
If an IP phone sends untagged voice traffic, to implement the voice VLAN feature, you must configure the PVID of the IP phone’s accessing port as the voice VLAN. As a result, 802.1X authentication cannot be implemented.
154