With Jabber for Cisco Unified MeetingPlace, users can initiate Cisco Unified MeetingPlace meetings from a Jabber Messenger client. The user who initiates the meeting selects meeting invitees from a list of contacts and invites them to the meeting. Each invitee receives a message (and a pop-up window) inviting them to join the meeting. By clicking on a hyperlink in the invitation message, the invitees can enter the Cisco Unified MeetingPlace meeting and have Cisco Unified MeetingPlace dial out to their phones.

Gathering Installation Values

Use the following table to record the information you need to prepare for your installation.

Description

Your Value

Cluster name

Note: Clusters enable your Jabber XCP server to use dynamic routing. All of the Jabber routers that you want to interact should be in the same cluster.

Realm name, which is a unique string used to identify the router and all of its components (i.e., the entire system). The realm name is used to distinguish between the components belonging to different Jabber XCP installations in the event that you run multiple Jabber XCP servers.

Hostname of your Jabber XCP server.

IP address of the Jabber XCP server.

Note: This must be a static IP address.

Port on which the Jabber router will listen for connections from all components (also referred to as the Master Accept Port).

Password to be used for router and component authentication.

Note: All components will use the same authentication password.

Staging directory, which holds files that are waiting to be scanned or that are being scanned. It also holds files that have failed the scan.

Final directory, which holds files that are ready for users to download.

Setting the JABBER_HOME Environment Variable

Before you install Jabber with Cisco Unified MeetingPlace, set the JABBER_HOME environment variable for the root account on the Jabber XCP server to point to the directory in which Jabber is installed.

Procedure

Sign in to the Jabber XCP server as root.

Enter bash at the command line.

Enter JABBER_HOME=<Path to the directory in which Jabber is installed>, where <Path to the directory in which Jabber is installed> is the path to the directory in which Jabber is installed. For example, enter JABBER_HOME=/opt/jabber.

Enter export JABBER_HOME.

Enter echo $JABBER_HOME. to confirm the setting.

The system displays the path to the directory in which Jabber is installed.

2 How to Install the Jabber with Cisco Unified MeetingPlace Integration

Unlike other Cisco Unified MeetingPlace integrations, the Jabber integration is installed on a standalone server and not on a Cisco Unified MeetingPlace Web Server. Perform the following steps in the order listed to install the Jabber with Cisco Unified MeetingPlace integration:

Related Topics

Starting and Stopping the Jabber XCP Server

The runjabber script (which is located in the bin subdirectory of the Jabber XCP installation directory) starts and stops the Jabber XCP server. It also allows you to see the status of the server and to view or change the logging level.

Note: When you start the Jabber XCP server, all events are logged to syslog by default.

Procedure

Enter cd /opt/jabber/bin to navigate to the bin subdirectory of the Jabber XCP installation directory.

Enter ./runjabber start to run the runjabber script to start the Jabber XCP server.

Related Topics

3 Configuring the Jabber with Cisco Unified MeetingPlace Integration

This section describes how to configure Jabber with Cisco Unified MeetingPlace on a Jabber XCP server so that users can initiate Cisco Unified MeetingPlace meetings from a Jabber Messenger client. You have the option to configure Secure Sockets Layer (SSL) to implement security between Cisco Unified MeetingPlace and the Jabber XCP server. Use SSL to provide secure transmission of data across the network through the use of public or private key encryption.

Before You Begin

Sign in to the Jabber XCP server as root.

Configure SSL on the Cisco Unified MeetingPlace Web Server. See the Configuration Guide for Cisco Unified MeetingPlace Release 8.0 or the online help in the administrator interface for information about configuring SSL.

Copy the certificate file from the Cisco Unified MeetingPlace Web Server to the Jabber XCP server. The certificate file is for Hostname [Home Page] and ends in .cer.

Obtain the hostname or IP address of the Cisco Unified MeetingPlace Web Server.

Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.

Procedure

Open a command line interface.

Enter keytool -import -alias "CiscoMeetingPlaceHomePage" -file <Certificate File for Hostname [Home Page]> -keystore <Keystore Location>, where <Certificate File for Hostname [Home Page]>'is the name of the certificate file for the Hostname [HomePage] and <Keystore Location> is thevalue for the -keystore parameter.

Note: The -keystore parameter specifies a file that holds the keystore. If you do not specify a full path, the keystore is created in the directory in which you run the keytool command.

Enter a password for the keystore.

Configuring SSL for Cisco Unified MeetingPlace on the Jabber Server

Before You Begin

Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.

Procedure

Locate the Cisco External Command Interface component.

Select Edit.

The system displays the Cisco External Command Interface Configuration page.

Problem: The Cisco External Command Interface component does not start after adding it to the Jabber XCP Controller.

Solution: This problem can occur if an incorrect version of Java is installed on the Jabber XCP server, or if an incorrect path is specified for the Java executable or the meetingplace.jar file in the Cisco External Command Interface configuration.

Before You Begin

Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.

Procedure

Locate the Cisco External Command Interface component.

Select Edit.

The system displays the Cisco External Command Interface Configuration window.

Choose Intermediate from the Configuration View list box.

Ensure that the value for Command in the Router Connection Information area is correct.

Ensure that the value for the Java path is correct. The value appears after "exec" in the command.

Ensure that the value for the meetingplace.jar file is correct. The value appears after "-jar" in the path.

(Optional) Copy the text from this field.

(Optional) Paste the text into a console to attempt to run the component.

Select Submit.

Clients Response is Slow When Attempting to Join a Meeting

Problem: Jabber Messenger clients experience slow response time when attempting to join a meeting, or when inviting users to a meeting.

Solution: If the response time between the Jabber Messenger client and Jabber is too long, users might think their Jabber client has hung while it is waiting for a response from the Jabber XCP server. The default time period is 300 seconds (five minutes). You can adjust this time period by completing the following procedure.

Before You Begin

Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.

Procedure

Locate the Cisco External Command Interface component.

Select Edit.

The system displays the Cisco External Command Interface Configuration window.

Choose Intermediate from the Configuration View list box.

Enter a new value in seconds for the Command time-out (secs) field in the External Command Integration Configuration area.

Select Submit.

Collecting Log Files

You can collect console information from the Jabber Messenger client and logs from the Jabber XCP server to help diagnose problems. If you report a problem to Cisco TAC, you might need to send the logs to them.

In the Jabber Messenger client, the Console tab lists the XML messages that pass between the client and the Jabber XCP server. To access the message list from the Jabber Messenger menu, click View > Console to enable the console.

On the Jabber XCP server, you can enable diagnostic logs from the Jabber XCP Controller web interface.

Before You Begin

Sign in to the Jabber XCP Controller web interface. See the Jabber documentation for information about how to access the Jabber XCP Controller web interface.

Procedure

Locate the Cisco External Command Interface component.

Select Edit in the Actions column.

The system displays the Cisco External Command Interface Configuration window.

Choose Intermediate from the Configuration View list box.

Locate the External Command Configuration area.

Locate the Cisco Unified MeetingPlace Command area.

Choose Verbose from the MeetingPlace Level Filter list box.

Make a note of the value of the file name parameter under Java component logging. This is the location where log will be written.