Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Resolved caveats
Cisco TelePresence Video Communication Server X7.2 Software Release Notes
Page 17 of 46
Resolved caveats
The following issues were found in previous releases and were resolved in X7.n.
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(.*)
CSCtu13020
Need to disable automatic DST timezone change for Russia from autumn 2011:
Symptoms: DST changes are wrong in some parts of Russia from autumn 2011.
Conditions: DST set to Russian area in an area where they have changed timezone rules.
Workaround: use a different timezone (for example Arabian GMT+4).
Additional Information: effective from autumn 2011, Russia has reduced the number of
timezones it uses. As part of this Russia is also changing the way it handles DST in some
areas as a way of converging areas together; the changed areas will stay with summer
timezone the whole year.
The changed areas will no longer adhere to the automatic DST change rules installed in the
VCS.
Symptoms: DST changes are wrong in some parts of Russia from autumn 2011.
Conditions: DST set to Russian area in an area where they have changed timezone rules.
Workaround: use a different timezone (for example Arabian GMT+4).
Additional Information: effective from autumn 2011, Russia has reduced the number of
timezones it uses. As part of this Russia is also changing the way it handles DST in some
areas as a way of converging areas together; the changed areas will stay with summer
timezone the whole year.
The changed areas will no longer adhere to the automatic DST change rules installed in the
VCS.
CSCtw75336
Symptoms: On dual network interface VCS, if the default gateway is in LAN 2's subnet, VCS
User Interface will show the gateway address as 127.0.0.1
Conditions: Dual network interfaces on VCS and default gateway in LAN 2 subnet
Workaround: Not a critical problem - this is a display only problem
User Interface will show the gateway address as 127.0.0.1
Conditions: Dual network interfaces on VCS and default gateway in LAN 2 subnet
Workaround: Not a critical problem - this is a display only problem