CCcam Debugging Information

I just stumbled upon this great tutorial where there are listed probably all CCcam errors and possible solutions for them. For this tutorial to be useful you need change/add one line in CCcam.cfg and start CCcam with special command. Here is how you need to do it:

1. Run CCcam from telnet with this command:/var/bin/CCcam -d >>/var/log/debug &

2. If you have a linux server like Ubuntu, you can add this line into CCcam.cfg: DEBUG: yes
All debugging data is then automatically stored here and without the need to use upper command: /var/log/debug

Access to tutorial: http://www.sat-dreambox.com/f643/cccam-debugging-8463/


Connect OScam with CCcam using CCcam protocol

This tutorial will be short. It is intended for people who have CCcam central server (Linux PC for example) and receivers with OScam which act as clients. Protocol which is used between OScam and CCcam is good old CCcam 🙂

Put these lines in oscam.server:

label                         = remote
protocol                      = cccam
device                        =,12333  #Change these two settings according to your setup. 12333 is port of my CCcam server. If OScam and CCcam runs on same receiver, just use instead of regular 192.168.x.x IP address!
user                          = test #You will have to create F line in CCcam.cfg with username and password that you used here!
password                      = testxxx
group                         = 1
emmcache                      = 1,3,2

This config is basic but you dont need additional (more advanced) settings. It works just fine! If you want faster zapping, then i recommend that you setup oscam.dvbapi file!

In CCcam.cfg create this line:

F: test testxxx 2 0 0 { 0:0:1 }

2 0 0 means that your receiver will get your local cards (if you have them), hop 1 and hop 2 cards. If you have server with only hop1 cards, you can just use 1 0 0

0 0 1 means that your receivers cannot share to other receivers. Thats ok, because you dont need reshare in your house. Reshare (0 0 2) is usually needed if you are sharing with clients outsite your house.

Thats it, for more info use comments.

For discussion please visit this thread:


For other “connect” tutorials, visit these links:


CCcam to CCcam Tutorial

How to connect two CCcams using two receivers. Easy!

Lets say we have Receiver 1 (R1) and Receiver 2 (R2). IP address of R1 (primary receiver – server) is, IP address of R2 (secondary receiver – client) is

In R1 we add this line in CCcam.cfg (you can get it on my blog, please use search in order to find it):

F: server test 2 0 1 { 0 0 2 }

In R2 we add in CCcam.cfg this line:

C: 11111 server test no

11111 is port but this doesnt really matter, because we will be sharing only in our own house not with outside world 😉

Thats it. This is basic tutorial for homesharing with CCcam. You will maybe start to ask yourself what does 2 0 1 { 0 0 2 } mean. Well lets say that you dont need to know anything else, especially if you are the beginner. For more info you will have to visit more detailed tutorials about CCcam which can be found on my site too!


CCcam C-line Tutorial

Source: http://linuxsat-support.com/cccam-support-tutorials/4907-cline-setting.html

Syntax : C: <hostname> <port> <username> <password> <wantemus> { caid:id:uphops, caid:id:uphops, … }

In a C line we can have :

1. Instructions where to look for a server <hostname>
2. Which port that server is using <port>
3. Username to connect to that server <username>
4. Password to connect to that server <password>
5. If you like to recieve Emulator shares from keys <wantemus> (i recommend using “no” here)
6. Limiting what to get from that particular server { caid:id:uphops, caid:id:uphops, … }


Basic C line that most users will use :
C: server.noip.com 12000 username password

C line that is more appropriate if you do not want to recieve key Emulators:
C: server.noip.com 12000 username password no

C line that is more appropriate if you want to recieve key Emulators (NOT  recommended) :
C: server.noip.com 12000 username password yes

Cline that will limit to receive all shares that are only up to 2 hops away (Recommended!!):
C: server.noip.com 12000 username password no { 0:0:2 }

Cline that will get all shares but does not get a specific provider:
C: server.noip.com 12000 username password no { 0:0:2, 093b:0 }

Cline that will get all shares but does not get specific providers:
C: server.noip.com 12000 username password no { 0:0:2, 100:3, 100:4, 100:5, 100:9, 100:A, 100:c }


Connect MGCamd and CCcam

You probably know MGCamd. This is great client EMU that is in my opinion better than CCcam and OScam (as client!!). Configuring is quite easy, you just need to have right instructions. For example, OScam is real pain in the arse when you want to set it up.

Well I prepared a package for you: https://www.satnigmo.com/MGCAMD_1.38_MIPS.rar

Here you will get mgcamd 1.36 for mipsel receivers (VU+, CT and Dreambox receivers) + two config files. One is called mg_cfg, other one is cccam.list. Both files need to be in var/keys

mg_cfg is already edited so it can be used immediately (mgcamd+cccam connection)! What you need to do is to make a C line and copy/paste it in cccam.list file. Easy! I assume you know how to make C line? First you need to make F line on your server side where cccam is running. Then simply make C line from that F line! For more instruction check google 😉

And thats it! You now have MGCamd which is connected to CCcam server. You will see that MGCamd is very fast when it comes to zapping speed 😉



Powered by moviekillers.com.com

Seraphinite AcceleratorOptimized by Seraphinite Accelerator
Turns on site high speed to be attractive for people and search engines.