ViciBox v.5.0.3 Released!

First the links:
http://download.vicidial.com/iso/vicibo ... -5.0.3.iso
http://download.vicidial.com/iso/vicibo ... -5.0.3.md5
http://download.vicidial.com/iso/vicibo ... reload.iso
http://download.vicidial.com/iso/vicibo ... reload.md5
http://download.vicidial.com/iso/vicibo ... -5.0.3.iso
http://download.vicidial.com/iso/vicibo ... -5.0.3.md5
http://download.vicidial.com/iso/vicibo ... reload.iso
http://download.vicidial.com/iso/vicibo ... reload.md5
It is based on the following softwares:
OpenSuSE v.12.3 "Dartmouth" built with SuSE Studio
Linux Kernel v.3.7
ViciDial SVN Trunk Rev 2011
Asterisk v.1.8.23.0-vici
DAHDI v.2.6.1
libPRI v.1.4.14
Amfletec VoiceSync v.1.3.2
OpenR2 v.1.3.2
ZoiperWeb v.2.8.15810
Apache v.2.2.22
MariaDB v.5.5.29
PHP v.5.3.3
phpMyAdmin v.4.0.4.1 (optional)
To the Sangoma T1 users and VoiceTime users:
Sangoma products are not supported at this time due to kernel compatibility or DAHDI compatibility issues. If you want to use a Sangoma T1 card or their VoiceTime modules you will need to work with ViciBox v.4 or v.3. We have reached out to Sangoma about getting driver updates and have not gotten a response. If you want to use a T1 with ViciBox v.5 we would recommend you look at a Digium card. The Amfletec VoiceSync PCI-Express timers are also very good at doing their job and are supported without issue.
What is new and improved:
The elusive --restore option is now written and tested. You pass this as a flag to vicibox-install I.E. 'vicibox-install --restore'. THIS IS NOT A BACKUP TOOL!!! It is designed to make replacing a server in a cluster easier. It will not back up or restore custom configuration files, recordings, audio files, crontab entries, or anything that a fresh out-of-the-box ViciBox installation doesn't do automatically. The intent is to give you a method for upgrading servers with less issues or replacing failed servers quickly.
There is now a vicibox-upgrade.pl script. This will create a vicibox table on the database, and then insert server records for additional servers that it is ran on while keeping the SVN version in sync. It is version agnostic meaning you can run it on older ViciBox installs without issue. It needs to be ran on the database first before all other servers. This will create the ViciBox table on the database if it does not exist, update the DB schema, and then update the SVN version in the vicibox table. When the upgrade script is ran on a dialer or web server then it will also update the local SVN code to the one that was used on the Database. You will still need to read the UPGRADE document located at /usr/src/astguiclient/trunk/UPGRADE to see if there are any local configuration file changes needed or changes to the crontab, etc.
DB Slave set-up has been tested and works now. On master databases you will need to create a slave user by either running the vicibox-upgrade.pl script or issuing the below SQL: grant replication slave,replication client,select,reload on *.* to 'slave'@'%' identified by 'slave1234';
This will create a slave user with the username 'slave' and password 'slave1234'. Please make sure this matches what is present in your vicibox table for the master database. It is recommended to run the DB Slave setup after hours as it can potentially be a very long process.
Make sure to read the ViciBox v.5.0 patch and bugfix thread to make sure you have all applicable updates and fixes installed! If not, feel free to post a new thread and we will dive into the issue.
http://download.vicidial.com/iso/vicibo ... -5.0.3.iso
http://download.vicidial.com/iso/vicibo ... -5.0.3.md5
http://download.vicidial.com/iso/vicibo ... reload.iso
http://download.vicidial.com/iso/vicibo ... reload.md5
http://download.vicidial.com/iso/vicibo ... -5.0.3.iso
http://download.vicidial.com/iso/vicibo ... -5.0.3.md5
http://download.vicidial.com/iso/vicibo ... reload.iso
http://download.vicidial.com/iso/vicibo ... reload.md5
It is based on the following softwares:
OpenSuSE v.12.3 "Dartmouth" built with SuSE Studio
Linux Kernel v.3.7
ViciDial SVN Trunk Rev 2011
Asterisk v.1.8.23.0-vici
DAHDI v.2.6.1
libPRI v.1.4.14
Amfletec VoiceSync v.1.3.2
OpenR2 v.1.3.2
ZoiperWeb v.2.8.15810
Apache v.2.2.22
MariaDB v.5.5.29
PHP v.5.3.3
phpMyAdmin v.4.0.4.1 (optional)
To the Sangoma T1 users and VoiceTime users:
Sangoma products are not supported at this time due to kernel compatibility or DAHDI compatibility issues. If you want to use a Sangoma T1 card or their VoiceTime modules you will need to work with ViciBox v.4 or v.3. We have reached out to Sangoma about getting driver updates and have not gotten a response. If you want to use a T1 with ViciBox v.5 we would recommend you look at a Digium card. The Amfletec VoiceSync PCI-Express timers are also very good at doing their job and are supported without issue.
What is new and improved:
The elusive --restore option is now written and tested. You pass this as a flag to vicibox-install I.E. 'vicibox-install --restore'. THIS IS NOT A BACKUP TOOL!!! It is designed to make replacing a server in a cluster easier. It will not back up or restore custom configuration files, recordings, audio files, crontab entries, or anything that a fresh out-of-the-box ViciBox installation doesn't do automatically. The intent is to give you a method for upgrading servers with less issues or replacing failed servers quickly.
There is now a vicibox-upgrade.pl script. This will create a vicibox table on the database, and then insert server records for additional servers that it is ran on while keeping the SVN version in sync. It is version agnostic meaning you can run it on older ViciBox installs without issue. It needs to be ran on the database first before all other servers. This will create the ViciBox table on the database if it does not exist, update the DB schema, and then update the SVN version in the vicibox table. When the upgrade script is ran on a dialer or web server then it will also update the local SVN code to the one that was used on the Database. You will still need to read the UPGRADE document located at /usr/src/astguiclient/trunk/UPGRADE to see if there are any local configuration file changes needed or changes to the crontab, etc.
DB Slave set-up has been tested and works now. On master databases you will need to create a slave user by either running the vicibox-upgrade.pl script or issuing the below SQL: grant replication slave,replication client,select,reload on *.* to 'slave'@'%' identified by 'slave1234';
This will create a slave user with the username 'slave' and password 'slave1234'. Please make sure this matches what is present in your vicibox table for the master database. It is recommended to run the DB Slave setup after hours as it can potentially be a very long process.
Make sure to read the ViciBox v.5.0 patch and bugfix thread to make sure you have all applicable updates and fixes installed! If not, feel free to post a new thread and we will dive into the issue.