With automation and bulk tasks getting more and more important in big UC environments, and well known methods like BAT jobs getting obsolete, I wanted to do a quick introduction to CUCM AXL API and show, based on an example, how easy and powerful it is.
I decided to write about that because over the last few weeks couple people asked me this very question. We know how to configure Early Offer support on CUCM, there are thousands of guides on that topic, but sometimes it’s not clear what’s actually the logic and reason behind.
Recently my customer reported ringback issue on their VG224 analog gateway. Basically, when someone tried to call analog phones via VG224, they just heard couple ringback tones and nothing after. On the called party side though, phones were not ringing at all.
Recently I was deploying some UC applications in customer’s environment and hit quite tricky issue while trying to install CER 11.5 OVA via vSphere 6.5 web client.
Today I’d like to share with you simple python script which can be used to automate and speed-up some time consuming activities in CUCM.
Goal of the script is to establish SSH connection to multiple CUCMs (using threads), issue required commands, wait for the output and save it to separate files on your PC.
In bellow examples we will check CUCM status and database replication, but you can play with it and implement whatever logic you want. This can be also used against IOS devices.
So here is the script:
We all know that CUCM database replication issues are serious. We are checking database every time there is an upgrade, server cores, new machine is added, etc., just to ensure that our customer will have properly functioning environment.
We all know CLI commands like utils dbreplication status or utils dbreplication runtimestate, but what these commands really do and what is the logic of using them?