Overriding Unified CM Group¶
The default Unified CM Group is used when creating the default device pool for a site when using Cisco Dial Plan Schema Types 1*4. This topic describes the steps for the users to use a Unified CM Group other than “Default” when deploying their site dial plan. The steps allow you to override the Default CM Group when deploying a site dial plan. The workflow that creates the default site device pool is hard-coded to use the Default CM Group when a site is created is as follows.
- HcsDpAddSiteSystemDataPWF
- Entire Country Dial Plan
- Dial Plan Schema Group (Type 1, 2, 3, 4, Shell)
- Device Pool (Device Management)
- Route List (Device Management)
- Hunt List (Subscriber management)
- Voice Mail Pilot Number Schema (VoiceMailService)
- Route List (Sip Gateway)
Log in as provider admin.
Set the hierarchy to the provider level.
Navigate to Dial Plan Management > Advanced Configuration > Dial Plan Schema Group.
On the Site Defaults tab, set the macro for the Default CUCM Group from:
{{ macro.DEFAULT_CUCM_GROUP }} = (( fn.is_site == True )) <{{ data.SiteDefaultsDoc.defaultcucmgroup }}><{{ fn.null }}>
to
{{ macro.DEFAULT_CUCM_GROUP }} = (( fn.is_site == True )) <{{ data.SiteDefaultsDoc.defaultcucmgroup }}><Default>
Setting the macro to Default returns the value of Default CUCM Group from the SDD if evaluated at site hierarchy, else it returns Default. This setting pushes the new or customized Unified CM groups in any workflow at the site hierarchy.
Note
If you delete the Default Unified CM group from the Unified CM, deployment of the Unified CM group fails, which isn’t at site hierarchy. In this scenario, change the macro DEFAULT_CUCM_GROUP implementation and modify the
{{ data.SiteDefaultsDoc.defaultcucmgroup }}><CUSTOM_GROUP NAME>
