callhistory.xml
RobertThompson:
Hello:
I think that I have found a simple way to remove all the 'NUL' characters from the Obi-202 Callhistory.xml file. These characters prevent you from opening the CallHistory.xml file with a text editor etc.
Here's how:
Download Notepad++ https://notepad-plus-plus.org/
Open your CallHistory.xml file in Notepad++
From Main Menu: Search -> Search Mode set this to: Extended
Then,
Replace -> Find what: \x00 (back slash, small x, zero, zero); Replace with: {leave empty}
Then, click Replace_All
Then 'Save as' something else, example: save as callhistory_changed.xml
RobertThompson:
It seems that you need to repeat the procedure for: \x02 (back slash, small x, zero, two)
RobertThompson:
I have made further updates to the programs.
OBi-202 CallHistory.xml file to tab-delimited file
The programs now reads the callhistory.xml file and cleans out all the non utf-8 characters. It leaves the original callhistory.xml file totally untouched but generates a new file called: CallHistory_Cleaned.xml
This new file is used to generate the 'Ch_' files.
I still do not generate a separate file containing ALL calls but it is coming soon-ish...
The Windows & Linux downloads may be found here: http://www.googlevoiceforcanadians.com/downloads/
Again, any feedback or input would be appreciated...
CoalMinerRetired:
Quote from: RobertThompson on July 23, 2015, 10:11:06 am
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.
Do the 34 fields include the case when a call is transferred? I notice that sometimes, not always, an OBi202 logs transferred calls differently.
Sometimes you see the entries for "Transfer To ... Bridged Ref:xxxxx" and the New Peer/Transfer Target, and sometimes you don't get these, the log just looks like two different calls with no mention the second call was initated as a transfer (Flash > Dial # > Flash > (Hangup or not, full transfer or three-way call).
RobertThompson:
Quote from: CoalMinerRetired on August 03, 2015, 06:00:11 am
Do the 34 fields include the case when a call is transferred? I notice that sometimes, not always, an OBi202 logs transferred calls differently.
Sometimes you see the entries for "Transfer To ... Bridged Ref:xxxxx" and the New Peer/Transfer Target, and sometimes you don't get these, the log just looks like two different calls with no mention the second call was initated as a transfer (Flash > Dial # > Flash > (Hangup or not, full transfer or three-way call).
Hi CoalMinerRetired:
It is difficult for me to answer you question because the only two Obi-202 callhistory.xml files that I have were provided (PM'ed) to me by two different members of this forum. The programs seem to handle the calls & events included in their files but I do not know if *** all possible *** entries are contained in those files.
Did you try the programs against a callhistory.xml file which contains such entries?
Please note that in the files that I have, many of the '34 fields' just contain "</Event>" which indicates the *** end *** of a specific event.
The program strips out these text strings and only outputs the information contained between "<Event time=" (i.e., the beginning of a specific event) & "</Event>" (i.e., the end of a specific event).
Navigation
[0] Message Index
[#] Next page
[*] Previous page