Why your CCcam is freezing and what can you do?

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 ...