IP Phone 4625SW Reboot Loop

[JW66]

I have several 4625SWs that have been unused for a while. I'm trying to get them working with IP Office. I've CLEARed the settings and provide all settings thru DHCP. This seems to work just fine. They boot showing a25d01a2_9_1.bin, then they connect to our TFTP server and download 46XXUPDATE.SCR and 46XXSETTINGS.TXT. Then, they reboot without connecting to the IP Office (as far as I can tell). No H.323 info shows in Monitor. I get no error messages. Then, the cycle repeats. I'm not prompted to enter the extension and password.

The TFTP server is a linux server. Files are getting accessed and downloaded by the IP phones without any problem.

I have a few 4625s that boot and connect OK without issue.

Any suggestions for what to try next?

Thanks -- JW

 

[Okkie26]

Is option 176 available and setup properly in the DHCP server?

 

[JW66]

Yep. Opt 176 is there. I’m specifying a sub folder for the avaya files and I see the phones getting the files from the logs. Also see the file transfers going over and the phone shows the right size for the update and settings files.

After downloading the files, the leds on speaker, headset, mute cycles 2-3 times and then the phone resets.

I’m monitoring traffic from the phones and after the tftp download there’s nothing. Weird, huh?

 

[bahmonkeys]

Use the phone systems memory card.

Make sure a25d01a2_9_1.bin is on this memory card

46xxsettings.txt is not needed so please delete.

If the phone system is old and doesn't have a memory card. Use the manager for TFTP, which you should know how to use instead of a Linux server

 

[JW66]

OK. I'm using a 406v2 (Yep I've been using IPO since v1.8 days).

There is no card on the 406v2 as far as I know BUT it does serve TFTP--the files are AutoCreated from what I can gather from the Monitor Log. In any case, after changing the DHCP settings to point to the 406v2, I can confirm that the IP phones get the files from there --- and they still don't work.

So, I served the files (via TFTP, of course) from the PC running the Manager Application. Mare sute the TFTP/BOOTP checkbox was selected from the Preferences menu. Changed the DHCP settings to point there. And, I can confirm that the files are downloaded from the Manager PC --- and, no change. The IP Phones still don't work.

I have stripped the 46xxsettings.txt to only a few settings that are mostly defaults. I agree that the file is not really needed. But, I keep it in place to remind me of future changes I'll need to make.

I'm able to monitor TCP/UDP requests from each IP Phone. I can definitely see the TFTP requests and responses, but nothing else after the tiny (1.5K) settings file is downloaded.

This is just weirdly perplexing. Surely, someone has 4625SW's working on IPO.

 

[JW66]

Note, I used TFTP command-line to GET the files from BOTH the IPO and the MANAGER server. They contained exactly what I expected them to.

 

[JW66]

Another thing I noticed...

When using MANAGER to provide TFTP, I receive the following in the LOG for each IP Phone...

Thursday, February 28, 2019 6:04:39 PM : Received BOOTP request for XXXXXXXX8cb2, 0.0.0.0:68, unable to process
​

As far as I know, there is no BOOTP requirement for the 4625. Or is there???

 

[bahmonkeys]

Delete your custom 46xxsettings.txt this is your issue. Leave this auto-generated by the phone system. This will point it to the phone system cert.

Reboot the system and it will work

 

[JW66]

Ok. Tried that, again, and it still doesn’t work.

The ones that work download the upgrade script then the settings script then connect to port 1719 on the IPO.

The ones that fail do everything but never contact the IPO.

 

[Westi]

IP 406 ? really

Did you bow before you plug them in - honour your elders and stuff

It has no 46xxsettings.txt file I think (I think I remember) so make sure that you have one on your TFPT server that is provided otherwise the phones will look for it over and over again. If you use Manager it has to probably be added manually to it.

Test the 46xxsettings.txt file by downloading it from your server.


Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter

 

[JW66]

Thanks Westi. All of that already done/tried.

Let me recap...

I have several 4625sw IP Phones that work just fine.

Plugged right next to them on the same switch, same network, same dhcp, I have several 4625sw IP Phones that do not work.

The difference is that AFTER downloading the 46xxupgrade.scr file and the 46xxsettings.txt file, the working phones connect to the 406v2 on port 1719. The non-working phones do not. This is what I’m trying to fix.

There is an app note from avaya that describes something similar where the 46xx MAC address gets corrupted. However, if thats the problem I was having, I wouldn’t see the dhcp registration with the correct MAC address for each phone. Also, I doubt dhcp works without a MAC address.

I don’t mind trying low-probability suggestions, but changing dhcp or tftp servers isn’t the problem. There is definitely something failing on with these phones that is working just fine on the working ones.

 

[Westi]

You could try and use a different release on a different system so that they upgrade and then downgrade (or the other way around) so that the firmware gets re-flashed.
But TBH I am not sure that this will work.

sounds more like an exorcism is needed.

Joe W.

FHandw, ACSS (SME)


"This is the end of the world, make sure to buy your T-shirt before it is too late"
Original expression of my daughter