Every contribution chain has a receiving end. vxReceiver is the product that sits there — it takes the IP stream, removes the protection it was carried under, and hands your headend a clean MPEG-TS. One device, at every site, for every protocol.
Getting the stream to the site is the easy half. What the site does with a protected, segmented feed is where contribution over IP actually breaks.
Reception, decryption and transport-stream hygiene — one product, at every site.
Reception, decryption and transport-stream conditioning in a single product — so the headend below never has to change.
SRT in caller, listener and rendezvous modes. HLS with MPEG-TS segments, including LL-HLS. UDP and RTP, unicast or multicast. One transport family end to end — what arrives is already a transport stream. Source parameters detected automatically by vxProber.
AES-128, SAMPLE-AES and CENC in AES-CTR and AES-CBC modes. Keys are pulled from vxDRM Gateway over CPIX, or from any third-party key server via token and session API. Key rotation is followed mid-stream without a visible artefact.
PCR restamping, CBR shaping with null padding, continuity counter repair, PID remapping, optional transrating via vxTranscoder and full PAT / PMT / SDT / NIT regeneration. The output is a stream your multiplexer, modulator or DTH encoder accepts without argument.
Lock to a fixed profile from the ABR ladder, or let the receiver follow what the site's link sustains. Optional transrating or transcoding brings the feed to the exact bitrate and codec the local headend expects.
Primary and backup sources on different protocols and different networks — an SRT path backed by an HTTP path, or two CDN edges. Automatic switchover with configurable dwell and return policy.
SCTE-35 ad markers, teletext, DVB subtitles, multi-language audio and closed captions survive the packaging round trip and are present on the output TS. Local ad insertion downstream keeps working.
A receiving estate is only viable if nobody has to visit it. Control, monitoring and recovery are built for sites with no engineer on shift.
All configuration and control through a single RESTful API and web GUI. Per-receiver stream health, buffer state and key status across the whole estate from one console.
vxMetrics dashboards plus SNMP traps and syslog into the NMS you already run. Monitoring is exported; the receiver itself is never configured over SNMP.
Automatic reconnect, configurable latency targets, slate or last-frame hold on loss of source, and event logging that stands up as post-incident evidence.
One live feed reaches many receiving sites over the public internet. The transmitting side packages and protects it with vxOTT Gateway and vxDRM Gateway. Every receiving site runs a vxReceiver — and every one of them is issued its own key.
The feed is encrypted once and cached once. What differs per site is the licence, not the content — bandwidth and storage do not grow with the number of receivers.
Every licence request is tied to a named receiver. vxDRM Gateway logs who took the feed, when, and from where — evidence for a rights contract, not a promise.
A contract ends, a site is compromised, a partner churns. Stop issuing that one key. No re-keying, no re-packaging, no truck roll to the other sites.
The other half is what a site does with a protected, segmented stream when everything downstream expects a constant-bitrate transport stream with valid tables and a stable clock. That conversion — decrypt, select, repair, shape, restamp — is what vxReceiver is for.
The same product at the receiving end of six different chains — regional distribution, repatriation, licensed venues, disaster recovery, cloud playout and multi-tenant hubs.
vxReceiver closes a chain that starts at the playout — packaged by vxOTT Gateway, keyed by vxDRM Gateway, cached at the edge and landed on-premise as broadcast UDP.
Packages and protects the contribution feed with SCTE-35 preserved. vxReceiver consumes that output natively — no intermediate format and no middleware between the two ends.
Keys and licencesIssues a separate key domain per receiver and serves the licence. Session control, geo-blocking and device filtering apply to receivers exactly as they apply to subscribers.
Local conversionAdjusts the received rendition to the codec, bitrate and resolution the local headend requires — MPEG-2 for a legacy multiplex, HEVC for a modern one.
One rack unit on sitevxReceiver runs as a vxApp inside the vxFlex appliance, so reception, decryption, transcoding and DVB-C or IPQAM modulation live in a single rack unit at the site.
Input, decryption, output conditioning and day-two operation — the four things a receiving site is judged on.