Buy or Renew
Buy or Renew
Cisco + Splunk: It’s a new day for your data. Learn more.
 
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
cancel
Start a conversation
562
Views
0
Helpful
9
Replies

Successful AddRoutePattern Example?

risiprekel
Level 1
Level 1

‎04-29-2008 12:17 PM - edited ‎03-13-2019 05:12 PM

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>

Labels:
0 Helpful
9 Replies 9

stephan.steiner
Spotlight
Spotlight

‎04-30-2008 06:10 AM

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).

0 Helpful

risiprekel
Level 1
Level 1
In response to stephan.steiner

‎04-30-2008 06:25 AM

Stephan,

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.

0 Helpful

risiprekel
Level 1
Level 1

‎04-30-2008 06:20 AM

Update, here is my packet (I've added some tags). It still doesnt add and I get 200 ok.

http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> 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"> 9.922RouteDenis-PSTN-911-PTFalseOffNANPNorth American Numbering Plan0Lamp OffOffNetFalseLD-RFDefaultDefaultDefaultDefaultFalseDefaultNo Error911-RL

0 Helpful

risiprekel
Level 1
Level 1

‎04-30-2008 06:33 AM

Here is what is being passed to call manager 4.2.3 (soap):

http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> 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">

9.922

Route

Denis-PSTN-911-PT

False

Off

NANPNorth American Numbering Plan

0

Lamp Off

OffNet

False

LD-RF

Default

Default

Default

Default

False

Default

No Error

911-RL

Here is the result of a get route pattern (xml output):

-

{B362067B-34D6-4FD6-A89A-B75031B3C613}

9.@

Route

Denis-PSTN-LD-PT

false

Off

NANPNorth American Numbering Plan

0

Lamp Off

OffNet

false

Local-RF

Default

Default

Default

Default

false

Default

No Error

false

true

PSTN-RL

false

0

false

0 Helpful

risiprekel
Level 1
Level 1
In response to risiprekel

‎04-30-2008 06:49 AM

Here is my new packet I am sending (includes three tags at bottom) still not adding, still return 200 ok.

http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema"> 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">

9.922

Route

Denis-PSTN-911-PT

False

Off

NANPNorth American Numbering Plan

0

Lamp Off

OffNet

False

LD-RF

Default

Default

Default

Default

false

Default

No Error

false

true

911-RL

false

0

false

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to risiprekel

‎04-30-2008 08:14 AM

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.

0 Helpful

stephan.steiner
Spotlight
Spotlight
In response to risiprekel

‎04-30-2008 08:27 AM

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:

0.@

International

Route

p_gateways

false

On

NANP

North American Numbering Plan

0

Lamp Off

OffNet

false

Default

Default

Default

Default

false

Default

No Error

false

true

10.145.4.85

false

0

false

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 tag.

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).

0 Helpful

risiprekel
Level 1
Level 1
In response to stephan.steiner

‎04-30-2008 09:12 AM

Hi Stephan,

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?

0 Helpful

risiprekel
Level 1
Level 1
In response to stephan.steiner

‎04-30-2008 09:31 AM

Working!

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!

0 Helpful
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Customers Also Viewed These Support Documents