I'm wondering whether or not anyone has used SQL to modify the Numplan and DeviceNumPlanMap tables in order to migrate from a 4 to 6 digit dial plan. I have a small implementation so I figured I would make the few changes to route patterns/translation patterns/hunt pilto/etc... by hand. I wrote a stored procedure and have been testing it without any issues (at this point at least). All I'm changing is the DNOrPattern (Device table), the label (DeviceNumPlanMap) and deletions to CFBDestination/CFBIntDestination/PFFDestination/PFfIntDestination.
Yep I was going to say that.. Cisco doesnt like you to touch the SQL DB directly.
They have AXL which is an API to CallManager.
It is the supported way to provision and make changes to the database programatically. (if i even spelt that right ;)
You access via SOAP over HTTP requests.
Dont trust it completely though. It is supposed to be a middle ware layer to protect you from doing something stupid. But it has let me add duplicate route patterns before :)
You can download the AXL programming guide from Cisco web site, and if you go to the Developer Support Central you can get the XML schema etc.
You can get information out using pre-defined methods - getPhone, getLine etc
Or you can send a SQL query in.
You can then process the information and send back the modifications.
If you are doing this just once, then the initial BAT suggestion is a good one.. but learning AXL and writing some tools in the long run can save you a heap of time.