PLAR (Hotdial) Workflows

When adding a new Hotdial Phone (PLAR configuration), the following workflow is executed:

  1. A Unified CM route partition is created with:

    1. Name set to the Hotdial Phone selected, prefixed with “HotdialPT-“. For example: “HotdialPT-SEP000000000000”.

  2. A Unified CM CSS is created with:

    1. Name set to the Hotdial Phone selected, prefixed with “HotdialCSS-“. For example: “HotdialPT-CSS000000000000”.

    2. The Partition created above is made a member of the CSS.

  3. A Unified CM translation pattern is created with:

    1. Partition name is set to the Partition added, prefixed with “HotdialPT-“, for example: “HotdialPT-SEP000000000000”.

    2. Calling Search Space Name set to the selected Destination Dialing CSS.

    3. Called Party Transformation Mask is set to the selected Hotdial Destination Pattern.

    4. Route Option is set to Route this pattern.

    5. Urgent Priority is enabled.

  4. The Unified CM phone selected is updated as follows:

    1. For SIP Phones only, a SIP Dial rule is created and the phone is set to use the SIP Dial Rule.

    2. CSS name is set to the “HotdialCSS-” added for the Phone.

    3. Hotline Device is set to true if the phone is marked as a Hotline Device by the user on the input form.

VOSS Automate automatically resets the phone when required.

When deleting PLAR (Hotdial) for a Phone (deleting the PLAR configuration), the following workflow is executed:

  1. Update Phone CSS to the original CSS.

  2. Delete the Hotdial Translation pattern.

  3. Delete the Hotdial CSS.

  4. Delete the Hotdial Route Partition.

  5. For SIP Phones only, the device is updated to use a Dial Rule of “None”, and the Dial Rule is deleted.

previous

PLAR (Hotdial): Overview

next

Manage Hunt Groups