C
Call authenticated message is displayed
Message Added to Release
1.5
Severity
Information not available
Explanation
This call is authenticated, and the security icon is displayed on the main screen.
Recommended Action
No action is required.
Call connected to [chars] remote_dn=[number]
Message Added to Release
1.5
Severity
Information not available
Explanation
A call from the indicated caller ID has been connected to the indicated remote directory number.
Recommended Action
No action is required.
Call downgraded to non-secure due to mismatched incoming and outgoing security mechanisms
Message Added to Release
1.8
Severity
Warning
Explanation
The CTS endpoints in the call are using different mechanisms to authenticate themselves. As a result, the security of the call has been downgraded to non-secure.
Recommended Action
Put the call on hold and then resume the call. If this condition persists, and a secure call must be made, work with your administrator to verify that the security configuration on the CTS and the remote endpoint. Alternatively, 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.
Call dropped due to incoming media issue ({0} codec)
Message Added to Release
1.9
Severity
Error
Explanation
The call has ended due to the reason shown in the system message.
Recommended Action
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.
Call ended due to 100 percent packet loss
Message Added to Release
1.6
Severity
Informational
Explanation
The call has ended because no packets have been received for the last 60 seconds.
Recommended Action
Collect the CTS log files as soon as possible, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Call ended due to bandwidth renegotiation timeout
Message Added to Release
1.7
Severity
Error
Explanation
During call setup, the CTS negotiates the minimum required bandwidth with the remote endpoint. After call setup, CTS renegotiates the bandwidth to accommodate for security, presentation, topology, and legacy overheads. One side of the call sends the renegotiation request, and the other side waits for arrival of the request. During the renegotiation, a timeout occurred while one of the sides waited for the renegotiation request to arrive.
Recommended Action
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.
Call ended due to inability to downgrade security
Message Added to Release
1.6
Severity
Error
Explanation
Two or more CTS endpoints were in a secured call when one of the endpoints (CTS-A) added a non-secure endpoint (CTS-C), for example, as an audio add-in. As a result, CTS-A sent a security downgrade request to the other endpoints that were in the secured call, in this case, CTS-B. However, CTS-B did not respond to this request in a timely manner.
Recommended Action
If secured calls must be made, 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.
Call ended due to incompatible media negotiated
Message Added to Release
1.7
Severity
Error
Explanation
The call was disconnected because one of the endpoints is an unsupported non-CTS endpoint, and the negotiation with this endpoint was unsuccessful.
Recommended Action
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.
Call ended due to incompatible software versions
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because the remote endpoint is running an older software version.
Recommended Action
Upgrade the remote endpoint software so that it is compatible with the software running on the other remote endpoints.
Call ended due to insufficient bandwidth
Message Added to Release
1.6
Severity
Error
Explanation
The call ended because of insufficient bandwidth.
Recommended Action
Work with your network administrator to check the network configuration. Check the bandwidth region settings in the Cisco Unified CM configuration. 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.
Call ended due to media service restarted
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because of a media component error. The call will be restarted.
Recommended Action
Verify that the cameras are properly connected. 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.
Call ended due to module reset. Module restarted.
Message Added to Release
1.6
Severity
Error
Explanation
The call ended because of a reset of the digital signal processor (DSP) firmware. The DSP module was restarted.
Recommended Action
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.
Call ended due to network congestion
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because packet loss is detected during the call.
Recommended Action
Work with your network administrator to determine the cause of the network congestion, and take the appropriate action.
Call ended due to packet loss exceeding 10 percent threshold
Message Added to Release
1.6
Severity
Error
Explanation
More than 10 percent packet loss was detected for more than 60 seconds, which caused the call to end and the bit rate to be downgraded to the lowest possible level.
Recommended Action
Work with your network administrator to determine if this condition is transient or longer term, and take the appropriate action. 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.
Call ended due to peer not authenticated during key exchange
Message Added to Release
1.8
Severity
Error
Explanation
The call has ended because one of the endpoints failed authentication during security setup.
Recommended Action
If this condition persists, work with your administrator to verify that the security configuration on the two endpoints. Alternatively, collect log files from the local and remote endpoints, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Call ended due to problem with remote endpoint
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because of a problem at the remote endpoint.
Recommended Action
If this condition persists, collect log files from the local and remote endpoints, and contact the Cisco Technical Assistance Center (TAC). For information on how to contact TAC, see the “Obtaining Technical Assistance” section.
Call ended due to remote DSP reset
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because the DSP of the remote endpoint was reset. This remote endpoint will recover, and the user can retry their call.
Recommended Action
Wait 1 minute, then verify that the remote endpoint is up and running. 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.
Call ended due to remote endpoint number not found
Message Added to Release
1.7
Severity
Error
Explanation
The call has ended because the remote endpoint number was not found.
Recommended Action
Take the following action:
-
Check the dial number configuration in Cisco Unified CM.
-
Make sure that the dialed number is routable by all instances of Cisco Unified CM in the path.
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.
Call ended due to remote endpoint resource not available
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because the remote endpoint resource was in use or not registered to Cisco Unified CM.
Recommended Action
Check the Cisco Unified CM configuration. 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.
Call ended due to security mismatch
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because the security level of the audio/video call was mismatched.
Recommended Action
Work with the CTMS administrator to check the CTMS security configuration. 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.
Call ended due to service unavailable
Message Added to Release
1.9
Severity
Error
Explanation
The call has ended because the CTS has received a service unavailable error.
Recommended Action
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.
Call ended due to unsupported protocol configuration
Message Added to Release
1.7
Severity
Error
Explanation
The call has ended because of incompatible protocols.
Recommended Action
Check the
Software
Compatibility Information for the Cisco TelePresence System
to ensure that the software running on your CTS products is compatible.
Call ended due to video quality configuration mismatch
Message Added to Release
1.6
Severity
Error
Explanation
The call has ended because of a video quality configuration mismatch. For example, the 720p endpoint cannot join the CTMS 1080p conference.
Recommended Action
Work with the CTMS administrator to check the CTMS static meeting configuration. 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.
Call entered preservation state due to interruption in call path. H/R not available for the remainder of the call. All other features are available.
Message Added to Release
1.7
Severity
Warning
Explanation
The call is in preservation state because communication with Cisco Unified CM is lost. No further call signaling messages can be exchanged. The Hold/Resume feature is not available for remainder of call.
Recommended Action
End the current call, and redial the same number to regain the hold/resume capabilities.
Call Manager hostname/ip address is not specified in configuration file
Message Added to Release
1.5
Severity
Information not available
Explanation
Cisco Unified CM is not configured. As a result, the calling services have stopped.
Recommended Action
Check the configuration of the Cisco TelePresence System, then restart the system.
Call nonsecure message is displayed
Message Added to Release
1.5
Severity
Information not available
Explanation
This call is a non-secure call, and the non-secure icon was displayed on the screen.
Recommended Action
No action is required.
Call, satellite message is displayed
Message Added to Release
1.5
Severity
Information not available
Explanation
A satellite endpoint is in a conference (either multipoint or point-to-point). All endpoints see this message, and it displays for new endpoints joining or performing a hold or resume action during the call.
Recommended Action
No action is required. Once the satellite endpoint has joined the conference, the call will remain in Satellite Mode whether the satellite endpoint remains for the duration of the call.
Call secured message is displayed
Message Added to Release
1.5
Severity
Information not available
Explanation
This call is a secure call, and the secure icon was displayed on the screen.
Recommended Action
No action is required.
Call service restarted due to media service not ready
Message Added to Release
1.5
Severity
Error
Explanation
The call service was restarted because the media component was restarted.
Recommended Action
Check the cabling between the codec and the cameras. 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.
Call services not available, unable to initialize phone interface
Message Added to Release
1.6
Severity
Error
Explanation
The call service is unavailable because the phone interface could not be initialized.
Recommended Action
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.
Camera cables are verified plugged in properly
Message Added to Release
1.6
Severity
Informational
Explanation
Indicates that overall, the camera is functioning properly.
Recommended Action
No action is required.
Camera Ethernet Status: (0)
Message Added to Release
1.6
Severity
Informational
Explanation
Indicates the status of the Ethernet connection to the camera. The status can be good or unknown.
Recommended Action
No action is required.
Camera is resetting. Calls cannot be made or received
Message Added to Release
1.6
Severity
Informational
Explanation
Indicates whether or not the camera is in the resetting state. Normally, the system resets the camera when it first comes online or when the call service is restarted.
Recommended Action
Wait for camera to reset before making calls.
Camera not detected ({0} codec)
Message Added to Release
1.6
Severity
Error
Explanation
The call ended because a camera was not detected by the indicated codec.
Recommended Action
Check the cabling between the codec and the cameras. 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.
Camera Power Status: (0)
Message Added to Release
1.6
Severity
Informational
Explanation
Indicates the power status of the camera, which can be one of the following:
Recommended Action
No action is required.
Camera synchronization inhibit option is enabled
Message Added to Release
1.6
Severity
Informational
Explanation
The camera synchronization inhibit option in the command-line interface (CLI) is enabled.
Recommended Action
No action is required.
Camera Video Cable Status: (0)
Message Added to Release
1.6
Severity
Informational
Explanation
Indicates the status of the video (DVI) cable that connects to the camera. The status can be one of the following:
-
Plugged-in
-
Loose
-
Unplugged
-
Unknown
Recommended Action
If the status is “loose” or “unplugged,” plug the cable in.
The status of “unknown” could indicate a third-party camera that is not supported by CTS. In this case, replace the unsupported camera with a supported camera.
Cannot connect to CMA or CMR process
callId=[inCallID] or codec_hostname=[codec hostname]
Message Added to Release
1.5
Severity
Information not available
Explanation
The system could not connect to the media services during initialization of a call.
Recommended Action
Restart the calling services. 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.
Cannot connect to CMA or CMR process. Exiting CCA, must restart. Retry attempts [dec]
Message Added to Release
1.5
Severity
Information not available
Explanation
The calling services could not connect to the media services and have reached the maximum number of retry attempts. The calling services process will exit and restart automatically.
Recommended Action
Restart the calling services. 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.
Cannot obtain phone information.
Message Added to Release
1.7
Severity
Error
Explanation
The phone information cannot be obtained.
Recommended Action
Verify that the phone is up and running.
CAPF operation unsuccessful: (0)
Message Added to Release
1.6
Severity
Error
Explanation
The Certificate Authority Proxy Function (CAPF) download or update from the CAPF server was unsuccessful. The “(0)” variable indicates the reason that the operation was unsuccessful.
Recommended Action
Check the Cisco Unified CM configuration; in particular, verify that the specified CAPF authentication string matches the configured string. Also check the security configuration. If the 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 Touch incomplete initialization; MAC addr {0}, IP addr {1}
Message Added to Release
1.8
Severity
Warning
Explanation
The Cisco Touch device did not initialize successfully.
Recommended Action
If the 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 Touch registers; MAC addr {0}, IP addr {1}
Message Added to Release
1.8
Severity
Informational
Explanation
The Cisco Touch device is successfully connected to the CTS.
Recommended Action
No action is required.
{0} clock status issue.
Message Added to Release
1.7
Severity
Error
Explanation
An issue exists with the camera clock.
Recommended Action
If this condition persists, turn the camera off then back on again.
Codec firmware upgrade is disabled
Message Added to Release
1.6
Severity
Error
Explanation
The codec firmware auto upgrade feature is disabled, and until it is re-enabled, you will not be able to upgrade the firmware.
Recommended Action
If you continue to get this message, 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.
Community already exists
Message Added to Release
1.6
Severity
Warning
Explanation
The specified SNMP community name already exists.
Recommended Action
Verify the community name for SNMP.
Compact flash integrity process returns {0}
Message Added to Release
1.7
Severity
Error
Explanation
An issue exists with the compact flash integrity process.
Recommended Action
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.
Conf Id [dec] received call drop from [chars] with error code = Endpoint does not respond to echo request
Message Added to Release
1.5
Severity
Information not available
Explanation
The endpoint did not respond to Cisco TelePresence Multipoint Switch (CTMS) heart beat messages. The endpoint is removed from the conference.
Recommended Action
Check the network connectivity to the endpoint. If you do not detect any problems with network connectivity, there might be inter-communication errors between the Cisco TelePresence System, the CTMS, and Cisco Unified CM. Since the issue can be with any of these components, collect the Cisco TelePresence System and Cisco Unified CM logs, and work with your CTMS administrator to collect CTMS logs, to determine the cause of the problem.
Config file rejected: (0)
Message Added to Release
1.6
Severity
Error
Explanation
The indicated Cisco Unified CM configuration file was rejected.
Recommended Action
Take this action:
-
Check the Cisco Unified CM configuration file.
-
Delete the Certificate Trust List (CTL) file, and re-register.
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.
Connected to (0)
Message Added to Release
1.6
Severity
Informational
Explanation
The call is successfully established with the remote endpoint directory number (DN).
Recommended Action
No action is required.
Connected to (0) at (1)
Message Added to Release
1.6
Severity
Informational
Explanation
Indicates the remote endpoint directory number (DN) and name.
Recommended Action
No action is required.
Connected to Cisco Unified CM but unable to obtain certificate
Message Added to Release
1.6
Severity
Error
Explanation
The Cisco Unified CM certificate was not received during the Transport Layer Security (TLS) handshake.
Recommended Action
Verify that Cisco Unified CM sent its certificate during the TLS handshake. For example, use tcpdump to capture the ethereal trace.
Connected to Cisco Unified CM but unable to verify client-side certificate.
Message Added to Release
1.6
Severity
Error
Explanation
The received Cisco Unified CM certificate did not pass validation against the Certificate Trust List (CTL) file.
Recommended Action
Verify that the Cisco Unified CM certificate is valid and included in the CTL file.
Connected to Cisco Unified CM but unable to verify server-side certificate
Message Added to Release
1.6
Severity
Error
Explanation
The received Cisco Unified CM certificate did not pass validation against the Certificate Trust List (CTL) file.
Recommended Action
Verify that the Cisco Unified CM certificate is valid and included in the CTL file.
{0} COS Current Priority: [{1}], Previous Priority: [{2}]
Message Added to Release
1.6
Severity
Informational
Explanation
The Class of Service (COS) quality of the audio call has changed. This message applies to incoming traffic. The “{0}” variable displays “audio,” the “[{1}]” variable indicates the current priority value, and the “[{2}]: variable indicates the previous priority value.
Recommended Action
No action is required.
Could not generate logs
Message Added to Release
1.8
Severity
Warning
Explanation
CTS was unable to generate the selected log file.
Recommended Action
Generate the selected log again.
CTL file rejected: (0)
Message Added to Release
1.6
Severity
Error
Explanation
The Certificate Trust List (CTL) file was rejected.
Recommended Action
Determine the cause of the CTL file rejection, and resolve the problem it possible. 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.
CTL updated
Message Added to Release
1.6
Severity
Informational
Explanation
The Certificate Trust List (CTL) file has been updated.
Recommended Action
No action is required.
CTS cannot read favorites information
Message Added to Release
1.8
Severity
Warning
Explanation
The CTS cannot read information about Favorites from the addrbook.conf file provided by Cisco Unified CM.
Recommended Action
Verify that the file /nv/usr/local/etc/addrbook.conf exists on the CTS. Verify that CTS has read access to the file.
CTS certificate updated in Cisco Unified CM
Message Added to Release
1.6
Severity
Informational
Explanation
Certified Technology Specialist (CTS) certificate has been updated in Cisco Unified CM.
Recommended Action
No action is required.
CTS could not begin recording at this time. To make a recording, a user in the meeting room must initiate a new recording session
Message Added to Release
1.8
Severity
Informational
Explanation
The CTS could not begin recording the current call.
Recommended Action
No action is required.
CTS is configured with appropriate file to perform B2B conference control
Message Added to Release
1.7
Severity
Informational
Explanation
The file required to perform intercompany conference control on a CTMS multipoint call is present.
Recommended Action
No action is required.
CTS is in an interop call and is not using TIP or MUX
Message Added to Release
1.8
Severity
Informational
Explanation
The CTS is in an interop call with a remote endpoint and is not using the MUX or TIP protocols.
Recommended Action
No action is required.
CTS is NOT configured with appropriate file to perform B2B conference control
Message Added to Release
1.7
Severity
Informational
Explanation
The file required to perform intercompany conference control on a CTMS multipoint call is not present.
Recommended Action
If you want to use the intercompany feature, you need to provide this file.
CTS is running in TIP mode
Message Added to Release
1.7
Severity
Informational
Explanation
CTS is connected to a TelePresence Interoperability Protocol (TIP) endpoint.
Recommended Action
No action is required.
CTS transmits presentation at 5 FPS.
Message Added to Release
1.5
Severity
Information not available
Explanation
The Cisco TelePresence System will transmit the presentation at 5 frames per second (FPS).
Recommended Action
No action is required.
CUCM IP is not defined in the Cisco Unified CM configuration file
Message Added to Release
1.5
Severity
Information not available
Explanation
The Cisco Unified CM IP address has not been configured, and the calling services process is terminated.
Recommended Action
Configure an IP address or hostname for at least one Cisco Unified CM server, then restart the system.