Vicidial traditionally uses over TCP to reduce overhead, but agc is often a misnomer for legacy or direct execution modes. However, in modern Vicidial clusters:
Proper file permissions are essential. Set directories to 755 or 750 and files to 644 , while avoiding world-writable 777 permissions. Ensure the web user (e.g., www-data or apache ) owns the AGC folder, and check SELinux contexts if using CentOS or AlmaLinux to allow Apache and PHP to read and write as needed.
The canonical process listing looks like: agc vicidial.php
The page establishes a persistent connection with the server to receive real-time updates regarding new calls or changes in campaign settings.
: Integrates external webforms (like CRM search pages) and internal scripts to guide agents through conversations. Common Use Cases & Configuration Vicidial traditionally uses over TCP to reduce overhead,
: Open the browser console (F12) to identify the specific error. This is often caused by mixed content issues (trying to load HTTP assets over an HTTPS connection) or a misconfigured server_ip setting in the VICIdial system settings. 3. High Server Load Issues
The agc/vicidial.php script renders a highly dense, functional dashboard that handles several critical workflows: Ensure the web user (e
The AGC uses phone credentials (login_user and login_pass) for initial authentication. After successful phone login, agents proceed to a secondary screen where they select or confirm their campaign affiliation.
When the call ends, the screen locks into a "Dispo" status until the agent selects a hangup cause, updating the lead status via backend PHP queries. Key Configuration Options in the Admin Panel