This lab will focus on the initial setup for CUE on the Baltimore 2811, as well as setting up basic voicemail for the Baltimore users. This lab and subsequent CUE labs are based on CUE 7.0. If you need to update you CUE image, excellent, well described instructions are outlined in the Cisco Unity Express 7.0 Installation and Upgrade Guide.
CUCME-CUE Lab 8.1 – Initial CUE Setup & Baltimore Messaging Tasks
1. Configure the Baltimore CUCME router to interface with CUE. Use extension 1999 as the voicemail pilot.
2. The IP Address for CUE should come from the voice subnet.
3. Use 8000 and 8001 for MWI.
4. Create voicemail users and mailboxes via the CUE CLI.
5. Mailboxes should be limited in size to accommodate up to 50 users on a AIM-CUE.
6. Make sure that messages can be forward via either dial by name or by extension.
7. Provision the system for GUI access.
CUCME-CUE Lab 8.2 – Initial CUE Setup & Baltimore Messaging Verification
1. Before you can begin configuring the CUE, you need to make some configuration modifications to the CUCME. A dial-peer needs to be created pointing to CUE. Next, the voicemail pilot needs to be added under the telephony-service. MWI is then created via an ephone-dn. Finally, call-forwarding needs to be provisioned for each user.
The details regarding the initial configuration parameters are covered in Configuring System Components chapter of the Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions.
Below are the configuration changes.
dial-peer voice 1999 voip
session protocol sipv2
session target ipv4:10.1.12.3
ephone-dn 1 dual-line
call-forward busy 1999
call-forward noan 1999 timeout 4
!repeat for ephone-dns 2-5!
username "cripken" password null
!repeat for ephones 2-5!
2. Next step is to enable IP connectivity to the CUE. This requires some additional configuration on the CUCME side of the equation.
ip unnumbered GigabitEthernet1/0.12
service-module ip address 10.1.12.3 255.255.255.0
service-module ip default-gateway 10.1.12.1
Once you’ve finished the above, you can session into the service-engine (CUE AIM).
Baltimore#service-module service-Engine 0/0 se
Baltimore#service-module service-Engine 0/0 session
Trying 10.1.12.1, 2194 ... Open
In the example above, I had previously logged into the CUE. If you haven’t yet done so, you will need to complete some basic CUE initialization tasks. Unfortunately, I was unable to find a concise document online that clearly articulates this initialization wizard. It is touched upon here. However, Chapter 11 of the IP Telephony Using CallManager Express Lab Portfolio covers it very well.
3. Now that there is connectivity between CUCME and CUE, users and mailboxes can now be created. Unfortunately, due to the way the CUE CLI functions, you have to create users in a somewhat disjointed fashion. The first step is to create the user and his/her phone numbers under configuration mode.
baltimore-cue(config)# username cripken create
baltimore-cue(config)# username cripken phonenumber 1001
baltimore-cue(config)# username cripken phonenumberE164 4105551001
Next, you need to create the mailbox for the use. However, per the requirement above, the configuration must support up to 50 users, thereby limiting the mailbox size to 720 seconds.
baltimore-cue(config)# voicemail mailbox owner "cripken" size 720
baltimore-cue(config-mailbox)# description "cripken mailbox"
baltimore-cue(config-mailbox)# end mailbox
In order to facilitate the dial by name requirement, you must exit configuration mode and then modify the users their full first and last names.
baltimore-cue# username cripken fullname first Cal
baltimore-cue# username cripken fullname last Ripken
Finally, you can verify the user and the associate mailbox by issuing the “show user detail username NAME” and “show voicemail detail mailbox NAME” commands
baltimore-cue# show user detail username cripken
Full Name: Cal Ripken
First Name: Cal
Last Name: Ripken
Nickname: Cal Ripken
baltimore-cue# show voicemail detail mailbox cripken
Description: cripken mailbox
Busy state: idle
Allow login without pin: no
Mailbox Size (seconds): 720
Message Size (seconds): 240
Play Tutorial: false
Fax Enabled: true
Space Used (seconds): 0
Total Message Count: 0
New Message Count: 0
Saved Message Count: 0
Future Message Count: 0
Deleted Message Count: 0
Fax Message Count: 0
Expiration (days): 30
Zero Out Number:
Created/Last Accessed: Feb 27 2009 17:47:37 EST
4. The final requirements on CUE involve configuration for communicating with CUCME and passing MWI. First, configure SIP to reach CUCME.
ccn subsystem sip
gateway address "10.1.12.1"
Next, the SIP trigger for the voicemail pilot, 1999, must be added to the system.
ccn trigger sip phonenumber 1999
Finally, MWI must be enabled.
ccn application ciscomwiapplication aa
parameter "strMWI_OFF_DN" "8001"
parameter "strMWI_ON_DN" "8000"
CUCME-CUE Lab 8.3 – Initial CUE Setup & Baltimore Wrap Up
CUCME and CUE has now been properly configured to interoperate. The best way to test the configuration is to place calls between phones and leave message. However, prior to this, each mailbox will require completion of the TUI setup wizard. Looking ahead, I will explore what it takes to have CUE support remote users, specifically the New York CUCME.
Au, Danelle, et. al. (2005). Cisco IP Communications Express: CallManager Express with Cisco Unity Express. Indianapolis: Cisco Press.
Cisco Systems. Cisco Unity Express 7.0 Installation and Upgrade Guide. Available online.
Cisco Systems. Cisco Unity Express 7.0 Release Notes. Available online.
Cisco Systems. Cisco Unity Express Voice-Mail and Auto-Attendant CLI Administrator Guide for 3.0 and Later Versions. Available online.
Schmidt, Cheryl A., and Friend, Ernie (2007). IP Telephony Using CallManager Express Lab Portfolio. Indianapolis: Cisco Press.