ViciBox v.3.0 archive-setup script is broken

[Kumba]

The included archive-setup is hopelessly broken. If you have already gotten your archive working, then you can skip these instructions. If yours is still broken, then the below actions should help rectify things.


So here is what you do to create an archive:

1) mkdir /home/archive
2) useradd -d /home/archive -s /bin/false <ftp-user>
3) passwd <ftp-user> (Enter the password when it asks)
4) chown -R <ftp-user>:users /home/archive
5) cd /etc/apache2/conf.d
6) rm viciarchive.conf (if it exists)
7) wget http://download.vicihost.com/conf/viciarchive.conf
chkconfig vsftpd on
9) rcvsftpd start
10) chkconfig apache2 on
11) rcapache2 start


The HTTP Path (VARHTTP_path) will be like this:
http://<server>/archive/RECORDINGS

The FTP directory (VARFTP_dir) will be "RECORDINGS"

To move any previously-created recordings and update their archive URLs, you need to do this on the dialers:

1) cd /var/spool/asterisk/monitorDONE/FTP
2) mv * ../MP3

If you are not using MP3 but something else, change line 2 appropriately. The FTP cronjob will pick up these new recordings and automatically re-send them to the archive server and update their URL link in vicidial.

[Trying]

Great instructions! I tried it and I didn't find any problems. The paths of my recordings are now showing!

The only remaining problem is that the seconds of the recordings are still not showing.

[Trying]

Just one correction: The path cd /var/spool/asterisk/monitorDONE/ftp should be cd /var/spool/asterisk/monitorDONE/FTP

[Kumba]

corrected

[racosta79]

I just want to add that there is one thing skipped in the ViciBox Redux Cluster Manual, it is to disable the SuSEfirewall2 or open the port to be used by the vsftp server.

Good luck!

[williamconley]

have you verified that this is necessary in the latest version of redux? It does not get opened automatically ..?

I think we avoided this problem by having the ftp server on the local subnet, and we always open the local subnet completely (our clustered servers always share a local subnet these days to allow easy local communication which is handled in a completely different manner than Internet traffic ... such as not blocking mysql/ftp/ssh ports locally).

But if that's not automatic, and isn't mentioned in the manual, it'd probably be a good note.