Does anyone have an addroutepattern example that works?
I am getting http 200 ok, when I pass my axl request, but the route pattern never gets added... (See example below).
Also, it doesnt seem to pick up routepatterns like 9.@ because of the @ sign...
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> <SOAP-ENV:Body> <axl:addRoutePattern xmlns:axl="http://www.cisco.com/AXL/1.0" xsi:schemaLocation="http://www.cisco.com/AXL/1.0 http://192.168.200.90/schema/axlsoap.xsd" sequence="1234"> <newPattern><pattern>9.911</pattern><usage>Route</usage><routePartitionName>Denis-PSTN-911-PT</routePartitionName><blockEnable>False</blockEnable><calledPartyTransformationMask></calledPartyTransformationMask><callingPartyTransformationMask></callingPartyTransformationMask><useCallingPartyPhoneMask>Off</useCallingPartyPhoneMask><dialPlanName>NANPNorth American Numbering Plan</dialPlanName><dialPlanWizardGenId>0</dialPlanWizardGenId><digitDiscardInstructionName></digitDiscardInstructionName><messageWaiting>Lamp Off</messageWaiting><networkLocation>OffNet</networkLocation><patternUrgency>False</patternUrgency><prefixDigitsOut></prefixDigitsOut><routeFilterName>LD-RF</routeFilterName><destination><routeListName>911-RL</routeListName></destination></newPattern> </axl:addRoutePattern> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
Did you try what I suggested last time (create the element via ccmadmin, do a get operation, compare the result with what you're attempting to write).
I'm not 100% sure but the dialPlanName element looks suspect... I figure it would most likely either be "NANP" or "NANP North American Numbering Plan" or "North American Numbering Plan".
Also.. if you want examples.. without even saying which CCM version you might get something that doesn't work for you ;)
The AXL traces from the CCM also usually help.. it takes a bit longer to get them but often they explain why something misbehaves, despite AXL returning you no usable error (or even a success message.. I've had both happen to me more times than I care to remember).
Thanks for the reply. The values I'm passing in are copies from another get, the difference is the Route Pattern only.
(I am doing list pull and then from the list doing gets for each route pattern. I then copy the string of the last route pattern (values included) and change the pattern element as my test.
Anyway, I'll keep at this, thanks for the help.
Update, here is my packet (I've added some tags). It still doesnt add and I get 200 ok.
Here is what is being passed to call manager 4.2.3 (soap):
Here is the result of a get route pattern (xml output):
Here is my new packet I am sending (includes three tags at bottom) still not adding, still return 200 ok.
What still bugs me though with your attempts is that there's quite a difference between the pattern you're attempting to write and the one you use as a template. Could you manually create the pattern you need to write automatically, then perform a get to see what is returned (sometimes, the weirdest things happen and you need to create your objects manually in order to know what you need to write to have them created automatically).
Also, here's how you get the AXL traces from your CCM: they're being written to c:\program files\cisco\Trace\AXL)
I'm not sure how much of the errors you'll see though.. I haven't worked with CCM4 in a while and CCM5+ is really a step up in terms of traces.. those AXL traces actually contain DB error messages that even make sense (at least sometimes) and help you figure out what's going on.
Are you sure that's what you get? I have used the axl test tool (which is very buggy but I still haven't found the time to write my own, better one which works on all ccm versions that my axl lib supports). And if I do a get on my @ pattern, here's what I get back:
Note the difference with regards to the dialPlan... according to the schema, either a full dialPlan element has to be returned (giving at least an uuid and a name.. just like in the response I'm getting) or just a
Now I suspect that your dialplan is like mine.. so the name is NANP and the description is North American Numbering Plan - and since you send that contactenated as one dialPlanName tag, the ccm cannot find a match for the dialplan (so we're back to the element I found suspect).
Thanks for your responses. I did try to send just NANP as the dialPlanName and it didnt make a difference. I guess I could do a look up and grab the UUID, Name and Description and try with that set...
Re: the return, yes, thats what Im getting. I write the response of the get out directly to an xml file and thats what I get...
I'll take a look at trace.
Do you have a working addroutepattern? I know there is an issue with the digitDiscardInstructionName... its in the documentation but not returned... I am including it, I dont know if thats an issue?
Stephan, thanks for the AXL trace tip! I was able to see what was wrong.
First, you were correct, the dialPlanName did need to only be NANP regardless of the return of the concatenated name.
Second, the blockenable value was FALSE, it needed to be false. (Case Sensitive).
It also didnt like the provideOutsideDialTone tag, which because it wasnt required, I removed.
Thank you for your responses and your experience. I am guessing I will no longer have any trouble now that I am able to use the trace!