1. Home
  2. How To
  3. How to Configure a Meraki Switch for VoIP
  1. Home
  2. Phone Hardware
  3. How to Configure a Meraki Switch for VoIP

How to Configure a Meraki Switch for VoIP

This document outlines the steps recommended to configure an MS Meraki Switch to optimize VoIP performance and minimize poor call quality:Standard Data/VoIP deployments commonly utilize a three port switch built in to the VoIP phone to connect a workstation and phone to the same switch port:

MS Access Switch should be configured with Voice VLANs and QoS (Quality of Service) to separate voice traffic into its own broadcast domain and tag it for optimal transfer and prioritization. The MS Access Switch utilizes LLDP (Link Layer Discovery Protocol) to recognize the VoIP phone connected and retrieve various properties of the phone. QoS on the MS Switch tags specific traffic that is incoming on the desired switch ports and prioritizes traffic which is important for voice traffic due to its sensitivity to latency.

  1. Configure the desired switch port(s) as access port(s)
  2. Configure data and voice VLANs 
  3. Configure QoS settings

Configuring Access Ports

  1. Navigate to Configure > Switch ports and choose the specific port to be modified. 
  2. Using the Type drop down, change the port to access:

Configure Data and Voice VLANs

Once the port has been changed to an access port, enter the data and voice VLANs:

Configure QoS settings

QoS settings can be enabled on dashboard under Configure > Switch Settings, in the Quality of service section:

This rule tells the MS Access Switch to place a class tag on the specific voice packets that enter it. See this knowledge base article for more information on QoS. This tag will follow the voice packets to other switches. Below is an example of a configured rule under the QoS section. VLAN 20 is the voice VLAN for this network:

These configurations ensure the switch will correctly prioritize voice traffic as it traverses the network and reduce the chance of voice data being forwarded incorrectly. 

Updated on June 17, 2021

Was this article helpful?

Related Articles