Mobile Connect Remote Destination created by AXL not activating (CUCM 8.6.2)

[David Fitzgerald-Irons]

Hi there folks

I'm using the AXLAPIBinding code from the Cisco AXL Toolkit plugin, customising the XML according to the objects being created or modified, and in essence following the procedure that would be used to manually configure a client for Mobile Connect (the aim is to automate the configuration in an Orchestrator run-book for the convenience of our help desk staff).

The problem I have is that although I am creating/modifying the necessary objects (addRemoteDestinationProfile, addTodAccess (required for addRemoteDestination), updateUser (to ensure mobility is enabled), addRemoteDestination, updateRemoteDestination) and these appear immediately in the CUCM web UI, it seems the Remote Destination will not activate unless I go into the web UI and "Save" the Remote Destination (no changes - just "Save" it)

I'm doing this with the XML code extracted from the Orchestrator run-book, loading each extract into SoapUI and running in the sequence outlined above, so I know the problem is not with Orchestrator.

Has anyone encountered this kind of problem ? Have you found a work-around ? Am I missing something ?

Any advice gratefully received.

David

[Mohammed al Baqari]

I never tried this before, but sounds to be something like 'Rest' is needed although Rest is not an option when you create Remote Destination. But may be you can rest the phone using the RDP

[David Fitzgerald-Irons]

Thanks, Mohammed.

I think in this context you may be referring to "REST", which is an architectural style for web services. So far as I can determine the Cisco AXL Toolkit uses the SOAP protocol within the REST architecture for implementing procedures such as those I've used (addRemoteDestinationProfile, addTodAccess, updateUser, addRemoteDestination, updateRemoteDestination).

For example, my "updateRemoteDestination" XML looks like this:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/8.5">
   <soapenv:Header/>
   <soapenv:Body>
      <ns:updateRemoteDestination sequence="1">
               <destination>10212851548</destination>
               <answerTooSoonTimer>5000</answerTooSoonTimer>
               <answerTooLateTimer>19000</answerTooLateTimer>
               <delayBeforeRingingCell>2000</delayBeforeRingingCell>
               <isMobilePhone>true</isMobilePhone>
               <enableMobileConnect>true</enableMobileConnect>
      </ns:updateRemoteDestination>
   </soapenv:Body>
</soapenv:Envelope>

That code is then incorporated into the body of a HTTP "POST" request to the Call Manager, and the Call Manager returns a SOAP encapsulated response such as:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <ns:updateRemoteDestinationResponse xmlns:ns="http://www.cisco.com/AXL/API/8.5">
         <return>{99291FE3-91B1-FC48-8299-BB6CCDD32AE4}</return>
      </ns:updateRemoteDestinationResponse>
   </soapenv:Body>
</soapenv:Envelope>

The response example above indicates the successful update of the Remote Destination.

So unless I've misunderstood what you mean when you suggest I should "rest the phone using RDP", I think the process I'm using is correct.

My problem is determining how to activate the configured RemoteDestination automatically when it is created by the SOAP protocol within the REST architecture.

Thanks again for your input

David