How to Install VICIdial 8 ( works same for Vicibox 7, Vicibox 8, Vicibox 9)

Introduction
Are you looking for a complete guide on how to install VICIdial 8 and configure it for your call center?
VICIdial is an open-source contact center platform used by BPOs, telemarketing companies, customer support teams, and sales organizations to manage inbound and outbound calls.
A properly configured VICIdial system can provide predictive dialing, agent management, call recording, campaign reporting, IVR, and VoIP integration.
However, installing VICIdial is only the first step. To make the system fully functional, you also need to configure the server, networking, telephony, SIP connectivity, agents, campaigns, and security.
In this guide, we explain the complete installation workflow, from preparing the server to testing your first call.
Important version note: This guide covers the legacy VICIdial 8 / ViciBox 8.1 installation approach. ViciBox 8.1 is an older release. For a new production deployment in 2026, use a currently supported ViciBox release unless you specifically require version 8 for compatibility or migration purposes. Legacy software may lack security fixes and modern compatibility. The installation concepts below remain useful, but the exact commands and configuration options can differ by release.
What Is VICIdial 8?
VICIdial is a contact center application built around Asterisk telephony technology. ViciBox is the official installation distribution that bundles the operating system and tools needed to deploy VICIdial.
A typical installation contains:
- ViciBox: The operating system and installation environment.
- VICIdial: The contact center application and campaign management interface.
- Asterisk: The telephony engine that handles calls.
- MariaDB/MySQL: The database used for application data.
- Web server: Provides the administrative and agent interfaces.
- SIP trunk: Connects the system to a VoIP provider.
- Agents and campaigns: Define who handles calls and how calling operations work.
For the historical ViciBox 8.1 installation, consult the official ViciBox 8.1 installation manual.
For current deployment documentation, visit the official ViciBox documentation.
Requirements Before Installing VICIdial 8
Before starting the installation, prepare your server and network.
1. Hardware requirements
The appropriate hardware depends on the number of concurrent calls, recording requirements, campaign workload, and whether you are installing a single-server system or a cluster.
For a small test environment, a modest server may be sufficient. Production systems should be sized for the expected workload and tested before launch.
| Component | Planning recommendation |
|---|---|
| CPU | Modern multi-core processor |
| RAM | Start planning around 8 GB for a small deployment; increase based on workload |
| Storage | SSD storage with adequate capacity for the OS, database, logs, and recordings |
| Network | Stable, low-latency internet connection |
| Public IP | Static public IP recommended for straightforward SIP connectivity |
| Backup | Separate backup destination for critical configuration and database data |
| Power | Reliable power and recovery arrangements for on-premises servers |
These are planning guidelines, not guaranteed capacity specifications. Agent accounts alone do not determine server capacity.
2. Software requirements
You will need:
- The appropriate ViciBox 8.1 installation ISO for the legacy deployment.
- Access to the physical server or virtual machine console.
- Root or administrative access.
- A static IP address and network configuration.
- A compatible SIP trunk or VoIP provider account.
- A computer and browser for accessing the web interface.
Download legacy installation media only from the official project archive and verify its integrity where checksums are provided.
3. Network and firewall requirements
Plan the network before installing the dialer.
You may need to permit:
- HTTPS for secure web access.
- SIP signaling using the port and transport supported by your provider.
- RTP media traffic for audio.
- SSH from trusted administrative IP addresses.
- Other application-specific ports required by the installed release.
Do not expose every service to the public internet. Restrict administrative access and follow the firewall guidance for your specific ViciBox release.
Step 1: Download ViciBox 8.1
The ViciBox installer prepares the operating system and provides the environment used to install VICIdial.
For a legacy version 8.1 installation, use the official ViciBox 8.1 installation manual and archive reference.
Before proceeding, confirm that the downloaded ISO matches the intended architecture and installation type.
Important: Do not assume that the legacy installer is appropriate for a new internet-facing production server. Prefer a supported release for a new deployment.
Step 2: Create the Installation USB
If installing on physical hardware:
- Download the correct ISO.
- Connect a USB flash drive.
- Use a trusted ISO-writing utility such as Rufus.
- Select the downloaded ISO and the appropriate target USB drive.
- Write the image to the USB drive.
- Safely eject the drive when the process completes.
The USB drive will be erased during image creation, so back up any files stored on it first.
For a virtual server, use the hypervisor’s ISO mounting feature instead.
Step 3: Boot the Server and Install ViciBox
Connect the installation USB or mount the ISO, then boot the server from it.
Follow the installer prompts to select the installation options, including:
- Region and time zone.
- Disk layout.
- Network settings, where requested.
- Root password.
- Installation confirmation.
Warning: Installing ViciBox can repartition and format the selected disk, permanently deleting existing data. Verify the target disk and backups before confirming installation.
After installation completes, reboot the server and remove the installation media.
Log in using the root password you configured during installation.
For the precise legacy installer screens and procedure, follow the official ViciBox 8.1 installation manual.
Step 4: Configure the Server Network
A dialer needs reliable network connectivity for administration, SIP signaling, and call audio.
yast lanConfigure the server with a suitable static IP address, subnet, gateway, and DNS settings according to your network environment.
Verify the configuration using commands supported by the installed operating system, for example:
ip addr
ip route
ping -c 4 <your-gateway-ip>Replace the placeholder with your actual gateway address.
Check that the server can reach the internet and that the IP address remains stable after reboot.
If the server is behind NAT, plan the SIP and RTP configuration carefully. Incorrect NAT settings can cause one-way audio, failed registrations, or dropped calls.
Step 5: Run the ViciBox VICIdial Installation Phase
ViciBox installation generally involves an operating-system phase followed by a VICIdial configuration and installation phase. Some releases also include an intermediate setup phase.
The exact commands vary by release, installation mode, and whether the system is standalone or part of a cluster.
For the legacy ViciBox 8.1 environment:
- Log in as root after the operating system installation.
- Review the installation manual’s remaining phases.
- Complete any required preliminary configuration.
- Run the installation procedure specified by that release.
- Select the appropriate standalone or cluster configuration.
- Allow the installation process to complete.
- Review any reported errors before rebooting or proceeding.
Do not copy commands intended for a newer ViciBox version into an older installation without confirming compatibility.
For current deployments, the official ViciBox documentation describes the installation process and available installation modes.
Step 6: Verify the Installed Services
After installation, confirm that the major components are working.
Check the Asterisk console using the command supported by your installation:
asterisk -rvvvIf the console opens successfully, inspect the system’s status and available SIP endpoints using the commands appropriate for its Asterisk version.
You should also verify that the database and web server services are running. Service names and management commands may differ between legacy ViciBox and newer releases.
Do not proceed to production until installation errors have been resolved.
Step 7: Open the VICIdial Web Interface
Once the web server and application are running, open a browser on a trusted computer.
Use the server’s configured address, for example:
https://YOUR-SERVER-IPThe exact URL, port, and certificate behavior depend on the installation and web server configuration.
Log in using the administrator credentials configured during setup.
If the interface does not load, check:
- Whether the web server is running.
- Whether the firewall permits the intended web port.
- Whether the server IP address is correct.
- Whether the database is available.
- Whether the application logs show errors.
Avoid exposing an unencrypted administrative interface to the public internet.
Step 8: Configure the VICIdial Server Entry
Inside the VICIdial administration interface, review the server configuration.
Typical settings include:
- Server IP address.
- Asterisk server identification.
- Active status.
- Telephony and application settings.
- Recording and monitoring settings, where applicable.
The configured address must match the actual server and network arrangement.
For a single-server deployment, the web application, database, and telephony services may share one host. A cluster installation requires more careful coordination between the database, web, and telephony servers.
After changing server settings, follow the release-specific instructions for rebuilding configurations or restarting services.
Step 9: Configure Your SIP Trunk
A SIP trunk connects VICIdial and Asterisk to your VoIP provider.
Before configuring it, obtain the following from your provider:
- SIP server or registrar address.
- Authentication credentials or IP-authentication details.
- Supported SIP transport and port.
- Allowed caller IDs.
- Outbound dialing permissions.
- Supported codecs.
- Required NAT or media settings.
- Inbound DID routing details.
Configure the trunk using the method supported by your Asterisk version and provider.
Do not copy a SIP configuration from an unrelated tutorial without checking compatibility. Older Asterisk versions and newer versions may use different SIP channel drivers and configuration formats.
After setup, verify registration or connectivity using the relevant Asterisk commands.
Test a single authorized outbound call before attempting a full campaign.
Step 10: Configure Dialing and Telephony Settings
Next, verify the settings required for outbound and inbound calling.
Depending on your configuration, these may include:
- Outbound dial prefixes and permitted destinations.
- Caller ID settings.
- SIP trunk selection.
- Call timeouts.
- Audio codecs.
- Recording policies.
- Inbound number routing.
- Dialing permissions and compliance controls.
Use only the prefixes, dial patterns, and routes required by your provider.
Keep test calls limited until you have confirmed that calls connect correctly and that the audio works in both directions.
Step 11: Create an Agent User
Agents need accounts to access the VICIdial agent interface.
In the administration area, create an agent record and configure the required credentials and permissions.
Depending on the installed release, you may need to configure:
- Agent user ID.
- Agent password.
- User group.
- Permission profile.
- Phone login details.
- Active status.
Use a strong, unique password and assign only the permissions the agent requires.
Do not share administrator credentials with agents.
Step 12: Create a Campaign
A campaign defines how a group of agents handles calls.
In VICIdial, create a campaign and configure the options needed for your business workflow.
Typical settings include:
- Campaign ID and name.
- Active status.
- Campaign dialing mode.
- Allowed user groups.
- Outbound route or dial prefix.
- Lead recycling and callback rules.
- Disposition settings.
- Calling time restrictions.
- Recording and reporting options.
Start with a small test campaign and a limited number of authorized test contacts.
Do not enable aggressive predictive dialing until you have confirmed call routing, agent availability, dialing rules, and applicable abandoned-call requirements.
Step 13: Upload a Lead List
For an outbound campaign, prepare a lead file with the required fields, such as names and phone numbers.
Check that:
- Phone numbers are formatted consistently.
- The file matches the import fields expected by VICIdial.
- Duplicate and invalid numbers are handled appropriately.
- Contacts have the necessary permissions or lawful basis for calling.
- Do-not-call and suppression lists are respected.
Import the file using the lead-list import workflow in the administration interface.
Assign the list to the intended campaign and verify that the records appear correctly before dialing.
Never upload sensitive customer data to an unsecured server or leave exported lead files accessible to unauthorized users.
Step 14: Configure Inbound Calling and IVR
If you want to receive customer calls, configure the inbound routing workflow.
This typically includes:
- Obtain an inbound DID from your VoIP provider.
- Configure the provider to route the DID to your SIP endpoint.
- Configure the appropriate inbound route in Asterisk and VICIdial.
- Associate the inbound number with the required group, campaign, or destination.
- Configure IVR prompts or queue handling if needed.
- Test the call from an external phone.
A successful inbound call should reach the intended destination and provide clear, two-way audio.
Step 15: Configure Remote Agents
Remote agents may connect using a compatible phone, softphone, or supported WebRTC configuration, depending on the deployment.
For remote access:
- Secure the web interface with HTTPS.
- Use supported phone connection settings.
- Restrict unnecessary access to the server.
- Configure NAT and media settings correctly.
- Test microphone, speaker, and call quality.
- Use strong credentials and appropriate access controls.
Do not expose SIP services indiscriminately to the internet. Use the security and firewall mechanisms appropriate for your ViciBox version.
Step 16: Configure Call Recording and Reports
Call recording and reporting help managers monitor operations and improve quality.
Configure the recording options required for your campaigns and verify that files are stored in the intended location.
Check available reports for:
- Call attempts and completed calls.
- Agent activity.
- Campaign performance.
- Call dispositions.
- Recording availability.
- Relevant operational statistics.
Apply appropriate access restrictions and retention rules to call recordings. Ensure your recording practices comply with applicable laws and customer privacy requirements.
Step 17: Test the Complete System
Before launching a real campaign, perform a complete acceptance test.
| Test | Expected result |
|---|---|
| Administrator login | Administration interface loads successfully |
| Agent login | Agent can access the agent interface |
| SIP trunk | Provider connection or registration works |
| Outbound call | Authorized test call connects |
| Two-way audio | Both parties can hear each other |
| Inbound DID | Incoming call reaches the intended destination |
| Campaign | Correct agents and settings are applied |
| Recording | Recording is available when enabled and permitted |
| Reporting | Test activity appears in the relevant reports |
| Remote access | Authorized remote agent can connect securely |
| Recovery | Backups and recovery procedure have been verified |
Fix any failed tests before enabling production traffic.
Step 18: Secure the VICIdial Server
Security is especially important for legacy VICIdial 8 installations.
Before production use:
- Restrict SSH and administrative access to trusted IP addresses.
- Use strong credentials and change any default passwords.
- Apply the firewall configuration recommended for your release.
- Use encrypted web access.
- Limit SIP access to trusted providers and authorized endpoints where feasible.
- Back up the database and configuration.
- Monitor system logs and failed login attempts.
- Establish a recovery plan.
- Review the support status and security limitations of the installed operating system and telephony stack.
Because VICIdial 8 / ViciBox 8.1 is a legacy platform, security hardening alone cannot guarantee that known vulnerabilities have been addressed. For a new production system, upgrading to a supported release is the safer option.
Common VICIdial Installation Problems
Problem 1: VICIdial Web Page Does Not Open
Check the server address, web server status, firewall, database availability, and application logs.
Problem 2: SIP Trunk Is Not Registering
Verify provider credentials, the SIP server address, supported transport, authentication method, and network access.
Some providers use IP authentication rather than registration, so confirm the provider’s connection method.
Problem 3: Outbound Calls Fail
Check the dial prefix, outbound route, caller ID permissions, provider account, destination permissions, and campaign configuration.
Problem 4: One-Way Audio
One-way audio commonly indicates a media routing, NAT, firewall, or RTP configuration issue.
Check the server’s advertised media address, firewall rules, and provider requirements.
Problem 5: Remote Agents Cannot Connect
Verify the web URL, TLS certificate, agent credentials, phone configuration, and any IP restrictions.
Problem 6: Call Recordings Are Missing
Check the recording settings, disk space, recording path, file permissions, and relevant service logs.
Avoid changing file permissions broadly without understanding the security consequences.
Frequently Asked Questions
Is VICIdial 8 still suitable for production?
VICIdial 8 and ViciBox 8.1 are legacy releases. They may be relevant to historical environments or compatibility requirements, but a new production deployment should generally use a supported release.
Can I install VICIdial 8 on Ubuntu?
The legacy ViciBox installer is designed around its own supported operating system environment. Do not assume that the ViciBox 8.1 installation steps apply directly to a generic Ubuntu installation.
Can I install VICIdial on a VPS?
A VPS may work if it meets the telephony, networking, virtualization, and performance requirements of the chosen release. Confirm that your provider permits VoIP traffic and provides sufficient network quality.
How many agents can VICIdial support?
Capacity depends on concurrent calls, server resources, recording workload, network conditions, and configuration. There is no universal agent count that applies to every installation.
Do I need a SIP trunk to use VICIdial?
For calls to and from the public telephone network, you generally need a suitable voice provider or other compatible telephony connection. A local lab can use different test arrangements.
Can I use VICIdial for inbound and outbound campaigns?
Yes. VICIdial supports inbound and outbound call handling, subject to appropriate configuration and telephony connectivity.
Is VICIdial free?
The open-source software is available without a software licensing fee, but hosting, installation, calling, maintenance, and technical support may incur costs.
Where can I get VICIdial installation support?
You can review the official ViciBox support resources or contact LiveCalls.in to discuss dialer installation, hosting, and VoIP requirements.
Need Help Installing or Configuring VICIdial?
Installing VICIdial is only one part of creating a reliable call center. Server planning, SIP connectivity, campaign configuration, remote agents, security, and testing are equally important.
LiveCalls.in provides dialer and VoIP services for businesses building or improving their call center infrastructure.
Our service offerings may include:
- VICIdial installation and configuration.
- Cloud and in-house dialer solutions.
- SIP and VoIP connectivity.
- DID and toll-free number solutions.
- IVR and broadcasting dialer solutions.
- GSM gateway solutions.
- Technical support and troubleshooting.
Whether you are setting up a new call center or migrating from an older VICIdial server, choose a solution that matches your capacity, security, and support requirements.
Ready to set up your call center?
Visit LiveCalls.in to explore our services and discuss your requirements.
Conclusion
Installing VICIdial requires more than completing the operating system installation. You must also configure the application, telephony services, SIP connectivity, agents, campaigns, inbound routes, recordings, security, and testing.
This end-to-end workflow provides a starting point for understanding the complete installation process.
For a new deployment, consider using a currently supported ViciBox release rather than deploying legacy version 8.1 on an internet-facing production server. The right installation, network configuration, and ongoing maintenance will help your contact center operate more reliably.
Looking for professional VICIdial setup and VoIP services? Contact LiveCalls.in to discuss your project.