CUCM version 10.5 with Publisher down

[adrianic2003]

Hello,


We have the following scenario:

A client has 2 x data-centers where the CUCM nodes are deployed, as per below:
     Data Center 1 (DC1) :CUCM Pub, CUCM Sub2
     Data Center 2 (DC2) : CUCM TFTP, CUCM Sub1, CUCM Sub3

Extension Mobility service is running on 2 x CUCM nodes, one in DC1 (CUCM Pub) and one in DC2 (CUCM TFTP). The client would like to know:


If DC1 1 is down = CUCM Pub and Sub2 are down, but the CUCM servers in DC2 are up and running, and there is an IP Phone registered to Sub 1 in DC2:

Q1:    Can an End User PIN be changed for Extension Mobility users (in case it is expired) and that user be able to login into EM, when the CUCM Pub is down?

Q2:    Can any changes be done to ta device (like adding a DN, etc.) by accessing CUCM Sub1 web admin interface when the CUCM Pub is down?

Q3:    Will the changes be updated to CUCM Pub database once it comes online?

Thank you,
Adrian

[Deepak Rawat · Accepted solution]

Unfortunately none of the above will be possible as all the subscriber servers have only Read Access. Only the Publisher server had Read-Write both hence all the above operations will not work in case of publisher not available.

Regards

Deepak

[adrianic2003]

Thank you Deepak.

Adrian

[Deepak Rawat · Accepted solution]

No issues Adrian, please remember to mark the thread as Answered if there are no further questions on the topic. Adding to my previous response, you might want to look at below thread as well in case you want to achieve redundancy for EM so that users can still login into that if required to do so without the need of a new pin though:

https://communities.cisco.com/thread/30704?tstart=0

Regards

Deepak

[adrianic2003]

Sounds good. Thank you again Deepak,

Adrian

[Pramodh.vtb]

Adrianic,

Question 1 -
Answer : Yes, it is possible to change the EM pin when PUB is down [EM is a user facing feature, which can be replicated to PUB when it comes online from SUB. ]

Database modifications for user-facing call processing features are made on the subscriber servers to which the IP phones are registered. The subscriber servers then replicate these database modifications to all the other servers in the cluster, thus providing redundancy for the user-facing features.

Call Forward All (CFA)

•Message waiting indicator (MWI)
•Privacy Enable/Disable
•Extension Mobility login/logout
•Hunt Group login/logout
•Device Mobility
•Certificate Authority Proxy Function (CAPF) status for end users and applications users
•Credential hacking and authentication