[Index]

Model: relation/HcsCustomerREL

Customers

Full HTML Help

Overview

Customers exist as a node in VOSS Automate's hierarchical structure. Typically, the structure has the following order (from highest level to lowest level).

Optional intermediary nodes can also be created.

Note

VOSS Automate employs hierarchies (organization levels), user roles, and access profiles to control and secure access to resources in the system. You can find out more about hierarchies at Introduction to Hierarchies in the Core Feature Guide.

In the hierarchical structure, sites (locations) can only be created under a customer. However, you will need to set up the customer-level configuration before adding sites. The complete on-boarding of a customer is done at the Provider hierarchy. You can find the customer on-boarding details in the Customer On-boarding Quick Start Guide in the Core Feature Guide.

Related Topics

Introduction to Hierarchies in the Core Feature Guide

Customer On-boarding Quick Start Guide in the Core Feature Guide

Network Device Lists in the Core Feature Guide

Add and Update Customers

This procedure adds a new customer, and updates an existing customer.

Note

If required, you can disable number management for the customer.

  1. Log in as Provider or Reseller administrator (depending on which organization manages the customer).

    Note

    Log in using the Provider or Reseller admin's email address (case-sensitive). You can find this email address via (default menus) User Management > Admins. Click on the admin's name to view the email address.

  2. Choose the hierarchy.

    Note

    If logged in as Provider and the Customer is to be added under a Reseller, set the hierarchy path to the Reseller.

  3. Go to (default menus) Customer Management > Customers.

  4. On the Customers page:

    Note

    To switch the page layout from panels to tabs or from tabs to panels, you can click the Switch to Tab/Panel Layout toolbar icon.

  5. Fill out or update the fields on the page (Customer Details and Contact Information tabs/panels):

    Important

    Additional custom string and boolean fields may be exposed via field display policies for the Customers configuration form. For details, see Add Custom Fields to Customer Configuration Screens

Customer Details Description
Customer Name

Mandatory. The name of the customer.

Note that when Create Local Admin is selected, any spaces in the customer name are converted to underscores in the Customer local administrator name and email.
Description Customer description
Extended Name (Provider) Descriptive name for the customer, used by external clients to correlate their own customer records with customer records stored in HCS.
External Customer ID (Provider) External customer ID used by the Service Inventory service, and included as a column in the customer record of the service inventory report. Specify an External Customer ID in this field that matches the customer ID used by the external inventory tool that receives the Service Inventory reports. If the Service Inventory service is not being used, this field is not required. However, it can be used to correlate customer records in external systems with customer records in HCS.
Domain Name

Customer domain. This field is used to create email addresses for:

If the customer domain is omitted, the provider domain (or reseller domain, if the customer is under a reseller in the hierarchy and the reseller domain was provided) is used instead.
Account ID The Account ID is used by external clients to correlate their own customer records with the customer records stored in HCS. This Account ID value is synced to the Customer record in the Shared Data Repository.
Deal IDs Deal IDs are used by the Hosted License Manager (HLM) service. HLM supports Point of Sales (POS) report generation. The report includes all customers on the system with aggregate license consumption at customer level. The optional Deal ID field associated with the customer is included in the report. Each customer can have zero or more Deal IDs. The Deal ID field is free text format and each deal ID is separated by a comma.
Customer Details Description
Shared UC Applications Indicates whether the customer can use Shared UC Apps. If selected, the customer sites can use Network Device Lists that contain Shared UC Apps. Shared UC Apps are UC Apps that are defined above the Customer hierarchy level.
Disable Number Management

Enable or disable Number Management for this customer.

  • If selected, you cannot add Directory Numbers and E164 Numbers to inventories for this customer.
  • If not selected, you can add Directory Numbers and E164 Numbers to inventories for this customer.
Public Sector Set the Customer as a Public Sector customer. Used for License Reporting.
Inactive Billing Exclude customer from billing (for testing). Used for License Reporting.
Customer Details Description
Create Local Admin Defines whether a default local administrator is created for the customer.
Cloned Admin Role The Provider or Reseller role used to create a new role prefixed with the customer name. The created customer role, shown in the Default Admin Role field, is assigned to the default local administrator user. This field appears only if the Create Local Admin checkbox is selected.
Default Admin Role The created customer role that is assigned to the default local administrator. This field is read-only, and appears only if the Create Local Admin checkbox is selected.
Default Admin Password The password to assign to the default local administrator. This field appears and is mandatory only if the Create Local Admin checkbox is selected.
Repeat Default Admin Password Confirm the default local administrator password. This field appears and is mandatory only if the Create Local Admin checkbox is selected.

  1. If you enable Number Management for a customer after it was disabled, run the DN Audit Tool. See Run the Directory Number Inventory Audit Tool.

  2. Click Save.

    Note

    When deleting a customer, remove any entities associated with the customer, such as LDAP, SSO providers, Devices, and NDLs.

Add Custom Fields to Customer Configuration Screens

VOSS Automate allows you to add up to ten custom string fields and up to 10 custom boolean fields to the field display policy you apply to the Customer data model (relation/HcsCustomerREL). This provides flexibility to add additional details for a customer, if required.

The summary attributes in the Customers list view always display three Boolean fields and three String fields, regardless whether they've been included in the FDP. If you wish to change the title of these fields in the summary attributes you can add a field override entry in the FDP.

When configuring a customer (add or update), you may specify field values or use named macros to populate values for these fields.

Macros for custom string fields for relation/HcsCustomerREL:

Macros for custom boolean fields for relation/HcsCustomerREL:

The macros can be applied in workflows and configuration templates to reference the custom field values. For example, executing macro.HcsVossCustomerDAT_custom_string_1 will return the value in the field where the macro is used.

To expose custom fields for relation/HcsCustomerREL

  1. Log in to VOSS Automate as Provider admin or higher.

  2. Create or update the Customers data model field display policy:

  3. Update the menu layout to apply the field display policy:

  4. Log out, then log in again as Provider admin.

    This allows the role-based access profile changes to refresh so that you can view the updated menu layouts and field display policies you applied, including new custom fields.

Customers

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

This procedure adds a new customer, and updates an existing customer.

Note

Perform the following steps:

  1. Log in to the Admin Portal as provider or reseller administrator (depending on the organization managing the customer).

    Note

    To log in, use the provider or reseller admin email address (case-sensitive). As a provider admin, you can find the reseller admin email address via (default menus) User Management > Admins. Click on the reseller name to view the email address.

  2. Choose the hierarchy. If you're logged in as provider and you want to add the customer under a reseller, set the hierarchy path to the reseller.

  3. Go to (default menus) Customer Management > Customers to open the Customers page:

Field Description
Customer Name

Mandatory. The customer name.

When Create Local Admin is selected, any spaces in the customer name are converted to underscores in the customer local administrator name and email.

A customer configured in HCM-F and synced into VOSS-4-U may exist at the sys.hcs hierarchy. If the customer name you enter matches this customer, the Migrate from HCM-F to VOSS Automate check box is displayed. Click Save to migrate this customer to the current hierarchy level. The fields are populated with the values that were configured in HCM-F. If you do not want to migrate the customer, enter a different Customer Name.
Description Customer description
Extended Name

Descriptive name for the customer, used by external clients to correlate their own customer records with customer records stored in HCS. Extended name value is synced to the customer record in the Shared Data Repository (SDR).

The Extended Name is not referenced by other components in HCS.
External Customer ID External customer ID used by the Service Inventory service, and included as a column in the customer record of the service inventory report. Specify an External Customer ID in this field that matches the customer ID used by the external inventory tool that receives the Service Inventory reports. If the Service Inventory service is not being used, this field is not required. However, it can be used to correlate customer records in external systems with customer records in HCS.
Domain Name

Customer domain. This field is used to create email addresses for:

If the customer domain is omitted, the provider domain (or reseller domain, if the customer is under a reseller in the hierarchy and the reseller domain was provided) is used instead.
Public Sector Set the Customer as a Public Sector customer. Used for License Reporting.
Inactive Billing Exclude customer from billing (for testing). Used for License Reporting.
Field Description
Create Local Admin Controls whether a default local administrator is created for the customer.
Cloned Admin Role The Provider or Reseller role used to create a new role prefixed with the customer name. The created customer role, shown in the Default Admin Role field, is assigned to the default local administrator user. This field appears only if the Create Local Admin check box is selected.
Default Admin Role The created customer role that is assigned to the default local administrator. This field is read-only and appears only if the Create Local Admin check box is selected.
Default Admin Password The password to assign to the default local administrator. This field appears and is mandatory only if the Create Local Admin check box is selected.
Repeat Default Admin Password Confirm the default local administrator password. This field appears and is mandatory only if the Create Local Admin check box is selected.
Field Description
Account ID The Account ID is used by external clients to correlate their own customer records with the customer records stored in HCS. This Account ID value is synced to the Customer record in the Shared Data Repository.
Deal IDs Deal IDs are used by the Hosted License Manager (HLM) service which can be activated on the Hosted Collaboration Management Fulfillment (HCM-F) server. HLM supports Point of Sales (POS) report generation. The report includes all customers on the system with aggregate license consumption at customer level. The optional Deal ID field associated with the customer is included in the report. Each customer can have zero or more Deal IDs. The Deal ID field is free text format and each deal ID is separated by a comma.
Prime Collaboration

Prime Collaboration is the application which monitors equipment used by this customer. Available Prime Collaboration applications must first be configured using the HCM-F User Interface. Then HCM-F synchronization must be executed on VOSS Automate. After the HCM-F data syncs into VOSS Automate, available Prime Collaboration applications will appear in this drop-down. Select an available Prime Collaboration application to monitor Unified Communications applications and customer equipment configured for this customer.

To unassociate Prime Collaboration for this customer, choose None.
Shared UC Applications Indicates whether the customer can use Shared UC Apps. If selected, the customer sites can use Network Device Lists that contain Shared UC Apps. Shared UC Apps are UC Apps that are defined above the Customer hierarchy level.
Disable Number Management

Enable or disable Number Management for this customer.

  • If selected, you cannot add Directory Numbers and E164 Numbers to inventories for this customer.
  • If not selected, you can add Directory Numbers and E164 Numbers to inventories for this customer.

  1. If you enable Number Management for a customer after it was disabled, run the DN Audit Tool - see Run the Directory Number Inventory Audit Tool.

  2. Click Save.

    Note

    If you're deleting a customer, remove any entities associated with the customer, such as LDAP, SSO providers, Devices, and NDLs.

This relation joins the HcsVossCustomerDAT with other VOSS and SDR customer models.

Model Details: relation/HcsCustomerREL

Title Description Details
Name * Customer's name
  • Field Name: name
  • Type: String
  • MaxLength: 64
  • Pattern: ^[A-Za-z0-9_\- ]+$
Directory Domain Customer's directory domain name
  • Field Name: directoryDomain
  • Type: String
  • MaxLength: 1024
Shared UC Applications Indicates whether the Customer shares UC Application instances Default: false
  • Field Name: shared_uc_apps
  • Type: Boolean
  • Default: false
Create Local Admin Indiates whether or not an Admin User should be created Default: true
  • Field Name: create_admin
  • Type: Boolean
  • Default: true
Hierarchy Path Customer entity's hierarchy
  • Field Name: HierarchyPath
  • Type: String
  • MaxLength: 1024
Migrate from HCM-F to CUCDM Migrate HCM-F Models to CUCDM Models Default: false
  • Field Name: migrate
  • Type: Boolean
  • Default: false
Disable Number Management Disables number management Default: false
  • Field Name: disableNumMgmt
  • Type: Boolean
  • Default: false
Public Sector Default: false
  • Field Name: publicSector
  • Type: Boolean
  • Default: false
Inactive Billing Default: false
  • Field Name: inactiveBilling
  • Type: Boolean
  • Default: false
Misc Data Miscellaneous data used at run-time
  • Field Name: misc_data
  • Type: String
  • MaxLength: 1024
Custom String 1
  • Field Name: custom_string_1
  • Type: String
Custom String 2
  • Field Name: custom_string_2
  • Type: String
Custom String 3
  • Field Name: custom_string_3
  • Type: String
Custom String 4
  • Field Name: custom_string_4
  • Type: String
Custom String 5
  • Field Name: custom_string_5
  • Type: String
Custom String 6
  • Field Name: custom_string_6
  • Type: String
Custom String 7
  • Field Name: custom_string_7
  • Type: String
Custom String 8
  • Field Name: custom_string_8
  • Type: String
Custom String 9
  • Field Name: custom_string_9
  • Type: String
Custom String 10
  • Field Name: custom_string_10
  • Type: String
Custom Boolean 1
  • Field Name: custom_boolean_1
  • Type: Boolean
Custom Boolean 2
  • Field Name: custom_boolean_2
  • Type: Boolean
Custom Boolean 3
  • Field Name: custom_boolean_3
  • Type: Boolean
Custom Boolean 4
  • Field Name: custom_boolean_4
  • Type: Boolean
Custom Boolean 5
  • Field Name: custom_boolean_5
  • Type: Boolean
Custom Boolean 6
  • Field Name: custom_boolean_6
  • Type: Boolean
Custom Boolean 7
  • Field Name: custom_boolean_7
  • Type: Boolean
Custom Boolean 8
  • Field Name: custom_boolean_8
  • Type: Boolean
Custom Boolean 9
  • Field Name: custom_boolean_9
  • Type: Boolean
Custom Boolean 10
  • Field Name: custom_boolean_10
  • Type: Boolean
Hcs Customer
  • Field Name: hcsCustomer
  • Type: Object
id
  • Field Name: hcsCustomer.id
  • Type: String
  • MaxLength: 1024
Short Name *
  • Field Name: hcsCustomer.shortName
  • Type: String
  • MaxLength: 64
Extended Name
  • Field Name: hcsCustomer.extendedName
  • Type: String
  • MaxLength: 128
External Customer ID
  • Field Name: hcsCustomer.externalCustomerID
  • Type: String
  • MaxLength: 128
Deal ID Info
  • Field Name: hcsCustomer.dealIDInfo
  • Type: String
  • MaxLength: 1024
Description
  • Field Name: hcsCustomer.description
  • Type: String
  • MaxLength: 128
Account ID
  • Field Name: hcsCustomer.accountID
  • Type: String
  • MaxLength: 64
Contact Name
  • Field Name: hcsCustomer.contactName
  • Type: String
  • MaxLength: 128
Contact Address1
  • Field Name: hcsCustomer.contactAddress1
  • Type: String
  • MaxLength: 128
Contact Address2
  • Field Name: hcsCustomer.contactAddress2
  • Type: String
  • MaxLength: 128
Contact City
  • Field Name: hcsCustomer.contactCity
  • Type: String
  • MaxLength: 64
Contact State
  • Field Name: hcsCustomer.contactState
  • Type: String
  • MaxLength: 64
Contact Post Zip
  • Field Name: hcsCustomer.contactPostZip
  • Type: String
  • MaxLength: 32
Contact Country
  • Field Name: hcsCustomer.contactCountry
  • Type: String
  • MaxLength: 32
Contact Phone Number
  • Field Name: hcsCustomer.contactPhoneNumber
  • Type: String
  • MaxLength: 64
Contact Email
  • Field Name: hcsCustomer.contactEmail
  • Type: String
  • MaxLength: 128
CUOM
  • Field Name: hcsCustomer.cUOM
  • Type: String
  • Target: data/HCSHcmfCUOMDAT
  • MaxLength: 1024
  • Format: uri
ELM
  • Field Name: hcsCustomer.eLM
  • Type: String
  • Target: data/HCSHcmfELMDAT
  • MaxLength: 1024
  • Format: uri
CUCDM
  • Field Name: hcsCustomer.cUCDM
  • Type: String
  • Target: data/HCSHcmfCUCDMDAT
  • MaxLength: 1024
  • Format: uri
Service Provider *
  • Field Name: hcsCustomer.serviceProvider
  • Type: String
  • Target: data/HCSHcmfServiceProviderDAT
  • MaxLength: 1024
  • Format: uri
CCDM
  • Field Name: hcsCustomer.cCDM
  • Type: String
  • Target: data/HCSHcmfCCDMDAT
  • MaxLength: 1024
  • Format: uri
CUCDM2
  • Field Name: hcsCustomer.cUCDM2
  • Type: String
  • Target: data/HCSHcmfCUCDM2DAT
  • MaxLength: 1024
  • Format: uri
Directory Domain
  • Field Name: hcsCustomer.directoryDomain
  • Type: String
  • Target: data/HCSHcmfDirectoryDomainDAT
  • MaxLength: 1024
  • Format: uri
Owns CTX
  • Field Name: hcsCustomer.ownsCTX
  • Type: String
  • Target: data/HCSHcmfCTXDAT
  • MaxLength: 1024
  • Format: uri
Monitors Prime Collab
  • Field Name: hcsCustomer.monitorsPrimeCollab
  • Type: String
  • Target: data/HCSHcmfPrimeCollabDAT
  • MaxLength: 1024
  • Format: uri
Reseller
  • Field Name: hcsCustomer.reseller
  • Type: String
  • Target: data/HCSHcmfResellerDAT
  • MaxLength: 1024
  • Format: uri
Uses CTX
  • Field Name: hcsCustomer.usesCTX
  • Type: String
  • Target: data/HCSHcmfCTXDAT
  • MaxLength: 1024
  • Format: uri
Northbound Adjacencies
  • Field Name: northboundAdjacencies.[n]
  • Type: Array
Clusters
  • Field Name: clusters.[n]
  • Type: Array
Uses TM Ss
  • Field Name: usesTMSs.[n]
  • Type: Array
Uses TS Virtuals
  • Field Name: usesTS_Virtuals.[n]
  • Type: Array
Uses TS Hardwares
  • Field Name: usesTS_Hardwares.[n]
  • Type: Array
Uses MC Us
  • Field Name: usesMCUs.[n]
  • Type: Array
Uses CTM Ss
  • Field Name: usesCTMSs.[n]
  • Type: Array
Uses IV Rs
  • Field Name: usesIVRs.[n]
  • Type: Array
Uses TS Supervisors
  • Field Name: usesTS_Supervisors.[n]
  • Type: Array
Uses VPG Ws
  • Field Name: usesVPGWs.[n]
  • Type: Array
Hcs Role
  • Field Name: hcs_role
  • Type: Object
Name
  • Field Name: hcs_role.name
  • Type: String
Role * The role selector.
  • Field Name: hcs_role.clonedRole
  • Type: String
  • Choices: [" "]
Role * The role selector.
  • Field Name: hcs_role.role
  • Type: String
  • Choices: [" "]
Data User
  • Field Name: data_user
  • Type: Object
Name
  • Field Name: data_user.name
  • Type: String
Password
  • Field Name: data_user.password
  • Type: String
  • Is Password: True
Data User
  • Field Name: dataUser
  • Type: Object
User Name * User's Username.
  • Field Name: dataUser.username
  • Type: String
Email Address The User email address.
  • Field Name: dataUser.email
  • Type: String
First Name The User first name.
  • Field Name: dataUser.first_name
  • Type: String
Last Name The User last name.
  • Field Name: dataUser.last_name
  • Type: String
Password The User password.
  • Field Name: dataUser.password
  • Type: String
  • Is Password: True
  • Store Encrypted: True
  • Pattern: .{8,}
Role * The role to which the user belongs. See: Role.
  • Field Name: dataUser.role
  • Type: String
  • Target: data/Role
  • Target attr: name
  • Format: uri
Language The preferred language for this user. Default: en-us
  • Field Name: dataUser.language
  • Type: String
  • Target: data/Language
  • Target attr: lcid
  • Default: en-us
  • Format: uri
Set by Default Language Indicate if the user's language is set by language default in the hierarchy.
  • Field Name: dataUser.set_language
  • 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: dataUser.account_information.change_password_on_login
  • Type: Boolean
Locked Indicates if the account has been locked to prevent the user from logging in.
  • Field Name: dataUser.account_information.locked
  • Type: Boolean
Disabled Indicates if the account has been disabled to prevent the user from logging in until an administrator enables the account again.
  • Field Name: dataUser.account_information.disabled
  • Type: Boolean
Reason for Disabled A description of why the account is disabled.
  • Field Name: dataUser.account_information.reason_for_disabled
  • Type: String
Credential Policy Specifies the policy with the rules used to govern this user's credentials.
  • Field Name: dataUser.account_information.credential_policy
  • Type: String
  • Target: data/CredentialPolicy
  • Target attr: name
  • Format: uri
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: dataUser.account_information.failed_login_lock_date
  • Type: String
  • Format: date-time
Time of Last Password Change The time when the password was last changed.
  • Field Name: dataUser.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: dataUser.account_information.password_last_change_time_by_user
  • Type: String
  • Format: date-time
Time of Last Successful Login The time the user last logged in successfully.
  • Field Name: dataUser.account_information.last_login_time
  • Type: String
  • Format: date-time
Number of Failed Login Attempts Since Last Successful Login The total number of failed login attempts since last successful login. Default: 0
  • Field Name: dataUser.account_information.num_of_failed_login_attempts
  • Type: Integer
  • Default: 0
Security Questions
  • Field Name: security_questions.[n]
  • Type: Array
Question *
  • Field Name: dataUser.account_information.security_questions.[n].question
  • Type: String
  • MaxLength: 128
Answer *
  • Field Name: dataUser.account_information.security_questions.[n].answer
  • Type: String
  • MaxLength: 128
Used Passwords List of passwords that have been used by user.
  • Field Name: used_passwords.[n]
  • Type: Array
Password Used password
  • Field Name: dataUser.account_information.used_passwords.[n].password
  • Type: String
Time Created Time when password was created.
  • Field Name: dataUser.account_information.used_passwords.[n].time_created
  • Type: String
Entitlement Profile
  • Field Name: dataUser.entitlement_profile
  • Type: String
  • Target: data/HcsEntitlementProfileDAT
  • MaxLength: 1024
  • Format: uri
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: dataUser.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: dataUser.sync_type
  • Type: String
  • Default: LOCAL
Building Name Building name or number.
  • Field Name: dataUser.building_name
  • Type: String
Country Country name.
  • Field Name: dataUser.country
  • Type: String
Department Department names and numbers.
  • Field Name: dataUser.department
  • Type: String
Directory URI Alphanumeric Directory URI (e.g. SIP URI)
  • Field Name: dataUser.directory_uri
  • Type: String
Display Name Display name of the user
  • Field Name: dataUser.display_name
  • Type: String
Employee Number Employee number of the user
  • Field Name: dataUser.employee_number
  • Type: String
Employee Type Employee type
  • Field Name: dataUser.employee_type
  • Type: String
Facsimile Telephone Number Contains strings that represent the user's facsimile telephone Number(s).
  • Field Name: facsimile_telephone_number.[n]
  • Type: Array
Home Phone Contains strings that represent the user's home phone number(s).
  • Field Name: home_phone.[n]
  • Type: Array
IP Phone Contains strings that represent the user's IP phone number(s).
  • Field Name: ip_phone.[n]
  • Type: Array
Jabber ID Jabber ID
  • Field Name: dataUser.jabber_id
  • Type: String
City Contains the name of a person's locality.
  • Field Name: dataUser.city
  • Type: String
Manager Manager.
  • Field Name: dataUser.manager
  • Type: String
Member Of The user can be a member of a variety of groups.
  • Field Name: member_of.[n]
  • Type: Array
Mobile Contains strings that represent the user's IP mobile number(s).
  • Field Name: mobile.[n]
  • Type: Array
Organization The name of the person's organization.
  • Field Name: dataUser.organization
  • Type: String
Object Class
  • Field Name: object_class.[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
Photo URL Photo URL.
  • Field Name: dataUser.photo_url
  • Type: String
Physical Delivery Office Name Physical Delivery Office Name.
  • Field Name: dataUser.physical_delivery_office_name
  • Type: String
Postal Code Contains code used by a Postal Service to identify postal service zones.
  • Field Name: dataUser.postal_code
  • Type: String
Preferred Language Preferred Language.
  • Field Name: dataUser.preferred_language
  • Type: String
State Contains full names of state or province.
  • Field Name: dataUser.state
  • Type: String
Street Contains site information from a postal address.
  • Field Name: dataUser.street
  • Type: String
Telephone Number Telephone Number.
  • Field Name: telephone_number.[n]
  • Type: Array
Timezone Timezone.
  • Field Name: dataUser.timezone
  • Type: String
Title Title.
  • Field Name: dataUser.title
  • Type: String
Unverified Mail Box Unverified Mail Box.
  • Field Name: dataUser.unverified_mailbox
  • Type: String
Custom String 1 Custom String
  • Field Name: dataUser.customString1
  • Type: String
Custom String 2 Custom String
  • Field Name: dataUser.customString2
  • Type: String
Custom String 3 Custom String
  • Field Name: dataUser.customString3
  • Type: String
Custom String 4 Custom String
  • Field Name: dataUser.customString4
  • Type: String
Custom String 5 Custom String
  • Field Name: dataUser.customString5
  • Type: String
Custom String 6 Custom String
  • Field Name: dataUser.customString6
  • Type: String
Custom String 7 Custom String
  • Field Name: dataUser.customString7
  • Type: String
Custom String 8 Custom String
  • Field Name: dataUser.customString8
  • Type: String
Custom String 9 Custom String
  • Field Name: dataUser.customString9
  • Type: String
Custom String 10 Custom String
  • Field Name: dataUser.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: dataUser.customBoolean1
  • Type: Boolean
Custom Boolean 2 Custom Boolean
  • Field Name: dataUser.customBoolean2
  • Type: Boolean
Custom Boolean 3 Custom Boolean
  • Field Name: dataUser.customBoolean3
  • Type: Boolean
Custom Boolean 4 Custom Boolean
  • Field Name: dataUser.customBoolean4
  • Type: Boolean
Custom Boolean 5 Custom Boolean
  • Field Name: dataUser.customBoolean5
  • Type: Boolean
Custom Boolean 6 Custom Boolean
  • Field Name: dataUser.customBoolean6
  • Type: Boolean
Custom Boolean 7 Custom Boolean
  • Field Name: dataUser.customBoolean7
  • Type: Boolean
Custom Boolean 8 Custom Boolean
  • Field Name: dataUser.customBoolean8
  • Type: Boolean
Custom Boolean 9 Custom Boolean
  • Field Name: dataUser.customBoolean9
  • Type: Boolean
Custom Boolean 10 Custom Boolean
  • Field Name: dataUser.customBoolean10
  • 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: dataUser.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: dataUser.ldap_server
  • Type: String
  • Target: data/Ldap
  • Format: uri
LDAP Username The login attribute of the associated LDAP device model instance
  • Field Name: dataUser.ldap_username
  • Type: String
SSO Identity Provider The entity id of the SSO Identity Provider.
  • Field Name: dataUser.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: dataUser.sso_username
  • Type: String
User Type Indicate the user's login type. Default: Admin
  • Field Name: dataUser.user_type
  • Type: String
  • Default: Admin
  • Choices: ["Admin", "End User", "End User + Admin"]
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: dataUser.exclude_from_directory
  • Type: Boolean
Hybrid Status
  • Field Name: dataUser.mvs_hybrid_status
  • Type: String
Primary Line
  • Field Name: dataUser.mvs_primary_line
  • Type: String
Primary Class of Service
  • Field Name: dataUser.mvs_primary_line_cos
  • Type: String
Extensions Extensions to select primary details from.
  • Field Name: mvs_extensions.[n]
  • Type: Array
Line
  • Field Name: dataUser.mvs_extensions.[n].line
  • Type: String
Line E164
  • Field Name: dataUser.mvs_extensions.[n].line_e164
  • Type: String
Class of Service
  • Field Name: dataUser.mvs_extensions.[n].line_cos
  • Type: String
Avaya System Manager User Name The username corresponding to the the Username in Avaya System Manager.
  • Field Name: dataUser.username_avaya_system_manager
  • Type: String
Broadworks User Name The username corresponding to the the Username in Broadworks.
  • Field Name: dataUser.username_broadworks
  • Type: String
Cisco Unity Connection User Name The username corresponding to the the Username in Cisco Unity Connection.
  • Field Name: dataUser.username_cuc
  • Type: String
Cisco Unified Communication Manager User Name The username corresponding to the the Username in Cisco Unified Communication Manager.
  • Field Name: dataUser.username_cucm
  • Type: String
HCMF User Name The username corresponding to the the Username in Cisco HCMF.
  • Field Name: dataUser.username_hcmf
  • Type: String
LDAP Directory User Name The username corresponding to the the Username in the LDAP Directory.
  • Field Name: dataUser.username_ldap
  • Type: String
Microsoft User Name The username corresponding to the the Microsoft Username.
  • Field Name: dataUser.username_microsoft
  • Type: String
Microsoft Office 365 User Name The username corresponding to the the Username in Microsoft Office 365.
  • Field Name: dataUser.username_ms_365
  • Type: String
Microsoft LDAP User Name The username corresponding to the the Username in Microsoft LDAP.
  • Field Name: dataUser.username_ms_ldap
  • Type: String
Microsoft Teams User Name The username corresponding to the the Username in Microsoft Teams.
  • Field Name: dataUser.username_ms_teams
  • Type: String
Open LDAP User Name The username corresponding to the the Username in Opoen LDAP.
  • Field Name: dataUser.username_open_ldap
  • Type: String
Cisco Unified Contact Centre Express User Name The username corresponding to the the Username in Cisco Unified Contact Centre Express.
  • Field Name: dataUser.username_uccx
  • Type: String
Webex App User Name The username corresponding to the the Username in Webex App.
  • Field Name: dataUser.username_webex_teams
  • Type: String
Zoom User Name The username corresponding to the the Username in Zoom.
  • Field Name: dataUser.username_zoom
  • Type: String
Authorized Admin Hierarchy A reference an Authorized Admin Hierarchy instance that defines this user's administrative capabilities. This enables administrative capabilities for end users.
  • Field Name: dataUser.authorized_admin_hierarchy
  • Type: String
  • Target: data/AuthorizedAdminHierarchy
  • Target attr: name
  • Format: uri
License Audit Details License Audit Information.
  • Field Name: license_audit_details
  • Type: Object
Last Checked The last time the License Audit Details were updated.
  • Field Name: dataUser.license_audit_details.last_checked
  • Type: String
  • Format: date-time
License Audit Status The License Audit status of the user. Default: Unknown
  • Field Name: dataUser.license_audit_details.status
  • Type: String
  • Default: Unknown
  • Choices: ["Licensed", "Unlicensed", "Unknown"]
Base Customer Dom
  • Field Name: baseCustomerDOM
  • Type: Object
Customer Name *
  • Field Name: baseCustomerDOM.name
  • Type: String
  • MaxLength: 64
  • Pattern: ^[\w\ -]+$
Internal ID Default: "Auto Generated"
  • Field Name: baseCustomerDOM.InternalCustomerID
  • Type: String
  • Default: "Auto Generated"
Description
  • Field Name: baseCustomerDOM.Description
  • Type: String
Address Line 1
  • Field Name: baseCustomerDOM.Address1
  • Type: String
Address Line 2
  • Field Name: baseCustomerDOM.Address2
  • Type: String
Address Line 3
  • Field Name: baseCustomerDOM.Address3
  • Type: String
Customer ID
  • Field Name: baseCustomerDOM.CustomerID
  • Type: String
Base Customer Dat
  • Field Name: baseCustomerDAT
  • Type: Object
Customer Name *
  • Field Name: baseCustomerDAT.CustomerName
  • Type: String
  • MaxLength: 64
  • Pattern: ^[\w\ -]+$
Internal ID Default: "Auto Generated"
  • Field Name: baseCustomerDAT.InternalCustomerID
  • Type: String
  • Default: "Auto Generated"
Customer ID
  • Field Name: baseCustomerDAT.CustomerID
  • Type: String
Address Line 1
  • Field Name: baseCustomerDAT.Address1
  • Type: String
Address Line 2
  • Field Name: baseCustomerDAT.Address2
  • Type: String
Address Line 3
  • Field Name: baseCustomerDAT.Address3
  • Type: String
Description
  • Field Name: baseCustomerDAT.Description
  • Type: String
Hierarchy
  • Field Name: baseCustomerDAT.Hierarchy
  • Type: String