Cisco TelePresence Server 3.1(1.95) Software Maintenance Release Notes October 2013 Contents Product documentation New platforms for TelePresence Server New features in 3.1 Resolved issues Open issues Limitations Interoperability Upgrading to 3.1(1.
New platforms for TelePresence Server n Cisco Multiparty Media 310 n Cisco Multiparty Media 320 The TelePresence Server software only runs in the remotely managed mode of operation on these new appliances; that is, Cisco TelePresence Conductor XC2.2 (or later), or a similar system, is required to manage the TelePresence Server on these platforms. Note: Owing to the lack of direct H.
New platforms for TelePresence Server release notes for TelePresence Server version 3.0, and the associated administrator documentation, for more details. Table 1: Differences between TelePresence Server platforms Feature name TelePresence Server on 7010 MSE 8710 or MCU MSE 8510 Media 310/320 or MCU 5300 Series Remotely managed mode Yes Yes Yes* Locally managed mode Yes Yes No* SIP support Yes Yes Yes H.323 support Yes Yes Not directly. Requires H.323 ↔ SIP interworking by Cisco VCS.
New platforms for TelePresence Server Platform licensing comparison The following table compares the number of TelePresence Server screen licenses that each of the platforms can accept and how they translate into conferencing capacity. The table does not display information about licensing for the locally managed mode of operation, as this is only possible on the 7010 and MSE 8710 platforms. Refer to the online help or administrator documentation for details of licensing in locally managed mode.
New platforms for TelePresence Server Call type description Main video Audio Screen licenses required per call Content Maximum calls by hardware type (with licenses to provide 100% of capacity) 10-core VM Media 310 or MCU 5310 Media 320 or MCU 5320 7010 MSE 8710 or MCU MSE 8510 Biggest appliance cluster (two appliances) Biggest blade cluster (four blades) 6 screen licenses 5 screen licenses 10 screen licenses 12 screen licenses 12 screen licenses 20 screen licenses 48 screen licenses Thr
New features in 3.1 New features in 3.
New features in 3.1 software, provided that the endpoints have Touch controllers. The following endpoints are capable of running TC 6.2; follow the links to the user guides to read about the interface options that use ActiveControl.
New features in 3.1 Table 3: TelePresence Server layout families Name and description Example layouts Overlay layouts show the active speaker or content and up to nine overlaid continuous presence panes (per screen) showing other recently active speakers. These are called ActivePresence layouts on the TelePresence Server. Single screen layouts only show the active speaker or content. On multi-screen endpoints, other recent speakers will show on the additional screens.
New features in 3.1 This feature requires that the Third Party Interop key is loaded on the TelePresence Server. The TelePresence Server must be part of a Webex Enabled TelePresence deployment. See the Cisco WebEx Enabled TelePresence Configuration Guide, at http://www.cisco.com/en/US/products/ps11338/products_ installation_and_configuration_guides_list.html, for details.
New features in 3.1 The TelePresence Server overlays these icons, when appropriate, over the video streams composed and sent to endpoints. If ActiveControl is enabled, the TelePresence Server sends the icon state information to endpoints so that endpoints can use their own indications (where supported).
New features in 3.1 Calls between the TelePresence Server and the following endpoints can include a content channel up to 1080p30: n Cisco TelePresence System 500-32 (with TX 6.0 software) n Cisco TelePresence TX1300 Series, TX9000 Series, TX9200 Series (with TX 6.0 software) 1080p30 content in a TelePresence Server conference with these endpoints is possible provided that the calls have adequate media resources and that the content source is 1080p30.
New features in 3.1 The technique involves interleaving the original stream with additional, corrective packets, so that if media packets are lost they can potentially be recovered by the recipient without resorting to retransmission of the originals. Applying FEC consumes additional bandwidth, so a call negotiated at a certain maximum bandwidth will use less bandwidth for the media streams because it needs overhead for the FEC packets.
New features in 3.1 make it more robust to corrupt or invalid incoming bitstreams. Isolated media processor reboot The TelePresence Server on Media 320 is now more resilient in the unusual circumstances of individual media processor failure. On Media 320 models, or mixed Media 310/320 clusters, if a media processor fails it will not cause the whole device to fail.
Resolved issues Assistance Center. If your deployment relies on this serial console output for troubleshooting, we recommend that you configure a syslog server to capture event messages from the TelePresence Server. Disconnection of inactive calls The TelePresence Server now responds to inactive calls by disconnecting them. If media is expected from an endpoint but is not received for 30 to 45 seconds, then the TelePresence Server will disconnect the call.
Resolved issues Identifier Description CSCui91240 Upon being merged into a TelePresence Server conference by an EX90 endpoint, a Cisco Unified IP Phone 9971 did not display any video. This is now resolved. CSCui77823 In a specific deployment model, where a Session Border Controller and Cisco TelePresence Exchange System were used, holding and resuming a call from a TC series endpoint would cause the BFCP-based presentation sharing to fail. This is now resolved.
Open issues Identifier Description CSCug37686 In previous releases, an endpoint advertising that it will send but not receive video was incorrectly reduced to an audio-only call. This is now resolved. CSCub87160 In previous releases, the call security status reported on a TIP-capable endpoint could differ from the security status reported in a TelePresence Server conference. This is now resolved. Open issues The following issues apply to this version of Cisco TelePresence Server.
Limitations Resource optimization causes brief video interruptions When TelePresence Conductor optimizes the resources used for a call, that endpoint's video contribution is very briefly interrupted. This can be visible to others as a flicker of black in the otherwise continuous stream. Issue identifier CSCuj53830. Call transfer is disabled The TelePresence Server does not support call transfer. DTLS and custom certificates DTLS is used to negotiate encryption parameters with TIP endpoints.
Interoperability Firefox 14 is not supported for use with the Cisco TelePresence Server We strongly recommend that you do not use Firefox 14 to access the TelePresence Server’s web interface. This version of the browser causes an issue that was not present in previous Firefox versions and has been fixed in Firefox 15. This issue also affected previous versions of the TelePresence Server software.
Interoperability Call path phrase Explicit call path description TIP Endpoint ← SIP → Cisco Unified CM ← SIP → Cisco VCS/TelePresence Conductor ← SIP → TelePresence Server with TIP negotiation (requires compatible endpoint) Endpoints This section lists interoperability issues with endpoints. Where an endpoint has limitations, such as a lack of support for encryption or content, the interoperability tests omitted the limitations and they are not listed here.
Interoperability Endpoint Software Comments Cisco TelePresence Codec C40 TC6.1.1 Tested H.323 and SIP: n Cisco TelePresence Content Server Cisco TelePresence SX20 Quick Set S5.3 TC6.1.1 Tested H.323 and SIP: n In low bandwidth H.323 calls, an incorrect aspect ratio may be chosen n Changing the display settings during the call may cause streaming and podcast output to fail n DTMF is not supported in Conductor-based deployments Tested H.323, SIP, CUCM to VCS/Conductor SIP, and CUCM to VCS H.
Interoperability Endpoint Software Comments Cisco TelePresence System 1700 MXP F9.3.1 Tested H.323 and SIP: Cisco TelePresence System 3000 1.10.1 n Automatic content handover does not work if MXP tries to present immediately after another endpoint sends content. (Issue identifier CSCud64503) n Under rare circumstances, corruption may be seen when the MXP transmits content in main video.
Interoperability Endpoint Software Comments Cisco TelePresence System EX90 TC6.1.1 Tested H.323, SIP, and CUCM to VCS/Conductor SIP: n A flicker is seen when the video from a participant changes from a continuous presence pane into the main pane. Seen when active speaker changes or when making a participant important. (Issue identifier CSCuh92611) Tested CUCM to VCS H.323 interworking: n Cisco TelePresence C Series, Cisco TelePresence System EX Series TC6.
Interoperability Endpoint Software Comments Cisco TelePresence System TX1300 47, Cisco TelePresence System TX9000 TX6.0.3 Tested TIP: n Orange or green flashes can be seen on the display of these endpoints in 1080p30/720p60 calls. (Issue identifier CSCui78297) n You cannot disconnect audio add-in participants via the participant list on the touch panel. (Issue identifier CSCuj50089) Tested CUCM to VCS H.
Interoperability Huawei Endpoint Software Comments ViewPoint 9039 VCT Tested H.323 and SIP: V100R011C02B013SP40 n Although this endpoint is interoperable in certain scenarios, it is not recommended with prefered Cisco TelePresence deployments LifeSize Endpoint Software Comments Express 220 4.11.13 Tested H.323 and SIP: n Icon 600 LS_RM3_ 1.1.
Interoperability Polycom Endpoint Software Comments HDX 8000 3.1.1.336019 HDX 9006 OTX 300 RealPresence Group 500 3.1.023277 3.1.023277 4.0.240451 Tested H.323 and SIP: n HDX does not support redial missed/rejected calls due to an endpoint limitation n If the endpoint and TelePresence Server are registered to different peers of a VCS cluster, call bandwidth may be limited to 64 kbps. This issue only occurs with H.323 calls n Media quality may be unreliable when using H.261 or H.
Interoperability RadVision Endpoint Software Comments Radvision XT5000 3.0 Tested H.323 and SIP: n 60fps video is not supported in calls with this endpoint n The TelePresence Server only supports H.264 to this endpoint (default codec) n Encryption and the G.722.
Upgrading to 3.1(1.95) Endpoint Software Comments Cisco Unified Communications Manager 8.6.2.21900- If the iX protocol is enabled on the TelePresence 5 Server (for ActiveControl), then calls will fail. To work around this, either disable iX on the TelePresence Server or route calls through a newer version of Unifed CM with iX disabled on the relevant trunk. Cisco Unified Communications Manager 9.0.1.
Upgrading to 3.1(1.95) CAUTION: Make sure that all the backup processes described in this section have been completed before you start the upgrade. Failure to do so could result in data loss. CAUTION: If you are upgrading a cluster you must upgrade all blades in the cluster to the same software version. Note: While you are upgrading a cluster, or restarting it for another reason, the master cannot report the cluster's full capacity until the slaves have also restarted.
Upgrading to 3.1(1.95) Downgrade instructions If you need to reverse your upgrade, you can re-install the former version of the software. The downgrade procedure is the same as the upgrade procedure except you will use the earlier software image. CAUTION: Make sure that all relevant backup processes described in Prerequisites [p.27] have been completed before you start the downgrade. Failure to do so could result in data loss. Downgrading from 3.1(1.
Using the Bug Search Tool Using the Bug Search Tool The Bug Search Tool contains information about open and resolved issues for this release and previous releases, including descriptions of the problems and available workarounds. The identifiers listed in these release notes will take you directly to a description of each issue. To look for information about a specific problem mentioned in this document: 1. Using a web browser, go to the Bug Search Tool. 2. Sign in with a cisco.com username and password.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
