BE6K Lab Guide 9

(1)

Cisco Unified Communications Manager

Business Edition 6000 (BE6K) UC 9

Lab Guide

Brought to you by the US Channels and UC Solution Readiness Engineer Organizations

(2)

Cisco Unified Communications Manager Business Edition 6000

Cisco Business Edition 6000 is designed for organizations with up to 1000 employees. The solution offers premium voice, video, mobility, messaging, presence and contact center features on a single platform and provides core communication capabilities medium-sized businesses need for improved collaboration across the value chain. Enabled by virtualization technology, Cisco Business Edition 6000 consolidates multiple applications on single platform and therefore allows medium business to reduce their lower total cost of ownership and improve productivity of their employees. The high availability features supported by the solution make Cisco Business Edition 6000 ideally suited for companies that require mission critical voice, messaging and contact center capabilities.

BE 6000 consists of the following foundational elements: • Cisco Unified Communications Manager (CUCM) • Cisco Unity® Connection (CUC)

• Cisco Unified Provisioning Manager (CUPM) • Cisco UC Virtualization Hypervisor

• Cisco Unified Computing System C220 M3 Rack-mount server.

The following applications can be optionally added to Cisco Business Edition 6000 solution: • Cisco Unified Presence

• Cisco Unified Contact Center Express • Cisco Unified Attendant Consoles

The focus of this lab is the implementation of the BE6K solution. In the lab the participant will have the opportunity to integrate Communications Manager, Unity Connection and IM and Presence using Unified Provisioning Manager 9.0BE.

Lab consists of:

TASK1: Pre-configuration of UC servers TASK2: CUPM Configuration

TASK3: Enterprise License Manager TASK4: Validate Configuration Appendix

(3)

Lab Aids

The BE6K Lab is constructed using the following software versions and hardware configurations: Platform Version ESXi 5.0 Communications Manager 9.0.1 Unity Connection 9.0.1 Presence 9.0.1

Provisioning Manger 9.0BE

Jabber 9.0.5

IP Communicator 8.6.1

Pod Details:

Server / PC Description IP Address Username Password

CUCM Communications Manager 10.110.X.3 admin Cisc0123 CUC Unity Connection 10.110.X.4 admin Cisc0123 IM an P IM and Presence 10.110.X.6 admin Cisc0123 W2K8 Active Directory Server 10.110.X.2 administrator Cisc0123 Workstation 1 Windows 7 10.110.X.7 user1 Cisc0123 Workstation 2 Windows 7 10.110.X.8 user2 Cisc0123 CUPM Unified Provisioning Manger 10.110.X.11 pmadmin Cisc0123

(4)

Connecting to the Lab

To connect to the remote lab you will be using the AnyConnect client. The two sections below show connecting with AnyConnect. The one you follow will be determined by if you have AnyConnect already installed or not.

Connecting with Cisco AnyConnect Pre-Installed

NOTE: This section is for students that already have the Cisco AnyConnect client installed on their PC. If

you are running an older version you will be instructed to upgrade at the time of login. If you don’t have it installed go to the next section to install it.

Connect to the student lab with the following steps:

Step 1: Open your Cisco AnyConnect VPN client

Step 2: Enter uctraining.cisco.com (128.107.89.254) into the Cisco

AnyConnect client

Step 3: Click Connect

Step 4: Enter the credentials given to you by the lab proctor. Step 5: Click OK to login.

Step 6: Click Accept on the connection banner. Step 7: Once connected proceed to Task 1.

NOTE: If you are connected to a corporate network via VPN or behind a restrictive firewall you may not be

able to use the Cisco AnyConnect VPN client. If you are connected to a VPN you may need to drop the VPN connection to gain access to the student lab.

Install and Connect with Cisco AnyConnect SSL VPN Client

NOTE: This section is for students that DO NOT have the Cisco AnyConnect client installed on their PC.

In these next steps you will install the AnyConnect client necessary to connect to the remote lab environment.

Step 1: Using a browser from your computer go to the following address: https://uctraining.cisco.com/be6k

Step 2: Continue through any security warnings.

Step 3: Login with the Username and Password supplied by the Lab Proctor. Step 4: Click Continue on the welcome banner.

Step 5: Click AnyConnect on the left hand side navigation window. Step 6: Click the Start AnyConnect link in the right window pane. Step 7: Click Yes on any and all security warnings.

(6)

NOTE: If you are connected to a corporate network via VPN or behind a restrictive firewall you may not be

able to use the Cisco AnyConnect VPN client. If you are connected to a VPN you may need to drop the VPN connection to gain access to the student lab.

(7)

TASK 1: Pre-‐configuration of UC Servers

For the sake of time all UC apps have been preinstalled. Each app has no configuration. All pre-lab setup is documented in the appendices.

Most of our configuration and set up of Communications Manager, Unity Connection, and Presence will be completed through Provisioning Manager. However, there is some pre-configuration that needs to be accomplished before you use UPM.

All of the UC app configurations will be completed from Workstation 1.

READ BEFORE STARTING LAB: Screen shots used in the lab guide are for reference only. Please configure the lab using the steps listed and not by the screen shots.

Communications Manager Initial Configuration

A thing to note

Now that you are connected to the lab via AnyConnect you will be able to reach all the UC web pages with your own local browser. If you want to start out configuring with your local web browser, you are more than welcome to do so. However, keep in mind that what is shown in the screen shots are from the Windows 7 RDP

session. There are files and bookmarks built into that Windows 7 image to make things easier as you go along so of course those wont be available to you unless you RDP to it. Also not all browser versions work with the admin pages. If you run into any issues with things not working and you are using your own web browser, try RDP’ing to the Windows 7 image built for this lab as a troubleshooting step.

Activate CUCM Services

1.1 On your PC/Mac, open a Remote Desktop Protocol (RDP) client (NOTE: Screen shots in guide use

Windows RDP. Since there are many different RDP clients on Windows and Mac you may not get the exact same screens. Use the screen shots for reference.) Screen resolution for the VM has been set to 1280x800. For the best experience you can connect with full screen or make sure your RDP client connects at 1280x800.

1.2 Connect to the IP address 10.110.X.7 (X=Pod#). 1.3 Once it connects click Use another account.

1.4 Enter acme\user1 for username. NOTE:Make sure you are logging in with the ACME domain user account by putting

acme\user1 as the login name and not just user1. If you use

just user1 as the login name you will logon locally to the PC and not on to the domain.

(8)

1.5 Enter Cisc0123 for the password. 1.6 Click OK.

1.7 Answer Yes to any security warnings.

1.8 Open Firefox and go to https://10.110.X.3/ccmadmin (X=Pod #). You can also use the CUCM bookmark in the Favorites toolbar. NOTE:Keep the Firefox window fully maximized throughout the entire lab for a better UI experience.

1.9 Select Cisco Unified Serviceability from the Navigation drop-down menu and click Go.

1.10 Log in using the following credentials 1.10.1 Username à admin

1.10.2 Password à Cisc0123

1.11 Select Tools à Service Activation from the main menu. 1.12 Check the box next to the following services:

1.12.1 Cisco CallManager (allows call processing)

1.12.2 Cisco CTIManager (used by JTAPI/TAPI apps for device control) 1.12.3 Cisco Tftp

1.12.4 Cisco AXL Web Service (required to perform searches) 1.12.5 Cisco DirSync (required for directory sync)

More information

In any CUCM deployment you only want to activate services that are necessary for your site. In this lab these services are the only ones required for the features this lab is using. At your site you may need more services activated.

1.13 Click Save.

1.14 Click OK on the pop up and wait for the page to refresh.

1.15 Select Cisco Unified CM Administration from the Navigation drop-down menu, and click Go. 1.16 Select System à Server from the main menu.

1.17 Click Find.

1.18 Click the server name link cucm.

1.19 Change server name to its IP address i.e. 10.110.X.3 (X=Pod

#).

1.21 Click OK on the pop up. 1.22 Click Save.

1.23 Select System à LDAP àLDAP System.

1.24 Check the box next to Enable Synchronizing from LDAP Server

Why am I doing this? In any UC application you want to reduce your dependency on DNS. One way to do this is change your server hostname to its IP address in all possible places.

(9)

1.26 Select System à LDAP à LDAP Authentication. 1.27 Configure LDAP Authentication as follows:

1.27.1 Select the Use LDAP Authentication for End Users check box.

1.27.2 LDAP Manager Distinguished Name à

cn=Administrator,cn=Users,dc=acme,dc=com 1.27.3 LDAP password à Cisc0123

1.27.4 Confirm password à Cisc0123

1.27.5 LDAP User Search Base à cn=Users,dc=acme,dc=com

1.27.6 Under LDAP Server Information enter the IP address à 10.110.X.2 (X=Pod #) 1.27.7 Click Save.

1.28 Select System à LDAP à LDAP Directory 1.29 Click Add New.

1.30 Click OK on the next two pop ups.

1.31 Configure the LDAP Directory Information as follows: 1.31.1 LDAP Configuration Name à MSAD

1.31.2 LDAP Manager Distinguished Name à

cn=Administrator,cn=Users,dc=acme,dc=com 1.31.3 LDAP Password à Cisc0123

1.31.4 Confirm Password à Cisc0123 1.31.5 LDAP User Search Base à

cn=Users,dc=acme,dc=com

1.31.6 Scroll down to the LDAP Server Information section. 1.31.7 IP address of the LDAP server à 10.110.X.2 (X=Pod

#).

1.31.8 Click Save.

1.32 Click on Perform Full Sync Now.

1.33 Click OK on the pop up.

1.34 Select User Management à End User 1.35 Click Find.

Helpful Tip There is a text document located on Workstation 1’s desktop called LDAP Path that has the path typed for you. To prevent typo’s you can copy the path from there and paste them in below where applicable.

More Information

For simplicity sake, rather than have you create a separate admin account for LDAP sync, you are using the default Administrator account located on the W2K8 domain controller that has Active Directory installed. In your environment you may not have access to the password to this account. In that case you would create a separate admin account you can control the password to.

(10)

1.36 Observe two users have been imported. NOTE: Sometimes the import takes a few minutes to process. If no users show up, continue on with your configuration and come back and check in a few minutes. If they still don’t show up, check to make sure your configuration is correct.

IM and Presence Initial Configuration

Presence Post-Install Deployment Wizard

Again as with the other apps, IM and Presence has been pre-installed to save time. The install screen shots are listed in the appendix.

When logging into the IM and Presence administration page for the very first time you will be directed to the post installation deployment wizard. This wizard will not be presented to the user in subsequent visits to the IM and Presence Administration page.

Always run the Post Installation Deployment wizard immediately after a fresh installation of IM and Presence, and before you back up or restore your data in the Disaster Recovery System.

1.37 In Firefox browse to https://10.110.X.6/cupadmin (X=Pod #) or use the CUP bookmark on the Favorites toolbar.

1.38 Login with username admin and password Cisc0123 1.39 The Post Install Setup wizard launches. Enter in the

following:

1.39.1 Hostname à cucm

1.39.2 IP Address à 10.110.X.3 (X = Pod #)

1.39.3 Click Next.

1.39.4 AXL User à admin

1.39.5 AXL Password and Confirm Password à Cisc0123 1.39.6 Click Next.

1.39.7 Security Password and Confirm à Cisc0123 1.39.8 Click Next.

1.39.9 Click Confirm. 1.39.10 Click Home.

A thing to note

Above you are using the admin account configured during install of CUCM. You have to use an application user account that has the Standard AXL API Access role. Since the admin account has that role we can use that for the AXL admin. However Cisco standard practice is to create a separate Application user and assign it to a group that just had that role defined. For the sake of time we will use the admin account already defined.

Configure IM and Presence

1.40 From the Navigation menu, choose Cisco Unified IM and Presence Serviceability from the drop

down list and click Go.

1.41 Select Tools à Service Activation 1.42 Click Set to Default at top.

(11)

1.43 Click OK on the pop up. 1.44 Uncheck Cisco SIP Proxy.

1.45 Uncheck Cisco Presence Engine.

1.46 Check the box next to the Cisco AXL Web Service.

1.48 Click OK on the pop up.

1.49 Wait for the page to refresh; this will take some time for all services to start. 1.50 From the main menu select Tools à Control Center – Network Services. 1.51 Scroll down the list of services, toward the bottom of the page and

select the radio button next to Cisco XCP Router.

1.52 Click Stop.

1.53 Click OK to confirm, wait for the screen to refresh.

1.54 From the Navigation menu, select Cisco Unified CM IM and Presence Administration and click Go.

1.55 Select System à Cluster Topology.

1.56 Click on the + sign next to DefaultCUPSubcluster. 1.57 Click on cup.

1.58 Under Node Configuration change the name cup to the IP Address 10.110.X.6 (X = Pod #).

1.59 Click Save

1.60 Click OK on the next two pop ups.

Changing the Domain Name

1.61 Click on Settings in the left hand side

navigation window.

1.62 Replace the default Domain Name (DOMAIN.NOT.SET) with acme.com

IM and Presence Services Start

To complete the configuration of IM and Presence the two services that weren’t started need to be started now. The one that was stopped will be started again when the system is rebooted later. Complete the following steps to start these services.

1.64 From the Navigation menu, choose Cisco Unified IM and Presence Serviceability from the drop

down list and click Go.

1.65 Select Tools à Service Activation. 1.66 Check Cisco SIP Proxy.

1.67 Check Cisco Presence Engine. 1.68 Click Save.

1.69 Click OK on the pop-up. A thing to note

The Cisco SIP Proxy, Cisco Presence Engine, and the Cisco XCP Router services must be turned off to be able to edit the domain name in the next section of this lab. These services will be turned on again after these setting are edited.

(12)

1.70 Wait for the page to refresh.

1.71 Minimize Firefox to return to Workstation 1’s desktop. 1.72 Double click the putty icon on the desktop.

1.73 Click Run.

1.74 Type the IP address of the cups server in the Host Name box 10.110.X.6 (X=Pod #)

1.75 Click Open.

1.76 Click Yes on the security alert.

1.77 Login to the CUP CLI console using the username admin and password Cisc0123 (Case Sensitive). 1.78 Reboot the CUP server by issuing the following command utils system restart

Note: DO NOT stop this server or all configurations will be lost. 1.79 Type yes, press Enter to confirm the restart.

1.80 Close the putty window.

Unity Connection Initial Configuration

Again as with the other apps, Unity Connection has been pre-installed to save time. The install screen shots are listed in the appendix.

There isn’t much to configure in Unity Connection that UPM doesn’t configure for you. In these next few steps in Unity Connection we are concerned with making sure Jabber can connect to Voicemail, setting pin requirements, and disabling self-enrollment.

1.81 Bring Firefox back up and browse to https://10.110.X.4/cuadmin (X=Pod #) or use the UC bookmark on the Favorites toolbar.

1.82 Login with username admin and password Cisc0123

NOTE: You may see one of two password warnings as seen below. If you do see the first one below, click

the link Click here to continue to login and change your password later to finish logging in. If you see the second warning below just put Cisc0123 in both the Password and Confirm Password boxes and click Save.

NOTE: Ignore the license warnings. You will fix that later in the lab.

1.83 On the left pane, near the top, under Class of Service select Class of Service.

1.84 In the right window pane, click the Voice Mail User COS link.

1.85 Under Licensed Features check the box next to Allow Users to Access Voice Mail Using an IMAP Client and/or Single Inbox. (This and the next

option allows Jabber to connect to the users voicemail box)

(13)

1.88 In the left pane under Templates select User Templates. 1.89 Choose the voicemailusertemplate link.

1.90 Uncheck Set for Self-enrollment at Next Sign-in.

1.91 Click Save. Wait for the Status Updated User Template.

1.92 In that same window select the Edit à Password Settings menu. 1.93 Uncheck User Must Change at Next Sign-in.

1.95 Change the drop down menu, under Choose Pin, to Web Application.

1.96 Uncheck User Must Change at Next Sign-in. 1.97 Click Save.

1.98 In the left pane under System Settings select Authentication Rules.

1.99 Select the Recommended Voice Mail Authentication Rule

link.

1.100 Change the Minimum Credential Length to 5 and uncheck Check for Trivial Passwords.

That completes the pre-configuration of the UC applications. You will now move to the next task which will use Unified Provisioning Manager to integrate all these apps as well as create users and devices.

Why am I doing

(14)

TASK 2: CUPM configuration

The Cisco Unified Provisioning Manager (CUPM) has already been deployed and preconfigured for you. The steps that were used to bring CUPM to the state it is right now are listed in the appendices. Follow the steps below to integrate CUPM into the lab.

Configure Server Connections

2.1 In Firefox, make sure your window is MAXIMIZED and go to URL http://10.110.X.11 or use the CUPM bookmark in the Favorites menu bar. (Having the browser maximized before connecting to UPM is a MUST, if it is not, you will not be able to complete some of the steps)

2.2 Use the following to log in. 2.2.1 User Name à pmadmin 2.2.2 Password à Cisc0123 2.3 Click Login.

2.4 Select Deployment à Devices from the main menu. 2.5 Close the Getting Started pop up.

2.6 Under Unified Communications Manager configure: 2.6.1 IP address à 10.110.X.3 (X=Pod #) 2.6.2 Account Name à admin

2.6.4 Click Test Access (Should see a successful

message at bottom of browser)

2.7 Under Unity Connection configure:

2.7.1 IP address à 10.110.X.4 (X=Pod #) 2.7.2 Account Name à admin

2.7.4 Click Test Access (Should see a successful message at bottom of browser) 2.7.5 Voicemail Pilot Number à 2500

2.7.6 Message Waiting Indicator On Extension à 2550 2.7.7 Message Waiting Indicator Off Extension à 2551 2.7.8 Port Range Starting Extension à 2501

(15)

2.8 Scroll down and expand Unified Presence (Optional). 2.9 Under Unified Presence configure:

2.9.1 IP address à 10.110.X.6 (X=Pod #) 2.9.2 Account Name à admin

2.9.4 Click Test Access (Should see a successful message at bottom of browser – SEE NOTE

BELOW)

NOTE: Your test may come back as unsuccessful since you just rebooted the server earlier and it has not completely come back up yet. Give it a few more minutes and try the test again until you get a successful message.

2.10 Expand LDAP (Optional). 2.11 Under LDAP configure:

2.11.1 IP address à 10.110.X.2 (X=Pod #) 2.11.2 Port à 389

2.11.3 Admin Distinguished Name à cn=Administrator,cn=Users,dc=acme,dc=com 2.11.4 Search Base à cn=Users,dc=acme,dc=com

2.11.6 Uncheck box next to Use SSL (If checked).

A thing to note UPM is capable of using SSL but there are extra steps that need to be taken to install SSL. Those have/will not been completed in this lab. You can find those steps from the UPM Quick Start Guide.

2.11.7 Click Test Access (Should see a successful message at bottom of browser)

NOTE: Check back up under the Unity Connection section. Sometimes what was configured

under Voicemail is cleared. If it has cleared you’ll need to go back to reconfigure. Sometimes the LDAP section clears as well. If you select the menu Deployment à Devices again the

(16)

settings should show back up under LDAP. You will still have to reconfigure the voicemail section.

2.12 Click Save

2.13 It will take some time to complete, sometimes up to 10 minutes. Right now UPM

is going out and configuring all the servers. Wait for the “Update is in progress” message to go away. When it has, continue on with the next step. Good time for a break or check out some of the links under the Related Documentation section at the beginning of the guide.

NOTE: If it has truly been over 10 minutes and the “Update is in progress” indicator hasn’t

gone away please let the proctor know. There are some cases where the timeout mechanism doesn’t take effect. The UPM engineers have tried to clear all of those out to fix the issue but some still may need to be addressed. If this has happened to your pod please let the proctor know, UPM will need to be reset on the backend for you to continue on.

Click Go To Site Management.

2.14 Under Site Configuration configure: 2.14.1 Name à PodX (X=Pod #) 2.14.2 Intra-Site Extension Length à 4 2.14.3 Gateway Name à 10.1.1.1

(Non-existent H323 gateway)

2.15 Expand Directory Number Block (Optional).

2.16 Click Add Row.

2.17 In the From box input 4085552001 2.18 In the To Box input 4085552010

2.19 Expand LDAP User Import (Optional). 2.20 Under LDAP User Import configure:

2.20.1 Mode à Authenticate and Synchronize 2.20.2 Update Existing User Details àDo not update 2.20.3 Delete Users à Do not delete

(17)

2.21 Under Additional Filtering chose Simple query. 2.22 Change User ID to IN.

2.23 Put a * in the box.

2.24 Scroll to the bottom and click Save and wait for creation

message.

Configure Usage Profile

2.25 Click Next.

2.26 Click the arrow next to Standard to expand it. 2.27 Configure the Standard Usage Profile as follows:

2.27.1 In the box next to matching type Executive as shown below.

A thing to note

These fields correspond to the configuration in the LDAP directory. For example, in this lab, we are using Microsoft Active Directory. The Title

configured here matches the Job Title configuration under the Organization tab in the LDAP user account.

2.27.2 Under North American Dial Plan keep all boxes checked. (UPM will actually create route

patterns for each of these numbers)

2.27.3 Under Services check: 2.28.3.1 Allow users to

manage their own services (Self-Care)

2.28.3.2 Line 2.28.3.3 Voicemail 2.28.3.4 Presence

2.27.4 Click the orange down arrow.

2.27.5 From the list that pops up in new window scroll to bottom and

select Cisco IP Communicator and CSF.

2.27.6 Close by using the X or clicking away from pop up box.

2.27.7 Put your cursor over the default phones (8945 and 7975) and click

(18)

2.27.8 Observe that the CIPC device is the default phone by having a green checkmark on it. If it

does not have a green checkmark on it, click on CIPC to make it appear. Your screen should look like the screen shot below.

A thing to note

Since this is a remote lab there are no hard phones used. However, in a real deployment there should be. When you configure your users, in a later step, these device types will be the only ones available to choose from. Since we are only using Jabber and CIPC these are the only two that we will choose.

2.28 Scroll down and click on Default Service Settings.

2.29 Take a moment to click on the different tabs to see all the different

options you can configure on a phone in this Usage Profile. For this lab we are only concerned with one option which you will configure in the next steps after you finish browsing the tabs.

2.30 Click on the Line tab.

2.31 Use the drop down for the Voicemail Profile and choose PM_Connection_VoiceMailProfile.

2.33 Click the X at the top right corner of the window to close (not Cancel). 2.34 Click Save again.

2.35 Click Deploy Site.

2.36 Click OK on the pop up message.

Configure Users and Phones

2.37 Once you get green check marks next to the three tasks

click Go To User Management.

2.38 Click the down arrow next to Add User and choose Import User. (NOTE: If you are not seeing a

menu please see note mentioned on step 2.1. Also if you are using an RDP client to connect to workstation 1 and your browser is maximized and you still aren’t seeing the menus try disconnecting from the RDP connection and

before you reconnect to workstation 1 look for options in your client to change the display to 1280 x 800. Once you’ve changed the display settings,

try connecting back again (10.110.X.7))

2.39 Select From LDAP on the pop up.

(19)

2.41 Click Import.

2.42 Click the Refresh Icon (top right corner) until both users have been imported and the Last Update

reads Complete for each user.

Create Jabber softphones

2.43 Select user1 from the list and click Add Phone.

2.44 Configure the Jabber softphone as follows:

2.44.1 Phone Type à Cisco Unified Client Services Framework

2.44.2 Phone Button Template à Standard Client Services Framework 2.44.3 Device Name à USER1JABBER

2.45 Select user2 from the list and click Add Phone. 2.46 Configure the Jabber softphone as follows:

2.46.1 Phone Type à Cisco Unified Client Services Framework

2.46.2 Phone Button Template à Standard Client Services Framework 2.46.3 Device Name à USER2JABBER

2.46.4 Click Save

A thing to note

As you may have noticed you did not create a CIPC device for each user. That is because UPM automatically creates a device from whatever is selected as the default device in the Usage Profile you created earlier. In this case it was CIPC. It also assigns the directory number to that device from what is configured in the LDAP server. For the device name it uses the users username. If it was a hard phone it would use a dummy mac address that you would have to modify later.

2.47 Select user1 and click the down arrow next to the Add Line

button and choose Add Shared Line.

2.48 Configure Line as follows: 2.48.1 Product Type à Line

2.48.2 Selected Phone à Cisco Unified Client Services Framework : USER1JABBER 2.48.3 Line Position à 1 – Available

2.48.4 Directory Number à 2001 2.48.5 Click Submit.

(20)

2.49 Select user2 and click the down arrow next to the Add Line button and choose Add Shared Line. 2.50 Configure Line as follows:

2.50.1 Product Type à Line

2.50.2 Selected Phone à Cisco Unified Client Services Framework : USER2JABBER 2.50.3 Line Position à 1 – Available

2.50.4 Directory Number à 2002 2.50.5 Click Submit.

Since you imported the users via LDAP no PINs have been configured for the user’s voicemail. So they will not be able to log on to their voicemail account. If users were created manually then PINs could be set at time of creation in UPM. Also since UPM imports users into Unity Connection via CUCM AXL, the Web Application password must be used to authenticate voicemail in Jabber. According to the Unity Connection 9 design guide in order to use LDAP authentication for Web Applications the users must be imported into Unity Connection via LDAP directly.

Each user has been given access to the Self-Care portal via the Usage Profile created earlier. They can change their own PIN and password by logging into UPM Self-Care page. You can also set this information for them via the admin page, which is what you will do now.

Just to note, the PIN and Web Application password could have been set in Unity Connection earlier by configuring them in the User Template voicemailusertemplate. When users get imported, that is the default template it uses to get its settings from to configure each user. In this lab, you will be configuring those settings in the Self-Care portal, just so you can get chance to see

how you can use it.

2.51 Select user1 and click Personal Settings. This will open the

Self-Care page in a new tab.

2.52 Click User Settings. 2.53 Click Password.

2.54 Change Password Type drop down to Unity Connection Web.

2.55 Enter Cisc0123 for the Password and Confirm Password. 2.56 Click Save.

2.57 Click PIN.

2.58 Keep Voicemail in the drop down box and enter 12345 for the PIN

and Confirm PIN.

2.60 Close the Self-Care tab in Firefox.

2.61 Select user2 and repeat the previous steps to set the voicemail

pin and web application password for User 2.

Helpful Tip

To check the progress on provisioning tasks you can click on the icon near the top right corner that looks like this . Change the drop down in that

window to All to see all tasks. Also you can use the icon next to that one to refresh the progress as well. . Another way to check on order status for an individual user is to select the user and choose View Order History under the General Information section.

(21)

That completes what needs to be configured on UPM. There are just a few more things to complete before you license and test what has been configured.

2.62 Open the CUCM Administration page again.

Create and modify UC Services

2.63 Select the User Management à User Settings à UC Service menu. 2.64 Click Add New.

2.65 Select MailStore from the drop down list. 2.66 Click Next.

2.67 Configure as follows:

2.67.1 Name à CUC-Mailstore

2.67.2 Host Name/IP Address à 10.110.X.4 (X=Pod#) 2.67.3 Port à 143

2.67.4 Protocol à TCP 2.67.5 Click Save.

Modify the Service Profile created by UPM

2.68 Select the User Management à User Settings à Service Profile menu 2.69 Click Find.

2.70 Select the PM_CUP-Service-Profile link.

2.71 In the MailStore Profile section change the drop down for Primary to CUC-Mailstore.

2.73 Select the User Management à End User menu. 2.74 Click Find.

2.75 Select the user1 link.

2.76 Scroll down to Service Settings.

2.77 Check the box next to Enable User for Unified CM IM and Presence.

2.78 Change the drop down for UC Service Profile to PM_CUP-Service-Profile.

2.80 Click Go next to Related Links. 2.81 Repeat steps 2.76 – 2.80 for user2.

That completes the integration portion of this lab. In the next task you will license the BE6K system.

More Information

With UC 9 there are now UC Services and Service Profiles to assign to users. This is used for IM and Presence to assign Jabber clients. This Service you are creating now is needed to connect Jabber to voicemail. In this version of UPM it does not create this. Since Unity Connection has its own mailstores we point the IP address to Unity Connection. Don’t let the Exchange type throw you off. We aren’t connecting to a Microsoft Exchange server.

(22)

TASK 3: Enterprise License Manager (ELM)

Now that you have the BE6K configured, it needs to be licensed before you test. UC 9 brings a new way to license your products called Enterprise License Manager (ELM). The following steps will show you how to add applications to the server as well as how to license them. Right now all servers are running on a 60 day demo license.

ELM can be running along with CUCM in the same server or can be installed as a separate application. With the BE6K it really doesn’t make sense to run as a separate server since that will take up one of the 5 virtual machines that can be installed on the BE6K.

Adding Products to ELM

3.1 On workstation 1 in Firefox open up a page to ELM by going to http://10.110.X.3/elm-admin (X = Pod #) or by using the ELM bookmark located in the Favorites toolbar.

3.2 Login in using the folloing: 3.2.1 User Name à admin 3.2.2 Password à Cisc0123 3.3 Expand Inventory.

3.4 Select Product Instances.

3.5 Select Add to display the product add dialog box.

3.6 Enter the following information in the Product Add dialog box: 3.6.1 Name àPX-CUCM (X = Pod #)

3.6.2 Product Type à Unified CM

3.6.3 Hostname/IP Address à 10.110.X.3 (X = Pod #) 3.6.4 Username à admin

NOTE: The credentials used to add products is the OS

Administration username and password of the product.

3.6.6 Click Test Connection (a successful connection

should appear)

3.6.7 Click OK on the successful message box. 3.6.8 Click OK to add the product.

3.7 There should now be one entry in the Product Instances list. 3.8 Now let’s add Unity Connection, click Add again.

3.9 Enter the following information in the Product Add dialog box. 3.9.1 Name àPX-CUC (X = Pod #)

3.9.2 Product Type à Unity Connection

3.9.3 Hostname/IP Address à 10.110.X.4 (X = Pod #) 3.9.4 Username à admin

3.9.6 Click Test Connection (a successful connection should appear) 3.9.7 Click OK on the successful message box.

(23)

3.9.8 Click OK to add the product. 3.10 Click Synchronize Now.

3.11 Observe the results in the lower right corner of the browser. Check the Product instances table

under Synchronization Status, you should see Success for both CUCM and CUC.

Generating Capability Requests in ELM

The ELM server will produce an encrypted output with all the information needed to create a license file. This information will be collected and presented to the licenses group at Cisco Systems, in turn this information will be used to generate a license file that will be emailed to the administrator of the UC products.

3.12 Expand License Management, menu option on the left side of the

Enterprise License Manager.

3.13 Click Licenses.

3.14 Click Generate License Request, the License Request windows will pop

up.

A thing to note

When you are licensing a production BE6K, either copy the License Request to clipboard or save the License Request to a file. Either way, maintain this information as it will be required when generating a license. Follow the direction on the License Request pop-up windows to copy or save this information.

(24)

A thing to note

In a production environment you would go to http://cisco.com/go/license to obtain licenses for your UC products.

In this lab we will not actually have Cisco generate licenses files, the license files have already been generated by Cisco for this lab. You will be instructed where to find these files in the next section

Installing a License File in ELM

As stated above the license file has already been generated by Cisco for this lab and is stored on a central server. In this first section you connect to a server to gain access to your pods license file.

3.16 Click the Start button on Workstation 1.

3.17 Input address \\10.110.1.2\share exactly as shown.

3.18 Press Enter on your keyboard.

3.19 Find your pods folder (example Pod 1 = P01) and open it 3.20 Copy the license bin file to Workstations 1 desktop. 3.21 Hit OK on the security warning pop up (if needed).

3.22 While still in the Licenses section, click Install License File.

3.23 Click Browse to browse to the license files you obtained from Cisco. This file will be the one you

copied to your Workstation 1’s desktop.

3.24 Browse to the Desktop folder and double click the license file.

3.25 Click Install. 3.26 Click Close.

(25)

3.27 Your system has now been licensed. If you go back to Communications manager or Unity

Connection, the demo warning message will now be removed.

3.28 Feel free to look around ELM. Take a look at your License Usage under Monitoring. Click each

license to see more info about each license that is installed.

3.29 You can also look at the licenses that are installed by going into the CUCM administration page and

going to System à Licensing à License Usage Report. (NOTE: If licenses don’t show yet click the Update Usage Details button.

Restart Connection Conversation Manager

In our lab, with CUCM, when we reset the pods the license timer resets. With CUC the reset of the pods does not reset the license timer as it does with CUCM. All Unity Connection VMs have hit the 60 day timer. This means UC stopped taking calls. In this section you loaded a valid license, which fixes the license issue. However, in order for UC to start taking calls again the Connection Conversation Manager service has to be reset. The following steps will reset that service. If you have not hit that 60 day license expiration on your system you should not have to reset this service.

3.30 In Firefox open the bookmark (UC) to Unity Connection.

3.31 Change the Navigation dropdown to Cisco Unity Connection Serviceability and click Go. 3.32 Login with username / password à admin / Cisc0123

3.33 Chose the Tools à Service Management menu.

3.34 Under Critical Services, click Stop next to Connection Conversation Manager.

3.35 Click OK on the pop-up.

3.36 Once the page refresh the button you clicked should read Start. Click that Start button to start the

service again.

3.37 Once that service starts you will be able to take calls again.

Now that you have successfully licensed the BE6K system you will move on to the next task, which will validate your configuration.

(26)

TASK 4: Validate Configuration

Now that your system is configured and licensed lets test what has been configured. Right now you should have two users configured and each has a CIPC assigned as well as voicemail and Jabber.

Configuring Jabber

4.1 Open Cisco Jabber on Workstation 1

4.2 The first time you open Jabber you will need to configure a server

type and login server.

4.3 Select Cisco Unified Presence under Server Type.

4.4 Select Use the following server under Login Server and use the

following info.

4.4.1 Server Address à 10.110.X.6 (X = Pod #) 4.4.2 Domain à acme.com

4.5 Login with Username / Password à user1 / Cisc0123. You may also optionally check the box next

to Sign me in when Jabber starts to prevent putting the username and password in every time you open Jabber.

4.6 From the File menu choose Options. 4.7 Click Phone accounts.

4.8 For username/password use user1/Cisc0123 under Phones Services and Voicemail. 4.9 Click Apply.

4.10 Both settings should come back with no errors. 4.11 Click OK.

4.12 Open up Cisco IP Communicator.

4.13 IP Communicator will have started after boot up but it may stuck in Configuring IP state. Unfortunately with using RDP you cannot just close IP Communicator and reopen to get it to register because of the sound

(27)

drivers. You will need to reboot the workstation and reconnect in a minute after it comes back up. That is why you will need to do the following few steps.

4.14 First exit Cisco Jabber to make sure account settings are

saved. Click the File à Exit menu on Jabber.

4.15 Click the Start button and choose Windows Security.

4.16 Down at the bottom right corner click the up arrow.

4.17 Choose Restart. (You may use Force restart if prompted)

While that is rebooting lets configure Workstation 2 now

4.18 Open a RDP connection to Workstation 2 using 10.110.X.8 (X=Pod #) just as you did for

Workstation 1.

4.19 On Workstation 2 login with Domain\Username / Password à acme\user2 / Cisc0123 4.20 Repeat steps 4.1-4.17 on Workstation 2 for User 2 (NOTE: For username use user2 instead of

user1)

4.21 Once you have Workstation 2 restarting open back up a RDP connection to Workstation 1

(10.110.X.7).

4.22 Open up IP Communicator and it should now show as being registered with DN 2001.

NOTE: Sometimes CIPC doesn’t want to start correctly or Windows 7 doesn’t auto login like it is supposed to. In these cases CIPC will not open properly and give audio driver errors. Unfortunately these are the issues you deal with in trying to run CIPC in a virtual machine with virtual audio drivers. Since Jabber is a softphone as well all the testing can and should be done from it. If you really need to see CIPC registered you can try restarting the virtual machine again or check with the proctor to log onto the backend and start CIPC manually. Also if you are running this lab via a Windows PC then you can download and install CIPC locally and register it to your pods CUCM.

4.23 Open Cisco Jabber as well and log in.

4.24 Open a RDP session to Workstation 2 (10.110.X.8) again. Once connected, open IP Communicator

and Jabber.

Validation

4.25 On Workstation 1 in Jabber start typing user in the search box. 4.26 Put your cursor over User 2 and click the +

button.

4.27 Click New group.

4.28 Give the new group a name such as

Coworkers.

4.29 Click Create. 4.30 Click Add.

4.31 Double click on User 2 to initiate a chat

dialog.

4.32 Type a message in the box and send to User 2. Congratulations Jabber works! Let’s test a few more

things out before we move on.

A thing to note

It may seem like an easy task to search for a user in the directory and add them to your contacts but there are things in the background that you need in place before this will work. The computer itself either needs to be added to the domain or a jabber-config.xml file needs to be configured and uploaded to CUCM. More information can be found about this XML file here :

(28)

http://tinyurl.com/jabber-4.33 Change User 2’s status to Away. Observe that it changed on User 1’s Jabber.

In the following steps User 1 is going to leave a voicemail on User 2’s mailbox from workstation 1.

NOTE: The system will use the sound and microphone capabilities in the RDP client you are using. Some

RDP clients on Windows as well as on Mac may not have these capabilities. The Windows 7 RDP client was used for the testing and should work. If it doesn’t check the settings before you connect to the VM to make sure that sound and microphone is being used on your system and not the remote system. If it still doesn’t work, you can also use the Cisco Jabber client from your own PC/Mac. Just configure/reconfigure your client as you did for workstation 1 (user1) in the lab. If you have appropriate download permissions in your CCO account you can download the client using the following links.

http://tinyurl.com/Jabber4Windows http://tinyurl.com/Jabber4Mac

4.34 Let’s test a phone call from Jabber and leave a voicemail for User2. On workstation 1

(or your PC/Mac), click the phone icon in the chat box to initiate a phone call to User 2. Do not answer the call for User 2. You can either let the Forward No Answer timer expire (12 seconds) or click Decline on workstation 2 to send to voicemail.

4.35 Leave a message and then hang up the call.

4.36 After a few seconds observe on Workstation 2 that the MWI light on CIPC

has been illuminated. Also in Jabber you should also see the voicemail show up (Visual Voicemail).

4.37 You can play the message and/or delete it in Jabber. 4.38 The MWI light on CIPC should turn off.

4.39 From the voicemail tab you can click Call voicemail at the bottom of

Jabber to make sure the voicemail pilot has been configured. The same can be accomplished by pressing the messages button on CIPC.

Congratulations on successfully setting up a Cisco BE6K system!!

Thank you for participating in today’s lab. Feel free to test other items on the system if you

desire. Once you are finished you can disconnect from the AnyConnect client.

Please take a moment before you leave and fill out the class survey.

config. Also a quick internet search on jabber-config.xml will give you many pages on the topic.

(29)

Appendices consists of:

Appendix A: Configuring the CIMC Appendix B: VMware Configurations

Appendix C: Communications Manager 9.0 Installation Appendix D: Unity Connection 9.0 Installation

Appendix E: Presence 9.0 Installation Appendix F: Deploy and configure CUPM

Along with this appendix check out this page on the BE6K Wiki site for more information on the initial setup of the BE6K system: http://docwiki.cisco.com/wiki/Implementing_BE_6000_9.0

Appendix A – Configuring the CIMC

A.1 Connect to the server by using the video/mouse/keyboard ports in the back or using the KVM dongle. A.2 Power on the server.

A.3 Press F8 at the BIOS splash screen.

A.4 Once you’ve clicked F8 the screen will update to indicate you’ve pressed F8.

(30)

A.6 Once complete press F10 to save changes. A.7 Press Esc to exit.

(31)

Appendix B –VMware Configurations

In this appendix you will find everything that you will need to do in VMware: Disabling LRO, NIC Teaming (optional), Virtual Machine Creation, Mounting the UC install ISO, and Installing VMware Tools.

Disable LRO

After installing/upgrading the ESXi host to 5.0 and upgrading VMs to VMware Tools 5.0, you may

experience slow TCP performance on VMs running on the 5.0 ESXi host. You can address this situation by disabling Large Receive Offload (LRO) on the ESXi host.

B.1 From within vSphere or vCenter, click on the server ip to

highlight it.

B.2 Select the Configuration tab.

B.3 Select Advanced Settings located in the Software box. B.4 Select Net and scroll down slightly more than half way. B.5 Set the following parameters from 1 to 0:

B.5.1 Net.VmxnetSwLROSL B.5.2 Net.Vmxnet3SwLRO B.5.3 Net.Vmxnet3HwLRO B.5.4 Net.Vmxnet2SwLRO B.5.5 Net.Vmxnet2HwLRO

B.6 Reboot the ESXi host to activate these changes.

NIC Teaming

(32)

B.8 Click Inventory.

B.9 Highlight your server and click the Configuration tab . B.10 Click Networking.

B.11 Click Properties for vSwitch0.

B.12 Click the Network Adapters tab. B.13 Click Add.

B.14 Check the box next to the Unclaimed Adapter vmnic and click Next.

B.15 Ensure both adapters are Active and click Next. B.16 Click Finish.

B.17 Click the Ports tab.

B.18 Ensure vSwitch is highlighted and click Edit. B.19 Click the NIC Teaming tab.

B.20 Change the Load Balancing method to Route based on IP hash.

B.21 Click OK.

B.22 Highlight Management Network and click Edit. B.23 Repeat steps 1.65-1.67.

B.24 Click Close.

B.25 The configuration below is what you will need to have on your connecting Cisco switch. Again if you

have another vendors switch then your configuration may be different. Also note your port numbers and channel-group will probably be different as will.

A thing to note

Contrary to “common knowledge” not all Cisco switches use a load-balancing algorithm of src-dst-ip by default (especially the lower end models). This switch (a c3750 series) used src-mac by default. The command port-channel load-balance

src-dst-ip was required to be configured. Since this is a communal switch and this

command can only be applied globally this step was already done for you.

It is important to note that only one load-balancing algorithm can be applied at a time on the switch. This means that any and all EtherChannels on this switch MUST be configured to support the selected load-balancing algorithm. This means the other ends of those EtherChannels also need to be doing the same algorithm and so on. All switches interconnected via EtherChannels will be required to do the same load-balancing algorithm.

(33)

interface range f1/0/1-2

switchport trunk encapsulation dot1q switchport mode trunk

switchport nonegotiate spanning-tree portfast trunk channel-group 1 mode on

Virtual Machine Creation

B.26 Open the vSphere client. B.27 Input the IP address of ESXi. B.28 Click Login.

B.29 Click Ignore on the Security Warning. B.30 Click OK on the license warning. B.31 Click Inventory.

B.32 From within vSphere, click on the server ip to

highlight it.

B.33 Select File, and click Deploy OVF Template..

B.34 Click Browse, navigate to the location of the OVA template that you downloaded from Cisco. Then

click Open.

B.35 Click Next.

B.36 Review the details and click Next again. B.37 Give the VM a name.

B.38 Click Next.

B.39 Change the drop down to CUCM 1000 user node – C200 (incl BE6K). B.40 Click Next.

B.41 Choose a the Datastore to install the virtual machine to. B.42 Click Next.

B.43 Select Thick Provision Lazy Zeroed. B.44 Click Next.

B.45 Select the NIC and then click Next. B.46 Click Finish to complete deployment.

B.47 Click Close on the successful deployment message.

Mounting the UC application ISO

B.48 Right click on the newly created VM and choose Edit Settings from the menu.

B.49 Select CD/DVD Drive 1 in the Hardware list.

B.50 Click on the Datastore ISO File radio button and click Browse…

B.51 Click datastore1 and click Open.

B.52 Find the ISO of the UC app you are installing, select it, then click OK. B.53 Check the box next to Connect at power on. If you don’t, your CD/DVD

won’t connect and your ISO will not load.

B.54 Click OK.

B.55 Right click on your VM and choose Power à Power On. B.56 Click on the Launch Virtual Machine Console button.

(34)

Installing VMWare Tools

Once you have completed the UC app installation using the screenshots below you will need to install VMware tools. The steps below are for UC apps 8.6 and later. Method 1 is for CUCM and CUC. Method 2 is for CCX and Presence. If you have a previous version you can browse to this link for more instructions.

http://docwiki.cisco.com/wiki/VMware_Tools Method 1

B.58 From within vSphere or vCenter, right click on the virtual machine and choose Guest > Install/Upgrade VMware Tools.

B.59 Choose the Automatic Tools Upgrade and press OK.

B.60 The process will take a few minutes. The task should then be

complete and the tools should be shown as OK. No reboot is required.

Method 2

B.61 From within vSphere or vCenter, right click on the virtual machine and choose Guest > Install/Upgrade VMware Tools.

B.62 Choose Interactive Tools Upgrade on the popup and click OK. B.63 Open a console window to the UC app and login to the command line. B.64 From the admin prompt type utils vmtools upgrade.

(35)

B.65 Choose y to have your system reboot twice to install.

B.66 When the system finishes the VMware Tools status will show as OK.

B.67 After the VMware tools install is complete, you will need to remove the VMware tools tar file from

the virtual CD/DVD drive. .

B.68 Right click on the VM and choose Edit Settings. B.69 Highlight the CD/DVD Drive.

B.70 Choose Client Device. B.71 Click OK.

(36)

Appendix C – CUCM 9.0 Installation

For the sake of time all of the UC applications were preinstalled. The following appendices will walk through the installation screens. Since most of the installation is exactly the same in each UC application the entire CUCM installation is covered. Then each app after it will only list the screenshots that are different from the CUCM installation.

C.1 Boot virtual machine from CUCM ISO

C.2 At the onset the system will request to do a Media Check. In the lab environment this is not

necessary. Select No to proceed.

C.3 Keep CUCM selected and tab to select OK in the Product Deployment Selection screen

C.4 Select Yes to proceed with the install

C.5 The system will now prompt with the platform installation wizard screen. Select Proceed and press

Enter

C.6 The system gives the opportunity to apply a patch as part of the upgrade. As this system does not

(37)

C.7 This is a basic install and as such will not use any imported data. Please press Enter to Continue

C.8 Select the appropriate Time Zone

C.9 Select Continue for auto negotiation of the Ethernet NIC

C.10 Select No to changing the default MTU size

(38)

C.12 Enter your Hostname and IP information

C.13 Select No for DNS Client

C.14 Enter the Administrator Login info

C.15 Enter the Certificate information

(39)

C.17 Enter a valid NTP server IP

C.18 Enter the Security Password

C.19 Select No to not configure SMTP

C.20 Configure the Application Username and Password

(40)

(41)

Appendix D – Unity Connection 9.0 Installation

All screens are the same as CUCM except for the Product selection screen which is shown below

(42)

Appendix E – Presence 9.0 Installation

All screens are the same as CUCM except for the Product selection screen which is shown below.

(43)

Appendix F – Deploy and configure CUPM

When you purchase a BE6K, CUPM come preinstalled inside an OVA and placed on the datastore of your UCS server. To get it up and accessible you’ll need to deploy it and configure it with the relevant IP addresses specific to your environment using the setup script. After it is accessible you’ll need to connect and configure the UC servers as shown in the lab guide above. The following steps will show you how to get your CUPM up and running to start adding users.

Deploy CUPM OVA

F.1 Connect to the ESXi server that will be hosting the CUPM server using the vSphere client.

F.2 You cannot deploy an OVA file from the datastore location so before you go through these steps you

must first browse the datastore of you server and download it to your computers desktop. After that you then can move on with the following steps.

F.3 Select File, and click Deploy OVF Template.

F.4 Click Browse, and navigate to the place where the CUPM OVA file resides. F.5 Click Next.

F.6 Review the details and then click Next. F.7 Give the VM a name and then click Next. F.8 Click Next.

F.9 Choose a Datastore and click Next.

F.10 Keep Thick provisioning checked and click Next. F.11 Click Finish.

F.12 Click Close on Completed Successfully pop up.

F.13 Right Click on the newly created VM and choose Edit Settings. F.14 Select Network adapter 1 and then select Manual.

F.15 Change the MAC Address to 00:50:56:11:11:11.

F.16 Click OK.

F.17 Right click on the VM and choose Power > Power On.

Configuring the Provisioning Manger VM

VM After you deploy the OVA, you must configure the Provisioning Manger VM for communications with other systems. You are prompted for the following account passwords when you configure Provisioning Manger:

- Linux server admin

- Provisioning Manager pmadmin - PostgresSQL admin

- Root

F.18 Select the CUPM VM and the click the Console tab A thing to note

- The server, PosgreSQL, and root passwords cannot be recovered. It is

recommended that you keep a record of these passwords for future reference. - Because pmadmin is the preconfigured Provisioning Manager username, do not use pmadmin as the administrative password

(44)

F.19 Click inside the window and type setup at the localhost login: prompt. F.20 Enter the following information as prompted

a. Hostname b. IP address c. Subnet mask d. Default gateway e. DNS domain

f. Primary name server

g. Secondary name server (if Y was pressed) h. Primary NTP server

i. Secondary NTP server (if Y was pressed)

j. Timezone (recommend to leave default, can change later. You can find a list of time zone formats here http://en.wikipedia.org/wiki/List_of_tz_database_time_zones )

k. Username for Linux server at shell prompt (suggested to keep default admin) l. Create password for Linux server

m. Reenter password

F.21 CUPM will now initialize the configuration entered.

F.22 You will be prompted to enter the following information

a. Create pmadmin password (used to login to web interface) b. Reenter pmadmin password

(45)

d. Reenter postgres password e. Create root password f. Reenter root password

BE6K Lab Guide 9

Cisco Unified Communications Manager

Business Edition 6000 (BE6K) UC 9

Lab Guide

Cisco Unified Communications Manager Business Edition 6000

Lab Aids

Related Documentation

Connecting to the Lab

TASK 1: Pre-­‐configuration of UC Servers

Communications Manager Initial Configuration

IM and Presence Initial Configuration

Unity Connection Initial Configuration

TASK 2: CUPM configuration

TASK 3: Enterprise License Manager (ELM)

TASK 4: Validate Configuration

Congratulations on successfully setting up a Cisco BE6K system!!

Thank you for participating in today’s lab. Feel free to test other items on the system if you

desire. Once you are finished you can disconnect from the AnyConnect client.

Please take a moment before you leave and fill out the class survey.

Appendix A – Configuring the CIMC

Appendix B –VMware Configurations

Appendix C – CUCM 9.0 Installation

Appendix D – Unity Connection 9.0 Installation

Appendix E – Presence 9.0 Installation

Appendix F – Deploy and configure CUPM

TASK 1: Pre-‐configuration of UC Servers