I am having a problem with an application which I created a while ago. It has been used for quite a long time at different installations with no problems. But at this new installation I receive an error code 10 when trying to logout.
The application sends a XML message to to callmanager to login or logout a specific user on a specific phone.
Shouldn't you have a single user which has em proxy rights (use its userid as appid) and other users (use them in the userid field) that you log in and out?
Also, what release are you running? EM proxy stuff has changed quite a bit between release 3.x/4.x and 5.0+
Also, and that's what devsupp will be asking for... did you check the logs? Logs often are key to determining the true cause of the problem as the APIs don't always tell you the proper error message (I know.. shouldn't happen, but unfortunately it does.. I've had a few instances where the error I got from the ccm would really confuse me and only when I looked at the logs would I figure out what was going wrong and could take steps to fix it).
The log category is conveniently named "Extension Mobility" :)
Now in order to have detailed enough logs, you need to do the usual: log into the serviceability pages of ccm (https://mycallmanager/ccmservice/), go to "Trace", "Configuration", select the server in question, then you need to locate the appropriate service group (that's really trying out categories until you find what you're looking for).. in this case, it's under CM services, then Select Extension Mobility, and change the debut trace level from info to debug and save.
Sometimes, when you need to see DB interactions, the "cisco database layer monitor" in the "database and admin services" service group is also helpful (look at that if the extension mobility logs show you nothing). Needless to say that dbl logs go over the entire system so if you have an active system, you might want to do this on off hours (both for load and size considerations.. )
The principle is the same in every case you have an unexplained error message, regardless of the api (I often do this for axl).. and those logs, even if they tell you nothing, you can send them to developer support (provided you have a valid contract) so that you don't have to wait 1-2 days only to be asked to provide traces and you then have to reproduce the problem and lose even more time.
After a few hours of tying without any success I created a new Enduser. This user was able to successful login and out. So there was no problem in the application, but probably in the Enduser configuration.
After a while I found out that the appID is case sensitive with the logout request.
appID is "ABcd". If I enter this appID in my application as username, the application uses it for userID and appID (all our end users have authentication proxy rights). When I use all lower case for the username I can login, but get the error message when I try to logout. When I enter the username in case sensitive I am also able to logout.
Why does the EM service for IP phones not care about case sensitive, the EM API login request not care about case sensitive, but the EM API logout request does care about case sensitive?
For me it seems like a bug... Although I do understand that they want case sensitive, but not in the selective way it is now.
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 ...