MANUALLY INSTALL CISCO CME AND CUE ON UC500 OR CME

IOS and CME Reinstall

The following process describes how to reformat the IOS Flash card and reinstall IOS and CME firmware to provide a known good baseline. This isn’t entirely necessary to reset a baseline configuration, but may be desirable if you feel that some of the files have been deleted or otherwise tampered with.

  1. Start your FTP and TFTP servers. Note the username and password required for FTP.
  2. Use a Secure Shell client to access the UC500 CLI at the default address 192.168.10.1.
    If the default addressing has been changed, use whatever default gateway address was assigned to your PC via DHCP.
    If you don’t get an IP address on your PC, it could be that the default configuration has been lost.
    A new UC500 should always be configured with the default address. The rest of this document assumes that this is the case and that your PC has been assigned IP Address 192.168.10.11.
  3. Log in with default username and password of cisco/cisco.
  4. Format the IOS flash card format flash: and confirm.
  5. Copy IOS copy tftp://192.168.10.11/uc500-advipservicesk9-mz.124-11.XW7 flash: confirm and accept default file name:
  6. Copy CME support files: archive tar /xtract tftp://192.168.10.11/CME-Support-Files-4.2.7.tarflash:      
  7. Copy CME phone loads: archive tar /xtract tftp://192.168.10.11/CME-Phone-Loads-4.2.7.tarflash:    
  8. Save the default config for the next restart (Use the specific file name for your model): “write memory” or “Copy running startup”

CUE Clean Install

One you have installed IOS and CME, CUE can be reinstalled. Provided that CUE is in a steady state, you will be able to install directly from FTP. If the CUE application has failed for some reason, it may be necessary to install using the bootloader.

Reinstall from Steady State (your PC is at 192.168.10.11)

  1. From your PC, ensure that there is a path to the CUE module: Ping 10.1.10.1
  2. Assuming that this is ok, access the CUE console via the UC500 CLI: service-module integrated-Service-Engine 0/0 session
  3. Log in if necessary, or just press enter on a new system to get the UC500-CUE prompt.
  4. Start the clean install process: software install clean url ftp://192.168.10.11/cue-vm-k9.uc500.8.0.6.pkg username <ftp username> password <ftp password>
  5. Confirm that you wish to continue.
  6. At the Language Installation menu, press 8 for UK English, then x to continue the install.
  7. Once the install has completed, the module will restart.
  8. If required, the CUE module can also be reinitialized at this point. To do this, first go Offline and confirm
  9. Then restore factory default and confirm.
  10. Press Enter to reload.

Reinstall using the CUE Module Bootloader

If the CUE module is non-responsive, it may be necessary to reinstall from the bootloader. For more information see the CUE Install Guide

  1. From IOS CLI reload the CUE module: service-module integrated-Service-Engine 0/0 reload and confirm.
  2. Immediately open the CUE Module console service-module integrated-Service-Engine 0/0 session and note that the module restarts.
  3. When you see the bootloader prompt type ***
  4. Type config to configure the module with the following settings
    • IP Address: 10.1.10.1
    • Subnet Mask: 255.255.255.252
    • TFTP Server: 192.168.10.11
    • Gateway: 10.1.10.2
    • Default Helper File: cue-vm-k9.uc500.8.0.6.pkg
    • Ethernet interface: Internal
    • Default Boot: Disk
    • Default Bootloader: Primary
  5. Once the flash has erased, start the install process by typing boot helper.
  6. At the Service Engine Helper Menu, select option 1 to install software and use the following configuration:
    • Package name: cue-vm-k9.uc500.8.0.6.pkg
    • Server URL: ftp://192.168.10.11
    • Username: <ftp username>
    • Password: <ftp password>
  7. Confirm disk clearing.
  8. At the Language Installation menu, press 8 for UK English, then x to continue the install.
  9. Once the install has completed, the module will restart. At this point CUE will be ready in its factory default state, ready for initialization using CCA.