vicidial.org

After migrating from one vicidial database v8 to another v9, everything is working well with one exception: Callback list

The data imported, however in the UI, it seems that all the records in the callback list are associating to the fake lead_id 1 (which is obviously not what our vicidial_callbacks data contains). I've affirmed that the respective callback_id, lead_id, list_id, campaign_id all exist in every related table we can identify.

Below are the callback report and the first record detail.



In attempting to isolate this problem we evaluated the Active Callback page and noticed the HTML payload obtained from invoking CalLBacKLisT in vdc_db_query.php is different between our two systems. In our working v8 legacy system, the first records correctly:

Clark-!T--!T-6057690838-!T-43907-!T-1100593-!T-MANUAL-!T-LIVE-!T-2019-10-18 10:51:03-!T-2019-10-21 07:00:00-!T-c/b n/a
pop. 129-!T-1-!T-

However in the new v9 system the callback_id and lead_id identifiers are all pointing to the erroneous test record:

Matt-!T-lead01-!T-7275551212-!T-9-!T-1-!T-MANUAL-!T-L-!T-2019-09-09 09:58:02-!T-2019-09-23 07:00:00-!T-ASKED 4
C/B-!T-1-!T--!T--!T-

Furthermore, as one might imagine, the Callback data is not editable.

vicidial.php version and build?

VERSION: 2.14-718a
BUILD: 190902-0839

Try upgrading to the latest svn/trunk revision, we recently fixed an issue like that one.

VERSION: 2.14-587c BUILD: 190902-0914

Issue remains. Pretty sure I have a screwed up database key somewhere, just not clear where that would be.

The latest build of vicidial.php should be 191018-0904, so I'm not sure you are upgrading svn/trunk properly if that isn't your build.

Yes; thanks! The latest vicidial UI cured the issue. VERSION: 2.14-722a; BUILD: 191101-1149

Took a bit to figure out how to upgrade, here are our tech notes:
On database, had to upgraded from db_schema_version 1575 to 1578; had to dissect and partial extract of the file upgrade_2.14.sql since it assumes version upgrade from 1478. Curious that we had a partial update; perhaps because this Vicidial was installed just a month back.
On web/voip server, the upgrade process worked as described here http://www.vicidial.org/VICIDIALforum/viewtopic.php?t=16326.