oscam

**couchpotato** · 04-01-10, 05:10 PM

If you have yet to do so, give oscam a try

Best of all FBO channels will work 100% with the preview.

The config files can be a bit complicated at first, do a google and your sure to find a guide.

**poiuytrewq** · 04-01-10, 07:59 PM

Will it work as a client to other EMU's (eg. CCcam) or does it need to run as a server?

**couchpotato** · 04-01-10, 10:01 PM

I think it has client abilities but I could not make it work in that way, it seems to be setup for PC hardware. The dvb adapter is hardcoded at /dev/dvb/adapter0/ where the dreambox is /dev/dvb/card0/.

It can reshare, but that defeats the purpose. It can serve all major cs protocols. My main reason for using it was the FBO channels, as the package im on gives me 2 free fbo's a month and I was sick of missing the first 5-10 mins of the movie.

At home I have it on an X86 maching serving 2 dreamboxes with cccam as the client and 2 mythtv boxes running sasc-ng as the client.

A family member is running the server on a dm500, with 2 dm500's feeding off it with cccam as the client.

As no images seem to support it yet? I just have it start in /var/etc/init

**davo** · 06-01-10, 04:21 AM

I have been running mpcs/oscam for about 12 months and currently have mine set up on PLi Jade3, I created my own cam file and it starts and stops ok. it has for last so many images I have tested on my DM5620 & DM7000.

Do you have yours working on an NDS card? I am yet to test it on my NDS card I have it going on a 5.3 spoungebob sub card ok. I been too lazy LOL.

oscam is a server only up till recently, last week they have added 'camd' on the linux version making it similar to CCcam. The dreambox version may follow but its open src so anyone can add it if they want to. (landlord upped the mod few days ago) it may have been in for a few releases but i haven't noticed. This is only good for those currently with sat tuner cards in the box.

Davo

But yes its very stable and works quite well.

**couchpotato** · 10-01-10, 08:39 PM

Hi Davo,

Have it working on a blue NDS card. Since Ive had it running Ive noticed EMM's are not getting to the card properly, this is from Mgcamd and sasc-ng. CCcam doesnt even seem to send them.

Today I checked out SVN. Dreambox dvbapi support has been added so it can be used as a camd client now on dreambox. Works well and EMM's seem to be getting processed ok. If anyone does try it as a client then in the dvbapi and account section you need to put a password in, its missing from the examples and documentation.

Andrew

**Decapper** · 10-01-10, 09:18 PM

Here is a config stolen.. cred = adskiqt

For D+ (not fox)

oscam.server

Code:
[reader
]label = D+
protocol = internal
detect = CD
device = /dev/sci0
group = 1
emmcache = 1,3,2
mhz = 368
ReconnectTimeout = 20
DisableServerFilter = 1
n3_boxkey = xxxxxxx <- Insert your boxkey
n3_rsakey = xxxxxxxxx <- Insert your rsakey

oscam.conf

Code:
[global]
Nice = -1
LogFile = stdout
MaxLogSize = 102400
Sleep = 0
FallbackTimeout = 2
ClientTimeout = 5
ClientMaxIdle = 120
CacheDelay = 150
WaitForCards = 1
PreferLocalCards = 1

[newcamd]
key = 0102030405060708091011121314
port = 15000@1810:004001,004101,000000

oscam.user

Code:
[account]
user = user
pwd = pass
group = 1
uniq = 0
caid = 1810

in CCcam.cfg

Code:
N: 127.0.0.1 15000 user pass 01 02 03 04 05 06 07 08 09 10 11 12 13 14 256

**jgm** · 11-01-10, 03:29 PM

Hi couchpotato,

I have a few questions:
1. Which oscam version are you using?
2. Which CCcam version are you using?
3. Which image?

I'm getting the following in oscam.log:
2010/01/11 15

21 6563 c01 encrypted newcamd:15000-client xxx.xxx.xxx.xxx granted (USER, au=0)
2010/01/11 15

21 6563 c01 user USER authenticated successfully (using client 4343)
2010/01/11 15

21 6563 c01 AU disabled for user USER
2010/01/11 15

21 6563 c01 no valid CAID found in CAID for user 'USER'
2010/01/11 15

22 6563 c01 Connection closed to client
2010/01/11 15

22 6563 c01 USER disconnected from xxx.xxx.xxx.xxx

It looks like I'm close, but have something wrong in one of the configuration files.

BTW, my bluey looks like it is being read OK:
2010/01/11 15

11 6551 r02 ATR: 3F 7F 11 25 03 33 B0 09 69 FF 4A 50 70 00 00 46 44 01 00 00
2010/01/11 15

16 6551 r02 type: Videoguard, caid: 090B, serial: xxxxxxxx, BoxID: xxxxxxxx
2010/01/11 15

16 6551 r02 ready for requests
2010/01/11 15

16 6551 r02 card detected
2010/01/11 15

16 6551 r02 type: Videoguard

**Adobe** · 11-01-10, 04:03 PM

In the oscam.user file you have to change the CAID

**jgm** · 11-01-10, 05:08 PM

Originally Posted by Adobe

In the oscam.user file you have to change the CAID

CAID in user file is the same as that in the log ie 090B - should it be something else?

**couchpotato** · 11-01-10, 05:24 PM

Here is my working config

[ oscam.conf ]

[global]
nice = -1
WaitForCards = 1

#pidfile = /var/run/oscam.pid
#logfile = /var/log/oscam/oscam.log
#usrfile = /var/log/oscam/oscamuser.log
#cwlogdir = /var/log/oscam/cw
#showecmdw = 1

[monitor]
port = 988
aulow = 120
monlevel = 1
nocrypt = 127.0.0.1,192.168.0.0-192.168.0.255
monlevel = 4

[newcamd]
key = 0102030405060708091011121314
port = 10000@090B:000000

[radegast]
port = 10004
user = user1
allowed = 192.168.0.0-192.168.0.255

[ oscam.server ]

# serial reader

[reader]
label = reader1
protocol = mouse
detect = CD
device = /dev/ttyS0
group = 1
emmcache = 1,3,2
caid = 090b
cardmhz = 357
mhz = 600

[ oscam.user ]

[account]
user = root
pwd = dreambox
uniq = 0
monlevel = 1
group = 1
au = reader1
caid = 090b

[account]
user = user1
pwd = dreambox
uniq = 0
monlevel = 1
group = 1
au = reader1
caid = 090b

[account]
user = mythtv
pwd = mythtv
monlevel = 1
group = 1
au = reader1

[account]
user = dm500c
pwd = dm500c
monlevel = 1
group = 1
au = reader1
caid = 090b
ident = 090b:000000

[account]
user = monitor
pwd = monitor
monlevel = 2

And in CCcam config

N: 127.0.0.1 10000 dm500c dm500c 01 02 03 04 05 06 07 08 09 10 11 12 13 14

My server is on an X86 so for the reader section you will need for dreambox dm500

[reader]
label = reader1
protocol = internal
device = /dev/sci0
group = 1
emmcache = 1,3,2
caid = 090b

**jgm** · 11-01-10, 06:18 PM

I'm still missing something:

[global]
nice = -1
WaitForCards = 1

# logging

pidfile = /var/run/oscam.pid
logfile = /var/log/oscam.log
usrfile = /var/log/oscamuser.log
cwlogdir = /var/log/oscam/cw

# monitor

[monitor]
port = 988
aulow = 120
monlevel = 1
nocrypt = 127.0.0.1,192.168.1.0-192.168.1.255
monlevel = 4

# protocols

[newcamd]
key = 0102030405060708091011121314
port = 15000@090b:004001,004101,000000

[reader]
Label = Foxtel
Protocol = internal
Device = /dev/sci0
EMMCache = 1,3,2
Group = 1
CAID = 090b

[account]
User = USER
Pwd = PASS
monlevel = 1
Uniq = 0
Group = 1
AU = Foxtel
CAID = 090B

N: 192.168.1.228 15000 USER PASS 01 02 03 04 05 06 07 08 09 10 11 12 13 14

I'm still getting errors in the log. Using pli-jade, CCcam 2.1.3 & oscam-0.99.4svn1175

2010/01/11 17:59:09 30670 s client(1) connect from xxx.xxx.xxx.xxx (pid=30676, pipfd=15)
2010/01/11 17:59:09 30676 c01 encrypted newcamd:15000-client xxx.xxx.xxx.xxx granted (USER, au=foxtel)
2010/01/11 17:59:09 30676 c01 user USER authenticated successfully (using client 4343)
2010/01/11 17:59:09 30676 c01 AU flag 0 for USER
2010/01/11 17:59:10 30676 c01 USER (090B&004001/07D5/6F:72AC): rejected user ident (0 ms)

**davo** · 11-01-10, 09:10 PM

[newcamd]
key = 0102030405060708091011121314
port = 15000@090b:004001,004101,000000

should be

[newcamd]
key = 0102030405060708091011121314
port = 15000@090b:000000

also look at yout CAID one is in CAPS and one isnt maybe a factor.

ADD THIS under account

ident = 090b:000000 -- REPLACE the 000000 with your cards Provider ID or leave as 000000 if it works dont stuff with it but the correct format is CAID:ProviderID.

replace the 000000 with your cards Provider id & this also is used for the IDENT entry in other oscam files where applicable.

davo

PS

EMMCache = 1,3,2 - is telling it to try the emm 3 times should use 1,1,2 see attached..

emmcache = usecache,rewrite,logging
set EMM cache of local reader:
usecache = 0|1 1=enable EMM chaching, default:0
rewrite = determines how often one and the same EMM is written
logging = 0 = log errors only
1 = log all EMMs except the double EMMs
2 = log all EMMs

Dave

**jgm** · 11-01-10, 09:55 PM

OK thanks, will try these tomorrow. SWMBO is home, so I can't play with things tonight.

**jgm** · 12-01-10, 09:08 PM

Thanks to all. It's now working.

next issue: how do I check status of oscam - specifically how do I get it to show if EMMs are getting through? I've got monitor port set to 988, but I can't browse or telnet to it, & I haven't been able to find any doco in a language I can understand (ie English).

**mcjules** · 14-01-10, 08:29 AM

Originally Posted by couchpotato

Hi Davo,

Have it working on a blue NDS card. Since Ive had it running Ive noticed EMM's are not getting to the card properly, this is from Mgcamd and sasc-ng. CCcam doesnt even seem to send them.

Today I checked out SVN. Dreambox dvbapi support has been added so it can be used as a camd client now on dreambox. Works well and EMM's seem to be getting processed ok. If anyone does try it as a client then in the dvbapi and account section you need to put a password in, its missing from the examples and documentation.

Andrew

I gave the dvbapi support a go on my DM500 and i was getting picture (and sometimes sound) glitching every few seconds when oscam was processing ECMs. Where you running it on a DM500 and if so what svn revision are you using?

**couchpotato** · 14-01-10, 01:59 PM

As time goes by I notice more little issues which tells me its not ready for prime time on NDS cards. On the dreambox the card will only init every 2nd time so either need to restart server or pull card and reinsert. With the current svn NDS EMM's are not getting through to the card.
Now there is a patch available which adds processing support for NDS EMM's. When I use with mgcamd with this patch the card will lock up in an hour or so. Seems bad emm's are getting through to the card.

Now Ive found best setup is to run oscam on an x86 and use CCcam as a client. Looks like CCcam filters the EMM's better but you need "EXTRA EMM LEVEL : yes" in the CCcam config for them to work.

@jgm:
microMon can be used for monitoring, it was written for MPCS but works with oscam. I put a filter on the raw log for emm and watch that.

@mcjules:
I tried the dvbapi support on a dm500c, was very quick and it was as a client only, today I tried it as a client/server and yes its very rough.

I dont get a lot of time in a day to debug this properly so may unintentionally give bad info. Its hard to find time in the day when no one is watching TV so not to disturb them. I will order a fbo over the phone in the next few days and confirm EMM's are working properly with CCcam.

Andrew

**jgm** · 14-01-10, 04:55 PM

@couchpotato:
I can't drive microMon & can't find a howto - don't like Windoze stuff anyhow. I'll wait for your report on ordering fbo. I was reasonably happy with CCcam server except for the missing 10 minutes issue. At least now I can see the free parts of the movies.

@mcjules:
I've changed the CCcam config on the server to add "EXTRA EMM LEVEL : yes" and on the clients to add "DISABLE EMM : yes", and it seems to have got rid of the glitches (mine were happening at about 10 minute intervals) - CCcam 2.1.3 & oscam-0.99.4svn1175.

Now if only we could get the full f*xtel EPG.....

**mcjules** · 14-01-10, 08:27 PM

Originally Posted by couchpotato

I dont get a lot of time in a day to debug this properly so may unintentionally give bad info. Its hard to find time in the day when no one is watching TV so not to disturb them. I will order a fbo over the phone in the next few days and confirm EMM's are working properly with CCcam.

Andrew

It's all good. I just wanted to know if I was the only one having these issues. That mgcamd work is currently in active development so maybe once they've ironed out the bugs we might be in business.

**davo** · 14-01-10, 11:47 PM

micromon -

you need to include your ip range in the MONITOR area not just 127.0.0.1 eg..

[monitor]
port = 988
aulow = 120
monlevel = 3
NoCrypt = 127.0.0.1,10.1.1.2-10.1.1.100 <---- bold is the range of my local PC's

then works a treat.

BTW - oscam is developed from mpcs original source. I started using mpcs last year or the year before it was quite ok and that the src was around you could fix in your own small groups what you needed fixing.

**jgm** · 15-01-10, 04:57 PM

Originally Posted by davo

micromon -

you need to include your ip range in the MONITOR area not just 127.0.0.1 eg..

Did all that, but when I clicked the start button nothing happened - may be an issue with Windoze7. I'll try it on an XP box, but as I said before I'm not a fan of Windoze (or anything microsloth for that matter).