5215 Firmware Upgrade

[SeanKirby]

I am having an issue setting up an 5215 phoneset with older firmware.

Due to the configuration of my network, phones will get IPs on different subnets depending on their physical location. Therefore I always have to manually configure the ICP IP Address on the phoneset whenever deploying it to a location where the phone's IP is a different subnet from that of the ICP.

Problem is, this phone has no option to configure ICP address. I have tried configuring it with the TFTP server address (which is the same as the ICP) in the hopes that this would cause it to "reach out" to the TFTP and grab the newest firmware, but it continues to say "upgrade not required" during bootup.

Any suggestions would be greatly appriciated, and I can of course clarify details if people want.

Thank you all in advance.

 

[slapin]

Any way to get DHCP running in those subnets or use DHCP helper?

 

[SeanKirby]

DHCP is running on all subnets; there is a separate DHCP server for each subnet. (Not that it matters but each subnet reflects a seperate domain, and the DC is also the DHCP) IP Phones receive IP address based on their subnet, but for some reason when there is no ICP address manually inputted into the phone, DHCP offer is repeatedly rejected.

Hope that makes some sense...

 

[slapin]

You need to add IP phones specific options into DHCP configuration.
It was discussed on this forum just a couple of days ago.

http://tek-tips.com/viewthread.cfm?qid=1570921&page=4

 

[Canuckvoip]

I wonder what would happen if you defaulted the phone to factory and plugged it into the location closest to the 3300?
Do you have a VLAN?

Dave




You can't believe anything you read... unless of course it's this sentence.

 

[slapin]

Canuckvoip,
Is it a question? The same rules apply regardless of location. You can have DHCP hosted on 3rd party server located somwhere else and use DHCP helper on the switch. This way you can use one central DHCP server (let's say a cluster) and all ICPs with DHCP disabled. Somethimes it may be needed in highly secured environment when you have to authorize every single device in the network, automaticaly assign permanent IPs, require filters on L2 and etc.

 

[Canuckvoip]

Thanks slapin,
And yes, it is a question because if I read the issue right it indicates that the problem relates to the phone/phones that are not on the native subnet.
Just thinking that he may be able to get the firmware upgraded and then move the phone.
Might learn something about the network in general...

Dave

You can't believe anything you read... unless of course it's this sentence.

 

[slapin]

There is no native sunbents. Term "native VLAN" stands for a VLAN which will be used for L2 frames without tags on a trunk port. Typicaly it is used when you connect your computer through a phone. Network switch will place untagged frames from the computer into a native VLAN for this port, which is similar to access vlan when port is in regular access mode. Frames from the phone will be tagged for voice VLAN. Vlan number has to match in switch configuration and DHCP configuration (in rare cases you may have it configured staticaly)

The problem in the original question is clearly pointing to missing DHCP options. The other way is to use Teleworker configuration. Push and hold button 7. Configure IP address of your ICP instead of Teleworker. In this case the phone will accept any DHPC offer which contains just IP address, mask and a gateway. In this case tftp server with firmware images must reside in ICP controller. Wide use of this method can introduce a huge mess and generally not recommended.

 

[SeanKirby]

Canuck, I tried plugging it into the same subnet as the ICP with default settings - it boots up, but does not download new firmware.

I used Slapin's last suggestion of programming the ICP IP address in place of the teleworker and that worked. It's not the ideal solution but it gets the phone working for now. I suspect I will have to look at these DHCP options in more detail.

Thanks guys.

 

[kwbMitel]

Is it possible that the 5212 is a dual mode phone and it is running in SIP mode? Have you tried restoring the phone to factory default? The RTC entry is configurable and you should be seeing it.

*******************************************************
Occam's Razor - All things being equal, the simplest solution is the right one.