[Index]

Model: view/QuickSubscriber

Quick Add Subscriber

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Overview

VOSS Automate Quick Add Subscriber (QAS) for Cisco Unified Communications Manager (CUCM) provides a single page where you can:

• Add users to CUCM.
• Add users to voicemail and WebEx accounts.
• Provision users with services, such as Voice, Extension Mobility, Voicemail, Single Number Reach (SNR), and conferencing and collaboration services. For example, see Provision the Voice Service
• Add lines for CUCM users.
• Associate a device pool directly from the user interface to a subscriber's newly associated devices or services other than the device pool provided in the Site Defaults Doc (SDD) or reference Configuration Template (CFT) in the Quick Add Group (QAG). See Quick Add Subscriber Device Pool for details.
• Associate Calling Search Space (CSS) values to a subscriber's newly associated lines, devices, or services other than the CSS's provided in the Site Defaults Doc (SDD) or reference Configuration Template (CFT) in the Quick Add Group (QAG), by selecting a Class of Service (CoS) directly from the interface. See Quick Add Subscriber Class of Service for details.

User types supported by QAS

QAS for CUCM users supports several user types, including:

• LDAP users
• Cisco Unified Communications Manager (CUCM) integrated users
• LDAP-integrated users on CUCM
• Manually created users

Quick Add Groups and Quick Add Subscriber

You will need to choose a Quick Add Group (QAG) when adding a subscriber via QAS. If Webex App is enabled, select the QAG that configures the required Jabber devices.

QAS default template

To add subscribers using QAS, a default user template called "voicemailusertemplate" must exist on the CUCM. This default can be updated by editing the default CUC User Template value in the SDD.

Self-provisioned phones and QAS

For self-provisioned phones to show as being associated with a subscriber, perform a CUCM data sync after setting up a self-provisioned phone.

Updating a subscriber added via QAS

Any changes you want to make to a subscriber or their associated services after adding the subscriber via QAS is done from the relevant service menu items.

Enabling services via QAS

When adding a subscriber via Quick Add Subscriber (QAS), you can enable user services, such as voicemail, extension mobility, single number reach, conferencing (meetings), and collaboration (messaging) services (such as Webex App).

See also: Webex Teams Quick Add

The QAS page only displays services that are included in the entitlement profile you select on this page. For example, if the entitlement profile does not include voice services, the checkboxes for Voice, Jabber, and Self Service ID won't appear on the page. The selected entitlement profile also filters options available in the Phone Type drop-down (showing only devices enabled in the entitlement profile).

For the Voicemail service:

• Configuration settings are only available if the site's SDD has a default value on the CUC Defaults tab for the Default CUC Subscriber Template.

  The default value (voicemailusertemplate) should already exist on the CUCM and is automatically populated on an HCS system when a voicemail pilot is created.

• A CUC device must be configured at the related NDL (Network Device List) at site level.

• If the selected QAG specifies any CFT entries for UserPin or UserPassword, these are applied. Otherwise, the values from the User Template defined on CUC apply. For default CFTs, see: Quick Add Subscriber Group Default Model.

While the Admin Portal hides configuration settings for unavailable services, API and Bulk Load operations have provisioning workflow checks that check for the presence of the Default CUC User Template in the SDD and a configured WebEx Server in the NDL, before the selected services can be added.

A CUCM (call manager) must be configured at the subscriber's hierarchy. If this does not exist, the QAS bulk load transactions and API calls display the following warning: No Call Manager has been configured

Webex App Quick Add

Selecting the Webex App checkbox on the QAS page displays the Webex Teams User Template drop-down, where you can select a Webex Teams User Template to apply to the user.

• Choosing a template from the drop-down overrides the default user template referenced in the Quick Add User Group (QAG) associated with the user.
• If you don't select a Webex Teams User Template from the drop-down, the Webex App User Template referenced in the associated QAG is applied.

If you want customized values, clone the Webex Teams User Template (Customizations > Configuration Templates) and edit as required. The Webex Teams User Template for CUCM Calling provides for a Settings group of controls for the specification of Calling Behavior and provisioning of Jabber devices if relevant to the calling behavior.

Related Topics

• Provision Webex App

Add a CUCM User via Quick Add Subscriber

This procedure adds a CUCM user via Quick Add Subscriber (QAS).

Pre-requisites:

• To choose phones by their description or description and line, configure the Global Setting (Phones tab) for displaying additional information.
• Configure Quick Add Groups. See Quick Add Subscriber Groups
• If required, expose Device Pools and Class of Service in Quick Add Subscriber. See Expose Device Pools and Class of Service in Quick Add Subscriber
• Ensure the site defaults are correctly configured.

Perform these steps

1. Log in to the Admin Portal, then go to (default menus) Subscriber Management > Quick Add Subscriber.

2. On the User Details tab:

   • Select the username, and specify a first name and last name.

   • Fill out the user's email address, and define whether to send the user a welcome email.

   • Fill out a password and PIN.

   • Select an entitlement profile, and a Quick Add Group.

   • Choose a device pool.

   • Add lines, and choose a directory number.

     Alternatively, select Use next available line to automatically populate the Directory Number field with the next available line. The default for Use next available line is False (disabled).

   • Select Voice, then fill out the additional configuration fields that display when this option is chosen.

   • Select additional services, such as extension mobility, voicemail, Webex App, Single Number Reach (SNR), Jabber / Dual-Mode device, and define whether you wish to enable self provisioning for this user.

     Note

     When choosing a phone name, you can configure (via the Phones tab in the Global Settings), how phone names display in this field. For example, the drop-down may list phones by their description only (default) or by first line only, or by description plus first line. At this drop-down, you can search for the phone using relevant criteria, for example, first letters of a description or line numbers (depending on the Global Setting for phone display).

3. Save your changes.

Related Topics

Global Settings in the Core Feature Guide.

Quick Add Subscriber Device Pool

A Device Pool contains system, device, and location-related information, and is mandatory when adding a Subscriber using Quick Add Subscriber. A Device Pool can be referenced by:

• Site Defaults Doc (SDD)
• Reference Configuration Template (CFT) referenced in the Quick Add Subscriber Group (QAG)
• Admin Portal (if exposed)

Site Defaults Doc

The Device Pool referenced in the SDD makes sure that a Subscriber's devices are always associated to a Device Pool. If there is no Device Pool referenced in either the QAG or Admin Portal drop-down (see below) the value defaults to the SDD.

Quick Add Subscriber Group (QAG)

The Device Pool referenced by a Configuration Template (CFT) in the QAG takes precedence over the Device Pool referenced in either the SDD or the Admin Portal drop-down (if exposed). See Quick Add Subscriber Groups for details.

Admin Portal

An Administrator can expose a Device Pool drop-down on the QAS page on the Admin Portal by editing or cloning the Field Display Policy. See Expose Device Pools and Class of Service in Quick Add Subscriber. The Device Pool drop-down allows an Administrator to overwrite the value in the SDD by selecting a custom Device Pool from the drop-down list. The options available in the list are the site-level Device Pools if they are available, otherwise it displays all Device Pools available at Customer level (NDLR aware).

Quick Add Subscriber Conditions

For details to provision services to users, follow these instructions:

• Provision the Voice Service
• Provision the Extension Mobility Service
• Provision the Voicemail Service
• Provision Webex App
• Provision the PexIP Conference Service
• Provision the Single Number Reach Service
• Provision the Jabber or Dual Mode Device Service
• Provision the Contact Center Agent
• Enable Self Provisioning

When creating users with the Quick Add Subscriber function, consider these conditions:

• A check box called Send welcome email is displayed when you type in a user email address only if the following configuration has been made and is enabled:

  • An SMTP server has been set up (SMTP Server)
  • The Allow email to be sent to user after Quick Add Subscriber on Email tab of the Global Settings is set to Yes for the relevant hierarchy (Global Settings)

  A welcome email is then sent to the subscriber email address using the configured "Quick Add Subscriber" HTML email template that applies to the hierarchy (Email)

• From the Quick Add Subscriber Group menu, create a custom group or use the default group.

• You can edit existing users on Cisco Unified Communications Manager (CUCM) through Quick Add Subscriber only if the users exist at the Site level.

  A check box called Include users at higher hierarchy can be displayed by means of a custom Field Display Policy (field name: lookUpForUser, hidden by default), so that the User drop-down list will also show users above the current site hierarchy. This setting is also available for bulk load sheets and API calls.

• A check box called Fail Transaction if user not found can be displayed by means of a custom Field Display Policy (field name: failIfNotFound, hidden by default) to prevent adding users not on Cisco Unified Communications Manager. By default, the transaction will not fail. The option is used for the case where users have not been synced from LDAP to Cisco Unified Communications Manager. This setting is also available for bulk load sheets and API calls.

• LDAP synced or LDAP integrated at Cisco Unified Communications Manager user fields are always read-only and cannot be edited.

• You can associate a Line with multiple phones.

• You can associate a Phone with multiple Lines.

• If you choose to add a Phone for the user, the Phone Name drop-down list will show available phones at the user's site, according to the Phone Type as specified in the Site Defaults for the site.

  The phones available from the drop-down list are those in the associated Quick Add Subscriber Group at the Customer level, which have synced from Unified CM, as well as the phones that are available at the specific site level.

  You can also add a new phone if required by entering a valid name in the Phone Name field. The Phone Name must consist of a prefix, for instance SEP, followed by a MAC address, which is 12 hexadecimal characters. If you enter the Phone Name incorrectly, for example too few or too many characters, then subsequent associated transactions will fail.

• Associate an Entitlement Profile with the Subscriber.

• You can create multiple devices for a user. Therefore, the Voice check box is always visible. When the Voice check box is selected, four optional fields are exposed: Phone Type, Phone Protocol, Phone Button Template, and Phone Security Profile.

• Values set in the Phone Type, Phone Protocol, Phone Button Template, and Phone Security Profile fields will override any existing values in QAG or CFT, as well as the SDD or any other backend CFTs (CFTs that can not be edited).

  If a specific phone type is not allowed in an entitlement profile, that phone type will not be displayed in the Phone Type drop-down list for a Subscriber associated to that entitlement profile.

  If a field is blank, the existing values in QAG, CFT, SDD or other backend CFTs will be used.

  If a Phone Template is not specified in QAG, or if the specified Phone Template has blank values for the phone fields, then the phone field values are pulled from the SDD.

  You can override the default Phone Button Template value by entering a custom value in the Phone Button Template field. The entered value will be applied on Unified CM if the Unified CM allows it for that phone type.

  Note

  To reduce the likelihood of conflicting QAS settings when completing the optional fields mentioned above, we strongly recommend setting the required fields in the order as displayed on the Quick Add Subscriber screen:

  1. Entitlement Profile
  2. Quick Add Group
  3. Voice (Phone Type, Phone Protocol, Phone Button Template and Phone Security Profile).

• You can set only one Extension Mobility profile for a user. Therefore, the Extension Mobility check box is not visible after you create an Extension Mobility profile.

• You can set only one WebEx account for a user.

• See Contact Center Agent Quick Add.

• You can associate multiple Jabber and Dual Mode devices to a user.

• Jabber and Dual Mode devices get the first line assigned to them that is specified in the QAS form.

• You can create a Directory Number in Unified Communications Manager in two ways:

  • By creating a Voicemail Line in QAS.
  • By creating a Line in QAS.

  When you create a Voicemail or Voicemail Line using Quick Add Subscriber, the Directory Number Used field is set to "true" under Subscriber Management > Directory Number Inventory.

• A Directory Number created without any device associations (for example, a Voicemail Line) is tagged under Subscriber Management > Lines as 'DN created without device from QAS.'

• When the Enable Self Provisioning check box is selected, phone lines are added using the Universal Line Template (ULT) referenced in the Self Provisioning User Profile chosen from the Self Provisioning User Profile drop-down list which is exposed upon selecting the check box.

  If a User is added with lines but no devices, then selecting the Enable Self Provisioning check box automatically sets the CUCM User Primary Extension to the QAS line pattern and ULT route partition. If a user is added with devices and lines, then selecting this check box also automatically sets the CUCM User Primary Extension to the QAS line pattern and ULT route partition.

  Choose the required User Profile from the Self Provisioning User Profile drop-down list. The available User Profiles are those under User Management > Self Provisioning > User Profile. A User Profile must be selected when a user is enabled for Self Provisioning. A default User Profile (as shown under Site Management > Site-Defaults) is selected. Change this default if required.

Contact Center Agent Quick Add

refer to UCCX Feature Reference

The Quick Add Subscriber feature supports the easy creation of an UCCX agent.

The Contact Center Agent check box becomes visible if:

• the associated Entitlement Profile has Contact Center enabled
• a Contact Center Server is available at the hierarchy - Contact Center Servers
• the selected user is not already associated with an Agent

If the check box is selected:

• A Contact Center Agent Profile drop-down list is available to select an agent profile.

  Note

  The Contact Center Agent Profile needs to be created before adding the Contact Center Agent from the Quick Add Subscriber feature.

  The agent profile will determine the team, resource group and skills assigned to the newly created agent. See: Agent Profiles.

• The Agent Extension can be selected.

  The extension will be a list of specified Lines, in other words, the administrator must specify the Line to be created or reused before selecting the Contact Center check box.

• The Agent Device Type can be selected: either Extension Mobility or Phone:

  • If Extension Mobility is selected, the Extension Mobility check box is automatically enabled.
  • If Phone is selected, the administrator must first enable Voice and specify a Phone to be created or reused before selecting the Contact Center check box.

An IPCC extension is automatically managed for the Unified CM user associated with the Contact Center Agent.

Related Topics

Introduction to Entitlement in the Core Feature Guide

Provision the Extension Mobility Service

Overview

In VOSS Automate, enabling extension mobility via Quick Add Subscriber (QAS) creates a device profile for the user on CallManager (the call processing component of CUCM).

A CUCM user device profile may be considered a dummy phone with lines. When the user logs in to a physical phone associated with the CallManager and enters their username and pin, CallManager applies their device profile to the phone (with their line, settings, and extension number), effectively assigning ownership of the phone to the user for the period they're logged in.

Provided a user is logged in to a physical phone via their device profile username and pin, they're always reachable via the extension number assigned to their device profile, regardless of the physical device they're using. The user's extension number is associated with their device profile and not to a physical device and is thus always 'mobile'.

Related Topics

Introduction to EMCC in the Core Feature Guide

Configuration Templates in the Core Feature Guide

Extension Mobility Profiles in the Core Feature Guide

EMCC and Multi-Cluster CallManager

A large organization (set up at the VOSS Automate Customer hierarchy) may have multiple CallManager clusters (separate CallManager servers in a multi-cluster setup). For example, a CallManager cluster located in London (providing phones and services to the London office), and a CallManager cluster located in New York (providing phones and services to the New York office). In this scenario, CallManager allows inter-cluster calls between these locations; each CallManager has a different IP address, and each has different data (the phones, users, and services, for either London or New York, in this case).

A CUCM administrator configures cross-cluster via the CUCM Extension Mobility Cross Cluster (EMCC) feature settings on CUCM, and in VOSS Automate (via Customer Management > EMCC).

Once configured on CUCM, EMCC may be enabled per user in CUCM, and a EMCC calling search space (CSS) is chosen for the user device profile.

A user enabled for EMCC can use their extension at another location that is part of the cluster. For example, a user can log in to a desk phone in London in the morning, travel to New York, and log in to a desk phone at the New York office when they arrive. Regardless of their physical location, the user remains reachable via the same extension number, provided they're logged in to a physical phone in a connected cluster, using their home cluster device profile username and pin.

Quick Add Subscriber and Configuration Templates

QAS references a selected QAG, which contains a number of configuration templates that define values for various settings. For example, the CUCM user template, or the extension mobility template (which defines the user device profile settings). For example, you can assign to the QAG, a CUCM user template that has Enable Extension Mobility Cross Cluster set to True, so that all subscribers added via QAS with this QAG are automatically enabled for EMCC.

Device Profiles and Extension Mobility Profiles

A CallManager device profile is called an extension mobility profile in VOSS Automate. Device profiles are configured in VOSS Automate via device profile configuration templates. EMCC CSS may be automatically assigned via device profile configuration template.

Assigning Extension Mobility via QAS

1. Go to Subscriber Management > Quick Add Subscriber, and choose a user from the Username drop-down list.

2. Select Extension Mobility.

3. To enable EMCC, select EMCC.

   Note

   The EMCC checkbox displays only if you've selected the Extension Mobility checkbox.

4. Click Save.

   • The CUCM user is added on CUCM.
   • The CUCM device profile user is added on CUCM, based on settings in the device profile configuration template in the QAG.
   • The device profile is associated with the CUCM user.
   • If you've enabled EMCC:
     • EMCC is enabled for the device profile on CUCM.
     • The EMCC calling search space (CSS) is set for the device profile. The CSS name is based on the country associated with the site, for example, EMCC-CSS-USA
     • The device profile is subscribed to the EMCC Login/Logout phone service on CUCM (which will allow the user to log in and log out of a physical device to use their extension remotely). VOSS Automate requires this service to exist on CUCM, or the provisioning will fail.

5. Verify that the extension mobility profile name appears in the Extension Mobility Profiles field on the Existing Services tab.

Provision the Voicemail Service

1. Choose Subscriber Management > Subscribers. From the Subscribers list, click on the name of the subscriber to be provisioned with voicemail.

2. Choose the Voicemail tab.

3. In the Voicemail Account field, click +. The Voicemail Line drop-down appears.

4. Choose a line from the Voicemail Line drop-down and click OK.

   For details on the workflow, see Voicemail.

5. Choose Subscriber Management > Quick Add Subscriber, and choose the same user from the Username drop-down list.

6. Choose the Existing Services tab.

7. Make sure that the voicemail line appears in the Voicemail Extension field.

Provision Webex Service

This procedure enables a subscriber for the Webex service.

1. In the Admin Portal, go to (default menus) Subscriber Management > Subscribers.
2. From the Subscribers list, click the name of the subscriber to be provisioned with WebEx service.
3. Select the WebEx tab.
4. In the WebEx User field, click the Plus icon (+) to display the Webex configuration fields.
5. Fill out the following details: First Name, Last Name, Email, Password
6. In the Privilege section, select relevant Webex privileges.
7. Click OK.
8. Go to (default menus) Subscriber Management > Quick Add Subscriber, and choose the same user from the Username drop-down.
9. Select the Existing Services tab, and ensure that "ACTIVATED" appears in the WebEx field.

Related Topics

• Provision Webex App

Provision the Single Number Reach Service

Procedure

1. Choose Subscriber Management > Quick Add Subscriber, and choose the user for whom you want to provision Single Number Reach from the Username drop-down list.

2. Choose the Single Number Reach tab. The SNR Mobile Number field appears.

3. In the SNR Mobile Number field, optionally enter the mobile number. Do not add any spaces or special characters to the number.

   The SNR Mobile Number can be the same as the user's Mobile Number shown in User Management > Users.

4. Click Save.

5. Choose Subscriber Management > Quick Add Subscriber, and choose the same user from the Username drop-down list.

6. Choose the Existing Services tab.

7. Make sure that the Single Number Reach displays the Single Number Reach profile name.

   The Single Number Reach profile name is the user name followed by "-RDP". For example: jsmith-RDP.

Provision the Jabber or Dual Mode Device Service

This procedure provisions a subscriber with the Jabber or dual mode device service, using Quick Add Subscriber (QAS).

1. Go to (default menus) Subscriber Management > Quick Add Subscriber.

2. From the Username drop-down, choose a user.

3. Select the Jabber/Dual-Mode Device check box. The Jabber and Dual-Mode Devices field appears.

4. Click the Plus icon (+) at Jabber and Dual-Mode Devices to expose the Jabber/Dual Mode Agent drop-down and Device Name field.

5. At Jabber/Dual Mode Agent, choose a device type. The Device Name field is automatically generated as follows:

   1. If no device name exists in the format <device type prefix><username>, then in this format:

      <device type prefix><username>

   2. If device name exists in the format <device type prefix><username> or <device type prefix><username><number>, then in the format:

      <device type prefix><username><random number>

      where <random number> is generated and unique.

   • <device type prefix> - always three characters, either BOT, CSF, TAB, TCT, CIM, or CTI.
   • <username> - 8 characters maximum. If a username contains '_' and '.' characters, these characters are removed from the automatically generated username. Automatically generated usernames can be edited if required.
   • <random number> - dependent on length of username, to make up a total of 11 characters along with the username.

   See examples in table below.

   Example Device Type and Device Name Combinations

   For this type of device	Device Name (automatically generated) Format (regex): "[a-zA-Z0-9]{1,15}"
   Android (Cisco Dual Mode for Android)	For example: BOTJOHND003938
   CSF (Cisco Unified Client Services Framework)	For example: CSFROBWOR77891
   iPad (Cisco Jabber for Tablet)	For example: TABRQUENT18947
   iPhone (Cisco Dual Mode for iPhone)	For example: TCTPDEVILLI156
   Carrier Integrated Mobile	For example: CIMJOHNSMI
   CTI Remote Device	For example: CTIJOHNSMI

   For the following Agents, also select the Mobile Identity checkbox to enable Mobile Identity if required:

   • Android
   • iPhone
   • Carrier Integrated Mobile

6. Click Save.

7. Go to Subscriber Management > Quick Add Subscriber.

8. From the Username list, choose the same user.

9. On the Existing Services tab, ensure that the Phones field displays the Jabber device.

For each device type, a Configuration Template that is associated with the Subscriber's Quick Add Group is used to provision the device. For defaults, see: Quick Add Subscriber Group Default Model.

Enable Self Provisioning

This procedure enables self-provisioning for a subscriber using Quick Add Subscriber (QAS).

1. Go to (default menus) Subscriber Management > Quick Add Subscriber. From the Username drop-down list, select a user.
2. Select the Enable Self Provisioning checkbox. The Self Provisioning User Profile drop-down appears.
3. From the Self Provisioning User Profile drop-down, choose a Self Provisioning User Profile. These were previously created under User Management > Self Provisioning > User Profile.
4. In the Lines field, click the Plus icon (+) to display the Directory Number drop-down.
5. Choose a line from the Directory Number drop-down.
6. Click Save.
7. Go to Subscriber Management > Subscribers and choose the same user from the Subscribers list view.
8. Verify that the Self Service and User Profile fields display the same settings as those set in Quick Add Subscriber.

Enhanced INI Filtering

If the Enhanced INI Filtering feature is enabled, administrators have access to the Inventory Filter dropdown list menu for lines on the following forms:

• Phones
• Quick Add Subscriber
• Subscribers

The filter would typically be used to show a filtered, shorter dropdown list of directory numbers.

The following options are available in the Inventory Filter list:

• Default

  This filter - enabled by default - corresponds with the standard filter of Directory Numbers:

  • used and unused INI numbers above and at the current hierarchy.
  • used and unused Associated E164 numbers above and at the current hierarchy.

• Show Unused Numbers with Associated E164's (Site Only)

  • Shows unused INI numbers with Associated E164 numbers at the current site only.
  • Format is: <INI number> <E164 number>. Example: 99003 \+279990003.

• Show Unused Numbers with Associated E164's

  • Shows unused INI numbers with Associated E164 numbers above and at the current hierarchy.
  • Format is: <INI number> <E164 number>. Example: 99003 \+279990003.

• Show Used Numbers (Site Only)

  • Shows used numbers at the current site only.
  • Format is: <INI number> (used) or <INI number> (used) <E164 number>. Example: 99000 (used) \+279990000.

• Show Used Numbers

  • Shows used numbers above and at the current hierarchy.
  • Format is: <INI number> (used) or <INI number> (used) <E164 number>. Example: 99000 (used) \+279990000.

• Show Numbers belonging to this Subscriber

  • The option shows results if a subscriber is selected on the Quick Add Subscriber or Subscriber form, or is associated with the selected phone on the Phones form.
  • Format is: <INI number> (used) or <INI number> (used) <E164 number>. Example: 99000 (used) \+279990000.

Quick Add Subscriber Class of Service

A Class of Service (CoS) allows the user to specify a Calling Search Space (CSS) for devices and lines, respectively. A CSS, in turn, is mandatory for lines and devices when adding a Subscriber using Quick Add Subscriber. A Calling Search Space can be referenced by:

• Site Defaults Doc (SDD)
• Reference Configuration Template (CFT) referenced in the Quick Add Subscriber Group (QAG)
• Admin Portal via the Class of Service field (if exposed)

Site Defaults Doc

The Calling Search Space values referenced in the SDD ensure that a Subscriber's lines and devices always have a Calling Search Space associated to it. If there are no Calling Search Space values referenced in either the QAG or via the Class of Service field in the Admin Portal drop-down (see below) the value defaults to the SDD.

Quick Add Subscriber Group (QAG)

The Calling Search Space values referenced by a Configuration Template (CFT) in the QAG take precedence over the Calling Search Space values referenced in either the SDD or the Class of Service via the Admin Portal drop-down (if exposed). See Quick Add Subscriber Groups for details.

Admin Portal

An Administrator can expose a Class of Service drop-down on the QAS page on the Admin Portal by editing or cloning the Field Display Policy. See Expose Device Pools and Class of Service in Quick Add Subscriber. The Class of Service drop-down allows an Administrator to overwrite the Calling Search Space values in the SDD by selecting a custom Class of Service from the drop-down list. The Class of Service, in turn, contains a custom Calling Search Space for Lines and Devices respectively. The options available in the list are the customer level Class of Service instances, as created by the relevant administrator.

Expose Device Pools and Class of Service in Quick Add Subscriber

Administrators with access to Field Display Policies (FDP) can expose the Device Pools field and Class of Service (CoS) field on the Quick Add Subscriber (QAS) interface at a specific hierarchy.

1. As an administrator with access to Field Display Policies (FDP), choose Customizations > Field Display Policies.
2. Filter the Target Model Type on view/QuickSubscriber.
3. Depending on which hierarchy or hierarchies the Device Pools or Class of Service field should be exposed in QAS:
   1. If the FDP exists at the correct hierarchy, open it.
   2. If the FDP does not exist at the required hierarchy, clone one of the available FDP's on a higher hierarchy to the required hierarchy (use Actions > Clone).
4. Open the FDP and go to the first group's Available list in the Fields block. Select device_pool or class_of_service.
5. Click on the Select button to move the device_pool or class_of_service label from the Available list to the Selected list.
6. Use the Move up and Move down buttons to move the label to the desired position relative the the other field labels.
7. Ensure that the cloned FDP name is "default", and click Save.

If an administrator is at the hierarchy where the cloned FDP is created or at a lower hierarchy, and then navigates to Subscriber Management > Quick Add Subscriber, a drop-down field with the title: Device Pools or Class of Service is exposed.

Model Details: view/QuickSubscriber