- Title
- Contents
- Overview
- Cisco TelePresence System Operation (Sysop) Log Messages: A through C
- Cisco TelePresence System Operation (Sysop) Log Messages: D through L
- Cisco TelePresence System Operation (Sysop) Log Messages: M through R
- Cisco TelePresence System Operation (Sysop) Log Messages: S through W
- Cisco TelePresence System Messages: 201000 to 201119
- Cisco TelePresence System Messages: 201150 to 201801
- Cisco TelePresence System Operation (Sysop) Log Messages by Type
- MIBs, RFCs, and SNMP Trap Messages for the Cisco TelePresence System
S
Screen resolution (0) not supported
The screen resolution setting of the laptop/desktop computer is not supported.
Verify that the screen resolution is set to 1024 x 768. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
SelfView on a CTS-1300 (for left, right or center camera) Request
While in SelfView mode, a request to toggle between the left, center, or right screens was made.
SelfView request was not fulfilled
A problem occurred, and as a result, the SelfView request could not be fulfilled.
Retry the SelfView request. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Software downgrade denied for this CUCM device type
The software downgrade was denied for this Cisco Unified CM device type due to the software version being unsupported on the device type.
Software upgrade denied for this CUCM device type
The software upgrade was denied for this Cisco Unified CM device type.
Change the device type for this endpoint in Cisco Unified CM. You can specify a CTS model-specific device, for example, the CTS 1100 or CTS 3000.
Software upgrade skipped as secondary codec(s) unavailable
The software upgrade was skipped because the secondary codec(s) were unavailable.
Retry the software upgrade. If this condition persists, check the connections and the power to the secondary codec.
Started in [chars] mode Either CUCM or non-CUCM mode
The system started in the mode that is specified in the message text.
Check the Cisco TelePresence System configuration in Cisco Unified CM to ensure it is correct. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
{0} State Change To : {1}[{2}]
The device temperature state changed as indicated.
If the temperature reaches a critical state, cool down or power off the device.
Switch CTS Image from {0} to {1} on Slot {2}
System Provisioning: No response to SUBSCRIBE SIP message
The VCS did not respond to a Subscribe SIP message from the Cisco TelePresence system.
Check your configuration with the VCS to make sure that it is valid. The type of SIP message that was received should help you to determine the problem.
System Provisioning: Received {0} response to SUBSCRIBE SIP message
The VCS responded to a SIP message from the Cisco TelePresence system. The numeric message is specified in place of the {0}. Possible values are shown in Table 5-1 .
Check your configuration with the VCS to make sure that it is valid. The type of SIP message that was received should help you to determine the problem.
System Provisioning: Received unchanged configuration
This system successfully received the full configuration from the VCS, and has noted that there is no change between this configuration and the local copy of the last-received configuration.
System Provisioning: Received updated configuration
This system successfully received the full configuration from the VCS, and has noted the change between this configuration and the local copy of the last-received configuration.
T
Table configuration expected, but not found
The CTS supports audio table configurations, but no table configuration was provided.
Check that the table configuration in the CTS Administrative UI matches the actual table configuration.
Terminate call due to unsupported CTS (mux version [dec]) mux_version=[dec]
The remote Cisco TelePresence Multipoint Switch (CTMS) or Cisco TelePresence System (CTS) is running a older software version.
Upgrade the remote CTS or work with your CTMS administrator to upgrade the CTMS to a recommended compatible software version. For more information, refer to the Release Notes for CTMS or CTS.
The Release Notes for CTMS are located at the following URL:
http://www.cisco.com/en/US/products/ps7315/prod_release_notes_list.html
The Release Notes for CTS are located at the following URL:
http://www.cisco.com/en/US/products/ps8332/prod_release_notes_list.html
Terminate call: not enough remote bandwidth
remote_topology=[dec]
The bandwidth that is offered in the Session Initiation Protocol (SIP) Session Description Protocol (SDP) is below the acceptable bandwidth. This bandwidth is calculated on the basis of the remote topology and the type of Cisco TelePresence system.
Check the bandwidth settings in Cisco Unified CM to ensure that they are adequate. If this conditions persists, work with your network administrator to determine if this condition is transient or longer term, and take the appropriate action.
Terminated call due to DSP failure
The call terminated because of a digital signal processor (DSP) issue. The hardware should reset.
If this condition persists, turn the hardware off then back on again.
Terminated call due to DSP failure on remote
The call terminated because of a digital signal processor (DSP) issue on the remote endpoint.
Determine the problem that occurred on the remote endpoint. if you need further assistance, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Terminated call due to incompatible software versions
An endpoint that does not support interoperability has joined a Cisco TelePresence Multipoint System (CTMS) call that has interoperability enabled. The call is rejected with a cause code of FACILITY_REJECTED (29). This condition can occur if the endpoint is running a Cisco TelePresence System (CTS) software version that is older than 1.3.
Upgrade the CTS software on the endpoint to a version that supports interoperability. Remember to check the Software Compatibility Information for the Cisco TelePresence System to ensure that the CTS software version you select is compatible with the other software running in your CTS topology.
Terminated call due to network congestion
The remote endpoint terminated the call because of network congestion.
Work with your network administrator to determine if this condition is transient or longer term, and take the appropriate action.
Terminated call due to resources unavailable
The remote endpoint terminated the call because a resource was unavailable.
Determine the problem that occurred on the remote endpoint. If you need further assistance, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Terminated call due to security mismatch
Terminated call due to security mismatch after add-in
A nonsecure audio device attempted to join a a secure multipoint conference by using audio add-in. The audio call could not be added in to the Cisco TelePresence System because the security status between the two calls does not match. The nonsecure audio call is dropped.
Either change the security of the multipoint conference to best-effort, or configure the device that is designated for the audio add-in as a secure device. In addition, if the audio device is a Cisco Unified IP Phone and the version of Cisco Unified CM is 6.x or older, ensure that the Cisco Unified IP Phone and the Cisco TelePresence System are on the same Cisco Unified CM cluster.
The [left | center | right] TelePresence screen was left in Self View mode. The system returned the screen to normal mode.
The indicated TelePresence screen was left in Self View mode. The system detected this condition, and returned the screen to normal mode.
The conference control connection to the CTMS or TS is restored for meeting ID {0}
The conference control connection to the CTMS or TS was lost for meeting ID {0}
The conference control connection has been lost.
Work with your network administrator to determine if there are network connectivity issues to the CTMS or TS.
The phone interface configuration is invalid
The phone XML specification identifier (XSI) interface configuration is invalid.
Check the phone configuration in Cisco Unified CM to ensure that it is correct. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
The presentation has been negotiated to 1 FPS
The Cisco TelePresence System will receive the speed of the presentation at 1 frame per second (FPS).
The presentation has been negotiated to 5 FPS
The Cisco TelePresence System will receive the speed of the presentation at 5 frames per second (FPS).
The presentation has been negotiated to 30 FPS
The Cisco TelePresence System will receive the speed of the presentation at 30 frames per second (FPS).
The presentation has been negotiated to 30 & 5 FPS
The Cisco TelePresence System will receive the speed of the presentation at both 30 and 5 frames per second (FPS).
The Presentation Negotiated to 5 FPS Receive
The Cisco TelePresence System will receive the presentation at 5 frames per second (FPS).
The Presentation Negotiated to 30 FPS Receive
The Cisco TelePresence System will receive the speed of the presentation at 30 frames per second (FPS).
The Presentation Negotiated to 30 FPS Transmit
The Cisco TelePresence System will transmit the presentation at 30 frames per second (FPS).
The user interface firmware version (XSI) running on the Cisco TelePresence System phone is no longer supported.
The phone is using the XML specification identifier (XSI) user interface, which is no longer supported.
Check the Software Compatibility Information for the Cisco TelePresence System to ensure that the software for your CTS options, for example, the CTMS, CTRS, and so on, are compatible. If one or more of the devices are not compatible, work with the appropriate member of your technical support team to upgrade the software on those devices. You can also upgrade the older XSI user interface to the Enhanced Phone User Interface (MIDlets).
This CTS version does not support this bandwidth capability. Please contact system administrator
TP Type=[dec] Remote Topo=[dec] Local BW=[dec] Remote BW=[dec] Negotiated BW=[dec] Presentation Bw=[int]
The network bandwidth was negotiated, and the system changed to the new bandwidth.
Transfer of file {0} successful
The transfer of the indicated file from the CTS to the remote host was successful.
Transfer of file {0} unsuccessful: {1}
The transfer of the indicated file from the CTS to the remote host was unsuccessful.
Change the External CTS Log Destination setting in the Cisco Unified CM for this endpoint.
Trap destination matching same version already exists
U
Unable to allocate media port, resource clean up started
There is a media port leak in the system. A recovery process has started to clean up the unused ports.
Collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to allocate RTP ports
Unable to allocate the Real-time Transport Protocol (RTP) port.
If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to allocate video media port
The call service component cannot allocate the video port. This problem can occur when there is a leak in the resource usage.
No action is required. The call service will find the leak and reuse the port.
Unable to connect to Cisco Unified CM.
The Transport Layer Security (TLS) client connection to Cisco Unified CM could not complete the handshake.
Verify that both sides of the connection have valid certificates. For example, use tcpdump to capture the ethereal trace during the handshake and check the error code.
Unable to convert CUCM name [chars] to IP -
The system could not resolve the name provided by Cisco Unified CM to an IP address. The system will attempt to use the configured TFTP IP address.
Work with the appropriate member of your technical support team to ensure that the Domain Name System (DNS) configuration for the CTS is correct.
Unable to detect camera. Calls cannot be made or received. Ensure all camera cables are plugged in and working
Indicates that the camera is not detected. Calls cannot be made or received.
Verify that all camera cables are plugged in and working. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to determine operating mode
The call service is not available because the TFTP configuration file could not be read.
If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to find matching certificate for {0}
The received Cisco Unified CM certificate did not match any certificates in the Certificate Trust List (CTL) file.
Verify that the Cisco Unified CM certificate is included in the CTL file. For example, if the CTL file is from another Cisco Unified CM server, remove the CTL file. Or, if the Cisco Unified CM certificate accidentally regenerated, rerun the Cisco Unified CM CTL client to regenerate the CTL file.
Unable to load calandar meeting information
Cisco Touch device failed to load the calendar for scheduled meetings.
Verify that the file /nv/state/SRCalendar exists on the CTS. Verify that CTS has read access to the file.
Unable to load certificate file (0)
Unable to load manufacturing installed certification (MIC) or locally significant certificate (LSC).
Unable to load private key file (0)
Unable to load the private key file for the LSC or MIC.
Verify that the private key file for the LSC or MIC is valid.
Unable to log call records for CTS-Manager
The log file could not be opened, and as a result, the call data record could not be maintained.
Unable to parse CUCM configuration
The Cisco Unified CM configuration could not be parsed.
Restart the calling services. If this condition persists, contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to read CUCM configuration file
The calling services could not be started because it could not read the Cisco Unified CM configuration file.
Take one or more of the following actions:
1.
Verify that the Cisco TelePresence System (CTS) is using the correct Cisco Unified CM IP address by checking the IP address in the CTS Administration interface.
2. Work with your network administrator to verify the network connection between the CTS and the Cisco Unified CM.
3. Make sure that the CTS device has been created in the Cisco Unified CM with the correct MAC address.
4. If the problem persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to read Cisco Unified CM configuration
The Cisco Unified CM configuration is not readable.
Restart the calling services. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Unable to receive video from remote endpoint {0}. Blank screen will be observed during this time.
The CTS has received an invalid video resolution from the remote endpoint, and has downgraded video image resolution, but the remote endpoint has not changed its video resolution.
Unable to resolve CUCM IP from TFTP server [chars]
The system could not resolve the Cisco Unified CM IP address from the TFTP server.
Work with the appropriate member of your technical support team to ensure that the DNS configuration of the CTS is correct.
Unable to resolve Cisco Unified CM hostname
The Cisco Unified CM hostname/IP address could not be resolved.
Work with the appropriate member of your technical support team to ensure that the DNS configuration of the CTS is correct.
Unable to resolve Cisco Unified CM IP address, using TFTP Server IP address: {0}
The Cisco Unified CM IP address cannot be resolved. The IP address of the TFTP server is used instead.
Work with the appropriate member of your technical support team to ensure that the DNS configuration of the CTS is correct.
Undefined media port range in Cisco Unified CM. Default to [{0},{1}]
The media port range is not defined in Cisco Unified CM. The default range is used instead.
Configure the media port range in Cisco Unified CM. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Cisco Unified CM hostname/IP address is not configured
Unsupported signal of [chars]
The connected presentation device is not supported.
Make sure that your presentation device is set at a resolution of 1024x768 pixels.
UnSupported version of Endpoint detected in a call, the call may become non-secure
An endpoint that is running Cisco TelePresence System Release 1.3 software is participating in a conference with endpoints that are running either Cisco TelePresence System release 1.4 or 1.5 software. Due to the differences in SSL versions, the call cannot be set up as a secure call and will be set up as a nonsecure call.
To create a secure conference, make sure that all endpoints are running Cisco TelePresence System release 1.4 or later. If required, upgrade to a later software release.
Unsupported video resolution received from remote end point {0}. Video resolution will be reduced from {1} to {2}. A blank screen may be observed for a short time while the video stream is reduced.
The CTS has performed a video resolution downgrade because an invalid resolution was received from the remote endpoint.
Upgrade unsuccessful: Could not connect to host
A connection to the host could not be established, and as a result, the upgrade was unsuccessful.
Make sure that the codecs are connecting properly. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Upgrade unsuccessful: Could not save file
The file could not be saved because the /tmp directory might not have enough space.
Restart the CTS. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Upgrade unsuccessful: File not found on host
The CTS image file was not found on the TFTP server, and as a result, the upgrade was unsuccessful.
Upgrade unsuccessful: File security violation
A file security violation occurred, and as a result, the upgrade was unsuccessful.
Make sure that a valid file security scheme has been implemented. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Upgrade unsuccessful: File transfer timeout
The file transfer timed out, probably because of a communication problem with the TFTP server, and as a result, the upgrade was unsuccessful.
Retry the upgrade. If this condition persists, check the network status of the TFTP server.
Upgrade unsuccessful: File type invalid
The file type was invalid, and as a result, the upgrade was unsuccessful.
Verify that the file is on the TFTP server, and that the file is a CTS image.
Upgrade unsuccessful: Incorrect checksum
An incorrect checksum was received, and as a result, the upgrade was unsuccessful.
Upload the CTS image again, and retry the upgrade. If this condition persists, collect the CTS log files, then obtain a valid software image by contacting the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Upgrade unsuccessful: Invalid host name
The retrieval of the new CTS image, and hence, the upgrade was unsuccessful because an incorrect hostname was specified or could not be resolved.
Upgrade unsuccessful: Invalid operation
An software issue occurred, and as a result, the upgrade was unsuccessful.
Collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Upgrade unsuccessful: Software does not support current hardware
The CTS hardware and software are incompatible, and as a result, the upgrade was unsuccessful.
Check the Software Compatibility Information for the Cisco TelePresence System to determine the CTS software versions that are compatible with the CTS hardware, and upgrade the software or hardware accordingly.
Upgrade unsuccessful: Unable to transfer file
A file could not be transferred, and as a result, the upgrade was unsuccessful.
Retry the file transfer. If this condition persists, work with your network administrator to determine if this condition is transient or longer term, and take the appropriate action.
Upgrade unsuccessful: Unspecified
The upgrade was unsuccessful for an unknown reason.
- Retry the upgrade.
- Work with the appropriate member of your technical support team to determine the status of the TFTP server.
- If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
V
Video call ended due to security mismatch from non-secure audio add-in
The add-in call was disconnected because the audio/video call to the secured multipoint call was not allowed to downgrade to a non-secured state.
Work with your CTMS administrator to verify that the security configuration on the CTMS is correct. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Video driver not responding ({0} codec)
The call ended because the video driver was not responding.
Retry the call. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Video driver successfully reloaded on {0} codec
Video DSP buffer overflowed ({0} codec)
The call ended because the video DSP buffer overflowed.
Retry the call. If this condition persists, collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
W
WARNING= No valid Manufacturing Installed Certificate found Secure mode operation may not be possible
An invalid manufacturing installed certificate was found for a secured endpoint.
Collect the CTS log files, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Feedback