Smart Numbers - Speed Dial
Speedy Smart Numbers, also known as Speed Dial, allows you to easily associate short telephone numbers to Speedy contacts. Usually the short number is 3 to 5 digits long, falls within the PBX numbering plan, and can be easily memorized. Once the Smart Number is defined, when you dial it on the phone the associated long number will be called.
Speedy allows the Application Suite users to easily create unlimited Smart numbers for their contacts trough the web interface. Smart Numbers can also be imported from file or synchronized from an external data source. You can associate a specific Smart Number to each phone number of the contact, such as business phone, mobile phone, fax number, and so on.
Once the Smart Numbers are defined, you can leverage the PBX features to restrict the class of phones allowed to reach them. Or you could allow some users to reach specific numbers bypassing the PBX restrictions (e.g. call some international numbers when international calls are blocked).
Compared to CallManager speed dial feature, Speedy Smart Numbers require very little configuration on the PBX, can be easily managed through the web interface and synchronized, and are integrated with Imagicle Applications.
Smart Numbers require at least Cisco CallManager 8.0(2) and Imagicle Application Suite Version 2014.12.1 or later.
Smart Numbers work through External Call Control (ECC-Curri). On the PBX you can define a trigger point which calls an external application every time a call matches a pattern. The trigger point can be a Translation Pattern (Cucm >= 8.0) or a Route Pattern (Cucm >= 10.0). When the pattern of the trigger point is matched, Imagicle Application Suite is called.
The request from the CallManager contains calling and called numbers. The calling number will be an internal phone number, while the called will be a Smart Number. Speedy looks for the calling number in the AppSuite users list, locates the associated user, and performs a lookup in the directories which can be accessed by him or her.
If the Smart Number is found in the user's contacts, Speedy changes the called number and diverts the call to it.
E.g. Contact Mobile Phone 333959595 - Speed Dial 8001. Outgoing prefix 0 - Outgoing suffix #
When 8001 is called, Smart numbers route the call to number to 0333959595#
Directory Lookup Priority
If the same Smart Number is defined in different directories available to the same user, the lookup order is: Private -> Department -> Public.
If the same Smart Number is defined in directories of the same type, VIP directories have the priority.
Note: when a Smart Number is called by an Imagicle Application (Speedy Click2Call, Speedy XML, Attendant Console, Gadget Jabber, Imagicle Contacts), no prefix will be added. in this, Smart Numbers are treated like internal numbers.
Cisco CallManager ECC Configuration for Speedy Smart Numbers
- Get the ECC Uri from the AppSuite Web Interface
- Add a new ECC profile to the CuCM
- Link the ECC profile to a trigger point
- Make sure the ECC request is triggered
All the Imagicle applications share the same ECC URL.
The PBX configuration is shared with the Caller ID service. Please see the "Caller ID Ecc - Curri configuration" page of this guide.
Warning: Due to a Cisco CallManager 8.x and 9.x known issue, every modification on a External Call Control Profile requires a Cisco CallManager service restart. This can drop all the calls in progress.
Smart Numbers are enabled by default. Since all the Imagicle applications share the same ECC URL, each time an Ecc request arrives, a Smart Number lookup is performed.
You may disable Smart Numbers lookup to prevent performance degradation.
To do this, go to the Imagicle Application Suite Web interface, and select "Speedy" -> "Manage Service".
In the Smart Numbers configuration box, uncheck "Enable Smart Numbers option".
How to associate a Smart Number to a contact Long Number
Log to Speedy web interface, select a directory, open it and edit a contact. For each contact telephone number, a speed dial box is available. If internal or the long number is not defined, the speed dial box cannot be edited.
Note: please ensure that the Speed Dial matches the internal phone numbers pattern in the Numbering Plan parameters web page. If it does not, please add a new pattern. This is to prevent Imagicle Applications adding prefixes to Speed Dials when they call them.
Speed dials can also be imported into directories from a CSV file just like you do for the contacts, using the to CSV template file.
Speed Dial Synchronization
Speed dials can be synchronized through LDAP or Estos Metadirectory as any other contact's field, according to the following mapping:
|IAS Field name||ESTOS field name||ESTOS' LDAP field name|
|Business Phone||Business Phone||telephoneNumber|
|Business Phone Speed Dial||Business Phone 2||otherTelephone|
|Mobile Business||Mobile Phone||mobile|
|Mobile Business Speed Dial||Mobile Phone 2||telephoneCar|
|Home Phone||Phone Home||homephone|
|Home Phone Speed Dial||Phone Home 2||otherhomephone|
|Mobile Private||Pager Phone||pager|
|Mobile Private Speed Dial||RadioTelephone||telephoneRadio|
|Fax Speed Dial||FacsimileHome||otherFacsimileTelephoneNumber|
Disable Synchronization of speed dial fields
To disable synchronization of speed dial fields for all the directories, edit file:
and insert these lines:
<preference key="db.sasdb.csvmatch.ldapsource.HomePhoneAlias" value="" /> <preference key="db.sasdb.csvmatch.ldapsource.BusinessPhoneAlias" value="" /> <preference key="db.sasdb.csvmatch.ldapsource.MobileBusinessAlias" value=""/> <preference key="db.sasdb.csvmatch.ldapsource.MobilePrivateAlias" value=""/> <preference key="db.sasdb.csvmatch.ldapsource.FaxAlias" value="" />
Check List & Troubleshooting
Basic functional test
Choose an Application Suite user with a phone associated to him/her. Add a contact to a public directory, add a mobile number and assign a speed dial to it.
Place a call from the user's internal phone to the speed dial.
The calls fails
Maybe a prefix is added to the short number. In the Admin -> System Parameters -> Numbering plan parameters web page, check the internal numbering plan patterns and the outgoing suffix and prefix.
On the PBX, check Calling Search Space and Partition configuration. There are two common issues in this configuration:
- Loop creation. It can happen, for example, if the translation pattern and the called number are in the same partition
- Call Flow is interrupted at some level. E.g. the caller CSS includes the Translation Pattern, but the Translation Pattern CSS doesn't include the partition containing ip phones
High Availability and Load Balancing
External Call Control Profile natively supports two server for routing requests. To achieve HA, first create an Imagicle Application Suite cluster. Then fill both the ECC profile URLs with Imagicle Application Server addresses (node 1 and node 2).
Cisco CallManager will autonomously determine which Application Server is answering requests and switch between them if needed.
Flag the "Enable Load Balancing" option to allow Cisco CallManager to use both Application Servers for routing requests contemporary, in case of high traffic.
Speedy contacts are are automatically replicated and aligned between the nodes, so it will be enough to define them on one node. For the same reason, contact synchronization must be enabled on one node only.
This article was:
Thank you for your feedback!
|Configuring Caller ID through ECC||Synchronizing contacts with external sources|