Setting up CCcam on Dreambox 920 UHD — step-by-step guide
Dreambox 920 UHD is one of the most powerful receivers on the market, and setting up CCcam on it is no more complicated than on any other Enigma2 box. However, there are nuances. The mips32el architecture, different config paths depending on the image, and minor pitfalls that every second person encounters. I went through all this myself and gathered in one place everything you need to know about dreambox 920 CCcam setup — from plugin installation to diagnostics through the web interface.
This guide is relevant for 2026, for OpenATV 7.x, OpenPLi 9.x, and Merlin4 OE 2.5+ firmware. If you have any of these, you are in the right place.
What you need before setting up CCcam on Dreambox 920
Firmware and image requirements
DM920 UHD operates on the mips32el architecture with OE 2.5 and above. This is a crucial point — packages for arm or aarch64 will not work here, and the installation error will be vague. It may just hang or silently refuse to start.
Compatible images:
- OpenATV 7.x — the most popular choice, huge package repository, CCcam is usually available in the standard feed
- OpenPLi 9.x — minimalist, stable, but CCcam may require manual installation
- Merlin4 OE 2.5+ — the native image from Dream Multimedia, good compatibility
You can check the architecture of your receiver with the command uname -m via SSH or Telnet. It should show mips.
What version of CCcam is sufficient for DM920
CCcam 2.3.2 is the minimum working version. It supports all current CAIDs and protocols. Older versions (2.1.x, 2.2.x) on OE 2.5 may not start due to library incompatibility.
I wouldn't chase after the "latest" builds from forums. Version 2.3.2 works stably, consumes minimal RAM, and has been time-tested. DM920 with its 2 GB of RAM can handle anything, but why complicate things.
Preparation: network, FTP client, text editor
What should be ready before starting:
- Network — the receiver is connected via Ethernet (recommended) or Wi-Fi. You can check the IP address in Menu → Settings → System → Network
- FTP client — FileZilla or Total Commander. Connection: receiver IP, port 21, login root, password as set in the image (often empty by default)
- Text editor — Notepad++ or Sublime Text. Encoding UTF-8 without BOM, line endings — Unix (LF)
Attention: the standard Windows Notepad adds a BOM marker at the beginning of the file and uses CRLF line endings. CCcam cannot process this — the config simply will not be read. I've seen dozens of cases on forums where people searched for hours for the problem, and it was in the editor. Use Notepad++ with the setting "Encoding → UTF-8" and "EOL Conversion → Unix (LF)".
Installing the CCcam plugin on Dreambox 920 UHD
Installation via the image package manager
The simplest way. On OpenATV:
- Menu → Plugins → Download plugins → Softcams
- Find
enigma2-plugin-softcams-cccam - Install, wait for completion
- Restart the GUI (not the entire receiver — just restart Enigma2)
On OpenPLi, the procedure is similar, but the section may be called "Cam setup" or "Softcam". If the package is not in the list — proceed to manual installation.
Manual installation via FTP
When CCcam is absent from the image repository, we install it manually. You need the IPK file for mips32el OE 2.5. Download from trusted sources (OpenATV, OpenPLi forums — in the Downloads sections).
- Via FTP (FileZilla), upload the file
enigma2-plugin-softcams-cccam_2.3.2_mips32el.ipkto the/tmp/folder on the receiver - Connect via SSH (PuTTY, port 22, login root)
- Execute:
opkg install /tmp/enigma2-plugin-softcams-cccam_*.ipk - If it complains about dependencies:
opkg updateand repeat the installation
After installation, the binary usually resides in /usr/bin/CCcam. On some images — in /usr/bin/CCcam.x32. Check:
ls -la /usr/bin/CCcam*\
which CCcam
Checking that CCcam is installed and running
A quick check via terminal:
ps | grep -i cccam
If the output shows the CCcam process — it is running. If not — it needs to be started via Softcam Panel or manually: /usr/bin/CCcam.
Through the receiver interface: Menu → Softcam Panel (or Information → Softcam). CCcam should be displayed as an available softcam. If it is not in the list — the installation was incorrect, repeat with a check of the package architecture.
Configuring the CCcam.cfg file — C-line configuration
Structure of the CCcam.cfg file
The entire CCcam config is a single text file. No databases, no nested directories. One file — and everything works. This simplicity is exactly why CCcam is loved.
Path on DM920:
- OpenATV:
/etc/CCcam.cfg(symlink to/var/etc/CCcam.cfg— the actual file) - OpenPLi:
/etc/CCcam.cfg(usually the actual file) - Merlin4:
/etc/CCcam.cfg
To check if it's a symlink or not: ls -la /etc/CCcam.cfg. If the output shows an arrow ->, edit the file at the actual path. Otherwise, you risk creating a second file, and CCcam will read the old one.
On custom builds, the config sometimes resides in /home/root/ — if the standard path does not work, search: find / -name "CCcam.cfg" 2>/dev/null.
Format of the C-line and meaning of each parameter
A C-line is a connection string to the card sharing server. The format is strict; an extra space can break everything:
C: server.example.com 12000 myuser mypassword
Breaking it down by fields:
| Field | Value | Example |
|---|---|---|
| C: | Line type (C = CCcam client) | C: |
| Server address | Domain or IP of the server | server.example.com |
| Port | TCP port of the server | 12000 |
| Login | Username | myuser |
| Password | Password | mypassword |
There should be one space between C: and the address. One space between each field. No tabs, quotes, or commas. The case of the login and password matters — MyUser and myuser are different accounts.
Example of a working configuration
Here is a minimal working CCcam.cfg for dreambox 920 CCcam client setup:
# CCcam config for Dreambox 920 UHD\
# Servers\
C: primary.example.com 12000 user1 pass1\
C: backup.example.com 15000 user2 pass2\
\
# Main settings\
SERVER LISTEN PORT : 12000\
ALLOW TELNETINFO: yes\
ALLOW WEBINFO: yes\
WEBINFO LISTEN PORT : 16001\
TELNETINFO LISTEN PORT : 16000\
\
# Logging\
LOG WARNINGS : /tmp/CCcam.log
You can add multiple C-lines — CCcam will switch to the backup server if the primary one goes down. The order of lines = order of priority.
File permissions:
chmod 644 /etc/CCcam.cfg\
chown root:root /etc/CCcam.cfg
Additional parameters: LOG, TELNET, WEBINFO
In addition to C-lines, CCcam.cfg has parameters that greatly simplify debugging:
- ALLOW WEBINFO: yes — enables the web interface on port 16001. Without this, diagnostics are blind
- ALLOW TELNETINFO: yes — access to info via telnet on port 16000
- LOG WARNINGS : /tmp/CCcam.log — writes a log of errors and warnings. The file in /tmp/ will not survive a reboot
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_tv_bot to bookmarks — they publish maintenance notices before SEMrush or uptime monitors raise alerts.