Remote destination Line gets in busy state after been configured via AXL

Version 1
    This document was generated from CDN thread

    Created by: PER-ARNE LIND on 28-02-2013 08:28:14 AM
    We're using a script that adds user and phones/lines via AXL and now all of a sudden we have encountered that by adding a remote destination this way we end up with a busy line when trying to call this extension. A restart of the line solves this issue. If I add same paramaters via Web GUI it works fine though. I opened a case with TAC but they just points to our script and says it's something wrong there. has anyone else experienced this behavior??
    CUCM version is 8.6.2.X
    Greatful for any suggestions or help to find out what's happening.

    Subject: RE: Remote destination Line gets in busy state after been configured via AX
    Replied by: Geoffrey Carman on 28-02-2013 11:16:53 AM
    Do you have a way to catch/trace/debug the output of your script and then post the SOAP call it generates?

    Subject: RE: Remote destination Line gets in busy state after been configured via AX
    Replied by: PER-ARNE LIND on 01-03-2013 05:21:32 AM
    Geoffrey Carman:
    Do you have a way to catch/trace/debug the output of your script and then post the SOAP call it generates?

    Hi !!
    Here's my answer to your question and you''l have to know that we ahve no issue with the AXL in itself, all is succes it's only that the somehow gets i a busy state after this configuration so we have to make a restart of the line.
    -----------------------------------------------------------------------------
     The process we use to add a Remote Destination Profile is as follows:
    addLine
    getLine - To get the guid of the line (yes, the addLine above returns the guid as well, but for various reasons this is the way we do it)
    updateUser – To enable Mobility on the LDAP-imported user
    addRemoteDestinationProfile
    addRemoteDestination
    I omitted the return values below. Each of the requests just returns a guid anyway, none of the requests fail. This has worked without problems and we haven’t changed CUCM versions or done any changes in the script. After a Remote Destination Profile has been created with the requests below we always have to do a restart of the line in CCMAdmin to get it working.
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Body>
          <ns2:addLine xmlns:ns2="http://www.cisco.com/AXL/API/7.1">
            <newLine>
              <pattern>50012</pattern>
              <usage>Device</usage>
              <routePartitionName>PT_Internal</routePartitionName>
              <callForwardAll>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
              </callForwardAll>
              <callForwardBusy>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
                <destination>44220</destination>
              </callForwardBusy>
              <callForwardBusyInt>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
                <destination>44220</destination>
              </callForwardBusyInt>
              <callForwardNoAnswer>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
                <destination>44230</destination>
              </callForwardNoAnswer>
              <callForwardNoAnswerInt>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
                <destination>44230</destination>
              </callForwardNoAnswerInt>
              <callForwardNotRegistered>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
                <destination>44230</destination>
              </callForwardNotRegistered>
              <callForwardNotRegisteredInt>
                <callingSearchSpaceName>CSS_PSTN_Central_Fwd_Sweden_and_mobile_CLIP</callingSearchSpaceName>
                <destination>44230</destination>
              </callForwardNotRegisteredInt>
              <alertingName>Ts Test8</alertingName>
              <shareLineAppearanceCSSName>CSS_Line_Sweden_and_Mobile</shareLineAppearanceCSSName>
            </newLine>
          </ns2:addLine>
        </soapenv:Body>
      </soapenv:Envelope>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Body>
          <ns2:getLine xmlns:ns2="http://www.cisco.com/AXL/API/7.1">
            <pattern>50012</pattern>
            <routePartitionName>PT_Internal</routePartitionName>
          </ns2:getLine>
        </soapenv:Body>
      </soapenv:Envelope>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Body>
          <ns2:updateUser xmlns:ns2="http://www.cisco.com/AXL/API/7.1">
            <userid>tstest8</userid>
            <enableMobility>true</enableMobility>
            <maxDeskPickupWaitTime>5000</maxDeskPickupWaitTime>
            <remoteDestinationLimit>1</remoteDestinationLimit>
          </ns2:updateUser>
        </soapenv:Body>
      </soapenv:Envelope>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Body>
          <ns2:addRemoteDestinationProfile xmlns:ns2="http://www.cisco.com/AXL/API/7.1">
            <newRemoteDestinationProfile>
              <name>RDP_tstest8</name>
              <description>Ts Test8 - 50012</description>
              <product>Remote Destination Profile</product>
              <model>Remote Destination Profile</model>
              <class>Remote Destination Profile</class>
              <protocol>Remote Destination</protocol>
              <callingSearchSpaceName>CSS_Dev_RDP_CLIP</callingSearchSpaceName>
              <devicePoolName>DP_RDP</devicePoolName>
              <networkHoldMOHAudioSourceId>2</networkHoldMOHAudioSourceId>
              <lines>
                <line uuid="{3D6487A9-453A-A17B-D7F0-4255A3B99B32}" index="1">
                  <display>Ts Test8</display>
                  <dirn>
                    <pattern>50012</pattern>
                    <routePartitionName>PT_Internal</routePartitionName>
                  </dirn>
                  <e164Mask></e164Mask>
                </line>
              </lines>
              <callInfoPrivacyStatus>Default</callInfoPrivacyStatus>
              <userId>tstest8</userId>
              <rerouteCallingSearchSpaceName>CSS_RDP_RR_Mobile</rerouteCallingSearchSpaceName>
            </newRemoteDestinationProfile>
          </ns2:addRemoteDestinationProfile>
        </soapenv:Body>
      </soapenv:Envelope>
      <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
        <soapenv:Body>
          <ns2:addRemoteDestination xmlns:ns2="http://www.cisco.com/AXL/API/7.1">
            <newRemoteDestination>
              <name>RD_tstest8</name>
              <destination>0007XXXXXXXX</destination>
              <answerTooLateTimer>34000</answerTooLateTimer>
              <delayBeforeRingingCell>300</delayBeforeRingingCell>
              <remoteDestinationProfileName>RDP_tstest8</remoteDestinationProfileName>
              <isMobilePhone>true</isMobilePhone>
              <enableMobileConnect>true</enableMobileConnect>
              <lineAssociations>
                <lineAssociation>
                  <uuid>{3D6487A9-453A-A17B-D7F0-4255A3B99B32}</uuid>
                </lineAssociation>
              </lineAssociations>
            </newRemoteDestination>
          </ns2:addRemoteDestination>
        </soapenv:Body>
      </soapenv:Envelope>
     
    -------------------------------------------------------
     
    I've replaced mobile number with 0007XXXXXXXX but otherwise not changed anything in xml.

    Subject: RE: Remote destination Line gets in busy state after been configured via AX
    Replied by: David Staudt on 01-03-2013 03:33:49 PM
    Sounds like a defect, recommend opening a case with CDN Developer Support: http://developer.cisco.com/web/memberservices/support

    Subject: RE: Remote destination Line gets in busy state after been configured via AX
    Replied by: PER-ARNE LIND on 04-03-2013 02:20:12 AM
    If it's defect in the AXL why has it been working for so long then. Right now I'm squezed between TAC which points ti Development and lack of development support contract.
    I'll get customer to restart the CUCM cluster to see if it goeas away...
    /P

    Subject: RE: Remote destination Line gets in busy state after been configured via AX
    Replied by: David Staudt on 04-03-2013 01:38:18 PM
    Is this something that just started happening with 8.6.2?  Or is it something that works fine for awhile (after UCM restart?) and then stops working? 

    Subject: RE: Remote destination Line gets in busy state after been configured via AX
    Replied by: PER-ARNE LIND on 05-03-2013 02:02:44 AM
    Customer has always had 8.6.2.x and it has been working. No one has changed version or the code for the AXL configuration program, it just stopped working. I've asked customer to restart the whole system to see if it starts working again.
    /P