Auto Attendant on SRST/CME gateway without CUEAugust 4th, 2008
At times it is not necessary for voicemail boxes or advaced auto-attendant features on a remote gateway that is serving a small office. This is especially true for remote non DID (ie FXO trunked) SRST gateways that are only active a small amount of time. Instead of adding a AIM-CUE or NM-CUE voicemail module in the gateway, basic auto attendant features can be provided right in IOS.
This is through the use of tcl scripting and the creation of applications. Cisco provides the tcl script for this purpose on their website at the SRST downloads page.
The basics for the script include the following components:
- tcl script – This is copied to the flash of your IOS gateway. For this example I am using the file from Cisco.com “its-CISCO.22.214.171.124.tcl”
- au files – The tcl script os packed with the audio files the script plays back to the caller. These are generic, but can be re-recorded to customize the feedback.
- application – an application will need to be created that calls the tcl script and passes the required variables.
- dial-peer – a dial-peer needs to be created to call the application.
- Enable the routing of calls to this extension.
- Additionally you will need to know what extension you want to assign to this auto attendant as well as teh extension of the operator for calls that are not matched.
Note that this is a VERY simple auto attendant. It simply answers, plays aa greeting, then asks the caller to enter the extension of a user. If the caller enters and invalid extension, it reprompts up to 3 times. If the caller enters 0, it transfers to the operator extension.
First make sure you have copied all the files from the download to you flash. You can place this in a subdirectory or the root directory of the flash. Just make sure you know where it is located. This will be important when we create the IOS application next.
Second, create the IOS application. For this example, I have coped the files into the root of the flash and I am using the extension 4999 for the autoattendant. Additionally, I am specifing the operator at extension 4001. The format for this is as follows:
service nicknetaa flash://its-CISCO.126.96.36.199.tcl
param operator 4001
paramspace english language en
paramspace english index 0
paramspace english location flash://
paramspace english prefix en
param aa-pilot 4999
Finnally, create the dial-peer to call the application. Again, I’m using 4999 as the extension for the auto attendant.
dial-peer voice 4999 voip
session target ipv4:188.8.131.52
incoming called-number 4999
Note that I am refercing the local loopback ip address (184.108.40.206) for the dial-peer destination. It is important to use a local interface ip that will not be “down” in the event of a link failure.
If you have a phone that is registered to the gateway, you should be able to dial it directly.
At this point, the application is configured and you simply need to route calls to it. This can be done in many differnt ways. If you are getting DID inbound from the provider, simply create the dial-peer and application as the extension of the main company number. Otherwise, the default-destination command under call-manager-fallback can be used. Another method if you have FXO trunking is to “connection plar” each of the voice FXO ports to the AA extension.