.. _add_call_handler_service:

Add Call Handler (Auto Attendant)
---------------------------------

.. _20.1.1|VOSS-719|EKB-5821:

This procedure adds a call handler to VOSS-4-UC and to Cisco Unity Connection (CUC).


**Prerequisites**:

* The relevant Cisco Unity Connection (CUC) call handler template must have been 
  synced from CUC.


.. note::

   Some of the configuration parameters required to provision the call hanlder 
   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.


**Perform these steps**:

1.  Log in as provider, reseller, or customer administrator.
#.  Set the hierarchy path to the required customer or site node.
#.  Choose (default menu) **Services > Auto Attendant > Call Handler**.
#.  Click **Add** to add a call handler.
#.  On the **Call Handler Basics** tab: 
    
    .. note:: 
       Other tabs on this screen remain read-only until you've saved and added the new 
       call handler: Transfer Rules, Caller Input, Greetings, Record/Playback, Upload Greeting. 
       Once you've saved the new call handler, you can edit these settings. See Modify a 
       Call Handler (Auto Attendant).

    * (Mandatory) From the **Network Device List** drop-down, choose the required network device
      list (NDL). 
      
      .. note:: 
         This field is auto-populated (read-only) if you're adding the call handler 
         at site level.
    
    * (Mandatory) In the **Name** field, enter a name for the call handler. 

    * (Optional) From the **Pilot** drop-down, select a number that you want to
      associate with the call handler. 
      
      .. note:: 
         This list displays a list of directory numbers that are available 
         at the selected hierarchy. Selecting a pilot number displays the **Route 
         List** drop-down. 

    * From the **Route List** drop-down, select the Cisco Unified CM route list 
      to apply to the call handler. 

      .. note:: 
         This drop-down displays if you've selected a pilot number. The NDL determines 
         the route lists available in this drop-down. If the NDL changes, 
         the drop-down list or route list options changes, based on the updated NDL. 
    
    * From the **Call Handler Template** drop-down, choose the CUC call handler template to 
      apply the call handler.

      .. 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.
    
#.  Click **Save**. 
    
    Adding a call handler through VOSS-4-UC also adds a route pattern on the Cisco
    Unified CM designated in the NDL. The pattern is the value of the pilot selected.

    The rest of the pilot configuration (including partition) is driven through
    a configuration template that can be cloned and modified. A direct routing rule 
    is also created on the Cisco Unity Connection designated in the NDL. This rule 
    accepts inbound calls into Cisco Unity Connection, and routes 
    them to the relevant call handler.




.. rubric:: Related Topics

* 
  .. raw:: latex

     Call Handler (Auto Attendant) in the Core Feature Guide

  .. raw:: html
  
     <a href="concepts-aa-call-handler.html">Call Handler (Auto Attendant)</a>
* 
  .. raw:: latex

     Modify a Call Handler (Auto Attendant) in the Core Feature Guide

  .. raw:: html
  
     <a href="tasks-modify-aa-call-handler.html">Modify a Call Handler (Auto Attendant)</a>