CCcam or OScam: which line should you run?

Updated August 2026

Both protocols do the same job. The right choice comes down to your receiver, your image, and how much you want to tinker. Here's a straight comparison.

We offer lines for both CCcam and OScam. They solve the same problem in different styles, and for most people either one works fine. Here’s how to pick.

The short version

• New to this, or want the simplest setup? Use CCcam. One line, paste, restart, done.
• Comfortable editing config files and want more control? Use OScam.

Both connect to the same service. This is a preference about the client software on your receiver, not about what you’re watching.

CCcam

CCcam is the older, simpler protocol. Setup is a single C: line in CCcam.cfg, a softcam restart, and you’re watching. It’s forgiving, widely supported, and included in nearly every Enigma2 image. If you just want it to work with minimal fuss, start here - see the CCcam quickstart.

OScam

OScam is more configurable. Instead of one line, you define a reader and a user across oscam.server and oscam.user. That’s more to set up, but it gives you finer control over how the box behaves, better logging, and options CCcam doesn’t expose. If you like tuning things or run a more complex setup, OScam rewards the effort - see the OScam quickstart.

Can I run both?

You can, but you usually shouldn’t run them against the same channels at once - let one softcam own decryption to avoid them fighting. Many people keep both installed and switch depending on the box.

Our take

If you’re setting up your first receiver, use CCcam and don’t overthink it. If you already know your way around a config file and want the extra control, OScam is worth it. Either way, the line you get from us works the same - pick the client that matches how much you like to tinker.