cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
490
Views
1
Helpful
1
Replies

AXL - UpdateLine how do routepartition and asciialertname get set?

clairetaylor1
Level 1
Level 1

In the UpdateLine xml below, the request processes fine with no errors and all the information is updated accept the routePartion and the asciiAlertingName.  This is on the 9.1 version of the Cisco Call Manager.

Any idea what to try differently to get these values to stick?

<axl:updateLine xmlns:axl="http://www.cisco.com/AXL/API/1.0" sequence="1">

<line>

  <pattern>69959</pattern>

  <description>69959</description>

  <alertingName>Dick Test</alertingName>

  <asciiAlertingName>Dick Test</asciiAlertingName>

<userHoldMOHAudioSourceId>1</userHoldMOHAudioSourceId>

  <callingSearchSpaceName>CSS-NCOS 2 - Countywide</callingSearchSpaceName>

  <networkHoldMOHAudioSourceId>1</networkHoldMOHAudioSourceId>

  <routePartitionName>PT-Phone DN</routePartitionName>

  <voiceMailProfile uuid="16C584EA-6A81-4138-9EA1-AF452DE8F75A"/>

  <callForwardBusy>

<forwardToVoiceMail>false</forwardToVoiceMail>

     <destination>4169959</destination>

<callingSearchSpaceName>CSS-NCOS 2 - Countywide</callingSearchSpaceName>

  </callForwardBusy>

1 Reply 1

dstaudt
Cisco Employee
Cisco Employee

This may be due to AXL versioning, whereby it is ignoring elements that do not match up with the schema version it is trying to apply to the request.

The example you have posted includes the '1.0' schema version, please make sure the schema version is one of those supported by your version of UCM, and also ensure the proper 'SOAPAction' header is included with the request.

https://developer.cisco.com/media/manager-xml-developer-guide/versioning.html

https://developer.cisco.com/media/manager-xml-developer-guide/hello_world.html