For example, applications written with CUCM 12.5 schema will still be supported through CUCM version 15 (because there won't be a The SOAP API request header SOAPAction: CUCM:DB ver=12.5 indicates which AXL schema version the request payload will follow.ĬUCM maintains backwards compatibility with the running release minus 2 versions.
#Cisco cucm 8.6 database schema device phone update
If the object can be configured from the CUCM Administration page, there is a Thick AXL method that lets you list, add, remove, and update that object.įor example, for phones the following Thick AXL methods exist: listPhone, addPhone, removePhone, updatePhone. For example, there are methods for things like phones, route lists, route patterns, and calling search spaces, just to name a few. Thick AXL: Methods are provided that allow you to perform certain tasks against the CUCM database in a very structured format that has been built aroundĮach type of object available in the CUCM database.Production environment is to use a separate account dedicated for each AXL API application.ĪXL has two distinct method types which operate in very different ways. In the interests of simplicity in this lab, you will be using the admin account which is a member of the Standard CCM Super Users group, however the best-practice in a
To provide read-only AXL API access you can create a separate Access Control Group and assign only the Standard AXL Read Only API Access role to it. To create an account dedicated forĪXL API use, you must first create an access control group and assign the Standard AXL API Access role to it, then associate the application user with the newly created This means that all super user accounts implicitly already have access to the AXL API. Standard AXL API Access role assigned to it. AXL API utilizes HTTPS Basic Authentication.Īny CUCM User (Application or EndUser) will have read/write access via AXL if they are members of the Standard CCM Super Users access control group or any group with the
0 kommentar(er)
