Solved: CCM 5.1 Extension mobility Redundancy

tmailula · ‎05-11-2008

I have a call manager Cluster version 5.1. One publisher and one subscriber. Actually every feature is in redundant mode apart extension mobility.90% of my users use extension mobility. Extension mobility feature needs to write on the publisher and replicates only the status on subscriber. If the publisher is down, all users using extension mobility are not able to login or logout, Is there a way to get the Ext Mobility up even when the Pub is down.

I want another publisher to replicate with the existing publisher. If one goes off, the second publisher will take over automatically.Is this a do-able can I have 2 publishers on 1 cluster or is it better to upgrade to CCM 6.x ??

Thanks in Advance

Rob Huffman · ‎05-11-2008

Hi Tau,

Hope all is well! You will need to go to CCM 6.x to have redundancy for EM. Here is the background (there is no way to do this on any CCM version until 6.x)

The configuration database is stored on a publisher server, and a read-only copy is replicated to the subscriber members of the cluster. Changes made on the publisher are communicated to the subscriber databases, ensuring that the configuration is consistent across the members of the cluster, as well as facilitating spatial redundancy of the database.

The publisher server is the only server that has read and write access to the configuration database. When configuration changes are made, other members of the cluster have a read-only copy of the database.

From this CCM SRND;

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/4x/42clproc.html

This changes with the release of CCM 6.x;

In prior versions of Cisco Unified Communications Manager, subscriber servers in the cluster use the publisher database for READ/WRITE access, and only use the local database for READ access when the publisher database cannot be reached. With Cisco Unified Communications Manager Release 6.0, subscriber servers in the cluster READ the local database. DB WRITES happens in both the local database as well as the publisher database, depending on the type of data. DBMS (IDS) replication is used to synchronize the databases on the nodes of the cluster. When recovering from a failover conditions such as loss of WAN connectivity for extended period of time, the Cisco Unified Communications Manager databases need to be synchronized with any changes that may have been made during the outage. This process happens automatically when database connectivity gets restored. This process may take longer over low bandwidth and/or higher delay links.

Database modifications for CallProcessing

User Facing features can be made on subscribers. These include updates for:

Call Forward All (CFA)

Message Waiting Indication (MWI)

Privacy Enable/Disable

Do Not Disturb Enable/Disable (DND)

Extension Mobility Login (EM)

Monitor (for future use, currently no updates at the user level)

Hunt Group Logout

Device Mobility

CTI CAPF status for end users and application users

Credential hacking and authentication

Hope this helps!

Rob

View solution in original post

Rob Huffman · ‎05-11-2008

Hi Tau,

Hope all is well! You will need to go to CCM 6.x to have redundancy for EM. Here is the background (there is no way to do this on any CCM version until 6.x)

The configuration database is stored on a publisher server, and a read-only copy is replicated to the subscriber members of the cluster. Changes made on the publisher are communicated to the subscriber databases, ensuring that the configuration is consistent across the members of the cluster, as well as facilitating spatial redundancy of the database.

The publisher server is the only server that has read and write access to the configuration database. When configuration changes are made, other members of the cluster have a read-only copy of the database.

From this CCM SRND;

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/srnd/4x/42clproc.html

This changes with the release of CCM 6.x;

In prior versions of Cisco Unified Communications Manager, subscriber servers in the cluster use the publisher database for READ/WRITE access, and only use the local database for READ access when the publisher database cannot be reached. With Cisco Unified Communications Manager Release 6.0, subscriber servers in the cluster READ the local database. DB WRITES happens in both the local database as well as the publisher database, depending on the type of data. DBMS (IDS) replication is used to synchronize the databases on the nodes of the cluster. When recovering from a failover conditions such as loss of WAN connectivity for extended period of time, the Cisco Unified Communications Manager databases need to be synchronized with any changes that may have been made during the outage. This process happens automatically when database connectivity gets restored. This process may take longer over low bandwidth and/or higher delay links.

Database modifications for CallProcessing

User Facing features can be made on subscribers. These include updates for:

Call Forward All (CFA)

Message Waiting Indication (MWI)

Privacy Enable/Disable

Do Not Disturb Enable/Disable (DND)

Extension Mobility Login (EM)

Monitor (for future use, currently no updates at the user level)

Hunt Group Logout

Device Mobility

CTI CAPF status for end users and application users

Credential hacking and authentication

Hope this helps!

Rob