6 replies to this topic

[bairav19]

Hi guys,

 

 I`m new to VU+. Its working fine with my card sharing account..but the problem is how to use my  original card with internal cam(card reader) ?

Any assistant will be grateful as I also need to use the original subscription card with the unit.
 

CCcam 2.3.0 server web page outputs are:

 

Available providers:

+----+----------+--------------+------+
|Caid| Provider | Provider Name| System|
+----+----------+--------------+------+
| 649| |Unknown |irdeto|

 

card reader /dev/sci0
handled 2324(0) ecms and 3592(3592) emms

Irdeto card
Caid 649 ACS 1544 IND
Cardserial 4*********U9290000A (ed7356)
Provider 00 2a6985
Chid 0001 - date 0x161d valid 0x1e
Chid 007F - date 0x161d valid 0x1e
Chid 7FFE - date 0x161d valid 0x1e
Chid 7FFD - date 0x161d valid 0xa
Chid FFD8 - date 0x161d valid 0x1e

 

Thank You..

 

 

 

 

 

 

[eximio]

Hello.
Did you manage to solve the problem?

 

Can you share the solution?

 

thanks

[s3n0]

@eximio:

 

In my opinion, for these purposes it is better to use OScam instead of CCCam. In OScam, there are more options for using internal card readers + at the same time for connecting to a remote server. OScam is much modern than CCCam. Of course, you need to learn a little, because OScam is also more complex.

[Tech]

I wonder what is more complex, something that you can simply set up via a web interface or something where you have to adjust config files.

Putting in a little effort to get something to work isn't bad at all.

 

Apart from that, this topic is borderline, because there is also something mentioned about external sharing, the question is that the question concerns a local card, otherwise support would have ended by now!

[s3n0]

@Tech

 

In the English language, the term "complex" does not mean complicated !

 

It means that a specific thing has a really large number of options / settings / configuration functions / available algorithms / ... etc. . However, in such a case, it is necessary to always count on them. Everything is related to everything. Everything is interconnected.

 

In the case of OSCam, for example, if you set a group in the case of the oscam.server file, you must take into account that the group must then also be set for all available readers and proxies in this oscam.server file. And also in the case of oscam.user, it is necessary to add the determination of the group(s) under each user. There's a lot to it, unlike a regular CCcam. I personally use CCcam only as a softcam client (softcam CCcam v2.3.0). But I won't elaborate on that here. That's a completely different topic .

 

CCcam is much simpler... even primitive. Anyone who has been working with OSCam for a long time knows that literally everything can be set in OSCam. Not only does it support many communication softcam-protocols, but you can really set a lot of rules in it (options, functions, conditions, ... etc.). There are very few such configurable options in CCcam softcam.

Edited by s3n0, 5 March 2024 - 11:14.

[Tech]

What I was trying to say is that Oscam's web interface shows what you're doing, in other words, it could seem easier than editing a cccam configuration file, which is actually nothing if you're familiar with it

[s3n0]

Exactly so... in both cases (CCcam + OSCam) I only use configuration files and their manual editing, never Web-GUI .