CUCM groups are used for redundancy and call process load balancing using a prioritized list of CUCM primary, secondary and tertiary (backup) servers. When a device attempts to register to the primary server that may be unavailable, the device tries to register to the next secondary backup servers, if this secondary server is also unavailable the device tries the tertiary server (three CUCM servers can be listed).
Each device pool has one CUCM group assigned to it. The video shows two CUCM servers configured as backups of each other, the CUCM7PUB group has 192.168.199.10 as the primary the 192.168.199.11 as the secondary, and the CUCM7SUB has 192.168.199.11 as the primary and 192.168.199.10 as the secondary.
Note : CUCM disables autoregistration by default. Enabling autoregistration carries a security risk in that "rogue" phones can automatically register with CUCM. You should enable autoregistration only for brief periods when you want to perform bulk phone adds.
Before enabling auto-registration a protocol should be selected, such as SCCP or SIP, this is done in System > Enterprise Parameters > Auto Registration Phone Protocol
Auto-registration can be enabled by CUCM groups from System > Cisco Unified CM Group, when auto-registration is enabled on a CUCM group, the previous groups auto-registration is automatically disabled.
Auto-registration can be enabled on a specific CUCM (this server needs to be a member of the CUCM group that is configure for auto-registration) from System > Cisco Unified CM, here you must select a starting and and ending DN range, this automatically disables the "checkbox and enable auto-registration.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment