Release Notes. LifeSize Video Communications Systems Release: v3.5.3

Transcription

1 Release Notes LifeSize Video Communications Systems Release: v3.5.3 Use of LifeSize equipment and software components are governed by the conditions and terms of the LifeSize Communications End User License Agreement. 1

2 Product Documentation The following documentation is available in this release: Documentation Administrator Guide User Guide Quick Reference Card LifeSize EULA and Third Party Licenses LifeSize Safety and Regulatory Notices Release Notes LifeSize Automation Command Line Interface Description Describes how to install, configure, and administer your LifeSize video communications system. Use with the Quick Reference Card included in the product box. Describes common usage and troubleshooting for your LifeSize video communications system. Available from the documentation CD included in the product box as well as from the Support page of the LifeSize web site. A visual depiction of the proper installation of all cables and components. Printed and included in the product box as well as available from the Support page of The LifeSize End User License Agreement and listing of Third Party Licenses are available from the documentation CD included in the product box and from the Support page of Describes safety guidelines and regulatory notices for the LifeSize hardware. This document is available from the documentation CD included in the product box as well as from the Support page of This document, which describes known issues in the current release and any available workarounds. Also provides Customer Support contact information. Available from the Support page of Provides a command line-based entry point for automating access and control of LifeSize Video Communications Systems. For the most current version of user documentation, refer to the Support page of Prerequisites If you are upgrading an existing LifeSize system, or if you need to downgrade after upgrading to this release, ensure that you meet the following prerequisites before performing the upgrade or downgrade. Upgrading from a Previous Release If you are upgrading from an existing release, ensure that all LifeSize cameras and adapters you intend to use are connected to your LifeSize system before you perform the upgrade. Cameras and adapters not connected before you perform the upgrade do not function properly if connected to the system after the upgrade. Note: Upgrading software from version 2.1 or 2.5 may take up to 10 minutes due to camera enhancements. Downgrading from this Release If you downgrade from this release, ensure that all LifeSize cameras and adapters that were connected to your LifeSize system during the upgrade to this release are connected to your LifeSize system before you perform the downgrade. 2

3 Interoperability LifeSize supports the following third party devices. Supplier Products Avaya SIP Enablement Services: 4.0 Communications Manager: Broadsoft Broadworks: 13 Cisco ClearOne EX 1.2 CallManager 4.x for audio calls and CallManager Express for both video and audio calls. Users can register LifeSize systems as H.323 extensions through the Cisco IOS Gatekeeper. The Cisco IOS Gatekeeper must be installed in the network. For more information about IP PBX configuration and support, contact your product distributor or LifeSize Customer Support. Codian MCU 4220: 2.2 (1.10) MCU 4505: 2.2 (1.10) ISDN Gateway 3240: 1.3 (1.8) LifeSize Multipoint: 5.1 Gatekeeper: Gateway: 5.1 Phone: Networker: Transit: 1.5 Control: 3.0 Polycom HDX9004: 2.0 VSX 7000: 8.7 VSX 8000: 8.7 ViewStation: EX: ViewStation MP: ViaVideo PVX: IP 3000: 2.8 (speakerphone) IP 4000: 2.2 (speakerphone) ipower9000: 6.2 MGC 50/1000: 8.0 Path Navigator 7.0 SoundStation Premier Radvision ECS Gatekeeper: 5.5 SCOPIA /24 MCU: 5.5 SCOPIA 100 PRI Gateway: 5.5 Sony PCS-1: 3.3 PCS-TL: 2.32 sipx PBX: 3.8 Tandberg Edge, Centric, and Set-top MXP: F : B : E : E5.3 Gateway: G3.0 3

4 LDAP Servers This release includes support for populating the corporate directory with data from a preconfigured LDAP server. LifeSize recommends that you use an LDAP server configured with an H.350 compliant schema. For more information about populating the corporate directory, refer to the LifeSize Video Communications Systems Administrator Guide. AES Interoperability Support AES interoperability is supported with the following third party devices. Supplier Products Codian MCU 4220 MCU 4505 ISDN Gateway 3240 Polycom Radvision Sony Tandberg ViewStation EX VSX family SCOPIA /24 MCU SCOPIA 100 Gateways PCS-TL PCS-1 MXP family Classic family New Features and Resolved Issues Following are the major new features and resolved issues in this release. Refer to your LifeSize product documentation for more information about using the product. Feature Enhancements: Enabling Telepresence does not automatically lock cameras. (END-8091) Screen view persistence affected by telepresence setting (END-8080) Description In previous releases, choosing Enabled for the Telepresence preference automatically locked all cameras connected to the codec. In this release, enabling telepresence does not automatically lock the cameras. In previous releases, the screen view that appeared in the display when a call connected was the screen view used in the previous call and was not affected by the setting chosen for the Telepresence preference. In this release, the user interface tracks and uses the last screen view selected for calls placed with telepresence enabled independently of calls placed with the telepresence disabled. A call placed with telepresence enabled uses the last screen view of the previous call placed with telepresence enabled. A call placed with telepresence disabled, uses the last screen view of the previous call placed with telepresence disabled. 4

5 Feature New automation command line interface targets for controlling camera exposure and auto focus. (END-8264, END-8266) Locking a camera disables autofocus and prevents changes in camera focus and exposure when the camera initializes. (END-8342) Resolved Issues: Description This release adds new targets for controlling video image brightness and camera auto focus to the LifeSize Automation Command Line Interface. For more information about using these targets, refer to New Automation Command Line Interface Targets on page 14. In this release, locking a camera in the user or web administration interface with the HD Camera Movement preference or in the automation command line interface with the set camera lock command, automatically disables autofocus and prevents changes in camera focus and exposure settings during camera initialization. PIP appears when In previous releases when users viewed statistics during a call with viewing statistics with telepresence enabled, picture-in-picture appeared in the display and remained telepresence enabled and visible when statistics were hidden. In this release when telepresence is does not hide when enabled, picture-in-picture does not appear when users view statistics. statistics are hidden. (END-7993) SNMP walk of the LifeSize Monitoring MIB fails after executing command line interface commands with the set verb and snmp object. (END-8136) An SNMP walk with the LifeSize Monitoring MIB fails after executing commands in the command line interface using the set verb and the snmp object. This issue is resolved in this release. Video freezes in far end Video freezes in the display of a far end participant that supports standard display of standard definition video if you select the VGA input as the primary video input for a definition video participant LifeSize system (v3.5.0 or later) during a call. This issue is resolved in this if PC chosen as primary release. video input during a call. (END-8210). Dialing a meeting from the command line interface fails. (END- 8004) Modified Indoor 2 option for HD Camera White Balance preference produces video that is less blue. (END-8084) Dialing a meeting from the command line interface using the control call dial command fails. The duration of the pause interval between dialing the parties in a meeting is increased in this release from one second to five seconds. The color coefficients associated with the Indoor 2 option for the HD Camera White Balance preference are modified resulting in video that is less blue compared to video in previous releases with this option selected. 5

6 Known Issues The following table lists known issues and their solutions or workarounds, if available. Numbers in parentheses following an issue are used for internal tracking purposes only. Issue/Problem The get video h241-mbps and set video h241-mbps commands in the CLI are not functioning properly. (END-7798) The set snmp enable on CLI command returns an error if the SNMP service is already enabled. (END-7740) (END-8336) Packet loss statistics not reported. (END-4297) Certificate message always displays. (END-4515) Configuring LDAP preferences does not automatically disable Auto Discovery (END-6462) Description/Workaround The get video h241-mbps and set video h241-mbps commands in the LifeSize automation command line interface (CLI) appear to function properly, but do not set and accurately report the setting of this target on the LifeSize system. Also, after a system is reset, the get video h241-mbps command does not return a value. The latter produces an error for the set video h241-mbps command in the output of a system restore performed from the web administration interface or from the CLI. To set the H.241 MaxStaticMBPS preference, use the user or web administration interfaces. The set snmp enable on command returns an invalid parameter error (04) in the automation command line interface (CLI) if the SNMP service is already enabled. To view the current setting, use the get snmp enable command in the CLI. This error may also appear in the output of a system restore performed from the web administration interface or from the CLI. Packet loss statistics may be incorrect with any entity that does not send RTCP reports. Internet Explorer 7 displays a certificate error message at the top of the LifeSize web administration interface at all times. You can safely disregard this message. The LifeSize Video Communications Systems Administrator Guide incorrectly states: If you configure the LDAP preferences, the LifeSize system automatically disables auto discovery to prevent duplicate entries from appearing in the corporate directory. This functionality is not included in this release. If you configure LDAP preferences, you must disable auto discovery to prevent duplicate entries from appearing in the corporate directory. 6

7 Issue/Problem The LED sequence when holding the reset button as documented in the Administrator Guide does not apply to LifeSize Express. (END-6834) Description/Workaround For LifeSize Express systems, pressing the reset button while the system is running affects the LED on the front of the codec and the system as follows: If you press the button for approximately 5 seconds, but less than 10 seconds, the LED appears blue and red and then solid red and the system restarts. If you press the button for more than 10 seconds but less than 15 seconds, the LED appears blue and red and then solid red. It then flashes blue on and off alternately for equal durations of time (50% duty cycle). The system restarts and resets preferences to their default settings. If you press the button for more than 15 seconds, but less than 20 seconds, the LED appears blue and red and then solid red. It then flashes blue on and off alternately for equal durations of time and then on for a shorter duration (10% duty cycle). The system restarts using the previous version of the software and resets preferences to their default settings. If you press the button for more than 20 seconds, but less than 25 seconds, the LED appears blue and red and then solid red, flashes blue on and off, and then appears solid blue. Continue to hold the reset button for at least five more seconds to restart the system without changes to the configuration. Product Limitations The following table lists known limitations with this LifeSize product. Numbers in parentheses following an issue are used for internal tracking purposes only. Feature Web administration interface supported with Adobe Flash Player v or later. (END-7456) G.728 audio codec not supported with LifeSize Networker v2.0. (END-7656) Delay in video transmission from LifeSize Room as the MCU in 5-way and 6-way calls when last speaker hangs up. (END-7507) (END-7518) Poor quality audio with G.728 audio codec in calls with LifeSize v3.5 systems and LifeSize Multipoint. Analog phone line connection (PSTN RJ-11) on LifeSize codec is not supported in China. Support or Limitation This release supports the use of the web administration interface with Adobe Flash Player v or later. Support for the G.728 audio codec in ISDN calls with LifeSize Networker v2.0 is not available in this release. You may experience long delays (approximately 30 seconds) in receiving video from LifeSize Room as the MCU in a 5-way or 6-way call if the last speaker in the call hangs up. You may experience poor quality audio when the G.728 audio codec is used in calls with LifeSize systems v3.5 and LifeSize Multipoint. Support for the analog phone line connection (PSTN RJ-11) on the back of the LifeSize codec is not available in China in this release. The analog phone line connection on LifeSize codecs shipped to China is blocked. 7

8 Feature Remote input selection of second camera. (END-3697) Caller ID support. (END-1201) System throughput limitation. (END-3667, END-4289, END-4443) Support or Limitation LifeSize systems installed with software release versions earlier than v2.5.0 do not show Main Camera 2 as a far end camera source during a call with a LifeSize Room system v or later that has two cameras. To resolve this issue, upgrade earlier versions. Caller ID of PSTN calls during call waiting is not supported. The maximum supported bandwidth (kb/s) for calls: Model Call AES Enabled AES Disabled LifeSize Room 2-way way way LifeSize Team MP 2-way way way LifeSize Team 2-way LifeSize Express 2-way VGA to S-Video or Composite cables are not supported. (END-4557) Calling your own system. (END-1560) Reopen your web browser after upgrade or downgrade to view the web interface. (END-3779) Maintaining camera brightness after upgrading from v2.5. (END-4735) Link from LifeSize Team or LifeSize Express LAN port to switch may fail when both devices set to auto negotiate speed. (END-6539) Registration to a gatekeeper fails after enabling IPv6. (END-6605) UTF-8 text editor required for viewing or editing imported/exported directory data. (END-6444) 4x3 aspect TV using SD inputs is not supported on either display. Calling your own LifeSize system is not supported and results in infinite looping of windows in your display with a system that supports multiway video calls and a busy signal with a system that supports only a point to point video call. Calling a device multiple times in the same call also results in a similar result and is not supported. To view and access all options in the web interface included in this release, if you are upgrading from a release version earlier than version or downgrading from this release to a previous release earlier than version 2.5.0, close and then reopen your web browser after performing the upgrade or downgrade. When downgrading, you must clear your browser cache. If you are upgrading a LifeSize system from software release v2.5, increase the Camera Brightness preference by 5 after performing the upgrade to maintain the same brightness setting. The LAN port on a LifeSize Team or LifeSize Express codec may be unable to establish a link when you connect the codec to a switch and both devices are set to auto negotiate the speed. If this occurs, set the speed on the switch and the Network Speed preference on the codec to either 100 Mb/s (full duplex) or 10 Mb/s (full duplex). Registration to a gatekeeper fails after you enable the IPv6 configuration preference. Gatekeeper registrations are not supported if IPv6 is enabled. When importing and exporting the directory from the web administration interface, use a text editor that supports UTF-8 encoding to view or edit the data. Double-byte characters are not supported in directory entries imported with the web administration interface. 8

9 Feature Calls placed from the web administration interface Call Manager always appear in the Redial list with auto as the bandwidth and protocol. (END-6497) Downgrading a v3.0 LifeSize system to v2.6 after enabling voice-activated switching leaves the system with voice-activated switching enabled. (END-6304) Far end camera control with voice-activated switching of video (LifeSize Room). (END-6188) Call statistics show incorrect value for packet loss of transmitted video in IPv6 calls. (END-6127) Virtual multiway support with LifeSize participants. Virtual multiway disabled below some resolutions. (END-5835) Virtual multiway only supported during H.264 video calls (END-5701) Auto answer of PSTN calls (END-5821) Support or Limitation Calls placed from the Call Manager in the web administration interface always appear on the Redial list with auto as the bandwidth and protocol, regardless of the actual bandwidth and protocol specified when the call was first placed. Downgrading a LifeSize system v3.0 or later to v2.6 after enabling voiceactivated switching removes the configuration preference but leaves voiceactivated switching enabled. You must perform a system reset on the downgraded system to disable voice activated switching. Participants can only control the far end camera of the MCU and not the active talker. In calls with systems using IPv6 addresses, call statistics incorrectly show zero as the value of the packet loss for transmitted video. Virtual multiway is available only to LifeSize participants during a call when a LifeSize system is the MCU. Non-MCU participants cannot hang up virtual calls. Virtual multiway is not supported during voice activated calls. If the LifeSize system serving as the MCU sends a 16:9 resolution below 544x304 or a 4:3 resolution below 352x288, virtual multiway is disabled. LifeSize participants see the video layouts of a 2-way call. If the resolution increases during the call, LifeSize participants automatically switch back to virtual multiway. This is typically encountered when the bandwidth of the call drops below 256 kb/s. Virtual multiway is only supported during multiway video calls that use H.264. If the call switches from H.264 to H.263, the non-mcu systems revert back to a non-virtual multiway layout. The user sees the layouts available for a 2-way call. If the call switches back to H.264, the system automatically switches back to virtual multiway. This is typically encountered when a third-party device that only supports H.263 is added to the call. A LifeSize system that is configured to answer calls automatically answers a PSTN call only if another call is already connected. AES Security supported with H.323 calls only. Call Manager polling in web administration interface. AES Security is supported with H.323 calls only. Data that appears in the Call Manager in the web administration interface refreshes every five seconds rather than in real time. Adjusting the Video Bandwidth Balance preference during a call has no effect. (END-5711) Adjusting the Video Bandwidth Balance preference during a call has no effect. Adjust this preference before placing a call. 9

10 Feature Voice-activated switching of video with LifeSize Room as the MCU Supported VGA input resolutions. (END-6314) (END-6047) (END-7559) Support or Limitation You must enable voice-activated switching before placing or receiving the first call in the conference. To enable voice-activated switching of video, access User Preferences : Appearance or Administrator Preferences : Appearance : Layout and set the Multiway Call Layout preference to Last Speaker. In 5-way and 6-way calls, only voice-activated switching of video is supported. Placing a 5-way or 6-way call using an entry in the meetings directory automatically changes this preference to Last Speaker and resets the preference to All Callers when the call ends. You cannot disable voice-activated switching during a call. LifeSize recommends that you keep the Multiway Call Layout preference set to All Callers when not using the system as the MCU in a call. Voice-activated switching is supported with H.323 calls only. AES security is not supported and is automatically disabled when voice-activated switching is enabled. The maximum supported bandwidth in a 6-way call with voice-activated switching enabled is 1152 kb/s. Video codecs supported in calls with voice activated switching include H.263, H.263+, and H.264; supported audio codecs include Polycom Siren14 TM (48 kb/s), Polycom Siren14 TM (32 kb/s), Polycom Siren14 TM (24 kb/s), G.722, and G.711 (µ-law and A-law). LifeSize systems support native 16:9 and 4:3 VGA inputs. The System Information screen shows the actual VGA input size for the "VGA Input" status. The input selector now shows a 16:9 or 4:3 window for the VGA depending on the aspect ratio. The largest VGA 4:3 supported is 1024x768. The largest VGA 16:9 supported is 1280x768. The system supports VGA input resolutions as follows: 640x480 - native, no system changes 800x600 - native, no system changes 1024x768 - native, no system changes 1280x scaled to 1024x768, aspect ratio distorted to fit 1280x720 - native, no system changes 1280x768 - native, no system changes The VGA resolutions are sent natively to the far end for the primary or secondary video streams. The resolutions may not exactly match due to H.264 or H.263 protocol resolution constraints. These resolutions are supported only with a screen refresh rate set to 60 Hertz on the device connected to the VGA input. 10

11 Interoperability Limitations The following table lists known limitations with third party products. Numbers in parentheses following an issue are used for internal tracking purposes only. Feature General Third Party Issues: Limitation Voice-activated switching of video delayed or not switched until a different participant becomes the active speaker after video codec renegotiation. (END-7754) When a LifeSize system using voice-activated switching is the MCU in a call and a participant that negotiates a different video codec joins the conference, video switching may be delayed or not switch until a different participant becomes the active talker. Video freezes in LifeSize system v3.5 as the MCU with voice-activated switching of video and LifeSize systems v2.6.7 and third-party endpoints that send H.263. (END-7520) Due to an issue with LifeSize systems v2.6.7 downgrading from H.264 to H.263 video, the video on a LifeSize system v3.5 serving as the MCU with voice-activated switching of video enabled may freeze when participants are a LifeSize systems v2.6.7 and a third-party device that supports only H.263 video. To work around this issue, upgrade the LifeSize system v2.6.7 to v3.5. Video issues in calls when static NAT enabled on LifeSize systems and calls placed through routers with application-level gateways. (END-6920 and END-7305) AES interoperability between LifeSize versions. (END-4922) Audio/video may be affected when registered to different gatekeepers. (END-2871) SIP multi-point calls with third-party devices are not supported. (END-2993) Codian: Enabling static NAT on a LifeSize system and then placing a call through a router with an application-level gateway or protocol fixup that modifies call control traffic may result in no video and/or audio at either the near end or far end of the call. Depending on the router, disabling static NAT on the LifeSize system may resolve this issue. Calls from LifeSize systems with software versions 2.6 and later to LifeSize systems with software version 2.5 are unsupported when AES is enabled. Audio and video may be affected in calls with LifeSize systems and thirdparty devices that are registered to different gatekeepers. SIP multi-point calls with third-party devices are not supported. SIP multipoint calls between LifeSize systems and point-to-point with third party devices are supported. Poor quality audio in calls with Codian MCU 42XX at software version earlier than v2.1. (END-5858) Tandberg: You may experience poor quality audio in calls with a Codian MCU 42XX that has system software earlier than v2.1. To resolve this issue, upgrade the Codian MCU to v2.1. Tandberg 1000 MXP with AES encryption enabled not receiving presentation from LifeSize system as the MCU. (END-7658) A Tandberg 1000 MXP system (F5.3) with AES encryption enabled does not receive a presentation sent from a LifeSize system as the MCU in a multiway call. To resolve this issue, upgrade the Tandberg system to F

12 Feature No video in Tandberg 1000 MXP from LifeSize system after Tandberg adds another caller. (END-7648) No video when AES security used in a call with a Tandberg MXP system (F6.0) (END-6053) Polycom: LifeSize system unable to send presentation from SD input with Polycom VSX 8000 as MCU in multiway call. (END-7611) No video sent to Polycom MGC from LifeSize calling through a third party IP/ISDN gateway. (END- 7506) MaxStaticMBPS capability not advertised in call placed by LifeSize system v3.5 to Polycom MGC v7.5.1 or earlier. (END-7032) Using video switching mode, MGC does not forward video correctly to all participants. (END-4280) Concurrent H.239 presentations unsupported with MGC. (END-3802) Older firmware on Polycom interoperability issues. (END-1925) Limitation In a call with a LifeSize system, no video appears in the Tandberg 1000 MXP display from the LifeSize system after the Tandberg system adds another caller. To work around this issue, from the Tandberg system do the following: 1. Place the call to the LifeSize system. 2. Add another LifeSize participant. 3. After the call connects, disconnect the last participant. Far end video may not appear in LifeSize systems when AES security is used in a call with a Tandberg MXP system (F6.0). To resolve this issue, upgrade the Tandberg system to release F6.1. A LifeSize system in a mutiway call with Polycom VSX 8000 as the MCU and Tandberg 880 MXP cannot send a presentation from a device connected to the SD input due to limitations in negotiating a compatible resolution for the video. LifeSize systems do not send video to a Polycom MGC when the LifeSize system calls the device through a third party IP/ISDN gateway. To work around this issue, use a LifeSize Networker for ISDN calls to the Polycom MGC. A call from a LifeSize system v3.0 to a Polycom MGC v7.5.1 fails and the MGC must be rebooted due to an issue with the MGC receiving the MaxStaticMBPS parameter as an advertised capability from the LifeSize system. A LifeSize system v3.5 does not advertise the MaxStaticMBPS capability when placing a call to an MGC with software v7.5.1 or earlier. To resolve this issue with a v3.0 LifeSize system, upgrade the MGC to v or later. When connecting LifeSize participants on the Polycom MGC (v ) at 512Kb/s or 768Kb/s using video switching mode, the MGC does not forward the video correctly to all participants. For bit rates below 512Kb/s or above 768Kb/s the video switching mode works appropriately. To work around this issue, upgrade the MGC to version 8.0. If a presentation is in progress during a call with a Polycom MGC as the MCU and another participant starts a presentation, the new presentation does not appear in the display. To work around this issue, stop the current presentation before starting the new presentation. You may need to disable H.239 to properly interoperate with older versions of firmware on Polycom equipment. LifeSize displays cloudy video with Polycom VSX8000. (END-3153) No video from Polycom VSX7000 (release 8.0.3) in a SIP call at 1MB. (END- 3042) LifeSize displays cloudy video on the top half of the screen due to a noncompliant bit stream from Polycom VSX8000 when you switch to the far end camera on the Polycom system as the active source. To work around this issue, hang up and retry the call. Video does not display in LifeSize in a SIP call at 1Mb/s bandwidth with Polycom VS7000 (release 8.0.3). To workaround this issue, upgrade the Polycom system to release

13 Feature Polycom Welcome Screen unsupported on LifeSize devices. (END-4266) Video and audio out of sync with Polycom MGC. (END-4265) No presentation from Polycom VSX 7000 with Polycom MGC as the MCU. (END-6513) Distorted audio and no video received in LifeSize systems in SIP calls placed from LifeSize systems to Polycom systems. (END-7528) (END-7557) Audio codec G722 negotiated in a call with Polycom MGC. (END-6029) Cisco: H.239 may not work through your CISCO PIX or ASA (Adaptive Security Appliance) firewall/asa Device. (END-1611) Limitation When LifeSize connects to a conference on the Polycom MGC with IVR, the Polycom Welcome screen does not display. The welcome screen video is transmitted in H.261 which LifeSize devices do not support. Any device that is connected to the Polycom MGC at 128 Kb/s will result in audio being out of sync with video. This problem is not specific to LifeSize. LifeSize systems do not receive a presentation from Polycom VSX 7000 when Polycom MGC is the MCU due to features sent from the MCU that are not supported on LifeSize systems. You may receive distorted audio and no video when placing a SIP call from a LifeSize system to a Polycom system. To work around this issue, place the call from the Polycom system. LifeSize systems negotiate only the G.722 audio codec in calls with Polycom MGC systems. The Cisco fixup protocol does not recognize H.239 and terminates a call if it attempts to open an H.239 stream. If you have a PIX firewall/asa device and are using it to manage the H.323 protocol, you may experience any of the following conditions. o If you are using the H.323 fixup protocol and your version of the PIX firewall/asa (Adaptive Security Appliance) only supports H.323 version 2 endpoints, (PIX Firewall or ASA version 5.3 through version 6.2) the calls always negotiate to H.263 CIF resolution instead of H.263 HD resolution, and the calls always negotiate to an audio algorithm other than AAC. To work around this issue, upgrade your PIX Firewall/ASA to a version that supports H.323 version 3 or greater. o If you are using any known version of the Cisco PIX/ASA H.323 fixup protocol, presentations (H.239) fail and will likely cause the call to terminate. To work around this issue, disable presentations. Call forward and voic on CME works only with Cisco Phones. (END-3320) Radvision: Poor quality audio with G.728 audio codec in calls with LifeSize v3.5 systems and Radvision SCOPIA /24 MCU. (END-7609) Alternatively, to work around all of these issues, configure NAT/firewall settings based on information in the LifeSize Video Communications Systems Administrator Guide, and then turn off the fixup protocol. LifeSize does not currently support the Cisco proprietary SCCP protocol required to use call forwarding or voic with the Cisco IP Phone. You may experience poor quality audio when the G.728 audio codec is used in calls with LifeSize systems v3.5 and Radvision SCOPIA /24 MCU with software versions earlier than To resolve this issue, upgrade the Radvision SCOPIA /24 MCU to version

14 Customer Support LifeSize Communications welcomes your comments regarding our products and services. If you have feedback about this or any LifeSize product, please send it to You may also contact LifeSize Customer Support as follows: Method Address Internet Phone (877) LIFESIZE or (877) , (512) Fax (512) New Automation Command Line Interface Targets This release adds new targets for controlling video image brightness and camera focus to the LifeSize Automation Command Line Interface. The following targets apply to the camera object. autoexposure When used with the get verb, the autoexposure target shows whether automatic adjustment of the camera iris to achieve the specified camera brightness setting for cameras connected to the codec is enabled (the default) or disabled. When used with the set verb, this target disables or enables automatic adjustment of the camera iris. When autoexposure is set to disable, you can adjust exposure manually with the autoexposure-gain and autoexposure-itime targets to control video image brightness. Manually adjusting exposure may be useful in video conference settings where participants are backlit or where lighting sources vary. Note: Adjusting camera brightness with the HD Camera Brightness preference in the user or web administrator interfaces has no effect when autoexposure is set to disable. get Arguments: None get Examples: get camera autoexposure enable ok,00 set Arguments: {enable disable} Enables or disables automatic adjustment of the camera iris. The default is enable. set Examples: set camera autoexposure disable ok,00 14

15 autoexposure-gain When used with the get verb, the autoexposure-gain target shows the current exposure gain setting for cameras connected to the codec. The default is 15. The range is When used with the set verb, this target controls the level of exposure gain when the autoexposure target is set to disable. Higher values for this target increase video image brightness; lower values decrease video image brightness. get Arguments: None Note: If autoexposure is set to enable, setting autoexposure-gain has no effect. get Examples: get camera autoexposure-gain 15 ok,00 set Arguments: {0..30} Specifies exposure gain for cameras connected to the codec. The default is 15. Higher values increase video image brightness; lower values decrease video image brightness. set Examples: set camera autoexposure-gain 20 ok,00 autoexposure-itime When used with the get verb, the autoexposure-itime target shows the current setting of the exposure integration time for cameras connected to the codec. Exposure integration time controls the number of sensor rows in which to accumulate charge for a single pixel in the video image. The default value is 5. The range is When used with the set verb, this target controls exposure integration time when the autoexposure target is set to disable. Higher values increase video image brightness; lower values decrease video image brightness. CAUTION: Changing the default for this setting may affect the frame rate of the video. Values 0-5 produce video at 30 frames per second (f/s); values 6-9 produce video at 15 f/s; and values produce video at 7.5 f/s. Below 30 f/s, video motion may be choppy. LifeSize recommends that you set this target to a value equal to or less than 5. Changing the value of autoexposure-itime may require that you change the value of autoexposure-gain to achieve an acceptable level of video image brightness. get Arguments: None Note: If the autoexposure target is set to enable, setting autoexposure-itime has no effect. get Examples: get camera autoexposure-itime 5 ok,00 15

16 set Arguments: {0..13} Specifies exposure integration time for cameras connected to the codec. The default is 5. Higher values increase video image brightness; lower values decrease video image brightness. set Examples: set camera autoexposure-itime 4 ok,00 autofocus When used with the get verb, the autofocus target shows whether automatic focus control is enabled (the default) or disabled for cameras connected to the codec. Disabling autofocus prevents the camera from automatically adjusting focus as participants move in the room or the camera position is changed. Ensure that you adjust the camera focus to the desired setting before setting this target to disable. get Arguments: None Note: Locking a camera automatically disables auto focus for that camera. Disabling auto focus in the command line interface with the autofocus target disables auto focus for all cameras connected to the codec. get Examples: get camera autofocus enable ok,00 set Arguments: {enable disable} Enables or disables autofocus for cameras connected to the codec. The default is enable. set Examples: set camera autofocus disable ok,00 16