When deploying CUCM on a regular basis, there is often a set of Enterprise Parameters common to most deployments that require configuration. These involve jumping through various hoops on the UI to set up, so are a perfect candidate for API tooling using AXL.
Enterprise Params are a bit of a special case in that you use the getServiceParameter method which supports get, update and list operations.
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/11.5"> <soapenv:Header/> <soapenv:Body> <ns:updateServiceParameter> <processNodeName>EnterpriseWideData</processNodeName> <name>AllowedPerfmonQueriesPerMinute</name> <service>Enterprise Wide</service> <value>100</value> </ns:updateServiceParameter> </soapenv:Body> </soapenv:Envelope>
These are housed in the processConfig table, and are called with the following special handling:
- processNodeName: EnterpriseWideData
- service: Enterprise Wide
The attribute names are most easily determined using a list . This allows for easily scripting using your preferred language or performed more manually using SoapUI.
afterthenumber 
I have noticed that parameters which have a drop down field for their parameter values are not updated „visually“, so when I look into the settings after the update, the parameter looks still the same, even when the „GET“ response proofs the succesful update.
LikeLiked by 1 person
interesting! Can you give me an example? Have you tried this out with Thin AXL as well?
LikeLike
Would you be willing to post a sample for setting the T302 timer? I have some code but I am not having the same success as with other settings.
Thnkas
LikeLike
Would you be willing to post a sample setting the T302 timer? I am not having any luck with the format. I have a small piece of sample code and the service data from CCM when performing the list.
param =
axl.updateServiceParameter(param)
{
‘processNodeName’: {
‘_value_1’: ‘EnterpriseWideData’,
‘uuid’: ‘{00000000-1111-0000-0000-000000000000}’
},
‘name’: ‘TimerT302_msec’,
‘service’: ‘Cisco CallManager’,
‘value’: ‘15000’,
‘valueType’: None,
‘uuid’: ‘{84BD105F-34B5-43CB-BCC0-D2AEAF335D41}’
}
LikeLike