To capture the CTS logs, log into the CTS web GUI and go to Troubleshooting -> Log Files.
Click the Log Files tab at the top of the page. Otherwise, you will only be downloading the sysop messages.
Select Capture new log files and pick Other/Unknown as the problem type.
Hit the Capture New Log Files button and you'll start to see progress under Log Capture Status. Depending on your browser/version this may not update at all. If after a couple minutes, nothing seems to have happened and the "Previous Logs Captured At" timestamp seems incorrect, please see the Troubleshooting section.
Once the logs are captured, hit Download existing log files to download a .tar.gz containing the logs. Do not extract this file, but please open it in compression software such as 7zip or WinRAR to ensure the logs are not corrupt.
To upload the logs to the case, you can either email them to firstname.lastname@example.org or upload them directly on Cisco.com if they are too large.
To email the logs to us, please Reply-All to an email we have sent you, and ensure email@example.com is CC'd on the email. Do not take the TAC case number (662XXXXXX) out of the subject line. This will automatically attach them to the case.
For larger files (20Mb+), you will probably have to use the web tool. Go to Cisco.com -> Support -> My Open Cases.
Select your case number. Then hit File Upload to bring you down the page to the file upload section. From here just choose the file, select Log/Trace File, add a comment of what device the file is from and hit Upload File.
The most common problem with CTS logs is either they will not capture from the web GUI or the log files are corrupt when you try to open them. You can attempt to fix either of these issues by re-capturing the logs from the CLI.
From the admin: prompt, use utils logs generate other to generate the logs again. Then download them from the web GUI.
If the web GUI is completely unresponsive (to both capture and downloading logs), you can also FTP, SFTP or SCP the log files off of the codec from the CLI. To do this, the syntax is utils logs [protocol] [username] [password] [destination]. For example:
utils logs sftp ciscoadmin p4$$w0rd 10.25.20.1
If you get an error such as Error reading header after processing 0 entries when trying to open the logs, you likely have the wrong file extension and your software can't understand what it's opening. Check to make sure the file extension is .tar.gz. The most common cause of this problem is if the file has been named ".tar" when in reality it is a .gz file.
If you have other problems capturing, downloading or sending logs to TAC, please contact your engineer.
Hello,I need to create a around 20 Application users with diferent permissions. But I facing a problem, using BAT I can create the app users but I dont know how to configure the password. It has to be done manually after creating the users with BAT? ...
Hey Webex Teams Users, I'm wondering if anybody has found a way to run a "random meeting scheduler", either through teams, Outlook, or another application. Microsoft teams has a pretty good product called "Icebreaker Bot", that would be gr...
Hope someone can help with a strange issue that I am having. I have one user that has placed call forwarding on their line. When we call the extension from within the company eg we dial 2222 it will forward to the phone no problem. When we dial the DID di...
Hello,Trying to install a Sub at new a DR site as an additional to our existing cluster. System version: 184.108.40.20600-26. It is failing during the DB install on step 4. I have found similar posts with exact same error below but with no co...
I'm working on a script that would send a call to an agent regardless of finesse state. I have it working well using the connect step, however the finesse layout does not get populated with Enterprise data that is set from a database dip. Is this normal f...