Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Open caveats
Cisco TelePresence Video Communication Server X7.2.2 Software Release Notes
Page 33 of 50
Open caveats
The following issues currently apply to this version of the Cisco VCS.
Identifier
Summary
CSCtr80148
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.
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.
CSCtr77670
SIP DNS zone defaults to UDP: searches made through DNS zones use UDP for A record
lookups. They do this even if UDP is disabled at the SIP protocol level (on the SIP page).
However, if SIP UDP is disabled, the call will not connect.
This scenario is more likely to occur in new installations of X7 software which has SIP UDP
disabled by default.
The workaround is to enable SIP UDP.
lookups. They do this even if UDP is disabled at the SIP protocol level (on the SIP page).
However, if SIP UDP is disabled, the call will not connect.
This scenario is more likely to occur in new installations of X7 software which has SIP UDP
disabled by default.
The workaround is to enable SIP UDP.
CSCtq81698
VCS allows port overlap for disabled protocols in multi traversal zones:
Symptom: some messages will not traverse the traversal zone.
Conditions: two (or more) traversal zones are configured with identical port numbers for a
disabled protocol (such as SIP).
Workaround: configure unique port numbers for each traversal zone and protocol (H323,
SIP), even if the protocol is disabled.
Symptom: some messages will not traverse the traversal zone.
Conditions: two (or more) traversal zones are configured with identical port numbers for a
disabled protocol (such as SIP).
Workaround: configure unique port numbers for each traversal zone and protocol (H323,
SIP), even if the protocol is disabled.
CSCtu21769
Symptoms: Java vulnerabilities have been observed on Cisco VCS running X7.0.1.
Conditions: Discovered on a Cisco VCS X7.0.1.
Workaround: This issue is triggered by the Java application that is run on VCS for legacy
TMS Agent provisioning and legacy OCS Relay.
Customers using the provisioning feature should migrate to the new TMS Provisioning
Extension.
Customers using the legacy OCS Relay feature should use the Microsoft OCS/Lync B2BUA.
Additional Information: In X8 Java will be removed from the VCS product.
Conditions: Discovered on a Cisco VCS X7.0.1.
Workaround: This issue is triggered by the Java application that is run on VCS for legacy
TMS Agent provisioning and legacy OCS Relay.
Customers using the provisioning feature should migrate to the new TMS Provisioning
Extension.
Customers using the legacy OCS Relay feature should use the Microsoft OCS/Lync B2BUA.
Additional Information: In X8 Java will be removed from the VCS product.
CSCtw93381
Symptoms: No video on CTS endpoint on CUCM to VCS trunked call after hold/resume.
Conditions: None.
Workaround: None.
Additional Information: See RFC 3711.
Conditions: None.
Workaround: None.
Additional Information: See RFC 3711.
CSCty93737
Symptom: It is not possible to cluster a set of VCS peers using IPv6 addresses. The following
is seen on the clustering page:
' Unknown: aaaa:bbbb:cccc:dddd::eeee:46854 '
And an alarm is raised:
'Invalid cluster configuration. The cluster configuration is invalid - Raised - Warning - Check the
Clustering page and ensure that this system's IP address is included and there are no
duplicate IP addresses'
Conditions: VCS running in an IPv6 environment.
Workaround: No work around.
is seen on the clustering page:
' Unknown: aaaa:bbbb:cccc:dddd::eeee:46854 '
And an alarm is raised:
'Invalid cluster configuration. The cluster configuration is invalid - Raised - Warning - Check the
Clustering page and ensure that this system's IP address is included and there are no
duplicate IP addresses'
Conditions: VCS running in an IPv6 environment.
Workaround: No work around.
CSCty82416
Symptom: Resource usage page shows “Max (peak)” registrations of 2500 and there is a
“Capacity warning: the number of concurrent registrations has approached the licensed limit”
alarm. The warning remains present in VCS (acknowledged) and that triggers tickets in TMS.
Workaround: There is no command option to reset the “Max (peak)” counters and thus
remove the alarm. The only way to reset them from VCS is to restart or reboot the VCS.
“Capacity warning: the number of concurrent registrations has approached the licensed limit”
alarm. The warning remains present in VCS (acknowledged) and that triggers tickets in TMS.
Workaround: There is no command option to reset the “Max (peak)” counters and thus
remove the alarm. The only way to reset them from VCS is to restart or reboot the VCS.
CSCua72781 Symptoms: Remote ringing tone will not be heard on an endpoint registered to VCS
Expressway.
Conditions: Ringing tones sent as "Early Media" via SDP on a provisional response (183 or
180) will not be forwarded.
Workaround: None. Note this does not affect a call after it has been answered, only the audio
ringing tone.
Conditions: Ringing tones sent as "Early Media" via SDP on a provisional response (183 or
180) will not be forwarded.
Workaround: None. Note this does not affect a call after it has been answered, only the audio
ringing tone.
CSCua78996 Symptoms: The VCS web interface may become slow or non-responsive, H.323 endpoint/SIP