Archivedir: Difference between revisions
No edit summary |
No edit summary |
||
Line 11: | Line 11: | ||
The chosen directory must have ownership / rights for asterisk. | The chosen directory must have ownership / rights for asterisk. | ||
It will create 2 things. A daily log file that the contents | It will create 2 things. A daily log file that the contents look similar to this... | ||
Revision as of 17:37, 16 December 2022
archivedir is a simple log and recorder.
Placed in rpt.conf
archivedir= /etc/asterisk/log/
Note: It will create a subdirectory from the stated path with the node# so each node has it's own archive.
i.e. /etc/asterisk/log/1999
The chosen directory must have ownership / rights for asterisk.
It will create 2 things. A daily log file that the contents look similar to this...
20221216112549,TXUNKEY,MAIN
20221216112800,RXKEY,29285
20221216112800,TXKEY,MAIN
20221216112800,RXUNKEY,29285
20221216112800,TXUNKEY,MAIN
20221216112801,LINKDISC,29285
The log file is named by date look like this:
20221216.txt
And a series of audio recordings, one each for an active COR on the node and named with file date and time down to the 1/100th of a second.
20221216115590.WAV (note that .wav and .WAV are not the same exact format)
Unfortunately, the log is not very in depth. But can show connects and disconnects and transmissions. Often you will need to listen to the audio to tell exactly what happened when trying to trace some things down. But you have a time stamp to make that easier.
You must take care if running this long periods of time as the audio files will consume a lot of HDD space.
This can be useful in debugging, policing or other creative things.