VICIfast
Operations

How to set the Stereo Rec Filename (and why it must differ)

The Stereo Rec Filename field controls what stereo call recording files are named. It must differ from the Campaign Rec Filename or stereo recordings will not work.

VICIfast Support
··2 min read
How to set the Stereo Rec Filename (and why it must differ)

The Stereo Rec Filename field tells VICIdial what to name each Stereo recording file it writes to disk. It looks simple, but two easy mistakes will silently break stereo recording entirely: leaving it blank, or setting it to the same value as the Campaign Rec Filename.

Why the field is required

VICIdial will not write stereo files for calls placed from a Campaign unless this field is populated. The default value is S_FULLDATE_CUSTPHONE, which produces a filename like S_20051020-103108_3125551212. The leading S_ is what separates it from the standard mono recording in the same directory.

The uniqueness rule

**Heads up:** The Stereo Rec Filename cannot be set to the same value as the Campaign Rec Filename. If they match, VICIdial cannot tell the two files apart on disk and stereo recording will not function correctly. Always ensure at least one variable or prefix differs between the two patterns.

Supported dynamic variables

The Stereo Rec Filename supports the same dynamic fields as the Campaign Rec Filename. You can use any combination of these tokens:

  • CAMPAIGN — the campaign ID
  • INGROUP — the inbound group ID if the call came in via an inbound route
  • CUSTPHONE — the customer phone number
  • FULLDATE — timestamp in YYYYMMDD-HHMMSS format
  • TINYDATE — compact timestamp
  • EPOCH — Unix epoch seconds
  • AGENT — the agent login ID
  • VENDORLEADCODE, LEADID, CALLID, RECID — lead and call identifiers
  • POST variables (POSTVLC, POSTSP, POSTARRD3, POSTSTATUS) — only when POST recording processing is enabled on the dialer

The 90-character limit

The resulting filename — after all dynamic tokens are resolved — must be under 90 characters. Long patterns that combine several tokens can breach this limit. Keep patterns concise: AGENT_FULLDATE_CALLID is typically safe, while chaining five or six long tokens risks truncation or errors.

Filename flow from config to disk

flowchart TD
  A[Stereo Rec Filename template set] --> B{Field populated?}
  B -->|No| C[Stereo recording disabled - no file written]
  B -->|Yes| D{Same as Campaign Rec Filename?}
  D -->|Yes| E[Conflict - stereo recording broken]
  D -->|No| F[Tokens resolved at call time]
  F --> G[File written to recording directory]

Practical naming patterns

A common approach is to prefix the stereo filename with ST_ or STEREO_ so it sorts separately from the mono file. For example, ST_FULLDATE_AGENT gives you a stereo file named ST_20051020-103108_6666 while the Campaign Rec Filename remains FULLDATE_AGENT.

If your QA platform ingests files by Agent login, including AGENT in the stereo filename makes bulk retrieval straightforward without querying the database.

For context on how the Campaign Rec Filename and its variables work, see VICIdial campaign rec filename variables. For a full overview of VICIdial's recording system, see VICIdial call recording explained.

Ready to run VICIdial with stereo recording already configured? See VICIfast pricing.

About VICIfast LLC

VICIfast LLC operates a managed VICIdial hosting + BYOI service for outbound and inbound call centers. We run the dialers, the carriers, the recordings pipeline, and the compliance plumbing so operators don’t have to.

Citing this article

VICIfast Engineering. “How to set the Stereo Rec Filename (and why it must differ)”. VICIfast LLC, June 24, 2026. Retrieved from https://vicifast.com/blog/vicidial-stereo-rec-filename

Have questions?

Related posts

You might be interested in

VICIfast newsletter

Liked this? Get the next one in your inbox.

We ship the kind of stuff you just read — concrete, numbers-first, no drip. One email when a new post goes live. Unsubscribe in one click.

Comments

Comments are reviewed before they appear. We never publish your email.

No comments yet — be the first.