A prospect customer of ours is having some issues with Auto registering phones, and it means that they now can't add new phones. The symptoms that they've put across to me are a little on the woolly side and we can't get remote access either!
Basically in CUCM 5.x they have the license report that tells them:
I havent got the exact wording, but the error the customer receives is along the lines that number of unused / pending licenses is preventing them from adding new phones.
Anyone care to explain what the "pending" field does? And why they might have ended up with pending licenses?
You are most welcome! There is no more DBLHelper for 5.x and beyond but there are some good methods to repair replication problems. This answer was recently provided by our good friend Java;
1) Run stop on all nodes that will be reset. Stop CLI will stop any currently running processes and give us a clean slate to restart replication.
2) Go to each server (that will be reset), get on the CLI, and run. "utils dbreplication stop"
3) On pub, run the "utils dbreplication stop" as well.
4) Then, (also on the pub) run "utils dbreplication reset all" command (to reset replication on the pub and ALL Subs.
The commands are described in this doc;
Hope this helps!