
NTV Plus is the largest satellite operator in Russia, broadcasting its channels via the "Yamal 401" and "Express AM5" satellites at frequencies of 56°E. Cardsharing allows multiple receivers to use one active smart card for decoding the encrypted signal. Let's break down what is needed for setup, what protocols are used, and how to correctly enter the server in the receiver's firmware.
How cardsharing NTV Plus works
NTV Plus uses the Viaccess conditional access system (versions 2.4, 2.6, and 5.0 depending on the package). The card inserted into the server receiver receives an encrypted Control Word (CW) from the satellite every few seconds — an 8-byte key necessary for decoding the picture. The server decrypts the CW using the card and transmits it over the local network or the internet to client receivers. The client receives the key before the previous one expires, and the image remains uninterrupted.
For stable operation, latency is critical: if the CW arrives more than 300–400 ms after the key change on the satellite, the picture freezes for a second. Good servers maintain a ping to the client within 30–80 ms inside Russia.
What is needed for connection
Receiver with emulation support
Any DVB-S2 receiver based on Linux with the ability to install an emulator will do. The most common options are:
- Openbox S9 HD PVR — a budget option, flashed with third-party images with built-in CCcam 2.3.0.
- Openbox SX9 Combo — supports DVB-S2 and DVB-T2, popular for combo installations.
- Dreambox DM900 / DM920 — professional hardware, runs on Enigma2, supports OSCam from the repository.
- VU+ Duo 4K / Ultimo 4K — top-tier lines, Enigma2 + OSCam installed via plugin manager.
- Formuler F4 Turbo — Android firmware, requires a separate CSP client.
Receivers based on Amlogic (MAG, Formuler on Android) work through external clients like OSCam in Docker or on a router. They do not support direct emulator installation.
Software
Two main protocols and emulators:
- CCcam — an old, widely compatible protocol. Version 2.3.0 works on most receivers with Linux firmware. Default port — 12000.
- OSCam (Newcamd / Camd35) — a modern open-source emulator, more flexible. Supports anti-cascading, load balancing, real-time logging. Newcamd port — 10000–20000, Camd35 — 15000.
OSCam is preferable: it is updated, correctly handles Viaccess 5.0 (the "NTV Plus Premium" package), and can perform failover between multiple servers.
Step-by-step setup on Enigma2 (VU+, Dreambox)
Step 1. Installing OSCam via plugin manager
Open the receiver menu → Plugins → Online plugins. In the "Crypt" category, find OSCam and install it. After rebooting, the configuration files will appear in the directory/etc/oscam/.
Step 2. Configuring oscam.conf
The file/etc/oscam/oscam.conf defines general parameters. The minimum working configuration:
[global]
Parameterclienttimeout = 3500 sets the maximum CW wait time in milliseconds. For NTV Plus, 2800–3500 ms is sufficient. Increasing the value does not speed up key retrieval but increases tolerance to slow servers.
Step 3. Server description in oscam.server
File/etc/oscam/oscam.server describes the connection to the sharing server. Example for the Newcamd protocol:
[reader]
Fieldident — provider identifiers for Viaccess for NTV Plus. The values032830,032840,032850 correspond to different operator packages. If the server provides all packages, leave all three. If only the basic one — check with the server operator for the specific ident.
For the CCcam protocol, the structure is different, the fileCCcam.cfg:
C: server.example.com 12000 login123 pass456
One line contains the address, port, login, and password. The CCcam client on the receiver connects to the server and receives CW automatically.
Step 4. Configuring oscam.user (if the receiver acts as a server)
If other devices are connected to your receiver, add users tooscam.user:
[account]
Step 5. Restart and check
Via SSH, execute:
/etc/init.d/oscam restart
The log should show a line likereader ntv_plus_newcamd: connected to server.example.com:15000 and after a few seconds —CW found when trying to open an encrypted channel. If instead you seeECM timeout — there is a problem with the network or incorrect connection data.
Configuration on Openbox (firmware)
Openbox S9 and SX9 work with CCcam through the built-in menu. Go toMenu → Settings → General Interface → Emulator. Enter the server data: IP or domain, port, login, password. Save and reboot the receiver.
If you are using third-party firmware (for example, AB-Com), the configuration file CCcam.cfg is located in/var/keys/CCcam.cfg or/usr/keys/CCcam.cfg depending on the version of the image. Edit it via an FTP client (FileZilla, WinSCP) or via SSH.
Common problems and their solutions
Freezing picture every 10 seconds
This is a classic symptom of delayed CW delivery. Reasons:
- Ping to the server above 200 ms — try another server, closer geographically.
- Server overload — too many clients on one card. The norm: up to 5–8 clients per NTV Plus card.
- Unstable internet on the client side — check packet loss with the command
ping -c 100 server.example.com, no more than 0.5% loss is acceptable.
The channel opens, but without sound or with artifacts
Most often — incorrect CAID or ident. NTV Plus uses Viaccess, CAID0500. If you have1800 (Nagravision) or0D00 (Cryptoworks) — the channel will not open. Check the emulator settings.
The server connects, but channels are not decoded
Check that the satellite is set up correctly. NTV Plus HD is broadcast on:
- “Yamal 401”, 56°E — main package, transponders 11.054 GHz (V, SR 27500), 12.015 GHz (H, SR 27500).
- “Express AM5”, 140°E — package for the Far East, 11.780 GHz (H, SR 44100).
Signal level should be no lower than 65–70%, quality — no lower than 80%. At lower values, the decoder receives damaged packets, and even the correct CW will not help.
OSCam does not start after firmware update
After updating Enigma2, the paths to the libraries sometimes change. Reinstall OSCam via the plugin manager. Configuration files in/etc/oscam/ are preserved — there is no need to delete them.
What to pay attention to when choosing a server
Card sharing servers differ in several parameters:
- Type of card: an official physical NTV Plus card provides a stable signal. Servers that operate through another sharing server (re-sharing, cascading) add latency.
- Number of clients: ask the provider how many clients one card serves. Ideally — up to 6.
- Server uptime: good operators publish statistics. Normal uptime — 99%+ per month.
- Technical support: the ability to contact in case of problems is an important criterion, especially for beginners.
Functionality check after setup
After connecting, open any encrypted channel of NTV Plus — for example, "NTV Plus Kino HD" or "Our Football". If the image appears within 5–10 seconds and holds without freezing — the setup is done correctly.
To monitor OSCam, open the web interface athttp://[receiver-IP]:8888. There you can see active connections, server response time, the number of successfully decoded ECM requests, and errors. A healthy system shows 0 timeouts and a response time of up to 300 ms.
Regularly check the log/tmp/oscam.log — it signals problems earlier than you notice freezes on the screen. Set up log rotation through the parametermaxlogsize = 512 in oscam.conf, so that the file does not fill up the device's memory.
Practical checklist for smooth viewing
Even the best CCCam or OSCam line needs two or three simple preparations. Update your receiver firmware, reset the ECM cache once a week and keep 15–20% free space on the USB stick or internal flash so that the reader can store keys without delays.
When tuning a dish, aim for MER/BER reserve: a two‑degree offset or a loose F‑connector often causes the “freezing” that users blame on cardsharing. Keep a short patch cord to test alternative routers, and save two profiles in OSCam — one for TCP, one for UDP — so you can switch instantly if your ISP starts filtering a protocol.
Utgard.tv monitors each hub 24/7, but you can speed up diagnostics by keeping a short log of your receiver actions. Note the time when you changed the channel, which CAID was active and whether you used Wi‑Fi or Ethernet. This tiny “journal” helps engineers reproduce your environment in the lab and return with a solution in minutes instead of hours.
- Keep two line slots enabled: if the first server hits a maintenance window, the second one instantly takes over without re-entering credentials.
- Run a monthly speed and latency test. Stable 1–2 Mbps with ping <80 ms is enough for SD/HD, but if jitter exceeds 20 ms, switch the router to wired mode.
- Save the Utgard.tv status page and Telegram bot @utgard_sharing_bot to bookmarks — they publish maintenance notices before SEMrush or uptime monitors raise alerts.