CUCM AXL user control

[andrew.spencer11]

Using CUCM 9.1.2.1, I am successfully creating basic users using <ns:addUser> AXL.

I want to provision my users with enableEmcc set to true, but <enableEmcc>t</enableEmcc> is not working, no error message is given, it simply does not update.

Provisioning AXL being used:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/9.1">

  <soapenv:Header/>

  <soapenv:Body>

  <ns:addUser sequence="?">

  <user>

  <userid>12345</userid>

  <firstname>bob</firstname>

  <lastname>ross</lastname>

  <mailid>test@test.com</mailid>

  <enableEmcc>t</enableEmcc>

  </user>

  </ns:addUser>

  </soapenv:Body>

</soapenv:Envelope>

I also want to be able to mark both password and PIN as locked by administrator but this is also not working, again with no error.

Pwd/PIN Locking AXL being used:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/9.1">

  <soapenv:Header/>

  <soapenv:Body>

      <ns:updateUser sequence="?">

        <userid>12345</userid>

  <passwordCredentials>

  <pwdCredLockedByAdministrator>t</pwdCredLockedByAdministrator>

  </passwordCredentials>

  <pinCredentials>

  <pinCredLockedByAdministrator>t</pinCredLockedByAdministrator>

  </pinCredentials>

      </ns:updateUser>

  </soapenv:Body>

</soapenv:Envelope>

I have attempted to find documentation and examples on the matter but am struggling to see where I am going wrong.

Any advice greatly appreciated.

[dstaudt · Accepted solution]

The first request with EMCC works for me on my 9.1(2) test system.  You might want to check that you are specifying the SOAPAction header correctly in the request - if not AXL may default to using an older schema version:

POST https://ds-ucm912.cisco.com:8443/axl/ HTTP/1.1

Accept-Encoding: gzip,deflate

Content-Type: text/xml;charset=UTF-8

SOAPAction: "CUCM:DB ver=9.1 addUser"

Content-Length: 498

Host: ds-ucm912.cisco.com:8443

Connection: Keep-Alive

User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

Authorization: Basic QWRtaW5pc3RyYXRvcjpjaXNjbyExMjM=

<?xml version="1.0" encoding="UTF-8"?>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/9.1">

  <soapenv:Header/>

  <soapenv:Body>

    <ns:addUser sequence="?">

      <user>

        <firstName>user999</firstName>

        <lastName>Sample</lastName>

        <userid>jonesss</userid>

        <mailid>jsample@company.com</mailid>

        <enableEmcc>t</enableEmcc>

      </user>

    </ns:addUser>

  </soapenv:Body>

</soapenv:Envelope>

Same with the second request, seemed to work fine on my system:

POST https://ds-ucm912:8443/axl/ HTTP/1.1

Accept-Encoding: gzip,deflate

Content-Type: text/xml;charset=UTF-8

SOAPAction: "CUCM:DB ver=9.1 updateUser"

Content-Length: 543

Host: ds-ucm912:8443

Connection: Keep-Alive

User-Agent: Apache-HttpClient/4.1.1 (java 1.5)

Authorization: Basic QWRtaW5pc3RyYXRvcjpjaXNjbyExMjM=

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/9.1">

  <soapenv:Header/>

  <soapenv:Body>

      <ns:updateUser>

        <userid>jonesss</userid>

        <passwordCredentials>

            <pwdCredLockedByAdministrator>t</pwdCredLockedByAdministrator>

        </passwordCredentials>

        <pinCredentials>

            <pinCredLockedByAdministrator>t</pinCredLockedByAdministrator>

        </pinCredentials>

      </ns:updateUser>

  </soapenv:Body>

</soapenv:Envelope>

Same as above, might check the SOAPAction header.  In the case of messing with passwords, might confirm that LDAP integration is not in effect, as password controls may be disabled from AXL.

Finally, if you are still having issues, I suggest opening a DevNet Developer Support ticket so they can take a look at the detailed logs from your system and find out the root cause...https://developer.cisco.com/site/devnet/support/

[andrew.spencer11]

Thanks - I didn't have a SOAPAction header at all. I added one as per your example and after a bit of trouble with 500 and 599 responses it's finally working correctly.

Much appreciated.