CUMA Pre-Installation

Wednesday, April 08, 2009

1:22 PM

Hardware and Software Requirement

Required hardware:
• A proxy server on MCS 7825 H2 or I2
• An Enterprise server on MCS 7845 H2 or I2.
Firewall ports:
should include
• A Proxy Server with both a client and provisioning port
• A Managed server with client, provisioning, and user portal ports
• An Admin server with an admin portal port.
Active Directory Requirements:
• The AD hostname/IP Address
• Lightweight Directory Access Protocol (LDAP) port
• Admin DN
• Admin password
• Searchbase
Exchange Requirements:
• The Exchange hostname, if it is clustered, and an OWA
Bridgehead.
• A WebDAV port
• Exchange Domain
Voicemail:
• Voice-mail system email
CCM Requirements:
• The hostname of the Cisco Unified Communications Manager
running the CTI service. If we have more than one CUCM, specify
all the hostnames as a comma-separated list with no spaces. CTI
services should be running on all the nodes.
• Username and Password - Up to 4 sets of usernames and
passwords for CUCM users.
• Version of the call manager.

Adding a User for AD access

Wednesday, April 08, 2009
2:44 PM

Adding a User for AD access:

• Cisco Unified Mobility Advantage requires an Active Directory
user account to read out user objects. This account needs read-
only access to all LDAP objects and attributes required by Cisco
Unified Mobility Advantage. Default users have read-write
privileges in Active Directory. Read-only configuration can be
done on a per-domain basis in Active Directory. The account
needs read-only access to all user accounts that are part of the
 Cisco Unified Communications solution. The account is used to
authenticate against a Domain Controller for LDAP access to
Active Directory.
• In order to add a new user within Cisco Unified Mobility
Advantage Active Directory, first open Active Directory Users
and Computers.

• Then, click the Add New User icon. Enter all credentials required
of the new user.
• Next, create a password. As this is a service account, the
password should be complex, but set to never expire.
• If necessary, a Group Policy Object (GPO) can be created to
deny this account interactive logon. Note that an Exchange
Mailbox is not required for this account.
• The option exists to set Active Directory users and computers to
show advanced features. To set this option, choose View >
Advanced Features from the drop-down menu.

• To open the Domain Security Settings within the Active

Directory, right-click the domain in the left menu and choose
Properties. Then choose the Security tab in the Properties
window. This tab is visible only with Advanced Features enabled.
The dialog allows you the Access Control List (ACL) of the
different Users and Security Groups to the selected part or parts
below the Active Directory Tree. In this case, the selected part is
the domain. When a user account is created, it will receive
default settings and inherit additional settings for Security
Groups to which it belongs. The Cisco Unified Mobility
Advantage user will now be added to the ACL by clicking Add.
• The Cisco Unified Mobility Advantage user will now be added to
the ACL by clicking Add. Then, enter the name of the user to
add it to the list.
• Still within the Security tab, locate and select the user. Set the
Deny Write permission. Setting the Deny Write permission at the
domain level will propagate this setting to all objects below in
the domain tree.
CUMA Architecture
Wednesday, April 08, 2009
2:47 PM
CUCM 6.x/7.x settings
Wednesday, April 08, 2009
2:50 PM

• First, you will need to navigate to the Cisco Unified CallManager Administration
page
• go to the User Management tab, and select Application User from the drop-down
menu

• From this screen you will be able to either add a set of new users by choosing
Add New or edit existing users by selecting individual user names.
• On the End User Configuration screen, you are able to create device association
for a maximum of 250 devices. From this screen, you can assign the user to
proper groups and assign the right roles.
Corporate Directory Configuration
Wednesday, April 08, 2009
3:12 PM

• The Corporate Directory Server acts as both the repository for corporate contact
information and the authenticating authority for user sessions. This part handles
the preparation for the integration into Microsoft Active Directory.
• Within the Corporate Directory Configuration screen, select and enter the
Corporate Directory Server information. Corporate Directory Type is the type of
corporate directory that is used by your organization; such as Active Directory.
Adapter Name is the name you want to assign to the corporate directory
adapter. This name is for the internal handling only. The third entry, Description,
is the description of the corporate directory adapter. After entering all necessary
information, click Next to proceed with the configuration.

BASIC PARAMETERS:
• First, enter the IP Host Name or IP Address from the Microsoft AD server. Click
Next.

• Then, the distinguished name of the root node needs to be entered in your
Corporate Directory Server. The Cisco Unified Mobility Advantage server makes
an auto discovery for Base Distinguished Name (Base DN). Select one from the
list, or click Edit if yours does not appear. Note that there is only one Base DN
possible, so be sure you will get all objects needed with the Base DN you
selected. Click Next to proceed with the configuration.
• After the Base DN has been entered, the Cisco Unified Mobility Advantage server
shows a default entry in Filter Criteria. The Filter Criteria data will be used to
distinguish corporate users from other corporate resources within the Corporate
Directory Server. In most cases, it is recommended that the default value is
used.
• Follow Referral gives the option of having the Cisco Unified Mobility Enterprise
Server follow referrals from the Corporate Directory Server or not. The default is
True. Polling Period defines how frequently the Cisco Unified Mobility Advantage
Enterprise Server polls the Corporate Directory Server for updates. After
completing all necessary sections, click Next to continue.
• For access to the Microsoft AD, an account needs to be entered. Enter the User
DN of the account that the Cisco Unified Mobility Advantage server uses to read
data from your Corporate Directory Server. This account needs to have read-only
permissions in your Corporate Directory Server. Select the Append Base DN
check box to allow the Cisco Unified Mobility Advantage Enterprise Server to
append the base DN to the user's DN, rather than giving the complete DN of the
user above. The default is checked, which is recommended. Enter the password,
and click Next to proceed with the configuration.
 MAPPING:
• The Mapping configuration screen surrounds the default mapping of the
attribute to the Microsoft AD. In most cases, the defaults should be used.
However, if different attributes are defined in your AD, then these fields need to
be adjusted accordingly. Click Edit to make any necessary changes. After doing
so, click Next to continue.
 EXCHANGE LOOKUP:

• The Exchange Lookup information is used by the Cisco Unified Mobility

Advantage Enterprise Server to auto discover a user's Microsoft Exchange
server. In most cases, the default values should be used. However, if necessary,
click Edit to make any changes. Click Next to finish the configuration for the AD
connection.
Communication Ports
Wednesday, April 08, 2009
3:36 PM

Managed Server Ports:

o User Portal Port
• Port used by the end user to access CUCM user portal
• Default is 8443

o Provisioning port
• Port used for over-the-air downloads of Cisco unified mobile communicator
• Default is 8080

o Naming port
• Internal communication port used by CUMA managed server
• Default is 1199

o RMI port
• Internal communication port used by the CUMA managed server
• Default is 1198
 o RMI object port
• Internal communication port used by the CUMA managed server
• Default is 4444

o Server bind port

• Internal communication port used by the CUMA managed server
• Default is 4445

o Non SSL client port

• Internal communication port used by the CUMA managed server
• Default is 5555

o SSL client port

• Port that client connect to for secure communication
• Default is 5443

o Inter-server SSL client port

• Port used by the CUMA managed server to server-to-server
communication
• Default is 6443

o Managed server SSL client port

• Port that the proxy server connects to for secure client communications.
• Default is 5443

o Managed server provisioning port

• Port that is used for over-the-air downloads of Cisco unified mobile
communicator.
• Default is 8080

Admin Server Ports:

o Admin portal port

• Port used by a system administrator to access the CUMA Admin portal.
• Port is used by the server to obtain configuration information from the
Admin server.
• Default is 7080

• Eg: https://abcd.com:7080/adminportal

• Only http and not https

o Naming port
• Internal communication port used by the CUMA admin server.
• Default is 7099

o RMI port
• Internal communication port used by the CUMA Admin server
 • Default is 7098

o RMI object port

• Internal communication port used by the CUMA Admin server.
• Default is 7444

o Server bind port

• Internal communication port used by the CUMA Admin server.
• Default is 7445

Node Manager Server Ports:

o HTTP port
• Internal communication port used by the Node manager server
• Default is 3080

o Naming port
• Internal communication port used by the CUMA Node manager server
• Default is 3099

o RMI port
• Internal communication port used by the CUMA Node manager server
• Default is 3098

o Server bind port

• Internal communication port used by the CUMA Node manager server
• Default is 3445

Proxy Server Ports:

o Admin server HTTP port

• Port used by a system administrator to access the CUMA Admin portal
• This must be the same as Admin portal port setting.

o Naming port
• Internal communication port used by the CUMA proxy server
• Default is 5099

o RMI port
• Internal communication port used by the CUMA Proxy server
• Default is 5098

o RMI Object port

• Internal communication port used by the CUMA Proxy server
• Default is 5444
 o Server bind port
• Internal communication port used by the CUMA Proxy server
• Default is 5445

o Proxy server client port

• Port that is used to secure client-server communication
• Default is 5443

o Proxy server provisioning port

• Port that is used for over-the-air downloads of Cisco unified Mobile
Communicator
• Default is 8080

Firewall Ports
Wednesday, April 08, 2009
4:09 PM

• The Proxy Server Client Port, with the default value of 5443, and the Proxy
Server Provisioning Port, with the default value of 8080, must be opened in
the external firewall. The Managed Server SSL Client Port, with a default
value of 5443, the Managed Server Provisioning Port, with the default value
of 8080, and the Admin Portal port, with a default value of 7080, must be
opened in the internal firewall.
CUMA Enterprise Server Installation
Wednesday, April 08, 2009
4:15 PM

• Boot from the OS DVD.

• During the installation, the system might reboot up to 3 times( each for Hard
drive, Raid and BIOS..if required).
• You will need to enter the following information in the course of installation:
o DNS ( if available)
o HOSTNAME
o IP ADDRESS
o GATEWAY
 o AUTO NEGOTIATION-use default value
o SPEED-use default value
• When the system displays the Cisco Application DVD page, you will need to
insert the Cisco Unified Mobility Advantage application DVD. Click install and
wait for the Installation Wizard to start. This process may take several minutes.
• When the Installation Wizard begins, review the information on the Important
screen. Click Next and the license agreement screen appears. You will then
review the license information and click I accept the Terms of the License
Agreement. Click Next and the Choose Install Set screen appears. You will
choose Cisco Unified Mobility Advantage as the type of installation, and click
Next.
• the Choose Install Folder screen appears. You will enter or select the location
where the Cisco Unified Mobility Advantage Enterprise Server will reside. The
default installation path is /opt/Cuma. Now you will click Next.
• The Managed Server Instance Name screen appears. You will enter the name
that you want to assign to this instance of the Managed Server, and then click
Next.

• The Managed Server Configuration screen appears now. You will enter the values
for the Managed Server ports. The default values are shown in parentheses. Use
these values or the values you determined during preinstallation tasks. When
you have entered all the information, click Next, and the Admin Portal
Configuration screen appears. You will enter values for the Admin Server ports
and then click Next
• Now the Admin Portal Password screen appears. You will need to enter a
password for logging into the Cisco Unified Mobility Advantage Admin Portal. By
default, the username is admin and cannot be changed. When you click Next,
the Node Manager Server Configuration screen appears. You will enter the
values for the Node Manager Server ports, and then click Next.
• When you are complete, the Preinstallation Summary screen appears. You will
need to review all of the information on the summary screen and make sure all
of it is correct
• The Cisco Unified Mobility Advantage Enterprise Server will install now. When
this process is finished, the Install Complete screen appears. You will click Done
and then Reboot to restart the server. After rebooting, the Admin Server and
Node Manager Server start automatically.
• After installing the Cisco Unified Mobility Advantage Enterprise Server, verify
that the Admin server and the Node Manager Server are started, as described
here.
 o Admin Server:
• Step 1: log into the system that is hosting the Admin server.
• Step 2: open a new terminal.
• Step 3: enter this command in the terminal window:
 /sbin/service cuma_admin status
The staus message should rea : "Cuma_admin is running". If there
service is not running you will have to issue the following
command to start the service:
 /sbin/service Cuma_admin start
The admin server starts when the "OK" message appears.
o Node Manager Server:
• Step 1: log into the system that is hosting the Admin server.
• Step 2: open a new terminal.
• Step 3: enter this command in the terminal window:
 /sbin/service cuma_nm status
The staus message should rea : "Cuma_nm is running". If there
service is not running you will have to issue the following
command to start the service:
 /sbin/service Cuma_nm start
The admin server starts when the "OK" message appears.

CUMA Proxy Server Installation

Wednesday, April 08, 2009
6:31 PM

• Basic installation is all the same. Like all bios, raid check etc, network time, root
password etc…
• Before installing the Proxy Server Application, the administrator must first
complete initial configuration of the Cisco Unified Mobility Advantage Enterprise
server and get the necessary certificates.
The procedure for installing the Cisco Unified Mobility Advantage Operating
system on the server that is going to host the Cisco Unified Mobility Advantage
Proxy Server can begin when the system displays the Cisco Application DVD
page. You will need to copy the proxy certificate file to the root directory on the
system using SSH file transfer protocol (SFTP). To copy the certificate file using
SFTP, you will use root as the User and the password you assigned to the
SSL Certificate file.

After copying the certificate file, insert the Cisco Unified Mobility Advantage
application DVD as prompted by the Cisco Application DVD page and click
Install. The Installation Wizard will start.
• When the Installation Wizard begins, review the information on the Important
screen. Click Next and the License Agreement screen appears. Review the
license information and click I accept the Terms of the License Agreement, and
click Next.
• The Choose Install Set screen appears. Choose Cisco Unified Mobility Advantage
Proxy as the type of installation, and click Next.
• The Choose Install Folder screen appears. Enter or select the location where the
Proxy server software will reside, and click Next. The SSL Certificate and
Password screen appears. Click Choose and locate the Proxy Server SSL
Certificate file you copied to the Proxy Server previously. Enter the password
associated with the certificate file, and click Next.
• The Admin Server Information screen appears.
• You will enter the information required for the Proxy server to communicate with
the Admin server. For the Admin Server Host, you will enter the Admin Server
host name or IP address and for the Admin Server Portal Port, you will enter the
Admin Server http port that was specified during the Admin Server installation.
Now click Next. The Proxy Server Configuration screen appears. You will enter
the values for the Proxy Server ports, or click Next to accept the default values.
• The Pre-Installation Summary screen appears.
• Review the information in the summary screen and make sure all of the
information is correct. If all of the information is correct, click Install. If any
changes are required, click Previous and make the changes.
• The Proxy Server installs and when it is complete, the Important Information
screen appears. Click Next and the Proxy server is installed.

• In order to verify that the Proxy Server is started, you will need to follow these
steps.

 Step 1: log into the system that is hosting the Admin server.
 Step 2: open a new terminal.
 Step 3: enter this command in the terminal window:
• /sbin/service cuma_proxy status
The staus message should rea : "Cuma_proxy is running". If there service is
not running you will have to issue the following command to start the
service:
• /sbin/service Cuma_proxy start
The admin server starts when the "OK" message appears.

Deploying CUMA
Wednesday, April 08, 2009
11:56 PM

CUMA Initial Configurations

Thursday, April 09, 2009
8:26 AM

• Log in to the CUMA admin portal by using the following URL:

o http://hostnameORip:7080/adminportal
• The Configuration Wizard prompts you through the steps required to configure
Cisco Unified Mobility Advantage for your system. To run the Configuration
Wizard, click Next on the Welcome screen.

SSL Certificate Management

Thursday, April 09, 2009
12:35 AM

• The SSL Certificate Management screen appears.

• The SSL Certificate Management screens prompt you through the steps required
to create an SSL certificate and is completed in two parts.
• Part One, Create a New Certificate, is completed during the Configuration
Wizard. You must complete Part One for the Proxy Server and again for the
Enterprise Server.
• Part Two, Request the Signed SSL Certificate, is completed after the
Configuration Wizard. You must complete Part Two for the Proxy server.
• If you choose to generate a signed certificate for the Enterprise server, you
must complete Part Two for the Enterprise server as well.

• In order to generate a Certificate Signing Request (CSR) and create a self-signed

certificate, you have two options. If this is a new installation, you can click Yes
and follow the steps for creating a new certificate. You must complete these
steps for the Proxy Server first and again for the Enterprise Server. If you have
already completed the steps for the Proxy Server and again for the Enterprise
Server, click No and follow the steps for uploading the certificate.

• If you clicked Yes on the SSL Certificate Management screen, then the Generate
Certificate Signing Request screen will appear. You will need to enter the
following information for the Proxy server first:
• server name,
• department name,
• company name,
• city,
• state,
• country code, and
• password.
 Click Next

• when the following screen appears, click the link to download the self-signed
certificate.
You will name the certificate proxy.example.selfsigned.keystore for the
Proxy server and example.selfsigned.keystore for the Enterprise server.
• The self-signed certificate downloads to your desktop, so make sure you record
the location of this file because it is required later in the process, when you
import the SSL certificate.

• Now copy the CSR text that is displayed below the download link and paste it
into a text file. Save the file and name it proxy.example.csr for the Proxy
server or example.csr for the Enterprise server, then click Reset at the top
of the page.
• The Configuration Wizard returns to the SSL Certificate Management screen.
Click Yes when prompted to create a new certificate and repeat the same steps
for the Enterprise server. When you complete the steps, the wizard returns to
the SSL Certificate Management screen, prompting you to create a new
certificate. Click No.
• In the Upload Certificate screen, browse and locate the example.self-
signed.keystore file for the Enterprise server,

• enter the password you assigned to the file when it was generated, and then
select the type of certificate file. The default is JavaKeyStore (JKS). You will need
to click Next when you are finished entering all the information.
• The SSL Certificate Management Summary screen will appear stating that you
have successfully uploaded the SSL Certificate. You will need to click Next again.

Enterprise Configuration: Corporate Directory

Thursday, April 09, 2009
12:36 AM
• The Corporate Directory Server acts as both the repository for corporate contact
information and the authenticating authority for user sessions. This part handles
the preparation for the integration into Microsoft Active Directory.
• Within the Corporate Directory Configuration screen, select and enter the
Corporate Directory Server information. Corporate Directory Type is the type of
corporate directory that is used by your organization; such as Active Directory.
Adapter Name is the name you want to assign to the corporate directory
adapter. This name is for the internal handling only. The third entry, Description,
is the description of the corporate directory adapter. After entering all necessary
information, click Next to proceed with the configuration.
 BASIC PARAMETERS:

• First, enter the IP Host Name or IP Address from the Microsoft AD server. Click
Next.
• Then, the distinguished name of the root node needs to be entered in your
Corporate Directory Server. The Cisco Unified Mobility Advantage server makes
an auto discovery for Base Distinguished Name (Base DN). Select one from the
list, or click Edit if yours does not appear. Note that there is only one Base DN
possible, so be sure you will get all objects needed with the Base DN you
selected. Click Next to proceed with the configuration.

• After the Base DN has been entered, the Cisco Unified Mobility Advantage server
shows a default entry in Filter Criteria. The Filter Criteria data will be used to
distinguish corporate users from other corporate resources within the Corporate
Directory Server. In most cases, it is recommended that the default value is
used.
• Follow Referral gives the option of having the Cisco Unified Mobility Enterprise
Server follow referrals from the Corporate Directory Server or not. The default is
True. Polling Period defines how frequently the Cisco Unified Mobility Advantage
Enterprise Server polls the Corporate Directory Server for updates. After
completing all necessary sections, click Next to continue.
• For access to the Microsoft AD, an account needs to be entered. Enter the User
DN of the account that the Cisco Unified Mobility Advantage server uses to read
data from your Corporate Directory Server. This account needs to have read-only
permissions in your Corporate Directory Server. Select the Append Base DN
check box to allow the Cisco Unified Mobility Advantage Enterprise Server to
append the base DN to the user's DN, rather than giving the complete DN of the
user above. The default is checked, which is recommended. Enter the password,
and click Next to proceed with the configuration.
 MAPPING:
• You will review the mapping attribute information, such as distinguished name,
first name, last name, and e-mail. It is recommended that you use the default
settings. Click Edit to make any changes, or click Next to proceed with the
default settings
 EXCHANGE LOOKUP:
• Review the lookup information, including contact adapter, DNS host name,
contact adapter DN mask, and contact adapter search base.

• Now the Corporate Directory Configuration Summary screen appears. Review

the information and click Reset to change any setting. If there are no changes,
then click Next.
Enterprise Configuration: Personal Contact Server
Thursday, April 09, 2009
12:48 AM
• You will need to complete several steps in order to configure the personal
contact server. First, you will enter the personal contact server information,
which includes
o the personal contact server type,
o adapter name, and
o Description
• click Next and you will be prompted to enter the exchange server information.
Next you will enter the port, exchange domain, and user name suffix information
and click Next

• Now you need to enter the voice-mail configuration information. These values
apply to systems that want to integrate Cisco Unified Mobility Advantage with
their voice-mail system.
• Now, you will need to select whether or not you want to enable the voice-mail
server and click Next

• You will choose whether or not you want to integrate Cisco Unified Mobility
Advantage with your corporate conferencing system to provide conference
notifications and viewing capabilities on Cisco Unified Mobile Communicator.
• Now, the Personal Contact Server Configuration Summary screen appears.

• Within the Call Control Configuration screen of the Cisco Unified Mobility
Advantage Admin Portal, there is the option of configuring a Call Control Adapter.
If you so desire, choose Yes, and then click Next.
• The next section of the Call Control Configuration page asks for the Call Control
Server Type, the Adapter Name, and the Description. After accurately completing
those sections, click Next.

• After choosing Next, you are required to enter the CallManager host name or IP
address, as well as a user name and password and CallManager Version. The
 host name should be the Cisco Unified Communications Manager running the
CTI service. You can enter up to four user name and password combinations,
each with up to 250 associated devices. After filling in the required information,
click Next to continue.

• The next section of the Call Control Configuration screen asks for several fields
regarding the dial plan settings of the Cisco Unified Communications Manager.
After completing each section, click Next to continue.
• This section within the Call Control Configuration screen gives the option of
enabling corporate PBX integration. You must also enter the Maximum Expiry of
Call Logs (days). Click Next to continue.

• The final page within the Call Control Configuration section gives an overall
summary of the elements that have just been entered. This includes the Call
Manager Server Configuration section, the Dial Plan Configuration section, as
well as the Call Control Service section. To reconfigure any settings, click Reset.
To move on throughout the Cisco Unified Mobility Advantage Admin Portal, click
Next.
• Within the Enterprise Configuration Summary page, view the configuration
summaries for each server, by clicking its respective host name or IP address.
Click Next to continue with the configuration.
• The System Configuration screen allows you to determine the Cisco Unified
Mobility Advantage Enterprise server domain information and SMTP server
information. The SMTP Server must allow relaying from the Cisco Unified Mobility
Advantage server. The Cisco Unified Mobility Advantage Enterprise server uses
the SMTP server to send out device provisioning and melt€™ messages, which
come as an e-mail for BlackBerry devices, and come as an SMS message for
Symbian devices. In order to determine system configuration information, you
will need to enter some general and SMTP Server configuration data.
• The Server Setup screen allows you to choose to configure the Cisco Unified
Mobility Advantage Proxy Server and enter information about the Managed
Server. To configure the Proxy Server and then the Managed Server, you need to
choose Yes when prompted to configure a Proxy server and click Next.

• On the Proxy Server Configuration screen, you will enter the necessary
information for the Proxy server and click Next.
• Enter the information for the Managed server, including the hostname, non-SSL
client port, SSL client port, and inter-server SSL port, then click Next.

• Review the information on the Server Setup Summary screen and then click
Reset if you need to make changes. If not, then click Next to continue the
installation.
• To upload the Cisco Unified Mobile Communicator onto the Cisco Unified Mobility
Advantage Enterprise server, first browse or enter the location of the Cisco
Unified Mobile Communicator software file and then click Next.

• When the upload is successful, the Handset Platform Management Summary

screen appears, displaying the handset platforms and versions of the Cisco
 Unified Mobile Communicator now installed on your system. If you want to
change the settings, click Reset. Click Next if changes are not necessary.

• The Summary screen displays your Cisco Unified Mobility Advantage Enterprise
Server setting. You are able to review the configuration summary and have the
option of clicking Reset under any area to make changes to that specific area.
To complete the configuration, click Finish.
• When you are prompted to start the Managed server, click Yes.

• After the server is started, the Admin Portal main window appears. After
completing the configuration and starting the Managed server, you will request
a signed SSL certificate from Verisign Corporation. A signed SSL certificate is
required for the Proxy server and recommended, but not required, for the
Enterprise server.
• To request a certificate, you will need to go to the Verisign web site,
www.verisign.com.
• When you request a certificate, you are asked to provide your information.

• Once you have entered that information, you will need to provide a CSR. Use the
text contained in the proxy.example.csr file, or the example.csr file you
created earlier.
• You will need to wait for an e-mail to arrive from Verisign, which may take
anywhere from a few minutes to a few days. This e-mail contains your final
certificate and a link to an intermediate certificate.
• When you receive the e-mail from Verisign, click on the link that downloads the
intermediate certificate. You will see text that says, Begin Certificate, and ends
with, End Certificate. Copy this text, including the begin certificate and end
certificate text, and paste it in a text file. You will name the file
proxy_intermediate_cert.text for the Proxy server or intermediate_cert.txt
for the Enterprise server. At the bottom of the e-mail, locate your Server
Subscriber Certificate, copy the text, and paste it in a text file. Name the file,
proxy_example.final_cert.txt for the Proxy server or example.final_cert.txt
for the Enterprise server.

• To import the signed server subscriber certificate, you will need to log in to the
Admin portal. Choose SSL Certificate Management, then Import Certificate. You
will need to provide the certificate file, password, intermediate certificate, and
certificate information. You will provide the information for either the Proxy
server or Enterprise server, based on which signed certificate you are importing.
Now, download the signed SSL certificate that is generated on your desktop, and
save it in a separate file. You will name the file
proxy.example.ca_signed.keystore for the Proxy server or
example.ca_signed.keystore for the Enterprise server. This is your final
certificate.
• In short, Follow the steps listed here for importing a signed certificate for the
Proxy server and Enterprise server.
Deploying CUMC
Thursday, April 09, 2009
8:27 AM

Admin Control Pane - Menu definitions

Thursday, April 09, 2009
8:28 AM
Install CUMC on a phone
Thursday, April 09, 2009
8:56 AM

• Before a system administrator or an end user can install and provision Cisco
Unified Mobile Communicator on a phone, the system administrator must do
several things.
o First, the end user on the Admin Portal needs to be activated.
o Then, the Cisco Unified Mobile Communicator software needs to be
downloaded.
o For BlackBerry end users, a system administrator must take an additional
step and add the end users to the Enterprise Server.
• End users must be activated on the CUMA Managed Server before they can
install and provision CUMC on their phone.
• Before activating an end user, verify that the end user has an activated e-mail
account on the network.
• Also, ensure that BlackBerry end users have been added to the BlackBerry
Enterprise Server.
Activate/Deactivate End User
Thursday, April 09, 2009
9:10 AM
Capacity
Thursday, April 09, 2009
9:09 AM
• There are 1,000 Cisco Unified Mobile Communicator users per deployment.
• Deployment includes both Cisco Unified Mobility Advantage Proxy and Cisco
Unified Mobility Advantage Enterprise servers.
• For JTAPI call log integration, up to 4 application users are configured within
Cisco Unified Communications Manager, each with 250 associated user desk
phones per deployment.

Adding a Phone
Thursday, April 09, 2009
9:13 AM

• First, within the user portal of the Cisco Unified Mobile Communicator, click the
My Phones icon in the menu on the left. If no phones currently exist, then you
will be prompted to click the Add Phone button to add your phone.
• After successfully adding a new phone to the Cisco Unified Mobile
Communicator, you should now be able to view its properties under My Phones,
with the option to edit, delete, or add an additional phone

Download and Install CUMC

Thursday, April 09, 2009
9:34 AM
Over-the-Air provisioning for symbain
Thursday, April 09, 2009
10:09 AM
Over-the-Air provisioning for Blackberry
Thursday, April 09, 2009
10:38 AM
User Over-the-Air Provisioning for Blackberry
Thursday, April 09, 2009
10:43 AM
Adding Users to the BES
Thursday, April 09, 2009
10:48 AM

Before activating a BlackBerry device user on the Cisco Unified Mobility

Advantage Managed Server, the user must be added on the BES first. In order to
add end users to the BES, it is necessary to follow five steps.

• First, start the BlackBerry Handheld Manager and click Users.

• Then, locate the end user and click on his or her user name.
• Click the Assign Software Configuration task under Device Management.
• From the Select a Software Configuration dialog box, select the configuration to
be associated, and then
• click OK.

Configuring Microsoft Outlook for use with CUMA and

BES initial Details
Thursday, April 09, 2009
10:51 AM

There is a specific procedure that describes how to configure Microsoft Outlook

to ensure that Cisco Unified Mobility Advantage alerts are sent to a user's
BlackBerry device, instead of the user's Junk folder in Outlook.

• Users should continue to check their Junk mailboxes and, if necessary, disable
junk-mail blocking during provisioning.
• End users must be provided with the Admin e-mail address in order to indicate
within Outlook that e-mails from this address are trusted, and are not junk.
• The admin e-mail address can be viewed under System Management > SMTP
Server Configuration.

NOTE:

In order to configure Microsoft Outlook to ensure that Cisco Unified Mobility

Advantage alerts are sent to BlackBerry devices instead of Outlook's junk mail
folder,
• first open the Tools menu in Outlook and select Options.
• Under Options, choose Preferences.
• This will then allow you to click the Junk e-mail button.
• Choose the Safe Senders tab and click Add.
• Enter the Admin e-mail address, which is found in the Admin Portal under
System Management > SMTP Server Configuration, and click OK.
• Finally, click OK again in order to complete the configuration.

Manual provisioning
Thursday, April 09, 2009
10:56 AM

• The first step in manual provisioning of Cisco Unified Mobile Communicator

client for Nokia requires logging into the Cisco Unified Mobility Advantage web
portal to pre-provision the phone.
• Once pre-provisioned, click the information icon to get the phone registration
information that will be needed later on in the provisioning process.
• Next, click the download icon to download the client to the PC.
• You should then install the client application on the phone using the Nokia PC
Suite, bluetooth, or infrared port.
• At application launch, select Yes when prompted to manually provision.
• Enter registration information that was obtained earlier.
• Just as in the SMS message within the over-the-air method of provisioning,
registration should include the Cisco Unified Mobility Advantage proxy
hostname, the user ID, as well as the device ID.
• Finally, once the client connects to the Cisco Unified Mobility Advantage proxy
server using the manually entered information, client provisioning is complete.
• Note that at first connection to the proxy server, the user will be prompted for a
password in order to access the Cisco Unified Mobility Advantage server. This will
be the user's AD password.

Downloading CUMC for symbain OS

Thursday, April 09, 2009
11:00 AM

If the End user manual provisioning process is not working, or if the

Administrator would prefer to manually provision End user phones, then
Administrative manual provisioning would be preferable.

After end users are activated on the Admin Portal, download the Cisco Unified
Mobile Communicator software onto your computer for provisioning purposes.
There are three steps to downloading Cisco Unified Mobile Communicator for
distribution to Symbian OS phones.

• First, select Handset Platform Management > Version Management.

• Then, click the Download icon next to Symbian to download the Cisco Unified
Mobile Communicator .sisx file to your system.
• Finally, transfer the .sisx file to end user's Symbian phones via infrared or
Bluetooth.
Mobility Connect Steps
Thursday, April 09, 2009
11:03 AM

• To configure the softkey template, choose Device > Device Settings > Softkey
Template. Add the Mobility softkey to the On Hook and Connected Call states.
• Configure the end user by choosing User Management > End User. Enable
Mobile Connect for the end user by checking the check box, and also set the
maximum number of RDs for that end user.
• This step of Mobile Connect configuration is optional.
o If you wish to implement access lists, you must first configure them by
choosing Device > Device Settings > Access List.
o Enter a name and description, and select the owner of the access list. Then
specify the type of ACL, whether Allowed or Blocked.
o Click Add Member to perform the initial configuration of an access list
member. You can also select an entry from the Access List Members list to
change the configuration of an existing member.
 o If you decided to configure access lists, you must also apply them to the
appropriate RDs. By choosing Device > Remote Destination, you can
specify either an Allowed Access List or a Blocked Access List for that
destination. Note that if a Blocked Access List is set, all numbers not
contained in the access list are allowed, and vice versa.

• Next, configure the IP Phone. Choose Device > Phone. Noting that one line will
be shared with the RDP, assign a softkey template and set the Owner User ID.
• To configure the RDP, choose Device > Device Settings > Remote Destination
Profile.
o Add the line of the office phone, noting that the screen updates after this
addition. Also note that this line is shared with the office phone. The
configured Line CSS and partition therefore apply to both the office phone
and RDP. The Line CSS and Device CSS are combined, with partitions of the
Line CSS considered first.
o The CSS is used for outgoing calls placed with MVA, while the Rerouting
Calling Search Space allows for ringing of an RD or RDs when a call is
received at the office phone.
• The next step in configuring Mobile Connect is adding an RD or RDs to the RDP.
o Choose Device > Remote Destination.
o Set the number of the destination, and check the Mobile Phone check box
to allow active calls to be transferred from the office phone to the RD using
the Mobility softkey.
o Checking the Enable Mobile Connect box allows calls placed to office
phones to also ring the RD.
o The line or lines of the RDP are shown only after you have set the RDP and
clicked Save in the previous step.
o Note that, once saved, the RDP cannot be changed.
o Check the check box to associate an RD with the line or lines of the RDP.

• To configure service parameters, choose System > Service Parameters.

o There are instances when a configured RD number may not match the
caller ID of the remote phone. This can occur, for example, because of a
 PSTN access code or steering digit and long distance code prefix, for
example '9 1', in the RD.
o To address this situation, you can change the Matching Caller ID parameter
from Complete Match to Partial Match, and then set the number of digits
required to match. The Partial match setting will ensure that calls to internal
devices are shown with the caller ID of the associated office phone.

Licensing and upgrading

Thursday, April 09, 2009
4:46 PM
Capacity
Thursday, April 09, 2009
4:50 PM
Integration of Voice mail and conferencing
Thursday, April 09, 2009
4:51 PM
• Basic settings