Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Resolved caveats
Cisco TelePresence Video Communication Server X7.2.2 Software Release Notes
Page 21 of 50
Identifier
Summary
Conditions: This will occur if the log rotation program fails, and the log files grow to fill up
/var/log.
Workaround: Delete the non-rotated log files in /var/log, or move them out of the way to
/mnt/harddisk.
/var/log.
Workaround: Delete the non-rotated log files in /var/log, or move them out of the way to
/mnt/harddisk.
CSCud24211
Symptom: Cisco TelePresence Video Communication Server (VCS) may report an early fan
"Hardware Failure" alarm condition that does not impact the server.
Condition: A VCS running a release prior to X7.2.1 will report a hardware failure alarm if a
single fan reports a speed below 7670 RPMs. The impact of this threshold is that fan
fluctuations that do not impact the functionality of the server have led to units being
prematurely replaced.
Starting in X7.2.1, new alarms values based upon extensive testing have been implemented.
Workaround: For systems running with releases prior to X7.2.1, you can safely ignore the
alarm if the VCS displays only one fan alarm message for a single fan. Customers should
monitor such alarms manually.
The VCS includes temperature alarms that are raised if the VCS reaches an unsafe
temperature.
Additional Information: You can log in to the VCS as root and run the "sensors" command
to get more detailed information on system fans and temperature.
"Hardware Failure" alarm condition that does not impact the server.
Condition: A VCS running a release prior to X7.2.1 will report a hardware failure alarm if a
single fan reports a speed below 7670 RPMs. The impact of this threshold is that fan
fluctuations that do not impact the functionality of the server have led to units being
prematurely replaced.
Starting in X7.2.1, new alarms values based upon extensive testing have been implemented.
Workaround: For systems running with releases prior to X7.2.1, you can safely ignore the
alarm if the VCS displays only one fan alarm message for a single fan. Customers should
monitor such alarms manually.
The VCS includes temperature alarms that are raised if the VCS reaches an unsafe
temperature.
Additional Information: You can log in to the VCS as root and run the "sensors" command
to get more detailed information on system fans and temperature.
Resolved in X7.2
Identifier
Summary
CSCty97265
Symptoms: A H323/SIP interworked G729 audio call may drop after the first session refresh.
Conditions: Offer/answer in H323/SIP interworked case may not send G729 capability in
SDP re-invite (at session refresh) since G729 can be signaled multiple times in H323 but only
once in SDP.
Workaround: Use SIP only.
Conditions: Offer/answer in H323/SIP interworked case may not send G729 capability in
SDP re-invite (at session refresh) since G729 can be signaled multiple times in H323 but only
once in SDP.
Workaround: Use SIP only.
CSCtr28842
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. Some of the call/registration status
information that is displayed is only updated when the call ends.
date if the status changes mid-call or mid-registration. Some of the call/registration status
information that is displayed is only updated when the call ends.
CSCts02660
Seconds since last refresh and Seconds to expiry do not update on the web interface:
the Seconds since last refresh and Seconds to expiry fields on the Registration details
web page do not get updated if a manual refresh of the web page is performed.
the Seconds since last refresh and Seconds to expiry fields on the Registration details
web page do not get updated if a manual refresh of the web page is performed.
CSCts31410
Phantom B2BUA calls appearing up in call status: the Call status page (Status > Calls >
Calls) can show phantom calls through the B2BUA. These are typically calls that were never
established. Such calls remain visible on the Call status page until the Cisco VCS is next
restarted.
Calls) can show phantom calls through the B2BUA. These are typically calls that were never
established. Such calls remain visible on the Call status page until the Cisco VCS is next
restarted.
CSCts25426
B2BUA does not support session timers (RFC 4028)
Symptoms: if a call is not properly cleared up with a BYE (either from the Cisco endpoint or
the MOC/Lync client) then it is not cleared from the Cisco VCS. It remains visible under call
status and if the Cisco VCS Expressway is used for TURN services the TURN session will
remain.
Symptoms: if a call is not properly cleared up with a BYE (either from the Cisco endpoint or
the MOC/Lync client) then it is not cleared from the Cisco VCS. It remains visible under call
status and if the Cisco VCS Expressway is used for TURN services the TURN session will
remain.
CSCtt17237
"sip:" prefix is not stripped before CPL search:
Symptoms: sip: and/or h323: prefixes to URIs are "unexpectedly" part of the pattern match
in CPL regexs. If deny rules are put in which do not explicitly cope with sip: or h323: prefixes
hackers may be able to make calls that would have been expected to have been denied.
Conditions: CPL regex rules in place to deny certain URIs, but do not explicitly include a test
that allows a sip: or h.323: prefix.
Workaround: for example, if the deny rule is to deny calls starting with a 9, instead of using a
regex of:
9(.*)
use:
(.*:)?9(.*)
Symptoms: sip: and/or h323: prefixes to URIs are "unexpectedly" part of the pattern match
in CPL regexs. If deny rules are put in which do not explicitly cope with sip: or h323: prefixes
hackers may be able to make calls that would have been expected to have been denied.
Conditions: CPL regex rules in place to deny certain URIs, but do not explicitly include a test
that allows a sip: or h.323: prefix.
Workaround: for example, if the deny rule is to deny calls starting with a 9, instead of using a
regex of:
9(.*)
use:
(.*:)?9(.*)