callhistory.xml
RobertThompson:
Quote from: restamp on July 13, 2015, 11:49:30 am
Any ideas?
My guess is that the file format of the OBi callhistory.xml file has changed since I wrote the program - I tested it against an old callhistory.xml file that I had on hand.
I'll outload a new callhistory.xml file and see what's wrong & will get back to you.
Rob.
RobertThompson:
The CallHistory.xml file for the OBi-202 is vastly different from the CallHistory.xml file for the OBi-110, so, I created a new program to deal with it.
You just need to download the correct version (Linux or Windows) to the same directory/folder as your OBi-202 CallHistory.xml file and run the program.
You can download the program from this page: http://www.googlevoiceforcanadians.com/downloads/
This is only 'Stage # 1' of the program - 'Stage # 2' will get rid of all the unnecessary characters & columns.
Any feedback would be appreciated.
Here is some "bla, bla" info, if you are interested:
In the Obi-202 Callhistory.xml file, a 'Call Record' starts with : <CallHistory date=
and ends with : </CallHistory>
Between these 'start' & 'end' lines, there may be from 8 to 34 of additional detail
lines of information relating to the call, at least this was the case with the Obi-
202 CallHistory.xml file that I have.
The only useful way that my little brain could figure out on how to deal with the
fact that a single 'Call Record' could have many detail lines was to output the Obi-
202 CallHistory.xml to many 'CH_Work.txt' files, based on the total number of
lines for each 'Call Record' , so, that is what I did.
When you open a 'CH_Work.txt file with a spreadsheet program, you will see that
I added 3 columns to the beginning of each row – remember that each row is a
'Call Record':
1. The total number of lines for that 'Call Record'
2. The starting line number from the 'CallHistory.xml' file for that record.
3. The ending line number from the 'CallHistory.xml' file for that record.
When you run the Obi-202 program, it will generate:
• A CH_Work.txt file that contains a single row for each 'Call Record', with as
many columns as there are lines for that 'Call Record'.
To use the program:
1. Copy it into the directory/folder where the CallHistory.xml file is living.
2. Launch the program.
3. The 'CH_Work' files will be generated in the same directory/folder.
RobertThompson:
Hello:
I have modified both the Windows & Linux "CallHistory to Tab-Delimited" for the Obi-202 programs to remove all the irrelevant characters.
The programs now create CH_n.txt files where the 'n' equals the number of relevant columns (events) in the file. The first three columns give you the number of lines 'read' from the CallHistory.xml for the row, the CallHistory.xml 'start line' for the row and the CallHistory.xml 'end line' for the row. The last column in each file is just the 'count' of relevant columns.
See: http://www.googlevoiceforcanadians.com/downloads/
I am now working on generating a single file (CH_All.txt) containing all the call records and events in a meaningful way.
Rob.
lrosenman:
would some of my XML's with the bad characters help you any? If so, PM me
RobertThompson:
Quote from: lrosenman on July 28, 2015, 10:23:26 pm
would some of my XML's with the bad characters help you any? If so, PM me
Yes, that would be very helpful - PM'ed you.
Navigation
[0] Message Index
[#] Next page
[*] Previous page