CCcam & OScam setup: the complete guide
Updated
Everything you need to get a cccam.io line running - pick a protocol, add the line to your receiver, and fix it when a channel won't decrypt.
Setting up a cccam.io line is quick once you know the pieces. This guide walks the whole path - from what you receive to a decrypted channel - and links each step in depth.
What you get
When you buy or trial a line, you get a username, a password, and two server hostnames. The two hosts are a failover pair: if one has a problem, your receiver switches to the other automatically. You add these details to a softcam on your receiver - either CCcam or OScam.
Pick a protocol
CCcam is the older, simpler option: one line in a config file, restart, done. OScam is more configurable and has better logging. Both connect to the same service with the same credentials, so the choice comes down to how much you like to tinker.
Add the line
On most Enigma2 boxes the flow is the same: open the softcam config, paste your line, restart the softcam, and tail the log for a CONNECTED message. Config paths differ slightly between images and brands, which is why we keep a short guide per receiver.
When it doesn’t decrypt
Most first-time failures are a blocked outbound port (12000), a receiver clock that’s years off, or a mistyped password. Confirm the credentials are live in the line tester first, then work down the checklist.
Start here
Frequently asked questions
Do I need CCcam or OScam? +
Either. CCcam is one line pasted into a config file - the simplest option. OScam is more configurable. Both use the same cccam.io credentials.
How long does setup take? +
About five minutes on most Enigma2 receivers: paste the line, restart the softcam, and check the log for a CONNECTED message.