I have on my lab environment a CUCM Publisher and a CUCM Subs.
As I understand, the subscriber is only there for redundancy purposes, and the phone should be registered to the subs as opose to the pub.
All my IP phones register to the subscriber, but when I kill my publisher, all the phones are losing its registration.
Aren't they meant to be still registered?
What you need to do is to use cucm group and device pool for redundancy.
SO in your cucm group you will have your subscriber first and your publish second. You will then assign this cucm group to a device pool and then assign the device pool to the phone.
Now when your subscriber is down, the phones will register to your publisher. This is only good for small deployments. For large deployments you will have multiple subscribers and you will then have first subscriber and second and third. You can only have 3 servers in a cucm group. So the phones can register to secondary and tertiary subscribers when the primary is down
Please rate useful posts
you might want to run utils network connectivity on the sub and see if it completes successfully.
any fw between the pub and sub..
its definitely a db replication problem.
if the above tests that i mentioned above are successfull including utils network connectity. you would want to run a stop and roll.
utils dbreplication stop on the sub (wait for it to complete)
utils dbreplication stop on pub
utils dbreplication reset all from the pub.