How to configure the switch to improve voice traffic quality (V4.80 firmware version)

Zyxel_Melen
Zyxel_Melen Posts: 2,403  Zyxel Employee
Zyxel Certified Network Engineer Level 1 - Switch Zyxel Certified Network Administrator - Switch Zyxel Certified Network Administrator - Nebula Zyxel Certified Sales Associate
edited February 7 in Port & VLAN settings

The example shows administrators how to use Voice VLAN to improve Voice traffic. Like the introduction in other FAQs, Voice VLAN not only groups voice traffic into an assigned VLAN, but also assign the voice traffic a certain priority. Administrators can use this priority to improve Voice traffic quality. The Voice VLAN priority can be applied to both tagged and untagged voice traffic.

Note: All network IP addresses and subnet masks are used as examples in this article. Please replace them with your actual network IP addresses and subnet masks. This example was tested using XS3800-32 and GS2220-50HP.

1. Configure VLAN for voice traffic

1-1. Configure VLAN 100 on Switch-1 and Switch-2. VLAN 100 is created for the Voice VLAN. Make sure that devices in VLAN 100 can communicate across Switch-1 and Switch-2.

2. Configure Voice VLAN

2-1. Enter the web GUI and go to: Menu > Switching > VLAN > Voice VLAN Setup. Key in the Voice VLAN. In this example, it is VLAN 100. Assign a priority to the traffic, for example, priority=6. Click “Add”.

Configure the OUI Setup: Enter the web GUI and go to: Menu > Switching > VLAN > Voice VLAN Setup > Voice VLAN Setup > Voice VLAN OUI Setup. Set the OUI address. (You can key in the MAC address.) In this example, it is 00:15:65:93:81:54. Set up the OUI mask as ff:ff:ff:00:00:00. Click “Add”.

Note: This will instruct the switch to process any traffic from devices with MAC address between 00:15:65:00:00:00 and 00:15:65:ff:ff:ff into the Voice VLAN.

3. Configure Mirroring (For "Test the Result")

3-1. To verify that results are acceptable, we have to use the mirroring function to check if the priority of the packet is what we assigned. Enter the web GUI and go to Menu > Switching > Mirroring > Mirroring. Check the “Active” box. Key in the Monitor port, which is used to monitor the traffic. Check the port we want to mirror. In this example, it is port 2. Select the direction as “Both”. Click “Apply”.

4. Test the Result

4-1. Connect the PC and Switch-1. Open Wireshark to monitor the packet. Filter “arp || igmp”.

4-2. Use Switch-2 to ping IP Phone: Enter web GUI and go to Menu > Maintenance > Diagnostic > Ping test. Switch-2 can ping IP Phone successfully.

4-3. Check the packet from IP Phone (192.168.100.100) on Wireshark. The VLAN header should indicate the assigned Voice VLAN priority “6”.


5. What Could Go Wrong

5-1. If the priority is not the same as the setting in voice VLAN, please verify the MAC address of the IP phone. The MAC address can usually be found on the label or sticker underneath the IP phones. This MAC address must be within the range of the Voice VLAN OUI settings.

5-2. Here are the expected behaviors of IP phones based on the different settings. If you find the behaviors of the IP Phone is not the same as your expectation, please refer below:

5-2-1. If the IP Phone is VLAN enabled and this VLAN is the same as Voice VLAN: The Switch will keep the Voice VLAN and assign the priority setting to the IP phone. The IP phone will only recognize the tagged traffic. In this case, port 1 in VLAN 100 on Switch should be set as tagged out (check the TX tagging box).

5-2-2. If the IP Phone is VLAN enabled and this VLAN is different from the switch’s Voice VLAN: The Switch will not apply any changes on the VOIP traffic of the IP Phone.

5-2-3. If the IP Phone is VLAN disabled: The Switch will assign the Voice VLAN and priority setting to the IP phone’s VOIP traffic. This setting causes the IP Phone to only send and receive untagged traffic. In this case, port 1 in VLAN 100 on Switch should be set as untagged out (uncheck the TX tagging box).

5-3. Some computer network cards may not support the 802.1Q (VLAN) information. If you don’t see the 802.1Q information in Wireshark, you may need to use a different NIC. We recommend using USB network adapters.