vicidial.org

vicidial from vicibox: VERSION: 2.10-448a BUILD: 140706-0927

all user groups have empty allowed campaign list, i cannot choose nor set all, this happened during server tuning and I have no Idea why and when. just they disapeared. any user cannot see any campaign on the campaign tab even though it is allowed to see and modify them

please help

What is "Server Tuning"? What did you do? If you were editing files outside the web GUI, you'll need to restore them. If you did not keep copies of the originals, never fear: You can just re-install from the trunk folder. It'll bring all preferences forward but overwrite any customized vicidial files ... back to the originals. "perl install.pl"

And are you sure that these agents are in a user group that has a campaign allowed?

And please post the full name of your installation .iso (hint: it's not vicibox 6.0 ... it's vicibox 6.0.X). It can make a difference.

I do not remember which iso it was, I did not edit any files, just changes in configuration.

The server was installed on august 2014 and yesterday upgraded by zypper up to latest packages. Then I tried to trunk upgrade vicidial but something whent wrong and upgrade was broken so i restored all backups from the one I've done as preupgrade step. I am sure that admin group with level 9 had rights to see all campaigns before. Now editing db entries in vicidial_user_groups table also does not help (null, [space]-ALL-CAMPAINGNS- -, camp name) nothing helps

Why did you try to upgrade the system? Was something broken? (IE: If this was broken before the upgrade, our conversation is quite different ... and if you're the type of sysadmin who upgrades "because it's the right thing to do", that's also useful information!).

When you say you restored the backups, I presume you mean you restored the vicidial configuration/script/web pages, but not the installed OS (ie: Ghost restore? Drive Image? or vicidial's "backup.pl") ... did you also restore the /etc/ config files? (Which may have had revisions due to your OS upgrade?)

Upgrading / restoring are often tricky with systems that interact on this level. Do you know which packages were upgraded?

When you log in via SSH, there is a Splash Screen welcoming you to your system. What is the last line of that welcome splash? I bet it has your Vicibox Distro Version on it ...

I am not such a sysadmin on other systems which I administer, this box was kind of experimental so I made decision to update it and vicidial do latest packages. this upgrade was clean and working. Updating just vicidial with svn up and perl install.pl probably broke sth, and when I tried to restore probably it wont restore all to previous state.

ATM I decided to move broken db/config aside and make new vicibox-install AIO version. Now everything works OK (after first day of new trials)

williamconley wrote:When you log in via SSH, there is a Splash Screen welcoming you to your system. What is the last line of that welcome splash? I bet it has your Vicibox Distro Version on it ...

6.0.what?

ATM this is what after login I see

- ViciBox Redux v.6.0-beta-

nysander wrote:ATM this is what after login I see

- ViciBox Redux v.6.0-beta-

Is this after the reinstall? If so, you may want to try again with 6.0.3 (latest! with several bugs removed).

whole system was not reinstalled, I have only done zypper up of whole packages as I said above and on /usr/src/astguiclient svn up, renamed broken db and then vicibox-install

nysander wrote:... and then vicibox-install

Um ... vicibox install is only done when first installing the packages. "perl install.pl" is for re-installing the latest version of vicidial from the source folder /usr/src/astguiclient/trunk

I'm not sure if it would break anything or not. But it could re-add DB entries which could be a challenge.

perl install.pl broke my setup and I had to recover my backup (which also failed) so I've tried plain install (with vicibox-install) on clean db and for now everything looks ok.

FYI: If perl install.pl broke your setup, there's something wrong with your setup. You can "perl install.pl" five times a day with no damage. It just copies the existing scripts back where they belong. If you're trying to get a "good install", you'll need to test that. If install.pl breaks something, you'll need to identify what and resolve that issue or you'll never be able to upgrade (and it's likely something's actually broken, to boot).

thanks for sugestions, this is experimental setup so I am aware of possible problems. when my experiments will be succesful I will do plain install on another better server and then clone the setup to it, hopefuly without problems.

nysander wrote:thanks for sugestions, this is experimental setup so I am aware of possible problems. when my experiments will be succesful I will do plain install on another better server and then clone the setup to it, hopefuly without problems.

When you get the hang of it, moving an install to a new machine is merely a matter of moving a Database and making adjustments for the new IP address by running the ip update script (and possibly editing the sip.conf externip= value). If all you're moving is the "configuration/setup". Audio files and client recordings would need to be copied also for a production server move.

great hints William, thank you very much with your assistance

I will inform you when my GSM Vicidial setup will be on production (after few months of works being suspended)

nysander wrote:great hints William, thank you very much with your assistance

I will inform you when my GSM Vicidial setup will be on production (after few months of works being suspended)

I would recommend you link your GSM system to a "stock asterisk box" and leave the Vicidial system as a remote connection to it. This way your Vicidial server is "generic" and can be easily swapped out.

Also, you can connect more than one Vicidial to your GSM (or more than one GSM to your Vicidial). Since Vicidial itself requires no special hardware and can be installed quickly and even have a catastrophic recovery managed quickly ... it's a shame when that model causes "problems" due to excessive hardware requirements or customization.

Keeping those add-ons separate can make your future much brighter from an upgrade and recovery standpoint as well as for expansion.

I have got this setup working as separate servers remembering your suggestions and enormous help at Aug 14 when I tried to make it work as Automatic Survey Setup. Now it is time to try this for people outbound calling.

this setup looks like this

4-5 USB GSM Dongles > GSM Gateway Server (plain asterisk) > SIP <------> SIP Carrier > Vicidial All in One Server > Softphones ... etc. (in very few words)