Print

Testing the Configuration

About this task

Use this procedure to test a configuration of the AE Services Integration for IBM Lotus Sametime.

Procedure

  1. Start the Sametime server.
  2. Start Sametime Connect on two computers (referred to as C1 and C2 in this example).
  3. If you do not see phone icons next to the users in your contact list, then it is possible that the installation of the telephony presence Eclipse plug-ins was not successful. In the latest release of the telephony presence Eclipse plug-in, the presence icon is only displayed when a user is off hook. However, if you do not have the latest release of IBM Sametime Connect, and there was an error installing the plug-ins, you may have to go to Tools > Plug-ins > Manage Plug-ins, uninstall the Extended Status feature and Telephony Status feature plug-ins, then restart Sametime Connect and reinstall the plug-ins.
  4. Perform one of the following steps:
    • For Windows: Open a terminal and, in .\telephony_ext\AES\presence\bin (Community server) or \sametime_tcspi\AES\presence\bin (Media Manager) or .\presence_service\AES\presence\bin (Standalone Presence Services), run wrapper.exe wrapper.conf. This will run the Telephony Presence Services in the foreground. The log level can be controlled via logging.properties in .\telephony_ext\AES\resources (Community server) or .\sametime_tcspi\AES\resources (Media Manager) or .\sametime_tcspi\AES\resources (Standalone Presence Services). (Note: If you rebooted the Domino server after installing the Telephony Presence Services, it will already be running as a service. Go to the Windows Service Controller and stop the service before performing this step.)

    • For Linux: Open a terminal and navigate to /telephony_ext/AES/presence/bin and run /wrapper. This will run the Telephony Presence Services in the foreground. The log level can be controlled via logging.properties in /telephony_ext/AES/resources (Community Server) or /sametime_tcspi/AES/resources (Media Manager) or /presence_service/AES/resources (Standalone Presence Services. (Note: If you rebooted the Domino server after installing the Telephony Presence Services, it will already be running as a service. From root, run /sbin/service presence-service stop.)

  5. Make a manual call (using the keypad on a phone, not Sametime Connect) from the device that belongs to the Sametime user logged in on computer C1.
    • If you do not see that user's phone icon go off hook after placing the call, then the Telephony Presence Services is not functioning correctly. Increase the logging level if there are not any obvious errors in .\telephony_ext\AES\presence\logs\presence.log.0 (Community server) or .\sametime_tcspi\AES\presence\logs\presence.log.0 (Media Manager) or .\presence_service\AES\presence\logs\presence.log.0 (Standalone Presence Services). (Note: ignore the exceptions about not finding the files in the mapping directory.) When the Telephony Presence Services is initialized successfully, you will see the message The presence service is starting. followed some lines later by The presence service started. in presence.log. Otherwise you will see the message The presence service failed to start.

    • If you do see that user's phone icon go off hook, the configuration for the Telephony Presence Services is correct. Stop the service in your console using Ctrl-C. Then perform one of the following steps:
      • For Windows, go to the Windows Service Controller, and start the Presence Services.

      • For Linux, run /sbin/service presence-service start.

  6. Using Sametime Connect, make a call from the user on C1 to the user on C2.
    • If the call does not succeed, there may be a configuration problem with the Conference Service or the LDAP store. Look at Trace\telephony_0.log for errors. The logging level for click-to-call is controlled via SametimeDiagnostics_Telephony.properties in the Domino directory. When the Conference Service is initialized successfully, you will see the message The conference service is starting. followed some lines later by The conference service started. in telephony_0.log. Otherwise you will see the message The conference service failed to start.