Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Resolved caveats
Cisco TelePresence Video Communication Server X7.2.3 Software Release Notes
Page 20 of 50
Resolved in X7.2.1
Identifier
Summary
CSCub34963
Symptoms: On upgrade to X7.2, local users or members of a remote (Active Directory) group
may not be able to log in on the web interface of the VCS.
Conditions: If a remote administrator group and a local admin user have the same name, only
one will be permitted access to the VCS web interface.
Workaround: Rename the remote group or the local user. Access to the VCS will still be
permitted by one or the other way.
may not be able to log in on the web interface of the VCS.
Conditions: If a remote administrator group and a local admin user have the same name, only
one will be permitted access to the VCS web interface.
Workaround: Rename the remote group or the local user. Access to the VCS will still be
permitted by one or the other way.
CSCub66229
Symptom: TMS will not produce CDR data of type "Gatekeeper and VCS", and the log-web-
public.txt log file in TMS will contain entries similar to:
---> Tandberg.TMS.SystemAPI.OakPine.InvalidStateException: Expected to find <Legs>, but
instead found <EndTime>.
at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.AssumePositionedAtTag
(XmlReader reader, String tag)
at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.ProcessCall(XmlReader
reader)
at Tandberg.TMS.SystemAPI.OakPine.HttpFeedback.ProcessCallDisconnected(IXMLDoc
txasDoc, RoutableSystem system)
--- End of inner exception stack trace ---
TMS Version 13.2.1
Background: Because of a change in the XML feedback which the VCS sends to TMS for
events related to calls connecting and disconnecting, TMS is not able to properly interpret the
XML data provided by the VCS. Because of this, TMS is not able to generate CDR records
based on the feedback data provided by the VCS.
Workaround: There is currently no known workaround for this issue when running X7.2
software on the VCS. X7.1 and previous versions of VCS software are not affected by this
issue.
public.txt log file in TMS will contain entries similar to:
---> Tandberg.TMS.SystemAPI.OakPine.InvalidStateException: Expected to find <Legs>, but
instead found <EndTime>.
at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.AssumePositionedAtTag
(XmlReader reader, String tag)
at Tandberg.TMS.SystemAPI.OakPine.XMLFeedbackReader.ProcessCall(XmlReader
reader)
at Tandberg.TMS.SystemAPI.OakPine.HttpFeedback.ProcessCallDisconnected(IXMLDoc
txasDoc, RoutableSystem system)
--- End of inner exception stack trace ---
TMS Version 13.2.1
Background: Because of a change in the XML feedback which the VCS sends to TMS for
events related to calls connecting and disconnecting, TMS is not able to properly interpret the
XML data provided by the VCS. Because of this, TMS is not able to generate CDR records
based on the feedback data provided by the VCS.
Workaround: There is currently no known workaround for this issue when running X7.2
software on the VCS. X7.1 and previous versions of VCS software are not affected by this
issue.
CSCub31927
Symptom: Attempting to use Cisco Jabber for iPad with a Cisco VCS Starter Pack Express
results in the Jabber client not being able to register to the VCS Expressway.
Conditions: Must be attempting to register the Cisco Jabber for iPad to a Cisco VCS Starter
Pack Express with no Cisco TMS in play. Cisco Jabber for iPad tries to register with device
type "jabbertablet" which is unknown.
Workaround: No workaround available. Customer must deploy Cisco TMS solution in order to
user Cisco Jabber for iPad client.
results in the Jabber client not being able to register to the VCS Expressway.
Conditions: Must be attempting to register the Cisco Jabber for iPad to a Cisco VCS Starter
Pack Express with no Cisco TMS in play. Cisco Jabber for iPad tries to register with device
type "jabbertablet" which is unknown.
Workaround: No workaround available. Customer must deploy Cisco TMS solution in order to
user Cisco Jabber for iPad client.
CSCuc16057
Symptom: Some older versions of Polycom endpoints registered on VCS failed to establish
call after software upgrade to X7.2.
Conditions: The VCS strips/filters some terminalCapabilitySet items based on the vendor and
H.323 version. However, with X7.2 these terminalCapabilitySet messages sent to the Polycom
ViewStation are larger than it can cope with (capability related to H.239). The Polycom
ViewStation stops responding to call negotiation from VCS after the terminalCapabilitySet
message and the call terminates by call setup timeout on endpoint.
Workaround: Disable H.239 on calling device (far end endpoint, MCU, etc.).
call after software upgrade to X7.2.
Conditions: The VCS strips/filters some terminalCapabilitySet items based on the vendor and
H.323 version. However, with X7.2 these terminalCapabilitySet messages sent to the Polycom
ViewStation are larger than it can cope with (capability related to H.239). The Polycom
ViewStation stops responding to call negotiation from VCS after the terminalCapabilitySet
message and the call terminates by call setup timeout on endpoint.
Workaround: Disable H.239 on calling device (far end endpoint, MCU, etc.).
CSCub25632
Symptom: When using the VCS B2BUA, an MCU joining a conference may not be aware it is
an MCU and will join as a regular participant.
Conditions: This only occurs when the VCS B2BUA is in use to enforce encryption policy on
the participating call legs.
Workaround: Do not use the VCS B2BUA in these circumstances and instead manually verify
participant encryption status.
an MCU and will join as a regular participant.
Conditions: This only occurs when the VCS B2BUA is in use to enforce encryption policy on
the participating call legs.
Workaround: Do not use the VCS B2BUA in these circumstances and instead manually verify
participant encryption status.
CSCub68929
Symptoms: When a 9971 phone dials into a Cisco TelePresence Server meeting and does a
hold/resume for the second time, you get a black screen. The first hold/resume works fine (you
get video after resume), but any further hold/resumes result in a black screen.
hold/resume for the second time, you get a black screen. The first hold/resume works fine (you
get video after resume), but any further hold/resumes result in a black screen.
CSCua49125
Symptoms: When the VCS sends a SIP INVITE, the P-Asserted-Identity field does not contain
a display name. This results in no caller ID on the far end. Currently the PAI header will look
a display name. This results in no caller ID on the far end. Currently the PAI header will look