[Index]

Model: relation/User

Users

From the default menu User Management > Users list view, users are shown at or below the current hierarchy node. The users can be created in the system in various ways, depending on your specific setup:

User creation can also vary across different hierarchies in the system.

Note the following user details:

Sync Source

The source application of user data, for example:

LOCAL indicates that the user has been manually created in VOSS-4-UC and has not been synced from LDAP or from Cisco Unified CM.

CUCM indicates that the user exists on both VOSS-4-UC and Cisco Unified CM, and is not synced from LDAP. The user may have been created first on VOSS-4-UC (top-down) or created on Cisco Unified CM and synced into VOSS-4-UC (bottom-up).

See: User Sync Source [1]
User Type

Administrators (Admin) who are users accessing the system in order to perform administrative activities

End users (End User) that will be set up with services in the system.
Auth Method See: User Authentication Methods [2]
[1]Sync Source: see: User Sync Source.
[2]Auth Method: see: User Authentication Methods.

Create a User

Users are typically added or updated on VOSS-4-UC from the sync source, e.g. LDAP, CUCM, CUC, etc. See User Sync Source for more details.

The Users form is primarily used to add or update Administrator (Admin) Users using VOSS-4-UC (see How to Create an Administrator User below).

Important

Sync Source precedence may override user input. If you update a user on VOSS-4-UC:

the data of these fields will be updated from the sync source and not the user input added in VOSS-4-UC. The Admin Portal would typically render these fields read-only.

Sync Source Scenarios

See also User Field Mapping.

How to Create an Administrator User

To manually create an Admin User:

  1. Log in at the hierarchy node where you want to create the Admin user.

  2. Open the Users form (default menu User Management > Users).

  3. Click Add.

  4. Complete the required mandatory and optional fields required for an Admin user on the tabs below.

    Note

    The interface of the Role will set the User Type. To add an Admin user, the interface of the Role needs to be "administrator".

  5. Click Save when complete. The Admin user is created.

User Details

Fields Description
User Name* Sign-in username. This field is mandatory.
Role* Choose the user's role. This field is mandatory.
Entitlement Profile Choose the entitlement profile that specifies which devices and services the user is entitled to.
Language

Choose the user's language.

Note:

If no language is selected, the language is inherited from the nearest hierarchy node (at or above the user) that has a default language configured. If no default language is configured anywhere in the hierarchy at or above the user, the user's language is English.

Note:

If a language is manually set for a user, that language remains unchanged even if the user is moved to a new place in the hierarchy. However, if the language is inherited, then the user's language changes when the user is moved to a hierarchy node that has a different default language.
Exclude from Directory If this check box is selected, the user will not appear in the corporate directory accessed via VOSS-4-UC Phone Services - [1]
Sync Source Identifies the application from which the user (and user data) was synced, i.e. LOCAL (VOSS-4-UC), CUCM or MS-LDAP. This field is read only.
User Type Cannot be edited - determined by the Role interface (administration / selfservice).
Auth Method

Identifies the authentication method for the user - [2]

This section is applicable to End Users only.

  • Local - VOSS-4-UC User
  • Automatic - If LDAP or SSO set at hierarchy or above, use this
  • LDAP - [3]
  • SSO - [4]
LDAP Server and Username Only editable when Auth Method is LDAP
LDAP Username Only editable when Auth Method is LDAP
SSO Identity Provider Only editable when Auth Method is SSO
SSO Username Only editable when Auth Method is SSO. Defaults to VOSS-4-UC username.
[1]See Phone Services Feature Setup
[2]See User Authentication Methods
[3]See View and Update LDAP Authentication Users
[4]See Single Sign On (SSO) Overview

Account Information

Fields Description
Account Information

The administrator can manage the user's account information, including:

  • Change Password on next Login
  • Credential Policy
  • Disabled (Y/N)
  • Reason for Disable
  • Time Locked Due to Failed Login Attempts
  • Time of Last Successful Login
  • Locked (Y/N)
  • Security Questions
  • Used Passwords

Contact Information

User contact information such as employee number, employee type, country, state, state, street, department, manager, Fax number, directory URL, Jabber ID, telephone number, mobile, IP phone, etc. This tab is applicable to End Users only.

Links

Provides direct hyperlinks to the associated user apps, such as: CUCM Subscriber, CUC User Voicemails, WebEx Teams user and UCCX Agent. This tab is applicable to End Users only.

Custom

User defined customized strings and booleans. This tab is applicable to End Users only.

Provisioning Status

Provides a view showing the composition of the user, this typically includes:

Select the Provisioned check box to view additional CUCM's if applicable. This tab is applicable to End Users only.

Note

See also: Update a User

Update a User

Users are typically added or updated on VOSS-4-UC from the sync source, e.g. LDAP, CUCM, CUC, etc. See User Sync Source for more details.

Important

Sync Source precedence may override user input. If you update a user on VOSS-4-UC:

Only the mapped fields will be updated from the sync source. The data of these fields will be updated from the sync source and not the user input added in VOSS-4-UC. The Admin Portal would typically render these fields read-only.

For user authentication method (Auth Method) changes upon updates, see Authentication Method Setting Rules.

Sync Source Scenarios

See also User Field Mapping.

Additional Info

Note

Updating an Admin user who has become a subscriber creates a sync with the application highest on the User Sync Source precedence, and according to the field mapping for that source. The sync occurs once you click Save.

If the Admin user password is updated, user passwords on Unified CM, Unity and WebEx are also updated if these have been provisioned for the user.

Note

Since different UC apps can have different password strictness rules, the update transaction will only succeed if the strictness rules of all the UC apps have been met. Otherwise, the update transaction will roll back.

Administrators should therefore choose a password that meets the requirements of all the UC apps.

On the button bar on the associated Users form, there are three additional actions available to manage a user:

See Create a User

Local Admins

Default local VOSS-4-UC administrators are created when provider, reseller, customer, and site hierarchy nodes are established. Use this procedure to modify or create more local administrators or operators. Also use this procedure to create administrators for intermediate nodes.

An administrator for a particular hierarchy level can create or modify the administrators and operators at that hierarchy level and any level below. For example, a Customer XYZ administrator can create other Customer XYZ administrators and site administrators for Customer XYZ.

Procedure

  1. Log in as an administrator.
  2. To create or modify an administrator or operator at a level below your current level, set the hierarchy path at the top of the window. If you have signed in as provider administrator, and want to create a customer administrator, set the hierarchy path to the customer for which you want to create the administrator.
  3. Open the Admins form (default menu User Management > Admins). Note that this form provides a subset of the tabs and fields available on the Users form - for more input field details, refer to Create a User.
  4. At a minimum, complete these fields:
Fields Description
Username Sign-in username. This field is mandatory.
Email Address User email address.
Role

Choose the administrator's role. This field is mandatory.

  • For a provider, reseller, customer, or site administrator or operator, the available roles are limited to those applicable to the hierarchy level.
  • For an intermediate node administrator or operator, the available roles are limited to those associated with the nearest non-intermediate node above the intermediate node in the hierarchy.
Password Set the password. This field is mandatory.
Language

Choose the administrator's language. Note:

If no language is chosen, the language is inherited from the nearest hierarchy node (at or above the administrator) that has a default language configured. If no default language is configured anywhere in the hierarchy at or above the administrator, the administrator's language is English.
Sync Source This is set LOCAL when the administrator is created on VOSS-4-UC.
User Type Cannot be edited - determined by the Role interface (administration / selfservice).
  1. To modify an existing administrator or operator, click the administrator or operator.
    1. Modify the appropriate settings for the administrator or operator.
    2. Click Save.

View and Update LDAP Authentication Users

All users that use LDAP for authentication are displayed on the Users form (default menu User Management > Users). This list includes users that use LDAP for authentication only, and users that have been synced from LDAP.

Note

To view LDAP Authentication Users only, filter the list to display LDAP users.

Procedure

  1. Log in as provider, reseller, or customer administrator.
  2. Choose User Management > Users.
  3. Filter on the Sync Source column to display LDAP users.
  4. Click Add to add a new LDAP user or select an existing LDAP user to update. For each user that uses LDAP for authentication the following information is displayed on the Account Information tab:
Field Description
LDAP Server The LDAP server being used for authentication.
LDAP Username Matches the value of the LDAP authentication attribute which is specified in the User Model Type field of the LDAP User Sync configuration.
  1. To disable LDAP authentication for a user, select the user and click Delete. LDAP Authentication for the user is removed from the Users list. Local authentication is used for the user to log in.
  2. To update LDAP authentication for a user, select the user, make the updates and click Save. You can update only the LDAP Username field. However, LDAP authentication fails if the corresponding change is not also done on LDAP.

User relation

Model Details: relation/User

Title Description Details
User Details Group Assigned by FDP
  • Field Name: User Details
  • Type: Object
User Name * The username corresponding to the the Username in Cisco Unified Communications Manager and Cisco Unity Connection server.
  • Field Name: User Details.username
  • Type: String
First Name The first name corresponding to the user first name in Cisco Unified Communications Manager and Cisco Unity Connection server.
  • Field Name: User Details.first_name
  • Type: String
Last Name The last name corresponding to user last name in Cisco Unified Communications Manager and Cisco Unity Connection server.
  • Field Name: User Details.last_name
  • Type: String
Display Name Display name of the user
  • Field Name: User Details.display_name
  • Type: String
Title Title.
  • Field Name: User Details.title
  • Type: String
Email Address The email address corresponding to the the Username in Cisco Unified Communications Manager and Cisco Unity Connection server.
  • Field Name: User Details.email
  • Type: String
Password The password corresponding to the user password in Cisco Unified Communications Manager. The password is hidden.
  • Field Name: User Details.password
  • Type: String
  • Is Password: True
  • Store Encrypted: True
  • Pattern: .{8,}
Role * The role to which the user belongs. See: Role.
  • Field Name: User Details.role
  • Type: String
  • Target: data/Role
  • Target attr: name
  • Format: uri
Entitlement Profile
  • Field Name: User Details.entitlement_profile
  • Type: String
  • Target: data/HcsEntitlementProfileDAT
  • MaxLength: 1024
  • Format: uri
Language The preferred language for this user. Default: en-us
  • Field Name: User Details.language
  • Type: String
  • Target: data/Language
  • Target attr: lcid
  • Default: en-us
  • Format: uri
Exclude from Directory Exclude from Directory flag to control the Phone Services directory lookup. If set to true the User's phone number will not appear in the directory lookup.
  • Field Name: User Details.exclude_from_directory
  • Type: Boolean
Auth Method The type of authentication that our user would be using. Typically this would be choices between a Standard VOSS 4 UC user, an LDAP user or an SSO user. Default: Local
  • Field Name: User Details.auth_method
  • Type: String
  • Default: Local
  • Choices: ["Local", "Automatic", "LDAP", "SSO"]
LDAP Server A reference to the LDAP server which this user must authenticate against.
  • Field Name: User Details.ldap_server
  • Type: String
  • Target: data/Ldap
  • Format: uri
LDAP Username The login attribute of the associated LDAP device model instance
  • Field Name: User Details.ldap_username
  • Type: String
SSO Identity Provider The entity id of the SSO Identity Provider.
  • Field Name: User Details.sso_idp
  • Type: String
  • Target: data/SsoIdentityProvider
  • Target attr: entity_id
  • Format: uri
SSO Username The name identifier that is used for an SSO authenticated user.
  • Field Name: User Details.sso_username
  • Type: String
Sync Source Sync source of the user. Identifies where the user was synced from. This value will determine the master of the data. The data in the User model will be derived from the fields of the master application (E.G. CUCM, CUC, MS-LDAP). Default: LOCAL
  • Field Name: User Details.sync_source
  • Type: String
  • Target: data/UserSyncSource
  • Target attr: name
  • Default: LOCAL
  • Format: uri
Sync Type Sync type of the user. Identifies the user type that was synced from device as indicated by Sync Source information, e.g. CUCM-Local, CUCM-LDAP, LOCAL. Default: LOCAL
  • Field Name: User Details.sync_type
  • Type: String
  • Default: LOCAL
User Type Indicate the user's login type. Default: Admin
  • Field Name: User Details.user_type
  • Type: String
  • Default: Admin
  • Choices: ["Admin", "End User"]
Account Information Group Assigned by FDP
  • Field Name: Account Information
  • Type: Object
Change Password on Next Login Indicates if the user must be forced to change their password the next time that login.
  • Field Name: Account Information.change_password_on_login
  • Type: Boolean
Account Information Additional account information for the given user.
  • Field Name: account_information
  • Type: Object
Change Password on Next Login Indicates if the user must be forced to change their password the next time that login.
  • Field Name: Account Information.account_information.change_password_on_login
  • Type: Boolean
Credential Policy Specifies the policy with the rules used to govern this user's credentials.
  • Field Name: Account Information.account_information.credential_policy
  • Type: String
  • Target: data/CredentialPolicy
  • Target attr: name
  • Format: uri
Disabled Indicates if the account has been disabled to prevent the user from logging in until an administrator enables the account again.
  • Field Name: Account Information.account_information.disabled
  • Type: Boolean
Reason for Disabled A description of why the account is disabled.
  • Field Name: Account Information.account_information.reason_for_disabled
  • Type: String
Time Locked Due to Failed Login Attempts The time when the user account was locked as result of the number of failed login attempts exceeding the permitted thresholds.
  • Field Name: Account Information.account_information.failed_login_lock_date
  • Type: String
  • Format: date-time
Time of Last Successful Login The time the user last logged in successfully.
  • Field Name: Account Information.account_information.last_login_time
  • Type: String
  • Format: date-time
Locked Indicates if the account has been locked to prevent the user from logging in.
  • Field Name: Account Information.account_information.locked
  • Type: Boolean
Number of Failed Login Attempts Since Last Successful Login The total number of failed login attempts since last successful login. Default: 0
  • Field Name: Account Information.account_information.num_of_failed_login_attempts
  • Type: Integer
  • Default: 0
Time of Last Password Change The time when the password was last changed.
  • Field Name: Account Information.account_information.password_last_change_time
  • Type: String
  • Format: date-time
Time of Last Password Change By User The time when the password was last changed by the user.
  • Field Name: Account Information.account_information.password_last_change_time_by_user
  • Type: String
  • Format: date-time
Credential Policy Specifies the policy with the rules used to govern this user's credentials.
  • Field Name: Account Information.credential_policy
  • Type: String
  • Target: data/CredentialPolicy
  • Target attr: name
  • Format: uri
Disabled Indicates if the account has been disabled to prevent the user from logging in until an administrator enables the account again.
  • Field Name: Account Information.disabled
  • Type: Boolean
Reason for Disabled A description of why the account is disabled.
  • Field Name: Account Information.reason_for_disabled
  • Type: String
Time Locked Due to Failed Login Attempts The time when the user account was locked as result of the number of failed login attempts exceeding the permitted thresholds.
  • Field Name: Account Information.failed_login_lock_date
  • Type: String
  • Format: date-time
Time of Last Successful Login The time the user last logged in successfully.
  • Field Name: Account Information.last_login_time
  • Type: String
  • Format: date-time
Locked Indicates if the account has been locked to prevent the user from logging in.
  • Field Name: Account Information.locked
  • Type: Boolean
Number of Failed Login Attempts Since Last Successful Login The total number of failed login attempts since last successful login. Default: 0
  • Field Name: Account Information.num_of_failed_login_attempts
  • Type: Integer
  • Default: 0
Time of Last Password Change The time when the password was last changed.
  • Field Name: Account Information.password_last_change_time
  • Type: String
  • Format: date-time
Time of Last Password Change By User The time when the password was last changed by the user.
  • Field Name: Account Information.password_last_change_time_by_user
  • Type: String
  • Format: date-time
Contact Information Group Assigned by FDP
  • Field Name: Contact Information
  • Type: Object
Employee Number Employee number of the user
  • Field Name: Contact Information.employee_number
  • Type: String
Employee Type Employee type
  • Field Name: Contact Information.employee_type
  • Type: String
Country Country name.
  • Field Name: Contact Information.country
  • Type: String
State Contains full names of state or province.
  • Field Name: Contact Information.state
  • Type: String
City Contains the name of a person's locality.
  • Field Name: Contact Information.city
  • Type: String
Building Name Building name or number.
  • Field Name: Contact Information.building_name
  • Type: String
Street Contains site information from a postal address.
  • Field Name: Contact Information.street
  • Type: String
Postal Code Contains code used by a Postal Service to identify postal service zones.
  • Field Name: Contact Information.postal_code
  • Type: String
Department Department names and numbers.
  • Field Name: Contact Information.department
  • Type: String
Manager Manager.
  • Field Name: Contact Information.manager
  • Type: String
Directory URI Alphanumeric Directory URI (e.g. SIP URI)
  • Field Name: Contact Information.directory_uri
  • Type: String
Jabber ID Jabber ID
  • Field Name: Contact Information.jabber_id
  • Type: String
Physical Delivery Office Name Physical Delivery Office Name.
  • Field Name: Contact Information.physical_delivery_office_name
  • Type: String
Unverified Mail Box Unverified Mail Box.
  • Field Name: Contact Information.unverified_mailbox
  • Type: String
Home Phone Contains strings that represent the user's home phone number(s).
  • Field Name: home_phone.[n]
  • Type: Array
Telephone Number Telephone Number.
  • Field Name: telephone_number.[n]
  • Type: Array
Facsimile Telephone Number Contains strings that represent the user's facsimile telephone Number(s).
  • Field Name: facsimile_telephone_number.[n]
  • Type: Array
Mobile Contains strings that represent the user's IP mobile number(s).
  • Field Name: mobile.[n]
  • Type: Array
IP Phone Contains strings that represent the user's IP phone number(s).
  • Field Name: ip_phone.[n]
  • Type: Array
Other Mailbox
  • Field Name: other_mailbox.[n]
  • Type: Array
Organizational Unit The name of the person's organization unit.
  • Field Name: ou.[n]
  • Type: Array
Member Of The user can be a member of a variety of groups.
  • Field Name: member_of.[n]
  • Type: Array
Object Class
  • Field Name: object_class.[n]
  • Type: Array
Provisioning Status Group Assigned by FDP
  • Field Name: Provisioning Status
  • Type: Object
Provisioned Hide/Show provisioned and un-provisioned data.
  • Field Name: Provisioning Status.hide_not_provisioned
  • Type: Boolean
User Provisioning Status
  • Field Name: UserProvisioningStatus
  • Type: Object
Provisioned Hide/Show provisioned and un-provisioned data.
  • Field Name: Provisioning Status.UserProvisioningStatus.hide_not_provisioned
  • Type: Boolean
VOSS User Username field as a placeholder, this field is not used.
  • Field Name: Provisioning Status.UserProvisioningStatus.username
  • Type: String
HCMF HCMF server where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.hcmf_bkey
  • Type: String
CUCM CUCM server where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey
  • Type: String
CUCM LDAP Directory CUCM LDAP Directory.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_ldap_directory
  • Type: String
CUC CUC server where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cuc_bkey
  • Type: String
LDAP LDAP server where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.ldap_bkey
  • Type: String
WEBEX TEAMS WEBEX TEAMS server where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.spark_bkey
  • Type: String
UCCX UCCX server where the agent exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.uccx_bkey
  • Type: String
VOSS User Hierarchy VOSS User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.voss_hierarchy
  • Type: String
HCMF User Hierarchy HCMF User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.hcmf_hierarchy
  • Type: String
CUCM User Hierarchy UUCM User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_hierarchy
  • Type: String
CUC User Hierarchy UUC User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.cuc_hierarchy
  • Type: String
LDAP User Hierarchy LDAP User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.ldap_hierarchy
  • Type: String
WEBEX TEAMS User Hierarchy WEBEX TEAMS User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.spark_hierarchy
  • Type: String
UCCX User Hierarchy UCCX User Hierarchy
  • Field Name: Provisioning Status.UserProvisioningStatus.uccx_hierarchy
  • Type: String
CUCM 1 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_1
  • Type: String
CUCM 2 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_2
  • Type: String
CUCM 3 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_3
  • Type: String
CUCM 4 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_4
  • Type: String
CUCM 5 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_5
  • Type: String
CUCM 6 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_6
  • Type: String
CUCM 7 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_7
  • Type: String
CUCM 8 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_8
  • Type: String
CUCM 9 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_9
  • Type: String
CUCM 10 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_10
  • Type: String
CUCM 11 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_11
  • Type: String
CUCM 12 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_12
  • Type: String
CUCM 13 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_13
  • Type: String
CUCM 14 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_14
  • Type: String
CUCM 15 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_15
  • Type: String
CUCM 16 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_16
  • Type: String
CUCM 17 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_17
  • Type: String
CUCM 18 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_18
  • Type: String
CUCM 19 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_19
  • Type: String
CUCM 20 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_20
  • Type: String
CUCM 21 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_21
  • Type: String
CUCM 22 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_22
  • Type: String
CUCM 23 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_23
  • Type: String
CUCM 24 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_24
  • Type: String
CUCM 25 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_25
  • Type: String
CUCM 26 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_26
  • Type: String
CUCM 27 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_27
  • Type: String
CUCM 28 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_28
  • Type: String
CUCM 29 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_29
  • Type: String
CUCM 30 CUCM servers where the user exists.
  • Field Name: Provisioning Status.UserProvisioningStatus.cucm_bkey_30
  • Type: String
VOSS User Username field as a placeholder, this field is not used.
  • Field Name: Provisioning Status.username
  • Type: String
HCMF HCMF server where the user exists.
  • Field Name: Provisioning Status.hcmf_bkey
  • Type: String
CUCM CUCM server where the user exists.
  • Field Name: Provisioning Status.cucm_bkey
  • Type: String
CUCM LDAP Directory CUCM LDAP Directory.
  • Field Name: Provisioning Status.cucm_ldap_directory
  • Type: String
CUC CUC server where the user exists.
  • Field Name: Provisioning Status.cuc_bkey
  • Type: String
LDAP LDAP server where the user exists.
  • Field Name: Provisioning Status.ldap_bkey
  • Type: String
WEBEX TEAMS WEBEX TEAMS server where the user exists.
  • Field Name: Provisioning Status.spark_bkey
  • Type: String
UCCX UCCX server where the agent exists.
  • Field Name: Provisioning Status.uccx_bkey
  • Type: String
VOSS User Hierarchy VOSS User Hierarchy
  • Field Name: Provisioning Status.voss_hierarchy
  • Type: String
HCMF User Hierarchy HCMF User Hierarchy
  • Field Name: Provisioning Status.hcmf_hierarchy
  • Type: String
CUCM User Hierarchy UUCM User Hierarchy
  • Field Name: Provisioning Status.cucm_hierarchy
  • Type: String
CUC User Hierarchy UUC User Hierarchy
  • Field Name: Provisioning Status.cuc_hierarchy
  • Type: String
LDAP User Hierarchy LDAP User Hierarchy
  • Field Name: Provisioning Status.ldap_hierarchy
  • Type: String
WEBEX TEAMS User Hierarchy WEBEX TEAMS User Hierarchy
  • Field Name: Provisioning Status.spark_hierarchy
  • Type: String
UCCX User Hierarchy UCCX User Hierarchy
  • Field Name: Provisioning Status.uccx_hierarchy
  • Type: String
CUCM 1 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_1
  • Type: String
CUCM 2 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_2
  • Type: String
CUCM 3 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_3
  • Type: String
CUCM 4 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_4
  • Type: String
CUCM 5 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_5
  • Type: String
CUCM 6 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_6
  • Type: String
CUCM 7 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_7
  • Type: String
CUCM 8 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_8
  • Type: String
CUCM 9 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_9
  • Type: String
CUCM 10 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_10
  • Type: String
CUCM 11 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_11
  • Type: String
CUCM 12 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_12
  • Type: String
CUCM 13 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_13
  • Type: String
CUCM 14 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_14
  • Type: String
CUCM 15 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_15
  • Type: String
CUCM 16 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_16
  • Type: String
CUCM 17 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_17
  • Type: String
CUCM 18 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_18
  • Type: String
CUCM 19 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_19
  • Type: String
CUCM 20 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_20
  • Type: String
CUCM 21 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_21
  • Type: String
CUCM 22 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_22
  • Type: String
CUCM 23 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_23
  • Type: String
CUCM 24 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_24
  • Type: String
CUCM 25 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_25
  • Type: String
CUCM 26 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_26
  • Type: String
CUCM 27 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_27
  • Type: String
CUCM 28 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_28
  • Type: String
CUCM 29 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_29
  • Type: String
CUCM 30 CUCM servers where the user exists.
  • Field Name: Provisioning Status.cucm_bkey_30
  • Type: String
Links Group Assigned by FDP
  • Field Name: Links
  • Type: Object
CUCM Subscriber Link to CUCM User
  • Field Name: Links.cucm_user_link
  • Type: String
  • Format: link
User Provisioning Status
  • Field Name: UserProvisioningStatus
  • Type: Object
CUCM Subscriber Link to CUCM User
  • Field Name: Links.UserProvisioningStatus.cucm_user_link
  • Type: String
  • Format: link
CUC User Voicemail CUC User Voicemail
  • Field Name: Links.UserProvisioningStatus.cuc_user_link
  • Type: String
  • Format: link
WEBEX TEAMS User Webex Teams User
  • Field Name: Links.UserProvisioningStatus.spark_user_link
  • Type: String
  • Format: link
UCCX Agent UCCX Agent
  • Field Name: Links.UserProvisioningStatus.uccx_user_link
  • Type: String
  • Format: link
CUC User Voicemail CUC User Voicemail
  • Field Name: Links.cuc_user_link
  • Type: String
  • Format: link
WEBEX TEAMS User Webex Teams User
  • Field Name: Links.spark_user_link
  • Type: String
  • Format: link
UCCX Agent UCCX Agent
  • Field Name: Links.uccx_user_link
  • Type: String
  • Format: link
Custom Group Assigned by FDP
  • Field Name: Custom
  • Type: Object
Custom String 1 Custom String
  • Field Name: Custom.customString1
  • Type: String
Custom String 2 Custom String
  • Field Name: Custom.customString2
  • Type: String
Custom String 3 Custom String
  • Field Name: Custom.customString3
  • Type: String
Custom String 4 Custom String
  • Field Name: Custom.customString4
  • Type: String
Custom String 5 Custom String
  • Field Name: Custom.customString5
  • Type: String
Custom String 6 Custom String
  • Field Name: Custom.customString6
  • Type: String
Custom String 7 Custom String
  • Field Name: Custom.customString7
  • Type: String
Custom String 8 Custom String
  • Field Name: Custom.customString8
  • Type: String
Custom String 9 Custom String
  • Field Name: Custom.customString9
  • Type: String
Custom String 10 Custom String
  • Field Name: Custom.customString10
  • Type: String
Custom List of Strings 1 Custom List of Strings
  • Field Name: customListOfStrings1.[n]
  • Type: Array
Custom List of Strings 2 Custom List of Strings
  • Field Name: customListOfStrings2.[n]
  • Type: Array
Custom List of Strings 3 Custom List of Strings
  • Field Name: customListOfStrings3.[n]
  • Type: Array
Custom List of Strings 4 Custom List of Strings
  • Field Name: customListOfStrings4.[n]
  • Type: Array
Custom List of Strings 5 Custom List of Strings
  • Field Name: customListOfStrings5.[n]
  • Type: Array
Custom List of Strings 6 Custom List of Strings
  • Field Name: customListOfStrings6.[n]
  • Type: Array
Custom List of Strings 7 Custom List of Strings
  • Field Name: customListOfStrings7.[n]
  • Type: Array
Custom List of Strings 8 Custom List of Strings
  • Field Name: customListOfStrings8.[n]
  • Type: Array
Custom List of Strings 9 Custom List of Strings
  • Field Name: customListOfStrings9.[n]
  • Type: Array
Custom List of Strings 10 Custom List of Strings
  • Field Name: customListOfStrings10.[n]
  • Type: Array
Custom Boolean 1 Custom Boolean
  • Field Name: Custom.customBoolean1
  • Type: Boolean
Custom Boolean 2 Custom Boolean
  • Field Name: Custom.customBoolean2
  • Type: Boolean
Custom Boolean 3 Custom Boolean
  • Field Name: Custom.customBoolean3
  • Type: Boolean
Custom Boolean 4 Custom Boolean
  • Field Name: Custom.customBoolean4
  • Type: Boolean
Custom Boolean 5 Custom Boolean
  • Field Name: Custom.customBoolean5
  • Type: Boolean
Custom Boolean 6 Custom Boolean
  • Field Name: Custom.customBoolean6
  • Type: Boolean
Custom Boolean 7 Custom Boolean
  • Field Name: Custom.customBoolean7
  • Type: Boolean
Custom Boolean 8 Custom Boolean
  • Field Name: Custom.customBoolean8
  • Type: Boolean
Custom Boolean 9 Custom Boolean
  • Field Name: Custom.customBoolean9
  • Type: Boolean
Custom Boolean 10 Custom Boolean
  • Field Name: Custom.customBoolean10
  • Type: Boolean