This document contains the steps required to
- Enable the AXL Web Service in CallManager
- Create a group in CUCM “AXL Service Users” to provide the permissions the AXL user will require
- Create an AXL user and assign it to the above group
- Retrieve the wsdl and xsd files needed
- Install the SA_cisco_cdr_axl app into Splunk (if you haven’t already)
- Configure the app with the credentials it will need
- Test that the configuration is valid.
Enable the AXL Web Service
Perform these steps in Call Manager.
These steps enable the AXL web service to work. Regardless of user account permission settings, if the base service for AXL isn’t enabled the AXL lookups can never work. You *may* find this is already enabled on your system. If so, just move on to the next section. 🙂
Experts: Check that the Cisco AXL Web Service is started and running.
If you need more specific directions –
- Browse to Tools, then to Control Center – Feature Services.
- Select your CUCM server from the drop down asking which server to configure, then click Go.
- Browse that list, find the Cisco AXL Web Service and depending on your version either …
- (for older CUCM versions) make sure there is a check mark beside it to enable it then click Save.
- (for newer CUCM versions) confirm its Status says Started. If it is not, click it and click Start at the bottom.
Create group “AXL Service Users”
Perform these steps in Call Manager.
This creates a group that we call “AXL Service User”, which has the rights/permissions inside CUCM for allowing anyone that’s a member of this group access to the AXL information. This is needed so that the user we create in the next step can be added to this role, and thus can access AXL.
Experts: Create a User level Access Control Group, then assign to that group the role Standard AXL API Access. (Our instructions create a new group for assigning the role, but do it in whatever way works for your environment).
Or, follow along below:
- Log into the Cisco Unified CM Administration application using an administrator account. NOTE you can access it from the “Navigation” menu in the upper right if you came to this section straight from the Enable the AXL web service section above.
- Click User Management, User Settings then Access Control Group.
- Scroll to the bottom of the list and click the Add New button.
- Type in AXL Service Users for the name and click Save.
- In the upper right, to the right of Related Links: (Which should say “Back to Find/List”) click Go.
- (You might find that you have to “Find” the AXL user we just created)
- To the right of the newly created Access Control Group AXL Service Users, click the “i” button under Roles.
- Click the button Assign Role to Group.
- In the “Find and List Roles” window, click Find to have it display all available Roles
- Click the checkbox beside Standard AXL API Access.
- At either the very top of the page or the very bottom, click Add Selected.
- Click Save. (Note this page refreshes with “Update successful” but otherwise gives no indications you are done.)
Create an AXL-enabled user
Perform these steps in Call Manager.
This creates a new user and adds the permissions (via the group created above) required for it to query the AXL information.
Experts: Create a user and add it to the above created access control group so that it can query AXL.
- Log into the Cisco Unified CM Administration application using an administrator account.
- NOTE you can access it from the “Navigation” menu in the upper right if you came to this section straight from the Enable the AXL web service section above.
- Click User Management then Application User.
- Click the Add New button.
- Supply a user name and an appropriate password. Remember these, we’ll need them later.
- For that user, down near the bottom find Add to Access Control Group
- In the new “Find and List Access Control Groups” window, click the checkbox beside AXL Service Users
- At the bottom of the page, click Add Selected.
- When returned to the Application User Configuration page, click Save.
- Again, this is a screen where the confirmation is subtle – “Add successful” but no other change.
- Check the roles and groups applied by going to User Management, Application User, finding the user you created in step 3 above and confirming it lists the Permissions information at the bottom.
- Click Save.
Retrieve the needed files from UCM
Perform these first few of these steps in Call Manager.
Cisco’s licensing does not allow redistribution of the portions of the Cisco Call Manager AXL SQL Toolkit Plugin, so we can’t provide it with the CDR app. Instead, see the below instructions to retrieve the toolkit and extract and deploy the required files.
- Log into the Cisco Unified CM Administration application using an administrator account. NOTE you may already be in this application if you were following the steps above.
- Go to Application | Plugins
- Click the Find button once (with default parameters) to populate the list.
- Click on the Download link by the Cisco CallManager AXL SQL Toolkit Plugin (older versions) or the Cisco AXL Toolkit (newer versions).
- Save the file onto your local system in a convenient place.
- After saving the axlsqltoolkit.zip file to your local system, open it with your favorite zip file utility.
- Drill down into axlsqltoolkit/schema/<UCM version>/
(For instance axlsqltoolkit/schema/11.5/ )
- Extract the three files you find there – AXLAPI.wsdl, AXLEnums.xsd and AXLSoap.xsd – into a temporary folder. Obviously, remember where you put them.
Install the SA_cisco_cdr_axl app into Splunk (if you haven’t already)
Perform these steps in Splunk.
- Log into Splunk
- Get to the “Manage Apps” page – either using the Apps menu at the top left of most pages in Splunk, or by going back to the “Launcher” app and clicking manage apps at the bottom left.
- Click the green button to “Browse more apps” in the upper right.
- Search for Cisco AXL and you’ll see our app.
- You should be able to just click “Install” and it will prompt you to restart Splunk after. If you see the app from that page but you don’t seem to be able to Install it, please contact us.
- ALTERNATIVE: If your Splunk admins have locked down your instance such that it can’t talk to Splunkbase, then you can download the tar.gz direct from Splunkbase and save it locally. Then in that same “Manage Apps” page from above you’ll see an “Install App From File” button. Click that and follow the prompts.
Configure the SA_cisco_cdr_axl app
Perform this in Splunk
“Install” AXL SQL Toolkit files
- Copy the three files AXLAPI.wsdl, AXLEnums.xsd and AXLSoap.xsd from the temporary directory where you extracted them before, to your $SPLUNKHOME/etc/apps/SA_cisco_cdr_axl/bin/ folder on the Search Heads.
- They can be deployed via most other “generally accepted” Splunk deployment methods as well – deployment server, deployer, puppet, etc…
- Restart Splunk!
Configure the AXL credentials.
- Open Splunk and log in as an administrator.
- Open the Supporting AXL Addon for Cisco CDR Reporting and Analytics app (SA_cisco_cdr_axl).
- Click “Update Credentials” at the top.
- Enter the publisher host, the port (generally 8443) and the username and password for the AXL user you created previously.
- Click Create to create the credentials.
- NOTE tiny bug in version 1.0 (and ONLY in 1.0 exactly)
- In the second section, Update existing credentials:
- Re-enter the password for the user just created, and click “Update”
Then try the following to confirm everything is set up correctly:
- Open the Supporting AXL Addon for Cisco CDR Reporting and Analytics app.
- Click on our Search navigation item near the top.
- Paste in the following search and press enter:
| ciscoaxl listPhone name="SEP%" columns="name,description"
If all is set up correctly, in a few moments (maybe minutes!) you should be presented with a list of all hardphones.
NOTE if your CUCM deployment is enormous you might want to filter that test down to a smaller subset of phones by changing “SEP%” to something more targeted. For instance “SEP0123%” will only match hardphones phones that have MAC addresses starting with “0123”.
Now that you have all this set up, it’s probably best to just contact us at firstname.lastname@example.org and we’ll help you get your Devices automatically generating.
However, if you look in “Searches, Reports and Alerts” (change to “All” apps) you’ll find we ship a disabled saved search called “get_devices_example”. If we were on the phone helping you with this last step, we’d follow a process similar to the following one to implement it:
- For that search, click Edit and then Clone it to a new search, named “get_devices_via_axl” or similar.
- View that cloned report, enable it from the button on that screen (it clones disabled, like the original) and confirm the data looks good for your environment.
- Edit the search and add to the end
| outputlookup devices
- Run that search once to populate the devices lookup for the first time.
- Save the altered search.
- Then Schedule that saved search to run perhaps once each night to update itself.
And remember, we’re very happy to hop on a webex and walk through the final implementation process with you, so feel free to drop us a line at email@example.com!
If you have any comments at all about the documentation, please send it in to firstname.lastname@example.org.