System-wide and Group Speed Dials

If you’ve taken a Cisco Unified Communications Manager course with me, then you’ve heard me say

80% of your CUCM problems can either be created or solved with partitions, calling search spaces, and translations.

Let’s put that axiom to the test by addressing two common feature requests: system-wide and group speed dials. To start off, let’s create three new partitions (tThere’s nothing magical about these names, you could name them whatever works for you):

  • system_speed_pt
  • group1_speed_pt
  • group2_speed_pt

The next step is to create some translation patterns.  For my example, I’m going to use *01 through *20 as my system-wide speed dials.  When creating the translation pattern, I’m going to use the settings listed below:

Translation Pattern: *01

Partition: system_speed_pt

Calling Search Space:  {Use your PSTN calling search space}

Called Party Transformation Mask: {The number you wish to speed dial to, including the outside line access code.}

Note that when a user dials this speed dial, the LCD on their phone will show the number the translation pattern is connecting them to.  If you don’t want this behavior, use the connected party presentation indicators settings on the translation pattern.

To create your group speed dials, just repeat this process, except use the correct groupx_speed_pt. Since the group speed dial translations are going into separate partitions, they can overlap.  In other words, you can have a *20 in one group and a *20 in another.

To review, so far we created a system speed dial partition and two group speed dial partitions. The translation patterns, which will convert the speed dial code into the correct number, have been created and placed in the respective partitions.  Since these translations are contained within partitions, the calling search spaces of the users will need to be modified to permit the users to access these partitions.

You would probably want to give all calling search spaces in the system access to the system_speed_pt, but I could envision not wanting to extend that common area phones. With the group speed dials, you would need each user community to have a separate calling search space so you could determine who has access to which group speed dial partitions.

There is one last thing I want to bring to your attention.  Once a speed dial call reaches the translation, the CUCM uses the translation’s calling search space to route the call to the next “hop.”  It’s entirely possible that an IP phone may have a calling search space which permits it to see the speed dial partition, but not the PSTN partition(s).  In such a case, the call will be extended by the translation pattern according to its CSS.  In other words, the call will go through even though the phone, in general, isn’t permitted to make that type of call.  You may or may not want this kind of behavior so take that into consideration as you’re planning your scheme out.

In this article

Join the Conversation