The agc/vicidial.php file is the heart of the VICIdial agent interface. If you are running an outbound call center or a blended contact center using this open-source software, this specific PHP script is where your agents spend 99% of their workday.
Understanding how agc/vicidial.php functions, how to optimize it, and how to troubleshoot common issues is essential for maintaining high productivity and a seamless user experience. What is agc/vicidial.php?
In the VICIdial directory structure, the agc folder stands for "Agent Graphical Console." The vicidial.php file within this folder is the primary application script that generates the agent's web-based dashboard. When an agent logs in, this script handles:
User Authentication: Validating agent credentials and campaign permissions.
Interface Rendering: Displaying the dialer controls, customer information forms, and script windows.
Real-Time Communication: Facilitating the connection between the web browser and the Asterisk telephony engine.
Data Logging: Recording call dispositions, talk time, and pause durations. Key Features of the Agent Interface
The agc/vicidial.php interface is designed for speed and high-volume calling. Key components include:
Customer Information: Automatically populates fields from the database when a call is delivered.
Scripting: Displays dynamic scripts to guide the agent through the conversation. agc vicidial.php
Manual Dialing: Allows agents to manually input numbers if permitted by the campaign settings.
Dispositions: A customizable list of outcomes (e.g., Sale, Not Interested, Answering Machine) that the agent must select to complete the call.
Callbacks: A dedicated area for agents to schedule and manage future follow-ups. Optimization Tips for Call Center Managers
Because agc/vicidial.php relies heavily on JavaScript and AJAX to communicate with the server without reloading the page, performance bottlenecks can occur. Use these tips to ensure a smooth experience: 1. Hardware and Network
Low Latency: Ensure agents have a ping under 50ms to the server to avoid "lag" when clicking buttons.
RAM Matters: Modern browsers like Chrome can be memory-intensive; ensure agent workstations have at least 8GB of RAM. 2. Server-Side Configuration
Keep it Local: If possible, host the web server on the same local network as the agents to reduce network hops.
Database Tuning: VICIdial is database-heavy. Regularly optimize your MariaDB/MySQL tables to prevent slow queries from hanging the vicidial.php interface. Troubleshooting Common agc/vicidial.php Issues
If your agents report that the screen is "white" or "stuck," look into these common culprits: The agc/vicidial
Invalid Login Credentials: Ensure the User ID and Password match the User entry in the Admin portal.
Campaign Availability: An agent cannot log into vicidial.php if there are no active campaigns assigned to their User Group.
Browser Cache: Sometimes, a browser update or a server-side change requires clearing the cache. Have agents try an "Incognito" or "Private" window first.
SSL Certificate Errors: If you are using HTTPS, an expired or self-signed certificate can block the AJAX requests necessary for the dialer to function. Security Best Practices
Exposing your agc/vicidial.php to the open internet is a major security risk. Hackers frequently scan for this specific URL to attempt "brute force" attacks on agent accounts.
IP Whitelisting: Only allow access to the /agc/ directory from known office IP addresses.
Change Default Paths: Some administrators choose to rename the folder or use an alias in Apache to hide the interface from generic bots.
Two-Factor Authentication (2FA): While not native to the basic script, implementing a 2FA layer via your web server configuration adds a vital shield of protection.
If you're looking to dive deeper into customizing the agent experience, I can help you with: Customizing the CSS to match your company branding. // Main logic if ($phone_number && $lead_id) $agc_data
Setting up Web Form integration to pass data to an external CRM.
Troubleshooting specific error codes like "No active campaign."
Vicidial’s vicidial.php accepts many parameters (e.g., phone, exten, callerid). An attacker could potentially inject Asterisk commands if input is not sanitized. Verify your version is up-to-date (release 2.14+ includes strong sanitization).
<?php // agc_vicidial.php // Version: 1.0 // Description: AGC integration script for Vicidialinclude_once('/etc/astguiclient.conf'); include_once('/usr/share/php/DB.php');
// Connect to Vicidial DB $db = DB::connect("mysql://$conf['db_user']:$conf['db_pass']@$conf['db_host']/$conf['db_name']");
// Retrieve incoming variables (from GET/POST or STDIN) $phone_number = $_GET['phone_number'] ?? ''; $lead_id = $_GET['lead_id'] ?? 0; $campaign_id = $_GET['campaign_id'] ?? '';
// Function to query AGC server function get_agc_content($lead_id, $campaign_id) $agc_api_url = "http://agc-server.local/api/v1/content"; $payload = json_encode([ 'lead_id' => $lead_id, 'campaign' => $campaign_id ]);
$ch = curl_init($agc_api_url); curl_setopt($ch, CURLOPT_POST, true); curl_setopt($ch, CURLOPT_POSTFIELDS, $payload); curl_setopt($ch, CURLOPT_HTTPHEADER, ['Content-Type: application/json']); curl_setopt($ch, CURLOPT_RETURNTRANSFER, true); $response = curl_exec($ch); curl_close($ch); return json_decode($response, true);// Main logic if ($phone_number && $lead_id) $agc_data = get_agc_content($lead_id, $campaign_id);
// Example: Override CallerID with AGC provided value if (!empty($agc_data['dynamic_callerid'])) echo "callerid_number=" . $agc_data['dynamic_callerid'] . "\n"; // Example: Inject pre-call audio file if (!empty($agc_data['audio_file'])) echo "custom_audio=" . $agc_data['audio_file'] . "\n"; // Log to AGC database $insert = "INSERT INTO agc_call_log (lead_id, phone_number, campaign_id, response_data, call_time) VALUES (?, ?, ?, ?, NOW())"; $db->query($insert, [$lead_id, $phone_number, $campaign_id, json_encode($agc_data)]);
else // Fallback to standard Vicidial dialing echo "status=continue\n"; ?>
