BOOTP Fails when using DHCP from IPOffice 412

[ipofficedude]

I have just set up a phone system/network that includes 40x 5400 series IP hard phones and 10x 3600 series spectralink phones.

We also have 10 Access points (AP7) and a AVPP.

The network backbone is a Nortel Baystack 5520 and 460 set up.

The switches accomodate 802.1af and Layer 3 routing, QoS and VLAN's.

We have done all the VLAN tagging so that you can plug a PC into the back of the phone and it will pick up a different VLAN to the Phone etc.

BUT

It only works for static IP entries on the phone (5400)!!!!

The moment you configure DHCP or just use 0.0.0.0 for the IPAddress only it (ip phone) fails to boot up at all!

i.e the tftp log says BOOTP failed to process.

the problem I feel is that i'm using the dreaded IPO as a DHCP server for the time being until the cust has his windows 2003 server set-up.

I have modified the text 46xx file but can't seem to get it working!

The Wireless phones are fien on DHCP as the Ap's are assigned to a single port VLAN.

Sorry, forgot to add that the IP hard phones also work on DHCP if you don't have the requirement to plug a PC into the back of it.

It seems that the phone or IPOffice or switch doesn't like splitting the port across two VLANS and tagging the phone but not the PC data?!?!

Any ideas?

Cust is not too happy with static assignment and admin will be a pain!
Cheers

 

[intrigrant]

Maybe your problem is that ipo can only assign 5 ip addreses at the same time, maybe if it gets more requests at once it gives up? I never tried.

 

[SuperJenks]

The IP phones are designed for the purpose of splitting voice network from Data/PC network by vlan. Are you tagging the pc network or untagged. Unless there is another reason for tagging the PC network, I would run the pc network untagged and tag the voice network. Also, by connecting the pc through the phone connection, the IP phone will prioritize the voice packets to be sent out first even if there was no tagging going on at all for either networks. The tagging is mainly for the managed switch to route the packets more efficiently. As far as the DHCP problem, my first question that comes to mind is: Are you entering an IP address for the phone under "Extensions" in manager for the VoIP users. The IP address must be left blank to accept a connect from any address verses a static address. Secondly, I would make sure the phones can connect to the tftp server ensuring that they are truly receiving the DHCP information from the .scr file. If that process never happens the phones will always fail.
Watch the tftp log viewer in the manager when the phone boots up. You could even put a network analyzer on the network to see whats truley happening. I hope some of this helps you. I may have stated the obvious but its usually the simple things that are forgotten about that will burn ya.