Normally I don't post about things related to sipx unless they are directly related to sipx.
For the past year or so I've taken a different approach to how I deploy sipx for what I would claim "obvious ease of use" reasons.
There are some caveats: When you don't control the firewall the firewall vendor/admin needs to know how to deploy vlans on their device. Some don't which is something I had to wade through last year. After I did that the vendor moved some equipment and there were dueling DHCP servers between the data and voice networks.
Lesson learned: Try to force the outcome before deployment. Make the vendor ante up the talent to deploy their firewall so that the ethernet ports are all trunked.
So, here's the skinny: It's really a linux thing.
First, copy your config file for the network interface (not sure what the interface is, do an ifconfig).
cp /etc/sysconfiog/network-scripts/ifcfg-eth0 /etc/sysconfiog/network-scripts/ifcfg-eth0.2
Then edit ll but the first two lines of ifcfg-eth0 out, in ifcfg-eth0.2 change the name from "eth0" to "eth0.2" in the file and in the next line add "VLAN=yes".
You will want to stop sipx services, then restart networking (service network restart). Assuming the interface comes up with no errors, start sipx services. Now make sure your switch where sipx is plugged in is VLAN2=tagged.
You will need to repeat the process with your gateways to make sure they are vlan2 tagged in their respective configs before changing the switch port from vlan2=untagged to vlan2=tagged.
Now with your phones on the same vlan (2), it's easy to move the server to whatever port you want. No more DHCP feuds either.