DHCP VOIP Without VLAN

We run VoIP for 1000 users over 26 sites using Cisco UCM's. Bit above what you are asking for but I can offer advice.

Although vlans might seem like an overhead to you, they can become your best friend. Yes, there is a learning curve but it will be worth it in the end.

The advantages of vlans come in their isolation ie they limit broadcast domains. They also give you more granular control.

Incidentally, you could achieve the same physically ie with another switch (on a different subnet) to which you only plug the phones into.

With VoIP, you need top notch networks ie you will need to pay attention to QoS etc as allowing users to fully saturate the bandwidth ie heavy download, file copy etc will result in degraded call quality with users don't like to put up with. In this day and age, they demand that phones just work. More so than pc's. Voice needs to be a priority as it needs to arrive in real time and any delay will cause call degradation.

For 40 users, my advice would be to go for a separate vlan (or physically lan if you don't want to get into vlan's)

Most managed switches have programming on them that can assist you with QoS etc eg voice vlan's which can also make it easier for you. So although it might seem daunting at first, it's worth putting the effort in or you could find yourself in a situation where there are issues and they aren't easy to diagnose.

We run VoIP for 1000 users over 26 sites using Cisco UCM's. Bit above what you are asking for but I can offer advice.

Although vlans might seem like an overhead to you, they can become your best friend. Yes, there is a learning curve but it will be worth it in the end.

The advantages of vlans come in their isolation ie they limit broadcast domains. They also give you more granular control.

Incidentally, you could achieve the same physically ie with another switch (on a different subnet) to which you only plug the phones into.

With VoIP, you need top notch networks ie you will need to pay attention to QoS etc as allowing users to fully saturate the bandwidth ie heavy download, file copy etc will result in degraded call quality with users don't like to put up with. In this day and age, they demand that phones just work. More so than pc's. Voice needs to be a priority as it needs to arrive in real time and any delay will cause call degradation.

For 40 users, my advice would be to go for a separate vlan (or physically lan if you don't want to get into vlan's)

Most managed switches have programming on them that can assist you with QoS etc eg voice vlan's which can also make it easier for you. So although it might seem daunting at first, it's worth putting the effort in or you could find yourself in a situation where there are issues and they aren't easy to diagnose.

Let me guess, one point against vlans is the planned usage of the builtin switch in the IP phones for the PCs and laptops? If I am right do yourself a favor and stop thinking about that idea any more ;-) In every situation we had to use them strange behaviours occured to the PC/Laptop connectivity that directly connected devices never have...

In an environment like this i would use a free interface of the UTM for another local network and change all ports on the switches, where a phone is connected to untagged vlan2 for example. Also the port where the UTM is connected via the additional Interface. The uplinks between switches have to be changed to untagged vlan1 (Default) and additionally transfer tagged vlan2. Now you can use the UTM as DHCP for the vlan2. All switches, where a phone is connected need to be vlan capable, but the invest in exchanging 'stupid' 5 or 8port switches to managed switches is worth it.