PDF(642.1 KB) View with Adobe Reader on a variety of devices
ePub(755.8 KB) View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle)(550.7 KB) View on Kindle device or Kindle app on multiple devices
Updated:November 20, 2023
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This document describes how to configure a Cisco IP Phone for PLAR or Hotdial with Cisco Unified Communications Manager (CUCM).
Cisco recommends that you have knowledge of these topics:
Cisco Unified Communications Manager (CUCM)
Calling Search Space (CSS)
Session Initiation Protocol (SIP) Dial Rules
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.
Skinny Client Control Protocol (SCCP) & SIP phones register with CUCM
The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any change.
This document can also be used with these hardware and software versions:
SCCP PLAR Configuration
In order to allow the phone to automatically dial a pre-configured phone number when the IP Phone goes off-hook, a CSS is configured with a partition that contains a translation pattern with a blank translation pattern string. This results in Cisco Call Manager immediately matching this pattern. The translation pattern then transforms the called number which is none to the destination number (Hotdial) where the call is delivered.
Note: Since a Directory Number (DN) configured for PLAR dials a preconfigured number when it goes off-hook, you cannot use PLAR DN to dial any other numbers. For example, this is a typical configuration in hotel lobbies.
Step 1. Create a Partition for the PLAR Destination
Navigate to Call Routing> Class Control>Partition and then Add a New Partition. Enter the required details and click Insert.
Step 2. Create a New CSS
Navigate to Call Routing> Class Control>Calling Search Space and then click Add a New Calling Search Space.
Step 3. Create a Translation Pattern
Navigate toCall Routing> Translation Pattern and then click Add a New Translation Pattern. Select the desired partition name and CSS that were previously created in Step One and Step Two. Finally, under Called Party Transformation Mask, enter the PLAR target number. Click Insert.
Note: Ensure that the Translation Pattern field is left blank.
Note: The design behind the example is base on DN 1161. 1161 is the target for the PLAR, but this configuration guarantees that 1161 can get a call from any other phone.
The CSS used in the first screenshot for the Translation Pattern has access to the target DN partition.
Step 4. Assign the Desired Calling Search Space for the PLAR Phone
Navigate to Device> Phone.
Click Find in order to locate all the registered IP phones in Cisco Unified Communications Manager
Select the PLAR phone, and choose the DN to PLAR.
Assign the CSS to the DN for PLAR.
Note: This configuration example creates a PLAR on DN 1054 to 1161, but the CSS is configured to a DN level, which provides the ability to assign another DN to a different button on the phone, allowing to make normal calls from the same IP Phone without affecting the PLAR feature.