How to connect card sharing: CCcam and OScam from scratch

Connecting card sharing may seem like a complicated task, especially if you are just starting out. But, if you have access to the line and a compatible receiver, the process can be quite simple. In this article, I will explain how to properly set up card sharing on your receiver using CCcam and OScam. We will go through all the steps, starting from the necessary data and ending with error diagnostics.

What you need to connect card sharing

First, it is important to understand what is needed to connect card sharing. The minimum set consists of several key components. First, let's clarify what a client connection is and how it differs from setting up your own server.

Compatible receiver or set-top box

You will need a receiver that supports softcam. The most popular models are devices based on Enigma2, such as Dreambox or Vu+. Make sure your tuner supports the required emulator, whether it is CCcam or OScam.

Line data: host, port, username, password, DES key

To connect, you will need the following data: host, port, username, password, and possibly a DES key. This data is usually provided by the provider.

Stable internet and open outgoing ports

Make sure you have a stable internet connection. Open outgoing ports are also critically important. For standard card sharing, these are ports 12000-13000 for CCcam and 15000+ for newcamd.

Current firmware and installed emulator

Make sure that your receiver has the current firmware and emulator installed. There are different versions for CCcam and OScam, so it is important to use the latest ones.

CCcam client setup: CCcam.cfg file

Now let's move on to setting up the CCcam client. The main configuration file is CCcam.cfg. You need to write the connection data to this file.

C-line syntax

An example of a connection line looks like this:C: my.server.net 12000 user1 pass1 no { 0:0:2 }. Heremy.server.net is the host,12000 is the port,user1 is the username,pass1 is the password. The last parameters indicate the connection settings.

Location of the config

The file can be located in several places. Usually, it is/var/etc/CCcam.cfg or/etc/CCcam.cfg. Make sure you are editing the correct file.

Parameters: no/yes wantemus, cccam version

You can also configure additional parameters, such aswantemus. If you need this feature, setyesFor the CCcam version, it is best to use the latest stable version.

Restart softcam and check through the log

After editing the file, don't forget to restart CCcam. You can use the commandkillall -9 CCcamor restart through the init script. Logs can be viewed in/tmp/cccam.logor through the web interface on port16001.

Configuring OScam: dvbapi, server, and reader

Now let's talk about configuring OScam. It is a bit more complicated but also more flexible. Here you need to create several sections in the configuration files.

oscam.conf: sections [global], [dvbapi], [webif]

In the fileoscam.confyou need to add the sections[global],[dvbapi]and[webif]. In each of them, various parameters are configured, such as access to the web interface and support for dvbapi.

oscam.server: protocols newcamd, cccam (CS378x), camd35

In the fileoscam.serveradd a line to connect to the server. For example:[reader] label=share1 protocol=cccam device=my.server.net,12000 user=user1 password=pass1. Pay attention to the correct choice of protocol.

oscam.user and oscam.dvbapi for local decoding

The filesoscam.userandoscam.dvbapiare necessary for local decoding to work. Inoscam.useryou also need to specify access parameters for your device.

OScam web interface

Don't forget to check the OScam web interface on port8888. There you will be able to see the status of the reader: online, connected, and CARD OK.

Checking operation and diagnostics through logs

After setting up, it's important to check if your line is working. Logs can tell you a lot.

Reading the ECM log

In the ECM log, look for lines withECM found. The response time should be reasonable. If the hop is 1, it's better than hop 2+, as a lower hop gives less latency.

Statuses: found, not found, timeout

Statuses in the logs indicate whether the line is working.found means that the line is active, whilenot found indicates connection issues.

Normal ECM time indicators

With a good line, theecm time should be up to 400-600 ms. If the indicators are higher, it's worth investigating the cause.

Checking hop level and line priority

Don't forget to check the hop level. The lower, the better. Hop 1 is a local card, while hop 2+ is a resharing that can cause freezes.

Typical connection errors and their resolution

Errors can occur at any stage. Let's look at the most common ones.

Line offline

If the line is offline, check the host and port data. This is usually related to a provider block or incorrect data entry.

CARD OK, but channels do not open

This can happen if the caid and provider id of the channel do not match those provided by the server. Check the settings.

Freezes on HD channels

If you experience freezes, it may be related to high ecm time. Check the stability of the connection and server load.

Authorization error

An incorrect DES key or login can lead to authorization errors. Make sure all data is entered correctly.

How to choose a reliable line source (general criteria)

When choosing a line source, pay attention to several key points. This will help avoid problems in the future.

Server uptime and ECM response time

Make sure the server is stable and has good uptime. The ECM response time should be minimal.

Support for required packages

Check if the server supports the necessary caid and provider id for you. This is critical for opening channels.

Limit on the number of connections and hops

Some providers limit the number of connections. Make sure you have enough resources for stable operation.

Availability of test access

Check if the provider offers test access before payment. This allows you to ensure the quality of the service.