Here are all the steps to perform if you want to integrate the CUE with the CME

  1. Create a SIP dial peer pointing to the CUE Module
  2. Configure the MWI On/Off extensions
  3. Configure the connectivity between CME and CUE Modules
  4. Perform CUE Configuration

For the first step , your dial peer will look like

dial-peer voice 1000 voip
destination-pattern 5555
session protocol sipv2
session target ipv4:172.17.1.1
dtmf-relay sip-notify
codec g711ulaw
no vad
!

The configurations of the MWI On/Off must be generic as it must cover all numbers and it is generally implemented as a kind of prefix as the MWI must know which number must be turned on or off. So it adds the number after the extension the MWI shortcut.

ephone-dn 50
number 5000….
mwi on
!
ephone-dn 60
number 6000….
mwi off

Regarding the link configuration between the CUE and CME, you need to borrow the Ethernet interface where the CUE module resides (don’t forget that CME and CUE can be splitted). So everything under the service-engine ( this is the CUE module) will rely on the Ethernet interfaces:

interface Service-Engine 1/0
ip unnumbered FastEthernet 1/0
service-module ip address 172.17.1.1 255.255.255.0
service-module ip default-gateway 172.17.1.254
!
ip route 172.17.1.1 255.255.255.255 Service-Engine1/0
!

In a multi-site implementations , you have then to configure a translation between your remote CME and the central CUE/CME because we told before that CUE relies on SIP Protocol and the rest of your network is an H323 network , so you need to translate all H323 request to SIP. You can do it generally with the config:

!
voice service voip
allow-connections H323 to sip