Welcome!

Welcome to Satlover forums, full of great people, ideas and excitement.

Please register if you would like to take part. link..

Register Now

Alert: Don't Use Hotmail Email Accounts for registration

Collapse

Before Access to all Forums and Trial accounts you must need to activate your account Email address

CCcam Frequently asked questions

Collapse
This is a sticky topic.
X
X
 
  • Time
  • Show
Clear All
new posts
  • aplok
    Experienced Board Member
    • Jun 2013
    • 1155

    Re: CCcam Frequently asked questions

    thx !

    yes indeed, here is from readme:

    - Example C lines, which is receiving cards from hop 3
    but do not want to receive provider 093b - Sky Italia:

    C: server.dns.com 12000 username password no (0:0:3, 093b: 0)

    and a nice example from
    __http://www.satlover.eu/forum/cccam/49898-how-do-i-apply-a-cline-to-sky-network-or-zee-network-only.html#post282551

    abstract
    C: <hostname> <port> <username> <password> <wantemus> { caid:id(:uphops), caid:id(:uphops), ... }

    Digital+ (19E/9E) on hop2 (0100:4106)
    Canal+ France (19E) on hop1 (0100:3315)
    Canal+ Nederland/Euro1080 (19E/23E) on hop1 0100:006A
    TVB/ABS/Showtime+ART+JSC/CTI/Bulsatcom/DSTV/TVHOME (13E/9E/5W/7W/15W/39E/68E/DVBC) on hop1 (0604)
    SKY Italia (13E) on hop1 (093B)
    SKY UK (28E) on hop1 (0961)

    gives the cline:

    C: <hostname> <port> <username> <password> <wantemus> no { 0:0:0, 100:4106:2, 100:3315:1, 100:6A:1, 604:0:1, 93B:0:1, 961:0:1 }

    0:0:0 -> 0:0 (all caid) :0 (authorized beyond 0 hop ) -> all caid rejected
    100:4106:2 -> 100:4106 ( Digital+ (19E/9E) ) :2 (authorized beyond 2 hops, 3 and more -> rejected )
    ...


    so, it is good to keep in mind:


    0:0:0 -> 0:0 (all caid) :0 (authorized beyond 0 hop ) -> all caid rejected
    0:0:1 -> 0:0 (all caid) :0 (authorized beyond 1 hop ) -> any server 1 hop away accepted
    0:0:2 -> 0:0 (all caid) :0 (authorized beyond 2 hop ) -> any server up to 2 hops away accepted

    Comment

    • SatWaveDude
      Board Senior Member
      • Apr 2012
      • 220

      Re: CCcam Frequently asked questions

      Yes kalpikos, this is the line command that I was looking for!

      C: server.dyndns.info 12000 login password no { 0:0:2, 0100:00006A:0, 0100:00006C:0, 0100:00006D:0 }

      But without the 0500:023800:0 this is a typo I guess
      SatWaveDude

      DM500HD, DM500+ | EMP S16/1PCP-W3 | WaveFrontier T90 | 16x SMART Titanium 0.1dB LNB's
      TechniSat SkyStar S2 PCI / SkyStar USB HD
      WaveFrontier T90 rev.2 - 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 3.3E | 4/5E | 0.8W | 7/8W | 12.5W

      If you find my post usefull please press the Thanks Button

      Comment

      • kalpikos
        Experienced Board Member
        • Sep 2011
        • 7663

        Re: CCcam Frequently asked questions

        oh , yes my friend
        I'm sorry for the wrong tyring

        The correct c-line is:

        C: server.dyndns.info 12000 login password no { 0:0:3, 0100:00006A:0, 0100:00006C:0, 0100:00006D:0 }

        I hope to work for you
        If You Like My Post..... Please Press the Thanks Button

        Comment

        • Triad
          Experienced Member
          • Jan 2012
          • 422

          Re: CCcam Frequently asked questions

          Nice to get this well written explanations Aplok...
          Only one thing to report. I don't know how you all are doing with your cccam.cfg priority files since those are defined in the cline itself?
          I'm experiencing non applying of those changes defined in cccam.cfg.
          Correctly denominated caids with their hops and that filter is not filtering any of the demands!?
          Thinking it could be to cccam installation since I've changed version from 2.3.0 to 2.2.1?
          In the other hand cccam.prio list changes are doing the job very well...
          Does anyone have any similar situations with filtering in your cccam.cfg clines!?

          Comment

          • SatWaveDude
            Board Senior Member
            • Apr 2012
            • 220

            Re: CCcam Frequently asked questions

            Originally posted by aplok
            so, it is good to keep in mind:


            0:0:0 -> 0:0 (all caid) :0 (authorized beyond 0 hop ) -> all caid rejected
            0:0:1 -> 0:0 (all caid) :0 (authorized beyond 1 hop ) -> any server 1 hop away accepted
            0:0:2 -> 0:0 (all caid) :0 (authorized beyond 2 hop ) -> any server up to 2 hops away accepted
            That is very well explained and understandable for evryone!

            We know that the third position has the function of how many HOP's away from you that you like to receive.

            What are the position one and two and what values are allowed?
            Can someone explain a bit more about these?
            SatWaveDude

            DM500HD, DM500+ | EMP S16/1PCP-W3 | WaveFrontier T90 | 16x SMART Titanium 0.1dB LNB's
            TechniSat SkyStar S2 PCI / SkyStar USB HD
            WaveFrontier T90 rev.2 - 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 3.3E | 4/5E | 0.8W | 7/8W | 12.5W

            If you find my post usefull please press the Thanks Button

            Comment

            • aplok
              Experienced Board Member
              • Jun 2013
              • 1155

              Re: CCcam Frequently asked questions

              Originally posted by SatWaveDude
              What are the position one and two and what values are allowed?
              Can someone explain a bit more about these?
              hi, here it is

              Caid:Provider:uphops

              just as in

              Code:
              +----+----------+-------------------------------+-----------+
              |Caid| Provider | Provider Name                 | System    |
              +----+----------+-------------------------------+-----------+
              | 500|     42400|JSC Sports (13E/20E/26E/7W)    |viaccess   |
              
              Caid:Provider:uphops
              500:42400:3
              
              caid : card id

              Comment

              • aplok
                Experienced Board Member
                • Jun 2013
                • 1155

                Re: CCcam Frequently asked questions

                hi,

                i have such a connection, but no tv channel !
                why ?

                thx

                Code:
                Server connections: 1
                +-------------------------+------------+---------+--------+----------------+-------+-------------------------------+
                | Host                    | Connected  | Type    | Version| NodeID         | Cards | CAID/Idents                   |
                +-------------------------+------------+---------+--------+----------------+-------+-------------------------------+
                |cccam.org:1245           |00d 00:31:39|CCcam-s2s|2.1.3   |1122334455667788|    29 |local 0500:032940 567(0)       |
                |                         |            |         |        |                |       |local 0500:032830 567(0)       |
                |                         |            |         |        |                |       |                               |
                +-------------------------+------------+---------+--------+----------------+-------+-------------------------------+

                Comment

                • aplok
                  Experienced Board Member
                  • Jun 2013
                  • 1155

                  Re: CCcam Frequently asked questions

                  cccam changelog history

                  here is the changelog with all the details

                  as it is not always delivered in tgz, i gives here after the full version


                  --read CCcam.cfg for details--

                  2.3.0
                  -add seca tunneled nagra card support (may need card reset to see new revision after updating)
                  -add SID LIMIT (see CCcam.cfg for details)
                  -several smartcard fixes
                  -several network fixes

                  2.2.1
                  -added via 3.0 emu (add working key in SoftCam.Key)
                  -fixed parsing GLOBAL EMM setting
                  -fixed occasional freeze (bug since 2.2.0)
                  -random loadbalance preference
                  -smartcard fixes

                  2.2.0
                  -several smartcard fixes
                  -added SCIDEVICES setting (see CCcam.cfg for details)
                  -fixed timings display
                  -fixed possible crash with SMP
                  -don't clear SMARTCARD SID ASSIGN and LOADBALANCE settings when configfile changes (changing these settings requires a restart, so they should not be touched when config is re-read)
                  -added SMARTCARD SID REJECT (see CCcam.cfg for details)
                  -distribute ASSIGN/REJECT info to clients to improve performance (needs 2.2.0 server and clients)
                  -improved detecting when CCcam.cfg has changed
                  -added GLOBAL EMM setting (clientside), to control generation of GA EMM traffic (see CCcam.cfg for details)

                  2.1.4
                  -ndz smartcard fixes
                  -ecm timeout decreased
                  -via26 emu
                  -seca handler improvement

                  2.1.3
                  -important cardreader fixes
                  -DRE crypt support
                  -963 support
                  -reenabled n2 emu

                  2.1.2
                  -several smartcard fixes
                  -via emm fixes
                  -seca emm fixes
                  -added SMARTCARD SID ASSIGN, see CCcam.cfg for details
                  -TNT sat
                  -double login loop fix
                  -serverside emm overload fix

                  2.1.1
                  -fixed MINIMUM CLIENT VERSION check, broken since 2.1.0
                  -several smartcard fixes

                  2.1.0
                  -keep persistant ecm counts for clients
                  -i2 emu
                  -IGNORE NODE option (see CCcam.cfg)
                  -emm caid tunneling
                  -Added seca handler to prefer or ignore SECA2 or SECA3 (see CCcam.cfg)

                  2.0.11
                  -support caid tunnelling
                  -improved chid selection

                  2.0.10
                  -improved system selection (based on distance). Note that prios from prio file overrule this and might give worse results
                  -fixed aborting lengthy request when switching channels
                  -fixed low audio pid detection

                  2.0.9
                  -improved system selection
                  -fixed irdeto chid selection
                  -dm800 detection
                  -fixed minor memleak

                  2.0.8
                  -fixed n2 emu freezes with static (non-openssl) version
                  -improved system selection (making prio file mostly obsolete)

                  2.0.7
                  -fixed camcrypt on static (non-openssl) version
                  -fixed segfault reading config

                  2.0.6
                  -ignore errors on emm demux (caused n2 AU to abort on certain hardware)
                  -tps au fix
                  -various optimizations; avoid server slowing down because of slow clients

                  2.0.5
                  -global share limits (see CCcam.cfg for details)
                  -global minimum required downhops setting (see CCcam.cfg for details)
                  -n2 AU fix (/var/keys/ROM120.bin required)
                  -cryptoworks sc fix
                  -90f sc fix
                  -viaccess sc emm fix
                  -changed 'double client login reject' mechanism
                  -G line local sharing fixed
                  -graceful shutdown

                  2.0.4
                  -support more than one emm listener (see CCcam.cfg for details)
                  -tps au fixes
                  -nds sc init fix

                  2.0.3
                  -nagra fixes
                  -G line remote sharing fixed
                  -allow more limits in C/F/G

                  2.0.2
                  -nagra fixes
                  -irdeto camcrypt
                  -tps au
                  -cryptoworks keys no longer hardcoded

                  2.0.1
                  -changed G: line syntax, see CCcam.cfg for details
                  -multiple G: lines on the same local port supported
                  -each G: line can have different localhost
                  -each G: line can have different pass
                  -sharing between G: lines supported
                  -nagra2 MECM

                  2.0.0
                  -removed gbox_indirect support
                  -added gbox support
                  -several smartcard fixes
                  -several smartcard reader fixes
                  -fixed LOADBALANCE parsing (broken in 1.7.1)

                  1.7.1
                  -several smartcard fixes
                  -conax ca pin support (use 'PIN:' in CCcam.cfg)
                  -added SMARTCARD WRITE DELAY setting, to tweak performance on mastera/sc8in1 and such
                  -moved providernames to an external file /var/etc/CCcam.providers. Format is 'hexvalue "providername" comments'
                  -channelname can now be displayed in webif instead of caid:ident:sid when defined in /var/etc/CCcam.channelinfo
                  -demuxapi support dropped
                  -gbox indirect: reuse slots
                  -avoid glitch when zapping over recorded channel (7025)
                  -two cam devices on DM600

                  1.7.0
                  -fixed password bug (consider using "MINIMUM CLIENT VERSION: 1.7.0" to avoid risk)
                  -added viaccess smartcard emm
                  -added support for gbox indirect/local connection
                  -added optional ip address/hostname to F: line, no ip given allows the connection from all ip's (See CCcam.cfg for example)
                  -tps au (tune to Hotbird transponder 10873 vertical)
                  -added smartcard custom post-init (see CCcam.cfg) Currently only T=0 supported
                  -support to override detected dvb api version
                  -support sc8in1 (note: PHOENIX READER PATH --> SERIAL READER in CCcam.cfg)

                  1.6.2
                  -fixed crash when reading malformed SoftCam.Key
                  -fixed possible crash betacrypt smartcard emm
                  -minor irdeto improvements
                  -added config option to avoid (hidden) chids being ignored on irdeto smartcard (See CCcam.cfg)
                  -added timeslots per friend connection, now possible to only open connection for a few hours (See CCcam.cfg for example)
                  -Nagra emu fixes

                  1.6.1
                  -fixed irdeto camdata setting (setting was not used correctly in 1.6.0)
                  -CCcam.prio: nagra caid:ident entries with nonzero ident now always match
                  (nagra ident is unknown at time of prio check, see CCcam.cfg for details)
                  -few small workarounds for buggy 7025 scidriver
                  -show share (nodeid_handlerid) in ecm.info
                  -tps.bin support (fixed location /var/keys/tps.bin), using systemtime

                  1.6.0
                  -fixed wrong irdeto camdata default (since 1.4.0)
                  -implemented irdeto camdata setting
                  -improved self learning for irdeto
                  -fixed constant cw
                  -added biss support
                  -added priolist support
                  -max C / F username length now 20 instead of 19
                  -max C / F password length now unlimited instead of 16
                  -switches to enable/disable web and telnet info info interfaces
                  -implemented authentication for web and telnet info interfaces
                  -Note: the web and telnet info port paramater have changed name in the config file
                  -Note2: /var/keys/CCcam.ignore does not exist anymore and /var/etc/CCcam.prio is the new one
                  see CCcam.cfg for details

                  1.5.0
                  -improved dvb api detection (for systems with both demuxapi and dvb devicenodes)
                  -avoid exit on systems that provide nonworking dvb devicenodes
                  -avoid blocking on nonworking newcamd connection (since 1.4.0)
                  -added column in client info output to see the ecm time per client, only available if SHOW TIMING is on
                  -reworked share and provider info into tabular form

                  1.4.0
                  -implemented irdeto camkey setting
                  -runtime dvb api version detection
                  -implemented share limits on client side (just like server side), see CCcam.cfg for details
                  -implemented load balancing between identical cards, see CCcam.cfg for details
                  -finetuned tcp behaviour and settings, saving some network load
                  -fixed newcamd connection emm
                  -seca smartcard entitlements fix
                  -irdeto smartcard emm fix
                  -removed -k cmdline parm, use config file instead
                  -cmdline parms could previously be overruled by rereading cfg file, fixed

                  1.3.1
                  -7025: several bugfixes
                  -7025: decoding of all 8 channels (1.3.0 only 4)
                  -fixed viaccess smartcard
                  -fixed stealth mode, also set per N line now (see CCcam.cfg)

                  1.3.0
                  -fixed some 64 bits issues
                  -fixed radegast provider id and nano field
                  -reduced binary size
                  -immediately interrupt lengthy emu calculations when zap takes place
                  -userinfo was not correctly reread, therefore you needed to restart CCcam when certain parts of the userinfo changed, fixed
                  -it is now possible to block a channel for a client, based on caid:id:sid see F entry config for an example
                  -changed emu share limits behaviour, <1.3.0 an emu matched a F entry limit with {caid:ident:n}, for any nonzero ident. >=1.3.0, an emu only matches {caid:0:n}
                  -added '-l' cmdline option, to disable all 'self-learning' stuff. This option might avoid problems with irdeto smartcards
                  -ports 15000-15004 and port 14000 are now gone. Use 16000 and 16001 (html) instead
                  -implemented workerthread pool to handle client requests, to improve handling larger numbers of clients
                  -added support for cryptoworks camcrypted cards (incl arena tv). IPK handing is internal, no need for external keys and such
                  -added support for BEEF patched cards using nagra over seca tunnelling, add id's in config file(see example)
                  -added conax smartcard support (ecm+emm)
                  -added entitlements for cryptoworks and conax smartcards
                  -allow emm one extra level

                  1.2.1
                  -fixed smartcard support for some seca providers
                  -fixed smartcard activation for some seca providers

                  1.2.0
                  -fixed betacrypt entitlements
                  -fixed betacrypt emm
                  -fixed nds entitlements
                  -fixed nds freeze with certain ecm on phoenix
                  -irdeto emu emm added
                  -seca emu added
                  -initialise all cards before starting to decode, ensures immediate success on startup
                  -restart emm when a card is inserted, for easier activation of new cards
                  -faster client ecm handling (new client logon no longer delays requests of existing clients)
                  -command-based info interface on port 16000
                  -web info interface on port 16001
                  (As of now getting info from ports 15000-15004 is deprecated. This interface will be removed in the next release.)
                  -newcamd stealth mode added
                  -removed <1.1.1 backward compatibility code from share protocol, to allow full use of optimisations introduced in 1.1.1
                  -when CCcam was connecting to a share it kept on connecting on same ip, not very good when a dyndns address was in the config
                  -ecm request cache didn't work in all situations, caching fixed and improved.
                  -emm didn't always work on demuxapi systems (e.g. relook, mutant). Fixed.
                  -WARNING: F: entry syntax changed, check and update your CCcam.cfg; added parameters to allow emusharing and emm, per client

                  1.1.1
                  -when a share doesn't work for a certain channel, skip aliases of that share for that channel
                  (aliases are the same cards shared through different routes, they have equal nodeID_shareID at the end of their line in the output on port 15002)
                  -ignore '0' providerids on seca cards
                  -nagra2 emu fix for some providers
                  -fixed occasional nds emm freeze
                  -allow multiple L: entries to connect to different cards on the same camd3 server/port
                  -fixed phoenix on certain comport chipsets
                  -optimized share protocol (backward compatibility with <1.1.1 guaranteed, warning, will be removed in next release)

                  1.1.0
                  -camd3 support, one card per L: line
                  -support to add downshare limits to F: entries

                  1.0.0
                  -first public release
                  -various smartcards
                  -various emus
                  -share2share support (C: and F: entry)
                  -newcamd support (N: entry)
                  -radegast support (R: entry)
                  -all shares are available for clients on a single port (default 12000)
                  -emu's can be shared one hop down only
                  -cards can be shared multiple hops down
                  -each CCcam node has a unique nodeid
                  -routes to a card are given with nodelists
                  -when a card is reachable through multiple routes, each unique route will be available as individual share
                  -shares with nodeid 'abc' in the routelist are never sent to client with nodeid 'abc', to avoid route loops
                  -watch your shares, including full routelist, on port 15002
                  -start with -h to view available commandline options
                  -syslog support, start with -v for more verbosity
                  -start with -d to run in foreground, and log to console instead of syslog
                  -inserted cards (in either available reader) start working right away
                  -all used config and key files are re-read on change, never need to restart CCcam

                  Comment

                  • aplok
                    Experienced Board Member
                    • Jun 2013
                    • 1155

                    Re: CCcam Frequently asked questions

                    hello

                    can somebody tell me what is the meaning of

                    11 (7)

                    in

                    | cccam.server.org:1234 | |CCcam-s2s|2.0.11 |abdeddddredddeded| 20 | local 1234:05678 11(7)

                    from

                    http://dbox:16001/servers

                    thx

                    Comment

                    • Satphoenix
                      Experienced Board Member
                      • Oct 2012
                      • 999

                      Re: CCcam Frequently asked questions

                      11 (7)

                      11 ecm requests sent, 7 answerd from server.

                      But no information, if answerd in time or to late so that you have glitches or freezes.
                      If you want to make God laugh, tell him your plans!

                      Comment

                      • kalpikos
                        Experienced Board Member
                        • Sep 2011
                        • 7663

                        Re: CCcam Frequently asked questions

                        Originally posted by aplok
                        hello

                        can somebody tell me what is the meaning of

                        11 (7)

                        in

                        | cccam.server.org:1234 | |CCcam-s2s|2.0.11 |abdeddddredddeded| 20 | local 1234:05678 11(7)

                        from

                        http://dbox:16001/servers

                        thx
                        Hello

                        As @Satphoenix said, you asked for 11 and took only 7.
                        It means that for some time your picture was freezed.
                        Also, it means that the server you use it's not the best
                        If You Like My Post..... Please Press the Thanks Button

                        Comment

                        • Satphoenix
                          Experienced Board Member
                          • Oct 2012
                          • 999

                          Re: CCcam Frequently asked questions

                          Originally posted by kalpikos
                          ...you asked for 11 and took only 7.
                          It means that for some time your picture was freezed.
                          Mostly yes, but not necessarily.
                          If an ecm is not answered fast enough but the server is still connected, cccam sends the ecm request a second time.
                          Especially overloaded servers or special cards in this server with heavy usage don't answer (fast enough) on a request so that sometimes a second request is necessary.
                          If you have alternative clines in your .cfg cccam often changes the server in that cases so fast, that you do not even notice this change - if the second line is good.

                          If you want to make God laugh, tell him your plans!

                          Comment

                          • kalpikos
                            Experienced Board Member
                            • Sep 2011
                            • 7663

                            Re: CCcam Frequently asked questions

                            I See your point and I agree with you, but I think that we should check the results only for a c-line each time.
                            Having only one c-line in cccam.cfg, you can say if that line is good or not.
                            Also we should never forget that the numbers don't lie.
                            If You Like My Post..... Please Press the Thanks Button

                            Comment

                            • sat-boy
                              Junior Member
                              • Jul 2014
                              • 11

                              Re: CCcam Frequently asked questions

                              Hi. I want to know how cccam work when you have 2-3-.... servers or different servers?!
                              I mean is it intermittent or it,s work with only one or with all servers!

                              Comment

                              • aplok
                                Experienced Board Member
                                • Jun 2013
                                • 1155

                                Re: CCcam Frequently asked questions

                                Originally posted by sat-boy
                                ... it,s work with only one or with all servers!
                                cccam starts connection with all the servers

                                then ranks the time responses

                                and chooses the fastest

                                ps: too many servers overload cccam, and deserves cccam

                                for more info, analyse log from cccam session in debug mode

                                enjoy

                                Comment

                                Working...