Release Notes

New features in XC2
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 3 of 21
Collaboration meeting room information available on the web interface
You can use the Collaboration meeting rooms page to search for one or more Collaboration Meeting
Rooms (CMRs) that have been configured via the TelePresence Conductor’s Provisioning API using a
management tool such as Cisco TMS. For each CMR, details on aliases, auto-dialed participant and other
related data can be viewed. The data associated with a CMR is configured via the Provisioning API. It cannot
be modified via the TelePresence Conductor’s web interface and it cannot be used by conferences
configured via the web interface.
Increased number of TelePresence Server calls supported
In older versions of TelePresence Server software it was possible to connect only up to 104 participants in
total to either a standalone TelePresence Server or cluster of TelePresence Servers. In TelePresence Server
version 4.0 it will be possible to connect up to 200 participants in total (up to 104 per conference). Changes to
TelePresence Conductor allow support for these new limits.
Audio-only quality setting added
You can configure audio-only conferences on TelePresence Servers using a new predefined 'Audio-only (no
video, mono audio)' conference quality setting.
Segment switching support
TelePresence Server version 4.0 supports segment switching, which allows multiscreen endpoints to switch
just the screen of another multiscreen endpoint that contains the loudest speaker rather than all screens. This
feature works only for multiscreen endpoints that provide loudest pane information and for TelePresence
Server version 4.0. It is ignored otherwise.The default is to have segment switching enabled.
The feature can be enabled or disabled via:
n TelePresence Conductor's web interface (on the Conference template page)
n Cisco TMS's web interface (via the Custom Parameters on the Create new CMR Template page)
n the advanced_parameters attribute of the ConfBundle object when using the TelePresence
Conductor's Provisioning API directly
The TelePresence Server must be:
n connected to the TelePresence Conductor
n running version 4.0 or later
n configured in Remotely managed mode
H.264 - SVC signaling passthrough
The TelePresence Conductor back-to-back user agent (B2BUA) now passes through all H.264-SVC
(scalable video codec) signaling. This will allow endpoints to use the hybrid conference and multistream
endpoint support on the TelePresence Server when it is available.A hybrid conference includes some audio
and video streams that are switched and some that are transcoded. See TelePresence Server Release
Notes for more information.
H.265 passthrough
The TelePresence Conductor back-to-back user agent (B2BUA) now passes through all H.265 signaling.
Like H.264 - SVC signaling this will allow endpoints to use the hybrid conference and multistream endpoint
support on the TelePresence Server when it is available.