vicidial.org

Hi Team,

We are trying to install vicidial version 6.0.3 on a machine. Even though we use old .iso from vicidial archives, build information

"VERSION: 2.14-718a
BUILD: 190902-0839
© 2019 ViciDial Group"

gets displayed on left side bottom of the page. Where as we want old build information getting displayed there with old interface.

We can not understand how it is happening, that new version and build information is coming.

Ok guys,


I have figured the most stuff out. But still key pieces are missing.

What i did this time around was, as mentioned in the installation guide there are three steps 1) os-install 2) yast lan (network settings) 3) vicibox-express.

What i did this time around is i skipped the step 2 and directly installed vicibox-express after os-install and surely it installed everything to the old version.

I am using Vicibox 6.0.3 iso downloaded from vicibox http://download.vicidial.com/iso/vicibo ... r/archive/

Now again, the problem i am having is, this is the build information which came after installing the mentioned way in admin.php,


VERSION: 2.10-452a
BUILD: 141111-0554
© 2014 ViciDial Group

While testing the installation method in virtual machine, the build information in admin.php came as,

VERSION:2.12-515a
BUILD:151007-2224
© 2015 Vicidial Group.

Now from reading the posts here, it has something to do with SVN version controling and updating about it in /usr/src/astguiclient/ .

But from what i have gathered, the version you get from "svn info" and build information displayed on admin.php are different.

So the build i am looking for is,

VERSION: 2.12-505a
BUILD:150806-1348
© 2015 Vicidial Group.


Can someone please please tell me, how to get this build from SVN archive ?

1) Do not answer your own posts. This usually results in nobody seeing it as "unanswered" so everyone skips over it for a while until they get curious about what the question/answer was. If nobody has commented on your post, just edit it instead.

2) Do not use vicibox express. It's not as thoroughly tested or maintained, and not nearly as robust, for instance:

3) In some of the old standard installers, you could choose the version of Vicidial to install. In vicibox express it will always install the latest if it has internet access to upgrade from what's on the CD.

4) For clarity: The "installer" determines ONLY the environment for Vicidial, not vicidial itself. The installer will always try to install the latest version of Vicidial. But the Asterisk, MySQL, Operating system versions are based on the installer.

5) If you require a specific version of Vicidial, you can upgrade or dump the /usr/src/astguiclient/trunk folder and download a fresh SVN revision level from the svn server. svn commands to upgrade to a specific SVN revision level, however, do not include the Vicidial Version, but the SVN revision level.

6) If you were to check the DB you are obviously trying to restore, you will likely find that the system settings has a revision level that *May* match what you need. If not, you can try an SVN reader or just experiment with the svn revision level until you find the admin.php with the value you need in it. Keep updating to the next number (or jump 10 at a time ...) until you can grep the admin.php inside the /trunk/www/admin folder and find the right version / build information.

7) Once SVN matches, you perform an "install.pl" on the /trunk folder and that installation process will put all the files where they need to be, and if that matches your database and the asterisk version matches, now all you need to do is modify the "Admin->Server", "Admin->System Settings", sip.conf and /etc/astguiclient to match your new setup (IP address in several places, perhaps domain name or two ..., asterisk version ...).

8 ) Some find it easier to just upgrade the Database to the latest version (UPDATE document in the /trunk folder) and then use the latest .iso installer instead. Then you get a brand new version of Vicidial and all your old data, too. But: Certify that the system works before you restore the Database. Back up that working blank system for reference. That way if it doesn't work properly after your restore you know it's the restore process that broke something and not just a bad install in general. We even like to change the DB name and keep it as a spare so we can copy the server and system setting tables (since those were working ... no need to manually edit them, just steal them from the working blank!).

Hi Williamconley,


Thanks for your reply and support.

If not, you can try an SVN reader or just experiment with the svn revision level until you find the admin.php with the value you need in it. Keep updating to the next number (or jump 10 at a time ...) until you can grep the admin.php inside the /trunk/www/admin folder and find the right version / build information.


I think what you said above might be the best approach. i read SVN page of vicidial, i said about using RapidSVN, which i have downloaded. I am looking to explore vicidial repository just to have basic grasp so i can do SVN revision as you said in your previous point. But if i try to connect to it using svn://svn.eflo.net:3690/agc_2-X/trunk url, username password prompt comes.

I have heard about SVN, have used GIT extensively. Still i am almost awake since 2 days and facing a kind of deadline. so if you can give me some quick instruction or point to some resource which will get me started on both SVN and Vicidial repos. I would be truly thankful

if you try to "connect" to SVN, you must have a user/pass. But if you just svn co (checkout) you don't need user/pass in this system. The information about SVN available on the Vicidial site is very stunted and meant for specific users, but it's just an SVN repository. find a general information site about svn and how to use any of the dozens of clients available for browsing, or just use the command line svn client and begin checking out revision levels until you hit the jackpot. Price-is-right style. lol