VLANS and VoIP

[Chuckster]

Created two VLANS on a HP switch

• VLAN 100 - Data
  
• VLAN 200 - Voice
  

 

We have a NEC phone system and the handsets we have allow PC data to be shared through it.

 

I have untagged the port for the voice VLAN and tagged for data.

 

The phone correctly obtains the correct IP address from VLAN 200. But the PC doesn't and will obtain the IP from the voice vlan.

 

I have gone through the handset menu settings and assigned the corresponding VLAN IDs - LAN port is set to 200 and PC port is set to 100.

 

However, it doesn't work.

 

If I make the handset port tagged and the data untagged, then the data works but then the handset doesn't function, i.e. no dial tone.

 

Any ideas?

[snagrat]

Do your switches not support Voice VLAN?

[rls2k5]

The ports should be untagged for data and tagged for voice.

 

On the switch the voice vlan should be marked as the voice vlan. (ArubaOS example below)

 

vlan 100

name "DATA"

untagged 1-20

vlan 200

name "VOICE"

tagged 1-20

voice

 

The handset should not need the vlan IDs set.

[FragglePete]

For our setup where we have phones with PCs attached, it's a case of tagging both VLANs on the port of the switch and the phone itself should have the ability to configure what sits on each VLAN.

 

Think of the phone as a switch itself and your trunking to the phone and the phone sets the tags for voice and then for data.

 

Pete

Edited August 10, 2022 by FragglePete

[Davit2005]

Created two VLANS on a HP switch

• VLAN 100 - Data
  
• VLAN 200 - Voice
  

 

We have a NEC phone system and the handsets we have allow PC data to be shared through it.

 

I have untagged the port for the voice VLAN and tagged for data.

 

The phone correctly obtains the correct IP address from VLAN 200. But the PC doesn't and will obtain the IP from the voice vlan.

 

I have gone through the handset menu settings and assigned the corresponding VLAN IDs - LAN port is set to 200 and PC port is set to 100.

 

However, it doesn't work.

 

If I make the handset port tagged and the data untagged, then the data works but then the handset doesn't function, i.e. no dial tone.

 

Any ideas?

 

Untagg it on data and tag it on voice is normally the way defo with Cisco and Mitel phones I have encountered. The phones nearly always strip the tagging then pass though the data. Whilst the PC will not normally deal with tagged data unless the network card is capable of vlans.

 

So if you have the vlan set to voice (some very old HP switches do not support LLDP-MED) setup right you should not need to do anything on the phone in the best scenario. DHCP is normally set to provide some info on the voice vlan i.e. scope either tftp so the phone can download it's config from the VOIP server or option 43 that point to the VOIP server.

 

For instance at home I have 3cx, DHCP scope has the tftp server pointing to the 3cx. I can literally plug a compatible phone in as default state and need not do any more. The VOIP vlan is set to voice on the switch where the phone connects and it is a LLDP-MED capable switch.

Edited August 11, 2022 by Davit2005