When an agent takes a call, agc/vicidial.php records the event in the vicidial_live_agents table. Best Practices and Security
| Version | Date | Changes | |---------|------|---------| | 1.0 | 2024-01-15 | Initial release | | 1.1 | 2024-03-20 | Added carrier failover logic | | 1.2 | 2024-06-10 | Implemented Redis caching |
The AGC listens for agent state changes (e.g., clicking "Pause" for a break) and updates both the database ( vicidial_live_agents ) and the Asterisk queue member's pause status.
asterisk -rx "manager show events" # capture an event perl /usr/share/astguiclient/AGI/agc vicidial.php --test-event="Event: AgentConnect..." agc vicidial.php
Always bind your agc/ portal to an SSL/TLS certificate (such as a free Let's Encrypt cert). Modern web browsers will block WebRTC audio components and microphone permissions if vicidial.php is accessed over an insecure HTTP connection. 5. Troubleshooting Common Errors "No shorthand user found" / "Invalid Credentials"
If the interface loads but hangs indefinitely before showing the login fields, JavaScript or network firewalls are usually blocking the assets.
Which deliverable would you like next?
Facilitating the connection between the web browser and the Asterisk telephony engine.
: Processes initial phone and user credentials to establish a session.
It processes the input and generates commands (often via the Asterisk Gateway Interface, or AGI) that tell the physical phone system what to do. When an agent takes a call, agc/vicidial
This directory is the heart of the Vicidial web application. It contains the core PHP scripts that interface with the Asterisk PBX software. While the "Vicidial Agent Screen" is the user interface, the files in the agc directory are the engine processing the logic.
This is the most infamous error seen on vicidial.php . It means the agent's local computer clock differs significantly from the Vicidial database server clock.
The Ultimate Guide to agc/vicidial.php: Configuration, Architecture, and Troubleshooting Modern web browsers will block WebRTC audio components
Automatically populates fields from the database when a call is delivered.
Never allow agents to log in via standard HTTP. WebRTC webphones strictly require a secure HTTPS origin to access browser microphone permissions. Ensure your Apache configuration forces all traffic hitting the /agc/ directory to redirect to port 443. Implement IP Whitelisting