Remove Dirn/route plan

[jacob.hansen]

We're in the process of switching to Skype, and we'd like to automate the process as much as possible. Now it's been releatively easy for us to remove devices, but inorder to be able to create a new rooute pattern, we need to remove the old unassigned directory number from the routing plan.

Anyone know how to do this?

[jacob.hansen · Accepted solution]

Figured out you needed routePartitionName as well as pattern for some reason.

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

  <soapenv:Header/>

  <soapenv:Body>

  <ns:removeRoutePattern sequence=""?"">

  <pattern>x</pattern>

  <routePartitionName>x</routePartitionName>

  </ns:removeRoutePattern>

  </soapenv:Body>

  </soapenv:Envelope>

[npetrele]

You can use AXL for this, but you don't have to. You can remove all unassigned DNs in one operation in the web UI.

From the CUCM web UI, select Call Routing -> Route Plan Report.

In the Find dropdown, select Unassigned DN.  Click the Find button.

Now, just select all (there's a box at the top for that) and Delete Selected.

[jacob.hansen]

Thanks for the reply Nicholas,

I know that was a possibility, but we wanted to automate the entire process of moving 700-* numbers to skype for business.

Basically we're removing every device assosiated with a number, then we're removing the route patterns and then we're creating a new route pattern. It all works nice and dandy now, I just had a lot of trouble because the <pattern> attribute wasn't enough on it's own and the documentation was bad.

We do have 19 pages of unassigned directory numbers which I'm told are there for a reason. So it wouldn't be a simple matter of just removing all the unassigned numbers. Don't ask me why they're there for a reason though, I'm just a developer.