J100 series firmware update issues 2

[BerettaGuy]

I've read through multiple topics on here regarding this process and I just can't seem to get this to work.

We just got a IP Office system installed, in a rush since our old Inter-Tel system died, and now I'm just trying to get/keep these devices updated and I can't see to figure out how to do this.

My main goal is to get at least ONE J179 phone up to version SIP 4.1 so it will support joining it to a hidden SSID WIFI. Right now all the phones I have are on 4.0.8 and I've attempted to upload a J100Supdate.txt file and the FW_S_J179_R4_0_9_0_4.bin file to the SD card via embedded file management but when restarting a currently connected phone I just get a "Software update failed" error message.

There was no 46xxsettings.txt file in the primary directory and I never configured one for any specific settings... I don't know if that missing is the cause of this, and I don't even know what I would put there since I'm not using it for configuration.

IP Office version is 11.1.0.0.0 Build 237 so GA release of 11.1.

This is my first time using an Avaya phone system and I'll say the installer was more versed in working with the 9500 series and 9600 series phones... the J100 series phones are new to him. The installer was also not 100% on going to the latest FP3 or even FP2 SP4.

*Edit, I'm able to browse to

http://serverIP/46xxsettings.txt

and I can see the autogenerated file, but I was under the impression that this would reside in the primary directory where you could edit it... Or do I need to take what I see on that URL and then save it to a TXT file and put it in the primary directory? Sorry for the newb questions here.

 

[nnaarrnn]

Correct- You'd have to copy the text and create your own 46xxsettings.txt file, then upload it to the primary directory.

Make sure the language file (.xml file for your language AND for your model phone) is also uploaded in that directory, as well as the "av_prca_pem.txt" file, but change the file extension so it becomes an actual certificate. (I don't recall off the top of my head which encoding or filetype it should be)

 

[sizbut]

Correct- You'd have to copy the text and create your own 46xxsettings.txt file, then upload it to the primary directory." - DO NOT DO THAT, for one it's not necessary as all the firmware instructions for the J100 phones come from the J100Supgrade.txt file.

Personally I wouldn't do this at all, each release of IP Office comes with and installs the various releases of phone firmware that it has been tested with and supports. If you want the latest IP Office supported J100 firmware, upgrade the IP Office. Your GA release of 11.1 is over 3 and half years old. The IP Office service packs since August 2022 have included J100 R4.0.10.3.2 firmware.

If you still really want to though, you need to see what your system is doing. Use a browser to request the J100Supgrade.txt file and see if it matches what you expect. The system also auto-generates a J100Supgrade.txt file for the supported J100 release if no physical file is present on the system, so you need to see which one is being served and the firmware listed in it.

Check the configuration, have a Phone File Server and HTTP Redirection settings been changed to tell the phones to get firmware from somewhere other than the IP Office's own System/Primary folder?

And then finally watch what happens in Monitor. Enable Services | FileSys in the trace options, you'll be able to see the file requests from the phone as it restarts and what happens in response to each request.



Stuck in a never ending cycle of file copying.

 

[sizbut]

... if you were to twist a developer's arm, they would tell you that the auto-generated files are ephemeral files. That is, the exist only for the duration of the request (if you are really sad like me, you can watch the file being supplied in Monitor and then being deleted immediately afterwards). If you must supply the phones with additional or different settings, use a 46xxspecials.txt file.

You can go fully free-style if you want and do things like add your own upgrade files and commands for GET myfile.txt in the upgrade file and all sorts of other things, but remember that you're just creating a support mystery (misery) for the next person who has to unravel that to understand it. So just use the main files (auto-generated 46xxsettings.txt, and 46xxspecials.txt if needed)

Stuck in a never ending cycle of file copying.

 

[BerettaGuy]

Personally I wouldn't do this at all, each release of IP Office comes with and installs the various releases of phone firmware that it has been tested with and supports. If you want the latest IP Office supported J100 firmware, upgrade the IP Office. Your GA release of 11.1 is over 3 and half years old. The IP Office service packs since August 2022 have included J100 R4.0.10.3.2 firmware.

I 100% understand where you are coming from here, but lets accomplish one thing at a time. I'm new to this system and it was just finished being installed maybe 3 weeks ago after a being without a phone system for over a month, I don't want to interrupt services for a FP update quite yet. I also don't want to introduce more changes going from GA to FP3 when that itself will not solve the root issue I'm having, they are just starting to grasp how to use this system as is. Yes they are horrible planners here and don't listen to my recommendations when populating their risk register which is why we were down for so long.

The only thing that I currently need to do is join a phone to a hidden Wi-Fi network and you can not do that unless the phone is running SIP 4.1 so even going to 4.0.10 wont accomplish what I need it to. In addition to that my phones are all at 4.0.8 but one that is at 4.0.4 (not sure why one had older firmware) but from what I've read I need to go to 4.0.9 before I can go to 4.0.10 or higher so that is why I'm testing that process out now. It also helps me understand how to push just firmware to phones if necessary vs having to do a full system upgrade, or waiting for a FP or SP to contain the newer J100 firmware that I'm waiting for. All the documentation states that the SIP 4.1 firmware will run on a 11.1 GA system so I don't see there being any issue in just updating the phones at this time. Once I get my feet wet then maybe I'll take on a FP or two and get the system OS current. I also don't want to step on my installers toes quite yet until I've obtained enough information from him to administer this system myself, as well as not cause a service call due to my fault attempting an upgrade when he did not recommend it, I doubt that would be covered by his 3yr install warranty.

Answering your other questions, the phones are out of the box installed and only the HTTP and HTTPS server fields were populated with the IP Office address, they were then connected up to our system and assigned extensions to them.

I did a browser request for the J100Supgrade.txt file and it is coming up with the file that is included with the 4.0.9 firmware which is what I uploaded to the system yesterday. The only thing I'm currently lacking from the previous reply is the av_prca_pem.txt file inn PEM extension, but I didn't think that was necessary.

IF $MODEL4 SEQ J129 GOTO J129_SW
IF $MODEL4 SEQ J139 GOTO J139_SW
IF $MODEL4 SEQ J159 GOTO J159_SW
IF $MODEL4 SEQ J169 GOTO J169_SW
IF $MODEL4 SEQ J179 GOTO J179_SW
IF $MODEL4 SEQ J189 GOTO J189_SW

GOTO GETSET

# J129_SW
SET APPNAME FW_S_J129_R4_0_9_0_4.bin
GOTO GETSET

# J139_SW
SET APPNAME FW_S_J139_R4_0_9_0_4.bin
GOTO GETSET

# J159_SW
SET APPNAME FW_S_J159_R4_0_9_0_4.bin
GOTO GETSET

# J169_SW
SET APPNAME FW_S_J169_R4_0_9_0_4.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_16.bin
GOTO GETSET

# J179_SW
SET APPNAME FW_S_J179_R4_0_9_0_4.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_16.bin
GOTO GETSET

# J189_SW
SET APPNAME FW_S_J189_R4_0_9_0_4.bin
SET JEM24_APPNAME FW_JEM24_R1_0_1_0_16.bin
GOTO GETSET

# GETSET
GET 46xxsettings.txt

I will run a system monitor today and see what I can capture during a phone restart.

... if you were to twist a developer's arm, they would tell you that the auto-generated files are ephemeral files. That is, the exist only for the duration of the request (if you are really sad like me, you can watch the file being supplied in Monitor and then being deleted immediately afterwards). If you must supply the phones with additional or different settings, use a 46xxspecials.txt file.

Thank you for the better explanation on the 46xxsettings.txt file... I just read about it everywhere but no where does it state that if you are not pushing out custom settings or need to modify the phones upon connection that you do not even need to generate or worry about this file. There is very little info on it out there.

 

[BerettaGuy]

I'm not sure what you need to see from the monitor but I saw this during the reboot process when the phone was saying Software Update Failed. It's clearly seeing the request to do the 4.0.9 firmware, but there is a disconnect indication after it starts the sending process and I have no clue what that means.

 08:50:25   66341203mS PRN: Service Access Connection from x.x.x.x(20860) to Port 411
 08:50:25   66341238mS RES: Tue 15/8/2023 08:50:24 FreeMem=49835444 Heap=48746252(12) Cache=1089192 MemObjs=19197(Max 23751) CMMsg=7(10) ASN=0 Buff=5200 1358 1000 7442 5 Links=57663(58935) BTree=1251(2421) CB=6072 MCT=0 CPU=05.39% CPUStats=05.01%/1/5/1515
                       /14041/15115/00.03%/0/02.65% 
 08:50:25   66341238mS RES2: IP 500 V2A 11.1.0.0.0 build 237 Tasks=61 RTEngine=0 CMRTEngine=0 ExRTEngine=0 Timer=14+95 Poll=0 Ready=0 CMReady=0 CMQueue=0 VPNNQueue=0 Monitor=1 SSA=0 TCP=44(TLS=9 OFF=0) TAPI=0 Partner=0 ASC=1 SYS=MNTD OPT=UMNT SDSPD=2034
 08:50:25   66341238mS RES4: XML MemObjs=8 PoolMem=4748404(2) FreeMem=4736284(0) HeapUsed=0
 08:50:25   66341239mS RES5: CLog MemObjs=973 FreePoolMem(Objs)=7112(127) TotalMem=61600 StringsTotalMem=103600
 08:50:26   66342159mS FILESYS: (74) FilesysReader(Read): A:\system\primary\J100Supgrade.txt (AutoGenerate: Enabled) (Total = 1)
 08:50:26   66342159mS FILESYS: (74) FilesysReader: LastStateDuration(1) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\J100Supgrade.txt
 08:50:26   66342160mS FILESYS: FileCache(f18249fc): Created Cache: A:\system\primary\J100Supgrade.txt (Total = 1)
 08:50:26   66342160mS FILESYS: (74) FilesysReader: Using Cache: A:\system\primary\J100Supgrade.txt (Usage = 1)
 08:50:26   66342160mS FILESYS: (74) FilesysReader: LastStateDuration(1) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\J100Supgrade.txt
 08:50:26   66342164mS FILESYS: (74) FilesysReader: LastStateDuration(4) SetState(FS_OPEN->FS_SENDING): A:\system\primary\J100Supgrade.txt
 08:50:26   66342164mS FILESYS: (74) FilesysReader: Send File: A:\system\primary\J100Supgrade.txt
 08:50:26   66342204mS FILESYS: (74) FilesysReader: SendConnectIndication: A:\system\primary\J100Supgrade.txt Size(731) Attributes(32) TotalSize(731) Range(1)
 08:50:26   66342230mS FILESYS: (74) FilesysReader: Percent(100): A:\system\primary\J100Supgrade.txt
 08:50:26   66342230mS FILESYS: (74) FilesysReader: LastStateDuration(66) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\J100Supgrade.txt
 08:50:26   66342232mS FILESYS: (74) FilesysReader: Master Cache Complete: A:\system\primary\J100Supgrade.txt (Usage = 0)
 08:50:26   66342232mS FILESYS: (74) ~FilesysReader: A:\system\primary\J100Supgrade.txt Duration: 74ms (Total = 0)
 08:50:26   66342265mS FILESYS: (75) FilesysReader(Read): A:\system\primary\46xxsettings.txt (AutoGenerate: Enabled) (Total = 1)
 08:50:26   66342265mS FILESYS: (75) FilesysReader: LastStateDuration(1) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\46xxsettings.txt
 08:50:26   66342266mS FILESYS: FileCache(f18243dc): Created Cache: A:\system\primary\46xxsettings.txt (Total = 2)
 08:50:26   66342266mS FILESYS: (75) FilesysReader: Using Cache: A:\system\primary\46xxsettings.txt (Usage = 1)
 08:50:26   66342266mS FILESYS: (75) FilesysReader: LastStateDuration(1) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\46xxsettings.txt
 08:50:26   66342458mS FILESYS: (75) FilesysReader: Master Cache Freed for Virtual File: A:\system\primary\46xxsettings.txt (Usage = 0)
 08:50:26   66342458mS FILESYS: (75) FilesysReader: LastStateDuration(192) SetState(FS_OPEN->FS_SENDING): A:\system\primary\46xxsettings.txt
 08:50:26   66342458mS FILESYS: (75) FilesysReader: Send File: A:\system\primary\46xxsettings.txt
 08:50:26   66342458mS FILESYS: (75) FilesysReader: SendConnectIndication: A:\system\primary\46xxsettings.txt Size(14263) Attributes(0) TotalSize(14263) Range(1)
 08:50:26   66342459mS FILESYS: (75) FilesysReader: Percent(10): A:\system\primary\46xxsettings.txt
 08:50:26   66342460mS FILESYS: FileCache(f18243dc): Deleted Cache: A:\system\primary\46xxsettings.txt (Total = 1)
 08:50:26   66342481mS FILESYS: (75) FilesysReader: Percent(100): A:\system\primary\46xxsettings.txt
 08:50:26   66342482mS FILESYS: (75) FilesysReader: LastStateDuration(24) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\46xxsettings.txt
 08:50:26   66342484mS FILESYS: (75) ~FilesysReader: A:\system\primary\46xxsettings.txt Duration: 220ms (Total = 0)
 08:50:26   66342592mS FILESYS: (76) FilesysReader(Read): A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml (AutoGenerate: Enabled) (Total = 1)
 08:50:26   66342592mS FILESYS: (76) FilesysReader: LastStateDuration(0) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342594mS FILESYS: FileCache(f18243dc): Created Cache: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml (Total = 2)
 08:50:26   66342594mS FILESYS: (76) FilesysReader: Using Cache: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml (Usage = 1)
 08:50:26   66342594mS FILESYS: (76) FilesysReader: LastStateDuration(2) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342598mS FILESYS: (76) FilesysReader: LastStateDuration(4) SetState(FS_OPEN->FS_SENDING): A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342599mS FILESYS: (76) FilesysReader: Send File: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342668mS FILESYS: (76) FilesysReader: SendConnectIndication: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml Size(206283) Attributes(32) TotalSize(206283) Range(1)
 08:50:26   66342669mS FILESYS: (76) FilesysReader: DisconnectIndication reason 5 code 0: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342688mS FILESYS: (76) FilesysReader: DisconnectIndication reason 4 code 0: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342688mS FILESYS: (76) FilesysReader: LastStateDuration(90) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342698mS FILESYS: (76) FilesysReader: Master Cache Failed: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml (Usage = 0)
 08:50:26   66342698mS FILESYS: (76) FilesysReader: Incomplete Cache(f18243dc) Keep for file details: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml
 08:50:26   66342698mS FILESYS: (76) ~FilesysReader: A:\system\primary\Mlf_J169_J179_LatinAmericanSpanish.xml Duration: 106ms (Total = 0)
 08:50:27   66343524mS FILESYS: (77) FilesysReader(Read): A:\system\primary\Mlf_J169_J179_CanadianFrench.xml (AutoGenerate: Enabled) (Total = 1)
 08:50:27   66343524mS FILESYS: (77) FilesysReader: LastStateDuration(0) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343526mS FILESYS: FileCache(f1823404): Created Cache: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml (Total = 3)
 08:50:27   66343526mS FILESYS: (77) FilesysReader: Using Cache: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml (Usage = 1)
 08:50:27   66343526mS FILESYS: (77) FilesysReader: LastStateDuration(2) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343530mS FILESYS: (77) FilesysReader: LastStateDuration(4) SetState(FS_OPEN->FS_SENDING): A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343530mS FILESYS: (77) FilesysReader: Send File: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343594mS FILESYS: (77) FilesysReader: SendConnectIndication: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml Size(207669) Attributes(32) TotalSize(207669) Range(1)
 08:50:27   66343594mS FILESYS: (77) FilesysReader: DisconnectIndication reason 5 code 0: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343614mS FILESYS: (77) FilesysReader: DisconnectIndication reason 4 code 0: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343615mS FILESYS: (77) FilesysReader: LastStateDuration(84) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343623mS FILESYS: (77) FilesysReader: Master Cache Failed: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml (Usage = 0)
 08:50:27   66343623mS FILESYS: (77) FilesysReader: Incomplete Cache(f1823404) Keep for file details: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml
 08:50:27   66343624mS FILESYS: (77) ~FilesysReader: A:\system\primary\Mlf_J169_J179_CanadianFrench.xml Duration: 100ms (Total = 0)
 08:50:27   66344454mS FILESYS: (78) FilesysReader(Read): A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml (AutoGenerate: Enabled) (Total = 1)
 08:50:27   66344454mS FILESYS: (78) FilesysReader: LastStateDuration(1) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344456mS FILESYS: FileCache(f1822f40): Created Cache: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml (Total = 4)
 08:50:27   66344456mS FILESYS: (78) FilesysReader: Using Cache: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml (Usage = 1)
 08:50:27   66344456mS FILESYS: (78) FilesysReader: LastStateDuration(2) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344460mS FILESYS: (78) FilesysReader: LastStateDuration(4) SetState(FS_OPEN->FS_SENDING): A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344460mS FILESYS: (78) FilesysReader: Send File: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344522mS FILESYS: (78) FilesysReader: SendConnectIndication: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml Size(205113) Attributes(32) TotalSize(205113) Range(1)
 08:50:27   66344522mS FILESYS: (78) FilesysReader: DisconnectIndication reason 5 code 0: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344544mS FILESYS: (78) FilesysReader: DisconnectIndication reason 4 code 0: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344544mS FILESYS: (78) FilesysReader: LastStateDuration(84) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344551mS FILESYS: (78) FilesysReader: Master Cache Failed: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml (Usage = 0)
 08:50:27   66344551mS FILESYS: (78) FilesysReader: Incomplete Cache(f1822f40) Keep for file details: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml
 08:50:27   66344552mS FILESYS: (78) ~FilesysReader: A:\system\primary\Mlf_J169_J179_BrazilianPortuguese.xml Duration: 99ms (Total = 0)
 08:50:28   66345399mS FILESYS: (79) FilesysReader(Read): A:\system\primary\Mlf_J169_J179_Italian.xml (AutoGenerate: Enabled) (Total = 1)
 08:50:28   66345399mS FILESYS: (79) FilesysReader: LastStateDuration(1) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345401mS FILESYS: FileCache(f1822c40): Created Cache: A:\system\primary\Mlf_J169_J179_Italian.xml (Total = 5)
 08:50:28   66345401mS FILESYS: (79) FilesysReader: Using Cache: A:\system\primary\Mlf_J169_J179_Italian.xml (Usage = 1)
 08:50:28   66345401mS FILESYS: (79) FilesysReader: LastStateDuration(2) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345405mS FILESYS: (79) FilesysReader: LastStateDuration(4) SetState(FS_OPEN->FS_SENDING): A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345405mS FILESYS: (79) FilesysReader: Send File: A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345466mS FILESYS: (79) FilesysReader: SendConnectIndication: A:\system\primary\Mlf_J169_J179_Italian.xml Size(204409) Attributes(32) TotalSize(204409) Range(1)
 08:50:28   66345466mS FILESYS: (79) FilesysReader: DisconnectIndication reason 5 code 0: A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345485mS FILESYS: (79) FilesysReader: DisconnectIndication reason 4 code 0: A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345485mS FILESYS: (79) FilesysReader: LastStateDuration(80) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345495mS FILESYS: (79) FilesysReader: Master Cache Failed: A:\system\primary\Mlf_J169_J179_Italian.xml (Usage = 0)
 08:50:28   66345495mS FILESYS: (79) FilesysReader: Incomplete Cache(f1822c40) Keep for file details: A:\system\primary\Mlf_J169_J179_Italian.xml
 08:50:28   66345496mS FILESYS: (79) ~FilesysReader: A:\system\primary\Mlf_J169_J179_Italian.xml Duration: 98ms (Total = 0)

 08:50:46   66362508mS PRN: Monitor Status  IP 500 V2A 11.1.0.0.0 build 237
 08:50:46   66362508mS PRN: LAW=U PRI=0, BRI=0, ALOG=12, VCOMP=52, MDM=0, WAN=0, MODU=1 LANM=0 CkSRC=0 VMAIL=1(VER=2 TYP=3) 1-X=0 CALLS=0(TOT=102)
 08:50:46   66362669mS PRN: Service Access Connection from x.x.x.x(40260) to Port 8411
 08:50:46   66362676mS FILESYS: (81) FilesysReader(Read): A:\system\primary\FW_S_J179_R4_0_9_0_4.bin (AutoGenerate: Enabled) (Total = 1)
 08:50:46   66362676mS FILESYS: (81) FilesysReader: LastStateDuration(0) SetState(FS_UNKNOWN->FS_BEGIN): A:\system\primary\FW_S_J179_R4_0_9_0_4.bin
 08:50:46   66362678mS FILESYS: FileCache(f181dab8): Created Cache: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin (Total = 6)
 08:50:46   66362678mS FILESYS: (81) FilesysReader: Using Cache: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin (Usage = 1)
 08:50:46   66362678mS FILESYS: (81) FilesysReader: LastStateDuration(2) SetState(FS_BEGIN->FS_OPEN): A:\system\primary\FW_S_J179_R4_0_9_0_4.bin
 08:50:46   66362697mS FILESYS: (81) FilesysReader: LastStateDuration(19) SetState(FS_OPEN->FS_SENDING): A:\system\primary\FW_S_J179_R4_0_9_0_4.bin
 08:50:46   66362698mS FILESYS: (81) FilesysReader: Send File: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin
 08:50:46   66362699mS FILESYS: (81) FilesysReader: SendConnectIndication: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin Size(59357476) Attributes(32) TotalSize(59357476) Range(1)
 08:50:47   66363205mS FILESYS: (81) FilesysReader: DisconnectIndication reason 4 code 0: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin
 08:50:47   66363205mS FILESYS: (81) FilesysReader: LastStateDuration(508) SetState(FS_SENDING->FS_COMPLETE): A:\system\primary\FW_S_J179_R4_0_9_0_4.bin
 08:50:47   66363228mS FILESYS: (81) FilesysReader: Master Cache Failed: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin (Usage = 0)
 08:50:47   66363229mS FILESYS: (81) ~FilesysReader: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin Duration: 553ms (Total = 0)
 08:50:47   66363230mS FILESYS: FileCache(f181dab8): Deleted Cache: A:\system\primary\FW_S_J179_R4_0_9_0_4.bin (Total = 5)

 

[nnaarrnn]

Lots of replies here, but I wanted to notate that my systems have NEVER generated a J100Supdate.txt file, and also notate that there are firmware releases newer than the firmware included in the most recent IPO firmware (at each time of release.

I also wasn't suggesting that OP upload a 46xxsettings file, just that they'd have to. I was directly answering their question.

 

[BerettaGuy]

I also wasn't suggesting that OP upload a 46xxsettings file, just that they'd have to. I was directly answering their question.

But is it not true that I only need to upload that if I'm using it to apply specific settings that do not get autogenerated? I don't have any special settings that I need enabled to my knowledge, or different than the autogenerated file from what I can see in it.

Simply said, leaving my system to autogenerate a 46xxSettings.txt file should not be preventing me from upgrading the firmware on the phone correct?

My system also did not have an autogenerated J100SUpdate.txt file, that was always present in the Primary directory from the start, I've just overwritten it with the newer one included with the phone firmware files.

 

[sizbut]

@nnaarrnn - What you said was "Correct- You'd have to copy the text and create your own 46xxsettings.txt file, then upload it to the primary directory." - So yes, you were suggesting that the OP upload a 46xxsettings.txt file. And its still 100% wrong.

I also did not say that people couldn't upgrade to a later version of J100 firmware, I just set out some of reasons why its not advisable to do that rather than using the version tested with the IP Office release.




Stuck in a never ending cycle of file copying.

 

[sizbut]

@BerettaGuy - I'm confused.

You said there was no 46xxsettings.txt file originally. Now you are saying that there was one, but you replaced with the one that came with the J100 firmware. And that all kind of worries me as there is no 46xxsettings.txt file included in any of the sets of J100 phone firmware. Where did that file come from and what is it?

Stuck in a never ending cycle of file copying.

 

[BerettaGuy]

@sizbut - Right now there is no physical 46xxsettings.txt in the primary directory on the IP Office system storage/SD card. However if you go go the

http://serverIP/46xxsettings.txt

address it will auto generate one. As far as the J100Supgrade.txt file, that has always physically existed in the primary directory, and when visiting the

http://serverIP/J100Supdate.txt

address it was accurate to whichever firmware I had uploaded.

You said there was no 46xxsettings.txt file originally. Now you are saying that there was one, but you replaced with the one that came with the J100 firmware.

I never stated that I created, or uploaded a 46xxsettings.txt file, I was asking if that was necessary for the update to work.

I said

My system also did not have an autogenerated J100SUpdate.txt file, that was always present in the Primary directory from the start, I've just overwritten it with the newer one included with the phone firmware files

For example out of the box the J100S file stated FW_S_J179_R4_0_4_0_10.bin, and when I uploaded the 4.0.9 firmware the J100S file then stated FW_S_J179_R4_0_9_0_4.bin. What I meant by that was never an autogenerated file is the fact that there has always been a physical file in the primary directory, and if I'm understanding the system correctly, if it's there physically it will not autogenerate one, and if it's missing it will autogenerate one when requested.

When you download the zip files from Avaya for the firmware none of them contain a 46xxsettings.txt file. I can't see how they could include that since it would contain specific values that are unique to your install. The most that they could include is a template for it, but they don't even include that. They do have a J100Supdate.txt file though... I would upload that txt file, with all of the .bin files, and all of the language files, even though I only have 19 J179's and 1 J189 phone, and 2 JEM24's.

I know there is discussions out there about certificates and such, but I have been leaving this off the table since we do not have TLS enabled. I don't know if that's a factor or not, but I would have to assume if it was there should be an error stating that.

I understand you hesitance to upgrading to firmware not boxed with the IPO system however that would leave a wireless phone completely off the table for me. I need SIP 4.1 to connect to my corporate Wi-Fi. As well as every document you read about newly released J100S firmware it states this right in the beginning of the readme, "This release supersedes all previous Avaya J100 Series SIP software releases. Avaya recommends that all customers using Avaya J100 Series SIP software upgrade to this version at their earliest convenience.

 

[sizbut]

I'll calm down now. Some misunderstanding of when you were referring to the auto-generated files and non-auto generated ones.

Avaya might say "Avaya recommends that all customers using Avaya J100 Series SIP software upgrade to this version at their earliest convenience." but that's written by a software developer who has probably never seen an IP Office in their life and doesn't have to look after multiple real customer system. If you were to follow that advice, you would be doing phone firmware upgrades every 2 to 3 months (looking at actual releases; there were 8 in 2020, 6 in 2021 and 5 in 2022). You have to remember that Avaya comes from a background of huge enterprise telephone systems with permanent support staff and centralize systems to support doing something like that. In reality, for reseller supporting multiple small systems at different disparate customer sites, most people interpret "at their earliest convenience" as - only do it if you have an actual customer issue and the release notes mentions a fix for that issue, or if its part of an IP Office upgrade as that will have involved developers who know IP Office doing a full round of testing of the phones and IP Office.

But lets ignore the lumbering juggernaut that was Avaya and try to fix just doing one phone firmware upgrade.

I did look at your monitor postings but no clues as yet. The system appears to be providing firmware files on request quite happily at the start and only starts to fail later.

- Can I assume that the phone involved has been successfully connected on the older firmware prior to this?

- What does System Status (SSA) show about the System SD card in the back of the system? (Its size and the free space available - an itch I have that the system may be trying to use space on the card and finding it doesn't have enough after a few file operations. If so, recreating the card and starting again may help).

Stuck in a never ending cycle of file copying.

 

[BerettaGuy]

- Can I assume that the phone involved has been successfully connected on the older firmware prior to this?

Yes, I've also defaulted the phone and gone through the setup process again, for us that is to skip auto provisioning and enter in the IPO address into the HTTP and HTTPS fields. Phone then comes up fine to the login screen and will login to an extension. Of course it fails the software update on every reboot though.

- What does System Status (SSA) show about the System SD card in the back of the system? (Its size and the free space available - an itch I have that the system may be trying to use space on the card and finding it doesn't have enough after a few file operations. If so, recreating the card and starting again may help).

This install is only 3 weeks old and its all brand new hardware, the SD card is an 8GB and it is showing 38% In use, 5063MB free.

To add to this I've also tried to update the phone using the web portal on the device itself, and that would fail during the bin file upload and just reboot the phone. It's almost the same situation where the phone itself is refusing or can't take the update file for some reason. I have also rebooted multiple phones btw and none of them will update, they all fail during the reboot process so it's not limited to just one J179.

 

[gwebster]

The firmware files are signed. The phone needs the “pem” file to validate the signing and then install the new firmware.

 

[BerettaGuy]

The firmware files are signed. The phone needs the “pem” file to validate the signing and then install the new firmware.

Can you please explain what you mean by that?
There isn't a "pem" file in the firmware zip, however there is a certificate in a txt file. I've read some posts that say you need to change the extension to .pem and upload it so I'm assuming it doesn't need to be renamed or named anything specific?

I will try putting that file as a pem in the primary directory tomorrow unless I hear differently before then.

 

[gwebster]

The av_prca_pem.txt file. Upload it just the way it is.

 

[BerettaGuy]

Same issue persists... and I actually tried to load that certificate in two different ways. One as noted, untouched just upload to primary directory. I thought that sounded too good to be true and it was. Nothing changed after doing that. I then followed these instructions to import that certificate into the Trusted Certificate Store.

https://www.youtube.com/watch?v=yPTFRcDNyc0

I imported the Avaya Product Root CA, aka the contents of the av_prca_pem_2033.txt file. The trusted CA then showed up in the Certificates list as expected. I saved that config and rebooted a phone to test updates and the same Software updates failed message came across the screen. I then did a system reboot thinking maybe it needed that after a certificate addition, and once again Software update failed.

I still have the same monitor sequence/error as above as well with "DisconnectIndication reason 4 code 0"

On the phone in the network information > Upgrade Info > I can see the failed attempt to update to 4.0.8.0.14 from 4.0.8.0.13 and the reason code is 11.

Adding in an oddity... I changed nothing else after doing the above and then when I was changing some other settings, one being "Visually differentiate external call" and then adding my extension to a ring group, I clicked on Save and had the option to merge my changes and after doing that all of the IP phones restarted... They all attempted to do a software update as well and every one failed. I don't know what would have triggered all of them to reboot at once, but thankfully it's only 15 phones. Automatic update policy is disabled.

 

[BerettaGuy]

So if I setup an IIS instance (following this

https://www.youtube.com/watch?v=2VslkHW04gk&t=117s)

on a W10 machine and copy all the files from the firmware zip to the

http://wwwroot

directory the phone still fails to update, however it ends with a Reason code of 1 instead of the 11 when it's pointing to the IPO. I have yet to find what those reason codes even mean.

​

 

[sizbut]

Whilst your perseverance is to be admired, I have to go back to my first answer - just upgrade the IP Office to a more recent IP Office R11.x service or feature pack. You keep stating that you installed the system as new 3 week ago, but you did that using 3 years old software.

The J100 phones on my test rigs are running J100 R3.0.10.3.2 on IP Office R11.1.3. My IP Office's have been upgraded numerous time but never once have I had to manually fiddle with the J100 firmware files, they just upgrade in parallel with the IP Offices. Having looked, there is no av_prca_pem.txt file on my systems, the IP Office devs have clearly dealt with the firmware signing through a different path.

AND BURN THAT MANUAL 46XXSETTINGS.TXT FILE. It will be the source of future issues when you change something in the IP Office configuration and it doesn't get automatically reflected in the settings passed to the phones by an auto-generated settings file. If there are any must have settings file changes, put them in a separate 46xxspecial.txt file. You can even ask your system to auto-generate a specials file for you as a template by using your browser to request the file. [And delete the J100Supgrade.txt file too]

Stuck in a never ending cycle of file copying.

 

[BerettaGuy]

I will clarify one more time, I don't use or have a manual 46xxsettings file. I have been, and always let the phones use the autogenerated file when requested... All this talk of that file was just trying to figure out if it's needed at all since it's mentioned so many times when it comes to firmware upgrades.

I would also love for your solution to be the fix all, but keep in mind here, I had this system installed, "I" did not install it at 11.1, that's how it came. Sure I can overrule the installer but then there goes my relationship with them, I would prefer for them to determine the update needs to be applied before I just jump head first into it and potentially cause more billable issues. In addition to that 11.1 is boxed with 4.0.4 firmware and the out of the box J179's come with 4.0.8... From the start none of the phones have ever downgraded to the boxed firmware that was included with the 11.1 IPO. I only have one phone at 4.0.4 and to be honest I don't know if that happed when provisioning it, or if that phone came with 4.0.4 already on it.

I will be working with local tech support either today or Monday to resolve this issue, because even going to FP3 and if it would miraculously install 4.0.10 on my phones I'm still not where I need to be, I will still need to "manually fiddle" with the J100 firmware to get to 4.1. As well as when your at version 4.0.8 on a J100 it states in the read-me that you need to take the phone to 4.0.9 before going to 4.0.10 or newer so I would need to figure out which IPO has that release before I can just jump to FP3. Also if you delete your J100Supgrade.txt file then you are locked into an autogenerated one, and only getting the boxed firmware with the IPO you're running.... once again will not get me to 4.1 making a wireless phone useless in my environment.

There are a lot of variables here and just jumping to the latest release of the IPO will most likely not fix this problem, and should have no bearing on what firmware the phones can accept or use. I have Reason Codes for update failures that no one can tell me what they are yet, so once I get someone who has that information that may help me figure out what is going on here so I can ensure that these phones will accept and do updates in the future.