Inspect the VICIdial database and trace a test lead

01 / 05

1. Identify the database and version

1. Ask the administrator for the database name and a least-privilege read-only connection; do not assume the name is asterisk.
2. In the SQL client run SELECT DATABASE(), VERSION(); and confirm the selected database with the administrator.
3. Inspect the installed application and schema versions in Admin → System Settings or with your administrator's version inventory.

mysql --batch --skip-column-names vicidb -e 'SELECT db_schema_version FROM system_settings;'

Observed database schema version

Open to enlarge

You should seeThe selected name and server version identify the instance you are inspecting. In the November 2026 lab the configured database was vicidb; that is an observation, not a universal default.

02 / 05

2. Inspect tables and engines

1. Run SHOW TABLES; to see the tables present in this database.
2. Run SELECT TABLE_NAME, ENGINE FROM information_schema.TABLES WHERE TABLE_SCHEMA = DATABASE() ORDER BY TABLE_NAME;.
3. Run DESCRIBE vicidial_list; and DESCRIBE vicidial_lists; before writing a query against either table.

You should seeThe live column definitions and engine values are authoritative for this installation. A missing table or denied query means stop and check the selected database and grants.

03 / 05

3. Trace one test lead

1. In Lists → Show Lists open the disposable list and privately record its List ID. In authorized lead search open one known synthetic lead and record its Lead ID.
2. Open the verified read-only client: sudo mysql --defaults-file=/etc/vicidial-readonly.cnf. Check SELECT CURRENT_USER(), DATABASE(); before any query.
3. Inspect the columns, then replace12345,90001 and the date bounds in the query below. Use the test’s actual database/report timezone and an inclusive start/exclusive end.
4. Read the lead/list/campaign result first. Read outbound vicidial_log and inbound vicidial_closer_log separately; one lead can have several attempts and not every call path writes the same source.
5. Compare the candidate event with the independently known test time, campaign/list and saved disposition in User Stats. An empty result is a scoped observation, not proof that no call happened elsewhere. Type quit when finished.

SHOW COLUMNS FROM vicidial_list;SHOW COLUMNS FROM vicidial_lists;SHOW COLUMNS FROM vicidial_log;SHOW COLUMNS FROM vicidial_closer_log; SELECT l.lead_id,l.list_id,l.status AS current_lead_status,ls.campaign_idFROM vicidial_list AS l JOIN vicidial_lists AS ls ON ls.list_id=l.list_idWHERE l.lead_id=12345 AND l.list_id=90001; SELECT uniqueid,lead_id,list_id,campaign_id,call_date,status,length_in_secFROM vicidial_logWHERE lead_id=12345 AND list_id=90001  AND call_date >= '2026-11-07 00:00:00' AND call_date < '2026-11-08 00:00:00'ORDER BY call_date,uniqueid LIMIT 20; SELECT closecallid,lead_id,list_id,campaign_id,call_date,status,length_in_secFROM vicidial_closer_logWHERE lead_id=12345 AND list_id=90001  AND call_date >= '2026-11-07 00:00:00' AND call_date < '2026-11-08 00:00:00'ORDER BY call_date,closecallid LIMIT 20;

You should seeThe current lead relationship and each selected history source have been checked independently; current lead status is not substituted for a call’s recorded outcome.

Check the same event in User Stats →

04 / 05

4. Check custom data separately

1. Open the test list's Custom Fields screen and note the list ID and field labels.
2. Run SHOW TABLES; and find the exact table name for your verified numeric test list ID. For example, only if custom_90001 is present, run DESCRIBE custom_90001;.
3. Compare the installed schema with the official custom-fields document before integrating.

You should seeCustom fields are list-specific. Never infer that another list has identical columns or write directly to a table merely because it exists.

05 / 05

Recorded lab terminal checks

Recorded lab checks were run against the synthetic demo on November 4, 2026. These read-only observations supplement the configuration steps above; they do not establish that a call, route, recording or report workflow succeeded.

Recorded lab observation: List 90001 was active and associated with LAB01; active list does not override inactive campaign.

Recorded lab observation: Three synthetic lab leads were NEW. Status counts do not prove eligibility, successful dialing or lead handling.

Recorded lab observation: Schema metadata only; no application behavior tested.

Recorded lab observation: The hopper relation columns result describes the installed schema, not a completed workflow.

mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SELECT list_id, campaign_id, active FROM vicidial_lists WHERE list_id=90001 AND campaign_id='LAB01';"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SELECT status, COUNT(*) AS lead_count FROM vicidial_list WHERE list_id=90001 GROUP BY status ORDER BY status;"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SHOW COLUMNS FROM vicidial_list LIKE 'list_id';"mysql --defaults-extra-file=/etc/vicidial-readonly.cnf --batch vicidb -e "SHOW COLUMNS FROM vicidial_hopper WHERE Field IN ('campaign_id','list_id','status');"

Recorded lab terminal: lab list

Open to enlarge

Recorded lab terminal: lab list status counts

Open to enlarge

You should seeThe recorded lab command and output show exactly what the demo returned. Use the original workflow’s separate end-to-end acceptance checks before declaring success.