Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Open issues
Cisco TelePresence Video Communication Server Software Release Notes (X8.1.2)
Page 13 of 27
Identifier
Description
CSCuh78199 Symptom: Multiway conference already established between three endpoints (two CUCM and
one VCS hosted). An additional CUCM user calls the conference initiator on the VCS but cannot
be joined to the conference.
be joined to the conference.
Workaround: None.
CSCuh98112 Symptom: When an endpoint dials to the internet, it sends its private IP to Cisco side in the SDP
and hence media fails. When you force the call through the VCS, DNS returns port 5061 and
5060 for cisco.com, however 5061 is disabled on the firewall. It says TCP Connection failed for
5061 and never falls back to TCP. In another test, we disabled TLS on the VCS altogether, in this
case the VCS just reports TLS not active and rejects the call with 408 Request timeout.
5060 for cisco.com, however 5061 is disabled on the firewall. It says TCP Connection failed for
5061 and never falls back to TCP. In another test, we disabled TLS on the VCS altogether, in this
case the VCS just reports TLS not active and rejects the call with 408 Request timeout.
Conditions: VCS not falling back to TCP when it cannot establish connection with TLS.
Workaround: Turn on 5061 on the firewall and enable TLS on VCS.
Table 2: Issues resolved in X8.1 (continued)
Open issues
.
Limitations
Unsupported features (general)
n
DTLS is not supported through the VCS Control/VCS Expressway; attempts to make secure calls will fail
n
SIP Early Media
n
SIP KeyPad Markup Language (KPML)
n
Audio calls may be licensed as video calls in some circumstances. Calls that are strictly audio-ONLY
consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as
the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.
consume fewer licenses than video calls. However, when audio calls include non-audio channels, such as
the iX channel that enables ActiveControl, they are treated as video calls for licensing purposes.
Unsupported Jabber features when using mobile and remote access
n
Directory access mechanisms other than UDS
n
Certificate provisioning to remote endpoints e.g. CAPF
n
File transfer (except when operating in hybrid Webex mode)
n
Deskphone control (QBE/CTI)
n
Additional mobility features including DVO-R, GSM handoff and session persistency
n
Self-care portal
n
Support for Jabber SDK
n
Shared lines are supported in a limited way. Multiple endpoints can share a line but in-call features (like
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.
hold/resume) only work on the first endpoint that answers. Endpoints sharing the line may not correctly
recognise the state of the call.