How do the sat providers update their cards.
Is it through the phone line or the dish feed ?
Is it through the phone line or the dish feed ?
Updating entitlements
- Thread starter charlie senator
- Start date
- Joined
- Aug 8, 2009
- Messages
- 6,590
- Reaction score
- 759
i have a 500c using cccam with my white sly card in, just set it up 2 days ago, whats the best way for me to update these entitlements, will it do it automatically via cccam or is it a case of putting it back in original receiver overnight to update it, and how do i know when there gunna run out to have to update them!
This is supposed to be an updating Cccam config but like you i dont know whether to use it or put the card back in the box.
Maybe one of the sat wizards can help out here
SERVER LISTEN PORT : 12000
ALLOW TELNETINFO: yes
ALLOW WEBINFO: yes
WEBINFO USERNAME :
WEBINFO PASSWORD :
TELNETINFO USERNAME :
TELNETINFO PASSWORD :
TELNETINFO LISTEN PORT : 16000
WEBINFO LISTEN PORT : 12001
ZAP OSD TIME :5
OSD USERNAME :
OSD PORT :80
# SERIAL READER :
# SMARTCARD WRITE DELAY :
# SMARTCARD CLOCK FREQUENCY: /dev/
SMARTCARD CLOCK FREQUENCY: /dev/sci0 3570000 #lower
# SMARTCARD CLOCK FREQUENCY: /dev/sci1 3570000 #upper
SHOW TIMING : yes
DEBUG : yes
NEWCAMD CONF :no
DISABLE EMM : no
MINI OSD : no
#CAM KEY
#CAMDATA
BOXKEY: /dev/sci0 xx xx xx xx
#BEEF ID :
#PIN :
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.channelinf
Maybe one of the sat wizards can help out here
SERVER LISTEN PORT : 12000
ALLOW TELNETINFO: yes
ALLOW WEBINFO: yes
WEBINFO USERNAME :
WEBINFO PASSWORD :
TELNETINFO USERNAME :
TELNETINFO PASSWORD :
TELNETINFO LISTEN PORT : 16000
WEBINFO LISTEN PORT : 12001
ZAP OSD TIME :5
OSD USERNAME :
OSD PORT :80
# SERIAL READER :
# SMARTCARD WRITE DELAY :
# SMARTCARD CLOCK FREQUENCY: /dev/
SMARTCARD CLOCK FREQUENCY: /dev/sci0 3570000 #lower
# SMARTCARD CLOCK FREQUENCY: /dev/sci1 3570000 #upper
SHOW TIMING : yes
DEBUG : yes
NEWCAMD CONF :no
DISABLE EMM : no
MINI OSD : no
#CAM KEY
#CAMDATA
BOXKEY: /dev/sci0 xx xx xx xx
#BEEF ID :
#PIN :
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.channelinf
Last edited:
I would guess the only important bit as far as enitlements are concerned is -
Entitlements are updated via the Emm mechanism. These are usually available from streamdata in several different varieties, global (all cards), group (all cards within a group of 256 cards ie 12 34 56 xx) and unique (addressed to a particular card ie 12 34 56 78).
Any cam you use must be able to interpret and extract all these packets and then send them to the card in a proper manner. Cams will often filter duplicates and buffer/prioritse emms in such a way that a card gets the most important Emm's first and with sufficient gap between them.
Note that Emm processing will usually prevent ecm processing so the cam must handle timing properly. If a lot of Emm's are presented to a card then handling multiple clients in CS may become difficult !!!
As far as CCcam is concerned, there is some suspicion that it doesn't handle emm's properly on certain systems and may be doing things that causes cards to be suspended.
Code:
You don't have permission to view the code content. Log in or register now.Entitlements are updated via the Emm mechanism. These are usually available from streamdata in several different varieties, global (all cards), group (all cards within a group of 256 cards ie 12 34 56 xx) and unique (addressed to a particular card ie 12 34 56 78).
Any cam you use must be able to interpret and extract all these packets and then send them to the card in a proper manner. Cams will often filter duplicates and buffer/prioritse emms in such a way that a card gets the most important Emm's first and with sufficient gap between them.
Note that Emm processing will usually prevent ecm processing so the cam must handle timing properly. If a lot of Emm's are presented to a card then handling multiple clients in CS may become difficult !!!
As far as CCcam is concerned, there is some suspicion that it doesn't handle emm's properly on certain systems and may be doing things that causes cards to be suspended.
Last edited:
so are you saying you should disable client emms (not that i've got any) ?
my interprition is to use ur slybox to update the card the cccam may fook ur card
Yes it seems at the moment the smart thing to do is disable client emm's and put the card in the box to update,
as to how often I dont really know but I would imagine every couple of weeks overnight should be fine
as to how often I dont really know but I would imagine every couple of weeks overnight should be fine
glic83
DW Regular
about every 6-8 weeks should cover it
How long does it need to be in the box glic ?
My entitlements run out on the 19/11
My entitlements run out on the 19/11
glic83
DW Regular
put it in overnight m8 and leave on an encrypted channel about 2 weeks before it expires
Might be silly question, but how do you find out when it expires?
- Joined
- Aug 8, 2009
- Messages
- 6,590
- Reaction score
- 759
in my cccam web browser you click entitlements,it shows the entitlements and a date next to them, im assuming this is the date they expire mate but could be wrong!
http: YOUR SERVER IP:16001/entitlements