Lab Guide Cucmbe V7: Cisco Unified Communications Manager Business Edition Page 1 of 104
Lab Guide Cucmbe V7: Cisco Unified Communications Manager Business Edition Page 1 of 104
CUCMBE v7
Task 1 - Log into the Remote Lab Machine and initialize the installation
process for CUCMBE
Step 1: Keyboard Alt+R / Click on start Run to execute the run windows as shown below.
CUCMBE v7
IP address
172.19.83.1
We will use a Vmware image to practise the installation of CUCM Business Edition. For the purposes of this
lab the mechanical process of putting the DVD in a physical drive is circumvented through the use of the VM
Ware software. The screens and processes that will be followed in this lab will mirror the Communications
Manager Business Edition DVD installation process.
Step 4: The next screen will bring up the option for installing the Cisco Unified Communication Manager,
Business Edition. Navigate and choose Business Edition (using the space bar to mark this version for the
installation) click OK and press Enter to continue.
Note: Use the up – down keys and the space bar to make selections. Use the tab button to move on to
the OK button.
The screen below is very similar to the screen presented when setting up regular Communications
Manager 7.0. The only difference is that with CUCM Business edition Unity Connection will install
behind the scenes.
Step 8: Select the time zone using . Use the TAB button to move the cursor to OK and press Enter.
Step 10: Select the 100 Megabit and Full duplex options. Select OK.
Step 12: Enter the Host name, IP address, IP mask, and default gateway address based on the information
seen in this screen shot. Select OK and press Enter
Step 20: Enter Application User Information (username student, password C1sco123)
Step 24: Press Ctrl-Alt to bring the focus back to the mouse.
Step 25: Click the red button to stop the VMWare image. Once the image has shut down, close the VMWare
server console window.
Activity Verification
This task is completed when this result is attained:
• Cisco Unified CM Administration Pages can be viewed.
Step 2: Note any differences or additions in the menus from previous versions of the Communications
Manager appliance.
Note: Navigation from Unified CM Administration to Unified Serviceability or to Unity Connection is
done via selecting the module from the drop down list at the top right hand corner and clicking Go.
Activity Verification
This task is complete when this result is attained:
• Reviewed all the menus in Cisco Unified CM Administration Page.
Step 8: Select Tools / Control Center - Feature Services to ensure that the Cisco CallManager service is up
and running. Another way to jump to Control Center – Feature Services is by using the related links
drop down list on the right hand side of the screen and clicking Go.
Step 2: From the System menu, Select Licensing (it’s right at the bottom) License Unit Report and verify
that there are enough units remaining.
Step 2: From the Workstation1, double click on the Cisco IP Communicator icon to launch the application.
Step 4: If requested, step through the Audio Tuning Wizard (keep default settings) to complete the
application launch.
Note: IPC may not register with an extension or with the correct MAC address. Follow these
troubleshooting tips to resolve these issues.
Step 5.1: From the Menu drop down select Preferences
B: Change the IP address of the TFTP server to 172.19.83.1 and remove any references to
a second TFTP server.
Step 9: Similarly, connect via RDP to Workstation 2 (172.19.83.4) and Workstation 3 (172.19.83.5).
Step 10: Once connected, make sure that the IP Communicator is running on all 3 workstations.
Step 11: From the Remote Lab Machine, if not already logged in, login to CUCM Administration.
Step 12: From the Device menu select Phone
Three IP Communicator phones should be listed. (Device names may not be exactly as shown on the next
page.)
Step 14: Verify that phone calls can be made between all of the workstation phones.
Note: This is a new version of IP Communicator. Any issues encountered with the application, such as
not responding, may require quitting the application and re-launching it.
Activity Verification
This task is complete when these results are attained:
• Three workstation phones are registered with Communications Manager.
• Calls can be made between the workstation phones.
Now create a new softkey template "HuntGroupLogout User" based on the "Standard User" softkey template
and add the “Hlog” button to the “On Hook” call state by doing the following:
Step 2: Click on Add New
Step 8: Find and double click on HLog Softkeys Item on the left side. It should “jump” over to the Selected
Softkeys box on the right.
Step 18: From either Workstation 1 or Workstation 2’s phones, call the hunt group at x2000. Verify that
Workstation 3’s phone does not ring as part of the hunt group.
Step 19: From either Workstation 1 or Workstation 2’s phones, call Workstations 3 directly. Verify that this
phone can be called directly even when logged out of the hunt group.
Activity Verification
This task is complete when these results are attained:
• All three phones ring when calling the hunt group.
• Workstation 3 IPC is able to log out of the hunt group and no longer receive hunt group
calls.
Troubleshooting Tips
If the new softkey template does not appear on Workstation 3’s IPC, try exiting the softphone
and launching it again.
Make sure the phone protocol is SCCP. ( SIP phone might not work)
If the template still does not appear on the phone, try disabling Extension Mobility on that
device and resetting it.
Step 3: Select the Phone Type: Cisco 7971 from the drop down list.
Step 10: Select Cisco 7971 Standard SCCP Non-Secure Profile (Scroll down to set this parameter).
Step 13: Change the “Audible Message Waiting Indicator Policy” to “On.”. Scroll down the page to find this
parameter.
Activity Verification
This task is complete when these results are attained:
• The “Audible Message Waiting Indicator Policy” for the added Cisco IP Phone 7971 is set
to on.
• This feature cannot be tested remotely
Before Cisco Communications Manager 6.0, nearly all recording and monitoring solutions required the use of
SPAN and RSPAN to send the audio stream to the monitoring or recording device. Drawbacks of this
approach are that SPAN and RSPAN are complex to configure, often requiring site specific equipment, does
not scale well, typically forces supervisors to listen to monitored and recorded calls through their pc; it also
lacks call admission control or region-based codec negotiation.
Step 5: In the Find and List Partitions page, select the newly created partition to view it.
Step 25: Select from the main menu Call Routing Class of Control Calling Search Space.
Step 26: Click Add New.
Step 27: Call the new Calling Search Space “RecordingCSS”
Step 28: Add the RecordingPart to the RecordingCSS.
Step 40: Set the IP Address of the SIP Trunk as 172.19.83.254. (Scroll down to SIP Information) -
Typically, the instructions provided by the recording device vendor would be used to configure specific
settings for the SIP trunk.
Activity Verification
This task is completed when these results are attained:
• The steps described above are completed.
• The operation of this feature cannot be tested remotely.
Task 13 - Intercom
Intercom allows a user to place a call to a predefined target. The called destination auto-answers the call in
speakerphone mode with mute activated. This sets up a one-way voice path between the initiator and the
destination so that the initiator can deliver a short message.
Create an Intercom Route Partition.
Step 1: Select Call Routing Intercom Intercom Route Partition.
Step 2: Click Add New
Step 3: Configure a new partition called “IntercomPart.”.
Step 10: Configure the Intercom Directory Numbers to range from x8000 to x8010
Step 11: Select the “IntercomPart” as the Route Partition
Step 12: Select the “IntercomCSS” as the Calling Search Space. (Optionally if the Intercom Calling Search
Space in the previous step was not created, use the “IntercomPart_GEN” for the CSS.)
Step 13: Click Save.
Now assign an intercom directory number on the 7971 phone (x1005)
Step 14: From the Phone configuration page select Intercom [1] – Add a new Intercom.
Activity Verification
This task is completed when these results are attained:
• The steps described above are completed.
• The operation of this feature cannot be tested remotely.
Complete these steps to allow all conference participants to add or remove conference participants:
Step 1: Select from the main menu System Service Parameters
Step 2: Select 172.19.83.1
Step 3: Select Cisco CallManager (Active)
Step 8: From Workstation 3, select a party to remove from the conference. It should be possible to remove
conference participants from the conference using both the original conference controller (Workstation 1 IPC)
and another conference participant’s phone (Workstation 3 IPC.)
.
Note: Remember the Workstation 1 IPC was the original conference controller.
Activity Verification
This task is completed when these results are attained:
• The steps described above are completed.
.
• Both the original conference controller’s phone and a phone other than the conference controller is
used to remove parties from a conference.
Step 1: Create a new Partition called “IntPhonesPart” using the steps described earlier for Partition creation
Step 2: Create a new Calling Search Space called “PhoneCSS” using the steps described earlier for Calling
Search Space creation. Add the IntPhonesPart Partition to the Calling Search Space.
Create two Directed Call Park Number/Ranges:
Step 3: Select Call Routing Directed Call Park
Step 4: Click Add New
Step 5: Make one with a range of numbers 700[0-9] and allow these to revert to the original parker; assign a
retrieval prefix of 99
Activity Verification
This task is completed when these results are attained:
• The steps described above are completed.
• The functionality of these features cannot be tested remotely
Task 17 – Create Calling Search Spaces for Devices and Voicemail Usage
The following output shows the result of the Voice Mail Port configuration. Do not close this window.
Continue on with the next part of this exercise.
Step 1: Select ‘Add this Line group to a new or existing Hunt List’.
Step 5: Place a checkmark in the “Make this the Default Voice Mail Pilot for the System” box. If this
message pops up, click OK.
Step 1: From Main Navigation drop down menu, select Cisco Unity Connection Administration
Step 2: Select Go
Step 4: Ensure the License file is installed. If not then select the check box and click on Install Selected.
Step 5: Once installed or if it is already installed, click on the CUCdemo.lic file.
Step 1: From the Top right Main Navigation menu, select Unity Connection Serviceability
Step 2: Select Go
Step 7: Verify that the restart was successful and that the service is running
Step 8: From any of the Workstation IPC’s call the voicemail pilot number created earlier. Unity
Connection’s opening greeting should answer.
Step 5: Scroll down further under Device Information Owner User ID select softphone1.
Step 10: Under Directory Number Settings Voice Mail Profile, select Unity_Connection.
Step 11: Under Call Forward and Call Pickup Settings Voice Mail, place a check box next to:
• Forward Busy Internal and External
• Forward No Answer Internal and External
Or by selecting Users from the Users menu on the left side of the screen. Users softphone1 and softphone2
should be listed.
Step 1: Return to the Main LabOps navigation Page and connect to Workstation 2
Step 2: Login with the same technique used earlier for Workstation 1
Step 3: Double Click on the Cisco IP Communicator Icon
Step 4: Verify that the IP Communicator has an extension number assigned by CUCM
Step 5: Return to the Main navigation Page and connect to Workstation 3
Step 6: Login with the same technique used earlier for Workstation 1
Step 7: Double Click on the Cisco IP Communicator Icon
Step 8: Verify that the IP Communicator has an extension number assigned by CUCM
Step 9: Place calls and leave messages from one IP Communicator to the other login and retrieve messages
to and verify that Unity Connection is correctly configured
Step 1: In the credential policy for the Phone View CTI user, verify that the User Must Change at Next
Login and the Does Not Expire check boxes are both unchecked. Otherwise, Phone View will not work.
From the main Cisco Unified CM Administration Page select User Management Credential Policy Default.
Step 2: Select the Default Credential Policy for the Application User
Step 2: Uncheck the User Must Change at Next Login check box.
Step 3: Click Save.
Step 4: Select User Management Application User from the main menu.
Step 5: On the Find and List Application Users page, click Add New.
On the Application User Configuration page, do the following substeps to create a CTI user account that will
have access to all user phones for Phone View:
Step 6: In the User ID field, enter "PhoneViewUser".
Step 7: In the password field, enter cisco.
Step 9: Associate the user phone devices with the new CTI user.
.
Step 3: Under Phone View Settings, check the Enable Phone View check box.
Step 4: Scroll down to the CTI Phone Access User Name field, enter PhoneViewUser. Note that the user
name is case-sensitive.
Step 1: Log into the voicemail account for the user on Workstation 1
Step 2: Press 5 to access Message Locator
Step 3: Press 2 to find all messages
Step 4: When the list of messages display on the IPC screen, use the following softkeys to learn how Phone
View interacts with Unity Connection.
Key Action
Select Start message playback from the selected message.
Next Go to the next page of messages, if applicable.
Previou Go to the previous page of messages, if applicable.
s
More Displays the Goto and Exit soft keys. This key appears only on phones that display a
maximum of 4 soft keys.
Goto Skip to the message specified.
Phone View displays a screen that allows you to specify the message number by
using the phone keypad. When the number is entered, the message is highlighted.
Exit Exit the Phone View display. This action returns you to the search criteria prompt.
Step 5: As UC plays the message use the following keys to control playback as you listen to the message
Step 6: The following keys can be used after the message is listened.
Step 3: Change the call waiting settings to only accept one call at this extension.
Step 8: Click OK
Step 10: Select Line [3] – Add a new DN from the right pane and move it to the left pane and move it to
under Line [2] – 6050 in internal
Step 21: Click on Save Selected/Changes and go back to the User page
Step 22: Scroll down and select 6055 as the Primary Extension for this Directory Number Association.
Step 1: Select Back to Find/List from Related Links and click Go.
Step 2: Select the ac user.
Step 3: Scroll down to Permissions Information and click on Add to User Group.
Step 4: Scroll down and select the Standard CTI Allow Control of All Devices, Standard CTI Enabled and
Standard CTI Call Park and Monitoring groups.
After you enable the super provider feature, you do not have to associate pilot points and attendant phones to
the Cisco Unified Communications Manager Attendant Console user.
Step 1: Select from the main menu Call Routing Directory Number
Step 2: Click Add New
Step 3: Enter in 6000 as the DN
Step 11: Enter the directory number 6000 and click tab. The remaining fields will auto fill with the previous
configured settings for this DN.
Step 12: Click Save.
Step 1: Return to the Attendant Console pilot point created above. Application Cisco Unified CM
Attendant Console Pilot Point.
Step 2: Click Add Member in the Hunt Group Member Information area.
Step 4: Click the Communications Manager tab. Some of the services are up and some are not activated.
Step 5: Look and see if the right services are activated or not.
Step 6: Highlight a service and right click on it. Access Control Center directly from RTMT.
Step 3: Right click on the tab and select New Category, name it CUC and add six CUC performance stats to
that window.
Step 4: Toggle between the performance screens that were created to see how the program works.
Step 1: From the User Management drop down menu choose the End User Configuration page.
Before
After
Create a Remote Destination Profile
Step 7: Choose Device Device Settings Remote Destination Profile.
Step 9: In the Remote Destination Profile Information configuration screen, enter the following:
Name: softphone1-rdp
Description: softphone1 remote destination profile
User ID: softphone1
Device Pool: Default
All other fields: Accept Defaults
Step 12: In the Directory Number field enter ‘x’ (which is the 1st line appearance on the softphone1)
Step 13: Leave all other settings as they are.
Step 16: Under the Associated Remote Destinations click the Add a New Remote Destination link.
Step 1: Select System Service Parameters from the main menu. (On systems with multiple CUCM’s this
service can only be activated on the publisher node.)
Step 15: After the CallManager service restarts ensure that the phones register again.
Step 16: Navigate back to CM Administration.
Step 17: Select Media Resources and Mobile Voice Access from the main menu.
Thank you for taking the time to complete this lab. We hope that this was a valuable exercise for you.