Home Usage About Download



The CVPParserG3 GUI has tabs for the different analysis: CVP, GW, CUSP, CUCM and PCAP (more will be added in the future for ICM, CUSP, etc) and each tab have sub-tabs for the analysis, search, filters and results.

For the CVP analysis, after dragging and dropping the CVP files or clicking Search (if the logs are already in the SOURCE Folder), the logs are automatically placed under the SOURCE directory and in a sub-directory "CVP" created by the tool, these files are copied like they were written from the CVP Call Server. Five options can be chosen to get the callguid: “ani", "legid", "rckey", "raw callid" and "all", for each search the parser will scan/search inside the logs for the appropriate strings matching calls, the default “callguid-ani” will cover mostly all the NEW-CALL’s and calls with ANI and the processing will be lighter than searching for all the legs. Once the search is completed the results are organized and displayed in the main Analysis window for ALL the SIP messages found in the logs and all the CALLGUID’s in the CALLGUID tab. As a note, depending on the amount of logs the processing can get slower so you can disable the parser from bringing all the SIP messages to the Analysis Tab and only the CALLGUID search by going to Options and uncheck CVP ALL-SIP.

From the main Analysis window the user can select to view the SIP messages, SIP Errors and ICM Errors. By right-clicking on a SIP message the user can run a filter for that Call-ID or find the CALLGUID or open the message in the original log using notepad++ to review it manually.

From the CALLGUID tab the user chooses, sorts or filters the selection of the callguid in question (the search display table can show thousands of calls that were extracted and organized in seconds). When the callguid is selected, it is populated in the callguid field in the Analysis tab. You can double click on the callguid or click the Execute button (Analysis Tab) that will make the parser search/scan the CVP log files again with the specific target callguid, extracting the SIP and ICM messaging to be organized in each different selection chosen in the options, it will also build the ladder diagrams for SIP, ICM and SIP/ICM combined in the Results tab so the user can easily see the interaction of each system in the ladder diagram. The main display in the Analysis tab can let you choose particular message to have a full display of itself in a lower window where you can find explanations and errors if applied to each message. There is also the GW, CUCM, CUSP and PCAP option called the “CVP Combined Filter” that when clicked it will populate the filters in the GW, CUCM, CUSP and PCAP filter “CVP Callguid table” so when doing the analysis for a GW, CUCM, CUSP or PCAP log then the filter can be applied and immediately have the corresponding call that matches the call from the CVP log side. With this you can have all the different logs from the different endpoints like CVP, ingress/vxml GW, CUCM, CUSP and PCAP from a sniffer and be able to troubleshoot and analyze in a combined fashion comparing side by side the call flow.
CVP has 2 Filters available, one for SIP and one for ICM, the filters will be applied for the SIP and ICM option it if the Filter selection is showing checked or red then you can select to build a diagram for those filters, the pdf will be in the result tab.

The GW, CUSP, CUCM and PCAP analysis work in the same fashion having the logs under the respective subfolders "GW", "CUSP", “CUCM” and "PCAP", the logs must be named putty.log/txt, SDL/ccm.txt, *cusp*.log and .pcap/cap, the is a numerical value that helps the parser sort them in an organized fashion since the beginning. Once any of these logs is "Searched" the results will be displayed in the Analysis Tab presenting each SIP message in the log, as the GW, CUCM, CUSP or PCAP logs does not have a sequence of leg-ids to organize each particular call, filters can be applied to display combined call-ids, source/destination, callguid's, and a generic text if selected. Each filter applied have an internal "and" operator and between filters an "or" operator so any combination can be applied to display the call flow desired. When the call flow is displayed, the user can go thru it in the same window displaying the messages itself or can select to build a ladder diagram for it that will be written and can be selected in the Results Tab.

Each SIP call leg is assigned a color for easy finding plus in the GUI table, the message can be clicked to read the entire content plus hints on certain messages to help the user understand reasons or causes for disconnects or errors.

User can drag and drop the files to the search window and will process it immediately.

Important Note: Wireshark must be installed so the CVPParser can use TShark to extract the messages
Install CVPParserInstaller.exe
Example: C:\Program Files (x86)\CVPParserG3
Installer will create the SOURCE and RESULTS Folder under the main CVPParserG3 Folder and the sub-folders for each technology analysis (CVP, GW, CUSP, CUCM, PCAP)
This is controlled by the cvpparser.properties file for the source and destination chosen (this will make those folders default), you can change the Source and Destination folder in the Folders Tab and it will update the cvpparser.properties.
Run CVPParserG3 icon from the desktop or Start->Programs or the CVPParserG3.exe from where it was uncompressed.
Go To Folders Tab and the source and destination to check if it is correct. These folders are where the files are copied and the results written.
Drag and Drop files into the search for any of the technology analysis. The logs must be named according to the different technology: CVP*.log, putty.log/txt, SDL/ccm.txt and .pcap/cap, the is a numerical value that helps the parser sort them in an organized fashion since the beginning. Dragging and dropping will automatically Search the file(s).
OR copy files CVP logs under SOURCE and sub-folder CVP, putty.log/txt for the GW under source sub-folder GW, SDL/ccm.txt for the CUCM under source sub-folder CUCM and .pcap/cap PCAP log for the PCAP under source sub-folder PCAP
Go to CVP Tab and on Analysis Tab click Search, the Search results will be populated in Search Tab.
Choose one of the last calls and go back to Analysis Tab, click the GW Option, PCAP Option or CUCM Option so it will populate the GW, CUSP, PCAP or CUCM CVP Callguid's filters. Then click Execute. (If you don’t need combined analysis just double click on the callguid in the Search Tab, it will automatically do the Execute)
Check the Callguid Call flow with all the CVP call legs generated.
Check the bottom combo-box to choose between SIP, ICM, Errors and SIP-ICM.
Check the Results Tab for the ladder diagrams and text file of the specific call flow. Double click if desired to look at results.
Go to GW Tab and click Search.
Once the results are displayed, go to Filters options and check the CVP Combined analysis and click Set All CVP and Apply Filter.
Go to Analysis Tab and look at results that match the CVP call flow. Click Diagram to generate ladder Diagram.
Go to Results Tab to access the ladder diagram.
Go to PCAP Tab and click Search.
Once the results are displayed, go to Filters options and check the CVP Combined analysis and click Set All CVP and Apply Filter.
Go to Analysis Tab and look at results that match the CVP call flow. Click Diagram to generate ladder Diagram.
Go to Results Tab to access the ladder diagram.
You can do other examples with other types of filters and callguid's.
You can email the results using your local Outlook email. (Note when clicking email button the outlook will launch an email window so cvpparser will wait until that window is closed)
You can email TAC with the activities recorded. (Note when clicking email button the outlook will launch an email window so cvpparser will wait until that window is closed)
Analysis window can be re-sized.
A double-click on the message row will send the content of the message to a separate Dialog window for easy viewing and comparison.

A right-click on the message will give the option to open the source file on the line that message was found, it requires Notepad++ installed.
A right-click on the message will give the option to build a filter with the call-id if a SIP message is selected.
A right-click on the message will give the option to search for the CALLGUID for that Call-id.


GW Config Validator tab:

-Combo box has the most used VXML templates.
-Switch button for 2 Way Mode will switch the comparison from File 1 to File 2 and viceversa.
-Open Files will open the files being compared.
-For template or 1 way mode drag and drop the file and it will compare it to the chosen template
-For 2 Way Mode drag 2 files at the same time or one by one and it will run the comparison between them. The first file will be the one referenced to look for differences.
-Double click on any row on any of the two window's files and it will look for the matches on the other side and highlight them.

Two algorithms to compare:
-Diff will give you the blocks of differences found between the template or two files. The order matters so the comparison is on the search for a string match in between the ones that do not. The pearl and skyblue color will point out blocks with differences. The pink or lightgreen will indicate that in between those strings the other side block is not present.
Results is in the format of the output from the python Diff function @@ -x,x +y,y @@
The - means the first file or the file on the left. + means the second file or the file in the right. The first number means the start row and the second number means the amount of row for the block.
-By Line will run from file 1 to file 2 looking for the string to match, it can be the template chosen or two files mode. It will report if it was Not Found or a match above 80% ratio. This means that the higher the match the more similar the strings are. As the sh run files may have different values but the command may be the same then is up to the user to visually compare and decide if the finding is relevant or not.

To check for Updates:
-Click on Help -- Check For Updates




Logging required for logs:

CVP Server:
-Login to CVP server and browse to http://localhost:8000/cvp/diag

-Click DEBUG/41.
-Set "Serv Mgr" to com.dynamicsoft.DsLibs.DsUALibs and then set "Level"
to DEBUG.
-Then click the Set button.
-Logs are located in C:\Cisco\CVP\logs
(The name of the log files must be as they were created on the Call Server)

For GW:
>debug ccsip message
Name the files *putty*.log/txt
(On multiple files please add a number to the file ascendant so parser can run them in order, i.e. putty1.log, putty2.log..)

For CUCM:
Trace Configuration: CM Services – Cisco CallManager:
Enable SIP Call Processing Trace. Debug Trace Level Detailed.
Apply all nodes
SDL*/ccm*.txt

For CUSP:
Important note, for the CUSP analysis, it only works at the moment with the SIP Stack logs:
< ENABLE LOGS >
module> cusp
module(cusp)>trace enable ! "trace disable" to turn off tracing
module(cusp)>trace level debug
module(cusp)>config
module(cusp-config)>sip logging

< SHOW LOGS >
module> cusp
module(cusp)>show trace log
module(cusp)>show sip message log

Name the files *cusp*.log/txt
(On multiple files please add a number to the file ascendant so parser can run them in order, i.e. cusp1.log, cusp2.log..)


MAC Users:
-Please find instructions attached on how to install this tool in MAC OS. Thank you to Steve Hartman.


NOTES:
-This tool is not supported by Cisco Systems.
-Please let me know any problems, issues or bugs, you can copy and paste the small output window and send it to me when an error happens.
-If there is something confusing in its usage please let me know so I can explain. I am working the documentation.