Configuration Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4
Appendix D: Configuring and Troubleshooting the Cisco Unified MeetingPlace Jabber Integration
Downloads: This chapterpdf (PDF - 116.0KB) The complete bookPDF (PDF - 4.38MB) | Feedback

Configuring and Troubleshooting the Cisco Unified MeetingPlace Jabber Integration

Table Of Contents

Configuring and Troubleshooting the Cisco Unified MeetingPlace Jabber Integration

About the Cisco Unified MeetingPlace Jabber Integration

Configuring the Cisco Unified MeetingPlace Jabber Integration

Configuring SSL (Optional)

Troubleshooting the Cisco Unified MeetingPlace Jabber Integration

Collecting Logs


Configuring and Troubleshooting the Cisco Unified MeetingPlace Jabber Integration


This chapter covers how to configure the Cisco Unified MeetingPlace Jabber Integration on a Jabber server so that users can initiate Cisco Unified MeetingPlace meetings from a Jabber Messenger client. It also covers troubleshooting steps to use if you encounter problems with the integration.

See the following sections:

About the Cisco Unified MeetingPlace Jabber Integration

Configuring the Cisco Unified MeetingPlace Jabber Integration

Configuring SSL (Optional)

Troubleshooting the Cisco Unified MeetingPlace Jabber Integration

Collecting Logs

About the Cisco Unified MeetingPlace Jabber Integration

With the Cisco Unified MeetingPlace Jabber Integration, users can initiate Cisco Unified MeetingPlace meetings from a Jabber Messenger client. The meeting initiator 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 Web Conferencing console and have the Cisco Unified MeetingPlace Audio Server dial out to their phones.

Meetings initiated from a Jabber Messenger client use system default settings to determine scheduling parameters, with the following exceptions (which override the value set in the profile of the meeting scheduler):

Password Required is set to No.

Who Can Attend is set to Anyone.

Note the following additional considerations for the Jabber Integration:

Users can initiate meetings from Jabber Messenger whether or not they have reservationless meetings enabled on their user profiles.

Meetings initiated from Jabber Messenger clients do not appear in Find Meetings search results, and do not generate e-mail notifications. Instead, notifications appear in the following ways:

Invitees are notified by receiving an instant message that contains a hypertext meeting ID link.

The user who initiated the meeting receives either an instant message or a broadcast tab from MeetingPlace that contains a hypertext meeting ID link.

Configuring the Cisco Unified MeetingPlace Jabber Integration

Before you begin the configuration, the Cisco Unified MeetingPlace Jabber Integration must be installed on a Jabber server. For information about installing the Cisco Unified MeetingPlace Jabber Integration component, see the Installation and Upgrade Guide for Cisco Unified MeetingPlace Web Conferencing Release 5.4 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

To complete the configuration after installation, do the following procedure by using the Jabber server XCP Controller web interface.

To Configure the Cisco Unified MeetingPlace Jabber Integration on the Jabber Server


Step 1 Log on to the Jabber XCP Controller web interface. Refer to the Jabber documentation for information on how to access this interface.

Step 2 In the Components section, from the Add a New drop-down list, choose Cisco External Command Interface, then click Go.

Step 3 On the Cisco External Command Interface Configuration page, scroll down to the Cisco Unified MeetingPlace Command Configuration section, and enter a value in the MeetingPlace Web Server Hostname or IP Address field.

Step 4 In the MeetingPlace Server Type drop-down list, choose MeetingPlace.

Step 5 Click Submit.

Step 6 From the XCP Controller home page, in the Components section, locate the Cisco External Command Interface component you just added. In the Actions column, click Start.


Configuring SSL (Optional)

You can implement security between the Cisco Unified MeetingPlace Web Conferencing server and the Jabber server by using the Secure Sockets Layer (SSL) protocol. SSL provides secure transmission of data across the network through the use of public/private key encryption.

For information on configuring SSL on the Web Conferencing server, see the "How to Configure Secure Sockets Layer" section on page 5-10.

After SSL has been configured on the Web Conferencing server, and a certificate has been procured or generated, do the following tasks to set up secure communication on the Jabber server:

1. Copy the certificate file from the Web Conferencing server to the Jabber server. The certificate name ends in .cer; you may have noted the location of the file in the "To Apply the SSL Certificate to the Cisco Unified MeetingPlace Web Conferencing Website" procedure on page 5-11.

2. Add the certificate to the keystore on the Jabber server. Do the "To Enter the Web Conferencing Server Certificate File in the Jabber Server Keystore" procedure.

3. Configure the keystore properties in the Jabber XCP web interface. Do the "To Configure the Cisco Unified MeetingPlace Jabber Integration on the Jabber Server" procedure.

To Enter the Web Conferencing Server Certificate File in the Jabber Server Keystore


Step 1 Log in to the Jabber server as root.

Step 2 At the command line, enter:
keytool -import -alias "CiscoMeetingPlace" -file <Certificate File> -keystore <Keystore Location>
and press Enter.


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. You will need to know the full path to the keystore file to configure the Jabber security settings in the next procedure.


Step 3 When prompted, enter a password for the keystore.


To Configure the Cisco Unified MeetingPlace Jabber Integration on the Jabber Server


Step 1 Log on to the Jabber XCP Controller web interface.

Step 2 From the Jabber XCP Controller home page, in the Components section, locate the Cisco External Command Interface component.

Step 3 In the Actions column, click Edit.

Step 4 On the Cisco External Command Interface Configuration page, from the Configuration View drop-down list, choose Intermediate.

Step 5 In the External Command Integration Configuration section, under Cisco Unified MeetingPlace Command, check the SSL Configuration check box.

Step 6 In the Full Path to SSL Key File field, enter the path to the keystore that you configured in Step 2 of the "To Enter the Web Conferencing Server Certificate File in the Jabber Server Keystore" procedure.

Step 7 In the Password for SSL Key File field, enter the password that you configured in Step 3 of the "To Enter the Web Conferencing Server Certificate File in the Jabber Server Keystore" procedure.

Step 8 Click Submit.

Step 9 From the XCP Controller home page, in the Components section, locate the Cisco External Command Interface component you just added. In the Actions column, click Start.


Troubleshooting the Cisco Unified MeetingPlace Jabber Integration

Problem   After adding the Cisco External Command Interface component to the Jabber XCP Controller, the component does not start.

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

For information about the version of Java required for the Cisco Unified MeetingPlace Jabber Integration, see the applicable System Requirements for Cisco Unified MeetingPlace at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html.

To check the Java and Jar paths, do the following procedure.

To Check the Java and Jar Paths


Step 1 Log on to the Jabber XCP Controller web interface.

Step 2 From the Jabber XCP Controller home page, in the Components section, locate the Cisco External Command Interface component.

Step 3 In the Actions column, click Edit.

Step 4 On the Cisco External Command Interface Configuration page, from the Configuration View drop-down list, choose Intermediate.

Step 5 In the Router Connection Information section, verify the value for Command. Check the value for the Java path, which appears after "exec" in the command. Also check the value for the meetingplace.jar file, which appears after "-jar" in the path. You can also copy the text from this field and paste it into a console to attempt to run the component.

Step 6 Click Submit to save any changes.


Problem   Jabber Messenger clients appear to hang when attempting to invite users to or join meetings.

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

To Change the Command Time-Out


Step 1 Log on to the Jabber XCP Controller web interface.

Step 2 From the Jabber XCP Controller home page, in the Components section, locate the Cisco External Command Interface component.

Step 3 In the Actions column, click Edit.

Step 4 On the Cisco External Command Interface Configuration page, from the Configuration View drop-down list, choose Intermediate.

Step 5 In the External Command Integration Configuration section, enter a new value in seconds for the Command time-out (secs) field.

Step 6 Click Submit to save any changes.


Collecting Logs

You can collect console information from the Jabber Messenger client and logs from the Jabber server to help diagnose problems, or to send when you report a problem to Cisco TAC.

In the Jabber Messenger client, the Console tab lists the XML messages passing between the client and the Jabber server; from the Jabber Messenger menu, click View > Console to enable the console.

On the Jabber server, you can enable diagnostic logs from the XCP Controller web interface. To do so, do the following procedure.

To Enable Logging on the Jabber Server


Step 1 Log on to the Jabber XCP Controller web interface.

Step 2 From the Jabber XCP Controller home page, in the Components section, locate the Cisco External Command Interface component.

Step 3 In the Actions column, click Edit.

Step 4 On the Cisco External Command Interface Configuration page, from the Configuration View drop-down list, choose Intermediate.

Step 5 In the External Command Configuration section, under Cisco Unified MeetingPlace Command, from the MeetingPlace Level Filter drop-down list, choose Verbose.

Step 6 Under Java Component Logging, note the value of the File Name parameter. This is the location to which the log will be written.

Step 7 Click Submit to save any changes.