Auto dialled calls landing to paused agents after svn upgrad

[lvish]

Hi

We recently did a SVN update for a cluster of 4 servers from SVN version 2189 (VERSION: 2.10-417c BUILD: 141113-1431)

to SVN version 2491 (VERSION: 2.12-543a BUILD: 160313-0756).

Post upgrade we have an issue of calls landing to agent who is paused or in callback screen or in disposition screen. Issue will be more if we increase the DROP time out.

For issue isolation purpose, we downgraded to older version in one of the dialer server ie SVN ver 2189 . After downgrade no issue is observed.

Is anybody facing same issue ?!! Please suggest any workaround , fix or solution .

thanks in adavnce.

----

Lvish

-----

Dell 2950 --- 8 Cores -- 16GB RAM -- 500 GB X 2 RAID 1 -- DB server -- 1no.s -- Vicibox 6.0.4 -
Dell 2950 -- 8 Cores -- 8 GB ram -- 500 GB X 2 Raid 1 ---- Dialer server -- 3 no.s -- Vicibox 6.0.2 - Allo PRI card
---

[williamconley]

sounds like you did not upgrade your DB, just the vicidial code.

describe your upgrade process, and where you acquired the instructions

[lvish]

Upgrade process followed --usr/src/astguiclient/trunk/UPGRADE

On DB
mysql -f --database=asterisk < /path/from/root/extras/upgrade_2.12.sql

[williamconley]

perhaps you should read the UPGRADE doc a little more carefully. You are at v 2.10, but not the end of 2.10. so ...

you needed to upgrade 2.10 first. check the file, it likely had a db schema after yours. which means you needed to execute "the rest" of the commands from 2.10 before you executed 2.12.

[lvish]

yes i had to run 2.10.sql and then 2.12.sql otherwise i cant see campaigns or users in gui.

mysql -f --database=asterisk < /path/from/root/extras/upgrade_2.10.sql
mysql -f --database=asterisk < /path/from/root/extras/upgrade_2.12.sql

Issue faced is only on latest version of agent interface, on the downgraded version we are not facing any issue. I think there is something to do with new version .

[williamconley]

did you reboot after upgrade?

did you include sample files during the perl install? (if "no" do it again now with "yes" and rebuld all the conf files)

also verify that your asterisk version is still set properly in admin->servers for each server.

[lvish]

Yes Servers were rebooted after upgrade.

Perl ./install.pl will not ask for any sample files creation.

Version we rechecked again , its perfect.

[williamconley]

Code: Select all

perl /usr/src/astguiclient/trunk/install.pl --help | grep sample

probably found your problem.

[lvish]

ok thanks will try and update shortly.

[lvish]

no luck.. issue still persist.

But one server where i have down graded to lower 2.10 version is not facing any problem. Is it a bug in new version ??

regds

[Merchant007]

after doing sql upgrade and svn upgrade did u Rebuild conf files ? from admin

[lvish]

yes ,rebuild on all servers is done.

which is SQL upgrade -- are u referring to schema upgrade mentioned below?

mysql -f --database=asterisk < /path/from/root/extras/upgrade_2.10.sql
mysql -f --database=asterisk < /path/from/root/extras/upgrade_2.12.sql

thanks

[williamconley]

And for clarity: These are standalone servers, not a cluster ... right?

[lvish]

This is a cluster one db and 3 dialer cum web servers.

[williamconley]

if you downgrade a single server in a cluster and it begins to work correctly, then the only conclusion I can draw is that you've NOT upgraded the DB. If you don't need to downgrade the DB (which can only be done by restoring from an old copy) to make one of the dialers work with old scripts, your DB is not really being updated.

Was there any output from the sql script's execution against the DB?

Did the db_schema field get updated? (what was the final db_schema value?)

[lvish]

Is there anything else to be done to upgrade db apart from schema upgrade in db ? .

[williamconley]

Sometimes a reboot may be required, but otherwise, no.

Was there any output from the sql script's execution against the DB?

Did the db_schema field get updated? (what was the final db_schema value?)

... Of course, I've NEVER had paused agents receive calls. So this could be a bug in your installation (only) do an anomaly present only in your installation, how were your servers installed?

[lvish]

Reboot was done for all servers.

Vicibox 6.0.2 installed using ISO image.

[williamconley]

6.0.2 was short-lived because it had a couple bugs. While I doubt they were related, you could check the release discussion and see if you get lucky.

Otherwise, full re-install and copy your leads/recordings/lists and reconstruct your campaigns and everything else ...

Or troubleshoot that paused agents getting calls issue directly to see what's really going on.