Release Notes

New features in XC2
Cisco TelePresence Conductor Release Notes (XC2.3.1) Page 6 of 21
Automated intrusion protection
An automated intrusion protection feature has been added. It can be used to detect and block malicious
traffic and to help protect the TelePresence Conductor from dictionary-based attempts to breach login
security.
Automated protection should be used in combination with the existing firewall rules feature - use automated
protection to temporarily block specific threats and use firewall rules to block permanently a range of known
host addresses.
Changes to B2BUA security status handling
The TelePresence Conductor back-to-back user agent (B2BUA) now modifies the conference security status
to be unencrypted when the inbound SIP connection is over TCP and the outbound SIP connection is over
TLS. For the conference security status to be encrypted, SIP signaling must be encrypted on all call legs.
ActiveControl support
The TelePresence Conductor now allows ActiveControl to be negotiated between an endpoint and
TelePresence Servers that support this feature. To operate, ActiveControl must be enabled on a
TelePresence Server version 3.1 or later by enabling the iX protocol on the TelePresence Conductor under
Conference templates > Advanced template parameters. Information about capabilities and limitations of
this feature is available in the CiscoTelePresence Server Release Notes.
Allow or disallow conference creation
A conference alias can now be configured to either allow or disallow conference creation.If the conference
alias is configured to disallow conference creation, participants can only join the conference via that alias if
the conference already exists.The conference can still be created via the API or by dialing a different
conference alias defined for the same conference.
New XML-RPC APIparameter added for maximum conference duration
A new XML-RPCparameter has been added to the TelePresence Conductor API that allows APIusers to
override the maximum conference duration configured on the conference template with a lower value.
New XML-RPC APIparameter added for number of endpoint screens
A new XML-RPCparameter has been added to the TelePresence Conductor API that allows APIusers to
override the number of endpoint screens configured on the conference template with a lower value. This
parameter is only applicable to conference templates that:
n point to a Service Preference containing TelePresence Server pools
n have Allow multiscreen set to Yes
n have a Maximum screens value that is greater than the value specified in the APIparameter
Firewall rules configuration
When configuring the firewall rules priority, it is now easier to change the order of the rules by using up/down
arrow buttons to swap the priorities of adjacent rules.
Managing trusted CA certificates
The TelePresence Conductor’s server and trusted CA certificates can now be viewed in either a human-
readable, decoded format, or in raw PEM format.