Enable Caller-id globally on Cisco Unity Express (CUE)

By default Cisco Unity Express only reports the called number in your message for internal calls.

It’s quite simple to change this so that all calls (where a number is available) have their numbers reported.

Router# service-module service-enable 1/0 session
Trying 192.168.n.2, 2066 ... Open
se-192-168-n-2# conf t
se-192-168-n-2(config)# voicemail callerid
se-192-168-n-2(config)# end
se-192-168-n-2# wr mem
se-192.168-n-2# exit

Session closed

[Connection to 192.168.n.2 closed by foreign host]

Simple really.

Installing two site CME and a single CUE

We have two CME’s and a single shared CUE.



3002 – Phone 1
3003 – Phone 2
3200 – AA Script (outside scope)
3600 – Voicemail
3998 – MWI off
3999 – MWI on


3004 – Phone 1
3005 – Phone 2
3998 – MWI off
3999 – MWI on

on CME1 (Central)

voice service voip
allow-connections sip to h323
allow-connections h323 to sip
allow-connections h323 to h323

interface FastEthernet 0/0
ip address 192.168.n.1
h323-gateway voip interface
h323-gateway voip bind srcaddr 192.168.n.1

interface service-engine 1/0
ip unnumbered FastEthernet0/0
service-module ip address 192.168.n.2
service-module ip default-gateway 192.168.n.1

ip route 192.168.n.2 Service-Engine 1/0

dial-peer voice 3600 voip
destination-pattern 3[126]00
session protocol sipv2
session target ipv4:192.168.n.2
incoming called-number 399[89]....
codec g711ulaw
no vad

dial-peer voice 3004 voip
destination-pattern 300[45]
voice-class h323 1
session target ipv4:cme2_ipaddress
dfmf-relay h245-alphanumberic
ip qos dscp cs3 signalling
no vad

dial-peer voice 3998 voip
destination-pattern 399[89]300[45]
session target ipv4:cme2_ipaddress

voicemail 3600

ephone-dn 1 dual-line
number 3002

ephone-dn 2 dual-line
number 3003

ephone-dn 3
number 3998....
mwi off

ephone-dn 4
number 3999....
mwi on

on CME2 (remote)

dial-peer voice 3002 voip
destination-pattern 300[23]
voice-class h323 1
session target ipv4:cme1_ipaddress
dfmf-relay h245-alphanumberic
ip qos dscp cs3 signalling
no vad

dial-peer voice 3998 voip
incoming called-number 399[89]....

voicemail 3600
mwi relay

ephone_dn 1
number 3004

ephone_dn 2
number 3005

ephone-dn 3
number 3998....
mwi off

ephone-dn 4
number 3999....
mwi on


1. The scope of this post only includes enough info to show CUE integration.

2. It is essential to control the codecs used to inbound and outbound calls. For this reason both the “destination-pattern” as well as the “incoming called-number” is defined on dial-peer 3600 on CME1. This is to ensure that calls coming from and going to CUE use codec g711ulaw.

3. For MWI to be passed between CME1 and CME2 you need to ensure that:

a) “allow-connections sip to h323” is configured inside “voice service voip” on CME1
b) “mwi relay” is configured in “telephony-service” on CME2

CUE Restore Factory Defaults

To restore factory defaults on Cisco Unity Express firstly take the module offline by typing “offline“, then when confirmed issue the “restore factory defaults” command.

An example follows :

Router# service-mode  service-engine 1/0
Trying 192.168.n.3, 2006 ... Open
se-192-168-n-3# offline
!!!WARNING!!!: If you are going offline to do a backup, it is recommended
that you save the current running configuration using the 'write' command,
prior to going to the offline state.

Putting the system offline will terminate all end user sessions.

Are you sure you want to go offline[n]? : y
se-192-168-n-3(offline)# restore factory default
!!!WARNING!!!: This operation will cause all configuration and data
on the system to be erased. This operation is not reversible.

Do you wish to continue[n]? : y
Restoring the system. Please wait .....done
System will be restored to factory default when it reloads.

Press any key to reload:

System reloading ....

INIT: Sending processes the TERRestarting system.

-- SNIP --

INIT: Entering runlevel: 2
********** rc.post_install ****************

IMPORTANT::    Welcome to Cisco Systems Service Engine
IMPORTANT::     post installation configuration tool.
IMPORTANT:: This is a one time process which will guide
IMPORTANT:: you through initial setup of your Service Engine.
IMPORTANT:: Once run, this process will have configured
IMPORTANT:: the system for your location.
IMPORTANT:: If you do not wish to continue, the system will be halted
IMPORTANT:: so it can be safely removed from the router.

Do you wish to start configuration now (y,n)?

Once this has completed you proceed to setup the hostname, whether to use dns and ntp settings. After this configuration the booting process can take quite some time !