Clean config
First things first, you need to clean up your CCcam.cfg. I'd recommend installing an application like CCcam webinfo PHP and see what your peers are sharing and if they are resharing. Contact the peers who aren't sharing to see what's going on there, if they do not respond; kick them. As a default I recommend F and C lines to look like these;
F: friend password 1 0 0 { 0:0:2 } { } { } friend.dyndns.org
C: friend.dyndns.org 12000 myname mypass no { 0:0:2 }
C: friend.dyndns.org 12000 myname mypass no { 0:0:2 }
This ensures you only receive hop1 and hop2 and only send your local and peers cards to your peers which they are allowed to reshare one more time.
The CCcam.prio file
With cardsharing it's possible that zapping channels takes some time, this can be normal as you might be trying to watch a channel for which you don't have a subscription and CCcam needs to find a valid decryption key in it's peer network.
It is annoying if you try to open a channel for which you have a valid subscription and have to wait a couple of seconds. The trick here is to tell CCcam it should try to use your card first (if possible) as the channel might be shared between several providers and many different cards might provide decryption keys for it. CCcam uses a seperate config file for that; 'CCcam.prio'. On top of this file you need to add your card type as a priority card.
# CCcam.prio
# Example; first try CD-NL (100:6a), then TVV (100:6c) and use old 622:0 last.
P: 100:6a
P: 100:6c
P: 622:0
# Example: Ignore the old Sky UK card (961:0) and use new Sky UK as priority.
I: 961:0
P: 963:0
# Example; first try CD-NL (100:6a), then TVV (100:6c) and use old 622:0 last.
P: 100:6a
P: 100:6c
P: 622:0
# Example: Ignore the old Sky UK card (961:0) and use new Sky UK as priority.
I: 961:0
P: 963:0
SID auto assign
A very cool feature is to let CCcam figure out which channels open with your specific card and build a list of that. After a while (might take a few days though) you use this channel-id list and reconfigure CCcam to only request decryption keys for these channels on your card and instantly refuse all others (no need to wait on the timeout for the decryption key any more!). You can initialize this feature by setting the appropriate line in your CCcam.cfg file:
# CCcam.cfg
# for a Linux cardserver, set a maximum of 500 auto assigned SID's
SMARTCARD SID ASSIGN : /dev/ttyUSB0 500 { }
# for a Dreambox receiver, set a maximum of 500 auto assigned SID's
SMARTCARD SID ASSIGN : /dev/sci0 500 { }
# for a Linux cardserver, set a maximum of 500 auto assigned SID's
SMARTCARD SID ASSIGN : /dev/ttyUSB0 500 { }
# for a Dreambox receiver, set a maximum of 500 auto assigned SID's
SMARTCARD SID ASSIGN : /dev/sci0 500 { }
Wait a few days, zap all the channels and the list will built up. You can check this list on the CCcam webinterface under "Entitlements". Copy the line starting with "assigned sids:", but leave that piece of text out. Paste this list between the curly brackets of the "SMARTCARD SID ASSIGN" line in your CCcam.cfg. If you are confident this list is complete and you feel brave enough then you can replace the "500" in this list with "0" (zero). All channels are now statically configured for your card resulting in faster zap times (for you and your peers!) for the channels not allowed on your local card, but queried though the CCcam network.
Satellite card overclocking
While zapping you'll also have to wait until you receive a valid decryption key, this is also called the ECM (Entitlement Control Message) time of the card. It is possible to "overclock" the satellite card in CCcam and shave 50-100 milliseconds in this process. Some cards overclock better than others and it will also depend on your cardreader. Be careful with builtin cardreaders as the card might run hot due to the generated heat of the receiver and the overclocking itself ;-)
I use overclocking to get better ECM times than my competitors on my peers. My peers will notice that I take the bulk of the ECM traffic and they will cherish our F/C lines ;-)
Here are some overclocking values I've found, I have not tested all of these myself. Replace XXX with the path to your cardreader (TTYUSB0 for linux, sci0 for a dreambox)
# CCcam.cfg
SMARTCARD CLOCK FREQUENCY: /dev/XXX 6860002 (SECA 0.330 to 0.275)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 8200000 (Irdeto 0.195 to 0.1370)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 5250000 (NDS 0.210 to 0.191)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 5300000 (NDS 0.191 to 0.172)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 5600000 (Conax 0.275 to 0.178)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 8300000 (Irdeto2 0.215 to 0.151)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 8420000 (Irdeto2 0.225 to 0.140)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 6860002 (SECA 0.330 to 0.275)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 8200000 (Irdeto 0.195 to 0.1370)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 5250000 (NDS 0.210 to 0.191)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 5300000 (NDS 0.191 to 0.172)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 5600000 (Conax 0.275 to 0.178)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 8300000 (Irdeto2 0.215 to 0.151)
SMARTCARD CLOCK FREQUENCY: /dev/XXX 8420000 (Irdeto2 0.225 to 0.140)
What are your overclocking values? :)
