#CCCAM CONFIG PC#

Each 'user' in your file has an 'account' with the server. user because in it you are setting various 'users' or 'clients' to your 'server'. If you have many C lines you can sub-divide them further, to make it all better optimised/efficient. Those are necessary to be able to hook onto their servers.Īs a client in CCcam protocol one does not need to open various ports, Only servers need to do that.įor now, let's just say that your embedded cardreader/internal reader/server should be in Group 1, whereas your CCcam peers should be in Group 2. The details marked xxxxxx in those you get from your colleagues/peers, like username, password, port and dyndns domain name. Hence all are simply 'readers', whether local or remote. their readers read their cards, not just for themselves, but for you, too. They are also servers but they are the servers of your peers, to which you hook onto, as a client. (.plus as many servers of your colleagues as you have, like the second example above.)Ī note, to explain the name of the file: the first is your reader, the 'server' primarily for yourself, to which the OSCam client part hooks onto, internally, to open the channels.Īll the following ones are external. 'Forwarding ports' means to open those ports up to your AZbug HD, so when your peers try to get to you the traffic will not be blocked and it will automatically be directed to AZbox HD, instead of any other device you have hooked onto your home network, via the same modem/router. You will need to forward the ports here defined, in your modem/router. ergo xxxxxx = whatever you desire or whatever the CAID of your smartcard. Note: xxxxxx = this you choose, whatever it is. # nf generated automatically by Streamboard OSCAM 1.00-unstable_svn build #4859 So, here are the four main configuration files - thanx primarily to but also hperez, gianni, subnixonfire, Siri, belami etc. If it is named differently -> right click on it -> rename it to oscam and hit Enter on your keyboard. All except oscam module itself, which you get from the net, as mentioned and then give CHMOD to 755, as above.

#CCCAM CONFIG PC#

On your PC you can create various files, using a freeware application Notepad++, which you will FTP to oscamCAS folder. But I will attach it in this thread, if I can!įTP to AZbug HD and go to PLUGINS folder, then OpenXCAS and create a folder oscamCAS, then give it CHMOD to 755. The version of OSCam I am using, fairly successfully, with all the stops, bumps, reboots and so on, is 4859, with dvbapii!!! You can find it on OSCam forum, in AZbox HD section, the 'sticky' thread with bin files. OK, this works - tested with my Conax CD card CAS5!!! - both as a card reader/server, as well as a client, so no need for any other Emus, thanx to various people for sharing info, like I am trying to do now.Īfter plenty of testing, many different configurations on a couple of OSs and a couple of original FWs, as well as a couple of E2. Don't write your completely different problem in someone else's TOPIC. Who is your provider, what encoding is used by your card, what CAID and possibly PROVID is used, etc.īTW, please set up a new and your own TOPIC for the future. You want to help with the setup, but did not write any details. You need to write more details about your problem.

What exactly is meant by this - 'everything just stops working with oscam' ? Oscam stop working ? Why ? Under what circumstances ? What exactly stops (oscam service, decoding ECMs, freezes Oscam, do you see any 'oscam stopped' message in LiveLog via OscamWebif) ? Or what exactly ? Maybe I have made some wrong settings in rver file? or what could be wrong? Anyone else got the issue with oscam But without making any changes in settings nothing works. I have heard restart cam will make it work, sometimes you have to restart it several times.

What can be the problem if everything just stops working with oscam? No problem with server.

Cccam config