as you configure the key biss with oscam?

Tigertim

Registered
Messages
75
There have been changes to oscam-emu's handling of BISS since this thread came to a stop in April '17. See https://github.com/oscam-emu/oscam-emu/wiki/BISS-config

While that old method is still supported, SoftCam.Key is recommended over constant.cw now.

So now if adding a new biss code you just open Softcam with notepad, insert the 2 biss lines like ?

F 26001FFF 00 72 92 91 95 12 AA AA 66
F 26001FFF 01 72 92 91 95 12 AA AA 66

and the send by ftp to etc/tuxbox/config or usr/keys ?
i'am using openvix image.
 
C

campag5242

I've no idea about the location of your SoftCam.Key on openvix.

As an alternative, you can edit the file from the webif's Files tab, Other Files... should be the last entry there in the drop-down menu.

You'll see several templates in the live log for the format of the line when you tune in a new feed, both SID:pID & hash-based variants.

The key is always entered *without* spaces, either 16 characters DVB-CSA or 12 characters BISS-SW (no checksums).

And only one line is needed, the second F XXXXXXXX 01 ... is redundant.

And when you've added the key, click on the emu-reader's "refresh-entitlements" icon to have the emu re-read the key file.
 
Last edited:

Tigertim

Registered
Messages
75
I've no idea about the location of your SoftCam.Key on openvix.

As an alternative, you can edit the file from the webif's Files tab, Other Files... should be the last entry there in the drop-down menu.

You'll see several templates in the live log for the format of the line when you tune in a new feed, both SID:pID & hash-based variants.

The key is always entered *without* spaces, either 16 characters DVB-CSA or 12 characters BISS-SW (no checksums).

And only one line is needed, the second F XXXXXXXX 01 ... is redundant.

And when you've added the key, click on the emu-reader's "refresh-entitlements" icon to have the emu re-read the key file.

Not had a try with webif yet, only had the box a few days, will try opening that tomorrow.
The lives logs are seen in webif or on my box under softcam manager.....reading that link it's the different hash variants i need to find when editing my biss line.
It's sports feeds iam looking to add.
 
C

campag5242

It's the Live Log as seen on a PC in your local network: http://ip.of.your.box:83 (or instead of 83 try 8888, or whatever it's set to in the .conf file). You'll need the user/pw pair if set in the .conf file too.
 
C

campag5242

No problem, there's a fair bit to learn initially, but stick with it, it'll be worth the effort.
 

Tigertim

Registered
Messages
75
I've no idea about the location of your SoftCam.Key on openvix.

As an alternative, you can edit the file from the webif's Files tab, Other Files... should be the last entry there in the drop-down menu.

You'll see several templates in the live log for the format of the line when you tune in a new feed, both SID:pID & hash-based variants.

The key is always entered *without* spaces, either 16 characters DVB-CSA or 12 characters BISS-SW (no checksums).

And only one line is needed, the second F XXXXXXXX 01 ... is redundant.

And when you've added the key, click on the emu-reader's "refresh-entitlements" icon to have the emu re-read the key file.

ok being trying the tennis feed on 7e...the Pco Hd one
http://www.sat-universe.com/showthread.php?t=252812&page=542

on my live log i get
2018/05/28 11:46:22 5FD3C528 c (dvbapi) Demuxer 0 ecmpid 0 CAID: 2600 ECM_PID: 1FFF PROVID: 000000

and

2018/05/28 11:46:22 5FD3C528 c (dvbapi) Demuxer 0 trying to descramble PID 0 CAID 2600 PROVID 000000 ECMPID 1FFF ANY CHID PMTPID 0102 VPID 0200

i entered F 26001FFF 00 ACCD45BE56CB3253 into softcam but no luck.

With the details i've given how would you write the line in softcam on webif please ?
 
C

campag5242

You should look lower down in the live log... if your oscam-emu is up to date, you'll see lines of the form:
Code:
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 1B26EF27
2018/05/28 12:51:08 2BD25401 r      (emu) Example key based on namespace hash: F 1B26EF27 18052816 XXXXXXXXXXXXXXXX ;   7.0E 11082H sid:0001 added: 2018-05-28 @ 12:51
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F A6A4FBD4
2018/05/28 12:51:08 2BD25401 r      (emu) Example key based on universal hash: F A6A4FBD4 18052816 XXXXXXXXXXXXXXXX ; av:3 pmt:0800 sid:0001 added: 2018-05-28 @ 12:51
2018/05/28 12:51:08 2BD25401 r      (emu) Feed has commonly used pids, universal hash clashes in SoftCam.Key are likely!
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00011020
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00011010
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00010200
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00010800
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00011FFF
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F A11FEED5
2018/05/28 12:51:08 2BD25401 r      (emu) ECM failed: Key not found

(That's not the tennis, it's CHEVC2 at 7E 11082H 9875 right now.)

All of those F XXXXXXXX lines are lines the emu has looked for in the keyfile, so any of those will work. The best one is the first listed/searched for (namespace), as that is the one which best/uniquely identifies the feed. For both namespace & universal hashes, you'll even see a complete template line but with key replaced by X's.
 

Tigertim

Registered
Messages
75
You should look lower down in the live log... if your oscam-emu is up to date, you'll see lines of the form:
Code:
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 1B26EF27
2018/05/28 12:51:08 2BD25401 r      (emu) Example key based on namespace hash: F 1B26EF27 18052816 XXXXXXXXXXXXXXXX ;   7.0E 11082H sid:0001 added: 2018-05-28 @ 12:51
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F A6A4FBD4
2018/05/28 12:51:08 2BD25401 r      (emu) Example key based on universal hash: F A6A4FBD4 18052816 XXXXXXXXXXXXXXXX ; av:3 pmt:0800 sid:0001 added: 2018-05-28 @ 12:51
2018/05/28 12:51:08 2BD25401 r      (emu) Feed has commonly used pids, universal hash clashes in SoftCam.Key are likely!
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00011020
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00011010
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00010200
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00010800
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F 00011FFF
2018/05/28 12:51:08 2BD25401 r      (emu) Key not found: F A11FEED5
2018/05/28 12:51:08 2BD25401 r      (emu) ECM failed: Key not found

(That's not the tennis, it's CHEVC2 at 7E 11082H 9875 right now.)

All of those F XXXXXXXX lines are lines the emu has looked for in the keyfile, so any of those will work. The best one is the first listed/searched for (namespace), as that is the one which best/uniquely identifies the feed. For both namespace & universal hashes, you'll even see a complete template line but with key replaced by X's.

Tuned into Chevc2 feed....my livelog looks nothing like yours....i get no sid or hash details, as i mentioned box is only a few days old..i downloaded oscam emu off openvix image

scrolling through my boxes setting whilst trying to find which version of oscam emu i had i've found under
Menu..Information...Service all the chevc2 channel info
such as
Namespace 00462B4A
Service Id 0001(1)
Video pid 0020(512)
Audio pid 1010(412)
Pcr pid 0200(512)
Pmt pid 0800(2048)
txt pid N/A
Tsid 4321(17185)
Onid 00EB (235)

would that information be enough to get what you need for biss line....on my webif sid and hash values arnt coming up....which is latest version i should be using please ?
 
C

campag5242

Do you have plain oscam installed, or oscam-emu? If you have both, ensure you have the emu version as the active cam.
 
Last edited:
C

campag5242

Have you enabled the emu reader? On the webif "Readers" section you may need to enable/start it.
 
C

campag5242

Things to check:
1. Is the emu reader configured with 2600 as one of its supported caids? You should see 2600 amongst a handful of others, separated by commas, on the emu edit reader page.
2. Check the emu version - on the entitlements page, click on "Serial" to reveal the emu build version.
 

Tigertim

Registered
Messages
75
Things to check:
1. Is the emu reader configured with 2600 as one of its supported caids? You should see 2600 amongst a handful of others, separated by commas, on the emu edit reader page.
2. Check the emu version - on the entitlements page, click on "Serial" to reveal the emu build version.

quite a lot of 2600 caids listed
oscam 1.20 unstable build 11398

newer oscam or webif version newer so i can see sids and hashes ?
 

Tigertim

Registered
Messages
75
Just opened the tennis feed...picture breaking up badly though
i put in F 00011FFF 00 ACCD34AD56CB3253 (7.0°E)
F 00011FFF 01 ACCD34AD56CB3253 (7.0°E)

i sent an edited softcam key over ftp to both /usr/keys and /etc/tuxbox/config....not sure which one worked tbh...that's for a later time...will try one of the football feeds next.
Having biss is important as that's one of the joys of satellite viewing getting sports/boxing ppv events, thank you for helping.
 
C

campag5242

quite a lot of 2600 caids listed
I suspect here you are reporting the entitlements, not the caids in reader's edit/config page. But since your subsequent post says you had success (albeit on a weak signal) I assume that part is OK.

oscam 1.20 unstable build 11398
That's the oscam version number, unrelated to the emu version. The emu version can be seen either *very* early in the Live Log after restarting oscam, or more easily on the emu reader's entitlements page as I outlined: click on "Show" beneath the "Serial" label to reveal the emu version.

That F line you've entered is fine for one feed, but if you want to zap between feeds you'll have problems - sid 0001 & ecmpid 1FFF is common to many many feeds. That's where the latest emu version helps, enhanced with namespace / pid hashes. And as I said before, that second line with 01 in place of 0 is redundant, not needed, and simply ignored on the last BISS emu revision.
 

Tigertim

Registered
Messages
75
I suspect here you are reporting the entitlements, not the caids in reader's edit/config page. But since your subsequent post says you had success (albeit on a weak signal) I assume that part is OK.

That's the oscam version number, unrelated to the emu version. The emu version can be seen either *very* early in the Live Log after restarting oscam, or more easily on the emu reader's entitlements page as I outlined: click on "Show" beneath the "Serial" label to reveal the emu version.

That F line you've entered is fine for one feed, but if you want to zap between feeds you'll have problems - sid 0001 & ecmpid 1FFF is common to many many feeds. That's where the latest emu version helps, enhanced with namespace / pid hashes. And as I said before, that second line with 01 in place of 0 is redundant, not needed, and simply ignored on the last BISS emu revision.

OSCam-Emu version 766

whats the latest version please ?
 
Top