Update Extension/Directory numbers in CUCM

This application is for updating extension/directory numbers in CUCM 8.x/9.x. Currently there is no way of doing this using “Bulk Tool”. If you need to move a set of extension/directory numbers to a new number range then this application will let you do that in an automated way.

As always it’s a free app but donations of teacakes and/or Guinness are always welcome 🙂

Prerequisites to running the Application
O/S: Windows
Requires JRE 1.7 and above. You can check this by running “java -version” in a dos prompt.
Tested on Windows 7 and Vista but as long as you have the correct JRE it should work.

Java version MS-DOS prompt

Java version MS-DOS prompt

Else got to Java Version click on Verify Java version, allow the plug-in to run and in a few seconds you should see something like this:

Java Version

Java Version

If you dont have version 7+ of Java JRE you can download it from here Java JRE

Download
Download Link:Re-Map Dn’s Last update Feb 2016

Ver:0.7 Date 26th of Feb 2016
Notes: Added support for CUCM version 11.x

Ver:0.6 Date 16th of Sep 2013
Notes: Fixed bug with log file and added more detail reporting.

Ver:0.5 Date 24th of Jul 2013
Notes: Base build

CUCM Prerequisites
CUCM version 8.x, 9.x or 11.x. These are the versions I used this app on. No reason why it wouldnt work on ver 10.x
CUCM Server Node must be running “Cisco AXL Web Service” service
The user account used in the application must have “Standard AXL API Access” privileges on CUCM

How to use the application
1. Enter the data in the “dns.txt” file. See below regarding the format the data should be in
2. Select the version of CUCM
3. Enter the IP address of the Node in cluster running the AXL service
4. Enter the Username for the user account on CUCM that has the “AXL group privileges”
5. Enter the Password of the account
6. If all details are correct enter “Y” or “y

Update DN

Update DN

7. When the application is done open up the “AppLog.txt” file. Search for the word “Error” to see if any errors have occurred. If an error happen when trying to update a line it will look something like this:

AXL Req to CUCM to Update:\+441234123123
Error:Item not valid: The specified PT_ALL_DN was not found

If it updated the line successfully it will look like this:

AXL Req to CUCM to Update:\+441234123123
Done!
AXL Response:{FEB7AC82-0EF0-0C3F-AB05-E82356BF87ED}

Update DN's

Update DN’s

Data entry in dns.txt

The diagrams below depict all the ways that data can be inputted into the “dns.txt” file to update 3 different entities (Pattern, Partition and CSS) for a specified line. Note is DN is in a E164 the you will need to include the “\+”. The examples in the diagrams are also included in the “dns.txt” file by default when the application is downloaded from the link above.

Update DN

Update DN

Update DN & Partion

Update DN & Partion

Update DN, Partion and CSS

Update DN, Partion and CSS

Update DN and CSS

Update DN and CSS

Application Architecture
•The application is built on the Java Development Kit (JDK) 7
•The application and CUCM communicate using Web Service Definition Language 2.0 (WSDL) with SOAP Requests Service Definitions (Doc/Literal)
•The application uses https to communicate with CUCM and as CUCM uses a self sign certificate to get round this while the application is running it suppresses Java’s SSL Certificate validation. The communication between the application and CUCM is secure but this allows the possibility of man-in-the-middle attacks to take place between the application and CUCM when communication is initiated.
•For every 100 AXL write requests sent to CUCM the application will pause for 10 seconds.
•CUCM 9 dynamically throttles AXL write request. If there are are more then 1500 change request waiting it stops processing AXL write request. You can check the status of throttling on a node by the following 2 performance counts using RTMT tool:

•ThrottleCount—Determines number of times Administrative AXL throttling has been engaged.
•ThrottleState—Determines the state of AXL throttling. That is, whether AXL throttling is currently active (throttling is engaged).

About Alexis Katsavras

Working as Freelance Cisco Unified Communications Consultant in the UK. www.NetPacket.co.uk