Cisco Cisco TelePresence MX700 Notas De La Versión
Known limitations
Cisco TelePresence System C/EX/SX/MX Series Software Release Notes
Page 86 of 194
2) Restart the TMS services, following the
below steps:
a) Log into the windows console of the TMS
server as a user with Windows Administrative
permissions.
b) Open the Services Control Panel (Control
Panel->Administrative Tools->Services).
c) For each service in the list below, select the
service from the Services list, and use the
restart icon or right-click->restart to restart the
service.
- World Wide Web Publishing Service
- TMSDatabaseScannerService
- TMSLiveService
- TMSSchedulerService
- TMSSNMPService
* Log into the TMS Web Interface, browse to
the system and do a ‘Force Refresh’. TMS
should communicate to the system properly and
the error message will clear.
* To minimize service abruption it will be
beneficial to upgrade all systems in one go,
avoiding following the above procedure for
every endpoints you upgrade. A future TMS
version will resolve this condition negating the
need to restart the services.
Workaround to restore the release keys:
* Once TMS has restored communication with
the systems, upgrade the units one more time.
This time TMS will be able to communicate with
the systems when they boot up and set the
release keys.
Note: Please read the resolved caveats
section Reference ID 85930 as well.
Note: The above issues are fixed for TMS
13.0
below steps:
a) Log into the windows console of the TMS
server as a user with Windows Administrative
permissions.
b) Open the Services Control Panel (Control
Panel->Administrative Tools->Services).
c) For each service in the list below, select the
service from the Services list, and use the
restart icon or right-click->restart to restart the
service.
- World Wide Web Publishing Service
- TMSDatabaseScannerService
- TMSLiveService
- TMSSchedulerService
- TMSSNMPService
* Log into the TMS Web Interface, browse to
the system and do a ‘Force Refresh’. TMS
should communicate to the system properly and
the error message will clear.
* To minimize service abruption it will be
beneficial to upgrade all systems in one go,
avoiding following the above procedure for
every endpoints you upgrade. A future TMS
version will resolve this condition negating the
need to restart the services.
Workaround to restore the release keys:
* Once TMS has restored communication with
the systems, upgrade the units one more time.
This time TMS will be able to communicate with
the systems when they boot up and set the
release keys.
Note: Please read the resolved caveats
section Reference ID 85930 as well.
Note: The above issues are fixed for TMS
13.0
CSCtr32348
TANDBERG PrecisionHD 1080p Camera
all SW versions.
all SW versions.
720p50, 720p30 and 720p25 output has no
CRC included for HD-SDI. Depending on the
device you connect the camera to, you may not
get video using this format. The Cisco C-Series
codecs will support these formats.
CRC included for HD-SDI. Depending on the
device you connect the camera to, you may not
get video using this format. The Cisco C-Series
codecs will support these formats.
N/A
Ver. TC2.1.0 and above
Startup scripts will not work with Windows end
of line. You must use Unix end of line to be able
to run multiple commands. Most editors have
the option to set which format to use. If you use
Notepad ++, you can set Unix format in the
Settings/Preferences menu.
of line. You must use Unix end of line to be able
to run multiple commands. Most editors have
the option to set which format to use. If you use
Notepad ++, you can set Unix format in the
Settings/Preferences menu.
N/A
Ver. Any
If you run cascaded cameras and the chained
cameras are running an old camera code, we
have seen that zoom only works when trying to
control the chained camera. The solution is to
cameras are running an old camera code, we
have seen that zoom only works when trying to
control the chained camera. The solution is to