Showing posts with label Unity Connection. Show all posts
Showing posts with label Unity Connection. Show all posts

Monday, February 8, 2010

CCIE Voice Lab 1.11 – Unity Connection and CUE

In CCIE Voice Lab 1.11, the New York, Los Angeles, and London locations will be configured to support voice messaging and associated components.

CCIE Voice Lab 1.11 Tasks

1. Configure Cisco Unity Connection (CUC) integration with CUCM. You must integrate using SCCP. Use pilot 1170, directory number 1171 and 1172, and 1180 for MWI-on and 1181 for MWI-off.

2. Configure Unity Connection voicemail for all users in New York and Los Angeles. Users must be imported from CUCM. Ensure that the users in the directory are listed last name, first name. Accounts should be created with the following requirements:
a. No Limit for Failed Logons
b. Credential Never Expires
c. Minimum Credential Length: 5
d. Stored Number of Previous Credentials: 0
e. No Check for Trivial Passwords
f. User must be prevented from sending Broadcast Messages to Users

3. Configure an Auto Attendant for NY with DN 1000. Configure the AA so that when users press “0” they are routed to Ari Gold at ext. 1001. Business hours are 8AM – 6PM EST/EDT. Customize the greeting as follows:
a. Allow callers to press “4” to use the phone keypad to spell all or part of the last then first name of the Connection user that they want to reach.
b. At the end of the greetings, users should be sent to a Directory Handler. If a Caller Exits, he/she should be sent back to the NY Opening Greeting. If a caller provides No Input, No Selection or Presses Zero, the call should be routed back to Ari Gold’s mailbox.
c. After hours messages should also be stored in Ari Gold’s mailbox.

4. Configure an Auto Attendant for LA with DN 2000. Configure the AA so that when users press “0” they are routed to Arliss Michaels at ext. 2001. Business hours are 8AM – 6PM PST/PDT. Customize the greeting as follows:
a. Allow callers to press “4” to use the phone keypad to spell all or part of the last then first name of the Connection user that they want to reach.
b. At the end of the greetings, users should be sent to a Directory Handler. If a Caller Exits, he/she should be sent back to the LA Opening Greeting. If a caller provides No Input, No Selection or Presses Zero, the call should be routed back to Arliss Michaels’s mailbox.
c. After hours messages should also be stored in Arliss Michaels’s mailbox.

5. Configure a second line appearance on Ari’s phone using *1001. When Ari’s primary extension is busy, calls should roll to this number, followed by voicemail. This line should be able to access voicemail in Ari’s mailbox.

6. London CUCME users should use their local CUE for voicemail, with the following parameters: pilot 3170; and 3180 for MWI-on and 3181 for MWI-off. Create mailboxes for Jerry Maguire and David Beckham with blank passwords and PINS.

7. Create an AA in London using ext 3000. Ensure that callers in NY and LA can reach the AA via VOIP as well as PSTN dialing.


CCIE Voice Lab 1.11 Solutions

1. The Cisco Unified Communications Manager SCCP Integration Guide for Cisco Unity Connection Release 7.x is an excellent document for describing the tasks required to integrate CUC with CUCM. I more or less used the examples and naming conventions provided in Programming the Cisco Unified CM Phone System for Integrating with Cisco Unity Connection section of the Setting Up a Cisco Unified Communications Manager 7.x SCCP Integration with Cisco Unity Connection chapter.

Below is screenshot of the final page of the Cisco Voicemail Port Wizard.



After the wizard finishes, configure the Hunt List and Hunt Pilot.Then, add the MWIs, Voice Mail Pilot Number for the Voice Mail Ports, and Voicemail Profile, per the instructions in Programming the Cisco Unified CM Phone System for Integrating with Cisco Unity Connection.

Now, proceed to Creating a New Integration with Cisco Unified Communications Manager. Do not forget to add your Pub as an AXL Server under the Phone System Configuration, as well as adding Unity Connection as an Application Server in CUCM.

2. To modify “No Limit for Failed Logons”, “Credential Never Expires”, “Minimum Credential Length: 5”, and “Stored Number of Previous Credentials: 0”, modify the default “Voice Mail Authentication Rule” under System Settings > Authentication Rules.

Looking ahead to the AA configuration, it would be wise to create a new schedule under Systems Settings > Schedules. Then, apply this new schedule to the Templates > User Templates > voicemailusertemplate.

Next, to ensure that users cannot send Broadcast Messages to Users on This Server, verify that “User Can Send Broadcast Messages to Users on This Server” is not-checked under Templates > User Templates > voicemailusertemplate > Send Message Settings.

Finally, you can import users from CUCM from Tools > Import Users. Be aware, users in CUCM must have their primary extension define. Visit Creating Multiple User Accounts from Cisco Unified Communications Manager Users for a good overview. Keep in mind that when you import your users, they will inherit the system Timezone. For your LA based users, you will need to modify their Timezone to PST.

3. Now we are ready to create the AA for both New York and Los Angeles. The process if almost identical. Basically, I create two now Call Handlers, “NY-Opening-Greeting” at extension 1000 and “LA-Opening-Greeting” at extension 2000. Edit the Greetings and Caller Input to match the task requirements. I then created to new Directory Handlers, one for NY and another for LA. I edit the Caller Input for each based on the task requirements.

4. Task 5 is relatively straight forward. Create a new Voice Mail Profile for the *1000 extension with a Voice Mail Box Mask of 1000; this strip the “*”. When you add the *1000 dn to Ari’s Phone, make sure that you use this Voice Mail Profile on this line appearance.

5. We now move on to CUE. Given that I covered CUE extensively in the CUCME-CUE Labs, so I will not recap the details here. However, I did run into an issue, which I haven’t fully yet fixed….

Because the SIP dial peer to the AA in London is not H323, it does not register with the gatekeeper. Therefore, I cannot dial 73000 from either NY or LA to hit the AA in London. I tried adding the e164 via the alias commands under gatekeeper. However, this is only a temporary fix and will not work in the actual lab. When you reboot either the gatekeeper (NY) or the CUCME router (London), the CUCME (London) will attempt to register using a random port. Since the alias command uses a static port (either 1719 or random, depending on how you initialing configuring), the RRQ from the gateway will be rejected (RRJ) by the Gatekeeper. I’ve spent a fair number of hours trying to find a work around, nothing has successfully worked. For now, I am moving on. If anyone finds a resolution, please share!

Monday, August 31, 2009

Unity Connection-CUCME Lab 7 – Baltimore CUE

This lab will revisit setting up CUE in Baltimore for eventual integration with Unity Connection via VPIM. It will be very similar to CUCME-CUE Lab 8.


Unity Connection Lab 7.1 – Baltimore CUE Tasks

1. Configure the Baltimore CUCME router to interface with CUE, using IP address 10.1.12.3/24.

2. Use extension 1999 as the voicemail pilot.

3, Use 8000 and 8001 for MWI.

4. Create voicemail users and mailboxes via the CUE CLI.

5. Mailboxes should be limited in size to accommodate up to 50 users on a AIM-CUE.

6. Make sure that messages can be forward via either dial by name or by extension.

7. Provision the system for GUI access.


Unity Connection Lab 7.2 – Baltimore CUE Verification

Since the tasks here are almost identical to CUCME-CUE Lab 8, please refer to that previous post for help on answers. Note, the Baltimore dial plan for Arliss Michaels and Cal Ripken is slightly different, refer to Unity Connection-CUCME Scenario Background.


Unity Connection Lab 7.3 – Baltimore CUE Wrap-up

The original intention for this lab was to stage Baltimore and then integrate with Unity Connection via VPIM. However, after some thought, I am not sure this is applicable for the CCIE Voice Lab. During the CCIE Voice Techtorial and Cisco Live 2009, the present suggested that the CCIE Voice lab would not have a DNS server. Based on some initial research for VPIM integration, DNS is a requirement. Therefore, one could infer that VPIM would not be tested in the Voice Lab.

That said, I will spend some time pretesting VPIM integration between Baltimore CUE and Unity Connection. If this testing consumes too much time and integration with DNS, I may abort and move on to some other items.

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.

Wednesday, June 10, 2009

Unity Connection-CUCME Lab 3 – Unity Connection Installation on VMware ESX 3.5

This lab discusses the procedures that I followed to install Unity Connection on a VMware ESX 3.5 Server. A special thanks to Ket Hum, a Federal Channels UC SE with Cisco, for giving me some tidbits.

1. My VMware ESX 3.5 server is installed on a DL320-G5 with two 750GB drives and 8GB of memory. My first step was to create separate vSwitch for the 10.1.20.0/24 New York Management VLAN.


2. Next step is to launch the “Create a new virtual machine” wizard.


As I walk through the New Virtual Machine Wizard, I select the following:

- Virtual Machine Configuration: Typical
- Guest Operating System: Linux > Red Hat Enterprise Linux 4 (32-bit)
- Memory: set to 1024MB
- Create Network Connection: One NIC on vSwitch1 (UC Network 10.1.20.0)
- Disk Size: 146GB (drive size of a MCS7835)


3. This next step is important… Prior to completing the wizard, check the “Edit the virtual machine settings before submitting” option. This allows us to statically assign the MAC address of the VM.


4. At this point, the wizard completes and the VM is created. You then can either boot the VM via an ISO image or DVD copy of Unity Connection. I opted to boot from an ISO copy of the image that I have on the storage of the ESX server; this is far quicker than booting and installing from the DVD.


5. At this point, you can proceed with the normal installation process. Installing Unity Connection is fairly easy; the Installation Guide for Cisco Unity Connection Release 7.x provides clear instructions regarding the tasks and process.

6. Once the installation process completes, login with your administrator username and password. Note, the console will tell you that VMware is not a supported platform.


7. The final step of the installation process is to very login via the web interface; in the case of this lab https://10.1.20.20/cuadmin. You can also few the demo license that comes with Unity Connection, which supports 10 mailboxes and 2 ports. Lastly, I used the snapshot feature in ESX. This will make things very easy to roll back to the clean image for later labs and study.


Unity Connection-CUCME Lab 3 Wrap-up
I’ve configured a simple Windows 2003 Domain Controller and Active Directory domain, adding users depicted in diagram from the Unity Connection-CUCME Scenario Background posting. With the installation of Unity Connection complete, we will begin the process of configuring the three Ballplayers, LLC CUCME locations to interface with Unity Connection.