How to configure Auto-VoIP on Omada Switches via Omada Controller
TL-SG2008P , TL-SG3452X , SG3452XMPP , TL-SG2218P , TL-SG3452XP , TL-SG2016P , SG2210XMP-M2 , SG3428XPP-M2 , SG3428XMPP , TL-SG2210P , SG2210MP , TL-SX3008F , TL-SL2428P , TL-SX3016F , SG2218 , SG3428 , TL-SG3452P , SG3218XP-M2 , SL2428P , SG3210X-M2 , TL-SG3428XF , TL-SG2210MP , SG3428X-M2 , SG3210 , SG3452 , SX3032F , SG3452X , SG3210XHP-M2 , TL-SG3210XHP-M2 , SG2008 , TL-SG2428P , SG3428XF , SG2005P-PD , SG2428LP , SG6428XHP , SX3008F , SG3428MP , SG3428X , SG3452P , SX3016F , TL-SG3428X-UPS , SX6632YF , SG2218P , SG2008P , SG3452XP , SG2452LP , SG2210P , SG6654X , SG2016P , SG6428X , TL-SG2008 , TL-SG3452 , TL-SX3206HPP , SG3428XMP , SX3206HPP
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device and check either the Datasheet or the firmware section for the latest improvements added to your product.
Contents
This article describes how to configure Auto-VoIP feature on Omada switches via Omada Controller.
- Omada Smart, L2+ and L3 series switches
- Omada Controller (Software Controller / Hardware Controller / Cloud Based Controller, V5.9 and above)
Auto-VoIP requires the IP Phone to support LLDP and deal with tagged packets.
Switch will send requirements of voice traffic to IP Phones by LLDP communication, then IP Phone would use corresponding tag, there are 4 types of tag are supported.
- None: Allow the voice devices to use its own configuration to send voice traffic.
- VLAN ID: The voice devices will send voice packets with desired VLAN tag. If this mode is selected, it is necessary to specify the VLAN ID in the Value field.
- Dot1p: The voice devices will send voice packets with desired 802.1p priority. If this mode is selected, it is necessary to specify 802.1p priority in the Value field.
- Untagged: The voice devices will send untagged voice packets.
Usually, VLAN ID is the most popular one, traffic from the IP phones will pass through the Voice VLAN, while data traffic will pass through the data VLAN (Native VLAN of port).
The below is the typical topology of Auto-VoIP feature, the voice traffic and data traffic are passing through the same port of Switch B. In that case, the Auto-VoIP need to be enabled on Switch B.
The tasks to configure Auto-VoIP are as following:
- Create 802.1Q VLAN for voice and data traffic
- Create port profile and apply it to the specific switch
- Configure LLDP and LLDP-MED
- Configure Auto-VoIP
Step 1. Create 802.1 Q VLAN for voice and data.
Login to Controller via web browser, go to Site Settings>Wired Networks>LAN, click Create New LAN to add Voice VLAN (VLAN10) and Data VLAN (VLAN20)
Step 2. Create port profile.
Go to Profile and click Create New Port Profile to create port profile.
Configure egress rule as VLAN 10 is tagged, while VLAN 20 is untagged.
The Native Network should be VLAN 20 for clients, and set VLAN 10 as Voice Network and click Save.
Note: LLDP-MED is enabled by default when create port profile, you can find it in the advanced settings of port profile. So we can skip this step and enable Auto-VoIP directly.
Step3. After creating port profile, it should be applied to the ports which are connected to IP Phones (In the topology, it’s port 2 of Switch B).
Go to Device>Switch B>Ports>Port 2, click Edit button.
Choose the Auto-VoIP profile and click Apply.
Step 4. Configure Auto-VoIP.
Since the Omada Controllers don’t support the configuration of Auto-VoIP on switches through the GUI, you need to use the CLI commands to perform the configurations in the Controller mode.
Go to Site Settings>CLI Configuration>Device CLI, click Create New Device CLI Profile
Input following commands and apply it to switch B:
auto-voip
interface gigabitEthernet 1/0/2
auto-voip 10
Please connect IP Phones to your configured switch and the IP Phone should work properly now.
We also can login to the switch by SSH to check the Auto-VoIP and LLDP status.
Go to Tools>Terminal, the Device Type is switch, and then choose Switch B, then input the following commands to check the status:
en
show lldp neighbor-information interface gigabitEthernet 1/0/2
With above steps, we have finished the configuration of Auto-VoIP, TP-Link also provide another method for voice QoS – Voice VLAN, please refer to the related FAQ to check more details.
Related FAQs
Is this faq useful?
Your feedback helps improve this site.
What’s your concern with this article?
- Dissatisfied with product
- Too Complicated
- Confusing Title
- Does not apply to me
- Too Vague
- Other
We'd love to get your feedback, please let us know how we can improve this content.
Thank you
We appreciate your feedback.
Click here to contact TP-Link technical support.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
This website uses cookies to improve website navigation, analyze online activities and have the best possible user experience on our website. You can object to the use of cookies at any time. You can find more information in our privacy policy . Don’t show again
Basic Cookies
These cookies are necessary for the website to function and cannot be deactivated in your systems.
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_base, tp_privacy_marketing, tp_smb-select-product_scence, tp_smb-select-product_scenceSimple, tp_smb-select-product_userChoice, tp_smb-select-product_userChoiceSimple, tp_smb-select-product_userInfo, tp_smb-select-product_userInfoSimple, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Analysis and Marketing Cookies
Analysis cookies enable us to analyze your activities on our website in order to improve and adapt the functionality of our website.
The marketing cookies can be set through our website by our advertising partners in order to create a profile of your interests and to show you relevant advertisements on other websites.
Google Analytics & Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads & DoubleClick
test_cookie, _gcl_au