.. _p-configure-class-of-service:

Line classes of service
------------------------

.. Model Details: relation/HcsDpClassOfServiceREL

:bdg-secondary:`provider-only`

.. _24.1|EKB-18724:


.. tip:: 

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



Configure class of service for a site
.......................................

This procedure creates a new Calling Search Space (CSS) or edits an
existing CSS that is tied to a site. The CSS can be used as a Class of
Service (COS) for a device or line, or any of the other templates that
rely on COS to filter different features.



1. Log in as provider, reseller, or customer administrator.
2. Select the relevant site. 

   .. note:: 
   
      When adding CoS, ensure you select a valid site under the customer in the hierarchy. You can only 
      add CoS at a site. 

3. Go to **Line Classes of Service**.

   .. note:: 
   
      There is one default Internal Calling Line Identification Presentation (CLIP) CoS that appears in the list. 
      The default CoS is provisioned automatically based on the criteria you selected when you added the site.

4. Choose an option: 

   * To add a CoS, click **Add**.
   * To edit an existing CoS, click on the relevant CoS, make your changes, then save. 
   * To clone an existing CoS, click on the relevant CoS, then click **Action > Clone**.

5. Fill out a unique name for the CoS in the **Class of Service Name** field. 

   .. note:: 
      
      Ensure the name is descriptive, using up to 50 alphanumeric characters, including spaces, 
      period(s), hyphens (-), and underscore characters (_). You can also use macros in Automate 
      to create a CoS name. See the Automate documentation for a list of possible macros. 
      
      MMacros allow you to dynamically add site IDs, customer IDs, and other types of information to the 
      CSS.

      Example: ``Cu1-24HrsCLIP-PT-{{macro.HcsDpSiteName}}``

      The actual CSS that is sent to the UCM (based on the macros entered) is mirrored in the 
      **Actual Calling Search Space** field. For example, the macro example above 
      changes to ``Cu1-24HrsCLIP-PT-SiteABC``.

6. Optional. Fill out a description for the CoS.
7. Choose route partition members to include in the CoS:  

   a. Click the Plus icon (+) to add route partitions.
   b. From the drop-down, select a route partition member.
   c. Repeat this step until you have selected all the members you need for this CoS. If you want to remove 
      any member from the CoS, click the Minus icon (-). 

8. Click **Save** to add the new CoS. The new CoS will display in the summary list view, from where you can 
   update it or delete it in future, if required. 

   When adding (including clone), updating, or deleting CoS, you can view transaction progress and details in the Transaction Logs. 


.. rubric:: Related topics   
 
* 
  .. raw:: latex

     Transaction Logging and Audit in the Core Feature Guide

  .. raw:: html
  
     <a href="concepts-transaction-logging-audit.html">Transaction Logging and Audit</a>

* 
  .. raw:: latex

     Class of Service in the Core Feature Guide

  .. raw:: html
  
     <a href="concepts-class-of-service.html">Class of Service</a>




Clone a class of service for a site
....................................

This procedure clones an existing Class of Service (CoS) to the same
site hierarchy node, with a new name.



1. Log in as provider, reseller, customer, or site administrator.

   .. note:: 

      When cloning a CoS, ensure that you select a valid site under the customer in the hierarchy. 
      Attempting to clone a CoS at any other node (at a customer or reseller for example), a system error 
      reminds you that you must be at a site. 

2. Go to **Class of Service**.
3. Click on the Class of Service to be cloned.
4. Click **Action > Clone**.
5. Fill out a unique name for the Class of Service in the **Class of Service Name** field. 

   .. note:: 
      
      Ensure the name is descriptive, using up to 50 alphanumeric characters, including spaces, 
      period(s), hyphens (-), and underscore characters (_).

6. Optionally, fill out a description. 
7. Save the cloned CoS. This creates a new CoS. 

   When adding (including clone), updating, or deleting CoS, you can view transaction progress and details in the Transaction Logs. 

   .. note:: 

      Save the cloned CoS to the same site hierarchy as the original CoS. You can't save the clone 
      to a different site or to a different hierarchy. 

      The new CoS displays in the summary list view, from where it can be updated or deleted in future, 
      if required. 



.. rubric:: Related Topics   
 
* 
  .. raw:: latex

     Transaction Logging and Audit in the Core Feature Guide

  .. raw:: html
  
     <a href="concepts-transaction-logging-audit.html">Transaction Logging and Audit</a>