Unity Connection-CUCME Lab 5 – Unity Connection & CUCME Baltimore Integration

Now that the New York CUCME has been integrated with Unity Connection, we will now provision basic voice mail connectivity for the CUCME users in Baltimore.

Lab 5.1 – Unity Connection & Baltimore CUCME Integration Tasks

1. Configure the Baltimore CUCME router to interface with Unity Connection via SCCP.

2. Use extension 2999 as the voicemail pilot.

3. Create voicemail users and mailboxes for Baltimore users for testing purposes.

4. Use PIN 135246 for each user and ensure that it never expires.

5. Users should be forced to enroll the first time they access Unity Connection.

6. Ensure that users receive their proper greeting when they dial from their Cisco IP Phone.


Lab 5.2 – Unity Connection & Baltimore CUCME Integration Verification

1. The first step for this lab is to configure the Baltimore CUCME router to integrate with Unity Connection. The first document to review is the Cisco Unified Communications Manager Express SCCP Integration Guide for Cisco Unity Connection Release 7.x, specifically the section “Programming a Cisco Unified Communications Manager Express Router to Integrate with Cisco Unity Connection (Without a Connection Cluster)”.

Note, this document does not call out the need for a VOIP dial-peer, which of course is necessary in order for Baltimore to connect with Unity Connection in New York. Also, pay attention to both how the actual ephone integration works, as well as MWI; both are different than CUE.

The appropriate sections of the configuration are below.

baltimore#sh run
!
!
dial-peer voice 2999 voip
description VOIP peer to Unity Connection
destination-pattern 2999
session target ipv4:10.1.20.20
codec g711ulaw
no vad
!
!
telephony-service
voicemail 2999
!
!
ephone-dn 1 dual-line
number 1001
label Arliss Michaels 1001
description 410-555-1001
name Arliss Michaels
call-forward busy 2999
call-forward noan 2999 timeout 4
!
!
ephone-dn 2 dual-line
number 1002
label Cal Ripken 1002
description 410-555-1002
name Cal Ripken
call-forward busy 2999
call-forward noan 2999 timeout 4
!
!
!
!
ephone-dn 5 dual-line
number 2999
description CUC1-VI1
name Unity Conneciton
huntstop channel
!
!
ephone-dn 6
number 8000 secondary 8001
mwi on-off
!
!
!
ephone 3
device-security-mode none
vm-device-id CUC1-VI1
button 1:5
!


2. The Unity Connection Integration is clearly documented in the “Creating a New Integration with Cisco Unified Communications Manager Express” section of the Cisco Unified Communications Manager Express SCCP Integration Guide for Cisco Unity Connection Release 7.x guide.

3. Add Arliss Michaels and Cal Ripken in much the same fashion as you did for Lab 4. Then, set up each user’s voicemail box and leave some test messages. Also, try forward messages to users in New York, and vice versa.


Lab 5.3 – Unity Connection & Baltimore CUCME Wrap-up

Since the Unity Connection Demo License only has two ports, we are somewhat constrained on integrating Los Angeles. I’ve played with some possible work-arounds, where users in Los Angeles were able to access Unity Connection. However, I was unable to get MWI to function properly. Therefore, the next couple of labs will involve removing the Baltimore CUCME Integration, adding Los Angeles, reconfiguring CUE in Baltimore, and then attempt to integrate CUE with Unity Connection.