vicidial.org

Hi typically before, I would be able to take a backup of a database on one instance of ViciBox, and clone it so to say on another machine for backup.

So in short, Will I be able to backup database from,
||Version: 2.8b0.5|| DB Schema Version: 1350 || ViciBox.x86_64-4.0.3.preload.iso || 1.4.44-vici|| BUILD: 130510-1350

And then load it into?

||VERSION: 2.8-409a|| DB Schema Version: 1355 || ViciBox5.x86_64-5.0.2.preload.iso || 1.4.21.2|| BUILD: 130809-1410

Also, I thought that this new version had asterisk 1.8? That what I get with doing a express install?

Question 1) Yes you can move the DB from DB Schema Version: 1350 to DB Schema Version: 1355. but you will need to upgrade the db by running the sql commands to upgrade from the earlier version to the later.

Question 2) We've found a couple boxes that had the wrong Asterisk version in the server's asterisk field after install. Have you started asterisk from the command line to see what version you actually have, or are you just going by "admin->servers" supplied values?

Question 2, I am just going by the supplied values.
Console Check.
Connected to Asterisk 1.8.23.0-vici currently running on linux

I am scared to upgrade a production system. I don't want to break anything.

There was a bug in the Beta versions of ViciBox v.5.0 that had that issue of saying it was 1.4 but was really 1.8. But it was fixed in the v.5.0.1 release. Notes on that bug are in the bugfix thread.

I'm guessing he did a MySQL dump and never changed the asterisk versions. Since the old system was v.4 it would have been setup with asterisk as 1.4. You need to go into the servers section in the web page and set the asterisk verstion to 1.8. You can also run vicibox-upgrade.pl to take care of the schema updates for you. It will even create a vicibox table.

Actually I have not done any upgrade yet. The v5.0 Box was the pre load ISO vanilla install, straight out of the box it said the wrong asterisk version.

Now as far as the production 4.0 box, I just wanted backup that database and copy the sql file to 5.0 machine and upload it, suck it in whatever you want to say. I now know it will not work.

Just did a preload 5.0.2 install and can't duplicate your issue. Probably the order in which you are doing things or something.

Hmm must be, thank you for your efforts Kumba.