[Index]
Headset Enablement
To enable the Cisco Headset Service for a Unified CM server listed under Apps Management > CUCM > Servers. Choose Enable Services from the Action menu.
A Headset Enablement menu option is also available to carry out this action by means of transfer boxes for all the Available servers in a Call Manager Cluster.
A data sync instance is also created for each server, in the format: HcsPull-<host>-headset_models that can be used to schedule a move of new Headset Inventory instances down to the matching user's hierarchy when it is run.
See: Headset Management.
Overview
VOSS Automate supports Cisco headset management for Unified CM (Call Manager, or CUCM) 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.
Headset data can be used for:
Subscriber or phone headset data can be viewed in VOSS Automate.
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:
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.
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:
See also Cloning Items.
| 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:
|
| Firmware parameters | Parameters as set on Unified CM:
One or more parameters can be set. |
Enable selected services for all nodes in the selected Call Manager clusters
| Title | Description | Details | |||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Call Manager Cluster | Select Call Manager clusters to process |
|
|||||||||||||||||||||||||||||||||||||||||||||||