📜 ⬆️ ⬇️

Implementing an auto attendant based on Cisco solutions



When calling almost any company, we usually hear a pleasant or not so much voice, reminding us where we got through and offering to perform some actions. We got ... hit the auto attendant. Auto Attendant (Eng. Auto Attendant / AA) is usually the simplest case of the Interactive Voice Menu (Eng. Interactive Voice Response / IVR) , which allows you to dial an extension number, send a voice message or fax, or contact a secretary when calling the company.

In this article, I propose to become familiar with the options for implementing an auto attendant based on Cisco solutions. There are at least four of them and when implementing solutions of unified communications of Cisco, we are often asked the question of what exactly to implement this functionality. Let's look at the pros and cons of each.
')
1. Development or use of ready-made scripts on TCL and VXML

This solution is fully software, the functionality is built into the Cisco IOS operating system, and is supported on routers with the Unified Communications feature set (UC) activated. There are a lot of examples of IVR scripts for Cisco equipment. For example, on Habré you can find options for TCL and VXML .

The advantages of this option include:



If you like the algorithm of his work - we take, set up and use.

The disadvantages of this option include:
* all prices in the article are taken from the Cisco GPL

This option is suitable for a small load on the number of simultaneous calls and can be integrated with any PBX (not only Cisco).

2. Using Cisco Unity Express (CUE)

This solution is presented as a module (for example, SM-SRE-700-K9) in Cisco 1861, 2800, 2900, 3800, 3900 series routers. The IVR script is created using the Cisco Unified Communications Express Editor. The solution is functional enough, and the process of creating a script and the logic of the work strongly overlap with the older solution based on UCCX, which we will discuss below. Cisco Unity Express integrates with Cisco Unified Communications Manager and Cisco Unified Communications Manager Express, as an auto attendant can work in standalone mode.

The advantages of this option include:

The disadvantages of this option include:

This option is most suitable for companies using Cisco Unified Communications Manager Express as a PBX or for branch offices where a Cisco Unified Communications Manager PBX is deployed in the central office, and the fault tolerance of the branches is provided by Cisco Unified Survivable Remote Site Telephony (SRST). This option as well as in the case of TCL / VXML can be integrated as a standalone auto attendant with any PBX.

3. Using Cisco Unity Connection (CUC)

This solution is a voice mail server and is installed on a separate virtual machine. Two CUC virtual machines merge into a failover cluster. Built-in CUC tools allow you to create an auto attendant logic. Used built-in call handlers - handlers.

The advantages of this option include:

The disadvantages of this option include:

This solution is suitable for companies that require a high load by the number of simultaneous calls and resiliency is important.

4. Based on contact center (Cisco Unified Contact Center Express or Cisco Unified Contact Center Enterprise)

The most functional and flexible solution. UCCX, as well as CUC, is installed on a separate virtual machine. Two virtual machines can be combined into a failover cluster. For an auto attendant, setting the IP IVR functionality is sufficient. We create an IVR script using the Cisco Unified CCX Editor. UCCX integrates with Cisco Unified Communications Manager. The maximum number of sessions is limited by the capacity of the virtual server (virtual machine template) and the number of licenses purchased.

The advantages of this option include:

The disadvantages of this option include:

UCCX is a full-fledged contact center with support for advanced contact center technology, so using it only to create an auto attendant is to shoot a cannon at sparrows. This solution is suitable for companies with high demands on functionality, performance and reliability.

We considered various options for organizing an auto attendant. The choice depends largely on what solution is available or being implemented (CUCMe, CUCM, BE6K or third-party PBX), as well as what requirements for functionality, performance and reliability are presented.

Conclusion

The simplest option would be a TCL / VXML based IVR, and the most functional and productive one would be based on Cisco Unified Contact Center Express / Enterprise.

The Cisco Unity Connection solution is not always deserved and often overlooked. Typically, when purchasing Cisco Unified Communications products, Cisco Unity Connection comes bundled with purchased licenses (for example, when purchasing UWL licenses, as well as bundled Business Editions). In this case, you don’t need to purchase anything to implement the auto attendant.

The Cisco Unity Express solution removes the load (compared to the TCL / VXML use case) for handling calls from the router, occupies an intermediate position between the scripting solutions on IOS and solutions on dedicated servers. It is quite simple and convenient, therefore it is suitable for solving the task of organizing an auto attendant using the own IT department of the company, since has a simple built-in web editor for scripts with support for basic actions.

There are options for integrating Cisco IP telephony systems with third-party solutions to implement the auto attendant function, but that's another story ...

Source: https://habr.com/ru/post/301696/


All Articles