Академический Документы
Профессиональный Документы
Культура Документы
Contents
WELCOME TO THE CISCO UC INTEGRATION(TM) FOR MICROSOFT OFFICE COMMUNICATOR LAB. .........2
LAB INFORMATION ............................................................................................................................4
ACTIVE DIRECTORY ............................................................................................................................7
OCS ADDRESS BOOK......................................................................................................................... 15
UC MANAGER .................................................................................................................................. 18
GROUP POLICY................................................................................................................................. 32
INSTALL ........................................................................................................................................... 47
DEMO .............................................................................................................................................. 54
*Please note that the contents of this lab guide have been divided into 8 lab sections. At any
time you may refer to the footer on each page to know which lab you are currently in.
Page 1 of 71 Lab 01
CUCIMOC Lab Guide
Welcome to the Cisco UC Integration(TM) for Microsoft Office
Communicator Lab.
In this lab you will learn how to deploy the new Cisco UC Integration for MOC. The l a b session will
last approximately 4 hours.
This lab session complements the presentation session delivered earlier by the proctor.
We have created a server environment (see topology diagram in Lab 2), including:
LabOps will not be used for this lab session. Alternatively, participants will RDP into their allotted host
machine and logon to their respective workstations. They will then RDP from their workstation to the
respective servers.
Each student will be assigned one server environment [POD]. Instructions will be provided prior to
start of lab session.
a. Launch Remote Desktop C o n n e c t i o n by clicking on Start-> All Programs -> Accessories ->
Remote Desktop Connection or alternatively press “Windows” + “R” and type “mstsc.exe”.
b. Prior to starting, an option on the local resources tab of the Remote Desktop Program
must be set in order for calls to be placed within the lab
Page 2 of 71 Lab 01
CUCIMOC Lab Guide
c. The options available for the RDP session should be configured as the following 2 figures on the
DISPLAY and EXPERIENCE tabs for conserving resources.
d. Use "your" assigned Pod's IP addresses to access Workstations 1 & 2 (either as according to
assignment) from within VMWARE.
e. A POD number will be assigned to you at the end of this presentation. Please make sure you
ONLY USE YOUR assigned POD's IP addresses, or otherwise, you will be accessing another
student's POD.
Page 3 of 71 Lab 01
CUCIMOC Lab Guide
LAB INFORMATION
User Information
Server Information
Access to ADX1, OCS are via RDP from XP1 or XP2 respectively
Access CUCMBE7 via HTTP from XP1 or XP2 respectively
Page 4 of 71 Lab 02
CUCIMOC Lab Guide
LAB ARCHITECTURE
Note that in our lab setup the Exchange Server will be running on the Domain
Controller (ADX1)
Page 5 of 71 Lab 02
CUCIMOC Lab Guide
Ensure that 3CDaemon is running on ADX1 if it is not started up (required for further
labs)
Page 6 of 71 Lab 02
CUCIMOC Lab Guide
ACTIVE DIRECTORY
In this module you will be working on the Active directory server. You will be updating user
accounts in Active directory, enabling users as OCS users in Active Directory and adding photo
information to users’ accounts.
From the user workstation, use the Remote Desktop "AD Server" icon to access the Active
Directory server and login with the above credentials
In this step you will add telephone numbers, Job title and company information to
Active directory.
Your first task is to add telephone numbers to your AD users. You will be adding
a main (business) number, home and mobile telephone number. AD is the
source of telephone numbers for OCS, MOC and CUCIMOC. The telephone
numbers displayed by both MOC and CUCIMOC come from AD.
Once a day OCS will scan AD and extract user and telephone information and
create the OCS address book file which is downloaded by MOC clients. By
default OCS expects these numbers to be in E.164 format and will reject any that
are not in this format.
When you select a Contact in MOC the telephone number will be passed to
Page 7 of 71 Lab 03
CUCIMOC Lab Guide
CUCIMOC and used to call the contact via UC Manager.
No, CUCIMOC will also use LDAP directly to search for contact information.
When you display the CUCIMOC contact card the full name and organization
information is displayed from an LDAP search of AD. For incoming calls the
number to name lookup is performed using an LDAP connection to AD.
This is why you will also be populating the Job Title and Company fields in Active
Directory.
Page 8 of 71 Lab 03
CUCIMOC Lab Guide
2) You will see that in the "cucimoc-users" organizational unit, 3 users have been
created for you. Using the table below, access each of the users in the OU and add
the information.
Bob Banks Solution Architect UC Solutions Inc +14443992001 +1444 8774333 +14442334333
Cathy Chung Data Center Manager UC Solutions Inc +14443992002 +14448774555 +14442334555
3) Update each user with their respective information - Double-click or Right click on
each user to go to Properties, use the following tabs to update the user:
General (Telephone Number - must be the full E.164 number as shown above
with the plus) – Office Number
Telephones (Home and Mobile - full E.164 numbers)
Organization (Title, Company)
Note: You may leave the Active Directory Users and Computers window open for the
next step
Page 9 of 71 Lab 03
CUCIMOC Lab Guide
STEP 2: Enable users for OCS - The next step is to enable users as OCS users
The enable process will create a SIP URI that the users will use to login to MOC, it
will also allocate them to an OCS server which will be their home server.
1) Select all the users - Right click, select "Enable users for Communications Server"
Page 10 of 71 Lab 03
CUCIMOC Lab Guide
2) The Wizard window will pop up, Click Next and Assign to ocs.cucimoc.lab
3) Click Next
Page 11 of 71 Lab 03
CUCIMOC Lab Guide
5) Click Next
Note: You may leave the Active Directory Users and Computers window open for step
below
Page 12 of 71 Lab 03
CUCIMOC Lab Guide
CUCIMOC can display photos in the contact details and conversation window. These
photos are downloaded from a file or web location which is configured in a directory
attribute.
Note: CUCIMOC does not support photos being stored in active directory in the same
way CUPC does.
NOTE: Normally, the scheme would be extended, however, for this lab we are going to
use an existing field in the directory which is acceptable for a demo environment.
2) Go to Active Directory Users and Computers (this window may already be opened from
step 2)
3) Double click cucimoc-users - Double-click or Right-click on each user to go to
Properties, enter the respective URL
aadams http://adx1/staff/aadams.jpg
bbanks http://adx1/staff/bbanks.jpg
cchung http://adx1/staff/cchung.jpg
Page 13 of 71 Lab 03
CUCIMOC Lab Guide
STEP 5: Log-off as Administrator to the Active Directory server to Close this Remote Desktop
session and return to the workstation desktop
Page 14 of 71 Lab 03
CUCIMOC Lab Guide
From the workstation desktop, use the Remote Desktop "OCS Server" icon to access the OCS
server and login with the above credentials
The address book service is responsible for updating the OCS address
book once a day. The default time for this update to occur is
1:30am.When this process runs it will extract telephone numbers from
OCS users from Active directory, normalize the numbers, and create the
OCS address book file and update files. During this process the OCS server
will reject any numbers that do not map to an E.164 format.
The address book services also provide access for clients to the address
book files.
When a MOC client logs into OCS, the location of the address book files is
provided to the client using SIP. The address book files are stored on an
IIS based web server (normally on the OCS server). The location
information provided by the server is an HTTPS URL on the IIS server. The
client will either download the entire address book file or a delta file
(updates only). As this location is secure, it's important that the client
has a valid certificate for access to the address book location.
Once the client has downloaded the file it will create a file called
"GalContacts.db". The MOC client will use this fil e to search for contact
Information.
As we don’t want to wait for the Address Book to update, we are going to
request an additional manual run. This step creates a flag to OCS asking
it to perform a run of the Add ress Book. OCS may take a few minutes o
pick up this request.
Since the OCS Address Book updates only once each day, new users may take
up to 24 hours to appear; therefore, a manual process will be performed.
(You can use the "TAB" key to auto complete the directory names)
Page 16 of 71 Lab 04
CUCIMOC Lab Guide
c. Check the Event Log - Start>Programs>Administrative Tools>Event
Viewer (this could take up to 5 minutes) - go to the next step
(You can come back and check this log later if you wish to get on
with the next step)
d. Click OK to close
STEP 2: Log-off as Administrator to the OCS server to Close this Remote Desktop session and
return to the workstation desktop
Page 17 of 71 Lab 04
CUCIMOC Lab Guide
UC MANAGER
In this module, you will work on the Cisco Unified Communications Manager. You will configure
a Cisco Unified Client Services Framework (CSF) Device type for each user and provide them
with a desk-phone (emulated by a CIPC in our lab) to be controlled by the client. Lastly, you will
create dial and directory rules and apply a "dial rule" COP file.
STEP 1: Start Internet Explorer and access the UC Manager server using http://cm1a
STEP 2: Navigate to the "Cisco Unified OS Administration" web page and login again as
admin"
Page 18 of 71 Lab 05
CUCIMOC Lab Guide
STEP 3: Load the COP file, which will update the UC Manager to support CSF based clients
Unless you're running UC Manager 7.1 you will need to install the Cisco Options
Packages (COP) files in order to get the Client Services Framework device type
recognized. UC Manager 6.1(3) and 7.0 will require the COP file to be applied. We will
be applying 2 COP files to the Communication Manager in total.
Later on in the Lab we will install a second COP file to update dial rules.
The COP files required for UC Manager in this Lab have been loaded onto an FTP server running
on the AD server (10.10.10.100). Typical install time is about 4 minutes.
Page 19 of 71 Lab 05
CUCIMOC Lab Guide
A new page will be displayed which shows all the COP files available on the FTP servers. The
drop down box will give a choice of 2 possible COP files.
NOTE THAT, THE LAB DIFFERS FROM THE ILLUSTRATIONS ON PAGES 3 TO 5. WE ARE NO
LONGER USING THE ALPHA VERSION OF THE COP FILE. YOU ARE NOW PROVIDED WITH THE
LATER FILE, “ciscocm.csf.cop.sgn” INSTEAD!
Page 20 of 71 Lab 05
CUCIMOC Lab Guide
d. File will download
Page 22 of 71 Lab 05
CUCIMOC Lab Guide
STEP 5: Associate phones to Alice and Bob (2 phones should be already auto-registered)
a. Navigate to Cisco Unified CM Administration web page - then, go to Device > Phone and
click Find
b. Confirm each phone is CTI Control enabled - click the Device and scroll to "Allow Control
of Device from CTI"
c. Confirm for each phone, click on the Line 1 DN link and change to the appropriate
directory number, (Alice - 2000, Bob - 2001)
Page 23 of 71 Lab 05
CUCIMOC Lab Guide
a. Go to Call Routing>Directory Number > Find - Select the line for Alice (2000) and set
the Voice Mail Profile to "Default"
b. Click Save
c. Repeat this step for Bob Banks
Page 24 of 71 Lab 05
CUCIMOC Lab Guide
STEP 7: Add CSF Device
a. Go to Device>Phone - Add New - Select "Cisco Unified Client Services Framework "
b. Click Next
c. Create CSF Devices for the two users below
Phone Button Template Standard Client Services Phone Button Template Standard Client Services
Framework Framework
Device Security Profile Client Services Framework - Device Security Profile Client Services Framework -
Standard SIP Non-Secure Standard SIP Non-Secure
SIP Profile: Standard SIP Profile SIP Profile: Standard SIP Profile
You are required to save the above information before you will have the link for updating the information below:
Page 25 of 71 Lab 05
CUCIMOC Lab Guide
STEP 8: Associate users to devices and Set Permissions
Note: Make sure you select the new Cisco Unified Client Services Framework phone
d. Click Save
e. Repeat for Bob Banks
Page 26 of 71 Lab 05
CUCIMOC Lab Guide
STEP 9: Confirm the Conferencing Bridge is enabled
CUCIMOC uses UC Manager conferencing resources for ad-hoc audio conferencing. Your UC
Manager server has a default software based conference bridge running.
d. Click Save
Page 27 of 71 Lab 05
CUCIMOC Lab Guide
STEP 11: Create Dial Rules
In this Lab we have configured E.164 addresses in Active Directory/OCS and we are using
a private dial plan in Communications Manager.
We also need to think about reverse number look-up. In order to map a number to be
used for incoming calls, we need to map 23333 back to +14442223333.
To perform the mappings, we are going to use Application Dial rules and Directory look-
up rules configured on UC Manager.
We are creating a very simple pair of rules for this lab, however, you would need to
create more rules for customer deployments based on the size, dial plan, and
distributed nature of your customer deployment.
Page 28 of 71 Lab 05
CUCIMOC Lab Guide
STEP 12: Create Directory Rules
Directory Lookup Rules are used to translate numbers received in UC Manager inbound
calls to a number that can be resolved in LDAP.
UC Manager 6.X and 7.X does not natively provide support for CSF based dial rules. This
second COP file we are going to install is not an updated file, but is a dial rule wizard.
The wizard in the COP file will extract the dial rules from the UC Manager database and
create an XML file in the UC Manager TFTP directory. This wizard will need to be run
every time you make any changes to any rules.
This COP files needs to be run on EVERY server running the TFTP service on a multi
server cluster.
Page 29 of 71 Lab 05
CUCIMOC Lab Guide
The TFTP server services files from a memory cache to the TFTP service needs to be
restarted to get the service to cache the new XML files after each run of the wizard.
a. Navigate to the "Cisco Unified OS Administration" web page and login again as
administrator (admin / C1sco123)
b. Select Software Upgrades> Install/Upgrades
c. Enter the information as shown below
Page 30 of 71 Lab 05
CUCIMOC Lab Guide
STEP 14: Restart TFTP Service
Page 31 of 71 Lab 05
CUCIMOC Lab Guide
GROUP POLICY
In this module you will work on the Active Directory server. You will be creating the
configuration for CUCIMOC. This configuration information has details of UC Manager
Services, Domain information and LDAP information. You will create a new Group Policy for
the Cisco Unified Client Services Framework (CSF) client and modify the setting for Microsoft
Office Communicator to only provide Instant Messaging and Presence.
From the workstation desktop, use the Remote Desktop icon "AD Server" to access the
Active Directory server and login with the above credentials.
CUCIMOC will retrieve it's configuration from the Windows registry settings. This
information can be populated in several ways with examples being, a simple batch file or
visual basic script file. These files can be configured as part of a domain login script.
Another way of providing this information to the client workstations is using AD group
polices, this is the distribution method we have chosen for the lab. This allows us to
configure multiple clients from the AD policy. We could have also used a 3rd party
deployment tool such as SMS or Altris.
A Group Policy is applied to an organizational unit (OU) in Active Directory. You may
remember that when we were working with our users, they were contained in an OU
called "CUCIMOC-users". We created an OU so that we could apply a group policy to
the group. The "users" folder in AD is NOT an OU but a container, so it would not have
been possible to create a policy.
Page 32 of 71 Lab 06
CUCIMOC Lab Guide
A Group policy can be applied to Users or Machines. If the policy is applied to a
machine all users on that machine will inherit the policy, if we apply the policy to users,
only users in the group would inherit the policy.
For example, we could create a policy which sets the wallpaper for all members of a
group, or stops access to control panel for all members of a group.
Microsoft has created group policies so that they can be extended. You can use an
application template file (ADM files) to add addition policy settings to a policy.
For example, Microsoft provides ADM files for Microsoft Office, Word, Excel, and
Communicator.
You can import ADM files into a policy to provide a template. You must then select
which policies you want to enable. If you don't enable a policy, the default setting is
used (if a default setting exists).
For CUCIMOC, we are going to use the CUCIMOC.ADM file, available for administrators
to use for CUCIMOC deployments. Note: This is not the first UCBU application to provide
group policy support. The Cisco UC “Click to Call” widget also provides an ADM file
which can be used to easily configure hundreds and thousands of work stations.
A policy gets applied when a workstation is logged into a domain. The policy will also
get refreshed every 90 minutes by default.
You can check the status of the workstation policy using the "gpresult" command and
you can update the policy using the "gpupdate" command.
You will import 2 ADM files, One for Microsoft Office Communicator and one for Cisco
UC integration for MOC. You will then enable settings for each application.
Page 33 of 71 Lab 06
CUCIMOC Lab Guide
Page 34 of 71 Lab 06
CUCIMOC Lab Guide
f. Select the "Group Policy" tab and click "New" to create a new Policy called
"CUCIMOC Configuration"
g. Click Apply
Page 35 of 71 Lab 06
CUCIMOC Lab Guide
b. Select "Administrative Templates" under "User configuration", Right Click and
Select "Add/Remove templates"
c. Select Add
Page 36 of 71 Lab 06
CUCIMOC Lab Guide
You are now going to configure 3 Policy Items for Microsoft Office Communicator. These
Policy Items are:
Specify transport and server These parameters will provide MOC with the OCS server host
information.
Disable A/V Conferencing The setting is used to disable voice on multi party MOC sessions.
Again, as CUCIMOC is providing the voice, we don't need to use
OCS voice.
a. In the Group Policy Object Editor, expand the "Microsoft Office Communicator
Policy Setting" branch and Double-click the Microsoft Office Communicator
Feature Policies folder
Page 37 of 71 Lab 06
CUCIMOC Lab Guide
Policy Enabled
Internal Server ocs.cucimoc.lab
External Server ocs.cucimoc.lab
Transport TLS
c. Click Apply
Page 38 of 71 Lab 06
CUCIMOC Lab Guide
d. Double-Click “Telephony Mode” to Enable “IM and Presence Only”
e. Click Apply
f. Configure the A/V Conferencing policy to Enable (this will “disable” the
feature)
Page 39 of 71 Lab 06
CUCIMOC Lab Guide
STEP 4: CUCIMOC Parameters
Page 40 of 71 Lab 06
CUCIMOC Lab Guide
Why did I do that step?
The CUCIMOC parameters are not stored in the user "policies" registry key on the
workstation. They exist in the "Client services Framework" Key. The group policy editor
therefore needs to be configured to show ALL registry keys.
The attribute values depicted in this next set of steps need to be propagated to each
machine running CUCIMOC. If you think about deploying CUCIMOC out to 10,000 users,
just remember, although this may seem tedious to some, you only do it once. After
that, when the user logs in to the domain, this information will be applied to that
machine.
The alternative would be to configure the same information in a batch file and in some
manner, get that batch run on each machine. If there are changes to be made, the batch
file must be re-run. As with the Group Policy, it will run every 90 minutes.
*Example: Self-extracting executable and batch file (partial file, not all information is
shown)
In the Group Policy Object Editor, under User Configurations, Administrative Templates,
Cisco Unified Communications Integrations for Microsoft Office Communicator, there
should be 5 folders:
Page 41 of 71 Lab 06
CUCIMOC Lab Guide
TFTP Servers
CTI Servers
CCMCIP Servers
Voicemail
LDAP Settings
a. Enable and set the following policies - in each of the 5 new folders are registry variables
(attributes) that need to be set to the following values
Attribute Value
TftpServer1: 10.10.10.110
CTI Server1: 10.10.10.110
CCMCIP Server1: 10.10.10.110
Voicemail: 2110
LDAP_Server_1: ldap://10.10.10.100:389
LDAP_SearchBaseDN_1 OU=cucimoc-users, DC=cucimoc,DC=lab
LDAP_UserLogonDomain: cucimoc.lab
Where a property is not specified, there is no need to enabled the policy property
b. Open the policy folder, highlight the registry object, right click to go to properties, check
Enable and modify the attribute
Page 42 of 71 Lab 06
CUCIMOC Lab Guide
The CUCIMOC ADM file default values should match the list below:
Attribute Value
LDAP_MaxCacheSize: 1000
LDAP_ResultSetMaxSize: 250
LDAP_AttributeName_objectclassKey: objectclass
LDAP_AttributeName_objectclassValue: person
LDAP_AttributeName_userLogonName: userPrincipalName
LDAP_AttributeName_displayName: displayName
LDAP_AttributeName_commonName: cn
LDAP_AttributeName_firstName: givenName
LDAP_AttributeName_lastName: sn
LDAP_AttributeName_email: mail
LDAP_AttributeName_uri: msRTCSIP-PrimaryUserAddress
LDAP_AttributeName_businessPhone: telephoneNumber
LDAP_AttributeName_homePhone: homePhone
LDAP_AttributeName_mobilePhone: mobile
LDAP_AttributeName_otherPhone: otherTelephone
LDAP_AttributeName_title title
LDAP_AttributeName_companyName company
LDAP_AttributeName_userAccountName sAMAccountName
Page 43 of 71 Lab 06
CUCIMOC Lab Guide
For the LDAP Photo attribute Property settings, we will use a custom value for the Photo field to
utilize the Staff Photo web site being used for the lab
LDAP_AttributeName_photoUri: wWWHomePage
f. Click OK
g. Log off as Administrator to the Active Directory server to close this remote desktop
session and return to the workstation desktop
a. Logout of the desktop on Workstation 1 as aadams and then log back in as aadams - this
is to confirm the group policies have been applied
Page 44 of 71 Lab 06
CUCIMOC Lab Guide
Alternatively, you can validate the registry settings by using the regedit command:
Page 45 of 71 Lab 06
CUCIMOC Lab Guide
Page 46 of 71 Lab 06
CUCIMOC Lab Guide
INSTALL
In this module you will first install the Microsoft Office Communicator client, confirm it is
working, and then install the Cisco UC Integration for MOC.
During this module you must be logged into Workstation 1 as Alice Adams and Workstation 2 as
BobBanks. This will require two separate Remote Desktop sessions to be active.
STEP 1: Install the MOC client - files are located in: c:\install\moc
a. Starting from Workstation 1 as Alice Adams, run the two files listed
The patch file is required to bring MOC up to the minimum version that CUCIMOC supports
As you are logged in as Alice Adams to the desktop, MOC should login without prompting you
for a user name and password
Page 47 of 71 Lab 07
CUCIMOC Lab Guide
STEP 3: Confirm that MOC has downloaded the address book correctly from
OCS
Why am I doing this step?
We want to confirm that the OCS address book has been successfully downloaded from
the OCS address book server.
We can do this very simply by searching for a contact. MOCs primary search method is
via the local address book. If the local address book file exists typing characters in the
search box should show a list of users that match the string you typed.
We also want to check that the address book contains the telephone numbers we
entered into AD earlier in the lab.
a. In the search panel, type "a" - this should display "Alice Adams"
b. Select Alice and press "Alt-Enter" - this should display the Contact card with the
Organization details from AD
c. Click the Call icon to confirm you see Alice's contact details
c. Follow the wizard to add Bob Banks and Cathy Chung (Example:
bbanks@cucimoc.lab)
NOTE: An alternative way to complete this step is to search for the contact and then
drag the found contact into the contact list.
STEP 5: Exit from MOC using the icon in the system tray
Page 49 of 71 Lab 07
CUCIMOC Lab Guide
Note: To install the "Cisco UC Integration for MOC" plug-in we must check and ensure Microsoft
Office Communicator (MOC) is shutdown.
If the MOC client is running you will see a MOC Icon ( ) in the system tray.*
a. To close down the MOC client, right click on the Icon and select the "Exit" option
from the menu
Note: To install the CUCIMOC client plug-in, you must have the following applications
shutdown:
Note: The CUCIMOC installer will install plug-in(s) for these applications.
Page 50 of 71 Lab 07
CUCIMOC Lab Guide
Page 51 of 71 Lab 07
CUCIMOC Lab Guide
b. A successful login will bring up the Cisco UC Integration for MOC (in the form of a
tab)
Page 52 of 71 Lab 07
CUCIMOC Lab Guide
a) Click Call
b) A conversation window will appear
Page 53 of 71 Lab 07
CUCIMOC Lab Guide
DEMO
In this module you will learn how to use the client. This section will guide you through the
features of CUCIMOC.
During this module you must be logged into Workstation 1 as Alice Adams and Workstation
2 as Bob Banks. This will require two separate Remote Desktop sessions to be active.
a. Drag and drop: The first step is to make a call from Alice to Bob. Make a call by
selecting the call destination (in this case Bob) and drag the contact to the Call
Page 54 of 71 Lab 08
CUCIMOC Lab Guide
icon on the CUCIMOC communications pane.
c. Select Bob on the contacts and right-click to select the "Place a Call" option to call
Bob
Page 55 of 71 Lab 08
CUCIMOC Lab Guide
Note: Notice the "Call" option is grayed out, this is the native OCS call function which
d. Again, use the hang up icon on the conversation windows to drop the call.
e. Use the dial Pad - click on the dial pad icon ( )and enter a phone number
(2002)
f. As you make calls notice how the presence icon changes to show the call state.
STEP 2: Receive a Call - This will require you to be logged in to both XP1 (as Alice) and XP2 (as
Bob)
Page 56 of 71 Lab 08
CUCIMOC Lab Guide
c. A conversation window appears
STEP 3: In Call Features - viewing the conversation window of the call between Alice and Bob
you will look at the in-call functions
Page 57 of 71 Lab 08
CUCIMOC Lab Guide
Conference With - a contact or a number
Transfer To - a contact (Bob Banks), a number or an Alternate Device (to a pre-
programmed mobile phone stored in Active Directory - not in this lab)
Park Call - park the call (remember the parked number), retrieve the call
Hold Call - place the call on hold, retrieve the call
End Call - hang up
a. Start by making a call to "Bob", during that call, drag Cathy on to the call icon button in
the communications pane
b. You now have two calls in progress and can switch between the two calls by clicking on
them
c. Using the drop down menu in the conversation window, use the conference (with)
feature to merge the calls into a conference call
Page 58 of 71 Lab 08
CUCIMOC Lab Guide
d. You can also create conference this way:
e. Multi-select users
Page 59 of 71 Lab 08
CUCIMOC Lab Guide
STEP 5: Voice Mail Features
CUCIMOC provides access to the voice mail pilot point in communications manager
SoftPhone mode
In SoftPhone mode, the voice mail icon will call the pilot point (number) configured in the
voice mail profile for the CSF device. If no voice mail profile has been configured, the icon
will be grayed out.
In SoftPhone mode, the icon will also show message waiting indication (MWI)
When you are running in desk phone mode, the pilot point (number) comes from the registry
setting you configured earlier. In Desk phone mode, MWI indication is not shown in the client
but is shown on the physical phone.
Additionally, the voice mail pilot point is taken from the CUCIMOC local configuration. (i. e.
the group policy in this case)
Note: There are two places to access Communications History (Received, Placed, and Missed
calls)
a. Client: Click on the Communication History button ( ) to open the history of
Received, Placed and Missed calls per client
Page 60 of 71 Lab 08
CUCIMOC Lab Guide
b. Outlook: You can elect to save Communications History to an Outlook Conversation
folder
Note: The parameter to set this option is described in “STEP 8: Options” further in the lab
b. CUCIMOC is set in DeskPhone mode - In this mode CUCIMOC has control over the Cisco
IP DeskPhone or chosen device
* When changing to DeskPhone mode, if your dial pad is still grayed out, restart the CTI
Manager. This is not a typical step. However, this indication tells us that there is an issue with
the CTI connection.
Page 61 of 71 Lab 08
CUCIMOC Lab Guide
d. From the list of active devices, select the device (if not already) and Click OK
Page 62 of 71 Lab 08
CUCIMOC Lab Guide
STEP 8: Options
Options allows the user to set a few specific features, such as Auto-sign in, Call Forwarding,
and setting communications history to Outlook
b. Personal option include: the ability to forward all calls to another number, Set
"Communications History to be stored in an outlook folder...
For the communication history option to be enabled, the client must have a
valid outlook mail profile which includes a SIP URI.
The SIP URI is added to an AD profile when the user is enabled for OCS. For the
option to be enabled, AD, OCS, Exchange, and Outlook address information must all
be up to date. In a normal Microsoft deployment it may take a few hours for this
synchronization.
In this Lab we have configured your Outlook client to work in Non-Cached mode.
Page 63 of 71 Lab 08
CUCIMOC Lab Guide
T his means outlook is using AD to search for contacts and not a local address book.
In a customer network, users would normally be using Cached mode. In this model,
users would need to wait for synchronization to occur before updates would be
visible.
You are now going to look at how CUCIMOC integrates with Microsoft Outlook. You are going
to work with:
In this first step we are going to save an IM history to outlook using MOC
b. Using the "File", "Save as E-mail" option in MOC, save this email to Outlook
Page 64 of 71 Lab 08
CUCIMOC Lab Guide
Note: MOC also provides an option which allows you to save all IM conversations
automatically to Outlook. This is enabled in the Options, Personal Information manage
settings in MOC.
c. Make a phone call from Alice to Bob so that we can create some voice call history
d. Start Microsoft Outlook which is in the Microsoft Office group on the "Start" menu
Notice the history contains both IM and Voice call history. The Conversation report also
includes hyperlinks which allow you to start another conversation with Bob.
a. Send an email from Bob Banks on XP2 to Alice Adams on XP1. The email can be about
anything you want.
b. From Workstation ,1 open the email from Bob
c. At the top of the email you'll see Bob's contact information with a smart tag (green ball).
If you right-click on this ball the "Personal Menu" will appear
Page 65 of 71 Lab 08
CUCIMOC Lab Guide
d. Select "Additional Actions" and the CUCIMOC call options will appear.
Do not select "Call Bob Banks" as this is the MOC calling options. It is possible to remove
this "Call" option using a Microsoft Office ADM file.
CUCIMOC supports Click to call from Microsoft Internet Explorer and Firefox.
We have created a sample company directory page on your AD server.
Complete this task from either workstation.
a. Place CUCIMOC in DeskPhone (ensure that CIPC has already registered) or SoftPhone
control mode.
b. Open Internet Explorer and go to http://10.10.10.100/staff
c. Move down the page to Cathy Chung. Using the mouse, select the text of Cathy's
phone (2002) and then right click, selecting the call option will initiate a call to 2002
Page 66 of 71 Lab 08
CUCIMOC Lab Guide
d. We have also enabled this page with TEL URI hyper links. This means we have a click to
call enabled a web application.
Click the "CALL" link next to Cathy and the CUCIMOC click to call window will display.
In this step we are going look at the CUCIMOC status information available. (CUCIMOC installs
additional options on the MOC tools menu)
a. From the tools menu select the "Communications Status" menu item, this will display
the current status
Page 67 of 71 Lab 08
CUCIMOC Lab Guide
The visible icons below show the status of a subsystem (LDAP, SoftPhone (SIP), Desk phone
(CTI). The health is shown using traffic light colors (Red, Amber, Green).
c. From the tools menu select the "Connection Status" menu item. This will display the
Page 68 of 71 Lab 08
CUCIMOC Lab Guide
current status.
Connection Status - Shows Call Statistics during a call while in SoftPhone mode (similar to
clicking the "?" twice with Cisco IP Communicator)
b. Check "I have read and agree to the privacy agreement above...", the click "Create
Report"
Page 69 of 71 Lab 08
CUCIMOC Lab Guide
c. A file will be stored on the local machine's desktop for easy access to email to the
company Help Desk or IT department
Note: A File Structure for the Client Services Framework is shown below that contains logs and
other helpful information
Page 70 of 71 Lab 08
CUCIMOC Lab Guide
Remember CUCIMOC is actually just a graphical head running on the Cisco Client Services
Framework so most of the configuration information is stored in the CSF folders.
The Log files are kept in the Logs folder, the main log file is called "core.log"
The TFTP CNF file is downloaded into the Config folder
The config\CUPC folder contains the XML dial rules from the CUCM TFTP Server
The CUCIMOC folder contains logs files for communication between the CUCIMOC and the CSF
and MOC.
CONGRATULATIONS !!
Page 71 of 71 Lab 08