I have some applications developed to CCM 4.3, and now I have to make them work with CCM 6.0.
My problem is that I need to access to the information pin/password of the users.
I have been study the Cisco Unified Communications Manager 6.0(1) Database Dictionary and Cisco Unified Communications Manager Developers Guide for Release 6.0(1).pdf. I can access the credential table in the database making an AXL request, but I don't know if this value â<CREDENTIALS>B1E093371D17A602638DFF87FF303F31DCBD9A5848BD9DB57424EB04F2537503</CREDENTIALS>â that is the pin or password. Is this with some kind of encryption?
The dictionary manual tells that âAXL and all applications access passwords and PINs only via IMS librariesâ, where can I found information about it?
doAuthenticateUser allows you to verify both pin and password (either or.. depending on the parameters you give).. but there's no way to read out the pin/password for us regular folks.. only cisco internal apps can do that.
using updateUser you can update a user's password/pin so basically you have everything you need except pin recovery. If you need to develop a pin recovery tool (eg. for a helpdesk), you'd just give them the ability to set a new pin (or password) for the user and be done with that.. it is after all the same procedure for an IT admin when you lose the password for your domain account or some IT service your company offers its employees.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...