MTS TV Satellite: card sharing and reception (CCcam/OScam)

If you are dealing with MTS TV Satellite: card sharing and reception — and something is not working, the problem is likely either in the config, the signal, or in CAID. Most articles provide a C-line and consider the task solved. This is not the case. Below is the real technical picture: paths to files, config structure, log diagnostics, and separating antenna problems from key exchange problems.

How MTS TV reception works through card sharing (CCcam/OScam)

The principle is simple. The receiver receives an encrypted stream from the transponder, extracts the ECM packet from it, and sends it to the sharing server. The server decrypts the ECM through the physical card and returns the control word. The receiver uses it to decode the picture. The entire cycle normally takes less than a second.

To set up the receiving side, you need to know three things: the CAID of the package, the provider ID, and the correct transponder. Without this, OScam will not understand where to direct ECM requests, even if the reader is up and the connection is established.

The role of CAID, provider ID, and ECM/EMM in decryption

CAID (Conditional Access ID) — the identifier of the encryption system. For MTS TV this is0x1830 (Verimatrix). The provider ID specifies which particular package is inside the system. ECM (Entitlement Control Message) — a packet with the encrypted control word, which changes every few seconds. EMM (Entitlement Management Message) — rights management packets, relevant for local cards.

In OScam, it is important that CAID1830 is explicitly specified inoscam.dvbapi and in thecaid parameter of the reader. If it is set to0 or the value does not match — the reader will be online, but the channel will be black. This is the most common mistake that people overlook for hours.

What is the difference between a local card and network sharing

A local card is read directly through a smartcard reader (physical USB or built-in slot of the receiver). Network sharing is when your OScam or CCcam connects to a remote server that has a physical card. You receive the same control word, only with a delay determined by the ping and server load.

With network sharing, you have no direct control over the quality of decryption. Therefore, ECM time is a key indicator. Anything above 1500 ms already leads to freezes. Above 3000 ms — almost guaranteed black screen.

What frequencies and transponders are used by the satellite package

MTS TV broadcasts via the Express-AT1 (56° E) and Express-AT2 (140° E) satellites. The main package for the European part of Russia is 56°, transponder 11.085 GHz, polarity V, SR 30000, FEC 3/4. If you have an old setup or the dish has shifted — the frequency may not match the current position of the package. When changing the transponder, the old config stops receiving channels regardless of the state of sharing.

Setting up the receiving side on OScam: configs and paths

On Enigma2 receivers (Dreambox, VU+, GigaBlue, and others), OScam configs are located in one of two places:/etc/tuxbox/config/oscam/ or/var/etc/oscam/. It depends on the firmware. On OpenATV and OpenPLi, you more often find/etc/oscam/. Check where the daemon is actually running —ps aux | grep oscam will show the path to the executable file, and the launch keys will indicate the config directory.

File oscam.server: reader parameters and cccam protocol

The minimum working block for connecting to the source via the CCcam protocol looks like this:

[reader]

The port in the linedevice is set by the exchange source — typical range 12000–18000. The parametercaid = 1830 restricts the reader to only the required encryption system. Without it, OScam will send ECM across all channels through this reader, creating unnecessary load.

reconnecttimeout = 30 — do not touch unnecessarily. A value that is too short creates an infinite reconnect loop in an unstable network, while a value that is too long results in a long recovery after a disconnection.

File oscam.user and access rights

If OScam is used as a local server with dvbapi (and not just as a client), then the fileoscam.user defines access for the local plugin. The minimum block:

[account]

Access rights for all configs:chmod 600 /etc/oscam/*. If the daemon is run by root — this is not mandatory, but good practice. On some firmware, OScam does not start if the configs have world-readable permissions like 644.

File oscam.conf and web interface on port 8888

Inoscam.conf the section[webif] enables the web interface:

[webif]

After starting OScam, openhttp://IP-receiver:8888 in the browser. There you can see the status of each reader (Online/Offline), current ECM time, and the latest requests. This is much more informative than reading the log manually — although the log is also needed:tail -f /tmp/oscam.log or the path specified in[global] section.

Binding CAID/provider in oscam.dvbapi

This is where most settings break. The fileoscam.dvbapi manages which CAID OScam processes through the dvbapi interface. An example line for MTS TV:

P: 1830:000000

If this line is missing or the CAID is written incorrectly — OScam ignores ECM from the required channels. The reader will still be shown as Online in the web interface. The channel will be black. This case is often overlooked in other instructions.

Configuration via CCcam.cfg: C-line format

CCcam is simpler than OScam in configuration, but less transparent in diagnostics. The fileCCcam.cfg on Enigma2 is usually located in/var/etc/CCcam.cfg or/etc/CCcam.cfg. On some old firmware — right in the root/, which is not great, but it works.

Syntax C: host port username password

Connection line to the server:

C: your.server.host 12000 login password

Four fields separated by spaces: host, port, login, password. No colons, quotes, or extra characters. The case of the login and password is important — it must match exactly, byte for byte. An error in one character gives a statusoffline in the log without any explanations.

The port must exactly match what is provided by the exchange source. Check before wasting time diagnosing other things:telnet your.server.host 12000. If the connection cannot be established — further digging is pointless.

Additional flags and parameters of the line

After the main four fields, you can add a fifth parameter — reconnect timeout in seconds (default 20). Some CCcam builds support the hopcount parameter throughSHARE HOPS in cfg, but for the client side, there is no need to touch it — leave it default.

LinesN: andF: in CCcam.cfg — this is newcamd and F-line (for sharing local cards with clients). They are not needed for pure client reception.

Restarting the daemon and checking the connection

On Enigma2, restart CCcam:init.d/softcam restart or through the plugin menu. You can also do it directly:killall CCcam&& CCcam&. After the restart, log:tail -f /tmp/CCcam.log. Look for the lineConnection to your.server.host:12000 successful. If you seefailed or silence — the problem is in the network or in the credentials.

File permissions:chmod 600 /var/etc/CCcam.cfg. On some CCcam receivers, the config with permissions 644 is read silently, without an error in the log.

Diagnosis of MTS TV reception problems

When MTS TV Satellite is not working: card exchange and reception — the first question is not "what's in the config," but "is there a normal signal." How many times have people spent hours editing oscam.server, only to find that the dish was misaligned. Therefore, the diagnosis proceeds strictly in order: signal → network → exchange.

Black screen and error "no access" with signal present

If the SNR is normal, but the channel does not open — check oscam.log. Look for lines withECM and the specific SID (service ID) of the channel. If ECM requests do not appear at all — the problem is in dvbapi, not in the reader. If requests are present, but returnCAID not found orno card — either the CAID in dvbapi is incorrect, or the required card is not available on the source side.

Check:grep "1830" /etc/oscam/oscam.dvbapi. If the output is empty — add the lineP: 1830:000000 and restart OScam.

High ECM time or decoding timeout

Normal ECM time for network exchange is up to 800 ms. At 1000–1500 ms, there are periodic freezes. Above 3000 ms — decoding cannot keep up, the control word becomes outdated before the next one arrives. Result: black screen or constant interruptions.

Main reasons for high ECM time: high ping to the server (checkping your.server.host), server overload during peak hours (Friday to Sunday evenings — classic), unstable internet connection with packet loss. Partially, this can be resolved by choosing a source with a geographically closer server.

Channel opens with delay or freezes

Freezing only on channels with high bitrate (HD, 4K) while others work normally — a separate case. Most often, this is not an exchange problem, but a problem with the receiver's network bandwidth or Wi-Fi connection. The control word arrives on time, but the stream does not buffer in time.

Channels open during the day and disappear in the evening — almost always a source overload. Check the ECM time in the OScam web interface at different times of the day. If at 14:00 it is 300 ms, and at 21:00 it is 2500 ms, the source is overloaded.

Signal quality check: SNR, BER, AGC level

In the receiver menu, find the "Signal Information" or "Signal Info" section. Look at three indicators:

• SNR (Signal-to-Noise Ratio) — should be above 12 dB for stable reception. Below 10 dB — unstable signal even in good weather.
• BER (Bit Error Rate) — should normally be 0 or close to zero. High BER with normal SNR — a problem with the LNB or cable.
• AGC (Automatic Gain Control) — signal level from the converter. Too low (below 50%) or too high (above 90%) — a problem with alignment or attenuator.

If at least one of these indicators is abnormal — the problem is in the antenna path. Key exchange has nothing to do with it, you can leave the configs untouched.

How to choose an exchange source: technical criteria

I will not name specific services here — that is not the goal of the article. But the technical criteria for evaluating any source are specific and measurable.

Stability of uptime and ping to the server

Ping to the server host should be below 80 ms from your receiver. Check specifically from the receiver with the commandping host, not from your home computer — these are different network paths. Server uptime — at least 99% per month. One hour of downtime per day is already critical for evening prime time.

Check the real uptime with a test period: take a test access, connect, and watch the ECM time in the OScam web interface every few hours for 2–3 days. There are no other methods of evaluation.

Support for the required CAID and the number of local cards

Ask the source specifically: is there a local MTS TV card (CAID 1830)? Not "we support the package," but a physical card. The more hops from you to the real card, the higher the ECM time. One hop (you → server with the local card) is ideal.

If the source retransmits someone else's signal through a chain of servers, the ECM time will definitely increase. This is evident from the unstable response time: 200 ms → 800 ms → 3000 ms over one hour.

Protocol (CCcam/newcamd) and connection limits

CCcam and newcamd are different protocols, not interchangeable in the config line. Clarify with the source which one is supported. Most modern servers provide CCcam on ports 12000–18000, newcamd on 10000–10100. OScam supports both through the parameterprotocol in the section[reader].

Connection limits are important if you are using multiple receivers. The source may limit you to one simultaneous connection — then the second receiver will be denied, and the channels will not open. This is not a config bug, but an account condition.

And finally: double decoding. If you have a physical MTS TV card inserted into the receiver and at the same time a network reader configured for the same CAID — a conflict may occur. OScam will try to use both sources and may enter a loop. The solution: explicitly specify the priority throughcacheex or disable one of the readers.

The topic of MTS TV Satellite: card sharing and reception is more complicated than it appears from the outside. Separate the problems of the antenna path and the problems of key exchange — this saves hours of diagnostics.