Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Question about deploying firmware

Status
Not open for further replies.

scifan

Technical User
Joined
Mar 12, 2018
Messages
59
Location
US
In an IPO server environment with multiple 500V2's, I think the HTTP entry for the DHCP scope determines the source for phone upgrades correct?

Do I just copy the TAR and TXT files from the zip file to that embedded file system? Assuming this is on the Linux server, can I just SCP these files to that location? Or do I have to go through the IP Office Manager software and use the embedded file system access functionality?

I notice that the TAR and bin files I see on the main host are replicated on the various 500v2's - but do those files need to be copied to all of the 500V2 expansion systems? Or does this happen through some sort of background task?

I thought I read that this file: "96x1Hupgrade.txt" is a necessary file, yet it doesn't appear to be included on any of these systems...

The readme file seemed to suggest that I needed to copy the 6_8_3 and 6_6_1 files over.

Should I remove the old files: 6_6_2, 6_6_4, 6_6_6, and 6_8_0?

 
Just keep the files that have been uploaded to the system during installation/upgrade.

Some files like 46xxsettings.txt, 96x1Hupgrade.txt and others are not present but autogenerated during runtime. You can look at them with a web browser.

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
Would I upload the new files to just the main IPO server?
 
Primarily, I'm wanting to install the new firmware update for 9608 and 9620 phones. Currently I have 6_8_0 installed, and wanted to upgrade to 6_8_3.
 
Then you have to upload 96x1Hupgrade.txt and 9600upgrade.txt along with the firmware files to each IPO that acts as file server for the phones.

They are not replicated automatically.

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
So, only to the IPO's, and not to the 500v2's correct?

Is this influenced by the HTTP dhcp setting for the phones? (if so, there's only one of the IPO's that's actually referenced).
 
The DHCP option "HTTPSRVR" defines where the phones get their files from.

If it only points to primary server, you don't have to deploy the files to IP500s

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
What's the format if I wanted to have it point to both servers? just something like "HTTPSRVR=10.0.0.1,10.0.0.2"?

I have MCIPADD= (which is pointed to the site 500v2) and HTTPSRVR=10.x.x.1,HTTPPort=80


Note that the DHCP option 66 points to each site's 500v2, not the IPO server address - would this be correct?
 
Option 66? The phones use option 242. You can only provide one server to the phones. You can configure the DHCP on each site to deliver MCIPADD as well as HTTPSRVR with the local IP500s IP address.

IP Office remote service Fixed price SIP trunk configuration: CLI based cale blocking: SCN fallback over PSTN:
 
I saw it, figured I'd ask since I wasn't part of the original dhcp scope configurations for this environment.

Is there any reason I shouldn't just put these updated files directly into /opt/ipoffice/system/primary folder on both of the IPO servers?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top