The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter contains information about the following special Cisco TelePresence features that can be configured with command-line interface (CLI):
This section describes the procedure for capturing a still image of the Cisco TelePresence System (CTS) camera room view for troubleshooting purposes:
This troubleshooting feature allows you to create a still image of the meeting room environment exactly as seen from the CTS camera in loopback mode. This information in the form of a.bmp image file is then submitted with the system logs for use in installation verification, camera alignment, and further troubleshooting activities associated with a normal installation or a service request. When you initiate the tool using command-line interface (CLI), the system sends a confirmation pop-up in the SSH command window, which you can accept (allow capture) or decline (no capture will be made).
Note Before running this tool to create still images from the CTS camera, it is required of the initiating party to acquire proper authorization from the customer and/or manager of the facility. A verbal authorization should concede to the creation of still images depicting the environment exactly as seen from the CTS camera to be provided in the system logs for use in installation verification, camera alignment, and further troubleshooting activities associated with a normal installation or a service request. These images may be provided to Cisco Systems Inc., for the same purpose, but would not otherwise be distributed for any reason or purpose and are protected between these parties by non disclosure.
Each capture request takes approximately 3 seconds and only one capture is allowed at a time. New video captures overwrite any earlier captures. If you request a capture while a prior request is already in progress, a message appears letting you know that a capture is already in progress. The entire capture process, including downloading to the logs, can take up to 6 seconds.
If one or more requests to get logs come into CTS while the logs are already being collected, subsequent requests will be queued and all requesters will get the capture.bmp files that they requested.
Tip Avoid interrupting the troubleshooting session while the capture is in progress. If you do click away, the capture will proceed and will be stored. The completed capture is included in the log files that can later be downloaded.
Avoid troubleshooting while in a call.
To turn on the camera image capture tool using CLI, follow these steps:
Step 1 Initiate an SSH session.
Step 2 Stop the Call Control Agent (CCA) on the CTS by entering the following command:
Step 3 Turn on camera loopback by entering the following command:
Step 4 Initiate the screen capture tool by entering the following command:
The prompt and legal agreement pop-up appears, as shown in the following example:
Step 5 Select either yes or no. If you select yes, a.bmp will be generated and saved on your system (for example, /var /log/cli/capture/screen-<hostname>.bmp) where hostname is the codec hostname. Errors or successful captures are logged in syslog messages.
Step 6 Generate your log file by entering the following command:
Step 7 Download your log file by entering the following command:
Tip Alternately, you can download your log files from the CTS administration interface by going to Troubleshooting > Log Files > Log Files. The capture.bmp (~6MB) will be removed from your system as soon as the system log capture has been created (even if the log capture file has not been gzipped or downloaded).