CUCM-CUE SRST

When integrating CUCM with CUE, you need to consider the functionality of CUE during SRST mode. The methodology is to use SIP triggers on CUE with dialpeers configured on SRST router pointing to CUE as per below configuration. In fact you will be configuring CME-CUE integration to be used in case of SRST.

SRST Router

dial-peer voice 1 voip
 description Local SRE-CUE Voicemail
 destination-pattern 28000
 session protocol sipv2
 session target ipv4:172.18.106.107
 dtmf-relay sip-notify
 codec g711ulaw
 no vad
!
dial-peer voice 2 voip
 description Local SRE-CUE Auto Attendant
 destination-pattern 28100
 session protocol sipv2
 session target ipv4:172.18.106.107
 dtmf-relay sip-notify
 codec g711ulaw
 no vad
!        
dial-peer voice 3 voip
 description Local SRE-CUE Greeting Management System
 destination-pattern 28111
 session protocol sipv2
 session target ipv4:172.18.106.107
 dtmf-relay sip-notify
 codec g711ulaw
 no vad
!                 
!
call-manager-fallback
 ip source-address 172.18.106.105 port 2000
 max-ephones 52
 max-dn 208
 voicemail 28000
 call-forward busy 28000
 call-forward noan 28000 timeout 12

CUE

The three configured destination patterns (28000, 28100, and 28111) correspond to the three DNs assigned to the route points. The CTI ports are not referenced anywhere.

The CUE is set up automatically when you use the Initialization Wizard. This portion must be in the configuration in order to verify from the CLI:

ccn subsystem sip
 gateway address "172.18.106.105"
 end subsystem

...
ccn trigger sip phonenumber 28000
 application "voicemail"
 enabled
 locale "en_US"
 maxsessions 4
 end trigger

ccn trigger sip phonenumber 28100
 application "autoattendant"
 enabled
 locale "en_US"
 maxsessions 4
 end trigger

ccn trigger sip phonenumber 28111
 application "promptmgmt"
 enabled
 locale "en_US"
 maxsessions 1
 end trigger

The gateway address is the Cisco SRST router. The phone number parameters must be the same as the route point DNs.

CME Integration with CUE

Step 1 Activate the network connectivity to CUE from the CME router.

int ISM0/0

 ip unnumbered GigabitEthernet0/0.34

 service-module ip address 10.34.x.251 255.255.255.0

 service-module ip default-gateway 10.34.x.1

 no shut

!

ip route 10.34.x.251 255.255.255.255 ism0/0

Note: For 'ip unnumbered' command to work, you need to make sure that 'proxy-arp' is enabled on the original interface.

Step 2 Configure a dial-peer on the CME router for CME phones to call voicemail number. CUE interface with CME is using SIP protocol only whether you are using SCCP or SIP CME.

dial-peer voice 780 voip

 description **** VOICEMAIL DIAL PEER ****

 destination-pattern xxxyyy

 session protocol sipv2

 session target ipv4:10.34.x.251

 codec g711ulaw

 voice-class sip transport switch udp tcp

 voice-class sip bind control source-interface GigabitEthernet0/0.34

 voice-class sip bind media source-interface GigabitEthernet0/0.34

 dtmf-relay sip-notify rtp-nte

 ip qos dscp cs3 signaling

CUE supports G711ulaw codec only. In case the dial-peer is using other codec, the CME will invoke a transcoder else the call will fail.

Step 3 Configure Voicemail access on Voicemail button.

voice register global

 voicemail 5222121

!

telephony-service

 voicemail 5222121

Step 4 Configure Call forwarding on directory numbers to voicemail

voice register dn  1

 call-forward b2bua busy xxxyyy

 call-forward b2bua noan xxxyyy timeout 30

 call-forward b2bua unregistered xxxyyy

!

ephone-dn 11
 call-forward busy xxxyyy
 call-forward noan xxxyyy time 10

 call-forward unregistered xxxyyy

Step 5 Configure MWI. We will cover this is separate section

Step 6 Configure voicemail application on CUE

Remote connectivity (SSH/Telnet) to CUE module can't be established. You need to console to the CUE module from the router. The credentials of the CUE module will be same as the router (AAA or Local).

service-module ism 0/0 session

On CUE, here is the configuration:

ccn application voicemail
 description "Cisco Voicemail"

 maxsessions 4   !!!... Max simultaneous sessions.

Step 7 Configure Auto-Attendant Application

ccn application autoattendant
 description "Cisco Auto-Attendant"
 maxsessions 4
 parameter "operExtn" "1001"

Step 8 Configure SIP Triggers for applications

ccn trigger sip phonenumber 2000
 application voicemail
 enabled
 maxsessions 4

!

ccn trigger sip phonenumber 2001
 application autoattendant
 enabled
 maxsessions 4

Step 9 Create Users

username John create
username John phonenumber 1002

Note: An administrator user is created by default when you first access CUE and cannot be assigned a voice mailbox.

Step 10 Create Mailboxes

voice mailbox owner John
 description "John's Mailbox"
 enable
 expiration time 10
 mailboxsize 300
 messagesize 120

Note: Not all the subscribers or extensions require a voice mailbox such as an administrator user.

CUCM Integration with CUE

CUCM integrates with CUE through JTAPI protocol for voice mail and automated attendant functionality.

The CUE is able to register with the CUCM through JTAPI and controls CTI Route-Points and CTI Ports. This allows you to control and manage the CUE as an additional endpoint through the CUCM, as well as facilitate the configurations and interactions with other endpoints in the cluster.

What are CTI Ports?

CTI ports are virtual lines that can send and receive audio but are controlled through the JTAPI protocol by CUE.

What are CTI Route Point?

CTI route point is a virtual device controlled by CUE. The CTI route point can receive multiple simultaneous calls and redirect them to the CTI ports configured earlier.

The end user with directory number (DN) 1005 calls the user with DN 1001. The call is forwarded after a few seconds if the call is not answered, Call Forward No Answer (CFNA), to the VM number configured on the user 1001 VM profile. The CUCM then sends the call to the configured VM Pilot 5000, which points to a CTI RP with DN 5000 that is controlled by CUE. The CUE VM application is triggered, and the call is redirected through JTAPI to an available CTI port (DN 5501) for media establishment. The audio greeting plays, and the user can leave a message or interact with the system through dual tone multi-frequency (DTMF) tones. When the caller ends the call, the CUE signals the CUCM to set the Message Waiting Indicator (MWI) lamp for extension 1001 to "On" through JTAPI. The CUCM then sends the Skinny Client Control Protocol (SCCP) message to turn on the light on the phone, as well as show the envelope indication on the display so user 1001 is aware that there is a new VM message in the mailbox.

These configuration tasks are required for integration with CUE:

CUCM

• Create one CTI port for each CUE VM port on the CUCM. The number of CUE VM Ports is controlled by the license. Issue the show software licenses command in order to verify the licenses.
• Add a CTI route point for each entry point in the CUE system. For example, you can add one route point for the voice mail pilot number, one or more for an AA, and one for the Greeting Management System (GMS). CTI Route Point CSS should contain the partition assigned to CTI Ports DNs.
• For CUCM create a JTAPI user that the CUE uses in order to log into the CUCM and take control of the Route Point and CTI port devices. The user should be created as an Application User. Next, the Standard CTI Enabled group policy must be applied and all Route Points and CTI ports must be associated with the user.

If you use multiple CUE modules, this can be the same user, or multiple users, and make sure that all devices (CTI route points and CTI ports) that should be controlled by the account are associated with it.

• Configure voicemail profile if you want to use CUE for voice mail. Configure Call Forward Busy (CFB) or Call Forward No Answer (CFNA) settings to use this profile. Voice mail profile creation involves the creation of a voice mail pilot number. This number is used on the route point for voice mail configuration and the voice mail profile.
• Create users on CUCM and have phones associated with them if necessary. These users can be imported later when the CUE Initialization Wizard runs. This step saves the need to re-enter all users created in CUCM in CUE. The accounts are created once in CUCM and then imported into CUE. CUE will connect to CUCM using AXL user to import the accounts
• Transcoding can be necessary if the CUE is at a remote branch as CUE supports G711ulaw only and typically G729 is used across WAN.

CUE

• Run the Cisco Unity Express Configuration Wizard. This is an easy way to set up the integration on the CUE side and create mailboxes for imported users.
• Alternatively, Log on to the CUE web page as admin user and choose Configure > Users. Then click Import. Note: Only full user IDs can be specified. No wildcards or partial matches are allowed when you search for users.
• One of the current limitations is that CUE mark JTAPI as DSCP 0. You need to mark the packets on the router which hosts the CUE (recommended marking is AF31). CUCM mark JTAPI packets correctly as DSCP=AF31. Also, JTAPI stream consumes an average of 20kbps between CUCM and CUE which needs to be reserved over WAN.

username administrator create
username marschne create
username jdoe create
username marschne phonenumber "2104"
username jdoe phonenumber "2103"

ccn application autoattendant
 description "autoattendant"
 enabled
 maxsessions 4
 script "aa.aef"
 parameter "MaxRetry" "3"
 parameter "operExtn" "0"
 parameter "welcomePrompt" "AAWelcome.wav"
 end application

!

ccn application promptmgmt
 description "promptmgmt"
 enabled
 maxsessions 1
 script "promptmgmt.aef"
 end application

!

ccn application voicemail
 description "voicemail"
 enabled
 maxsessions 4
 script "voicebrowser.aef"
 parameter "logoutUri" "http://localhost/voicemail/vxmlscripts/mbxLogout.jsp"
 parameter "uri" "http://localhost/voicemail/vxmlscripts/login.vxml"
 end application

!

ccn subsystem jtapi
 ctiport 28001 28002 28003 28004      !!!... These are the DNs assigned to CTI ports
 ccm-manager address 14.80.227.127 14.80.227.128
 ccm-manager credentials hidden "+DuGhIBvqsghj6p6aBUoRQ4E0vzCD5YHSd8ZZNgd+
 Y9J3xlk2B35j0nfGWTYHfmPSd8ZZNgd+Y9J3xlk2B35jwAAAAA="
 end subsystem

!

ccn trigger jtapi phonenumber 28000      !!!... This is the DN assigned to CTI Route Point
 application "voicemail"
 enabled
 locale "en_US"
 maxsessions 4
 end trigger

!

ccn trigger jtapi phonenumber 28100
 application "autoattendant"
 enabled
 locale "en_US"
 maxsessions 4
 end trigger

!

ccn trigger jtapi phonenumber 28111
 application "promptmgmt"
 enabled
 locale "en_US"
 maxsessions 1
 end trigger

!

voicemail mailbox owner "jdoe" size 420
 description "jdoe mailbox"
 end mailbox

!

voicemail mailbox owner "marschne" size 420
 description "marschne mailbox"
 end mailbox