On this page

PLAR (Hotdial)

Overview

Private Line Automatic Ringdown (PLAR), also called Hotdial, automates the Cisco Unified Communications Manager (CUCM, or CallManager) configuration required to set up PLAR for a phone.

PLAR provides an administrator with a single interface and workflow for managing the following parts of CUCM:

  • RoutePartition

  • CSS

  • TransPattern

  • Phone

  • Line

  • SIP Dial Rule

Additionally, the PLAR feature provides an administrator with the following:

  • A simplified user interface to choose:

    • A phone that must be enabled for PLAR

    • A destination number

    • The destination CSS

  • A workflow that creates and applies a number of elements to the relevant phone and number. These elements include:

    • The required CUCM partition

    • CSS

    • Translation pattern

To configure an existing phone for PLAR (Hotdial), you choose a pre-existing device and indicate that the device is a Hotdial device.

As soon as a PLAR-configured phone goes off hook (or the NewCall softkey or line key gets pressed), the phone immediately dials a pre-configured destination number. The phone can’t dial any other number except the Hotdial destination that is configured for PLAR.

The PLAR configuration can be added or deleted, but not modified.

PLAR (Hotdial) Workflows

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

  1. A CUCM route partition is created with:

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

  2. A CUCM 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 CUCM 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 CUCM 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

Pexip Conference Users

next

Hunt Groups