topic Re: using updateRouteList request to add the Route Group member does not work in Management

using updateRouteList request to add the Route Group member does not work

jdrinkwater — Mon, 21 Oct 2019 16:11:12 GMT

using updateRouteList request to add the Route Group member does not work

Trying to add the Route Group/Local Route Group using updateRouteList request. Does not produce any errors but does not add the members to Route List. Anyone having same problem?

Here is the request and response.

<axl:updateRouteList xmlns:axl="http://www.cisco.com/AXL/API/12.5">
<name>routelist6</name>
<addMembers>
<routeGroupName>routegroup1</routeGroupName>
<selectionOrder>1</selectionOrder>
<calledPartyTransformationMask>
</calledPartyTransformationMask>
<callingPartyTransformationMask>
</callingPartyTransformationMask>
<dialPlanWizardGenId>
</dialPlanWizardGenId>
<digitDiscardInstructionName uuid="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true">
</digitDiscardInstructionName>
<callingPartyPrefixDigits>
</callingPartyPrefixDigits>
<prefixDigitsOut>
</prefixDigitsOut>
<useFullyQualifiedCallingPartyNumber>Default</useFullyQualifiedCallingPartyNumber>
<callingPartyNumberingPlan>Cisco CallManager</callingPartyNumberingPlan>
<callingPartyNumberType>Cisco CallManager</callingPartyNumberType>
<calledPartyNumberingPlan>Cisco CallManager</calledPartyNumberingPlan>
<calledPartyNumberType>Cisco CallManager</calledPartyNumberType>
</addMembers>
</axl:updateRouteList>

<ns:updateRouteListResponse xmlns:ns="http://www.cisco.com/AXL/API/12.5">
<return>{8291F148-A0F2-3F11-E19C-649624AB04D8}</return>
</ns:updateRouteListResponse>

Re: using updateRouteList request to add the Route Group member does not work

dstaudt — Mon, 21 Oct 2019 20:48:36 GMT

It looks like you might be missing the <member> element surrounding the member info:

<axl:updateRouteList xmlns:axl="http://www.cisco.com/AXL/API/12.5">
    <name>routelist6</name>
    <addMembers>
        <member>
            <routeGroupName>routegroup1</routeGroupName>
            <selectionOrder>1</selectionOrder>
            <calledPartyTransformationMask></calledPartyTransformationMask>
            <callingPartyTransformationMask></callingPartyTransformationMask>
            <dialPlanWizardGenId></dialPlanWizardGenId>
            <digitDiscardInstructionName uuid="" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"></digitDiscardInstructionName>
            <callingPartyPrefixDigits></callingPartyPrefixDigits>
            <prefixDigitsOut></prefixDigitsOut>
            <useFullyQualifiedCallingPartyNumber>Default</useFullyQualifiedCallingPartyNumber>
            <callingPartyNumberingPlan>Cisco CallManager</callingPartyNumberingPlan>
            <callingPartyNumberType>Cisco CallManager</callingPartyNumberType>
            <calledPartyNumberingPlan>Cisco CallManager</calledPartyNumberingPlan>
            <calledPartyNumberType>Cisco CallManager</calledPartyNumberType>
        </member>
    </addMembers>
</axl:updateRouteList>

Re: using updateRouteList request to add the Route Group member does not work

thedd — Tue, 22 Oct 2019 06:58:34 GMT

I would always only use the elements i defintly need.

So everything what is not mandatory would not be in my xml.

This helps keeping the xml as simple as possible.

To Update a Route Group

I would use

<useFullyQualifiedCallingPartyNumber>Default</useFullyQualifiedCallingPartyNumber>

</member>

</addMembers>

Re: using updateRouteList request to add the Route Group member does not work

jdrinkwater — Tue, 22 Oct 2019 13:07:28 GMT

I figured out the problem. I was sending wrong format for the <digitDiscardInstructionName>. I just need to send the uuid as an attribute. Some reason it was not giving me an error which confused me.

Thanks for the reply!

Re: using updateRouteList request to add the Route Group member does not work

jdrinkwater — Tue, 22 Oct 2019 14:09:49 GMT

I tried with <member> and found out that I am sending the wrong format for <digitDisacardInstructionName> attribute. It seems to work now after the fix.

Thanks David!