Cisco Cisco TelePresence MX700 Nota De Lançamento
Known limitations
Cisco TelePresence System C/EX/SX/MX Series Software Release Notes
Page 181 of 194
main video channel: 1280*768, 1280*800 and
1440*900.
1440*900.
N/A
TC4.x and later
If the ‘admin’ user is deleted, TMS will not be
able to manage the system. At the same time
the ‘admin’ user with a blank password will be
recreated during next reboot if no other user
with admin access exists.
able to manage the system. At the same time
the ‘admin’ user with a blank password will be
recreated during next reboot if no other user
with admin access exists.
N/A
TC4.x and later
xFeedback register Event/KeyDown will mask
the keys pressed on the remote control with a
‘*’. This is a security measurement to prevent
key logging from the remote control. The ‘*’ can
be used to detect that someone has pressed a
button on the remote control.
the keys pressed on the remote control with a
‘*’. This is a security measurement to prevent
key logging from the remote control. The ‘*’ can
be used to detect that someone has pressed a
button on the remote control.
CSCtr28267
TC4.X
OCS registration is broken in TC4.x. This issue
will not be fixed. The recommended usage is
to utilize a SIP trunk between VCS and OCS.
Direct registration is not supported.
will not be fixed. The recommended usage is
to utilize a SIP trunk between VCS and OCS.
Direct registration is not supported.
TC4.x
If you downgrade from TC4.x.x to any software
less than TC4.0.0 and have set the IP stack to
IPv6, the system will be unusable. The stack
will still think it should do IPv6 even though
there is no place to configure this in pre
TC4.0.0 code. The workaround will be to factory
reset the system. Even if the system does not
report any IP address, it will still have an IPv4
address. If you can’t get hold of this address,
you will have use RS-232 to restore the unit or
the procedure of using the power button (for
C20, EX60 and EX90).
less than TC4.0.0 and have set the IP stack to
IPv6, the system will be unusable. The stack
will still think it should do IPv6 even though
there is no place to configure this in pre
TC4.0.0 code. The workaround will be to factory
reset the system. Even if the system does not
report any IP address, it will still have an IPv4
address. If you can’t get hold of this address,
you will have use RS-232 to restore the unit or
the procedure of using the power button (for
C20, EX60 and EX90).
N/A
TC4.1.0
The Cisco TelePresence Touch screen does
not support up loadable layout families. Hence
you should not use the Cisco TC Console to
upload layouts to a system with the Cisco
Touch screen attached.
not support up loadable layout families. Hence
you should not use the Cisco TC Console to
upload layouts to a system with the Cisco
Touch screen attached.
N/A
Cisco TelePresence Touch
TC4.1.0/TT2.1.0
TC4.1.0/TT2.1.0
The Cisco TelePresence Touch must be
connected to the same subnet as the codec it is
pairing to.
connected to the same subnet as the codec it is
pairing to.
N/A
TMS 12.6 or below when upgrading to
TC4.0.0 and above
TC4.0.0 and above
Starting with TC4.0, the security model used by
the system changes which impacts compatibility
with existing installations of TMS. The
incompatibilities will result in:
1) Upgrading endpoints from a version less
than TC4.0 to a version TC4.0 or higher using
existing versions of TMS (12.x or lower) will
appear to have failed in TMS. Additionally, the
endpoint will not get the required release key
updated, so the endpoint will not be able to
make calls until a release key has been entered
into the system.
2) After an endpoint is upgraded to TC4.0 or
newer, the system will have an incorrect
username or password error message in TMS
and TMS will not be able to communicate with it
properly.
A workaround to restore communication
with TMS will be:
1) Restart the TMS server, or
2) Restart the TMS services, following the
below steps:
the system changes which impacts compatibility
with existing installations of TMS. The
incompatibilities will result in:
1) Upgrading endpoints from a version less
than TC4.0 to a version TC4.0 or higher using
existing versions of TMS (12.x or lower) will
appear to have failed in TMS. Additionally, the
endpoint will not get the required release key
updated, so the endpoint will not be able to
make calls until a release key has been entered
into the system.
2) After an endpoint is upgraded to TC4.0 or
newer, the system will have an incorrect
username or password error message in TMS
and TMS will not be able to communicate with it
properly.
A workaround to restore communication
with TMS will be:
1) Restart the TMS server, or
2) Restart the TMS services, following the
below steps: