CUE Notes
Connectivity
To connect to module: service-module service-Engine 1/0 session
IP Configuration:
interface Service-Engine1/0
ip unnumbered FastEthernet0/0.311
service-module ip address 177.3.11.254 255.255.255.0
service-module ip default-gateway 177.3.11.1
!
ip route 177.3.11.254 255.255.255.255 Service-Engine1/0
Basic Configuration
Take offline – offline
Set to default – restore factory default
Cue will run you through the setup script
Changing the License
You may need to change the integration between CME and UCM. You need to install a license to do this. Start a FTP server with the correct license in the home path. From the CUE module, do a ‘software install clean url’ command. Pretty self explanatory from there.
CUE with CME Configuration
URL available during the lab :
Configure dial-peers for CME to CUE Voicemail
dial-peer voice 2 voip
! this is the pilot VM number
destination-pattern 3600
session protocol sipv2
session target ipv4:10.10.202.2
codec g711ulaw
no vad
! this is for MWI
incoming called-number 399[89]….
Configure Voicemail Access
telephony-service
voicemail 3600
web admin system name admin password cisco
call-forward pattern .T
! H450.2 method for transfer
transfer-system full-consult
! needed to transfer to voicemail
transfer-pattern .T
! add CFB and CFNON to DN’s
ephone-dn 1
call-forward busy 3600
call-forward noan 3600 timeout 12
Configure the HTTP server
ip http server
ip http authentication local
ip http path:/GUI
Configure MWI’s
ephone-dn 10
number 3999…. no-reg primary
mwi on
ephone-dn 11
number 3998…. no-reg primary
mwi off
Configure the Voicemail Application
ccn application voicemail
description “Cisco Voicemail”
Configure CUE via the GUI
- Run the wizard, set the web user name and import the users
- Set the voice mail number and the MWI method (make sure that the MWI on/off numbers show up
CUE with CME Configuration
CME Configuration
1. Configure dial peer for communication between CME and CUE.
Dial-peer voice 2 voip
Destination-pattern (DID to voicemail)
Session protocol sipv2
Session-target ipv4:x.x.x.x
dtmf-relay sip-notify
no vad
codec g711ulaw
2. Configure voicemail access
Telephony-service
Voicemail (dn)
Call-forward pattern .T
Web admin system name admin password cisco
Dn-webedit
Transfer-system full-consult
Transfer-pattern .T
3. Configure ephone-dn to forward to voicemail
Ephone-dn (tag)
Call-forward busy (vm dn)
Call-forward noan (vm dn) time 10
4. Configure MWIs
Configure ephone-dn for MWI on and one for off. Below turns on MWI
Ephone-dn (tag)
Number (dn)
Mwi on
5. Configure SIP
Sip-ua
Mwi-server ipv4:10.10.202.2
Voice register dn 2
Call-forward b2bua busy 3600
Call-forward b2bua mailbox 3600
Call-forward b2bua noan 3600 timeout 12
Voice register pool 2
Dtmf-relay rtp-nte
Voice register global
Voicemail 3600
Create profile
Reset
CUE Configuration from GUI
- Run the installation wizard
Import the users (sccp only).
Check mailbox and set cfna/cfb
Set the defaults
Configure the call handling numbers
2. Modifiy/create users
SIP phones need manual user addition
3. Set the MWIs
Subscribe – notify for SIP phones
CUE general delivery mailbox (GDM)
1. Create voice hunt group in CME. Make final number the normal voicemail DN.
2. Add group on CUE. Add members to group. Enable mailbox.
CUE Configuration from CLI
1. Configure voicemail application
Ccn application voicemail
Description “cisco voicemail”
Maxsessions (x)
2. Configure auto-attendant
Ccn application auto-attendant
Parameter “operExtn” “(dn)”
3. Configure SIP triggers for applications.
Ccn trigger sip phonenumber (dn) – dn should match voicemail dn
enabled
4. Create users
Username John create
Username John phonenumber (dn)
5. Configure mailboxes
Voice mailbox owner John
Enable
Expiration time
Mailboxsize
Messagesize
CUE with CUCM examples
CUE configuration
Use steps listed above for the CUE portion
CM Configuration
1. Create CTI ports. One port for each CUE port. Device pool must match where the CUE is installed – the codec must match.
Device > phone
Add a new phone
Choose CTI port
Assign a DN to the CTI port. DN has no correlation with what users might call.
2. Add CTI route points. Normally three CTI route points: voicemail, one for each AA and one for GMS to manage recorded prompts.
Device > CTI route point
Add a new CTI route point
Name the device
Configure device pool and location
Configure the CSS and ensure that this includes the partition with the DNs of the CTI ports.
Add a DN for each route point (DN is voice mail pilot)
3. Create JTAPI user, grant CTI permissions and associate devices
User management > application user
Add new
Specify a user id
Add the user to the standard CTI enabled role. If you don’t do this or add to a different role. the CTI point will not register.
In the device information field, under available devices, select the route points and CTI ports that are associated with the ID.
In the permissions information section, click add user to group. Select standard CTI enabled.
4. Create a voicemail pilot and a voicemail profile
5. Assign the voicemail profile to the DN.
Voice CCIE Study Material 