VOSS LLDP-MED with Mitel Phone

[bfaltys]

Trying to get this to work, but no luck so far. I have 2 separate VLANs for data and voice. On the VSP port, the data VLAN is default and untagged. I have also configured 2 commands for LLDP-MED to get the Mitel onto the voice VLAN. However, the phone is still landing on the data VLAN. The LLDP-MED commands used on the interface are:

lldp med-network-policies voice tagging tagged vlan-id 1121
lldp med-network-policies voice-signaling tagging tagged vlan-id 1121

#show lldp med-network-policies
************************************************************************************
Command Execution Time: Thu Oct 21 13:47:35 2021 CDT
************************************************************************************

==========================================================================================
LLDP-MED Network Policies
==========================================================================================
Port Application Type VlanID Tagging DSCP Priority
------------------------------------------------------------------------------------------
1/9 Voice 1121 Tagged 46 0
1/9 Voice Signaling 1121 Tagged 0 0
------------------------------------------------------------------------------------------

As a follow up question, does anyone know the difference between the policy types? That being {guest-voice | guest-voice-signaling | etc..}.

[bfaltys]

Followed the steps at the link below, but that did not work.

https://extremeportal.force.com/ExtrArticleDetail?an=000099587

[bfaltys]

I can get this to work with the "auto-sense" feature, but we have locations with more than 1 voice VLAN so we really need to be able to define this per port.

[Roger_Lapuh]

The idea of auto-sense is to be able to remove any per port configuration and let auto-sense take care of the device assignments automatically. If a global voice vlan for auto-sense does not work for you, then I suggest to either use NAC to assign a voice vlan to the phones via Radius or, then you take the port out of auto-sense (no auto-sense enable convert-to-config) and then adjust the voice vlan manually. This can be done on any port individually. I recommend to use 8.4.2 as there are additional capabilities that will simplify per port assignments.
I hope this helps. 
Roger

[bfaltys]

When I got this working with the auto-sense I did try the convert to config. At that point I removed the auto-config voice vlan and that broke it. If it is converted to a config on an interface I would think it should no longer rely on a global setting, right?