jamesarbrown
IS-IT--Management
We have a K175 here and its locked to its previous owner admin password.
The problem is that its trying to reach their 46xxsettings.xml file server instead of the IPO one coughed up on DHCP 242 code and until it has that file, it wont know a new admin password
Steps Taken
Tried default password 27238
Tried to CNAME the fileserver.xyz.co.uk (grabbed from config verifier on phone) via a spoof DNS record (which works in a browser and brings up the self generated 46xxsettings.txt and checked thats the DNS the phone uses), but no luck, but could be they have used https and the phone is unhappy with the IPO self cert.
Tried to move the DHCP to the IPO for that vlan (and that is working as tested with a B179 SIP phone and my PC), to 100% ensure that the DHCP 242 Option is being (hopefully) sent exactly as Avaya want it.
I also did check the 46xx... and it does have SET ADMIN_PASSWORD xxxxxxx in there, but we already know thats only going to work if it will pickup the file and it is not.
The problem is that its trying to reach their 46xxsettings.xml file server instead of the IPO one coughed up on DHCP 242 code and until it has that file, it wont know a new admin password
Steps Taken
Tried default password 27238
Tried to CNAME the fileserver.xyz.co.uk (grabbed from config verifier on phone) via a spoof DNS record (which works in a browser and brings up the self generated 46xxsettings.txt and checked thats the DNS the phone uses), but no luck, but could be they have used https and the phone is unhappy with the IPO self cert.
Tried to move the DHCP to the IPO for that vlan (and that is working as tested with a B179 SIP phone and my PC), to 100% ensure that the DHCP 242 Option is being (hopefully) sent exactly as Avaya want it.
I also did check the 46xx... and it does have SET ADMIN_PASSWORD xxxxxxx in there, but we already know thats only going to work if it will pickup the file and it is not.