I'm setting up MediaSense 9.1 in the lab, and got successfully through the initial installation. After logging in for the first time, I hit the section where it was asking for the AXL provider. I put in the previously built application user, and MediaSense immediately complained that the configuration wasn't right. I verified the IP address, the user name, password, permissions (AXL role and Standard CM Administration), and they were all set as I intended. But MediaSense insisted that it wasn't right. CUCM AXL is running, and UCCX communicates via AXL with no problem.
Tried to research this, and it appears someone had a similar situation with 8.5, but was able to resolve it by rebuilding. I tried rebuilding Media sense, and hit the same problem.
Since I was out of other things to try, I put in the default application administration account for CUCM (the superuser) and tried that. Surprisingly, that did work, and allowed MediaSense to come up.
Once it came up, I tried to change it to the designated AXL accounts, only to have MediaSense continue to complain that they weren't correct. Changing it back to the CUCM default application administrator worked.
At this point (since it's a lab), I went to my AXL user, and gave it the super user role in addition to the AXL role it already had. When I hit save, MediaSense happily accepted the new user.
I have searched the documentation, but CANNOT find anything that tells me that the AXL account needs any additional rights other than just the AXL role and the Standard CM Administration roles. The install and admin guide specifies those two. Apparently, super user access is what's required, and not just standard admin access.
I thought I would put this out there so that others could benefit/clarify the information as appropriate.
You have reached the Cisco Logistics Support Center.. To Check Status of
your RMA, visit Product Returns & Replacements (RMA). Need help? Contact
us by Phone or Email. North Americas Phone: 1800 553 2447 Option 4
Email: email@example.com Europe Phone: +3...
The short answer is that you don't.... That isn't entirely true while at
the same time it kind of is, but for the most part you don't configure
the softkeys. You enable or disable them via TCL. Here is the long
answer. Be sure to read the whole thing or e...
Topology: IP Phone > Switches > Microsoft NPS setup to forward 802.1x
proxy to > ISE 2.1 patch 3 Authentication: EAP-TLS using Cisco MIC SANs
Phone Models 802.1X support? 802.1x flavor Addtl Comment EAP-MD5 EAP-TLS
Cisco 3905 Y Y N Cisco 6911 Y Y N Cisco ...