J179 on R11 - Software Update Failed 7

[dsm600rr]

Hello all,

I am configuring a new Deployment, IPO R11 and J179 Phones and when they are booting up I get "Software update failed"

Thoughts?

ACSS

 

[dsm600rr]

These 2 or the entire folder contents?

J100Supgrade.txt and
FW_S_J179_R4_0_3_1_4.bin

ACSS

 

[derfloh]

Those two are enough.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[dsm600rr]

Thanks Gents,

I removed the old ones (backed up locally) and I will report back what happens.

ACSS

 

[dsm600rr]

That worked, thanks for all the input everyone, this was a rush install. I just received the hardware yesterday and we install tomorrow morning :|

For the future, is it always best to load the latest firmware from Avaya on these SIP Phones? I know the H.323 like 9608's were specific to the software release the IPO is running.

ACSS

 

[joe2938]

show him some pink then

 

[gwebster]

Little late but look at

https://downloads.avaya.com/css/P8/documents/101062454

on page 32. The J179D03A has a minimum software release of 4.0.1.0. That is why it was rejecting the attempt to downgrade to 4.0.0.0.

 

[dsm600rr]

gwebster: Makes sense. Being in a rush to have this done in a day and running into issues didn't help things.

I will take a look at that document over the weekend, however I do have the same question if someone could chime in, I would appreciate it.

H.323 IP Phones Firmware was specific to match the version the IPO was running.

On the SIP J100's, is it best practice on new installs to head over to Avaya Downloads, Download the latest FW_S_J1XX.bin files and run that? I am assuming yes however I do not like to assume.

The reason I ask is it took quite some time to back up all of the FW_S_J1XX.bin files and upload all of the new bin files, so I will need to plan that into the project.

Thanks!

ACSS

 

[derfloh]

The H323 never had to match IPO firmware in any way. But IPO delivered one firmware automatically with each release.

IP Office remote service

https://www.fwilke.com/home

Fixed price SIP trunk configuration:

https://www.fwilke.com/en/ip-office-sip-trunk-en/

CLI based cale blocking:

https://blog.fwilke.com/ip-office-block-calls-from-specific-cli/

SCN fallback over PSTN:

https://blog.fwilke.com/ip-office-scn-fallback/

 

[critchey]

Digital phones firmware is dictated by version (and even that can be circumvented if you know what you are doing) H323 and SIP can be changed independent of IPO release.

The truth is just an excuse for lack of imagination.