Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Resolved caveats
Cisco TelePresence Video Communication Server X7.2.3 Software Release Notes
Page 25 of 50
Identifier
Summary
Conditions: This can occur if the database is taking too long to respond, and the license is
eventually allocated after the caller has timed out trying to set up the call.
Workaround: These allocated licenses can be cleared by restarting the VCS.
eventually allocated after the caller has timed out trying to set up the call.
Workaround: These allocated licenses can be cleared by restarting the VCS.
CSCty97430
Symptoms: Calls and other SIP traffic failing. Lync servers not able to communicate with
B2BUA.
Conditions: This can be seen if B2BUA has used up all 20 TCP connections for SIP traffic. To
check the current number of active TCP connections in use by the B2BUA, run the command
'netstat -anp | grep ESTABLISHED | grep /ivy | grep -v :127.0.0.1:4370'
from a root SSH shell on the B2BUA VCS.
Workaround: Reduce the number of Lync hosts communicating with B2BUA, for example by
routing all Lync to VCS traffic through a single Director server.
Additional Information: None.
B2BUA.
Conditions: This can be seen if B2BUA has used up all 20 TCP connections for SIP traffic. To
check the current number of active TCP connections in use by the B2BUA, run the command
'netstat -anp | grep ESTABLISHED | grep /ivy | grep -v :127.0.0.1:4370'
from a root SSH shell on the B2BUA VCS.
Workaround: Reduce the number of Lync hosts communicating with B2BUA, for example by
routing all Lync to VCS traffic through a single Director server.
Additional Information: None.
CSCtz35304
Scenario: An H.323 MCU contains a SIP endpoint in the conference. If the SIP endpoint gets
its network connection disconnected, a frozen picture remains forever on the conference.
Conditions: A SIP/H.323 interworked call is never torn down at the H.323 end despite 408
Request Timeout messages being generated.
Workaround: None, although non-interworked calls will not be affected.
its network connection disconnected, a frozen picture remains forever on the conference.
Conditions: A SIP/H.323 interworked call is never torn down at the H.323 end despite 408
Request Timeout messages being generated.
Workaround: None, although non-interworked calls will not be affected.
CSCua02807
Symptoms: The VCS loses its connection to Active Directory (identified by running "net ads
testjoin" on the root command line) and users cannot be authenticated with NTLM.
Conditions: This will occur if an AD server does not respond to a machine account password
change request within 10 seconds.
Workaround: Re-join the domain with the "domain_management" command as root. A fix to
disable machine password refreshes will be developed.
Additional info: Note that the NTLM web page does not show the correct join status in this
scenario. This is addressed by CSCty38860.
testjoin" on the root command line) and users cannot be authenticated with NTLM.
Conditions: This will occur if an AD server does not respond to a machine account password
change request within 10 seconds.
Workaround: Re-join the domain with the "domain_management" command as root. A fix to
disable machine password refreshes will be developed.
Additional info: Note that the NTLM web page does not show the correct join status in this
scenario. This is addressed by CSCty38860.
CSCua11868
Symptom: When calling from VCS to OCS/Lync via B2BUA, B2BUA removes ";user=phone"
from the request-URI.
Conditions: None.
Workaround: None.
from the request-URI.
Conditions: None.
Workaround: None.
CSCud58380
Symptom: Security Issue in Apache. Vulnerabilities CVE-2012-0883, CVE 2012-0053, CVE
2012-0031, and CVE 2012-0021 apply to Apache version 2.2.21 found in Cisco VCS version
X7.1.
Conditions: None.
Workaround: Upgrade to Cisco VCS X7.2.x
Additional Information: Cisco VCS version X7.2.x runs Apache version 2.4.2 which resolves
these issues.
2012-0031, and CVE 2012-0021 apply to Apache version 2.2.21 found in Cisco VCS version
X7.1.
Conditions: None.
Workaround: Upgrade to Cisco VCS X7.2.x
Additional Information: Cisco VCS version X7.2.x runs Apache version 2.4.2 which resolves
these issues.
Resolved in X7.1
Identifier
Summary
CSCtt13556
When a new policy service is created or modified its status defaults to Active:
Symptom: when a policy service is created or modified its status defaults to Active. It can
remain as Active for 30 seconds - long enough to convince the user that it really is active, even
if it subsequently fails.
Workaround: after creating or modifying a policy service, wait 30 seconds and then refresh the
policy services page.
Symptom: when a policy service is created or modified its status defaults to Active. It can
remain as Active for 30 seconds - long enough to convince the user that it really is active, even
if it subsequently fails.
Workaround: after creating or modifying a policy service, wait 30 seconds and then refresh the
policy services page.
CSCtx34916
Duplicate of CSCtx34918.
CSCtr80175
Cisco VCS Starter Pack Express and remote authentication of login account credentials
requires lower case usernames: when setting up user (FindMe) accounts you must enter the
account usernames in lower case. If usernames are created with mixed or upper case the user
will not be able to log in to the Cisco VCS. Note that passwords are case sensitive.
This issue applies only if you have a Cisco VCS Starter Pack Express and are using remote
requires lower case usernames: when setting up user (FindMe) accounts you must enter the
account usernames in lower case. If usernames are created with mixed or upper case the user
will not be able to log in to the Cisco VCS. Note that passwords are case sensitive.
This issue applies only if you have a Cisco VCS Starter Pack Express and are using remote