Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Open caveats
Cisco TelePresence Video Communication Server X6 Software Release Notes
Page 14 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.
85612
External policy:
If the Registration restriction policy is set to Policy service on the VCS configuration
> Registration > Configuration web page then any changes to this web page will result
in an incorrect password being set if the password field was not changed during the edit.
This can be worked around by always supplying the password in the field when making
changes or by using the CLI to make changes to these settings.
If the Call Policy is set to Policy service on the VCS configuration > Call Policy >
Configuration web page then any changes to this web page will result in an incorrect
password being set if the password field was not changed during the edit. This can be
worked around by always supplying the password in the field when making changes or
by using the CLI to make changes to these settings.
If the Registration restriction policy is set to Policy service on the VCS configuration
> Registration > Configuration web page then any changes to this web page will result
in an incorrect password being set if the password field was not changed during the edit.
This can be worked around by always supplying the password in the field when making
changes or by using the CLI to make changes to these settings.
If the Call Policy is set to Policy service on the VCS configuration > Call Policy >
Configuration web page then any changes to this web page will result in an incorrect
password being set if the password field was not changed during the edit. This can be
worked around by always supplying the password in the field when making changes or
by using the CLI to make changes to these settings.
N/A
Starter pack provisioning: when using the Cisco VCS Starter Pack, authentication must
be enabled in order for provisioning to work.
be enabled in order for provisioning to work.
N/A
Traversal port configuration: when configuring the traversal client and traversal server,
the ports needed for the SIP and H.323 communication must be modified on the Cisco
VCS traversal client and/or the traversal server side to match. This is expected behavior
and is required due to the ability for a single Cisco VCS to handle multiple traversal client
and server zones.
the ports needed for the SIP and H.323 communication must be modified on the Cisco
VCS traversal client and/or the traversal server side to match. This is expected behavior
and is required due to the ability for a single Cisco VCS to handle multiple traversal client
and server zones.
N/A
SIP neighboring over TLS: for the Cisco VCS to support SIP encryption over a Traversal
or Neighbor Zone, TLS must be configured as the transport type. When configuring TLS
on a neighbor zone the port needs to be manually changed from 5060 to 5061.
or Neighbor Zone, TLS must be configured as the transport type. When configuring TLS
on a neighbor zone the port needs to be manually changed from 5060 to 5061.
N/A
Case-sensitive logins: the username and password for user and administrator logins are
case-sensitive.
case-sensitive.
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 or on the LCD panel located
on the front of the Cisco VCS.
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 or on the LCD panel located
on the front of the Cisco VCS.
N/A
Call transfer: the Cisco VCS does not currently support the ability to transfer a call or dial
a call from the API of the Cisco VCS itself.
a call from the API of the Cisco VCS itself.
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.
75287
Encrypted Duo Video calls: if a call is encrypted and Duo Video is started and stopped
there is a possibility that when next started, the video will not be decoded (resulting in a
black screen). Repeated stopping and restarting Duo Video may restore Duo Video
operation. The workaround for this is to not have the call encrypted when doing Duo
there is a possibility that when next started, the video will not be decoded (resulting in a
black screen). Repeated stopping and restarting Duo Video may restore Duo Video
operation. The workaround for this is to not have the call encrypted when doing Duo