On this page

Manage Headsets

VOSS Automate supports Cisco headset management for Unified CM version 12.5 SU3 onwards. See: Headset Enablement. Third-party headset management may also be supported, depending on the headset type and Unified CM version.

Headset metrics are pulled from Unified CM and displayed on an easy to understand, read-only form in an inventory in VOSS Automate. This headset data can be used for:

  • inventory tracking of assets and usage

  • integration into VOSS Insights for compliance checks, e.g. headset firmware versions, correct headsets, etc.

Subscriber or phone headset data can be viewed in the VOSS Automate Legacy Admin Portal, Admin Portal and Business Admin Portal.

Headset templates are also listed and custom templates can be added as required.

Headset Inventory

Note

Headset details on Unified CM are updated dynamically, for example when a headset is either connected or disconnected from a phone connected to the Unified CM.

To ensure regular headset status updates in VOSS Automate, we recommend that you create a custom data sync and schedule it to run on a daily basis or more frequently if required. See also:

The Headset Inventory list view and instance form (default menu Subscriber Management > Headset Inventory) will display the latest headset data after you have executed a sync.

There are two ways a headset can be associated with a user:

  1. when connecting the headset to a phone which is associated to a user.

  2. when a user logs in to the headset. This method is typically used in an extension mobility environment (on Unified CM version 12.5 SU3). The headset is paired to a phone, which automatically logs the user in to the phone.

As soon as a Cisco USB Headset gets connected to, or disconnected from a phone on the Unified CM, the phone automatically provides details about the headset to the Unified CM.

VOSS Automate pulls this information from Unified CM, and displays it on the Headset Inventory form allowing you to view and track headsets across clusters, providing headset details such as Headset Serial Number, Vendor, Model, Owner, Connected Device Owner, Connection Type, Connected Device Name, and so on.

  • Headset Last Change is the date and time is the last connected time if a headset is disconnected.

  • Located At is derived from the location of the phone to which the headset is connected.

Note

For non-Cisco headsets, the Device Name is used as the Serial Number. Using the same non-Cisco headset in multiple phones creates duplicate headset records.

Headset Templates

The headset template allows you to associate User Profiles. The Headset Templates list (default menu Subscriber Management > Headset Templates) shows the following types of headset templates:

  • Standard Default Headset Configuration Template - System default template. This template contains the headset settings supported by the latest headset firmware installed on your system for all your headset model series. You cannot edit the default settings though you can change the profile configuration setting.

  • System Generated Custom Headset Template - This template has the headset configuration settings that were manually uploaded to the Unified CM server.

  • Custom Headset Configuration Template - create customized headset templates as per your deployment needs:

    1. Clone an existing template.

    2. Rename the template.

    3. Change the configuration as required.

    4. Save it to the desired hierarchy level.

    See also Create a Clone.

Configuration Settings

Field

Description

Name*

Enter a unique name to identify the headset template.

Description

Enter a description that identifies use of the template.

Associated User Profiles

To associate a User Profile to this template, click ‘+’ and select the profile from the drop-down, which displays all User Profiles that are available to use with this headset

Note

By default, all User Profiles are assigned to the Standard Default Headset Configuration Template. To associate a User Profile to a different template, create the new template and assign the User Profile to the new template.

Model Specific Settings

Models

E.g. 521, 522, 531, 532

Model Series

E.g 500

Model Firmware

Select the required firmware version:

  • Remain on current version - choose this option if you want the headset to remain on the existing firmware version, i.e. the headset firmware version is not upgraded to the latest firmware version on the system.

  • Latest - choose this option if you want to upgrade the headset firmware version to the latest firmware version on the system.

Firmware parameters

Parameters as set on Unified CM:

  • Name: e.g. SpeakerVolume

  • Value: integer, e.g. 5

  • Access: e.g. User

  • Usage ID: e.g. 32

One or more parameters can be set.

See also “Headsets” in the Business Admin Portal

previous

Add a Class of Service

next

Extension Mobility Profiles