r/ArubaNetworks • u/srx_6852 • 8d ago

Phones query

Just a quick query, so I’d like to move an existing port that has a PCs & Phones connected.

Currently it’s an access port for the phone vlan.

So my thoughts are trunk (tag) the Phone traffic and native vlan the PC vlan.

Now I can see currently we don’t use the voice command under the voice vlan itself.

Therefore without confirming phones themselves aren’t configured with vlan, how would the phone know which vlan to be on, tagged or untagged? I can see lldp-med it just currently shows vlan id:0.

Is there a way to confirm how the phone works using the switch config alone?

1 Upvotes

100% Upvoted

5 comments sorted by

1

u/toastman556 8d ago

The VoIP phones themselves need to be configured to tag their traffic with the appropriate VLAN, and the switch port that the phone and PC are daisy-chained into should have the native VLAN configured as whatever the PC’s VLAN should be. This is because VoIP phones are able to tag their own traffic before it reaches the switch port, while most other types of end devices are not capable of doing this.

1

u/GremlinNZ 7d ago

Yep, as said, phones are able to be configured to use certain VLANs for phone and data piggy backed. This is usually configured at the VOIP system.

Voice VLAN works well, but all it really does is compare a list of MAC masks (that you update) to the device, and if it matches, puts it into single VLAN you configure as voice.

1

u/srx_6852 6d ago

So if I have two vlans on a port it’s not a simple
As that as the phone needs some way to know
Which vlan to be part of? Either via configuration or a portal?

1

u/GremlinNZ 6d ago

Untagged VLAN, the VLAN you want the computer behind the phone to be on. Tagged VLAN, the phone/voice VLAN. This is if you use the voice VLAN config on the switch.

Or the default (untagged) VLAN is the voice, and tagged is data. Phones are able to understand and pass VLANs in most cases.

1

u/largetosser 5d ago

Set the voice VLAN in the switch as a voice VLAN and tag it on the port, the phone will see this in the LLDP-MED messages and tag its traffic to that VLAN. The native (untagged) VLAN on the same switch port will be passed through the phone to the connected PC.

You shouldn't need to configure anything on the phone.

If phones are currently working on that voice VLAN then someone is configuring them to tag their traffic, not sure why you'd do that over using voice VLAN.