MCD 5.0 SP1 & 5320 DHCP

[ASCStech]

Guys having real issues with 5320's working at remote sites now that we have gone to MCD5.0.
Our sites are all within our private network and they use the Teleworker option with the private IP of the controller to communicate and get their upload.
However on going to MCD5.0 the 5320 handsets just sit there at DHCP Discovery, but only when on a managed switch that has VLAN's enabled. The phones are always in the default VLAN and we just cannot get them to work.
I know there is a MITEL article on this but it does not help.
Has any one got any ideas on how i can configure the phone or the switch to get around the DHCP Discovery.
By the way the DHCP server is a WAN device and does not have the option to add DHCP Options. the ARP table shows that it has alloctaed the IP to the phone but the phone doesn't seem to acknowledge this. 

[bluewhite4]

If you can, open a ticket with Mitel and get them the traces they're going to ask for. This sounds exactly like the same issue we had, which the bulletin and article didn't apply to. We ended up having to static the phones as it was day of install and we had to get it done.

[ASCStech]

Thanks BlueWhite4 I'll get one raised, although here in OZ we go through a distributor not straight to MITEL and its much harder to get things resolved. 
We tried putting a static on the phone but when it goes through it's boot up it says CONTACING ICP and still cant communicate. When we then check the Static IP settings the IP address is not in the IP V4 Settings
Cheers

[bluewhite4]

Ok, well the fact that it separated the ip address section into ipv4 and ipv6, means that the phones are running the latest firmware. When you say that the "IP Address is not in the IP V4 settings" are you saying the ICP's Ip address or the phones? In our case, we had to static everything including the phones ip address.

[ASCStech]

The statically assigned phone IP disappears when it reboots after saving the config.
However, it kind of looks like a problem between our switch (cisco esw520) and our WAN router. When we plug the phone direct into the router, it worked without any static info. Put back to the switch didn't work.
Did a bit more testing and then all of a sudden it works with DHCP plugged into the switch.
we think it may have something to do with the VLAN tagging but still trying to figure it out. done a few woreshark traces but nothing looks out of the ordinary.

[ralph]

I may be flap'n here a bit but it may be possible that the cisco is trying to put the phone in a different vlan other than default.
Rather than setting the IP address statically have you tried hard coding the vlan?

Ralph

[ASCStech]

Ralph, not far off actually.
what we have found is that the switch is by default using CDP, and the vlan associated with the CDP is VLAN100 (default Cisco). even though we deleted VLAN100 from the switch the CDP Field still showed it. The phone was booting and must have been getting the CDP because as it was going through the boot process we could see the vlan was going to VLAN 0? anyway when we turned CDP off on the switch all was ok. We also left CDP on but deleted the VLAN number which had the effect of putting a 0 in the VLAN field on the switch, which we couldn't do manually as VLAN 0 is not a valid VLAN?? Anyway, with CDP on and VLAN field set to 0 the phone then booted with VLAN NONE, and away to go.
Interestingly enough none of this affected the 5312 handset that we had connected too.
Thanks for the help all.