ciscoaxl VS netpalm

If you do go the AXL route however, you can control just about everything you want to in UCM. It allows you to be a lot more precise about exactly what you want to happen, at the cost of having to script it all out. You don't need to work with SOAP through Zeep if you use the already-build ciscoaxl Python module. While it's not the most fleshed out module, it's an excellent starting point. A lot of the common API elements/commands (like getPhones or addCallingSearchSpace) already have methods built for you. I've been getting by with just using their axl class as a base class and adding my own methods on top.

Netpalm (https://github.com/tbotnz/netpalm) is my goto for "if you actually need to talk to a device".

You might look at github.com/tbotnz/netpalm.

if you want something thats already been built checkout netpalm https://github.com/tbotnz/netpalm

Others have given you good answers. Another alternative is something like netpalm, which is just a service you deploy, and then you send it jobs via REST API, and it does all the direct interaction with the devices including balancing work over worker nodes and handling async, etc.

Made this, https://github.com/tbotnz/netpalm. Saves around $60k per year compared with $vendors orchestrator

Checkout https://github.com/tbotnz/netpalm

Script and netpalm for execution

Netpalm?