[Index]

Model: data/LineConfigMapping

Device Profile Configuration Mapping

Configuration mapping is available for higher level administrators as a part of the overall Business Administration Portal configuration as well as for other purposes.

The mappings serve a number of purposes:

Phone Configuration Mapping

Note

Profiles

These mapping profiles define a list of phone types that can be selected along with:

The value in the Profile Name field will be presented to the lower level administrator user in Phone drop-downs inside the administration portal.

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

Note

The Base Configuration Template as well as the Feature Configuration Template may also contain profile item fields such as Phone Type and Protocol. In this case, the order of precedence for the values is:

  1. Feature Configuration Template
  2. Base Configuration Template
  3. Profile items

For example, a phone type specified in the Phone Type field under Profiles will be superceded by the phone type specified in the Base Configuration Template or Feature Configuration Template.

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.

A list of Feature templates available:

These will be presented to the lower level administrator as the list of templates (phone, device profile or line) for selection when adding a phone or extension mobility or line and will contain the additional configuration settings that are applied on top of the settings mentioned above.

Configuration Template Input Contexts

The following context macro variables are available when defining configuration templates for the phone mappings above.

Macro Description
{{ input.standalone }} Flag whether it is a standalone phone or being associated with a subscriber.
{{ input.username }} Username of the subscriber the phone is being associated with. Only when standalone is false.
{{ input.device_type }} The user selected device type. This in fact is the phone mapping profile name.
{{ input.template_name }} The user selected feature template.
{{ input.name }} The user entered phone name.
{# input.lines #} The user entered list of lines.
{{ input.lines.0.directory_number }} The number of the first line.
{{ input.lines.0.template_name }} The user selected line template.
{{ input.lines.0.label }} The user entered line label.
{{ input.lines.0.display }} The user entered line display.
{{ pwf.user }} Object containing all UCM user settings of the associated subscriber. Only when standalone is false.

Device Profile Configuration Mapping

Note

The setup for Device Profile configuration mapping is identical to that for Phone Configuration Mappings.

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 Templates

Note

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.

The following context macro variables are available when defining configuration templates for the line mappings. See Feature Templates under Phone Configuration Mapping.

Macro Description
{{ input.userid }} User ID for description.
{{ pwf.PassedLine.pattern }} Line pattern description.
{{ input.firstName }} User first name for Alerting name or ASCII Alerting name.
{{ input.lastName }} User last name for Alerting name or ASCII Alerting name.
{{ input.Phone.0.lines.line.0.dirn.pattern }} The destination.

The following are named macros that can be used when defining configuration templates for the line mappings above. 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, refer to the Advanced Configuration Guide.

Stores default Line Configuration Mappings.

Model Details: data/LineConfigMapping

Title Description Details
Name * Name of the Line Configuration Mapping. Default: Default
  • Field Name: name
  • Type: String
  • Default: Default
Line Templates List of line configuration templates. These template definitions will be available to users creating or managing phones.
  • Field Name: line_templates.[n]
  • Type: Array
Template Name * Name to be used for this line template. This is what will be displayed in dropdowns.
  • Field Name: line_templates.[n].template_name
  • Type: String
Configuration Template * Configuration template to use when provisioning lines when selected by the user.
  • Field Name: line_templates.[n].config_template
  • Type: String