IP Phone firmware upgrade procedure (CP8945)

When you upgrade CUCM or install a new Device Pack it’s important to make sure that your end devices are prepared for firmware upgrade. First of all check your current firmware load and newest one provided in the new version of CUCM or Device Pack. For example:

current firmware load new firmware load
cmterm-8941_8945-sip.9-3-1-18 cmterm-894x-sip.9-4-2-8

Look at the readme doc for the cmterm-894x-sip.9-4-2-8 firmware, at the very beginning you can see:

“9.4(2) can be upgraded only from SCCP/SIP 9.3(4) onwards!!!”

So before you will provide new firmware files for your end devices you first need to upgrade to supported version: cmterm-8941_8945-sip.9-3-1-18cmterm-8941_8945-sip.9-3-4-17cmterm-894x-sip.9-4-2-8. If not, phones will not boot up.

This article applies to all end devices when you upgrade CUCM or install new Device Packs.

You can upgrade specific devices or all of them.

Specific devices by providing Phone Load Name at Device Information field (Device > Phone).
All devices by providing Load Information at Device Defaults (Device > Device Settings > Device Defaults). Note Maximium Serving Count for tftp server:

This parameter specifies the maximum number of client requests to accept and to serve files at a time. Specify a low value if you are serving files over a low bandwidth connection. You can set it to a higher number if you are serving small files over a large bandwidth connection and when CPU resources are available, such as when no other services run on the TFTP server. Use the default value if the TFTP service is run along with other Cisco CallManager services on the same server. Use the following suggested values for a dedicated TFTP server: 1500 for a single-processor system and 3000 for a dual-processor system. For higher CPU configurations, the serving count can be up to 3500.
This is a required field.
Default:  500
Minimum:  1
Maximum:  3500


Read More

Cisco RTMT in Linux (Xubuntu)

I was preparing a new virtual machine with Linux OS for Cisco UC maintenance purposes. It was quite difficult to implement RTMT but finally I have managed to install it. Below you can find steps which allow you to use RTMT in Linux (Xubuntu).

RTMT 10.5

Xubuntu 15.04

Java 7

First you need to install appropriate java version, remember to install java 7 (with java 8 it won’t work).

me@xubuntu15:~$ sudo add-apt-repository ppa:webupd8team/java

me@xubuntu15:~$ sudo apt-get update

me@xubuntu15:~$ sudo apt-get install oracle-java7-installer

Make sure that the downloaded file is executable:

me@xubuntu15:~$ chmod +x CcmServRtmtPlugin.bin

Run instalator with path to previously installed java:

me@xubuntu15:~$ sudo sh CcmServRtmtPlugin.bin LAX_VM /usr/bin/java

rtmt #1

rtmt #2

rtmt #3

rtmt #4

Go to:

me@xubuntu15:~$ cd /opt/Cisco/Unified-Rtmt/JRtmt/

and edit run.sh file and type appropriate path to java:

me@xubuntu15:/opt/Cisco/Unified-Rtmt/JRtmt$ sudo nano run.sh


Now you can run RTMT:

me@xubuntu15:/opt/Cisco/Unified-Rtmt/JRtmt$ sudo sh run.sh

Read More

IM and Presence upgrade from 9.1 to 10.5

There are few things that need to be done before or during upgrade process. From my notes:

  1. IM and Presence Release 10.5(2) must match CUCM Release 10.5(2). First you need to upgrade CUCM cluster.
  2. AXL user password cannot contain special characters!
  3. Manual backup has to be done (in case of something goes wrong),
  4. Disable DRS scheduled backup (in case of backup and upgrade time conflict),
  5. Install cop file:

    You must also install the ciscocm.version3-keys.cop.sgn cop file before you upgrade to IM and Presence Service Release 10.5(1), or later, from any release earlier than 10.0(1). This COP file is necessary for all upgrades from pre-10.0(1) to 10.5(1) and later.

  6. Check database replication:
    CLI: utils dbreplication runtimestatedbreplication 2GUI: Cisco Unified IM and Presence Reportingdbreplication 1
  7. Use “Switch to new version after upgrade” switch option for both Publisher and Subscriber.

Read More

VMware ESXi reset password with Slax

Regarding to the Vmware kb article (1317898) this is unsupported way:

“Reinstalling the ESXi host is the only supported way to reset a password on ESXi. Any other method may lead to a host failure or an unsupported configuration due to the complex nature of the ESXi architecture. ESXi does not have a service console and as such traditional Linux methods of resetting a password, such as single-user mode do not apply.”


Cannot complete login

If you still need to reset it then you can use linux OS iso file from remote location instead of booting ESXi locally. I used Slax as it can be booted from network location, fot instance Ubuntu can’t. It allows you to reset password from ESXi partition. On Cisco UCS use CICM GUI interface with KVM Console to boot it from network.


Esxi: 5.1.0
Slax: slax-English-US-7.0.8-x86_64 (slax can be booted from network location).

Here’s what you need to do:

1. Shutdown all vm machines.
2. Use KVM console to boot external ISO image.
a) Cisco CICM
Server > Summary > Launch KVM Console:

Launch KVM Console

b) Click Add Image… and point to the slax image on your local hard drive. Select “mapped“. Reset VMware esxi machine and after reload press F6 to select the boot menu and then choose virtual KVM DVD drive with the Slax.

Add image

3. Slax:

Open terminal:

root@slax:~# cd /

root@slax:/# mount /dev/sda5 /mnt
root@slax:/# ls -l /mnt

ls -l mnt

root@slax:/# cd /tmp
root@slax:/tmp# cp /mnt/state.tgz /tmp

ls tmp

root@slax:/tmp# tar xzf state.tgz

ls tmp #2

root@slax:/tmp# tar xzf local.tgz

ls tmp #3

root@slax:/tmp# cd etc

ls etc

root@slax:/tmp/etc# kate shadow


Delete everything between “root:” and “:16582” and save it. (note that it will be different than 16582).

kate shadow before


kate shadow after

root@slax:/tmp/etc# cd ..
root@slax:/tmp#  tar czf local.tgz etc

ls tmp #4

root@slax:/tmp#  tar czf state.tgz local.tgz

ls tmp #5

root@slax:/tmp# cp state.tgz /mnt
root@slax:/tmp# cd /mnt

ls -l mnt #2

Files have been changed.

Now you need to shut down slax and power on Vmware Esxi. Remember to unmapp Slax iso file. Boot your system from hard drive.

Now you can log in to the esxi using vSphere client with no password at all. Set new in Vsphere GUI.

Read More