CCcam

Why your CCcam is freezing and what can you do?

2011-07-14T05:38:00.000-07:00

Freezing channels or slow opening channels are common problem among cccam user or even other card sharing protocol users as well.

There are several things that will cause freezing, also remember you have no control over what is happening on the server you are connected to as peer and a lot of the problems come from the other end.
But still there are certain thing you can do to improve your card sharing experience

Firstly, when you allocated your router ports, set them for for both TCP/UDP.
You can test if the ports are opening by going here:
http://www.dyndns.com/support/tools/openport.html

Some of the common causes are:

Your internet connection is slow
Check your ping times and don't download torrents at the same time when viewing or sharing with CCcam.

The person you are connected to has slow internet connection
By this i mean not only the speed but the response time as well (which is more critical than speed itself), slow response time could be because of hardware used by server holder or server is overloaded.

Multiple users on same cline.
You have the same cline active in more than one receiver in your home or someone else is using same cline.
You can't do that. Think it as two or more people talking to one person at same time on same line ....
Common symptoms are your cline is reconnecting and disconnecting every few seconds

You have two different C lines to two different servers - both supplying the same card.
This can cause problems. Test and find with which line you have the better performance. It can be easily done by connecting one line and watch channels for few hours and see which one gives less cutting or freezing

You are receiving the same card on hop1 & hop2 etc..
If it is 2 different server use the one with better response time(sometime hop2 card have beter response than hop1). Try to use the cccam.channelinfo, cccam.prio and cccam.providers files

The server is overloaded at the other end
The most common cause of all of them. An overloaded hop1 server can cause your file to connect to a Hop2 instead - but then keeps trying to get back on the hop1.

Because a guys card shows you hop1 - it does NOT mean it is hop1- or he even has a card
There are methods of faking this especially with nline and oscam - and a lot out there doing it. Try another server with the same card to compare.

Your CCcam config is not optimized
Look at other post in the forum regarding correctly configuring cccam.cfg.
You can also add name os the package or channel next to cline for reference and better management of cccam.cfg.
e.g.
C: server1.no-ip.info user1 password1 ##opens Zee network at 105.5E 5 channels
C: server2.no-ip.info user2 password2 ##opens Sky hd channels etc etc

Your dish is not tuned correctly to the sat or cable and connecting are not good
This is also a common problem where a bad connection in cable or sockets cause intermittently channel freezing or pixelating, which can so easily be mistaken with bad cline.

Certain cards freeze/glitch if the other persons file is not set up correctly
As mentioned above, you have no control over the set up at the other end however you can still inform server holder about the problem for possible fix. You have to try several sources to test for a reliable server and disconnect the rest

Remember, "Quality and not Quantity"
The trick isn't to have a lot of cards but having stable and fast ones. Filter out the crap ...

Does CCcam need Port Forwarding ?

2011-07-09T15:26:00.001-07:00

If you want to connect to a server only you do not need any Port forwarding in your router, this apply only if in your CCcam.cfg file has only C lines

If on the other hand you have a card and want to give away some shares to your friend then yes you must use port forwarding or virtual server , so saying that if you have any F lines in your CCcam.cfg you would need to setup your router with port forwarding !!

CCcam Telnet Commands

2011-07-09T15:25:00.002-07:00

Here are a few commands that will help you should you need to check CCcam via telnet.

-d run in foreground (implies -v and -q)
-v be verbose
-q don't use syslog
-C <configfile> use <configfile> instead of default (/var/etc/CCcam.cfg)
-k <keyfile> use <keyfile> instead of default (/var/keys/SoftCam.Key)
-f filter on specific demux data (saves some CPU)
-n show network packets
-s disable server
-t show timing

What is Web Interface and its parameters ?

2011-07-09T15:25:00.000-07:00

Web Interface is like a website with information about your CCcam !! This is build in the CCcam itself.

How do i access it and is it enabled by default?By default it is enabled on port 16001 and without a user name and a password. This can be accessed by entering the Dreambox/server Ip and access it with port 16001!! So lets assume your dreambox ip is 192.168.1.1 Just open your favorite web browser and enter this:

http://192.168.1.1:16001

Can i protect it with a user and a password ?
Yes you can use a username and password of your choice !! Just add this to you CCcam.cfg replace the username and pass of your choice.

WEBINFO USERNAME : username
WEBINFO PASSWORD : password

Can i use another port instead the default 16001 ?
Yes you can use any port of your choice!! Just add this line in CCcam.cfg with the port of your choice.

WEBINFO LISTEN PORT : 18000

Can i switch off the Web Interface completely?
It is possible to switch off completely the Web Interface by adding this line to your CCcam.cfg
ALLOW WEBINFO: no

Where do i put the files in my box and what they mean?

2011-07-09T15:23:00.001-07:00

CCcam.cfg ---> /var/etc -----> Configuration file, where we set the Clients and Friends and additional configuration.

CCcam.bin ---> /var/bin -----> This is the binary file ( like the .exe in windows ) This file should have 755 permission. (Right click in this file with your preferred FTP client and click set attributes). Otherwise CCcam will not start

CCcam.prio ---> /var/etc -----> This file is where you can set your priority cards or ignore any cards ( not necessarily needed to run CCcam )

CCcam.channelinfo ---> /var/etc -----> In this file you can put the channel info for the web interface, so you will see which channel is decoding CCcam instead of seeing the sid ( not necessarily needed to run CCcam )

CCcam.providers ---> /var/etc -----> In this file you can put the provider info for the web interface, so you will see which package is decoding CCcam instead of seeing the caid ( not necessarily needed to run CCcam )

SoftCam.Key ---> /var/keys -----> In this file you will find keys to open channel trough keys instead trough network ( not necessarily needed to run CCcam )

AutoRoll.Key ---> /var/keys ----> this file will have the next key the provider will have and will use the next automatically ( not necessarily needed to run CCcam )

constant.cw ---> /var/keys ----> In this file you will find constant keys to open channel trough keys instead trough network ( not necessarily needed to run CCcam )

Other files created by CCcam itself while running

warnings.txt ---> /tmp ----> Here you will find attempted logins to CCcam without your authorization , this file will be shown only if you have this line in CCcam.cfg **** LOG WARNINGS : /tmp/warnings.txt **** , be careful with this file as if you enable it and you have a lot of warnings you will run out of memory in your box

ecm.info ---> /tmp ----> this file will show you information about the encoding of the channel you are viewing

Dreambox DM-800HD Tuner Changing Video

2011-07-09T15:22:00.000-07:00

How to Block certain cards in CCcam.....

2011-07-09T15:19:00.001-07:00

It is possible to block certain cards from getting to your server, especially those fake cards or older cards:

Example:

You would like to block provider 0919 so to get the newer 093b cards from that provider.

In that case it would be necessary to make your C: line like this:

C: server.noip.com 12000 username password no { 0:0:2, 0919:0 }

Getting Started - Flines & Clines For Beginners

2011-07-06T04:22:00.000-07:00

This is probably the most confusing thing for beginners so i will try and keep this as simple as possible.
The first thing you need to to is create yourself a dns address and download the updater software to go with it.I recommend using one of the following,both are equally good.

Dyndns- Register Here - http://www.dyndns.com/
Updater Software here - http://www.dyndns.com/support/clients/windows.html

No-ip - Register Here - http://www.no-ip.com/
Updater Software here - http://www.no-ip.com/downloads.php

The dns address you choose will form the first part of all clines you send to your peers like this.

C: anyone.dyndns.org

The next part of the cline is the server listen port, by default this is 12000.
If you want to change it look in your cccam.cfg for the following line.

SERVER LISTEN PORT : 12000

you can change it to whatever you want as long as you open the corresponding port in your router.

So the cline so far reads.

C: anyone.dyndns.org 12000

This is how every cline you send will start,now you need to create a user name and password in your cccam.cfg that will allow a peer to connect to your server.This is where the fline comes in.

Remember this
F: = Friend, for others to connect to you.
C: = Connect, for you to connect to others.

To make the fline using your ftp programme connect to your box and go to Var/ect you will then see a file named cccam.cfg, right click on this and choose edit.

Everything you see with # in front of it is not read by cccam and can safely be deleted or if you wish to leave it there it will make no difference.These are the only lines that need to be there for it to work.If you find it easier delete it all then copy and paste this in its place.

SERVER LISTEN PORT : 12000
ALLOW TELNETINFO: yes
ALLOW WEBINFO: yes
WEBINFO USERNAME : yourchoice
WEBINFO PASSWORD : yourchoice
TELNETINFO USERNAME : yourchoice
TELNETINFO PASSWORD : yourchoice
TELNETINFO LISTEN PORT : 16000
WEBINFO LISTEN PORT : 16001
ZAP OSD TIME : 3
#OSD USERNAME : yourchoice
#OSD PASSWORD : yourchoice
OSD PORT : 80
SHOW TIMING : yes
DEBUG : no
NEWCAMD CONF : no
DISABLE EMM : no
EXTRA EMM LEVEL : no
MINI OSD : yes
SOFTKEY FILE : /var/keys/SoftCam.Key
AUTOROLL FILE : /var/keys/AutoRoll.Key
STATIC CW FILE : /var/keys/constant.cw
CAID PRIO FILE : /var/etc/CCcam.prio
PROVIDERINFO FILE : /var/etc/CCcam.providers
CHANNELINFO FILE : /var/etc/CCcam.channelinfo
EMM THREADS : 1
#MINIMUM DOWNHOPS: 1
#LOG WARNINGS : /tmp/warnings.txt

You can disable/enable any of these by adding/removing #

A simple Fline looks like this.

F: Joe bloggs

This is all you need for your peer to connect to you and means we can complete the cline using the user name and password from the fline.

Completed cline ready to send to your peer looks like this.

C: anyone.dyndns.org 12000 Joe bloggs

Other Settings

To optimize your servers performance and security there are some other settings to add to both the c & f lines,I recommend you start with the following on your flines

F: Joe bloggs 2 0 0 { 0:0:2 } { } { } yorpeersdnsaddress

This will give you the best performance i will now try and explain what these numbers mean

The 2 0 0

The 2 means that the peer will get all cards at a maximum of 2 hops away from you.

The first 0 means that the peer gets no emus from you. Change to 1 to get peerâ€™s emu.

The other 0 means that the peer is not allowed to send us emm. Change to 1 to take peerâ€™s emu. Please note that there has to be a corresponding entry in the in the server you are sharing with.Cccam is capable of its own emu these are the optimal settings.

The { 0:0:2 }

The 2 means that the peer can reshare your card once.Change to 1 for no reahsare,3 for 2 reshare ect,ect.

The IP or DNS address at the end of the F line

The IP Address at the end of the F:line makes sure that only the specified peer connects to your server. This is known as locking the fline and is very important against hackers.

Cccam is capable of its own emu work so there is no point using your peers or vice versa.
The safest way to share is receive emm from only the person you trust most - YOURSELF

Extra cline settings

You should restrict the amount of hops you receive from your peers as anything above hop 3 is virtually unwatchable,ideally you want to using hop1 and 2 only this is done by adding the following after the cline you receive from your peer.

No { 0:0:2 }
This means you receive your peers local and hop 1
if you are sharing without a local make this No { 0:0:3 }

Later on
Once you have most of the cards you want in hop1 and there are still some hop2 cards you use it is possible to take only the cards you want from hop2 to further improve the speed of your server.To do this add the caid of the provider like this

C: anyone.dyndns.org 12000 anyuser anypass no { 0:0:1, 0963:0:2, 093b:0:2 }

This takes the peers local plus sky uk & sky italia from hop 2

There is loads more on this but follow this guide and you should be off to a good start.Please ask as may questions as you want i will try and write a complete guide once i get some feedback on my attempts so far.