Lifesize – Video Conference Codec

This Driver has been tested on a Lifesize Room 200 video conference system running firmware version: 4.7.19.

Revision History

The Initial Release of the driver

TCP Connection

The ETHERNET connection on the Lifesize codec should be connected to the Network connection. Ethernet control is the preferred method of control for this series of codecs, as not all codecs have RS232 capabilities.

The Lifesize codec should be set to a Static IP Address using port 23. The TCP connection requires a user and password credentials in order to make a connection. By default the user name is “auto” and the password is “lifesize”. You MUST enable Telnet on the codec in order to use this driver. By default Telnet is NOT enabled.

Enabling Telnet

Connect to the codec via the web interface, login and proceed to the “Preferences/Security/General” property window. Once in the correct settings window, you will need to select “Enabled” in the Telnet property. Save Changes, and reboot the codec.

RS-232 Connection

The RS232 connection on the Lifesize Room Series Codecs should be connected with a standard patch cable to the XP Series Processor serial adapter; a null modem adapter and a female gender changer are needed.

The LifeSize Room Series Codecs default to a baud rate of 9600. Only the “Room” series of codecs have a RS232 Port.

Enabling RS-232

In order to use the RS232 Port for control, you must enable the port and set the baud rate. By default it seems the serial port is disabled. I had to, using a SSH client (Putty), connect into the codec, login and configure the RS232 Port. The command I used was “set serial port1 –s auto –b 9600”. Once I sent this message I was able to communicate on port1. According to the manual Port2 is already configured, but my codec seem to have just one serial port.

Configuration Info

This instruction guide is not a replacement for the Lifesize Operation or Control Manuals. Please be familiar with the Lifesize Codec prior to configuration of this driver. The codecs listed below are supported by this driver. Although the codecs in this series use the same protocol, there are differences in their capabilities. The “Alpha” letter next to the codec is used throughout the driver configuration and control to indicate the differences and options available with each codec type. When configuring the driver, select the codec type from the list.

Codecs Supported

Express (A)

Express 200 (B)

Express 220 (C)

Room (D)

Room 200 (E)

Room 220 (F)

Team MP (G)

Team 200 (H)

Team 220 (I)

IR Remote Emulation

The simplest method of control is to use IR Remote Emulation, which is control of the codec via RS232/TCP using commands that emulate the IR remotes. The driver emulates two versions of the remote, “Black or “Silver”. It is recommended you use the correct remote emulation for the system that you are controlling.

Using the remote emulation should only be used when the user of the system can see the codec video output display. Without this, the user has no reference as to what they are doing with the system.

Phonebook

The phonebook can be quite large on this system. Because of this, the driver was designed to retrieve searched listings. On the initial search the driver returns up to 25 listings. If there is more, you can load more if needed. There are System Variables that indicate if there are more to load, “Searched Count” lists have many it found, while “List Count” list how many are currently loaded. Using Driver command “Search Directory (Next 25 Entries)” will load additional listings into the list control. Eventually you will be able to load all the listings. The users should be taught to do smart searches using the search keyboard to narrow the search versus loading all the entries into the list control. The phonebook search engine allows you to search both a local and a corporate directory.

Call ID

The codecs support up to 6 calls simultaneously, 4 Video and 2 Audio. The codec system uses variable call handles; the driver assigns these calls to driver managed “Call IDs”. Some driver commands use these “Call IDs” to manage things like Far end Camera Control and Hanging up a call. There are 6 Call Status System Variables Section that show you what calls are assigned to what “Call IDs”. Use these System Variables as needed to provide the user with information pertaining to the calls. It will help them to know which call they are hanging up.

System Events

Incoming Call

There is an Incoming Call system event programmed into the driver, use this to provide indication to the user that there is an incoming call. There are specific System Variables to allow the user to get information about the incoming call prior to answering. The Incoming Call system event only gets triggered when the codec has auto-answer disabled.

Far End External Camera Control

When in a video call, it is possible for the far end user to move your camera. When the camera is connected to the codec for control purposes, this will work automatically as long as the settings are correct in the local codec. When you have to control a camera external from the codec, the far end may still wish to control the camera. System Events have been programmed into the driver to provide you the ability to control and externally controlled camera. So when the far end user tries to control you camera you will get the following System Events. You do not need to use them, they are optional.

Pan Left (Called when the initial request to move the camera is received)

Pan Right (Called when the initial request to move the camera is received)

Tilt Up (Called when the initial request to move the camera is received)

Tilt Down (Called when the initial request to move the camera is received)

Continue (Called when the user wants you to continue the last move request)

Stop (Called when the user wants you to stop all movements)