There are 15 replies in this Thread which was already clicked 2,776 times. The last Post () by glasscr4ck.
Without seeing how you`ve configured things its difficult to pinpoint the problem.
Hi.
You need three basic files:
oscam.conf
oscam.server
oscam.user
Next you need to set up some CA source where the packets will be decoded :) in this your Oscam server. This "decoding source" is usually set in the oscam.server file. There you set up an internal card reader or also a connection to an external reader.
If your Oscam server is running on a set-top box, where you also want to use packet decoding (ie the server will also be a client), then a "dvbapi" interface is used for this purpose. In the example config (see appendix) this dvbapi is already set up. It must be set to both oscam.conf and oscam.user files.
Attached is the basic configuration of Oscam - just as an example.
Here you will find a description of the configuration files for Oscam:
How to convert "C-Lines" to "oscam.server" configuration file:
How to setup Oscam.server on H 7 C box
Of course, don't forget to add group = 1 there, because you definitely use these groups in the configuration as well. So you have to add an external reader (external Cccam server) also to this group of yours (or set up the groups as you need - according to your Oscam configuration).
That has nothing to do with it. You enter there an IP address. The IP address must be visible and an open port must also be available to connect.
only for 15 seconds, after that the reader shows unknown in the status and the user is connected but idle and in yellow
If no channels are being used by the external reader it will become idle, unless you add keepalive = 1 to the [reader] or the [account].
What does "Live Log" show in Oscam-Webif ?
Is group = 1 added also for an external reader connected by the cccam protocol ? I mean in the oscam.server file.
What does sending requests with ECM packets on both sides look like ?
Didn't you just mean EMMs writing to the decoder card ? These are very important for some coding systems. These are control packets, which, however, also write the so-called "entitlements" (table with prepaid channel packages). AU (AutoUpdate) configuration is used in Oscam for these purposes. However, in my basic oscam config-files for you, AU is already enabled.
If you also use remote Cccam set up as a softcam server, then of course you have to enable the writing of EMMs (AutoUpdate).
Problems can still arise with versions of the cccam protocol. I recommend removing the entry from the "oscam.server" file to determine the cccam version (https://wiki.streamboard.tv/wi…g/oscam.server#cccversion). Maybe it will help.
Also, Oscam softcam usually doesn't work very well with Cccam softcam. Personally, I have a good experience only with Cccam softcam in version 2.3.0 (mipsel architecture). Other versions of Cccam softcam unfortunately in my case of IRDETO coding, never worked properly. Therefore, I am forced to use only Cccam softcam in version 2.3.0. I use Oscam softcam as a server (including writing and decoding the card also on the local port - in the set-top box). I always use Cccam softcam 2.3.0 exclusively as a softcam client.
I don't even know that how you got there... everything and each other... connected to all others - between all devices there. So I probably won't advise you very much.
I don't even know what the problem is, so...
Don’t have an account yet? Register yourself now and be a part of our community!
