Some people use CCCam for its simplicity. OSCam is a good emu when used on its own but if its not setup correctly it can cause ecm flooding when it connects to a CCCam server. A lot of people use CCCam for these reasons.
Here are a few threads that will explain this better;
Oscam using CCcam or oscam alone? What's best?
Why not use Oscam as a server with CCcam protocol?
Display More
Upon reading on the link Oscam using CCcam or oscam alone? What's best? would like to summarize it here:-
OSCan+CCcam
a) Possible of crashes when it comes to we start one side of the emulator (OScam) only, and not both. This will cause CCcam to run in and read the card (/dev/sci0 card reader) where by it is not suppose be.
b) When OScam + CCcam restart at one time, but CCcam fully loaded first before OScam. Causing same problem as above.
Nothing much after that because the content twisted to OSCam+CCcam explanation.. (Running out of topic)
My thinking on this: I think the way of that 2 above main problem happen when the STP is set to run 2 lines from both OSCam + CCcam. (Correct me if I'm wrong).
Let say if I split out the emu work into 2 section, whereby OSCam will purely work as a card reader job, not others.
CCcam job will be fully on peering job, whereby providing access to STB.
With this separation of job, would it be able to solve the crash problem?
------------
On Reference Link Why not use Oscam as a server with CCcam protocol?[/QUOTE] summarize :-
Purely on OSCam
a) Issue of faker when it happen to be a barter trade of N Lines. However someone pointed out it can be solve by grouping it correctly, but to conclusion or solid prove on it.
b) Hopping issue, where by I still do not understand
c) Pure response on bug reporting for OSCam, and they simply mark "solved" to ""unsolved"" issue.
OScam+CCcam
a) Problem of CCcam ver 2.1.3 or below with the "256" tricks
Summary
As I had mentioned above, what if OSCam work purely as "Card Reading Job" only and "CCcam" works as "Peering Job to STB", will it be a perfect solution??