voipmeister.com voip stuff matters and more

Articles tagged with CUCM

Cisco IP phone inventory tool

From the sourceforge website:

Cisco IP Phone Inventory Tool: Inventories Cisco SCCP IP phones->outputs .CSV file with the following information: IP Address, Model Number, MAC Address, Host Name, Phone DN, Phone Load Version, Phone Serial Number, and switch name, ip, and port information

A promising tool which can be found here: http://sourceforge.net/projects/cipinventory/.

This tool however, requires access to network components. You can also gather this info by querying the CUCM servers directly, just like so:

admin:show risdb query phone

List Devices outside of Home Location

Ever wondered how many of your telephony devices are located outside of their home location (as configured on the device when using the Device Mobility feature)?

Here’s how: log on to the CUCM CLI and run the following query:

run sql select d.name, d.description, dp.name from devicemobilitydynamic dmd, device d, devicepool dp where dmd.fkdevice = d.pkid and dmd.fkdevicepool_devicemobility = dp.pkid

This will produce output like:

name            description           name
=============== ===================== =====
SEP0016466166B8 Phone 77640           HQ
SEP001E156CF34B Phone 79117           HQ
SEP001149604BFA Phone 77666           HQ
SEP0015FFFF5B38 Phone 77685           HQ

What this means is that the given devices are put in the HQ Device Pool (according to the Device Mobility setup) while they have another Device Pool configured. To remedy this solution, you should reconfigure those devices so they belong to the HQ Device Pool. You’ll probably need to change the Location and Device Calling Search Space settings as well.

This has been tested with CUCM 6.

CUCM database replication issues

A little note to self how to troubleshoot db replication issues on CUCM:

  • Make sure the hostnames of the CUCM servers are IP only (or set up a working DNS configuration)
  • Make sure both servers have the right time and timezone configured and make use of NTP servers

Retrieve core dumps via the CLI on CUCM

If Alert Central in the Real Time Monitoring Tool shows that there are core dumps, you can list them via the CLI.

admin:utils core list

    Size         Date            Core File Name
=================================================================
298200 KB   2010-11-24 17:36:51   core.13869.11.cef.1290616611
admin:

This is the equivalent of:

admin:file list activelog /core
<dir>   analyze
core.13869.11.cef.1290616611
dir count = 1, file count = 1
admin:

The latter has the advantage that you know the absolute path, which you need when you want to retrieve the file.

The file can be retrieved via the RTMT as well as via the CLI. All you need is an SFTP server on which you have write access, in this case I used a CentOS server running openssh. Here it goes:

admin:file get activelog /core/core.13869.11.cef.1290616611
Please wait while the system is gathering files info ...done.
Sub-directories were not traversed.
Number of files affected: 1
Total size in Bytes: 305356800
Total size in Kbytes: 298200.0
Would you like to proceed [y/n]? y
SFTP server IP: 10.133.133.133
SFTP server port [22]:
User ID: root
Password: ***********

Download directory: /root

The authenticity of host '10.133.133.133 (10.133.133.133)' can't be established.
RSA key fingerprint is 5b:8b:28:78:86:3d:9c:48:c9:2b:5e:42:e9:dd:bc:1d.
Are you sure you want to continue connecting (yes/no)? yes
.
Transfer completed.
admin:

Please not that the RSA key needs to be stored only once, it is presented upon the first connection you make with the SFTP server.

CCM 6 backups

To be able to create CCM 6 backups, you need a SFTP server. The easiest way to accomplish this (assumed you have some experience with managing *NIX systems and you have linux system at your disposal) is to create an extra account like ‘ccmbackup’ on a running Linux system:

adduser ccmbackup -s /bin/bash

Next, configure the backup settings on the CCM environment and perform a backup. Expect the backup to be around 300MB in size, depending on the information stored in your environment. YMMV.