Cisco Cisco TelePresence MX700 Nota Di Rilascio
Open caveats
Cisco TelePresence System C/EX/SX/MX Series Software Release Notes
Page 98 of 194
Open caveats
Reference ID
Summary
CSCtz08306
If non-standard rate is set for default call rate, different rate is used instead of the
rate set when dialing via web or remote
rate set when dialing via web or remote
CSCua59516
Endpoint reflects wrong bandwidth info when connected to MCU 4200
CSCua84373
C-series receive dual channel as part of main video when MCU H.239 minimum
bitrate set as 512kbps
bitrate set as 512kbps
CSCub54863
SX20 Reboots when making or receiving a SIP call when system clock set to
1936.
1936.
CSCua08205
Cisco TelePresence Touch 8 may not respond properly to interaction on the
bottom row. NOTE: Some Touch 8 devices will still exhibit this behaviour after
upgrading TC 5.1.3. These panels are defective.
NOTE: This issue was resolved in TC5.1.3 but is reverted in TC5.1.4 due to
higher probability of false touch registrations in TC5.1.3 (CSCub65256)
bottom row. NOTE: Some Touch 8 devices will still exhibit this behaviour after
upgrading TC 5.1.3. These panels are defective.
NOTE: This issue was resolved in TC5.1.3 but is reverted in TC5.1.4 due to
higher probability of false touch registrations in TC5.1.3 (CSCub65256)
CSCty11069
Dual screen connected to an EX90 is black until you have shared presentation in a
call.
call.
CSCtz87452
MX, EX, E20, C and SX series endpoints can not use CUCM phone books with
numbers including white spaces.
numbers including white spaces.
CSCtz77758
SX20: 1680x1050 VGA input detected as 1400x1050
CSCtz78809
In some call scenarios, dual stream will not work in a C-series multisite call
involving MXP (VCS registered) and CUCM registered endpoints such as CTS/C-
series
involving MXP (VCS registered) and CUCM registered endpoints such as CTS/C-
series
CSCtz93712
SIP Presentation will fail when Polycom HDX calls a Cisco multisite endpoint.
Cisco endpoint becomes BFCP server and Polycom changes BFCP/TCP port in
re-invite without sending a new BFCP HELLO. Issue will be fixed by upgrading
Polycom to 3.0.5 which uses BFCP over UDP.
Cisco endpoint becomes BFCP server and Polycom changes BFCP/TCP port in
re-invite without sending a new BFCP HELLO. Issue will be fixed by upgrading
Polycom to 3.0.5 which uses BFCP over UDP.