- Help center
FSVM Configuration of Recording Archiving
Please consider to change the FSVM configuration only as the last resort. Most likely you will never have to change it.
The default configuration of recoding archiving module is located in the file
/opt/faster/conf/rak.xml. To keep your changes persistent they should be placed into
/opt/faster/conf/localhost-config.xml file, because updating overwrite the former file.
Sample of content of
<configuration> <archiving> <spool>/var/spool/asterisk</spool> <from>23:00</from> <upto>06:00</upto> <interval>30000</interval> <batch>50</batch> <dryMode>false</dryMode> <shape>ymdutc</shape> <gc> <active>true</active> <idleInMinutes>12</idleInMinutes> <expirationInDays>14</expirationInDays> </gc> </archiving> </configuration>
Sample of content
/opt/faster/conf/localhost-config.xml with the changes.
<configuration> <archiving> <from>02:00</from> <upto>08:00</upto> </archiving> </configuration>
- spool: it points to the asterisk spool directory.
- from, upto: time range for archiving and gc activity. Examples:
- whole day:
- whole day:
interval: it is an interval in milliseconds between successive runs (both archiving and gc activity).
- batch: it is a maximal count of calls processed during a single run (both archiving and gc activity.
truevalue here will completely turns the archiving activity off. Please don't change this.
plain- internal shape of archive (see the Recoding Archive Format article for details).
falsevalue here will turns of removing outdated file in the
- gc.idleInMinutes: when all outdated files are removed from the protected folder the gc activity sleeps for given interval. It should be a big value like 10-30 minutes. When activity wakes up it run with interval period until all outdated files are removed and sleeps again for gc.idleInMinutes.
- gc.expirationInDays: number of days to keep files in the protected folder.
The batch and interval properties limit throughput of the module. The archiving throughput should larger then PBX one. Default is 100 calls per minute (30sec interval, two polls per minute, each is 50 calls max). If it is not enough, then change these properties and restart the daemon.