04-05-2016 09:09 AM
Greetings,
I am trying to add a Route List via AXL and one member of the route list uses NANP:PreDot for digit deletion. AXL, however, responds the NANP:PreDot cannot be found. I can select NANP:PreDot from the GUI when I creat RLs by hand. Any ideas as to why AXL can't find it?
CUCM version is 8.6.2. Request and response are below.
Thanks,
Mike
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:axl="http://www.cisco.com/AXL/API/8.5"> |
<soapenv:Body> | |
<axl:addRouteList sequence="?"> | |
<routeList> | |
<name>RL-ISI-012-MRG1</name> | |
<description>Israel to MRG1 (Miragolf ARG)</description> | |
<callManagerGroupName>IDC-CMG-01</callManagerGroupName> | |
<routeListEnabled>true</routeListEnabled> | |
<members> | |
<member index="1"> | |
<routeGroupName>RG-ICT-IS-AMRSS</routeGroupName> | |
<selectionOrder>1</selectionOrder> | |
<calledPartyTransformationMask></calledPartyTransformationMask> | |
<callingPartyTransformationMask></callingPartyTransformationMask> | |
<callingSearchSpaceName></callingSearchSpaceName> | |
<digitDiscardInstructionName></digitDiscardInstructionName> | |
<prefixDigitsOut></prefixDigitsOut> | |
<callingPartyPrefixDigits></callingPartyPrefixDigits> | |
<useFullyQualifiedCallingPartyNumber></useFullyQualifiedCallingPartyNumber> | |
</member> | |
<member index="2"> | |
<routeGroupName>Standard Local Route Group</routeGroupName> | |
<selectionOrder>2</selectionOrder> | |
<calledPartyTransformationMask></calledPartyTransformationMask> | |
<callingPartyTransformationMask></callingPartyTransformationMask> | |
<callingSearchSpaceName></callingSearchSpaceName> | |
<digitDiscardInstructionName>NANP:PreDot</digitDiscardInstructionName> | |
<prefixDigitsOut>01253351553</prefixDigitsOut> | |
<callingPartyPrefixDigits></callingPartyPrefixDigits> | |
<useFullyQualifiedCallingPartyNumber></useFullyQualifiedCallingPartyNumber> | |
</member> | |
</members> | |
</routeList> | |
</axl:addRouteList> | |
</soapenv:Body> | |
</soapenv:Envelope> |
Result:
'xmlns:soapenv' => 'http://schemas.xmlsoap.org/soap/envelope/',
'soapenv:Body' => {
'soapenv:Fault' => {
'detail' => {
'axlError' => {
'axlmessage' => 'Item not valid: The specified NANP:PreDot was not found',
'request' => 'addRouteList',
'axlcode' => '5007'
}
},
'faultcode' => 'soapenv:Server',
'faultstring' => 'Item not valid: The specified NANP:PreDot was not found'
}
}
};
Solved! Go to Solution.
04-05-2016 11:00 AM
It looks like the values for <digitDiscardInstructionName> element do not directly match up with the UI. I configured a Route List with NANP:PreDot, and used AXL <getRouteList> to determine that the AXL enum looks to be 'PreDot':
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns:getRouteListResponse xmlns:ns="http://www.cisco.com/AXL/API/10.5">
<return>
<routeList uuid="{C65CB663-D6E2-9C35-0351-CC4E9EB1D7B7}">
<name>Test_RouteList</name>
<members>
<member>
<routeGroupName uuid="{00000000-1111-0000-0000-000000000000}">Standard Local Route Group</routeGroupName>
<digitDiscardInstructionName uuid="{714EAFFA-55C2-11D3-B52D-0008C7C6A4C6}">PreDot</digitDiscardInstructionName>
</member>
</members>
</routeList>
</return>
</ns:getRouteListResponse>
</soapenv:Body>
</soapenv:Envelope>
Checking the Data Dictionary, the 'routelist' table has a field 'fkdigitdiscardinstruction' which points to the 'digitdiscardinstruction' table, which shows the following list of values for 'name', which should correspond to what's in the UI:
admin:run sql select name from digitdiscardinstruction
name
================================
NoDigits
PreDot
10-10-Dialing
PreDot 10-10-Dialing
PreAt
PreAt 10-10-Dialing
11D->10D
PreDot 11D->10D
PreDot 11/10D->7D
PreAt 11D->10D
PreAt 11/10D->7D
Intl TollBypass
PreDot IntlTollBypass
PreAt IntlTollBypass
PreDot Trailing-#
PreDot IntlTollBypass Trailing-#
PreAt 11/10D->7D Trailing-#
PreAt Trailing-#
PreAt IntlTollBypass Trailing-#
PreAt 10-10-Dialing Trailing-#
PreAt 11D->10D Trailing-#
PreDot 10-10-Dialing Trailing-#
PreDot 11/10D->7D Trailing-#
PreDot 11D->10D Trailing-#
Intl TollBypass Trailing-#
Trailing-#
10-10-Dialing Trailing-#
11D->10D Trailing-#
11/10D->7D Trailing-#
11/10D->7D
PreDot IntlAccess IntlDirectDial
04-05-2016 11:00 AM
It looks like the values for <digitDiscardInstructionName> element do not directly match up with the UI. I configured a Route List with NANP:PreDot, and used AXL <getRouteList> to determine that the AXL enum looks to be 'PreDot':
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns:getRouteListResponse xmlns:ns="http://www.cisco.com/AXL/API/10.5">
<return>
<routeList uuid="{C65CB663-D6E2-9C35-0351-CC4E9EB1D7B7}">
<name>Test_RouteList</name>
<members>
<member>
<routeGroupName uuid="{00000000-1111-0000-0000-000000000000}">Standard Local Route Group</routeGroupName>
<digitDiscardInstructionName uuid="{714EAFFA-55C2-11D3-B52D-0008C7C6A4C6}">PreDot</digitDiscardInstructionName>
</member>
</members>
</routeList>
</return>
</ns:getRouteListResponse>
</soapenv:Body>
</soapenv:Envelope>
Checking the Data Dictionary, the 'routelist' table has a field 'fkdigitdiscardinstruction' which points to the 'digitdiscardinstruction' table, which shows the following list of values for 'name', which should correspond to what's in the UI:
admin:run sql select name from digitdiscardinstruction
name
================================
NoDigits
PreDot
10-10-Dialing
PreDot 10-10-Dialing
PreAt
PreAt 10-10-Dialing
11D->10D
PreDot 11D->10D
PreDot 11/10D->7D
PreAt 11D->10D
PreAt 11/10D->7D
Intl TollBypass
PreDot IntlTollBypass
PreAt IntlTollBypass
PreDot Trailing-#
PreDot IntlTollBypass Trailing-#
PreAt 11/10D->7D Trailing-#
PreAt Trailing-#
PreAt IntlTollBypass Trailing-#
PreAt 10-10-Dialing Trailing-#
PreAt 11D->10D Trailing-#
PreDot 10-10-Dialing Trailing-#
PreDot 11/10D->7D Trailing-#
PreDot 11D->10D Trailing-#
Intl TollBypass Trailing-#
Trailing-#
10-10-Dialing Trailing-#
11D->10D Trailing-#
11/10D->7D Trailing-#
11/10D->7D
PreDot IntlAccess IntlDirectDial
04-05-2016 11:08 AM
That was exactly it. I have been away from AXL for quite some time and had not thought of going this way to figure it out.
Thanks,
Mike
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide