CallAudit Logfile Information

LOGFILE Data

Each time CallAudit software starts, the program generates a diagnostic file names LOGFILE.TXT.  This file is located in the same directory as the CallAudit software.  The information contained in the LOGFILE is lengthy, but can be very useful in helping resolve various user issues and problems.  

Data in a log file appears similar to the example shown below:

09-15-04 09:00:01 : Program (32-bit): CallAudit Voice 6.0 for Windows 
09-15-04 09:00:01 : Build: Build 600-4.65765 
09-15-04 09:00:01 : Path : C:\CAV60 
09-15-04 09:00:01 : Exe : Cav60.EXE 
09-15-04 09:00:01 : Pgm Exe Count: 1069 
09-15-04 09:00:01 : 
09-15-04 09:00:01 : OS: Microsoft Windows XP 5.1 (Build: 2600.0) Service Pack 2 
09-15-04 09:00:01 : 
09-15-04 09:00:01 : LastOS: Microsoft Windows XP 5.1 (Build: 2600.0) Service Pack 2 
09-15-04 09:00:01 : 
09-15-04 09:00:01 : Build : 2600 
09-15-04 09:00:01 : WinInfo : Service Pack 2 
09-15-04 09:00:01 : WinDir : C:\WINDOWS 
09-15-04 09:00:01 : ComputerName : DELL2 
09-15-04 09:00:01 : User : EdDixon 
09-15-04 09:00:01 : IP : 198.168.0.43 
09-15-04 09:00:01 : RAM : 535,805,952 
09-15-04 09:00:01 : Modem Count : 1 
09-15-04 09:00:01 : 
09-15-04 09:00:01 : Model : 56HP92-D 
09-15-04 09:00:01 : DriverDesc : 56HP92-D 
09-15-04 09:00:01 : Manufacturer : BDP 
09-15-04 09:00:01 : 

Each line has a time/date stamp with other data generated by CallAudit software to show overall info as well as detailed info about each telephone call.

MODEMLOG Data

By the same token, Windows keeps a separate log file for modem information called MODEMLOG.TXT, which is located in the Windows directory on your PC.  This info can also be helpful in determining exactly what you modem did for an incoming call and what actions might be necessary to make it work better.

The data in a typical MODEMLOG file would look similar to that shown below:

09-16-2004 09:36:06.421 - File: C:\WINDOWS\system32\tapisrv.dll, Version 5.1.2600 
09-16-2004 09:36:06.421 - File: C:\WINDOWS\system32\unimdm.tsp, Version 5.1.2600 
09-16-2004 09:36:06.421 - File: C:\WINDOWS\system32\unimdmat.dll, Version 5.1.2600 
09-16-2004 09:36:06.421 - File: C:\WINDOWS\system32\uniplat.dll, Version 5.1.2600 
09-16-2004 09:36:06.453 - File: C:\WINDOWS\system32\drivers\modem.sys, Version 5.1.2600 
09-16-2004 09:36:06.468 - File: C:\WINDOWS\system32\modemui.dll, Version 5.1.2600 
09-16-2004 09:36:06.484 - File: C:\WINDOWS\system32\mdminst.dll, Version 5.1.2600 
09-16-2004 09:36:06.484 - Modem type: 56HP92-D
09-16-2004 09:36:06.484 - Modem inf path: oem5.inf
09-16-2004 09:36:06.484 - Modem inf section: ModemX
09-16-2004 09:36:06.484 - Matching hardware ID: pci\ven_14f1&dev_2f00&subsys_8d8413e0
09-16-2004 09:36:06.765 - Opening Modem
09-16-2004 09:36:06.765 - 115200,8,N,1, ctsfl=1, rtsctl=2
09-16-2004 09:36:06.781 - Initializing modem.
09-16-2004 09:36:06.812 - DSR is low while initializing the modem. Verify modem is turned on.
09-16-2004 09:36:06.812 - Send: AT<cr>
09-16-2004 09:36:06.812 - Recv: <cr><lf>OK<cr><lf>
09-16-2004 09:36:06.812 - Interpreted response: OK
09-16-2004 09:36:06.828 - Send: AT&FE0V1S0=0&C1&D2+MR=2;+DR=1;+ER=1;W2<cr>
09-16-2004 09:36:06.968 - Recv: <cr><lf>OK<cr><lf>
09-16-2004 09:36:06.968 - Interpreted response: OK
09-16-2004 09:36:06.984 - Send: ATH<cr>
09-16-2004 09:36:07.000 - Recv: <cr><lf>OK<cr><lf>
09-16-2004 09:36:07.000 - Interpreted response: OK
09-16-2004 09:36:07.015 - Send: ATS7=60M1+ES=3,0,2;+DS=3;+IFC=2,2;X4<cr>
09-16-2004 09:36:07.031 - Recv: <cr><lf>OK<cr><lf>
09-16-2004 09:36:07.031 - Interpreted response: OK
09-16-2004 09:36:07.046 - Waiting for a call.
09-16-2004 09:36:07.062 - Send: at+vcid=1<cr>
09-16-2004 09:36:07.078 - Recv: <cr><lf>OK<cr><lf>
09-16-2004 09:36:07.078 - Interpreted response: OK
09-16-2004 09:36:07.093 - Send: ATS0=0<cr>
09-16-2004 09:36:07.109 - Recv: <cr><lf>OK<cr><lf>
09-16-2004 09:36:07.109 - Interpreted response: OK

Sending LOGFILE and MODEMLOG Data to MSI

You can have CallAudit automatically send both the LOGFILE and MODEMLOG data directly to MSI.  To do so, perform the following steps:

• Wait until a number of telephone calls have occurred where the issue to be address is included
• Go to the Internet Menu at the top of the program where the Menu items are listed (things like File, Edit, View, etc)
• Select the option shown as "Send System Information via the Internet"
• Check the LOGFILE option
• Check the MODEMLOG option
• Enter a short description with info about the issue or problem you are experiencing
• Press the "Send Information to Mountain Systems" button

An example of this display is shown below: