Tuesday, July 28, 2009

Unity Connection-CUCME Lab 4 – Unity Connection & CUCME New York Integration

With the basic CUCME setup completed in Lab 2 and an initial installation of Unity Connection in Lab 3, we will now provision basic voice mail connectivity for the CUCME users in New York.

Lab 4.1 – Unity Connection & New York CUCME Integration Tasks

1. Configure the New York CUCME router to interface with Unity Connection via a SIP Trunk.

2. Use extension 2999 as the voicemail pilot.

3. Create voicemail users and mailboxes for NYC 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 4.2 – Unity Connection & New York CUCME Integration Verification
Seemingly simple, this lab presented me with a challenging troubleshooting curve ball.

1. To configure the SIP Trunk from the NYC CUCME Router to Unity Connection, refer to the Cisco Unified Communications Manager Express SIP Trunk Integration Guide for Cisco Unity Connection Release 7.x. I suggest reading this entire document prior to beginning this lab.

For the CUCME CLI configuration, follow the instructions provided in the section “Programming the Cisco Unified Communications Manager Express Phone System for Integrating with Cisco Unity Connection”. The truncated output is as follows:

newyork#sh run
!
voice service voip
no supplementary-service sip moved-temporarily
!
!
!
dial-peer voice 2001 voip
description ucnx01
max-conn 2
destination-pattern 2999
session protocol sipv2
session target ipv4:10.1.20.20
dtmf-relay rtp-nte
codec g711ulaw
no vad
!



2. The next step, although not articulated in the Cisco Unified Communications Manager Express SIP Trunk Integration Guide for Cisco Unity Connection Release 7.x document, is to provision the CUCME SIP phones for voicemail. The process is very similar to the CUCME-CUE Lab 9 – New York City Messaging lab. Below are the truncated commands.



!
voice register global
mwi stutter
mwi reg-e164
!
!
!
voice register dn 1
number 2001
call-forward b2bua busy 2999
call-forward b2bua mailbox 2999
call-forward b2bua noan 2999 timeout 20
name Ari Gold
label Ari Gold 2001
mwi
!
voice register dn 2
number 2002
call-forward b2bua busy 2999
call-forward b2bua mailbox 2999
call-forward b2bua noan 2999 timeout 20
name David Wright
label David Wright 2002
mwi
!
voice register dn 3
number 2003
call-forward b2bua busy 2999
call-forward b2bua mailbox 2999
call-forward b2bua noan 2999 timeout 20
name Eli Manning
label Eli Manning 2003
mwi
!



3. I then return to the Cisco Unified Communications Manager Express SIP Trunk Integration Guide for Cisco Unity Connection Release 7.x document, following the step to configure Unity Connection as discussed in Creating a New Integration with Cisco Unified Communications Manager Express. The integration on Unity Connection is fairly straight forward, so I will not rehash the steps, which are pretty clear in the document and links referenced above.


4. Finally, I add the voicemail user profiles for Arliss Michaels, David Wright, and Eli Manning as described in the Testing the Integration section of the Cisco Unified Communications Manager Express SIP Trunk Integration Guide for Cisco Unity Connection Release 7.x guide. Here I will point out a few modifications. First, for the ease of lab management, I disable the complex password requirements for users under System Settings > Authentication Rules > Recommended Voice Mail Authentication Rule by un-checking the “Check for Trivial Passwords” box.


For each user I modify their Password Settings by checking the “Does Not Expire” box and supplying a default password of 123456.

5. At this point, I am ready to set up each user’s voicemail TUI. On each phone, I press the voicemail key and walk through the Setup Wizard. I then proceed to leave a view voicemails, but quickly notice that MWI is not functioning. I first reviewed the MWI parameters on Unity Connection in regards to the Cisco Unified Communications Manager Express SIP Trunk Integration Guide for Cisco Unity Connection Release 7.x guide, and everything seems to match. Next, I review my previous CUCME-CUE integration from the CUCME-CUE Lab 9 – New York City Messaging lab and notice that I’ve missed the following commands:

sip-ua
mwi-server ipv4:10.1.20.20 expires 3600 port 5060 transport udp


However, within a few minutes of adding these commands I noticed that my SIP phones were spontaneous rebooting. When logging into the router CLI, I also notice horrific response time. My next step was to refer to the Cisco Unity Connection Integration of the Cisco Unified Communications Manager Express System Administrator Guide. Unfortunately, this document was of little value, since it points to a much older Unity Connection 1.1 integration document.

Next, I run the “sh processes cpu sorted” command and notice the two SIP process have consumed the majority of the CPU cycles.

newyork#sh processes cpu sorted
CPU utilization for five seconds: 98%/6%; one minute: 20%; five minutes: 8%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
327 49040 12373 3963 60.20% 10.58% 2.63% 0 CCSIP_SPI_CONTRO
329 22812 10307 2213 21.92% 3.86% 0.98% 0 CCSIP_UDP_SOCKET


Here’s where some dumb luck saved the day…

I add the “unsolicited” keyword to the mwi-server command above, and vola, issue solved.

sip-ua
mwi-server ipv4:10.1.20.20 expires 3600 port 5060 transport udp unsolicited


We can see almost immediately that the SIP process begins to return to normal. An explanation of the unsolicited option is available here.

newyork#sh processes cpu sorted
CPU utilization for five seconds: 12%/0%; one minute: 41%; five minutes: 19%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process
327 73376 15862 4625 4.55% 20.75% 8.98% 0 CCSIP_SPI_CONTRO
329 37644 13965 2695 2.15% 11.87% 4.61% 0 CCSIP_UDP_SOCKET



Lab 4 Unity Connection & New York CUCME Integration Wrap-up

One final note. During my staging and configuration, I could not help but notice that my VM image of Unity Connection was running extremely slow. The Performance tab VMWare Infrastructure Client was informing me that the memory utilization was running constantly near 100%. As a result, I have adjusted the amount of memory allocated from the original 1024MB, as described in Unity Connection-CUCME Lab 3 – Unity Connection Installation on VMware ESX 3.5, to 2048MB.