Log File Format ** SOLVED

[erike4]

Does anyone have the format of fields in the Call history file for the various record types? Also does anyone know the life cycle of this file? It seems only have about 6 days of data in it and only contains a small anout of data - espicialy weird since it in a folder called Backup.
I am writing some acconting programmes for our various divisions and need to "crack" this file and archive it so that we can do billback.

 

[nb]

Re: Log File Format

That folder has rotated, saved itself in the backup folder and a new file was created.
What do you want to know exactly? You should forward this request to support since it is something internal. They should be able to provide you with what the codes mean.

Life cycle is size - when it reaches a certain size it rotates, puts copy in backup and creates new file.

by trial and error in any case you should get this information. Each call if I am not mistaken is 1-2 lines depending on the calls. Also when you see the cal you are making and the numbers, you can quickly identify what is the start time, end time, connected time, caller number and destination number.

 

[erike4]

That folder has rotated, saved itself in the backup folder and a new file was created.

ED) What then of the old file? There is nothing older that 6 days ago!

ED) what happens on a system crash or anomoly or bug or normal or abnormal shutdown shutdown? Are these file created non-buffered or just happenstance? (is that why the restart, shutdown and hybernate is removed from the start menu <at risk system or??)?)

ED) P.S. The CallHistory records are not in the backup folder? Why , what reason?? Customer inconvience or oops?

What do you want to know exactly? You should forward this request to support since it is something internal. They should be able to provide you with what the codes mean.

ED) How long do they take to answer? This question was turned over just after I installed in October 2010. Someone at 3CX has the answers or at least the documentation. Without their participation we as customers are in the position of guessing over and over again. (That has nessatated forums as companies have abandoned full service customer support and documentation. - Sorry I am from the old school (<Grandpa> Demming et all))

Life cycle is size - when it reaches a certain size it rotates, puts copy in backup and creates new file.

ED) What then of the old file? There is nothing older that 6 days ago! and the only three peices parts are different sizes, rolled at different times and have large gaps in time between them. Do i need to run backups to snapshot and retain older data?

by trial and error in any case you should get this information. Each call if I am not mistaken is 1-2 lines depending on the calls. Also when you see the cal you are making and the numbers, you can quickly identify what is the start time, end time, connected time, caller number and destination number.

ED) as you can see by the records below there are more than two, And, yes, without support (or) documentation trial by error (times the number of interested customers) yealds many questions and some little meaningfull data. As you can see there are joined pairs- but why repeated? why the "1" at the end? is the hash continously unique? Why did record type 8 and 9 suddenly appear and what are they? Is there a type 5 and 7? what is the significance of record type 6 after a record type 4 (disconnect)? Why is record type 10 subtyped and none of the other records (are we going to see more records appearing in the future and have to guess again?)

# print "Start $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 1,20101226071325.955,c41a6049a45a6d38,15,0828932024,15,0828932024,1
# print "Connect $id $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 2,20101226071343.973,c41a6049a45a6d38,15,10000,15,0828932024,1
# print "Ring $id $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 3,20101226071325.955,c41a6049a45a6d38,15,,15,,1
# 3,20101226071326.018,c41a6049a45a6d38,10000,0828932024,27129400511,0828932024,1
# print "Disconnect $id $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 4,20101226071412.007,c41a6049a45a6d38,15,,15,,1
# print "Eof $id $seq $date $time\n";
# 6,20101226071412.194,c41a6049a45a6d38,,,,,
# print "Internal $id $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 8,20101230180626.452,15394d41a057b520,13,,,,1
# print "Unavaliable $id $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 9,20101230181009.282,b6405a27923b3b77,0714772768,,,,1
# print "Recording $id $seq $date $time $ext $arg1 $arg2 $arg3 $arg4\n";
# 10,20101226165309.843,653058309916324a,15,,RecON,D:\Recordings\15\[27123720330]_15-0837299939_20101226185309(55).wav,1
# 10,20101226171212.290,653058309916324a,10000,0837299939,RecOFF,D:\Recordings\15\[27123720330]_15-0837299939_20101226185309(55).wav,1

ED) And what of all the other logs? what are they? What is life cycle? and specifically the Server Activity Log, where can we get a longer term log for diagnosis of calls across providers.....

ED) are the logs "safe" across (above - shutdowns, failures etc.), software updates, system reinstalls, system restarts?

ED) In reference to your trialand error comment: You may be too young to remember IBM. But we always had cabenets microfilm to bakeup the paper documentation of each CPU, Operating system, upgrade and if there was a question you could find the answer in a short time with a little digging, or make a call and get the answer, pointers to the doc's or a body to help find or fix it. They were the ones who when visiting the customer site always said "Thank you customer". Now with pay for support from 3CX we cant even get past the first question (notice I Did Not include "answer")......

 

[nb]

ED) What then of the old file? There is nothing older that 6 days ago!

We dont save this forever. you Are using the wrong feature. Those logs are saved in the database. We have no reason to keep them there. If you want call history files, use CDR.

ED) what happens on a system crash or anomoly or bug or normal or abnormal shutdown shutdown? Are these file created non-buffered or just happenstance? (is that why the restart, shutdown and hybernate is removed from the start menu <at risk system or??)?)

?? What do you expect happens on a system crash? Everything is real time here. Again wrong feature. Go in the database.

ED) P.S. The CallHistory records are not in the backup folder? Why , what reason?? Customer inconvience or oops?

Because if you read the documentation you will find that there is a database that stores information. You cannot miss this if you are writing accounting programs. If I were you the first thing I would do is put my foot in the database and see what there is in there.

ED) How long do they take to answer? This question was turned over just after I installed in October 2010. Someone at 3CX has the answers or at least the documentation. Without their participation we as customers are in the position of guessing over and over again. (That has nessatated forums as companies have abandoned full service customer support and documentation. - Sorry I am from the old school (<Grandpa> Demming et all))

Did you open a support request? Yes or no? If yes send me the ticket number and I will trace it for you.
Also it is quite strange because support have a couple of documents that they give to developers who want to integrate with our system. Locate the ticket and I will send them to you.

ED) What then of the old file? There is nothing older that 6 days ago! and the only three peices parts are different sizes, rolled at different times and have large gaps in time between them. Do i need to run backups to snapshot and retain older data?

Again - ????
And yes you can get half the information. Let me tell you with 1 call that 2,4, 6 can already be known to you.
2 Dialing 120 to 116
4 Connected start time
4 Connected End time
6 Terminated.

From:
2,20110105080804.810,2d695930892dda00,120,116,120,116,1
4,20110105080807.823,2d695930892dda00,116,,116,,1
4,20110105080807.830,2d695930892dda00,120,,120,,1
6,20110105080807.988,2d695930892dda00,,,,,

This is what I mean by trial and error.

Now if you want to start your program by making complex calls involving transfers, pickups and whatever, then you are coding in the wrong direction anyway. Start from simple.

ED) And what of all the other logs? what are they? What is life cycle? and specifically the Server Activity Log, where can we get a longer term log for diagnosis of calls across providers.....

The call history log is a temp storage of logs. the actual real like calls are stored there. Then a service comes, parses that file, and injects the data in the database. That file is deleted, its contents put in the backup folder.

ED) are the logs "safe" across (above - shutdowns, failures etc.), software updates, system reinstalls, system restarts?

Again..

ED) In reference to your trialand error comment: You may be too young to remember IBM. But we always had cabenets microfilm to bakeup the paper documentation of each CPU, Operating system, upgrade and if there was a question you could find the answer in a short time with a little digging, or make a call and get the answer, pointers to the doc's or a body to help find or fix it. They were the ones who when visiting the customer site always said "Thank you customer". Now with pay for support from 3CX we cant even get past the first question (notice I Did Not include "answer")......

I respect everything you stated here and I agree with you in certain aspects yes. I just don't agree with your development approach. It doesn't work like this. Also I remember IBM now and I can tell you that to install a raid driver or controller I have to read till my eyes turn red. Also you can you really compare IBM company size with ours What is this? Locate the ticket and I will address it.
Secondly you are missing a very important point here:
Your case is NOT NORMAL SUPPORT. Your case is Developer support which is completely different - more time consuming and more intricate. If you locate the ticket, I will be able to guide you into first using the right feature.