Cisco Cisco TelePresence Video Communication Server Expressway 릴리즈 노트
Known limitations
Cisco TelePresence Video Communication Server X7.2.3 Software Release Notes
Page 37 of 50
Known limitations
Manufacturer
Equipment / Version /
Protocol
Protocol
Summary
Cisco
TelePresence Content
Server versions earlier
than S5.2
Server versions earlier
than S5.2
The SIP Standard registration refresh minimum setting introduced
in VCS X7.0 has a default value of 45 seconds.
Devices that request a value lower than the Standard registration
refresh minimum setting will result in the registration being rejected
with a 423 Interval Too Brief response.
Any SIP devices, such as the Cisco TelePresence Content Server,
that do not retry their registration request after receiving a 423
response will fail to register.
The workaround is to set the Standard registration refresh
minimum setting on the Cisco VCS to 30 seconds.
in VCS X7.0 has a default value of 45 seconds.
Devices that request a value lower than the Standard registration
refresh minimum setting will result in the registration being rejected
with a 423 Interval Too Brief response.
Any SIP devices, such as the Cisco TelePresence Content Server,
that do not retry their registration request after receiving a 423
response will fail to register.
The workaround is to set the Standard registration refresh
minimum setting on the Cisco VCS to 30 seconds.
Polycom
HDX 9000 / 3.0.0.2 and
3.0.4 / SIP
3.0.4 / SIP
An H.323 call routed via Cisco VCS will not connect when the
destination is Polycom HDX registering using SIP.
Polycom HDX does not send a response to a Cisco VCS interworked
SIP INVITE request (because it contains a “Session-Expires” header
without a “Supported: timer” extension).
Polycom have stated that this will be fixed in a future release.
destination is Polycom HDX registering using SIP.
Polycom HDX does not send a response to a Cisco VCS interworked
SIP INVITE request (because it contains a “Session-Expires” header
without a “Supported: timer” extension).
Polycom have stated that this will be fixed in a future release.
Lifesize
Room / 4.6.0 / SIP
An H.323 call routed via Cisco VCS will be disconnected when the
H.323 party puts the call on-hold.
Lifesize Room (SIP) incorrectly responds to Cisco SDP (media
capability) offer.
This issue is resolved in Lifesize Room version 4.8.3.
H.323 party puts the call on-hold.
Lifesize Room (SIP) incorrectly responds to Cisco SDP (media
capability) offer.
This issue is resolved in Lifesize Room version 4.8.3.
Lifesize
Room / 4.6.0 / SIP
A Movi SIP call routed via Cisco VCS will connect, however no video
will be seen on the Lifesize Room.
Lifesize Room (SIP) incorrectly responds to Cisco SDP (media
capability) offer.
This issue is resolved in Lifesize Room version 4.8.3.
will be seen on the Lifesize Room.
Lifesize Room (SIP) incorrectly responds to Cisco SDP (media
capability) offer.
This issue is resolved in Lifesize Room version 4.8.3.
Lifesize
Room / 4.6.0 / H.323
A C20 or E20 SIP call routed via Cisco VCS will connect, however no
video will be seen on the Lifesize Room.
C20 and E20 do not send media to Lifesize after call is connected.
This issue is resolved in Lifesize Room version 4.8.3.
video will be seen on the Lifesize Room.
C20 and E20 do not send media to Lifesize after call is connected.
This issue is resolved in Lifesize Room version 4.8.3.
Lifesize
Room / 4.6.0 and 4.8.3
/ H.323
/ H.323
A Movi SIP call routed via Cisco VCS will connect, however no video
will be seen on the LifeSize Room system if an HD camera is used
and the requested bandwidth is > 1MBps.
will be seen on the LifeSize Room system if an HD camera is used
and the requested bandwidth is > 1MBps.
TANDBERG
Gatekeeper
TANDBERG Gatekeeper interoperability: If a TANDBERG
Gatekeeper is configured as a client in a traversal relationship with a
Cisco VCS running X3.0 or later, then it is recommended that the
Gatekeeper be upgraded to N6.1. If the Gatekeeper is not upgraded,
it may occasionally restart when a call is attempted.
Gatekeeper is configured as a client in a traversal relationship with a
Cisco VCS running X3.0 or later, then it is recommended that the
Gatekeeper be upgraded to N6.1. If the Gatekeeper is not upgraded,
it may occasionally restart when a call is attempted.
TANDBERG
Border Controller
TANDBERG Border Controller interoperability: if a TANDBERG
Border Controller is configured as a server in a traversal relationship
with a Cisco VCS running X3.0 or later, then it is recommended that
the Border Controller be upgraded to Q6.1. If the Border Controller is
not upgraded, it may occasionally restart when a call is attempted.
Border Controller is configured as a server in a traversal relationship
with a Cisco VCS running X3.0 or later, then it is recommended that
the Border Controller be upgraded to Q6.1. If the Border Controller is
not upgraded, it may occasionally restart when a call is attempted.
Mozilla
Firefox Version 4.0 and
later
later
It is not possible to access the Cisco VCS HTTPS web interface in
Mozilla Firefox Version 4.0 using a raw IPv6 address. It is possible
with IPv4 addresses and in earlier versions of Firefox, or if a
hostname is used instead of the raw IPv6 address. This is being
tracked by Mozilla as bug 633001.
Mozilla Firefox Version 4.0 using a raw IPv6 address. It is possible
with IPv4 addresses and in earlier versions of Firefox, or if a
hostname is used instead of the raw IPv6 address. This is being
tracked by Mozilla as bug 633001.