AXL 12.5 get or add UC Service of type Jabber Configuration

[sebastien_michelet]

When I try a getUcService to get details of a UC service with new type "Jabber Configuration", I get the following error:

<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Body>
<ns0:getUcService xmlns:ns0="http://www.cisco.com/AXL/API/12.5">
<name>CTC Standard Full Feature</name>
</ns0:getUcService>
</soap-env:Body>
</soap-env:Envelope>

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault>
<faultcode>soapenv:Server</faultcode>
<faultstring>This operation is not allowed using AXL API. If you wish to get Jabber Configuration please use the Unified CM Administration interface.</faultstring>
<detail>
<axlError>
<axlcode>5003</axlcode>
<axlmessage>This operation is not allowed using AXL API. If you wish to get Jabber Configuration please use the Unified CM Administration interface.</axlmessage>
<request>getUcService</request>
</axlError>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope>

Does this mean there is no way to list, get or provision the Jabber configuration UC Service (new in 12.5)?

[KiranKL]

Hi,

Yes. I tried the same request (addUcService and getUCService) and got the same message as a response.

If a user tries to get a Uc service of jabber client configuration type, an error code 5003 is generated with the following error message "This operation is not allowed using AXL API. If you wish to get Jabber Configuration please use the Unified CM Administration interface"

Its by design. Right now i am not sure about complete rationale behind the design. Lets wait for any expert to comment.

Please refer UDS API for your usecase, as jabber configurations added using CUCM UI distributed to jabber clients via UDS API.

[Anusha B R]

Hi,

Right, this error is expected and right now there is no way to provision Jabber Configuration from AXL in 12.5 .

Best Regards,
Anusha B R

[dstaudt]

It appears that it's possible to provision a Jabber UC Service by going down into the SQL.  See the 'axl_executeSQLUpdate_Jabber_config.py' example in this Python sample collection: https://github.com/CiscoDevNet/axl-python-zeep-samples

[sebastien_michelet]

Thanks for pointing this out, that makes sense, I will give it a try

[mikael.andre]

Hi,

Same issue on CUCM 14.0.1.13900-155.

Is there any change planned regarding this point? Many thanks.

[mikael.andre]

Hello,

I successfully make modification on Common Phone Profile using this Python code:

print("*** Update common phone profiles ***")
cppVendorXml = '<items><ciscoCamera>1</ciscoCamera><PasswordPersistenceForCollaborationEdge>1</PasswordPersistenceForCollaborationEdge><webAccess>0</webAccess><useEnblocDialing>1</useEnblocDialing><sshAccess>1</sshAccess><RingLocale>0</RingLocale><lineMode>1</lineMode><iceCapability>0</iceCapability><serverreflexiveaddress>0</serverreflexiveaddress></items>'
cppXmlOptions = ET.fromstring(cppVendorXml)
cppVendorXmlArray = []
for i in cppXmlOptions:
cppVendorXmlArray.append(i)
ucm.update_commonphone_profile(name='CPP_Collab1k', vendorConfig={ '_value_1': cppVendorXmlArray})
time.sleep(timer02)