CLUSTER

[hanidhakwani]

Hello,
I have a cluster installation, 1 DB / WEb and 1 DIALER, it works very well, I added another DIALER, the agent logs in and I can see that it enters into conference but the auto calls to the car do not not launch on the 2 DIALER, the trunk of the campaign is correctly configured on the 2 dialer.
your help please

[williamconley]

As this is clearly an installation question, the installer that you used would be a very useful thing to know.

Given the odds, of course, you installed a more recent version of Vicidial on the new server and the new code does not work with the old database schema and the scripts fail.

So: Add "Vicibox X.X.X" to the description for the DB/Web and again for each of the 2 Asterisk/Dialer servers. If you're not sure, most of the time the version (or most of it ...) is available in the splash/motd screen when you log in. Additionally, the SVN revision level for each of the servers is available like this:

Code: Select all

cd /usr/src/astguiclient/trunk/; svn info;

If those are different, you'll want to get the SVN revision level from the DB/Web and force the new Dialer to the same version:

Code: Select all

cd /usr/src/astguiclient/trunk/; svn up -r XXXX;

Then Verify your Asterisk Version is correct in both /etc/astguiclient.conf and admin->servers for this server. And post them here as there are often red flags with some install bugs that get the version wrong. For instance, if the asterisk version in astguiclient.conf is "11", it should actually be "11.X". When you run through perl install.pl, there is a list of asterisk versions presented, and you must choose one and enter it exactly as displayed, including any dots or Xs. In Admin->Servers it's often something like "11.25.1-vici". The version of asterisk is available by entering at the CLI:

Code: Select all

asterisk -V

Then re-install the Vicidial scripts on your new dialer, now that you have the right ones in the SVN trunk folder:

Code: Select all

cd /usr/src/astguiclient/trunk/; perl install.pl --copy_sample_conf_files;

This will take you through the installation, verifying the Asterisk version on the way past, but it will also obliterate any customizations you've made to the asterisk .conf files. You'll need to re-modify those. Usually the only thing that should be customized is the externip value in sip.conf.

[hanidhakwani]

Thanks for your reply, here are the details:

Vicibox v.8.1.2 in all server

DB/WEB :
Repository UUID: 3d104415-ff17-0410-8863-d5cf3c621b8a
Revision: 3247
Node Kind: directory
Schedule: normal
Last Changed Author: mattf
Last Changed Rev: 3247
Last Changed Date: 2020-05-15 19:57:07 +0200 (Fri, 15 May 2020)


Dialer 1 (is OK) :
Repository UUID: 3d104415-ff17-0410-8863-d5cf3c621b8a
Revision: 3047
Node Kind: directory
Schedule: normal
Last Changed Author: mattf
Last Changed Rev: 3047
Last Changed Date: 2018-09-30 16:14:35 +0200 (Sun, 30 Sep 2018)


Dialer 2 ( KO):
Repository UUID: 3d104415-ff17-0410-8863-d5cf3c621b8a
Revision: 3047
Node Kind: directory
Schedule: normal
Last Changed Author: mattf
Last Changed Rev: 3047
Last Changed Date: 2018-09-30 16:14:35 +0200 (Sun, 30 Sep 2018)

version of asterisk : Asterisk 13.21.1-vici

I don't see what doesn't work for and what should I do?

[williamconley]

the svn revision level on the DB/Web server is different than that of the other two. Which server(s) work, and which do not? Or was that a typographical error of a 2 instead of a 0?