User's Manual

BDH Editor; Reviewed: RJS,
JWS,CLB,ML,RS,RKP,TGS,BH,
PMS, RGF, NHK 4/20/06
Application Notes
©2006 Avaya Inc. All Rights Reserved.
17 of 18
CID 117689
back into service before updated software could be downloaded. Processor occupancy
increased 7 to 10% consistently throughout the 8 minute download interval.
Due to these test results, it is not recommended to use the Avaya Media Server to download 46xx
IP telephone software to more than 300 telephones when using HTTP/HTTPS.
Additionally, the impact to processor occupancy when downloading telephone software depends
on the Media Server configuration and other activities that are occurring on the Media Server
while 46xx IP telephones are downloading software. For instance, if a duplicated S8710 server
pair is in the process of shadowing memory from the active server to the standby server while
downloading 46xx IP telephone software, the impact to processor occupancy can be more severe
than the impact resulting from the tests performed on the S8500 Media Server.
Due to the processor intensive nature of downloading software to IP telephones it is
recommended that this activity be coordinated and performed during times when the Media
Server is relatively inactive (non busy times), especially if the maximum number of
recommended phones (300) are all being updated at the same time.
Currently there is no tracking of IP telephone downloads to assure the phones download the
updated software prior to coming into service. Therefore, when downloading software to more
than 300 phones using a Media Server, which is not recommended, it might be necessary to
perform the download again on any phones that timed out during the initial “mass” update. The
SAT commands reset ip-stations ip-network-region rrr and reset ip-stations ipaddr
xxx.xxx.xxx.xxx yyy.yyy.yyy.yyy can be used to reset specific 46xx IP telephones to target them for
software updates.
10. Known Issues
The following are issues to be aware of when implementing and using Avaya Media Servers to
download 46xx IP telephone software.
1. Communication Manager Software releases earlier than 3.1 do not save the 46xx IP
telephone configuration settings in the 46xxsettings.txt file, located in the tftpboot
directory, when backing up and restoring data on a Media Server. The workaround is to
manually save the file to an external source after making any settings changes.
2. The 46xx IP telephone software binaries and configuration/settings files are not preserved
in the tftpboot directory during an upgrade of Communication Manager. The workaround
is to save the phone software and settings files to an external source prior to an upgrade
and move the files back into the tftpboot directory after the upgrade is completed. Or, the
46xx IP telephone software can be re-downloaded onto the Media Server after the
upgrade is completed.
3. In Communication Manager Software releases earlier than 3.1.2 do not transfer the 46xx
IP telephone configuration settings 46xxsettings.txt file to the secondary server in a server
pair when file synchronization occurs. The workaround is to manually move the
46xxsettings.txt file onto the secondary server when updates are made.
4. 46xx IP telephone software RPMs must be downloaded onto both Media Servers in a
server pair when the active alias IP address is used.
5. The Maintenance Web Page error message Object not found!, provided when attempting
to access the 46xx IP Phones link and a 46xx IP phone software RPM has never been
downloaded, isn’t very descriptive.