This article relates to the Cisco TelePresence MCU 4203, Cisco TelePresence MCU MSE 8420, Cisco TelePresence IP VCR 2210, Cisco TelePresence VCR MSE 8220, Cisco TelePresence ISDN GW 3241, Cisco TelePresence ISDN GW MSE 8321, Cisco TelePresence IP GW 3510, Cisco TelePresence MCU 4505, Cisco TelePresence Supervisor MSE 8050, Cisco TelePresence MSE 8000 and Cisco TelePresence Advanced Media Gateway 3610 products.
A. The instructions for downgrading your TANDBERG Codian product depend on which software version you are currently running.
If you are downgrading from any of the following, see Downgrading from MCU 4.0, ISDN GW 2.0, AM GW 1.0, or Supervisor 2.0 below:
MCU software version 4.0
ISDN GW software version 2.0
AM GW software version 1.0
Supervisor software version 2.0
If you are downgrading from any of the following, see Downgrading below:
MCU software version 3.1 or earlier
ISDN GW software version 1.5 or earlier
IP GW software version 2.0 or earlier
Supervisor software version 1.2 or earlier
IP VCR software version 2.3 or earlier
Downgrading from MCU 4.0, ISDN GW 2.0, AM GW 1.0, or Supervisor 2.0
Note: You will have been instructed to save a copy of your configuration file (configuration.xml) before upgrading to 4.0/2.0. If you did not keep an appropriate configuration file and have at any point enabled Advanced account security mode you will no longer be able to log in to your product. If you do not have a configuration.xml file for the software release you are downgrading to, contact TANDBERG Technical Support.
You must restore the configuration before downgrading:
Go to Settings > Upgrade.
Select User settings. If required, select Network settings.
Locate a configuration.xml file that is compatible with the release to which you want to downgrade and click Restore backup file.Note: This must be a configuration file saved before Advanced account security mode was enabled.
When the configuration has been restored, follow the downgrading instructions provided below.
Note: Back up your CDRs before downgrading. See the online help for instructions.
Downgrading
You can downgrade your product in two ways:
Using the web interface
Download the required software version from www.tandberg.com (Support > Download software).
Unzip the image file.
Browse to the IP address of your Codian product using a web browser.
Log in as an administrator.
Go to the Settings > Upgrade page.
In the Main software image section, type in, or browse to the location of the software image file.
Click Upload software image.A progress bar is displayed in a separate pop-up widow while the web browser uploads the file to the product. This takes some time - dependent on your network connection. Do not move your web browser away from the Upgrade software page or refresh this page during the upload process; otherwise, it will abort.After a number of minutes, the web browser refreshes automatically and displays Main image upload completed successfully.
Click Close Status window.
In the changed Upgrade page, click Shut down TelePresence Product.
Click Confirm TelePresence Product shutdown.
When shutdown has completed, click Restart TelePresence Product and upgrade.
When prompted, confirm the restart. The unit will reboot and upgrade itself - this may take up to 25 minutes to complete.
Note: If you have been logged out due to inactivity, log in again as admin and click Restart TelePresence Product and upgrade on the Shutdown page.
Download the required software version from www.tandberg.com (Support > Download software).
Unzip the image file.
Use an FTP client to connect to the product - e.g. ftp <MCU IP Address> from the command prompt.
Log in as an administrator.
Upload the downgrade file from the command prompt. For example:put codian_mcu_3.0(1.5)
When the upload has completed, go to the Upgrade page within the web interface.
Click Shut down TelePresence Product and upgrade.
Click Confirm TelePresence Product shutdown.
When shutdown has completed, click Restart TelePresence Product and upgrade.
When prompted, confirm the restart. The unit will reboot and upgrade itself - this may take up to 25 minutes.
Revision | Publish Date | Comments |
---|---|---|
1.0 |
23-Apr-2015 |
Initial Release |