.. _nextgen-vm-integration-dialplan-profile:

Dial plan profile
-----------------

.. _18.1-Patch-Bundle-3|EKB-672:


.. tip:: 

   :ref:`use-action-search-to-navigate-automate`


On the **Dial Plan Profile** page, an advanced administrator can define all of the dial plan elements that
make up the CUC integration.

.. note::

   You can only add a SIP integration once a dial plan profile is configured.

You will need to complete at least the following mandatory fields: 

* Profile Name 
* SIP Profile 
* SIP Trunk Security Profile 
* Device Pool
* Route Group 
* Route List 
* SIP Trunk Inbound CSS 
* Call Manager Group 
* Voicemail Pilot CSS

You can configure details on this page with static (exact) values if you wish to deploy these same values 
over and over at store level. Typically, this option is not used. 

At the Provider hierarchy, macros are used to make the profile portable across
several customers. For example, if you had two or three different versions of dial
plans, then you would have two or three versions of this profile. The lower level
administrators could then apply the profiles as required.