Table Of Contents
Prerequisites for Installing Cisco Unity Express Software
Prerequisites for Cisco Unified CallManager Express
Prerequisites for Cisco Unified CallManager
Recording an Auto-Attendant Greeting or Prompt File
Configuring Auto-Attendant Scripts
Restrictions for Implementing Cisco Unity Express
Prerequisites for Installing Cisco Unity Express Software
Last Updated: July 25, 2006
This chapter describes the prerequisites for installing the Cisco Unity Express software on your system and contains the following sections:
•
Prerequisites for Cisco Unified CallManager Express
•Prerequisites for Cisco Unified CallManager
•Recording an Auto-Attendant Greeting or Prompt File
•Configuring Auto-Attendant Scripts
•Restrictions for Implementing Cisco Unity Express
Prerequisites for Cisco Unified CallManager Express
Before Cisco Unity Express configuration can be started, the Cisco Unified CallManager Express (Cisco Unified CME) system must be installed. If you did not or are not performing the Cisco Unified CME installation, contact the designated installer to ensure that the following procedures are completed:
1. Install all Cisco Unified CME and Cisco Unity Express hardware and verify functionality.
a. Attach the telephones so that they register with the Cisco Unified CME router.
b. Verify that the Cisco Unity Express router is configured with a Cisco IOS release that supports the Cisco Unity Express network module (NM) or advanced integration module (AIM). For information on the minimum Cisco IOS release required to support these modules, see the Release Notes for Cisco Unity Express 2.3.
c. Install the Cisco Unity Express NM or AIM in the same router where Cisco Unified CME is installed.
d. For the NM, verify that the Enable LED is lit.
Note See "Uninterruptible Power Supply Recommendations" on page 3.
2. Install and verify Cisco Unified CME software functionality.
a. Verify that you have web connectivity to the Cisco Unified CME configuration web page at http://cisco-unified-cme-router-ipaddress/ccme.html.
b. Verify that the Cisco Unified CME router flash memory has the following files, which control the functionality of the Cisco Unity Express GUI:
- CiscoLogo.gif
- Delete.gif
- Plus.gif
- Tab.gif
- admin_user.html
- admin_user.js
- dom.js
- downarrow.gif
- ephone_admin.html
- logohome.gif
- normal_user.html
- normal_user.js
- sxiconad.gif
- telephony_service.html
- uparrow.gif
- xml-test.html
- xml.template
c. Configure the following path in Cisco Unified CME configuration mode:
Router(config)# ip http path flash:
Verify the path with the show running-config command.
d. Configure IP connectivity between the router and the Cisco Unity Express module. The module has an internal IP address and a default gateway configuration. The router has a service-engine interface with an IP address, which may be unnumbered.
One configuration method uses the ip unnumbered command, which allows the Cisco Unity Express module to use a network subnet IP address associated with a specific router egress port, such as FastEthernet0/0. This method requires a static route to the service-engine interface. The router interface associated with the Cisco Unity Express interface must be in an "up" state at all times for communication between the router and module.
In the following example, 10.3.6.128 is the IP address of the Cisco Unity Express module and Service-Engine1/0 is the router slot hosting the Cisco Unity Express module.
interface FastEthernet0/0
ip address 10.3.6.1 255.255.255.0
interface Service-Engine1/0
ip unnumbered FastEthernet0/0
service-module ip address 10.3.6.128 255.255.255.0
service-module ip default-gateway 10.3.6.1
ip route 10.3.6.128 255.255.255.255 Service-Engine1/0
If your network uses a VLAN interface with an Etherswitch module, use the example above but replace both instances of "FastEthernet0/0" with "VLAN1."
e. Verify that a SIP dial peer is configured to point to the Cisco Unity Express module, that it specifies G.711 u-law and SIP Notify for DTMF Relay, and that VAD is turned off, for example:
dial-peer voice 6000 voip <------ SIP dial peer pointing to Cisco Unity Express
session target ipv4:10.3.6.128 <---- Cisco Unity Express IP address
Configure the appropriate number of SIP dial peers to support your dial plan.
f. The FTP server that communicates with Cisco Unity Express must support passive FTP requests. To configure this functionality on the FTP server, see the FTP server documentation.
g. Verify that a Cisco Unified CME web administrator is configured with a user ID and password, for example:
web admin system name admin password user1
or
web admin system name admin secret 5 encrypted-password
Note If you plan to use the Cisco Unity Express graphical user interface (GUI) for configuration purposes, configure an administrator user ID with a password in the Cisco Unified CME interface. You must log in to the GUI as this user. If no administrator user is created in Cisco Unified CME, the administrator cannot proceed with the initialization wizard in the Cisco Unity Express GUI.
h. Configure the telephones and subscribers and save them to the Cisco Unified CME database. The Cisco Unity Express initialization wizard allows you to copy this data to the Cisco Unity Express database. You can create additional subscribers and telephones later using the Cisco Unity Express CLI commands or GUI options.
Use the following sample ephone-dn and ephone configurations to configure the telephones and subscribers manually:
ephone-dn 1 <---- ephone dn configuration for a user
call-forward noan 6900 timeout 10
ephone-dn 20 <---- ephone dn configuration for a group
call-forward noan 6900 timeout 10
ephone 1 <--- ephone configured for the ephone-dn configured above
username "Salesgroup" password null
mac-address 0009.B7F7.556A
button 1:1 2:20 3:21 4:22 5:23
i. Configure the message waiting indicator (MWI) on and off extensions. Add the wildcard characters (.) to the DNs to represent the length of a telephone extension number. Cisco Unity Express requires these wildcards when importing the MWI DNs from Cisco Unified CallManager Express during the initialization wizard. If the wildcard characters are not configured in Cisco Unified CME, the DNs will not appear as available choices in the MWI extension field. For example:
ephone-dn 30 <---- ephone-dn configurations for MWI on
number 8000.... <---- valid MWI DN 4-digit extension
ephone-dn 31 <---- ephone-dn configurations for MWI off
number 8001.... <---- valid MWI DN 4-digit extension
3. (Optional) If no subscribers were created in the Cisco Unified CME interface, create a list of all subscribers, groups, and their extensions to simplify the task of configuring many subscribers and extensions.
Note Designate a primary extension for each subscriber who will receive voice-mail messages. Cisco Unity Express does not activate the MWI for an E.164 number.
4. (Optional) Create an alternate welcome message for the auto-attendant application. Auto attendant includes a default welcome message. You can create a different message in a .wav file and install it as part of the auto-attendant configuration. See "Recording an Auto-Attendant Greeting or Prompt File" for more information.
5. (Optional) Customize the auto-attendant prompt flow to meet your business requirements. See "Configuring Auto-Attendant Scripts" for more information.
6. (Required) Copy the IP address of the Cisco Unity Express module because you need it to access the GUI to configure the system.
Prerequisites for Cisco Unified CallManager
Before Cisco Unity Express configuration can be started, the Cisco Unified CallManager system must be installed.
Caution Cisco Unity Express 2.3 does not support versions of Cisco Unified CallManager prior to 4.1. If you are using an earlier version of Cisco Unified CallManager, you must upgrade to version 4.1or higher to interoperate with Cisco Unity Express 2.3.
If you did not or are not performing the Cisco Unified CallManager installation, contact the designated installer to ensure that the following procedures are completed:
1. (Required) Install all Cisco Unified CallManager and Cisco Unity Express hardware and verify functionality.
a. Attach the telephones so that they register with the Cisco Unified CallManager server.
b. Verify that the Cisco Unified CallManager server is configured with a Cisco IOS release that supports the Cisco Unity Express network module (NM) or advanced integration module (AIM). For information on the minimum Cisco IOS release required to support these modules, see the Release Notes for Cisco Unity Express 2.3.
c. For the NM, verify that the enable LED is lit.
Note See "Uninterruptible Power Supply Recommendations" on page 3.
2. (Required) Install and verify Cisco Unified CallManager software functionality.
a. You should be able to access the Cisco Unified CallManager configuration webpage.
b. Configure IP connectivity between the router and the Cisco Unity Express module. The module has an internal IP address and a default gateway configuration. The router has a service-engine interface with an IP address, which may be unnumbered.
One configuration method is to use the ip unnumbered command, which allows the Cisco Unity Express module to use a network subnet IP address associated with a specific router egress port, such as FastEthernet0/0. This method requires a static route to the service-engine interface. The router interface associated with the Cisco Unity Express interface must be in an "up" state at all times for communication between the router and module.
In the following example, 10.3.6.128 is the IP address of the Cisco Unity Express module and Service-Engine1/0 is the router slot hosting the Cisco Unity Express module.
interface FastEthernet0/0
ip address 10.3.6.1 255.255.255.0
interface Service-Engine1/0
ip unnumbered FastEthernet0/0
service-module ip address 10.3.6.128 255.255.255.0
service-module ip default-gateway 10.3.6.1
ip route 10.3.6.128 255.255.255.255 Service-Engine1/0
If your network uses a VLAN interface with an Etherswitch module, use the example above but replace both instances of "FastEthernet0/0" with "VLAN1." On the Cisco Unified CallManager, configure 16 CTI ports for a Cisco Unity Express system with a CUE-NM-EC. Configure 8 ports for a CUE-NM.
c. For the NM, configure eight CTI ports on Cisco Unified CallManager. For the AIM, configure four CTI ports on Cisco Unified CallManager. Use the Cisco Unified CallManager option Device > Phones > Add new Phone. These ports will be assigned to the Cisco Unity Express applications (voice mail, auto attendant, and Administration via Telephone [AvT]) to terminate calls.
Note Do not configure extra CTI ports on Cisco Unified CallManager. Doing so will impact the scalability of your Cisco Unified CallManager and will limit the number of other devices Cisco Unified CallManager can support.
d. Configure at least two route points on Cisco Unified CallManager using the Device >
CTI Route Point option. The Cisco Unity Express voice-mail application uses one route point, and the auto-attendant application uses the other route point. If you plan to use the Cisco Unity Express AvT, configure a third route point on Cisco Unified CallManager.
Note Do not configure extra route points on Cisco Unified CallManager. Doing so will impact the scalability of your Cisco Unified CallManager and will limit the number of other devices that Cisco Unified CallManager can support.
e. Create a Cisco Unified CallManager JTAPI user with the User > Add new user option. Use the Device Association option to associate the CTI ports and route points with this JTAPI user. (The JTAPI user is not assigned a Cisco Unity Express voice mailbox. It is a placeholder for Cisco Unity Express to establish a connection with Cisco Unified CallManager.) Verify that the Enable CTI Application use check box is checked for this JTAPI user.
f. If you are using Cisco Unified CallManager 5.0 or later, verify that the AXL service is active. To do this, go to the Cisco Unified CallManager serviceability website, click on Tools > Service Activation. Look for Cisco AXL Web service.
g. During the Cisco Unity Express software installation, create the Cisco Unity Express administrator user ID and password and specify the IP addresses for the DNS server and NTP server. This user ID and password is needed to log in to the initialization wizard.
h. For efficient call processing, configure access lists on the Cisco Unity Express router to prioritize JTAPI traffic. For example:
class-map match-all jtapi
class-map match-all voice
ip address 192.168.10.0 255.255.255.0
service-policy output jtapi
access-list 100 permit udp host 10.3.6.128 any range 16383 32727
access-list 110 permit tcp host 10.3.6.128 any eq 2748
where 10.3.6.128 is the IP address of the module that contains Cisco Unity Express.
The output from the show policy-map interface command should indicate that the marked packets number is increasing. For example:
Packets marked 334 <-----This number should increase.
3. (Required) The FTP server that communicates with Cisco Unity Express must support passive FTP requests. To configure this functionality on the FTP server, see the FTP server documentation.
4. (Optional) If no subscribers were created in the Cisco Unified CallManager interface, create a list of all subscribers, groups, and their extensions to simplify the task of configuring many subscribers and extensions.
5. (Optional) Create an alternate welcome message for the auto-attendant application. Auto attendant includes a default welcome message. You can create a different message in a .wav file and install it as part of the auto-attendant configuration. See "Recording an Auto-Attendant Greeting or Prompt File" for more information.
6. (Optional) Customize the auto-attendant prompt sequence to meet your business requirements. See "Configuring Auto-Attendant Scripts" for more information.
7. (Required) Copy the IP address of the Cisco Unity Express module because you need it to access the GUI to configure the system.
Recording an Auto-Attendant Greeting or Prompt File
Two methods are available to create auto-attendant greeting and prompt files:
•Create a .wav file with the following format: G.711 u-law, 8 kHz, 8 bit, Mono. The file cannot be larger than 1 MB. After recording the greeting, use the GUI or Cisco Unity Express can copy command to copy the file in to the Cisco Unity Express system.
•Use the AvT on the TUI to record the greeting or prompt. Dial the GMS telephone number and select the option to record a greeting. When finished recording, save the file. GMS automatically saves the file in Cisco Unity Express.
The GMS prompt filename has the format UserPrompt_DateTime.wav, for example: UserPrompt_11152003144055.wav. You may want to use CLI commands or GUI options to download the file to a PC, rename the file with a meaningful name, and then upload the file back to Cisco Unity Express.
Configuring Auto-Attendant Scripts
Cisco Unity Express provides a set of auto-attendant prompts and a process, called a script, for handling callers' responses to the prompts. You can modify this script so that specific caller responses are handled in a different way. For example, callers can be directed to leave a voice message in a specific mailbox if they call after business hours.
Use the Microsoft Windows software-based script editor that is included with Cisco Unity Express to modify the script or create a new script. See the Cisco Unity Express 2.3 Guide to Writing Auto-Attendant Scripts for guidelines and procedures.
The file cannot be larger than 256 KB.
After creating the script file, save the file on your PC. Use the CLI interface or the GUI option Voice Mail > Scripts to upload the script file to the auto-attendant application.
Restrictions for Implementing Cisco Unity Express
The following restrictions, listed in alphabetical order, apply to Cisco Unity Express.
Backup and Restore
Cisco Unity Express does not support the following backup and restore capabilities:
•Scheduled backup and restore operations. The backup and restore procedures begin when you enter the appropriate command.
•Centralized message storage arrangement. The Cisco Unity Express backup files cannot be used or integrated with other message stores.
•Selective backup and restore. Only full backup and restore functions are available. Individual voice-mail messages or other specific data cannot be stored or retrieved.
Hardware Limitations
•Only one Cisco Unity Express module per router chassis is permitted, regardless of the number of module slots in the chassis.
•The hard disk on the NM cannot be replaced. If the network module's hard disk crashes, you must replace the network module.
•The NM's front panel Fast Ethernet 0 port is not used by the Cisco Unity Express applications and is disabled. The Fast Ethernet 1 port connects the Cisco Unity Express network module to the router and is the only active Fast Ethernet port on the network module.
•Online insertion and removal (OIR) of the Cisco Unity Express NM is available only on the Cisco 3745 and 3845 routers. The replacement module must be the same type as the original module. OIR is not available for the AIM.
Caution If the NM or AIM flash memory card must be replaced, manually shut down the Cisco Unity Express application before removing the module from the chassis to prevent file corruption and data loss.
•The AIM must be installed only in slot 1 of the Cisco 3745 router chassis. Installing it in slot 0 may damage the AIM module.
Networking
•Cisco Unity Express supports voice-mail networking only with other Cisco Unity Express and Cisco Unity voice-mail systems. Networking support for other voice-mail systems is not available in Cisco Unity Express.
Other Restrictions
•Cisco Unity Express is an embedded system and provides no access to the Linux system. Users cannot add other Linux-based applications to the Cisco Unity Express module.
•Cisco Unity Express does not support Cisco Networking Services or Subnetwork Access Protocol (SNAP) autoprovisioning.
•Cisco Unity Express does not support CiscoWorks configmaker.
System Functionality
•Only one person with administrator privileges and four people with user privileges may log in to the GUI simultaneously.
•Date and time are determined by the Network Time Protocol (NTP) server and cannot be set in the Cisco Unity Express software. Cisco Unity Express can be configured as an NTP client. See the NTP configuration section in the Cisco Unity Express 2.3 CLI Administrator Guide and your NTP server documentation for more information.
•Cisco Unity Express supports one language on the system at a time. This language controls the telephone user interface (TUI) system prompts and greetings. The administrative interfaces (GUI and CLI) are available only in United States English. The call platform controls the telephone displays, which may be available in multiple languages and are independent of the Cisco Unity Express supported languages. See the Release Notes for Cisco Unity Express 2.3 for a list of Cisco Unity Express supported languages.
Voice-Mail Application
•Cisco Unity Express supports two greetings per subscriber, one standard greeting and one alternate greeting. The greetings' time is included in the subscriber's allotted mailbox storage space.
