Tandberg’s LCS integration enables both call and control of video end points by Microsoft’s Office Communicator client. Version 2.4 of the “Tandberg LCS Integration installation manual, getting started” guide was used during the installation. The LCS Integration package consists of two parts, the Tandberg SIP-CX Gateway and Tandberg Communicator Integration.
Tandberg SIP-CX Gateway.
The Tandberg SIP-CX Gateway provides a multi-participant conference facility when coupled with a Tandberg MPS.
Page 6 of the installation manual says “Do not install the SIP-CX gateway on the LCS Server as this will lead to problems with LCS setting up trusted sites”. Page 8 of the manual says “The SIP-CX gateway can be installed on the TMS server, the LCS server or a dedicated server. The only difference is that if installing it on the LCS server, the default SIP-CX port (5060) cannot be used for the LCS/SIP-CX gateway communication as it will cause port conflicts with the LCS software”. This is somewhat conflicting advice. I chose to go with a seperate server as Server3 is only running Tandberg’s TMS. for performance reasons, you would want this to be on a dedicated server for typical deployments. The diagram on page 10 shows the port settings. I chose to change from the default 5060 to 5080 just so I could see how a slightly different configuration can be done from the LCS configuration tools when establishing an authorised host (page 14) and most importantly during the steps described on pages 16 and 17 as this is where the port setting is entered when creating the static route. As there is no CA for the domain, I didn’t select a HTTPS connection to the TMS server as shown on page 10. As per the advice on page 17 suggesting the use of a different domain, I chose horizon.sip for conferences. A copy of the conferences.xml file was made and then using the Tandberg LCS Configuration tool as shown on page 37, a demo config was created.
Tandberg Communicator Integration
The Tandberg Communicator Integration is an extension to Microsoft’s Office Communicator and adds a Tandberg tab to the client.
TandbergCommunicatorIntegrationPreRequirements.msi was run on the LCS server followed by TandbergCommunicatorIntegration.msi. I created a local user called TandbergCommunicator as per page 34 and as per suggestion on page 35, a domain user called VideoConferenceAssistant. VideoConferenceAssistant is used as a bot for sending feedback to Office Communicator clients.
The Tandberg Communicator Integration Configuration tool TLCSConfigTool.exe was run to generate the registry file containing the Office Communicator extensions. As only a few clients are involved, I manually imported the .reg file on each workstation. When Office Communicator was restarted, the Tandberg tab was visible on the bottom of the client. The extension is essentially a customised http interface to the TMS. Unfortunately the tab was not visible on all of the clients and Appendix 4 covers adding the TMS server as a trusted site. Once Office Communicator was restarted, the tab was visible.
Rather than editing the IM filter as per Appendix 2, the filter was disabled using the LCS MMC. Obviously in a live environment, the filter would be edited to allow traffic from the Tandberg bot.
