.. _add_call_handler_service:

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

Before You Begin
................

Make sure that the relevant Cisco Unity Connection Call Handler template has been
synced from Cisco Unity Connection.

.. note::
       
   Not all the configuration parameters needed to provision the Call Handler are
   exposed in the user interface. Many settings and values are derived from
   Configuration Templates, i.e. **Provide Outside Dial Tone = False**, and
   **Call Classification = OnNet** are hard coded in the **AddCucmRoutePatternForCallhandlerCFT**
   configuration template. If you want to change these, or other values, clone
   the configuration template from **Customizations > Configuration Templates**
   to the desired hierarchy level, and edit the fields as required.    


Procedure
.........

1.  Log in as provider, reseller or customer administrator.
#.  Make sure that the hierarchy path is set to the required Customer or Site
    node.
#.  Choose **Services > Auto Attendant > Call Handler**.
#.  Click **Add** to add a Call Handler.
#.  From the **Hierarchy** drop-down, choose the Site to which you want to add
    the Call Handler (if not already done).
#.  From the **Network Device List** drop-down, choose the required network device
    list (NDL). This is a mandatory field. This field is only applicable at the
    customer node, and the value is derived automatically at the site node.
#.  Enter a **Name** for the Call Handler. This is a mandatory field.
#.  From the **Pilot** drop-down, choose the pilot number to which you want to
    associate the Call Handler. The drop-down list displays a list of directory
    numbers that are available at the selected hierarchy level. This is a mandatory
    field.
#.  From the **Route List** drop-down, choose the Cisco Unified CM route list to
    apply to the Call Handler. The route lists available in the drop-down are
    determined by the NDL. If the NDL changes, the drop-down list auto updates
    to display new route lists based on the updated NDL.
#.  From the **Call Handler Template** drop-down, choose the Cisco Unity Connection
    Call Handler Template to apply to the Call Handler.
    
    For detailed 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** to add the Call Handler to VOSS-4-UC and Cisco Unity Connection.
#.  Optionally, edit the Call Handler settings, see :ref:`modify_call_handler_service`.

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, during this
step. This rule will accept inbound calls into Cisco Unity Connection, and route
them to the relevant Call Handler.