Vlan for VOIP

[karldenton]

Hi

 

Just after a bit of advice regarding a VoIP VLAN.

 

Our current setup is

 

Sophos UTM router for all network traffic. This has a vlan on it and we vlan all our switches for wifi devices. The UTM gives out the IP.

Separate router from cloud voice company connected to a switch. The router gives out the ip address to the phones. The phones are patched into this switch

 

The issues is some phones are connected on the main LAN going out through the UTM and I'd like to vlan them off so they get an IP on the phone network.

 

I have tried untagging a port on our core switch on the VoIP vlan, connecting that to the phone switch and tagging another port on the core as a test, but it gets a normal LAN IP.

 

I'm presuming I either need another cable from the router to our core switch or I need to setup the vlan on the phone switch as well?

 

Thanks

[AlanD]

So ...on the core switch....untag the VOIP vlan on two ports. Set the PVID (primary/default/whatever) on those ports are set to the Voip Vlan..and remove the default/main/all other Vlans from those ports. Plug phone router into one port....phone in other.

[karldenton]

Thanks Alan.

I presume I can then do what I've done with the iPad network and tag the fibres etc so phones can be tagged at the other ends of the switches too.

 

If I'm just tagging rather than untagging, I'm presuming I need to set on the handsets the vlan too

Edited September 7, 2018 by karldenton

[Davit2005]

What switches are you running, what sort of VOIP system have you got or is it cloud based, what phones are you using?

 

For instance at home I have 3cx phone system hosted internally, HP switches and Cisco SIP phones. The voice vlan is completely different to all other vlans and ports are tagged on the switch for the voice vlan and untagged for normal data i.e. PC's. The voice vlan is set to voice on the switch so the phone works with LLDP-MED. On the Voice vlan DHCP scope there are specific settings so the phones know the 3cx server and pull the config down direct from the server. In the ideal setup you should just be able to plug a VOIP phone in to a port and as long as the port is tagged for the voice vlan it all should work.

 

 

So in your scenario I suggest try untagging the port connecting to the switch for the voice vlan to the voice router then tagg the port on the switch that connects to the phone with that vlan and untagg normal data trafiic that should go via the UTM.

Edited September 7, 2018 by Davit2005

[mavhc]

What switches are you running, what sort of VOIP system have you got or is it cloud based, what phones are you using?

 

For instance at home I have 3cx phone system hosted internally, HP switches and Cisco SIP phones. The voice vlan is completely different to all other vlans and ports are tagged on the switch for the voice vlan and untagged for normal data i.e. PC's. The voice vlan is set to voice on the switch so the phone works with LLDP-MED. On the Voice vlan DHCP scope there are specific settings so the phones know the 3cx server and pull the config down direct from the server. In the ideal setup you should just be able to plug a VOIP phone in to a port and as long as the port is tagged for the voice vlan it all should work.

 

 

So in your scenario I suggest try untagging the port connecting to the switch for the voice vlan to the voice router then tagg the port on the switch that connects to the phone with that vlan and untagg normal data trafiic that should go via the UTM.

 

How does the phone know which vlan to use, or switch know that a device is a phone?

[Davit2005]

To be honest. Without knowing what phones, or switches the OP is using it is hard to know.

 

For instance I use HP 2530 switches but have used others and they have a specific setting where you enable voice on the vlan. this with LLDP-MED should help.

[karldenton]

Hi. Thanks

 

Using Yealink T23 handsets with HP 1920 switches