.. _concepts-call-handler-service:
Call Handler
----------------
.. _19.1.1|VOSS-515:
.. _20.1.1|VOSS-719|EKB-5720:
.. _20.1.1|VOSS-719|EKB-5821:
.. _21.1|EKB-8974:
.. _21.2|EKB-9462:
.. _21.3-PB3|EKB-13640:
.. _21.4-PB5|EKB-19138:
Overview
..........
A Cisco Unified Communications Manager (CUCM) Auto-Attendant Call Handler
transfers incoming calls to the extension of a user or department
without the intervention of an operator, via a system of voice menus that the
caller interacts with, using their telephone keypad or voice commands.
.. note::
Auto-Attendant is a comprehensive service that provides for the provisioning,
configuration, and management of Call Handlers, greetings, schedules, and related
dialplan components in Cisco Unity Connection (CUC) and Cisco Unified Communications
Manager (CUCM).
Some Call Handler systems are comprised of message-only information menus and voice
menus, which allow organizations to provide business information such
as hours, directions to their premises, or
to answer other frequently-asked questions. Once the message plays, the caller
can be forwarded to an operator, or they can choose to return to the main menu.
Call Handlers can be created at the Customer hierarchy or the Site hierarchy in VOSS Automate:
========================= ==============================================================
Created at Customer You must select a Network Device List (NDL), which then
instructs the workflow which UC Application servers to
provision.
Created at Site The NDL associated to the site is chosen automatically.
========================= ==============================================================
.. rubric:: Related Topics
*
.. raw:: latex
Manage Greeting Files in the Core Feature Guide
.. raw:: html
Manage Greeting Files
*
.. raw:: latex
Call Handler (Auto Attendant) Schedule in the Core Feature Guide
.. raw:: html
Call Handler (Auto Attendant) Schedule
*
.. raw:: latex
Add a TimeZone Filter in the Core Feature Guide
.. raw:: html
Add a TimeZone Filter
* :ref:`concepts-number-status-usage`
* See "System Call Handlers" in the "Cisco Unity Connection System Administration
Guide for more information about Call Handlers.
.. _call-handlers-and-shared-numbers:
Call Handlers and Shared Numbers
..................................
VOSS Automate allows you to share the same directory number (DN) between a Call Handler and one or more device types (phone, SNR, EM), provided
you're using different line partitions between the Call Handler and the device types.
.. note::
SNR is short for Single Number Reach device. EM is short for Extension Mobility device. Device can include,
for example, desk phone, BOT.
Shared Number Scenarios for Call Handler
.............................................
Overview
'''''''''
This section describes scenarios for number sharing between Call Handler and one or more device types and
how this changes the status and usage values for the number in the number inventory.
The following scenarios are described:
* :ref:`add-device-to-shared-number`
* :ref:`add-ch-to-shared-number`
* :ref:`remove-ch-from-shared-number`
* :ref:`remove-devices-from-shared-number`
.. note::
Status defines whether the number is available to be assigned (or shared) between Call Handler and one
or more devices. Usage value is added to the line details in the directory number inventory.
When adding a Call Handler, all numbers available for the Call Handler (whether shared or not)
display in the **Pilot** drop-down. See :ref:`add-call-handler-service`
.. image:: /src/images/dn-inventory-status.png
When a number is currently used exclusively by Call Handler (not shared with a device), the status
and usage detail for that number is as follows:
======================= ======================================================
Status Usage
======================= ======================================================
Used-Utility Call_Handler_Pilot
======================= ======================================================
When a number is currently used exclusively by a device (not shared with Call Handler), the status
and usage detail for that number is as follows:
======================= ======================================================
Status Usage
======================= ======================================================
Used Device
======================= ======================================================
.. _add-device-to-shared-number:
Add Devices to a Number with an Existing Call Handler
'''''''''''''''''''''''''''''''''''''''''''''''''''''''''
In this scenario, Call Handler is added first and is assigned to a number. Then you can add
additional devices (e.g. deskphone, BOT, EM, SNR) with the same number.
.. tabularcolumns:: |p{5cm}|p{5cm}|p{5cm}|
+-----------------------------+--------------------------------------+-------------------------------------------------+
| Scenario | Before adding devices | After adding devices |
+=============================+======================================+=================================================+
| Add devices to a number | * Status: "Used-Utility" | * Status: "Used" |
| already assigned to | * Usage: | * Usage: "Call_Handler_Pilot,Device" |
| Call Handler | | |
| | * "Call_Handler_Pilot", or | |
| | * "Call_Handler_Pilot, Device" | |
+-----------------------------+--------------------------------------+-------------------------------------------------+
.. _add-ch-to-shared-number:
Add a Call Handler to a Number with Existing Devices
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
In this scenario, one or more device types (device, EM, SNR) were added first to a number, then you add the same number to Call Handler.
.. tabularcolumns:: |p{5cm}|p{5cm}|p{5cm}|
+-----------------------------+--------------------------------------+-------------------------------------------------+
| Scenario | Before adding Call Handler | After adding Call Handler |
+=============================+======================================+=================================================+
| Add Call Handler to a | * Status: "Used" | * Status: "Used-Utility" |
| number already assigned to | * Usage: "Device" | * Usage: "Call_Handler_Pilot,Device" |
| devices | | |
| | | |
| Scenario also applies if | | |
| Call Handler was added with | | |
| with a different | | |
| number, then you change the | | |
| Call Handler number to one | | |
| that is used by devices. | | |
+-----------------------------+--------------------------------------+-------------------------------------------------+
.. _remove-ch-from-shared-number:
Remove Call Handler from a Number Previously Shared Between Call Handler and Devices
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
In this scenario, you have a number that is currently shared between Call Handler and one or more devices. Now you
remove Call Handler from the number.
.. tabularcolumns:: |p{5cm}|p{5cm}|p{5cm}|
+-----------------------------+--------------------------------------+-------------------------------------------------+
| Scenario | Existing Status / Usage | Updated Status / Usage |
+=============================+======================================+=================================================+
| Where Call Handler was | * Status: "Used" | * Status: "Used" |
| added first, and then | * Usage: "Call_Handler_Pilot,Device" | * Usage: "Device" |
| devices were added. Now you | | |
| delete the Call Handler or | | |
| change the number it uses. | | |
+-----------------------------+--------------------------------------+-------------------------------------------------+
| Where devices were added to | * Status: "Used-Utility" | * Status: "Used" |
| a number first, and then | * Usage: "Call_Handler_Pilot,Device" | * Usage: "Device" |
| Call Handler was added. Now | | |
| you delete Call Handler or | | |
| change the number it uses. | | |
+-----------------------------+--------------------------------------+-------------------------------------------------+
.. _remove-devices-from-shared-number:
Remove Devices from a Number Previously Shared Between Call Handler and Devices
''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''''
In this scenario, Call Handler was added first, then you added devices (one or more) to that number. Now you
remove devices.
In this case, number status and usage depends on whether there was only one device and
you remove it, or whether there are multiple devices, and you remove one device from the number shared
with Call Handler.
.. tabularcolumns:: |p{5cm}|p{5cm}|p{5cm}|
+-----------------------------+--------------------------------------+-------------------------------------------------+
| Scenario | Existing Status / Usage | Updated Status / Usage |
+=============================+======================================+=================================================+
| Call Handler was added | * Status: "Used" | * Status: "Used-Utility" |
| first. One device (e.g. a | * Usage: "Call_Handler_Pilot,Device" | * Usage: "Call_Handler_Pilot" |
| phone) shares a number with | | |
| Call Handler. | | |
| | | |
| You delete that one device, | | |
| or you update that device | | |
| to remove the number (e.g. | | |
| update phone to use a new | | |
| line, or remove line from | | |
| phone). | | |
+-----------------------------+--------------------------------------+-------------------------------------------------+
| Call Handler was added | * Status: "Used" | * Status: "Used" |
| first. Two or more devices | * Usage: "Call_Handler_Pilot,Device" | * Usage: "Call_Handler_Pilot,Device" |
| are then added to the | | |
| shared number (e.g. two | | |
| phones using the same | | |
| number). | | |
| | | |
| One device is deleted | | |
| (e.g. delete phone), or | | |
| you update one device | | |
| to remove the number (e.g. | | |
| update phone to use a new | | |
| line, or remove line from | | |
| phone). | | |
+-----------------------------+--------------------------------------+-------------------------------------------------+
.. _add-call-handler-service:
Manage Auto-Attendant Call Handlers
......................................
This section describes how to add, update, or delete an Auto-Attendant Call Handler in VOSS Automate and Cisco Unity Connection (CUC).
.. note::
Some of the configuration parameters required to provision the Call Handler
are defined via the configuration templates and are not exposed in the
user interface. For example, the following settings are hardcoded in the
**AddCucmRoutePatternForCallhandlerCFT** configuration template:
* Provide Outside Dial Tone = False
* Call Classification = OnNet
To change these settings or any other values defined via the configuration template,
clone the template (via **Customizations > Configuration Templates**) to the relevant
hierarchy level, and edit the fields as required.
Add a Call Handler
''''''''''''''''''''''
This procedure adds a Call Handler.
.. rubric:: Before you start:
* The relevant Cisco Unity Connection (CUC) Auto-Attendant Call Handler template must have been
synced from CUC.
.. rubric:: To add a Call Handler:
1. Log in to the Admin Portal as Provider, Reseller, or Customer administrator.
#. Choose the relevant hierarchy, either Customer or Site.
#. Go to (default menus) **Apps Management > CUC > Call Handler**.
#. Click **Add**.
.. note::
The **Call Handler/New Record** page opens at the **Call Handler Basics** tab. All
other tabs on this page remain read-only until you configure the initial settings on this tab. Once
you've saved the new call handler, you can edit these settings. See :ref:`modify-call-handler-service`
#. Mandatory. At **Network Device List**, choose the required network device list (NDL).
.. note::
This field is auto-populated and read-only if you're adding the call handler at site level.
#. Mandatory. At **Name**, enter a name for the new Call Handler.
#. At **Call Handler Template**, choose the CUC Call Handler template.
.. note::
For more information about the Call Handler template, see the "Call Handler
Templates" section of the "Call Management" chapter of the System Administration
Guide for Cisco Unity Connection, Release 11.x.
#. Optional. At **Pilot**, choose a directory number to associate with the Call Handler.
.. note::
The drop-down displays the list of directory numbers available at the selected hierarchy. This
can include numbers already assigned to one or more device types, since VOSS Automate allows
sharing of numbers between Call Handler and multiple device types. See :ref:`concepts-call-handler-service`
#. At **Do not add Route Pattern** define whether to remove the mandatory requirement for
adding a route list (if you've chosen a pilot).
.. note::
* When enabled, (checkbox selected), choosing a route list (route pattern) is optional.
* When disabled (default), choosing a route list (route pattern) is mandatory.
This setting is relevant when adding or updating a Call Handler.
#. At **Route List**, choose a CUCM route list for the new Call Handler.
.. note::
* Optional when **Do not add Route Pattern** is enabled.
* The NDL determines the route lists available in this drop-down. If the NDL is updated,
route list options are updated.
#. Click **Save**.
.. note::
* Adding a Call Handler through VOSS Automate also adds a route pattern on the CUCM
designated in the NDL (if **Do not add Route Pattern** is disabled, and you've
chosen a route list and a pilot for the Call Handler). The pattern is the value of the pilot
(directory number) you choose.
* A configuration template (which can be cloned and modified) defines the rest of the pilot configuration (including partition).
* A direct routing rule is also created on the CUC designated in the NDL. This rule
accepts inbound calls into CUC, and routes them to the relevant Call Handler.
.. _modify-call-handler-service:
Update a Call Handler
''''''''''''''''''''''''''
To update a Call Handler:
1. Log in as Provider, Reseller, or Customer administrator.
#. Choose the relevant hierarchy.
#. Go to (default menu) **Apps Management > CUC > Call Handler**.
#. In the list view, click the relevant Call Handler to open the **Call Handler** page.
#. Click through the following tabs, and update settings as required:
.. tabularcolumns:: |p{5cm}|p{10cm}|
+--------------------------+-------------------------------------------------------+
| Tab | Description |
+==========================+=======================================================+
| Call Handler Basics | Only this tab is enabled when adding a Call Handler. |
| | All tabs are available when updating a Call Handler. |
| | |
| | * **Do not add Route Pattern** (disabled by default) |
| | defines whether to remove the mandatory requirement |
| | for choosing a route list (if you've chosen a |
| | pilot). |
| | |
| | * When disabled, you must choose a route list if |
| | you've selected a pilot |
| | * When enabled, choosing a route list is hidden and |
| | no longer required (even if you've chosen a |
| | pilot) |
| | * **Call Handler Owner** - choose the CUC user to |
| | associate with the owner of the Call Handler. |
+--------------------------+-------------------------------------------------------+
| Transfer Rules tab | Enables/disables transfer rules. |
| | |
| | * The **Standard** transfer rule can't be disabled. |
| | * By default, **Transfer Call To** is set to |
| | **Greeting**. When changing this setting to |
| | **Extension or URl**, you can specify an extension |
| | number or URl, and a transfer type (either `Release |
| | to Switch` or `Supervise Transfer`) |
+--------------------------+-------------------------------------------------------+
| Caller Input tab | Configures the default caller. Additional settings |
| | become available as you choose options on this tab. |
| | For example, choosing **User with Mailbox** (from the |
| | **Action** drop-down in **Callhandler Menu Entry**) |
| | displays the **Transfer/Greeting** drop-down. |
+--------------------------+-------------------------------------------------------+
| Greetings tab | Configures greeting settings. |
+--------------------------+-------------------------------------------------------+
| Record/Playback tab | Configures the greeting you want to record and |
| | playback on the chosen extension. You can trigger a |
| | call to a physical device, which allows for recording |
| | or playback of a greeting. The extension to dial must |
| | be an accessible extension for the administrator (or |
| | user) to answer and record or listen to greetings |
| | |
| | * At **Extension**, choose an extension, or manually |
| | type in the number of the device you want to call |
| | to record or listen to a greeting. |
| | * To record or playback a greeting for a specific |
| | purpose, select the **Specific Greeting** checkbox; |
| | else, the action applies to the main Call Handler. |
| | * At **Duration (seconds)**, specify a time period |
| | (in seconds) that the system allows for recording a |
| | greeting. This time duration does not apply when |
| | playing back a recording. Ensure you set this timer |
| | appropriately. Setting it too low may result in an |
| | incorrect configuration. |
| | * Before saving the settings on this tab, go to |
| | **Action > Record Greeting**, or to **Action > |
| | Playback Greeting** (as applicable) to record or |
| | playback the greeting you wish to use. |
+--------------------------+-------------------------------------------------------+
| Upload Greeting tab | At **Greeting File**, choose the greeting file (.wav) |
| | to upload to the Call Handler. Then configure the |
| | specific greeting (if required). |
+--------------------------+-------------------------------------------------------+
6. Click **Save**.
Changes are saved to the Call Handler in VOSS Automate and in Cisco Unity Connection (CUC).
Delete a Call Handler
''''''''''''''''''''''''
To delete a Call Handler, click on the Call Handler you want to delete; then, click
**Delete**. On the pop-up, click **Yes** to confirm.
If this Call Handler is using a number shared with one or more additional device types, see :ref:`concepts-call-handler-service`
to understand how the status and usage description of the number may change when you delete the Call Handler.
Call Handler Page
...................
This section provides more information about the information required in the tabs and fields when adding or
editing a Call Handler.
Call Handler Basics Tab
''''''''''''''''''''''''
This tab configures base information for the Call Handler.
.. image:: /src/images/call-handler-basics-tab.png
.. tabularcolumns:: |p{4.5cm}|p{3.5cm}|p{7cm}|
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+===================+=====================+========================================================================================+
| Network Device | HF.target_ndl | Mandatory input-field for the **option** (if hierarchy is at Site-node, however, this |
| List * | | value is derived automatically). The workflow (and GUIRules) will target the UC |
| | | devices that is linked to this Network Device List (NDL). In the Mod use-case, this |
| | | should also be derived automatically and can thus be omitted from Updates. |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Cisco Unity | HF.cuc_info | Informative (non-input) field. Indicates the target CUCx host/IP, which is |
| Connection | | automatically derived from the input NDL. |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Cisco Unified CM | HF.cucm_info | Informative (non-input) field. Indicates the target CUCM host/IP, which is |
| | | automatically derived from the input NDL. |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Name * | DisplayName | The text name of the handler to be used when displaying entries in the administrative |
| | | console, e.g. Cisco Unity Connection Administration. For example, the display name for |
| | | the default opening greeting Call Handler is "Opening Greeting." |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Route List | route_list | The CUCM Route List to use. The valid options are dependent on the selected NDL/CUCM. |
| | | console, e.g. Cisco Unity Connection Administration. For example, the display name for |
| | | the default opening greeting Call Handler is "Opening Greeting." |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Pilot | DtmfAccessId | The DTMF access id (i.e., extension) for the call handler. The dialable number. |
| | | |
| | | When adding a call handler, all numbers available for the call handler (whether shared |
| | | or not) display in the Pilot drop-down. |
| | | |
| | | Removing a pilot number from a call handler changes the number's status to *Available* |
| | | in the Internal Number Inventory (INI). |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
| Call Handler | cuc_template | Select the Unity Template for Call Handler. |
| Template | | |
+-------------------+---------------------+----------------------------------------------------------------------------------------+
.. note::
If the pilot number is shared between the Call Handler and one or more additional device types, see :ref:`concepts-call-handler-service` to
understand the status of numbers available to assign to the Call Handler.
Transfer Rules Tab
''''''''''''''''''''
This tab configures transfer rules for the Call Handler, for example, the system behavior to transfer a call
to an alternative number.
.. image:: /src/images/call-handler-transfer-rules-tab.png
|
.. tabularcolumns:: |p{4.5cm}|p{4cm}|p{7cm}|
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+========================+==========================+========================================================================================+
| Message | callerInput_tab_message | Caller Input |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Callhandler Menu | CallhandlerMenuEntry.[n] | |
| Entry | | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Object Id | ObjectId | The primary key for this table. A globally unique, system-generated identifier for a |
| | | MenuEntry object. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Call Handler * | CallHandlerObjectId | The unique identifier of the CallHandler object to which this menu entry belongs. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Touchtone Key | TouchtoneKey | The character on the touch-tone keypad that this menu entry corresponds to |
| | | ( * , #, 0,1...9). |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Ignore Additional | Locked | A flag indicating whether Cisco Unity Connection ignores additional input after |
| Input (Locked) | | callers press this key. Values: 0: Additional input accepted 1: Additional input |
| | | ignored; Cisco Unity Connection performs the action assigned to the key. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Call Action | Action | The type of call action to take, e.g., hang-up, goto another object, etc. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Extension or URI | TransferNumber | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Description | DisplayName | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Transfer Type | TransferType | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Rings to Wait for | TransferRings | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Target | TargetConversation | The name of the conversation to which the caller is routed. |
| Conversation | | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Target Handler | TargetHandlerObjectId | The unique identifier of the specific object to send along to the target conversation. |
| Object Id | | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
.. _caller-input:
Caller Input Tab
''''''''''''''''''
This tab defines the Call Handler behavior for caller input and navigation.
.. image:: /src/images/call-handler-caller-input-tab.png
|
The table describes fields on this tab:
.. tabularcolumns:: |p{5cm}|p{10cm}|
+---------------------------------------------+----------------------------------------------------------------+
| Field | Description |
+=============================================+================================================================+
| Wait for Additional Digits (milliseconds) | The amount of time (in milliseconds) that Cisco Unity |
| | Connection (CUC) waits for additional input after a caller |
| | presses a single, unlocked key. If there's no input within |
| | this time, CUC performs the action assigned to the key. |
+---------------------------------------------+----------------------------------------------------------------+
| Enable Prepend Digits to Dialed Extensions | Defines whether to prepend digits when dialing an |
| | extension number to transfer to. |
+---------------------------------------------+----------------------------------------------------------------+
| Digits to Prepend | The touch-tone digits to prepend to the extension when |
| | dialing the transfer number. |
+---------------------------------------------+----------------------------------------------------------------+
.. note::
These fields are exposed automatically in the default FDP for relation/CallhandlerREL. If the
FDP has been customized, you'll need to expose these fields manually by exposing the following
field names: OneKeyDelay, EnablePrependDigits, PrependDigits
The table describes options in the **Call Handler Menu Entry** fieldsets:
.. tabularcolumns:: |p{4.5cm}|p{4cm}|p{7cm}|
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+========================+==========================+========================================================================================+
| Message | callerInput_tab_message | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Callhandler Menu | CallhandlerMenuEntry.[n] | |
| Entry | | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Object Id | ObjectId | The primary key for this table. A globally unique, system-generated identifier for a |
| | | MenuEntry object. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Call Handler * | CallHandlerObjectId | The unique identifier of the Call Handler object to which this menu entry belongs. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Touchtone Key | TouchtoneKey | The character on the touch-tone keypad that this menu entry corresponds to |
| | | ( * , #, 0,1...9). |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Ignore Additional | Locked | A flag indicating whether Cisco Unity Connection ignores additional input after |
| Input (Locked) | | callers press this key. Values: 0: Additional input accepted 1: Additional input |
| | | ignored; Cisco Unity Connection performs the action assigned to the key. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Call Action | Action | The type of call action to take, e.g., hang-up, goto another object, etc. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Extension or URI | TransferNumber | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Description | DisplayName | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Transfer Type | TransferType | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Rings to Wait for | TransferRings | This setting only applies if "Call Action" is set to 'Transfer to Alternate Contact |
| | | Number'. |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Target | TargetConversation | The name of the conversation to which the caller is routed. |
| Conversation | | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
| Target Handler | TargetHandlerObjectId | The unique identifier of the specific object to send along to the target conversation. |
| Object Id | | |
+------------------------+--------------------------+----------------------------------------------------------------------------------------+
.. _greeting:
Greetings Tab
''''''''''''''''
This tab configures the behavior and type of greetings enabled in the Call Handler.
.. image:: /src/images/call-handler-greetings-tab.png
|
.. tabularcolumns:: |p{4.5cm}|p{4cm}|p{7cm}|
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+========================+===============================+========================================================================================+
| Message | greetings_tab_message | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Greeting | Greeting.[n] | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Greeting Type | Enabled | The type of greeting, e.g. "Standard," "Off Hours," "Busy," etc. |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Enabled | Enabled | If TimeExpires is set, this field is ignored. |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Time Expires | TimeExpires | The date and time when the greeting rule expires. The greeting rule is considered |
| | | not expired (enabled), if the value is NULL or a future date. The greeting rule is |
| | | considered expired (disabled), the value is in the past. |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Callers Hear | PlayWhat | The source for the greeting when this greeting is active. |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Play the "Record | PlayRecordMessage Prompt | A flag indicating whether the "Record your message at the tone?" prompt prior to |
| Your Message at | | recording a message. |
| the tone" Prompt | | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Callers See My | EnablePersonal VideoRecording | It will Enable the Personal video Recording in CUCA. |
| Personal Recording | | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Callers See Play | PlayRecordVideo MessagePrompt | A flag indicating whether the "Record your message at the tone?" prompt prior to |
| the "Record Your | | Video recording a message. |
| Message at the | | |
| Tone" Prompt | | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Ignore Caller | IgnoreDigits | A flag indicating whether Cisco Unity Connection takes action in response to touchtone |
| Input During | | keys pressed by callers during the greeting. |
| Greeting | | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Allow Transfers to | EnableTransfer | A flag indicating when an extension is dialed at the greeting and the extension is |
| Numbers Not | | not available whether to transfer to another extension. |
| Associated with | | |
| Users or Call | | |
| Handlers | | |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Times to Re-prompt | Reprompts | The number of times to reprompt a caller. After the number of times indicated here, |
| Caller | | Cisco Unity Connection performs the after-greeting action. |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
| Delay between | RepromptDelay | The amount of time (in seconds) that Cisco Unity Connection waits without receiving |
| Re-prompts | | any input from a caller before Cisco Unity Connection prompts the caller again. |
+------------------------+-------------------------------+----------------------------------------------------------------------------------------+
.. tabularcolumns:: |p{4.5cm}|p{4cm}|p{6.5cm}|
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+=========================+=====================================+========================================================================================+
| After Greeting | AfterGreetingAction | The type of call action to take, for example, hang-up, goto another object, etc. |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| After Greeting | AfterGreetingTarget Conversation | The name of the conversation to which the caller is routed. |
| Target Conversation | | |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| After Greeting | AfterGreetingTarget HandlerObjectId | The unique identifier of the specific object to send along to the target conversation. |
| Target Handler | | |
| Object Id | | |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| Call Handler | CallHandlerObjectId | The unique identifier of the Call Handler object to which this greeting rule |
| Object Id | | belongs. |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| Callhandler URI | CallhandlerURI | |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| Greeting Stream | GreetingStreamFilesURI | |
| Files URI | | |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| Greetings Type | GreetingType | The type of greeting, e.g. "Standard," "Off Hours," "Busy," etc. |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
| URI | URI | |
+-------------------------+-------------------------------------+----------------------------------------------------------------------------------------+
.. _record-playback:
Record/Playback Tab
''''''''''''''''''''
This tab configures message recording and playback for the Call Handler.
.. image:: /src/images/call-handler-record-playback-tab.png
|
.. tabularcolumns:: |p{4.5cm}|p{4cm}|p{7cm}|
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+=====================+==================================+========================================================================================+
| Message | RecordPlayback.note | A special interface, which allows administrators to trigger a call to a physical |
| | | device, which allows for recording or playback of a greeting. The extension to dial |
| | | must be an accessible extension for the admin (or user) to answer and record or |
| | | listen to greetings. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Call Handler Name | RecordPlayback.call_handler | Call Handler Name. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Extension | RecordPlayback.extension | Extension to Record message on. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Specific Greeting | RecordPlayback.specific_greeting | The unique identifier of the Call Handler object to which this menu entry belongs. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Greetings | RecordPlayback.greeting | Greetings. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Duration | RecordPlayback.duration | Duration to allow enough time to make recording/playback. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
.. _upload-greeting:
Upload Greeting Tab
''''''''''''''''''''''
On this tab you can upload a greeting for the Call Handler.
.. image:: /src/images/call-handler-upload-greeting-tab.png
|
.. tabularcolumns:: |p{4.5cm}|p{4cm}|p{7cm}|
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Title | Field Name | Description |
+=====================+==================================+========================================================================================+
| Message | note | Upload a greeting to the selected Call Handler. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Greeting File | Upload.filename | Call Handler Name. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Call Handler Name | Upload.call_handler | Call Handler Name. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Specific Greeting | Upload.specific_greeting | Specific Greeting. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+
| Greetings | Upload.greeting | Greetings. |
+---------------------+----------------------------------+----------------------------------------------------------------------------------------+