.. _csa.callengine.supportedproducts: Product and feature support =========================== Supported products ------------------ VCS/Expressway ^^^^^^^^^^^^^^ **Log file format** Upload the full diagnostic archive collected under *Maintenance -> Diagnostics -> Diagnostic logging*. Check the "take tcpdump while logging" option on the web interface to also include pcap for extended feature set of the tool. We rely on xconf and xstat (txt and xml) files to get general system information, but also some vital information required for successful main log analysis (loggingsnapshot file). We expect 1 archive per server. .. image:: images/expressway_diag_archive_content.png :align: center :width: 500pt **Note:** Default logs levels are fine for most of the analysis. Additional XMPP communication can be displayed with Mobile and Remote Access login message flow when "developer.xcp.jabber" is set to DEBUG under *Maintenance -> Diagnostics -> Advanced -> Support Log configuration*. **Supported features** * SIP/H.323 calls * RTP streams (pcap) * SIP registrations * MRA sessions * DNS * XMPP * STUN * TCP/UDP streams (pcap) CUCM (Cisco Unified Communications Manager) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ **Log file format** Please make sure that the data is correctly prepared as per the following guidelines: 1. Use RTMT (Real-time monitoring tool) to download the Cisco CallManager service traces from ALL nodes in the cluster. 2. Traces should be set to detailed which is the default setting from CUCM 9.X unless configured otherwise. 3. Zip all the files and folders that RTMT created in one archive and upload to the tool. 4. Leave original filenames(SDL*/calllogs*) and structure of directories created by RTMT. 5. If there are multiple clusters, upload one archive per cluster. 6. When troubleshooting CTI-related issues, the CTI Manager traces should be collected together with the CCM traces. For more information about setting the traces to "detailed" level and collecting them please refer to this `document `_. **Supported features/scenarios** * Call flows with different signalling protocols (H323/SIP/MGCP/SCCP/CTI) * Call features: Transfer/Forward, Hold, Recording(Gateway-recording, BIB recording) * Media resource allocation(MTP/Xcoder,etc.) * Mobility(SNR) .. note:: Other call scenarios/features should work as well but are subject to the continuous testing. **Analysis** Due to the nature and size of CCM/CTI SDL traces, the data filtering is required and the full analysis is applied on per call basis only. Several steps are executed during the analysis flow: * Extract the archive and map SDL*/calllogs* for the same host * Find calls that are within SDL timelines based on SDLs/calllogs(UCM calls overview). * After selecting the call(manual step), filter only relevant lines * Apply annotations, ladder diagram based on the filtered data * Allow ability to download the filtered data(which includes related raw SDL files). .. note:: Please note that the UCM calls overview page may not provide full information about a call, for instance `Disconnect reason`, `CI B`, `Call-Id` can be missing or multiple entries can be present. After selecting the call, all call legs should be linked and complete information is available in `Call Details` TC/CE endpoints ^^^^^^^^^^^^^^^ **Log file format** Upload log archive collected over web interface under *Diagnostics -> Log Files*. For more information about collecting the logs please refer to this `document `_. **Supported features** * SIP calls * DNS * SIP registration * HTTP CMS (Meeting server) ^^^^^^^^^^^^^^^^^^^^ **Log file format** Upload logbundle.tar.gz file collected over SFTP from your CMS server. Alternatively, upload log archive collected using the CMS log collector tool found `here `_. **Supported features** * SIP calls Jabber client ^^^^^^^^^^^^^ **Log file format** Upload the problem report (PRT) generated by the Jabber client. All jabber platforms are supported from version 11.6. **Supported features** * SIP calls and registration * DNS requests * HTTP requests Jabber version CLI script ^^^^^^^^^^^^^^^^^^^^^^^^^ Currently there is no option in IM&P server user interface to list versions of Jabber clients logged into IM&P server at any give time. This tool uses data dump from server CLI to generate the report. **Log file format** There are 2 txt files required, each of which has the following format: * line 1: CLI query * line 2+: the output of CLI query and contains one of the 2 queries: * *run sql select pkid ,userid from enduser* (ran on CUCM) * *run pe sql ttlogin select* * *from clientsessions* (ran on IM&P) **Example file content** query 1 .. code-block:: none admin:run sql select pkid ,userid from enduser pkid userid ==================================== =============================================== ae003243-0632-4b79-a042-dcbc82b68485 vsidimak@cisco.com query 2 .. code-block:: none admin:run pe sql ttlogin select * from clientsessions sqlRv(t) sqlstmt(select * from clientsessions;) ***result set start*** "count(1), success(t)" TTLOGINclientsessions
Q<1>4f40c76b-148d-47cc-a7d4-5d18a83c479c<5>1<6>11.8.4.52954<2>5e029d96-bb8d-8983-5af4-b6d70db3fd33<4>null<3>4adc1203-0eca-14cd-b5b8-3a78f76cbce6<0>00000001:59a31f79:000095bf:00000006 **Usage tips** 1. Since the output of queries might be large, make sure you increase the 'Lines of scroll back' under 'Window' section in Putty. 2. Run the query on each node in the IM&P cluster and copy the output into separate files. You will have to run the tool for each IM&P individually, or alternatively merge the outputs from different servers for the same query into 1 file, following the format above. 3. Upload the files to the tool, which will automatically detect the product types as IMP_JABBER_VERSION_STAT_1 (query 1) and IMP_JABBER_VERSION_STAT_2 (query 2) respectively. 4. Select both files and hit "Run analysis". .. image:: images/csa//callengine/csa_callengine_jabber_version_script_files.jpg :align: center :width: 500pt **Note:** The CLI outputs only provide Real-time Jabber statistics and not historical. **Sample tool output** .. image:: images/csa//callengine/csa_callengine_jabber_version_script_output.jpg :align: center Conductor ^^^^^^^^^ **Log file format** Upload the full diagnostic archive collected under *Maintenance -> Diagnostics -> Diagnostic logging*. Check the "take tcpdump while logging" option on the web interface to also include pcap for extended feature set of the tool. We rely on xconf and xstat (txt and xml) files to get general system information, but also some vital information required for successful main log analysis (loggingsnapshot file). **Supported features** * SIP calls * Conferences * RTP streams (pcap) * TCP/UDP streams (pcap) * DNS (pcap) * API/HTTP CVP (Customer Voice Portal) ^^^^^^^^^^^^^^^^^^^^^^^^^^^ **Log file format** Upload the CVP Call Server logs collected from location C:\\Cisco\\CVP\\logs. The log file names should not be changed. In order analyze SIP calls from CVP, SipLibrary logging should be enabled on CVP CS server. Please refer to `this instruction `_. **Supported features** * SIP calls * GED-125 (communication between CVP and ICM) PerfMon for Voice Operating System ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ **Log file format** Upload the archive that contains perfmon logs(Cisco RIS Data Collector PerfMonLog) collected using the RTMT tool from your Voice Operating System (CUCM,CUC,UCCX, etc.) server. The log bundle should contain PerfMon_*.csv files which record performance counters like CPUTime, VmSize(Virtual Memory Size), etc. This tool visualizes specific counters allowing you to easily spot issues. **Supported features** Before analysis, you will need to select one of the available templates: * Performance preview template (CPU, memory, IOWait) * Disk/storage troubleshooting template * CPU template * CUCM call activity template * DB replication