Cline to oscam

There are 47 replies in this Thread which was already clicked 9,664 times. The last Post () by s3n0.

  • OK try to verify that the configuration files are in the correct folder, because if you used the ipk / deb installation package, it could also create default config.files in another folder and then this folder will be used in Oscam as well.


    Read more about configuring the configuration directory here:

    find oscam location


    I add that the "oscam.server" file is not enough. The "oscam.conf" file is also important, as a basic configuration for Oscam. Or also the "oscam.user" file for setting up a dvbapi local user. Or, if you use CAIDs in your config files, the "oscam.dvbapi" file (for setting CAIDs priorities) may be also important.

  • At least someone thanks :).


    Great.


    Many users do not even write whether the problem was solved or how they solved the problem :) - which would help other users if the same problem occurs.

    Hmm... that's not fair, I guess many people never solve the problem on them own.

    I should have get test lines before I bought it. Lesson learnt.

    Thanks again :thank_you2:

  • hello folks,


    I need your help. I'm having problems with oscam. After an hour the image on my box freezes, and I need to restart the oscam. Now I wonder what to do about this. I have already looked around a bit on this forum and came across a few things. I am currently using the files from master G 'Basic OSCam config with dvbapi configured'. I saw that he advised not to include ccckeepalive in the oscam.server file cause off glitching, but without this setting I have no image. My knowledge about this is very minimal. Thanks in advance!


    Device: VU + duo 4K se

    Image: VTi 15

    OScam: OScam 1.20_svn Build: r11603


    oscam.config

    [global]

    logfile = /dev/tty

    clienttimeout = 4000

    clientmaxidle = 300

    netprio = 1

    nice = -1

    maxlogsize = 1000

    waitforcards = 0

    preferlocalcards = 1

    dropdups = 1


    [dvbapi]

    enabled = 1

    au = 1

    pmt_mode = 0

    request_mode = 1

    user = linuxsatsupport

    read_sdt = 1

    write_sdt_prov = 1

    boxtype = dreambox


    [webif]

    httpport = 8888

    httpshowmeminfo = 1

    httpshowuserinfo = 1

    httpshowcacheexinfo = 1

    httpshowecminfo = 1

    httpshowloadinfo = 1

    httpallowed = 127.0.0.1,192.168.0.0-192.168.255.255,10.0.0.0-10.255.255.255,::1

    http_status_log = 1


    [newcamd]

    port = 10001@0963:000000

    key = 0102030405060708091011121314

    mgclient = 1

    keepalive = 1


    [cccam]

    port = 12000

    version = 2.0.11

    build = 2892

    reshare = 1


    oscam.server

    [reader]

    label = ziggo

    protocol = cccam

    device = server:port

    user = username

    password = password

    caid = 0604

    group = 1

    audisabled = 1

    ccckeepalive = 1



    oscam.user

    [account]

    user = linuxsatsupport

    group = 1

  • Hello.


    I recommend using Cccam-softcam instead of Oscam-softcam (if you only want to use softcam as a client). Personally for me the Oscam makes problems in Irdeto. Of course, this depends on the different details of the particular provider and the particular decoding card algorithm. In my opinion, changing the Oscam configuration will not help to you.


    You can simply use the Cccam v2.3.0 softcam at least for stability testing. I had similar problems and no Oscam configuration helped to me. I already have better experience with configuring Oscam :) so I know what I'm setting up in Oscam. However, I have no experience with DVB technology (eg such as DVB-S encryption algorithms), because I am not very interested in this :). I've tested a lot of things in Oscam configuration. Unfortunately, no result.


    In my case, the Oscam accidentally froze, within 1-2 days, any Oscam version (I tried old and new versions), as a softcam-client. I tested the connection via the "newcamd" protocol but also via the "cccam" protocol - I tried both protocols. In the case of cccam protocol, I also tried to force different version (2.0.11, 2.1.0, 2.2.1, 2.3.0, 2.3.2, ...).


    Finally, the use of cccam-softcam (as a client) helped.


    I did not use EMM packet writing (AU / AutoUpdate) with a remote softcam client. EMMs are registered on the main set-top box, on which Oscam (as a softcam-server) runs successfully.

  • look this config please klick me

    It just froze on me again... :unhappy1:




    My box doesn have cccam in its feed because it has a ARM chipset. Is cccam 2.3.0 available for arm? Thanks!

OSCam Support Forum

Configs, discussion, downloads and guides for OSCam Softcam.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!