--> A CUCM Cluster is a group of CUCM servers running the same version of CUCM that share the same database and resources to provide high availability of services for clients, transparent sharing of resources, features and enables system scalability.
--> When a failure occurs on one server in a cluster, resources are redirected to another server in the cluster.
--> Every cluster has only one publisher and the rest of the servers are called as subscribers.
--> Configuration is done only in publisher, however, we need to enable Cisco CallManager service on every subscriber not only on the publisher.
--> A publisher is also called as the first node, a subscriber is also known as the subsequent node.
--> Only the publisher needs to synchronize its clock with the lowest stratum NTP server, subscribers will get their time through NTP from publisher only.
--> The CUCM can support these two types:
Cluster:
--> Supports up to 30000 IP phones.
--> Can be scaled to a maximum of 20 Servers in which there can be a maximum of 1 Publisher, 8 Call Processing Subscribers, 2 TFTP servers, 9 Other Servers.
--> Call Processing Servers are the Servers which performs call routing, call controlling and call restriction services.
Supercluster (Mega Cluster) :
--> Requires Cisco BU approval via Cisco Accounts Team.
--> Supports upto 60000 IP phones.
--> Can be scaled to a maximum of 21 Servers in which there can be a maximum of 1 Publisher, 16 Call Processing Subscribers, 2 TFTP Servers, 2 Other servers.
There are two types of data communication between CUCM servers :
1) Database Replication :
- Read/write copy of the database is with the Publisher.
- The database is replicated to all Subscribers from Publisher.
- The Database replication is secured using embedded Red Hat Linux, ip tables dynamic firewall.
2) Cluster Communication :
ICCS Signaling :
- Used to replicate run-time data such as Registration of devices, Locations bandwidth, Shared Media Resources.
- This signaling runs only between the servers that have the "ccm.exe" service i.e the Call manager service running (Call Processing agents).
- Uses TCP ports 8002-8004.
CDR & CAR :
- Call Detail Records are logged by the Call Processing Engine taking the call.
- These are periodically pushed to the Publisher server.
- The Cisco CAR or any third party billing application server always points to and collects data from the Publisher.
Ref: Cisco.com
Md.Kareemoddin
CCIE # 54759
--> When a failure occurs on one server in a cluster, resources are redirected to another server in the cluster.
--> Every cluster has only one publisher and the rest of the servers are called as subscribers.
--> Configuration is done only in publisher, however, we need to enable Cisco CallManager service on every subscriber not only on the publisher.
--> A publisher is also called as the first node, a subscriber is also known as the subsequent node.
--> Only the publisher needs to synchronize its clock with the lowest stratum NTP server, subscribers will get their time through NTP from publisher only.
--> The CUCM can support these two types:
Cluster:
--> Supports up to 30000 IP phones.
--> Can be scaled to a maximum of 20 Servers in which there can be a maximum of 1 Publisher, 8 Call Processing Subscribers, 2 TFTP servers, 9 Other Servers.
--> Call Processing Servers are the Servers which performs call routing, call controlling and call restriction services.
Supercluster (Mega Cluster) :
--> Requires Cisco BU approval via Cisco Accounts Team.
--> Supports upto 60000 IP phones.
--> Can be scaled to a maximum of 21 Servers in which there can be a maximum of 1 Publisher, 16 Call Processing Subscribers, 2 TFTP Servers, 2 Other servers.
There are two types of data communication between CUCM servers :
1) Database Replication :
- Read/write copy of the database is with the Publisher.
- The database is replicated to all Subscribers from Publisher.
- The Database replication is secured using embedded Red Hat Linux, ip tables dynamic firewall.
2) Cluster Communication :
ICCS Signaling :
- Used to replicate run-time data such as Registration of devices, Locations bandwidth, Shared Media Resources.
- This signaling runs only between the servers that have the "ccm.exe" service i.e the Call manager service running (Call Processing agents).
- Uses TCP ports 8002-8004.
CDR & CAR :
- Call Detail Records are logged by the Call Processing Engine taking the call.
- These are periodically pushed to the Publisher server.
- The Cisco CAR or any third party billing application server always points to and collects data from the Publisher.
Ref: Cisco.com
Md.Kareemoddin
CCIE # 54759
0 Comments