[S]Can Call History be outload in a format other than .xml?
Stewart:
I was unable to read my OBi's file in OOO or even Excel. Examination with a text editor showed that the file is corrupted -- several hundred bytes are missing from the middle, such that the syntax is incorrect. The missing and butchered calls do show correctly in the Web interface. Retrying the download did not help. If I get a chance, I'll take a more detailed look tomorrow.
infin8loop:
Quote from: Stewart on February 22, 2012, 11:30:43 am
I was unable to read my OBi's file in OOO or even Excel. Examination with a text editor showed that the file is corrupted -- several hundred bytes are missing from the middle, such that the syntax is incorrect. The missing and butchered calls do show correctly in the Web interface. Retrying the download did not help. If I get a chance, I'll take a more detailed look tomorrow.
I've noticed downloading a non-corrupted xml file (either call history or config backup) through a browser is at times a hit or miss for me. Today I tried downloading a call history file several times and every file had an xml error. So, I slapped together yet another script to emulate the "Save All" button on the call history page. I was able to download several error free call history xml files using the script which import into Excel just fine. This is odd, because when I type http://192.168.0.40/callhistory.xml (which is what the "Save All" button does) into a browser window and click open or save, the file is corrupt, but the same URL invoked by script seems to work every time.
obi-historydumpinator.vbs is attached. There are three variables in the script that must be changed to your specific configuration. The call history file is saved with date/time stamp as callhistory_yyyymmdd_hhmmss.xml. The script could be scheduled to run on a server via task scheduler to regularly save off call history if needed.
Sorry, I don't do Mac.
Updated version obi-historydumpinatorV2.vbs: https://www.box.com/shared/9vdwpvswrvja3wbkuptd
This version includes an option to clear the OBi's history after it's dumped controlled by an additional variable that must be edited in the script. There are four variables in this version of the script that must be changed to your specific configuration.
Robert.Thompson:
Quote from: infin8loop on February 22, 2012, 08:21:59 pm
Quote from: Stewart on February 22, 2012, 11:30:43 am
I was unable to read my OBi's file in OOO or even Excel. Examination with a text editor showed that the file is corrupted -- several hundred bytes are missing from the middle, such that the syntax is incorrect. The missing and butchered calls do show correctly in the Web interface. Retrying the download did not help. If I get a chance, I'll take a more detailed look tomorrow.
I've noticed downloading a non-corrupted xml file (either call history or config backup) through a browser is at times a hit or miss for me. Today I tried downloading a call history file several times and every file had an xml error. So, I slapped together yet another script to emulate the "Save All" button on the call history page. I was able to download several error free call history xml files using the script which import into Excel just fine. This is odd, because when I type http://192.168.0.40/callhistory.xml (which is what the "Save All" button does) into a browser window and click open or save, the file is corrupt, but the same URL invoked by script seems to work every time.
obi-callhistorydumpinator.vbs is attached. There are three variables in the script that must be changed to your specific configuration. The call history file is saved with date/time stamp as callhistory_yyyymmdd_hhmmss.xml. The script could be scheduled to run on a server via task scheduler to regularly save off call history if needed.
Sorry, I don't do Mac.
Hello:
I don't know anything about vbs but I did not let that stop me from downloading and clicking your file.
I got:
Status code 12029:unknown
Is there something else that I must do?
Thanks,
QBZappy:
Robert.Thompson
Open the file with notepad or any text editor, and follow the instructions to customize it to your local environment. It is explained in the remarks. Have a look.
Robert.Thompson:
Quote from: QBZappy on February 23, 2012, 07:06:53 am
Robert.Thompson
Open the file with notepad or any text editor, and follow the instructions to customize it to your local environment. It is explained in the remarks. Have a look.
Thanks QBZappy! :)
I made the changes, ran it and it created the file but I still cannot load it into LibreOffice Calc. LibreOffice Writer works, just as it did before.
I am going to try writing a Pascal program to format the callhistory.xml file into CSV.
Rob.
Navigation
[0] Message Index
[#] Next page
[*] Previous page