In this recipe we will set up basic short dials on a per location basis.
We will need a location-specific partition for the location for which we are implementing short dials. In this recipe we use PT-SFO-DialPlan.
To implement short dials for a location, perform the following:
Add the short dials partition to the calling search space of the device for the relevant location (Call Routing | Class of Control | Calling Search Space):
Create and save a translation pattern for the short dial in an appropriate partition (Call Routing | Translation Pattern):
Fill in Translation Pattern and Partition as appropriate. Here we use
4357and PT-SFO-DialPlan, respectively.Calling Search Space is of special note. Here, we apply a device calling search space appropriate to the location, CSS-SFO-Device.
Finally, under the Called Party Transformations section, we change Called Party Transform Mask to the final number,
2222in this recipe.
When a call matches the translation pattern, the called number is translated as per our rule to 2222, and the call continues to be routed normally.
It is important to remember that the number we are translating must be accessible from the translation pattern.
How call routing works with short dials
When a user enters a short dial number, it is modified by the appropriate translation pattern and then routed normally. However, in the case of short dials, calling search spaces and, to a lesser extent, partitions play a vital role in routing the call properly.
Before a number is modified by a translation pattern and routed, the pattern will first attempt to match a pattern or number in the same partition as the translation pattern. If no match is found the applied calling search space will be used to search partitions for a match. It is because of this behavior that it is important for the short dial translation pattern to have access to the same partitions as the device, and that is why we choose to use a device calling search space appropriate to the location.