CBS on satellite: frequency, transponder, and CCcam setup

Requestwhat channel is cbs on cardsharing forums usually means one thing: the person found the channel in blind scan but doesn't understand what to do next. CBS is not a single channel with one frequency. It is a network of affiliated stations that broadcast on different transponders, with different CAIDs, and some of them do not require a card at all.

Let's break everything down step by step — from the orbital position to the line in oscam.server.

On which satellite and transponder CBS broadcasts

Before diving into the configs, you need to understand: which specific stream your receiver caught. CBS is present in satellite broadcasting in several forms — open regional feeds (FTA) for the needs of affiliate networks and encrypted packages within paid platforms.

Regional feeds of CBS and their positions in orbit

The main American positions are AMC-8 (139° W), SES-1 (101° W), Galaxy 17 (91° W). On these orbits, the so-called contribution feeds are circulating — streams that CBS sends to regional broadcasters. Some of them are open (FTA), while others are packed in encrypted packages.

For European and Middle Eastern users, the situation is different: CBS reaches Hotbird (13° E) or Astra 19.2° E as part of encrypted packages through IPTV-over-DVB resellers — there the CAID is completely different.

Current transponder parameters are checked in databases like LyngSat or KingOfSat. It makes no sense to provide specific frequencies here as a "guaranteed fact" — they change, and what worked in March may not work now.

Transponder parameters: frequency, polarization, Symbol Rate, FEC

During blind scan, the receiver will find the transponder and display its parameters in the menu — usually something like: Freq 11880 MHz, POL H, SR 22000, FEC 3/4. Write down this data — it will be needed for checking in the database and for oscam.dvbapi if you need to set priority by transponder.

Symbol Rate for American C-Band feeds is often 3/4 or 5/6, polarization is vertical or horizontal — it depends on the specific transponder. Ku-Band for European positions usually has an SR of 27500 or 22000.

How to distinguish FTA feed from encrypted stream

The simplest way is to look in OScam WebIF (port 8888 by default): switch to the channel and open the ECM info tab. If CAID is not requested and the channel is showing — it is FTA. If you see an active ECM request with CAID and provid — the channel is encrypted and a source of keys is needed.

The receiver may show the channel as "encrypted" even on an FTA stream if it is not configured correctly. Check specifically through the OScam log, not through the lock icon in the EPG.

CAID, provider, and SID: what is needed for decoding

Many get stuck at this point because they search for "how to open CBS" instead of looking for "how to open CAID 0xXXXX with provid 0xYYYY". For OScam, the channel name does not matter at all — only CAID + provid + SID.

How to find out the CAID of the channel through OScam WebIF (ECM info)

Open your browser:http://<ip-receiver>:8888. In WebIF, go to theStatus orReaders section, switch to the CBS channel on the receiver. In the ECM column, a request of the form will appear:

CAID: 0x0963  provid: 0x000000  SID: 0x1234

This is what your reader needs. Write down these three values.

If ECM info is empty and the channel is showing — congratulations, this is FTA, cardsharing is not needed. This case creates half of the questions "why CBS does not open" — the person tries to run the FTA stream through the reader and getsno matching reader, while they just need to remove the unnecessary request.

Binding CAID to the required reader in oscam.server

In the file/etc/oscam/oscam.server (or/var/tuxbox/config/oscam/oscam.server depending on the firmware) each reader is described by a block. For correct CAID binding:

[reader]
label     = my_reader
protocol  = cccam
device    = host,port
user      = user
password  = pass
caid      = 0963
ident     = 0963:000000
group     = 1

The parameterident — is the CAID:provid pair. If the provider supports multiple provids, list them separated by commas. Without an explicitident OScam will try all available sources, which is slower and causes unnecessary timeouts.

The role of SID and onid/tsid in channel filtering

SID (Service ID) — a unique identifier for a channel within the transponder. There can be a situation: CAID matches, the reader is active, but CBS still does not open. The reason is an incorrect SID or a conflict inoscam.dvbapi.

In/etc/oscam/oscam.dvbapi you can set the priority for a specific CAID on a specific transponder:

P: 0963:000000
F: 0963:000000:1234

Where 1234 — is the SID of the CBS channel. The F (filter) line tells OScam: for this SID use this CAID specifically, do not look for other options. This is especially necessary when there are multiple CBS feeds with different parameters on one transponder.

How to add CBS to the OScam/CCcam config

Now for the specifics. The structure of the configs depends on the firmware, but typical paths are as follows:

• OpenATV, OpenPLi:/etc/oscam/
• DreamElite, old Dreambox:/var/tuxbox/config/oscam/
• CCcam.cfg: usually/var/etc/CCcam.cfg

Writing the service in oscam.services

The fileoscam.services allows you to create named groups of channels and bind them to specific readers. For CBS:

[cbs_channels]
caid    = 0963
provid  = 000000
srvid   = 1234,1235,1236

Then inoscam.server you add to the reader:

services = cbs_channels

This guarantees that requests for these SIDs go only to this reader. Without such binding, OScam may go to another source that does not support the required region, and you will get a timeout.

Configuring CCcam.cfg: C-line and reader priority

If you are using pure CCcam without OScam, the config is simpler. In/var/etc/CCcam.cfg you add a C-line:

C: host port user pass

Where host, port, user, pass — are the data of your source (placeholder in the example). CCcam does not have such flexible filtering by CAID as OScam. If the source supports the required CAID — the channel will open, if not — it won't. Diagnosing this is more complicated, so for such analysis aswhat channel is cbs at the CAID level, OScam is more convenient.

Several C-lines CCcam processes from top to bottom. Priority is determined by the order of the lines. If you want a specific source to be first for American channels — place it higher in the file.

After changes — restart the daemon:

# Для OScam:
systemctl restart oscam
# или
/etc/init.d/oscam restart

# Проверка статуса:
systemctl status oscam
# или посмотреть лог:
tail -f /var/log/oscam/oscam.log

Check via oscam.dvbapi and decoding log

After the restart, switch to CBS and watch the log in real time:

tail -f /var/log/oscam/oscam.log | grep -i "cbs\|0963\|1234"

Successful decoding looks something like this:

2026/05/29 10:23:15 c (dvbapi) [email protected] SID 0x1234 CAID 0x0963 PMT 0x0050 ECM decoded OK (45ms)

The number at the end (45ms) — is the ECM response time. Under 100ms — is normal. 300ms and above — indicates a problem with the source or network.

Why CBS does not open: error diagnosis

When something doesn't work, 90% of people start changing configs randomly. The right way is to read the log and understand at which step the failure occurs. Signal and authorization — are two different problems, and they are treated differently.

ECM timeout and no matching reader in the log

no matching reader — this is not a source error. It means that no reader in oscam.server is configured for the requested CAID/provid. Check:

1. The valuecaid in oscam.server matches what is requested in the ECM?
2. The valueident includes the required provid?
3. The reader is in the correctgroup, and this group is specified in oscam.user?

ECM timeout — the reader was found, the request was sent, but there is no response. Reasons: the source is unavailable (ping fails), too many users on one key, or a specific region/feed is not supported by this source. Check the average ECM time in WebIF — if it is 2000ms+, the source is overloaded or does not support this stream.

A separate case: FTA channel, the user has entered it in oscam.services and is waiting for decoding. The log saysno matching reader, but this is normal — FTA does not require an ECM request at all. Remove the SID from oscam.services or simply ignore this line in the log.

Invalid CAID or closed provider

Sometimes, a source supports CAID, but only for certain regions. This is called regional key blocking — the key is valid for the feed, say, of New York, but not for the Los Angeles feed with the same CAID and a different provid.

Look in the log for lines like:

CAID 0x0963 provid 0x000001 not found in reader

This means the provid is incorrect. Take the real provid from ECM info WebIF and compare it with what is specified in the reader's ident.

Another source of pain — several CBS feeds with different CAIDs at one orbital position. This really happens: the contribution feed of one regional affiliate may be in a package with CAID 0x0963, another — with 0x0B00. Blind scan caught both, but the reader is configured for only one.

Problems with the tuner: low signal, incorrect polarization

If ECM is not requested at all and the channel does not show — the problem is at the tuner level. Open WebIF → Tuner/Signal, check SNR and AGC. SNR below 10 dB on Ku-Band and below 13 dB on C-Band — unstable reception, PMT is not read, decoding is impossible even with the key.

After changing the transponder (for example, CBS moved to a different frequency), the PID and PMT may change. The picture is black, although the ECM is decoded successfully — this means that the receiver is holding the old PMT. A manual transponder scan update or a full rescan of the package helps.

Incorrect polarization will give either a zero signal or an unreadable stream with constant errors. Check the parameter in the transponder settings manually, not just through blind scan.

Criteria for selecting a key source (without advertising)

Questionwhat channel is cbs sooner or later leads to the question "where to get keys". I won't name specific services here — not because they don't exist, but because the right choice depends on your CAID, region, and requirements. I will better explain how to evaluate the source yourself.

Stability of uptime and speed of ECM delivery

The only metric that matters is the average ECM time in oscam.log. Look at it over several hours, not just one minute. A good source keeps the ECM time at 30-80ms consistently. If you see spikes from 50ms to 800ms — the source is overloaded or has an unstable connection.

In the WebIF OScam, there is a response time graph for each reader. A straight line — good. A sawtooth — bad.

Uptime can be indirectly assessed from the log: count the number ofreader reconnected in 24 hours. More than 5 — the source is unstable.

Support for the required CAID and region

Before connecting any source, find out: does it support the specific CAID and provid that your CBS feed requests? The source may decode thousands of channels, but your specific American feed with provid 0x000001 may not be supported.

It’s easy to check: connect the source, look in WebIF → Readers → CAID/provid list. Is your pair there? Then there is a chance. If not — this source is not suitable for you, regardless of price and reviews.

Signs of an unstable source

Worrying signs that I see in the logs with a bad source:

• ECM time constantly increases throughout the day (the source degrades under load)
• Frequentecm timeout specifically during prime time (overload from the number of users)
• ECM decoded OK, but the picture freezes every 10-15 seconds (the key is being shared with too many users simultaneously)
• Different SIDs of the same channel are decoded, but separate CBS regions give timeout (regional key filtering)

The last sign on the list is particularly indicative: if the source supports CAID, but the specific provid/region does not open — look for another source with clear support for the required regional feed.