getRoutePattern response missing destination and routePartitionName

[Daniel Appleby]

Hi All,

I am trying to use AXL on CUCM 10.5 to fetch data about a routePattern using getRoutePattern. Most properties are returned except complex ones like destination and routePartitionName.

Request Xml:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5">

    <soapenv:Header />

    <soapenv:Body>

        <ns:getRoutePattern>

  <pattern>12345</pattern>

  <returnedTags>

  <pattern/>

  <routePatitionName />

  <provideOutsideDialtone/>

  <destination><gatewayName /></destination>

  </returnedTags>

        </ns:getRoutePattern>

    </soapenv:Body>

</soapenv:Envelope>

The response I get back:

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">

<soapenv:Body>

<ns:getRoutePatternResponse xmlns:ns="http://www.cisco.com/AXL/API/10.5">

<return>

  <routePattern uuid="{DCF3D735-7E74-FD60-DBB1-474831916C13}">

  <pattern>12345</pattern>

  <routePartitionName/>

  <provideOutsideDialtone>false</provideOutsideDialtone>

  <destination/>

  </routePattern>

</return></ns:getRoutePatternResponse></soapenv:Body></soapenv:Envelope>

The destination and routePartitionName are missing but they are set for this routePattern in CUCM.

Any help getting these values to return would be much appreciated.

Thanks in advance.

-Daniel

[npetrele]

Good find.  I was able to reproduce the problem here.  I will file a defect for this. 

[Daniel Appleby]

Oddly enough it works when the routePartitionName is included in the search query

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/10.5">

    <soapenv:Header />

    <soapenv:Body>

        <ns:getRoutePattern>

  <pattern>12345</pattern>

<routePatitionName>PT-Test </routePatitionName>

  <returnedTags>

  <pattern/>

  <routePatitionName />

  <provideOutsideDialtone/>

  <destination><gatewayName /></destination>

  </returnedTags>

        </ns:getRoutePattern>

    </soapenv:Body>

</soapenv:Envelope>

[npetrele]

That makes sense, now that I think of it.  A single line can have more than one route partition, depending on your setup. For example, I have a test line 7101 set up with two route partitions because the number is used in a hunt list and is assigned to a phone. The entry in the hunt list points to a different route partition than the one for the phone.  I can see that when I use the Admin UI and go to Call Routing->Route Plan Report.

So it makes sense that you'd need to specify the route partition in the search parameters to get the information you need for that line/route partition combo.  So this is probably not a bug at all. 

[stephan.steiner]

could this be a remant of the old days where (iirc) you could run a lot of commands with non unique identifiers and still get a Response? The Documentation states that if you're going to select with pattern, routePartitionName, routeFilterName and under certain conditions, dialPlanName are also mandatory.