Oscam takes time to descramble

There are 4 replies in this Thread which was already clicked 3,186 times. The last Post () by RayBobo.

    Sorry, made a mistake first, posted in oscam-emu...

    Hello,


    :hello



    New on this forum, happy to find I hope some help for my "little" problem;



    When arriving on some channels, or when returning, sometimes and mostly on the same channels, my Oscam takes circa 30 seconds to 1 minute to descramble.

    Here under an extract from the log when it happens.


    2019/05/18 17:56:42 15B999C7 b (dvbapi) Demuxer 0 restarting decodingrequests after 2 ms with 2 enabled and 4 disabled ecmpids!
    2019/05/18 17:56:42 15B999C7 b (dvbapi) Demuxer 0 trying to descramble PID 1 CAID 0500 PROVID 099990 ECMPID 0333 ANY CHID PMTPID 0334 VPID 0334
    2019/05/18 17:56:43 15B999C7 b (ecm) anonymous (0500@099990/09999/XXXX/86:D5550E19E788888DFBDADC69F555551E): not found (1 ms) by TVFR - ANIMAUX
    2019/05/18 17:56:43 15B999C7 b (dvbapi) Demuxer 0 trying to descramble PID 5 CAID 0100 PROVID 00006D ECMPID 05E0 ANY CHID PMTPID 0334 VPID 0334
    2019/05/18 17:56:44 15B999C7 b (ecm) anonymous (0100@00006D/5C00/XXXX/64:40462B666666C6A5DFA54F0D4D4C321AB): not found (279 ms) by TELEBOUM – ANIMAUX     2019/05/18 17:56:44 15B999C7 b (dvbapi) Demuxer 0 restarting decodingrequests after 2 ms with 2 enabled and 4 disabled ecmpids!

    2019/05/18 17:56:44 15B999C7 b (dvbapi) Demuxer 0 trying to descramble PID 1 CAID 0500 PROVID 099990 ECMPID 0333 ANY CHID PMTPID 0334 VPID 0334

    2019/05/18 17:56:46 15B999C7 b (ecm) anonymous (0500@099990/09999/XXXX/86:D5550E19E788888DFBDADC69F555551E): found (1426 ms) by TVFR - ANIMAUX

    2019/05/18 17:56:59 15B999C7 b (ecm) anonymous (0500@099990/09999/XXXX/86:27C463B71777777DEDCF034B4444442D20): found (1458 ms) by TVFR - ANIMAUX


    What can be the cause of this and what are the parameters I have to check?


    OpenPli 6.2, Oscam r11493, Vu+Duo2


    Many thanks for the help.

    Only a long timeout attempt to search the CAID + PID on the remote reader is visible in your LOG. Nothing else. So the error can be anywhere in 100 different cases.


    You probably use a reader emulator (or "Oscam-Emu" client), judging by PROVID 099990, and also you mention it in the introduction. So why did you put this post under "Oscam" instead of "Oscam-Emu" forum thread ?


    Also, you did not list configuration files so guessing is unnecessary.


    However, I will only try to guess:


    The client attempts to connect via a badly set (unnecessarily and manually configured) reader weight. Then it turns out that the client tries to connect with higher priority (focused) to the remote reader where the decoding channels are not available. Up to a few seconds later, the client also connects to other readers according to a set weight where the decoding channel already needed exists.

    Quote from s3n0

    The client attempts to connect via a badly set (unnecessarily and manually configured) reader weight. Then it turns out that the client tries to connect with higher priority (focused) to the remote reader where the decoding channels are not available. Up to a few seconds later, the client also connects to other readers according to a set weight where the decoding channel already needed exists.

    Ok and thanks for the answer.


    It seems strange to me and hard for me to understand all what you says, as newbie in oscam. And the other channels on the same reader doesn't create problem. Only 1 channel mainly create this, and not always...


    I give you here under what looks this reader:


    [reader]

    label = ZOP1

    protocol = newcamd

    device = beloubi.argdns.org,XXXXX

    key = XXXXXXXXXXXXXXXXXXXXXXXXXXXX

    user = BobZop

    password = Zop

    inactivitytimeout = -1

    disableserverfilter = 0

    connectoninit = 1

    caid = 0X00

    ident = 0X00:042XX0

    group = 31

    blockemm-unknown = 1

    blockemm-u = 1

    blockemm-s = 1

    blockemm-g = 1


    Thanks again for the help

    Hello.


    I won't help anyway.


    I don't know your CAID (your provider) because you also added "X" to the CAID. Also, I don't know your other configuration files - maybe there is an error in them (oscam.dvbapi, oscam.conf, oscam.user). I don't understand why you are using group number 31. This setting is used for internal Oscam configuration only, to effectively integrate connected users into multiple groups (for example, set different group access rights for different CAIDs on Oscam server).


    Since I don't know your provider, I don't even understand EMM blocking. I can't comment on it. Some providers require it, and some do not. The same applies to the remote reader (remote Oscam server). However, these EMMs can also be blocked by simple audisabled = 1 in the reader section of oscam.server or by adding au = 0 to the particular user in the oscam.user file.


    I don't understand why I see anonymous and dvbapi (local user) connections there. Maybe you have wrong oscam.conf and oscam.user files. Either deactivate the user's dvbapi (primarily to make Oscam client connect to his own server - as himself) or either use dvbapi, but you have to set it up correctly. To use the dvbapi, set this:


    - oscam.conf :

    Code
    [dvbapi]
enabled                 = 1
au                      = 1
user                    = internal_user

    - oscam.user :

    Code
    [account]
user     = internal_user
pwd      =
au       = 1
group    = 1


    If you are using a group, you must have it set in both oscam.server + oscam.user (for the user you want to access). Don't forget to edit au = 0 if you don't need to send EMMs. However, much depends on the principle of encoding your provider (the principle of the remote server with a card reader).


    Sometimes, EMMs may not be blocked and sometimes the server itself will be blocked if it has been set up. On the client side, they are often blocked so that they do not overwhelm the server unnecessarily (it is sufficient if only one client sends EMMs to the server). Sometimes only some EMMs are required (only certain type).


    If you just connect to a remote server and have no card in your set top box, and if you are blocking EMMs, then you probably don't need to activate the dvbapi user at all.

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!

Register Yourself Login