topic Re: Using Phone Migration Feature using AXL in Management

Using Phone Migration Feature using AXL

stephan.steiner — Mon, 19 May 2025 11:00:52 GMT

Is there a way to use the 'Migration Phone' functionality of the CUCM admin interface through AXL? We're looking into a way to programmatically migrate phones.

Re: Using Phone Migration Feature using AXL

Elliot Dierksen — Mon, 19 May 2025 12:18:30 GMT

Are you asking about migrating phones from one CUCM cluster to another, or from CUCM to WxC?

Re: Using Phone Migration Feature using AXL

DavidStaudt — Mon, 19 May 2025 16:03:56 GMT

There doesn't appear to be anything in AXL proper to manage bulk admin of any kind 😕

There are a number of bat* tables described in the Data Dictionary that look like they would enable you to manage/schedule batch job things, with the perennial caveat of there being no programmatic mechanism for uploading the actual bat files (other than emulating the web UI.)

Re: Using Phone Migration Feature using AXL

TomTom1313 — Tue, 20 May 2025 06:26:08 GMT

Phone migration from one model to another (phone lifecycle) as it's possible via cucm webUI. One by one (initiated when the technician is in front of the phone), no (prior) bulk migration.

Re: Using Phone Migration Feature using AXL

Elliot Dierksen — Tue, 20 May 2025 11:24:20 GMT

I am not aware of how you could do that conversion in bulk as you would from the GUI one at a time. It shouldn't be terribly difficult to code it manually if you are comfortable with python. I would compare how a phone looks before and after the conversion so you could have a template. A large number of the data element could be copied directly. The dicey part is that you would have to delete the old phone, and then add the new phone.

Re: Using Phone Migration Feature using AXL

stephan.steiner — Wed, 21 May 2025 07:43:27 GMT

The question was just about the functionality - is there an API for it.

I've been doing AXL since CCM 4.x, so I'm aware of the alternatives - but if you load the full device, and modify, there's some things you need to figure out through trial & error - not every device type has every object. So, besides changing obvious things like phone button templates, there's certainly things in the 'product specific layout' that changes. And that's really where the rubber meets the road.

It would be great if Cisco adopted their 'API first' approach for CUCM, too. There's too many things you can do in CCMAdmin that there's no API for. CCMAdmin should be a frontend using AXL to talk to the CUCM.