After plenty of testing, many different configurations on a couple of OSs [original FW and E2] and a couple of original FWs [4890 and 5303], as well as a couple of E2 [RC4 and RC7]...
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... But I will attach it in this thread, if I can!
FTP to AZbug HD [use the freeware FileZilla Client] and go to PLUGINS folder, then OpenXCAS and create a folder oscamCAS, then give it CHMOD to 755 [right click on the file -> File permissions -> 755 -> OK].
On your PC you can create various files, using a freeware application Notepad++, which you will FTP to oscamCAS folder. All except oscam module itself, which you get from the net, as mentioned and then give CHMOD to 755, as above. If it is named differently -> right click on it -> rename it to oscam and hit Enter on your keyboard.
So, here are the four main configuration files [do not deviate from them, for starters... later, try different ones...] - thanx primarily to B@mbi but also hperez, gianni, subnixonfire, Siri, belami etc. etc.:
You will need to forward the ports here defined, in your modem/router. "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.
All the following ones are external [readers]. They are also servers but they are the servers of your peers, to which you hook onto, as a client. I.e. their readers read their cards, not just for themselves, but for you, too.
Hence all are simply "readers", whether local [yours] or remote [virtual, via internet].
The details marked xxxxxx in those you get from your colleagues/peers, like username, password, port and dyndns domain name. Those are necessary to be able to hook onto their servers.
As a client in CCcam protocol one does not need to open various ports, Only servers [your colleagues/"peers" giving you access to their cards] need to do that.
For 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. If you have many C lines you can sub-divide them further, to make it all better optimised/efficient. We shall come to that later.
Externally speaking: partially, you allow your peers access to your server right here, by setting up their username and password. The other parts to allow them access to your server, with which you create C (for your CCcam clients) or N (for your Newcamd clients) lines for your peers/colleagues, are from oscam.conf file, which we will discuss a little bit later, in the P.P.S.
You can divide the [readers] and [accounts] into groups.
For instance, your own internal server [the first "reader"] is in group 1.
All the other "readers", are in group 2.
The very first "account", i.e. "user" has to be in both groups 1 and 2, to hook both onto your own server/reader, as well as your colleague's readers/servers. So, this first user [which is yourself] must hook onto both your internal reader/server [group 1], as well as external readers [group 2].
The other users/accounts are, in my case, Newcamd protocol clients of mine [me being a server, in this case, passing my smartcard to them], i.e. they are getting access solely to my smartcard [internal] reader/server by being placed in Group 1. That way they will not draw from anything but my smartcard/reader.
Apparently, Newcamd server is meant for this purpose, so this is how it is supposed to be used. The N-lines you [partially] create from this file [oscam.user] and [partially] from Newcamd part of oscam.conf file, are to be given to your colleagues, people you trust. With those lines you pass only your card and nothing else and this is how it is done. These [users] are connected to my internal reader/server via Group 1 and thereby not connected to the CCcam protocol, which busy traffic is placed in Group 2.
This is enough for you to be both a [Newcamd protocol] server, as well as [mainly CCcam] client. You give your card[s] in return for other people's cards. No need to pay for "CS services", run by our little CS entrepreneurs, spoiling the fun for us!!!
I will attach the rest of the files here, including the module itself, so you don't have to search for it too much...