Quick Reference

Error Recording Not Starting
Severity Medium
Component Asterisk

Recording Not Starting

What Causes This Error

Call recordings are configured in the campaign but not being created. Common causes: recording directory doesn’t exist or has wrong permissions, disk space full on recording volume, Asterisk MixMonitor application not loaded, campaign_recording setting set to NONE, or the recording path in VICIdial configuration doesn’t match actual server path.

How to Fix It

  • 1 Verify recording directory exists: ls -la /var/spool/asterisk/monitor/

  • 2 Check disk space: df -h (recording partition must have space)

  • 3 Check directory permissions: chown -R asterisk:asterisk /var/spool/asterisk/monitor/

  • Verify MixMonitor is loaded: asterisk -rx ‘module show like MixMonitor’

  • 5 Check campaign_recording setting in Admin > Campaigns — must not be NONE

  • 6 Review Asterisk log for recording errors: grep -i record /var/log/asterisk/messages

  • Test recording manually: asterisk -rx ‘originate…’ with MixMonitor in dialplan

How to Prevent It

Monitor recording disk space with alerts at 80% capacity. Implement automated recording archival and deletion policies. Test recording functionality after any VICIdial or Asterisk update. Include recording check in daily system health report.

ViciStack’s free 30-day support plan includes unlimited live VICIdial troubleshooting. If you can’t resolve this error with the steps above, our engineers will connect to your system and fix it directly — no support tickets, no hourly billing.

Frequently Asked Questions

What causes the VICIdial "Recording Not Starting" error? +

Call recordings are configured in the campaign but not being created. Common causes: recording directory doesn't exist or has wrong permissions, disk space full on recording volume, Asterisk MixMonitor application not loaded, campaign_recording setting set to NONE, or the recording path in VICIdial configuration doesn't match actual server path.

How do I fix the VICIdial "Recording Not Starting" error? +

Verify recording directory exists: ls -la /var/spool/asterisk/monitor/ Then: Check disk space: df -h (recording partition must have space) Then: Check directory permissions: chown -R asterisk:asterisk /var/spool/asterisk/monitor/ Then: Verify MixMonitor is loaded: asterisk -rx 'module show like MixMonitor' Then: Check campaign_recording setting in Admin > Campaigns — must not be NONE Then: Review Asterisk log for recording errors: grep -i record /var/log/asterisk/messages Then: Test recording manually: asterisk -rx 'originate...' with MixMonitor in dialplan

How can I prevent the "Recording Not Starting" error in VICIdial? +

Monitor recording disk space with alerts at 80% capacity. Implement automated recording archival and deletion policies. Test recording functionality after any VICIdial or Asterisk update. Include recording check in daily system health report.

Related Errors

Asterisk Not Running View error → Database Connection Lost View error →

Related Settings

campaign_recording View setting →

Part of the Complete VICIdial Implementation Guide

Need Help Fixing This Error?

Our VICIdial experts can diagnose and resolve this issue quickly. Get a free performance audit and we'll identify all critical problems.

Get Your Free Audit →