Configuring CME and CUE Integration using the CLI
The CUE initialization wizard is handy, and certainly provides an administrator an easy way to configure a system quickly; however it is not absolutely essential to run the Wizard for CUE to operate correctly. It is also very useful to know how to configure CUE integration manually since, on first login, if the initialization wizard is not run, it is not possible to re-run the wizard (unless you factory reset, of course, which will take time!). This article walks through the minimum configuration required to integrate CUE with CME using only the CLI.
The steps required are:
- Define the SIP proxy server IP addres (i.e. the CME gateway)
- Define the voicemail application and associated a SIP trigger; in other words, the voicemail pilot
- (Optional) Define the numbers to be used for Message Wait Indication (MWI)
The first step is to define the SIP proxy server address. This is the IP address of the CME gateway (defined under telephony-service).
ccn subsystem sip
gateway address "192.168.255.99"
gateway port 5060
end subsystem
Verify that your configuration is correct using show ccn subsystem sip.
se-192-168-255-98# sh ccn subsystem sip
SIP Gateway: 192.168.255.99
SIP Port Number: 5060
DTMF Relay: sip-notify,sub-notify
MWI Notification: outcall
MWI Envelope Info: disabled
Transfer Mode: bye-also
SIP RFC Compliance: Pre-RFC3261
Next, the voicemail application is defined, and a trigger (or pilot) assigned. The maximum number of sessions will depend on the license applied to the device.
ccn trigger sip phonenumber 8888
application "voicemail"
enabled
maxsessions 6
end trigger
Verify that the configuration has been applied and the application created using show ccn trigger sip.
se-192-168-255-98# show ccn trigger sip
Name: 8888
Type: SIP
Application: voicemail
Locale: systemDefault
Idle Timeout: 10000
Enabled: yes
Maximum number of sessions: 6
Lastly, and optionally but recommended, is to configure MWI DN's. For CCM this is a little different, however this article focuses on CME.
ccn application ciscomwiapplication aa
parameter "strMWI_OFF_DN" "882...."
parameter "strMWI_ON_DN" "881...."
se-192-168-255-98# sh ccn application
Name: ciscomwiapplication
Description: ciscomwiapplication
Application type: aa
Script: setmwi.aef
ID number: 0
Enabled: yes
Maximum number of sessions: 6
CallControlGroupID: 0
strMWI_OFF_DN: 882....
strMWI_ON_DN: 881....
Now interestingly, the Cisco documentation for Cisco Unity Express indicates that outcall notification has been retained for backward compatibility, so it would be worth considering enabling at least Unsolicited MWI notify. More information is available here http://www.ccievoicestudy.com/Cisco/VoIP/Message_Waiting_Indication_(MWI)_explained:_CUE_and_CME/