Supporting App for AXL | Installation Notes
All these steps are performed in Call Manager.
The four steps are to
Experts bypass: If all the above is old hat to you, you may only need a quick reminder of what to do. In that case, see the various little sections titled “Experts”
These steps enable the AXL web service to work.
Experts: Check that the Cisco AXL Web Service is started and running.
If you need more specific directions –
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.
Or, follow along below:
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.
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.
Next up is to Install the AXL app into Splunk next to the Cisco CDR Reporting and Analytics app.
There are many ways to deploy, configure and update the Splunk Universal Forwarder. Here we cover a variety of the more advanced ways to handle updating the TA for Cisco CDR Reporting and Analytics.