To add to Rajesh's excellent post, OS access is definitely tied down. TAC has a way to access the OS via a temporary password which they create using a hash you give them from the system. This will give you real root access and you can use commands in unix/linux. (Very dangerous to use if you dont know what you are doing). Accessing the system like this is not really supported unless you are assisted by a tac engineer.
We're looking at things like... how to access the call manager trace logs. Before, we could turn on the call manager trace, and we could go into the folder structure and grab them easily.
The same is true for your bat files. We were storing them on the server, and moving them around into sub directories as needed. Just an easier way of keeping the documentation with the server of what was imported and when (we name the files with a "smart" name).
As far as *nix access. We're pretty experienced on that front. Due to a database replication issue we had recently, TAC had to use that exact piece to go in and make some changes at the *nix level (gotta love bugs!)
For traces, once you enable them via servicability, you have to install RTMT plugin from Plugins page. Once this is installed on your computer, you can login using admin username and password and go to Trace central to collect the logs. Logs will be zipped and downloaded to a local folder (Look at the folder in which RTMT is installed (C:/program files/RTMT/...)
Bat files in 5.x and 6.x are stored in the server itself. You can manage them via Bulk administration menu in Callmanager. (Specifically publisher). When you upload them you have to select the type of upload (Phones, Phone-users, UDP etc). They are all grouped separate, so when you are trying to BAT in Phones-users, you only see the appropriate BAT files that belong to that class.
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...