Table of Contents
Advertisement
Verification of the installation
After completing the installation, it is recommended test by verifying that meeting changes populate
both from Lotus to Cisco TMS and from Cisco TMS to Lotus.
Testing meetings from Lotus to Cisco TMS
To verify that meetings booked from Lotus are being saved in Cisco TMS, create a test meeting for a
date in the future in your calendar using two rooms in Lotus that are integrated with Cisco TMS.
Check that:
You receive a meeting request email for each room.
You receive a meeting confirmation for each room.
The meeting is shown in Cisco TMS under Booking > List Conferences.
If the tests are not successful, troubleshoot the issue using the sections below.
Process overview for meetings created in Lotus
The steps taken when booking a meeting from Lotus are described below. Use this workflow to help
you diagnose where a failure is occurring if your test meeting does not complete successfully.
1.
A user creates a meeting request in their calendar and clicks send to send the invitations.
2.
The Lotus Notes client sends meeting requests to participants, including each room selected for
the meeting. These are displayed in the rmeeting organizer's Inbox.
3.
The meeting requests for the rooms show up in the Reservation Database under Reservations >
Waiting for Approval.
4.
The "Waiting for Approval" requests are processed by the Cisco TMS Trigger agent.
5.
The Integration components log into the Cisco TMS server and try to create a meeting using the
details from the Lotus Meeting request.
6.
Cisco TMS tries to book the meeting request and will accept or reject the meeting if it is not
possible to book.
7.
If the meeting is accepted by Cisco TMS, the reservations requests are approved and moved out
of the Waiting for Approval view and into the Reservation Database calendar and can be seen
in the Date and By Resource views in the Reservation Database. If the meeting is rejected by
Cisco TMS, the reservation requests are denied and moved into the Declined view of the
Reservation Database.
8.
The emails accepting or declining the meeting are then sent to the meeting requester by Domino
from the Reservation Database.
Troubleshooting
If the test booking is not successful and the organizer does not get an email notification of acceptance
for each room in the test meeting, you can use the list of symptoms and tips below to troubleshoot
each phase of the process listed above to help diagnose the problem.
Steps 1 and 2
Symptom: User never sees meeting request email messages after sending a meeting request.
Tip: Look at the Lotus Notes Client or User Actions. Be sure to refresh the Inbox (F9) to check for new
email.
Step 3
Symptom: Meeting requests do not show up in the Reservation Database Waiting for Approval
View.
Tips:
Make sure that the request is not in other views in the Database.
Cisco TMS Extension for IBM Lotus Notes – Installation and getting started guide
Verification of the installation
Page 29 of 45
Advertisement
Table of Contents
Troubleshooting
