sundance-communications.com/forum Forums Other TDM Phone Systems Shoretel Telephones & Systems Guide for DHCP/VLAN setup?

Does anyone have a guide or basic walk through for setting up DHCP or Boot Option 156 when you have a VLAN that is dedicated for voice?

Struggling a little with this.

D

Are you having trouble configuring this on a Window server or having trouble with the syntax of the option?

If you have a Vlan, is the same server also handling DHCP on the 2nd VLan? Some people have trouble with this. After the phones reconfigure to be on the voice vlan, they can't reach the Windows server to get DHCP. You need to have the router pass DHCP using DHCP helper.

Some people (even me in rare cases) have used the Shoretel server to handle DHCP for phones on a voice vlan. Shoretel does not recommend using the server as a DHCP server.

DO you have IP400 series phones? There is a new value for those phones, although the ftpservers value is still supported. The new option 156 value is configServers=.

Just sent you a PM with a couple more details about setting up DHCP options on a Windows server

Thanks!

Today's struggle was brought to you by IT guy (hads off my network, I'll do it all guy) and trying to convey what he needed to do to get phones operational.

All good now, just a frustrating experience today.

Thanks again!!

D

I'm glad it all worked out. I know how that can be. Unlike a TDM PBX, with Shoretel you often have to plug into a network manged by someone else.

We don't try to make the IT out to be the bad guy. We want to try and would out issues together. I've ran into some that didn't really know how to build the VLANs in a switch, so I'll help. I ask for a couple static IPs so I don't conflict with his DHCP scope.

One time I had statically assigned about 30 phones so we can finish the job and go home.

We have lost more then 1 account to an outside IT service that also does Shoretel after they convinced the customer that it was better to have only point of contact for both phones and data service.

I see that is is 2 months old now, but what was the final answer?

We are evaluating a Shoretel for our health System, and need advice on the network side.

The phones are not pulling the voice vlan or config server information.

this is our switch and DHCP scope for the test

interface FastEthernet0/20
switchport access vlan 14
switchport voice vlan 15
speed 100
duplex full
spanning-tree portfast

my DHCP scopes

ip dhcp pool data
network 192.168.14.0 255.255.255.0
default-router 192.168.14.1
!
ip dhcp pool shoretel
network 192.168.15.0 255.255.255.0
default-router 192.168.15.1
option 156 ip 192.168.15.200

Thanks

The phones pull dhcp from vlan 14 not vlan 15

I at least got it looking at the correct vlan
Changed my DHCP scope to

ip dhcp pool data
network 192.168.14.0 255.255.255.0
default-router 192.168.14.1
option 156 ascii"configservers=192.168.15.200,ftpservers=192.168.14.200,layer2tagging=1,vlanid=15"
!
ip dhcp pool shoretel
network 192.168.15.0 255.255.255.0
default-router 192.168.15.1
option 66 ascii "192.168.14.200"
option 155 ascii "192.168.14.200"

What doesn't work is the config server, the entry is still unpopulated on the phone.

Any idea's would be great please.

So far my experience has been to have the IT group setup a seperate vlan for the phones and make sure the Shoretel boot option 156, and boot option 42 (for older 655 and 230/235 phones) is setup.

Lets say you've got two vlans, 192.168.x.x for data network and 10.0.x.x for the voice vlan. The downside I've seen is that the phone will pull a 192.168.x.x address then will use boot option 156, re register and then pull a 10.0.x.x address, which is normally fine, unless you have 200 phones and not enough addresses in the 192.168.x.x scope to accommodate the temporary lease to the phone.
I've had to have the IT folks go in and clear out the addresses from the 192.168.x.x so the rest of the phones can come up because the scope filled up.

You're setup looks good.

D

I was just going to say to use option 156 on both VLANs, but you already took care of it. Once the phones reconfigure the Ethernet card for the new VLAN, they will come back looking for a DHCP server on the new VLAN. Sometimes people that are using a Windows server for DHCP don't have the network configured properly to pass DHCP to the second VLAN, and the phones will just sit there looking for a DHCP server.


Also, you should consider adding option 004 for a time server so the phones can have the correct time on the display.

Thanks All.