Reset admin password E129 1

[lizarazo]

Hello friends, I have a problem resetting the admin password on the E129 phone. From what I've researched, to do this, it's necessary to upload the cfg.xml file to the HTTP server (which in this case would be the IPO itself). I also configured this cfg file to include the phone's MAC address, and according to the monitor, the error that appears is a 404 code:

116421897mS HTTP: 10.5.2.139(47654)-(80) HTTPSession (Total = 2)
116421900mS HTTP: 10.5.2.139(47654)-(80) HTTPSession: Operational
116422041mS HTTP: Rx Src: 10.5.2.139(47654)-(80)
GET /j100settings.txt/cfg000b828a048b HTTP/1.0
User-Agent: Avaya Model HW E129 SW 1.25.2.26 DevId 000b828a048b
Accept: */*
Host: 10.5.1.5
Connection: Keep-Alive
116422041mS HTTP: 10.5.2.139(47654)-(80) HTTPServerSessionIO: stCreationCallback(7) public IP=10.5.2.139 private IP=Not set
116422042mS HTTP: 10.5.2.139(47654) HTTPEmbeddedFileServerSessionIO: stCreationCallback
116422042mS HTTP: 10.5.2.139(47654) HTTPEmbeddedFileServerSessionIO this f18c6080 session f19d8650
116422042mS HTTP: 10.5.2.139(47654) HTTPEmbeddedFileServerSessionIO: SetState Schedule
116422045mS HTTP: 10.5.2.139(47654) HTTPEmbeddedFileServerSessionIO: SetState WaitForServiceResponse
116422065mS TFTP Download: Upgrader: Upgrade is not in Progress
116422261mS Ping Pong: WebSocket 10.5.2.157(59422)|mtcti: Received Ping
116422262mS Ping Pong: WebSocket 10.5.2.157(59422)|mtcti: Sending Pong
116422327mS HTTP: 10.5.2.139(47654) HTTPEmbeddedFileServerSessionIO: DisconnectIndication reason 2 code 4
116422327mS HTTP: 10.5.2.139(47654)-(80) HTTPSession: SendErrorResponse Code: 404, Entity: Embedded File Server File Does Not Exist
116422328mS HTTP: 10.5.2.139(47654) HTTPEmbeddedFileServerSessionIO: SetState Disconnect
116422328mS HTTP: 10.5.2.139(47654)-(80) HTTPServerSessionIO: SetState GracefulClose
116422331mS HTTP: Tx Dest: 10.5.2.139(47654)-(80)
HTTP/1.0 404 Not Found
Date: Wed, 12 Feb 2025 18:30:15 GMT
Server: IPOffice/
X-Frame-Options: DENY
X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
X-Robots-Tag: noindex, nofollow
Content-Type: text/plain
Content-Length: 40

From what I see in the Monitor, the problem is that it is making the GET request to a URL that does not exist on my IP Office (GET /j100settings.txt/cfg000b828a048b). Who generates this path? The phone or the system? And is there a way to fix this? Has anyone been able to reset the password of an E129 using this .xml file?

Thanks.

 

[sizbut]

E129 - A phone so bad it made people appreciate the J129 as at least being less evil.

I'd start by rerunning that process and letting the trace just keep running. Sometimes Avaya phones will run through a whole series of different requests as they try different methods of getting configuration settings. Having failed to get a response for /j100settings.txt/cfg000b828a048b it may have then asked for something else.

Officially E129 hasn't been supported for a long time, some if you look in the IP Office documentation set on support.avaya.com, you'll may have to go back to something like IP Office 10.0 or even older.