.. _managing-voss-phone-servers:

Managing VOSS Phone Servers
-----------------------------

.. _20.1.1|VOSS-722:

Adding phones requires three areas of configuration. These are all automated by VOSS Automate during the phone addition:

Set up call routing
.....................

In HCS mode, the CUCM dial plan is created to provide call routing of the
chosen numbers towards VOSS Phone Server. This allows incoming call routing.
Outbound calling Class of Service and routing are also configured to allow internal
extension and E164 call routing. Number inventory and CLI management through transformation
patterns are maintained.

1. Set up the VOSS Phone Server

   VOSS Phone Servers are managed on the customer hierarchy - verify that you
   are at the customer hierarchy.
   
   * **Version**: there is currently only 1.0.0 (base release version).
   * **Deployment Mode**:  two options are available:

     * HCS - VOSS Automate manages the Cisco CUCM dial plan and trunking, removing the need for manual integration.
       Use HCS to configure Unified CM call routing to the VOSS Phone server.
       Standard Cisco dial plan integration uses a dial plan templating facility.
       Other dial plans may be supported by creating custom dial plan templates suitable for the dial plan in use.
     * Standalone - manual integration with other call routing devices such as SBCs or other PBX and trunking services is required.
   * If the HCS deployment mode is selected, the **HCS CUCM** must be selected.
   * **Network Addresses**:

     * The SERVICE_PROVIDER_SPACE IPv4 address is the address as viewed from VOSS Automate, so could be an address viewed through NAT.
     * The APPLICATION_SPACE IPv4 addresses is the local address of the Phone Server in the customer network.

       Both addresses are required, even where the address is the same as would be found if NAT was not in use to
       provide access from the service provider network.
   * **Virtual Machine**: name is optional and is used for administrator data purposes. It is not used by VOSS Automate.

2. Add country support.
   
   Country support must be added in HCS mode in order to integrate with the HCS dialplan.
   A template is required for each supported country. GBR and USA are provided by default,
   and other countries may be created or provided by VOSS as required.

   To add HCS country support, use the "phone server countries" menu item and select the template
   for the required country. There are no user parameters required.
3. Configure the physical phone

   In HCS mode, sites must be created with site dialplan and number inventory
   in the same way as when using Cisco Phones registered directly to CUCM.
   It is possible to host both CUCM and Phone Server phones at the same site.

   The phone itself requires configuration in order to register and handle calls.

   Soft clients will likely be manually configured locally on the hosting PC,
   and a "generic soft client" device type allows for locally configured devices.

   Other hardware devices such as phones from SNOM, Cisco and Grandstream may be
   configured using configuration files hosted on the VOSS Phone Server and downloaded
   at start up by the phone. TFTP is used to download these files.
   VOSS Phone Server hosts such files for fully automated configuration of the device.

   See: 
   
   * :ref:`voss-phones`
   * :ref:`adding-phone-types`