IP Office R4.0(14), Control Unit is a v1, phone is a 5410, Essential Edition
When replacing 5410 phones, they get stuck on the "Please Wait" since they can't find a server to upgrade/downgrade their BIN file. I've had the tech in the field try the following:
-Change the TFTP server to the LAN 1 address, which works occasionally
-Add the ALLOW_5410_UPGRADES source code to the NoUser user, which so far hasn't worked
I was going to have the tech change the working directly to his laptop and set it as the TFTP server, but he's got a much later release on his laptop. I do have remote access to these systems, and available phones in my lab that I could try and pre-program with the correct BIN files and then ship to site, but I have a few questions:
1 - the laptop I connect remotely with has a much newer release of Manager software on it, but I do have the R4.1 software installed on a USB drive. Could I plug the USB drive into the laptop, change the working directory and Binary directory to the USB drive Manger folder, and then try either the ALLOW_5410_UPGRADE approach or change the TFTP server to the PC LAN Address?
2 - if I try to downgrade the firmware to the proper BIN file in the lab and then ship, what's the easiest way to do that? I don't have any v1 Control Units here, but I do have an R6.1(22) one available. The BIN file for the 5410 in that is R6, but I also put the R5 BIN file in there to see if I could push that file onto the phone. I just did a self-test on the 5410 I connected to the R6.1(22) machine and it came up with the following info: REL:5.00, HWT:32H, HWV:1, and FWV:5. Does this mean that the phone is at the correct BIN release to ship to site and plug into the 4.0(14) machine? The phone came up immediately without any sort of firmware download, so I'm skeptical that it worked.
If the answer is D: none of the above, what do you suggest? I have quite a few sites with R4.0 or R4.1 machines, and I'll have to send other 5410s in the future, so I'd rather figure out a working approach ahead of time.
Thanks in advance for your help.
When replacing 5410 phones, they get stuck on the "Please Wait" since they can't find a server to upgrade/downgrade their BIN file. I've had the tech in the field try the following:
-Change the TFTP server to the LAN 1 address, which works occasionally
-Add the ALLOW_5410_UPGRADES source code to the NoUser user, which so far hasn't worked
I was going to have the tech change the working directly to his laptop and set it as the TFTP server, but he's got a much later release on his laptop. I do have remote access to these systems, and available phones in my lab that I could try and pre-program with the correct BIN files and then ship to site, but I have a few questions:
1 - the laptop I connect remotely with has a much newer release of Manager software on it, but I do have the R4.1 software installed on a USB drive. Could I plug the USB drive into the laptop, change the working directory and Binary directory to the USB drive Manger folder, and then try either the ALLOW_5410_UPGRADE approach or change the TFTP server to the PC LAN Address?
2 - if I try to downgrade the firmware to the proper BIN file in the lab and then ship, what's the easiest way to do that? I don't have any v1 Control Units here, but I do have an R6.1(22) one available. The BIN file for the 5410 in that is R6, but I also put the R5 BIN file in there to see if I could push that file onto the phone. I just did a self-test on the 5410 I connected to the R6.1(22) machine and it came up with the following info: REL:5.00, HWT:32H, HWV:1, and FWV:5. Does this mean that the phone is at the correct BIN release to ship to site and plug into the 4.0(14) machine? The phone came up immediately without any sort of firmware download, so I'm skeptical that it worked.
If the answer is D: none of the above, what do you suggest? I have quite a few sites with R4.0 or R4.1 machines, and I'll have to send other 5410s in the future, so I'd rather figure out a working approach ahead of time.
Thanks in advance for your help.