Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
New features in X7
Cisco TelePresence Video Communication Server X7.2.4 Software Release Notes
Page 15 of 50
Shared cluster licenses
Call licenses are now shared across the entire Cisco VCS cluster.
Traversal and non-traversal call license option keys are still installed on each individual peer and are
subject to per-peer limits, but the licenses are available to all peers in the cluster. Note that any other
option keys (FindMe, for example) must still be installed identically on each cluster peer, as before.
subject to per-peer limits, but the licenses are available to all peers in the cluster. Note that any other
option keys (FindMe, for example) must still be installed identically on each cluster peer, as before.
Note that if a Cisco VCS peer loses its connection to the cluster, the shareable licenses installed on
that peer will remain available to the rest of the cluster peers for two weeks from the time the cluster
lost contact with the peer.
that peer will remain available to the rest of the cluster peers for two weeks from the time the cluster
lost contact with the peer.
Microsoft Edge Server support via B2BUA for Microsoft OCS/Lync
Support for Microsoft Edge Server communications has been added via the introduction of a back-to-
back user agent (B2BUA) application. The B2BUA provides interworking between Microsoft ICE (used
when MOC / Lync clients communicate through the Edge Server) and media for communications with
standard video endpoints. The B2BUA also provides call hold, call transfer and Multiway support for
calls with OCS/Lync clients, and can share FindMe presence information with OCS/Lync.
back user agent (B2BUA) application. The B2BUA provides interworking between Microsoft ICE (used
when MOC / Lync clients communicate through the Edge Server) and media for communications with
standard video endpoints. The B2BUA also provides call hold, call transfer and Multiway support for
calls with OCS/Lync clients, and can share FindMe presence information with OCS/Lync.
The B2BUA replaces the deprecated “Microsoft Office Communication Server” zone profile. After
upgrade, any OCS zones, if enabled, will still work as in previous software versions. However, users
are recommended to migrate to the new B2BUA functionality by following the Microsoft OCS 2007,
Lync 2010 and Cisco VCS deployment guide (document reference D14269).
upgrade, any OCS zones, if enabled, will still work as in previous software versions. However, users
are recommended to migrate to the new B2BUA functionality by following the Microsoft OCS 2007,
Lync 2010 and Cisco VCS deployment guide (document reference D14269).
Presence User Agent
You can now configure the Default published status for registered endpoints to be either Online or
Offline. This is the presentity status published by the Presence User Agent for registered endpoints
when they are not "In-Call".
Offline. This is the presentity status published by the Presence User Agent for registered endpoints
when they are not "In-Call".
Enhanced SIP registration expiry controls
New SIP registration settings on the SIP page (VCS configuration > Protocols > SIP >
Configuration) allow you to configure how the Cisco VCS calculates the expiry period for SIP
registration requests. These settings enable the system to balance the load of registration and re-
registration requests. They can be configured separately for standard and Outbound registration
connections.
Configuration) allow you to configure how the Cisco VCS calculates the expiry period for SIP
registration requests. These settings enable the system to balance the load of registration and re-
registration requests. They can be configured separately for standard and Outbound registration
connections.
These settings supersede the previous Registration expire delta setting.
Improved diagnostics
A range of tools have been introduced to improve troubleshooting.
Diagnostic logging
Additional diagnostic tools have been introduced under a new Maintenance > Diagnostics menu
structure:
structure:
There is a Diagnostic logging tool (Maintenance > Diagnostics > Diagnostic logging) that
can be used to assist in troubleshooting system issues. It allows you to generate a diagnostic log
of system activity over a period of time, and then to download the log so that it can be sent to your
Cisco customer support representative.
can be used to assist in troubleshooting system issues. It allows you to generate a diagnostic log
of system activity over a period of time, and then to download the log so that it can be sent to your
Cisco customer support representative.
You can configure log levels for specific Network Log and Support Log modules. Note that
these are advanced logging configuration options and should only be changed on the advice of
Cisco customer support.
these are advanced logging configuration options and should only be changed on the advice of
Cisco customer support.
The existing System snapshot and Incident reporting options have been moved under the new
Maintenance > Diagnostics menu structure.
Maintenance > Diagnostics menu structure.