Model: data/DeviceProfileConfigMapping

Mapping Profiles

The mapping profiles define the list of phone types that can be selected, and includes:

• Profile name
• Profile items: Phone type, Protocol, Button template, Security profile
• Base configuration template (CFT)

The value in the Profile Name field is presented to the lower-level administrator user in Phone drop-downs in the Admin Portal.

For example, if the administrator selects "Cisco 7841", then:

• The phone is provisioned as a "Cisco 7841" SIP device
• The phone will have a button template called Standard 7841 SIP
• The phone will a security profile called Cisco 7841 - Standard SIP Non-Secure Profile
• The phone configuration will come from a basic CFT called Basic Phone CFT

Feature Templates

The Feature Templates section of the Phone and Device Profile configuration mapping allows a higher-level administrator to configure a list of Feature Configuration Template CFTs, providing different configurations to complete the setting of the phone, device profile or line.

The image shows the list of available Feature templates:

The Feature templates are presented to the lower-level administrator as the list of templates (phone, device profile or line) that can be chosen when adding either a phone, extension mobility, or line. The Feature templates will contain the additional configuration settings that are applied on top of the settings mentioned above.

Macros for Phone Configuration Mapping

The table describes the available context macro variables when defining configuration templates for the phone mappings:

Device Profile Configuration Mapping

There may only be one device profile configuration mapping at any hierarchy, and the name of this mapping (at any hierarchy) must be Default.

The setup for device profile configuration mapping is identical to the phone configuration mapping. The phone type list and Feature* templates are presented to the administrator when adding an extension mobility service to a subscriber via the Subscriber Management page. See Feature Templates under Phone Configuration Mapping.

Line Configuration Mapping

There may only be one line configuration mapping at any hierarchy, and this line configuration mapping (at any hierarchy) must be Default.

A list of line templates can be configured and these will be presented to the administrator when new lines are be created, for example when adding a new phone.

Macros for Line Configuration Mapping

The table describes the available context macro variables when defining configuration templates for the line mappings:

The table describes the named macros that can be used when defining configuration templates for the line mappingse. High-level administrators with access to data/Macro can inspect and evaluate these named macros to verify result values. For details on Configuration Template customizations, see the Advanced Configuration Guide.

• For callingSearchSpaceName

  {{ macro.CUCM_LINE_callForwardAll_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardAlternateParty_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardBusy_callingSearchSpaceName-2 }}
  {{ macro.CUCM_LINE_callForwardBusyInt_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardNoAnswer_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardNoAnswerInt_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardNoCoverage_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardNoCoverageInt_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardNotRegistered_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardOnFailure_callingSearchSpaceName }}
  {{ macro.CUCM_LINE_callForwardOnFailure_callingSearchSpaceName }}
  

• For presenceGroupName

  {{ macro.CUCM_LINE_presenceGroupName }}
  

• For routePartitionName

  {{ macro.CUCM_LINE_routePartitionName }}
  

• For secondaryCallingSearchSpaceName

  {{ macro.CUCM_LINE_callForwardAll_secondaryCallingSearchSpaceName }}
  

• For voiceMailProfileName

  {{ macro.CUCM_LINE_vmprofile }}