ORECX OREKA (CallMiner Record) integration explained

ORECX OREKA - now rebranded as CallMiner Record - is a third-party recording suite that hooks into SIP (Session Initiation Protocol) audio at the network level rather than relying on VICIdial's native MixMonitor. The result is a richer capture: raw Call recording audio plus an optional screen-recording layer that logs every agent action during the call.

What OREKA actually captures

OREKA operates as an open-source recording suite built for Voice-over-IP environments. Inside a VICIdial cluster it does two things. First, it intercepts the SIP audio stream directly and handles audio compression independently of Asterisk's MixMonitor. Second, it can capture the agent's screen throughout the call so that every keystroke, screen navigation, and disposition change is timestamped alongside the audio. That screen capture is what makes the integration valuable for quality-assurance teams that need more than just audio replay.

Server twinning - the core requirement

OREKA requires VICIdial servers to be deployed in pairs, a topology the project calls server twinning. One server is designated the Agent Server; the other is the Non-Agent Server. The split exists because OREKA needs to observe traffic on distinct paths: agent SIP (Session Initiation Protocol) signaling on one side and inbound call delivery on the other.

• Agent Server: set "Active Agent Server" = Y. All agent phones register here. Max Trunks should be set to 0 on this server if you are auto-dialing.
• Non-Agent Server: set "Active Agent Server" = N. All inbound calls must be directed here exclusively.
• Both servers must reference each other using the "Active Twin Server IP" field in server settings.
• In every campaign and inbound group that should be recorded, enable "Extension Append CID" so OREKA can match audio streams to the correct call leg.

**Heads up:** Skipping the "Extension Append CID" setting is the most common reason OREKA recordings come out mismatched or silent. Enable it in both campaign settings and in-group settings before testing.

How the twin architecture routes calls

flowchart TD
  A[Inbound call arrives] --> B[Non-Agent Server]
  B --> C[OREKA captures SIP audio]
  B --> D[Route to Agent Server via Twin IP]
  D --> E[Agent phone registered here]
  E --> F[OREKA screen capture starts]
  C --> G[Merged recording stored]
  F --> G

CallMiner rebranding - what changed

ORECX is now part of CallMiner, and the product is sold as CallMiner Record. The underlying open-source OREKA engine still works the same way, but licensing and support now flow through CallMiner's commercial platform. If you are pricing a new deployment, start at the CallMiner website rather than the old orecx.com domain.

VICIdial's native Call recording tools cover most environments, but if your compliance or QA program requires screen capture alongside audio, OREKA adds that layer without replacing your Asterisk infrastructure. Read more about how VICIdial handles recording at the core level in our guide on VICIdial call recording explained.

If you want to analyze what those recordings actually contain, see how Voice analytics tools like the now-discontinued RankMiner approached that problem in RankMiner voice analytics explained.

Running a hosted VICIdial cluster where server twinning is already configured? See VICIfast pricing to find a plan that fits OREKA-ready deployments.