Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Open caveats
Cisco TelePresence Video Communication Server X6.1 Software Release Notes
Page 15 of 26
Open caveats
The following issues currently apply to this version of the Cisco VCS.
Reference ID
Summary
85593
External policy: when editing a policy service under the VCS configuration > Dial plan
> Policy services web page it is not possible to change the password used for remote
authentication. The password can however be changed via the CLI interface or by
deleting and then recreating the whole policy service with the new password.
> Policy services web page it is not possible to change the password used for remote
authentication. The password can however be changed via the CLI interface or by
deleting and then recreating the whole policy service with the new password.
N/A
Hardware shutdown procedure: the Cisco VCS is shipped with a 250 GB Hard Drive,
which is utilized for saving logs and the TMS Device Provisioning Agent. You are
recommended to shut down the Cisco VCS prior to it being unplugged to ensure a clean
shutdown process. This can be done from the web interface.
which is utilized for saving logs and the TMS Device Provisioning Agent. You are
recommended to shut down the Cisco VCS prior to it being unplugged to ensure a clean
shutdown process. This can be done from the web interface.
N/A
TANDBERG Gatekeeper interoperability: if a TANDBERG Gatekeeper is configured as
a client in a traversal relationship with a Cisco VCS running X3.0 or newer, then it is
recommended that the Gatekeeper be upgraded to N6.1. If the Gatekeeper is not
upgraded, it may occasionally restart when a call is attempted.
a client in a traversal relationship with a Cisco VCS running X3.0 or newer, then it is
recommended that the Gatekeeper be upgraded to N6.1. If the Gatekeeper is not
upgraded, it may occasionally restart when a call is attempted.
N/A
TANDBERG Border Controller interoperability: if a TANDBERG Border Controller is
configured as a server in a traversal relationship with a Cisco VCS running X3.0 or newer,
then it is recommended that the Border Controller be upgraded to Q6.1. If the Border
Controller is not upgraded, it may occasionally restart when a call is attempted.
configured as a server in a traversal relationship with a Cisco VCS running X3.0 or newer,
then it is recommended that the Border Controller be upgraded to Q6.1. If the Border
Controller is not upgraded, it may occasionally restart when a call is attempted.
69881
TURN server port configuration: if the port of the TURN server is changed while the
TURN server is running, then the TURN server must be restarted before the port change
takes effect. This can be achieved by turning TURN services Off and then On again from
the TURN configuration page.
TURN server is running, then the TURN server must be restarted before the port change
takes effect. This can be achieved by turning TURN services Off and then On again from
the TURN configuration page.
79180
Out of date call and registration status: call and registration status displays can be out
of date if the status changes mid-call or mid-registration. The call/registration status
display is only updated when it ends. This means that the registration out-of-resources
status will not be reflected in until an MCU unregisters.
of date if the status changes mid-call or mid-registration. The call/registration status
display is only updated when it ends. This means that the registration out-of-resources
status will not be reflected in until an MCU unregisters.
85692
Truncated SNMP object value: the SNMP sysObjectID scalar MIB object value is being
returned truncated by the Cisco VCS. Instead of returning 1.3.6.1.4.1.5596.130.6.4.1 it
actually returns 1. This means that if Cisco TMS is configured to find devices using SNMP
(the default configuration) it will not discover the Cisco VCS. The workaround for this
when adding a system to Cisco TMS (via Systems > Navigator) is to expand the
Advanced Settings section and select the Discover Non-SNMP Systems check box.
actually returns 1. This means that if Cisco TMS is configured to find devices using SNMP
(the default configuration) it will not discover the Cisco VCS. The workaround for this
when adding a system to Cisco TMS (via Systems > Navigator) is to expand the
Advanced Settings section and select the Discover Non-SNMP Systems check box.
88084
Incorrect responses to attempts to communicate with the Cisco VCS on ports in
range 4369–4380: the Cisco VCS incorrectly responds with an ISAKMP message if a
device attempts to connect to a VCS port in the range 4369–4380.
range 4369–4380: the Cisco VCS incorrectly responds with an ISAKMP message if a
device attempts to connect to a VCS port in the range 4369–4380.
88239
Viewing web pages with IE8 in compatibility mode: there are display problems with
the Cisco VCS web interface when viewing web pages with IE8 in compatibility mode.
The workaround is to switch off IE8 compatibility mode.
the Cisco VCS web interface when viewing web pages with IE8 in compatibility mode.
The workaround is to switch off IE8 compatibility mode.
88493
Internal server error when unregistering and blocking an alias: if the VCS
Registration Policy is set to Deny List, use of the Unregister and block button on the
Registration details page will generate an internal server error message.
Registration Policy is set to Deny List, use of the Unregister and block button on the
Registration details page will generate an internal server error message.
The workaround is to manually add the alias to the Deny List and then use the
Unregister button on the Registration details page.
Unregister button on the Registration details page.
166997
VCS crashes and drops all calls, registrations, and connection when attempting an
interop call on VCS X6 or X6.1 using Movi 4.7 on OSX Mavericks.
interop call on VCS X6 or X6.1 using Movi 4.7 on OSX Mavericks.
The workaround / fix is to upgrade to VCS X7 or later.