Here is a quick guide on customizing the Auto Attendant settings and prompts on the UC520.
In this example, I will be using the ‘aa_transfer’ AA script that is included in the newer UC520 systems. If you don’t have it, you can get it from the UC520 support files by going to Cisco.com, and clicking on ‘Voice Software’ under the downloads section, then find ‘UC500 Series.’ The AA script is in the support files package.
The aa_transfer script is simple and works good for small offices. It will play one greeting message, and you can configure 10 different transfer options by using buttons 0-9. If necessary, you can use this same procedure to configure multiple AA scripts (UC520 supports up to 5) to create a nested tree, using one AA to transfer into a second AA.
First you need to record your greeting message for AA. Make a note of the options and buttons you will need to record the greeting. Your greeting will end up something like this: “Thank you for calling Cisco. For Sales, press 1. For Support, Press 2. To transfer to the operator, press 3. To leave a message in our general mailbox, press 5.” Of course use whichever numbers and destinations you need.
There are two ways to get the prompts into the system: Sound Recorder and Prompt Management.
Option A: Sound Recorder
Startup Sound Recorder from any Windows PC (Start, Programs, Accessories, Entertainment). Of course you will need a microphone on the PC for this. Push the ‘record’ button and record your message. When you are happy with the message, click on File, Properties. Under Format Conversion, click Convert Now. In the Sound Selection window, select ‘CCITT u-law’ and ‘8KHz, 8 Bit, Mono.’ Save this file, and keep it for later.
Option B: Prompt Management
The UC520 system has a built-in system for recording prompts into the system. To configure prompt management, start by logging into the CUE GUI (default address is http://10.1.10.1, default username/password is cisco/cisco). Then click on Administration, Call-In numbers, then click Add. On the ‘Add Call-in Number’ screen, select ‘promptmgmt’ for the Application, and give it a call-in number (i.e. 410), then click Add. The new number should then be listed in the list of call-in numbers. Next, you will need to configure one or more of your existing users as a CUE Administrator to be able to utilize prompt management. Click Configure, Users. Select one of your users, and ensure they have a PIN under the Profile tab (and make sure you know what it is). Then under the Groups tab, click ‘Subscribe as Member’ then enter ‘Administrators’ for Group ID and click Find. Put a check-mark next to Administrators and hit the ‘Select Rows’ button. The user should now be a member of the Administrators group.
Next, you will need to add a Dial Peer for the prompt management system. To do this, access the CLI via Telnet to the IP address of your UC520 and entering your username and password. Enter the configuration prompt by typing ‘configure terminal’ and hitting enter. Then type in the following commands to create the Dial Peer:
Dial-peer voice 2010 voip
(*NOTE: 2010 is an unique identifier, use an available number on your system)
Description Prompt Management Dial Peer
Destination-pattern 410
(*NOTE: use the extension you created earlier)
B2bua
Session protocol sipv2
Session target ipv4:10.1.10.1
Dtmf-relay sip-notify
Codec g711ulaw
No vad
You can then ‘exit’ out and close your telnet session.
To record your prompt, dial the prompt management extension from one of the connected phones. You should be prompted for an extension number and PIN, enter the information for the user you configured as an Administrator. Then just follow the directions to access Custom Prompts and record a new prompt.
Now that we have the prompt recorded, it’s time to setup AA. Access the CUE GUI again at http://10.1.10.1. Select Voice Mail, Auto Attendant. Click on the existing ‘autoattendant’ to modify it. Under Auto Attendant Script, select the ‘aa_transfer’ script (or click upload to upload it if it isn’t on your box already), then click next. Setup each of the extension numbers you want to be available when the AA script runs, i.e. Extension1: 201, Extension 2: 202, etc. Leave ‘none’ for any buttons you aren’t using. For menu prompt either upload the prompt you created with Sound Recorder, or select the prompt already on the system you created with Prompt Management (which will be in the form of ‘UserPrompt_(date, time).wav.’ Click Next, then finish.
Your prompt should now be active, you can dial your AA extension (usually 401) to test it out.
To create nested attendants, use the same procedure and just add additional AA scripts under the CUE GUI, giving each of them a unique call-in number. Then use the first AA to transfer to the extension of the second AA, and so-on. This will also work with other AA scripts, just configure the options appropriately for the script you are using.
Hope this helps!
Different Auto Attendant per Analog Line
We just aquired another company and are in the middle of our UC500 setup. I was able to setup our 0/3 line to answer with the name of the aquired company.. This is COOL! I was able to do everything from the GUI & CNA, just had to add a dial-peer for it to work. This site is awesome, thank you all for the posts.!!!
Linking AA's via Call in Number
I can not get the aa_sbcs_v01.aef script to "link" an Option# with a Call in Number. It links to an extension fine, butif I try and link to a Call in Number of a second script (to create a nested script), nothing happens.
Am I doing this wrong or does anyone have any suggestions?
Thanks,
Derek
Can't Find aa_transfer script
I have a brand new UC500 and I've been following this article for creating my customized AA script. I've run into a snag however, I don't have the ‘aa_transfer’ AA script as the article states I should. I've also looked on Cisco's site as per the article but cannot find it there.
Anyone has any suggestions? Thanks.
Merging AA_transfer.aef and AA.aef files
I was trying to use Cisco Unity Express Scripting Editor and merge some of the funtionality of AA.aef, or in this case; an edited AA_simple.aef; with the call transfer features of AA_transfer.aef. '
I realized that AA.aef was a system file on the UC520 and not downloadable to a TFTP server, however; the AA_simple.aef that is included with CUE Scripting Editor can be modifed per the link below to function as AA.aef...
http://www.cisco.com/en/US/products/sw/voicesw/ps5520/products_configura...
So, I tried to use the guidance of the AA_transfer.aef file and simply add some of the output branches in the menu structure
I.E. Menu / Extension1 / Set extn = Entension1...
And put them under the AA.aef menu structure
I.E. Menu / DialByExt
Menu / DialByName
Menu / Extension1
Menu / Operator
Menu / Timeout
Menu / Unsuccessful
I then went into the Menu (Contact: --Triggering Contact--, prompt: prompt) Properties and assigned Extenstion1 a keypad value of 3.
In the end I really want to be able to do away with the Cisco System AAMainMenu.wav file, which can be done in the AA.aef script be removing "prefixPrompt + menuPrompt" and leaving only the "prefixPrompt" in the Create Containter Prompt properties... This way, only the prompt that you can record via the handset referencing instructions in this article, Option 2 for prompts, Prompt 3, will be heard when the caller calls in.
I.E. Thank you for calling the office of UC520, press one to dial by extension, two by name, three for accounting, 0 for operator.
It appears though that I am locked down, once again, by the set menuPrompt = SP[AA/AAMainMenu] and it's inability to do more then 1 for number, 2 for name, and 0 for operator.
Is this correct, do I need to scrap the ideal of adding to the AA.aef script and start from scratch?
Thanks.
http://10.1.10.1
I guess I don't get how you can http to the address 10.1.10.1 when 10.1.10.0 is subnetted 255.255.255.252, and 10.1.10.2 is used for Loopback addresses on the box. I am plugged directly into the box, should I alter the subnet to allow more hosts and statically configure an IP on my machine? I have changed the 192.x.x.x VLan1 to a 10.0.0.x setup to facilitate communication with the network scheme that I currently have deployed for data. Any advice would be helpful as I htink I have everything figured out save for the AA, BTW; this site is the only thing with useful information on the UC520 out there.
Doh!
I was using a DHCP server on our data network that has a firewall as a default gateway that didn't know about the segment. Change DF GW to IP of UC520 and it worked... Again, this page rocks, keep it up!
Excelent
I just did what you wrote it down and it worked fine...However While the new AA is running I am not able to access any extension. i have to wait until the AA finishs and then I can.
Is there any way we can interrup the AA by pressing the Extension number ??
Cheers,
Victor
I havent noticed that. I
I havent noticed that. I believe it works fine for me. I have now switched to the new AA_SBCS_v01 script, and it works well. allows 'dial at any time' as well as business hours, etc. give it a shot.
Nice quick guide
Congratulations SPECWAR,
nice job!
Best Regards,
ArTiCo