Project

General

Profile

Bug #1860

Encrypted Channels fail

Added by Markus Gonaus about 11 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Descrambling
Target version:
-
Start date:
2013-12-07
Due date:
% Done:

0%

Estimated time:
Found in version:
HTS Tvheadend 3.9.279~geb8c99b~precise
Affected Versions:

Description

Whenever I try to map an encrypted Channel, it fails.
Codeword Client is configured and green in tvheadend Web Interface.
But Oscam log shows not even a login.

It has worked and works with the 2.5 builds, but not with the 3.9 builds


2013-12-07 22:28:30.066 service_mapper: checking 602000/Syfy
2013-12-07 22:28:30.066 mpegts: 602000 - tuning on /dev/dvb/adapter1/frontend0
2013-12-07 22:28:30.066 subscription: "service_mapper" subscribing on "none", weight: 3, adapter: "/dev/dvb/adapter1/frontend0", network: "KTV-Kaufmann", mux: "602000", provider: "SKY", service: "Syfy"
2013-12-07 22:28:30.066 service_mapper: waiting for input
2013-12-07 22:28:32.008 subscription: "service_mapper" unsubscribing
comet failure [e=this.el.dom is undefined]
2013-12-07 22:28:32.127 service_mapper: 602000/Syfy: failed [err No descrambler]
2013-12-07 22:28:32.127 service_mapper: idle
2013-12-07 22:28:38.000 eit: grab started
2013-12-07 22:28:38.000 mpegts: 386000 - starting for 'epggrab' (weight 1)
2013-12-07 22:28:38.000 mpegts: 386000 - tuning on /dev/dvb/adapter1/frontend0
2013-12-07 22:28:38.000 subscription: 'epggrab' subscribing to mux, weight: 1, adapter: '/dev/dvb/adapter1/frontend0', network: 'KTV-Kaufmann', mux: '386000'
2013-12-07 22:28:48.119 eit: grab complete
2013-12-07 22:28:48.119 subscription: "epggrab" unsubscribing
2013-12-07 22:29:08.000 eit: grab started
2013-12-07 22:29:08.000 mpegts: 450000 - starting for 'epggrab' (weight 1)
2013-12-07 22:29:08.000 mpegts: 450000 - tuning on /dev/dvb/adapter1/frontend0
2013-12-07 22:29:08.000 subscription: 'epggrab' subscribing to mux, weight: 1, adapter: '/dev/dvb/adapter1/frontend0', network: 'KTV-Kaufmann', mux: '450000'
2013-12-07 22:29:18.115 eit: grab complete
2013-12-07 22:29:18.115 subscription: "epggrab" unsubscribing

History

#1

Updated by Pim Zandbergen about 11 years ago

I have been struggling as well with decryption with the post dvb rewrite builds.
Too bad I had to revert to builds predating the rewrite, because I loved what I saw.

Now I finally got it working, using the "simplified OSCam dvbapi protocol".
You need brand new tvheadend and oscam builds for that.
Also, you need to select the new oscam mode in the capmt configuration.

Thanks to all who made this working.

Pim

#2

Updated by Adam Sutton about 11 years ago

CWC should have been working fine. Capmt had a bug in it, I shuffled some code around right at the beginning of the rewrite and stupidly missed the fact I'd deleted an important line. This wasn't spotted until manio decided to update the code to add new oscam mode and realised what I'd done.

That being said, the version number reference in this issue has that fixed applied, so not sure what is going on.

Adam

#3

Updated by Adam Sutton almost 11 years ago

  • Status changed from New to Need feedback

Is this still happening? I've been unable to reproduce.

Adam

#4

Updated by Rob vh almost 11 years ago

I have been testing today (from the main branch), cannot get Canal Digitaal channels to play. I'm using the conventional oscam via capmt socket (with oscam mode selected). I did not refresh oscam. oscam sends code words back.

Jan 1 16:25:15 sat tvheadend5250: capmt: Starting capmt server for service "NED2" on tuner 0
Jan 1 16:25:15 sat tvheadend5250: subscription: "HTTP" subscribing on "NED2", weight: 100, adapter: "/dev/dvb/adapter0/frontend0", network: "19.2E", mux: "125
15H", provider: "CANALDIGITAAL", service: "NED2"
Jan 1 16:25:35 sat tvheadend5250: webui: Stop streaming /stream/channel/83fcac0111fc0916e140bca8cfa99f44, timeout waiting for packets
Jan 1 16:25:36 sat tvheadend5250: subscription: "HTTP" unsubscribing from "NED2"
Jan 1 16:25:36 sat tvheadend5250: capmt: Removing CAPMT Server from service
Jan 1 16:25:36 sat tvheadend5250: htsp: Got connection from 10.29.1.39
Jan 1 16:25:36 sat tvheadend5250: htsp: 10.29.1.39: Disconnected
Jan 1 16:25:36 sat tvheadend5250: mpegts: 12515H - tuning on /dev/dvb/adapter0/frontend0
Jan 1 16:25:38 sat tvheadend5250: capmt: Starting capmt server for service "NED2" on tuner 0
Jan 1 16:25:38 sat tvheadend5250: subscription: "HTTP" subscribing on "NED2", weight: 100, adapter: "/dev/dvb/adapter0/frontend0", network: "19.2E", mux: "12515H", provider: "CANALDIGITAAL", service: "NED2"
Jan 1 16:25:38 sat tvheadend5250: htsp: Got connection from 10.29.1.39
Jan 1 16:25:38 sat tvheadend5250: htsp: 10.29.1.39: Disconnected
Jan 1 16:25:58 sat tvheadend5250: webui: Stop streaming /stream/channel/83fcac0111fc0916e140bca8cfa99f44, timeout waiting for packets
Jan 1 16:25:59 sat tvheadend5250: subscription: "HTTP" unsubscribing from "NED2"
Jan 1 16:25:59 sat tvheadend5250: capmt: Removing CAPMT Server from service

#5

Updated by A. S. over 10 years ago

The same error still happens on the newest master branch version while adding scrambled channels!

comet failure [e=this.el.dom is undefined]

#6

Updated by A. S. over 10 years ago

sorry While mapping scrambled channels, all of them ignored and didn't added

#7

Updated by Meindert Oldenburger over 10 years ago

I have no problems with encrypted channels from CanalDigitaal. I'm using Capmt in TVHeadend (3.9 (latest)) and OSCam as camserver. It was not easy to configure I remember, but now it working all the time.

#8

Updated by Rob vh over 10 years ago

I agree, 3.9.509 works fine in combination with oscam (I use mode=2 on the capmt tab).

#9

Updated by Adam Sutton over 10 years ago

  • Status changed from Need feedback to Rejected

I simply cannot reproduce this, I've used by CWC and CAPMT without issue for a long time on master.

Adam

#10

Updated by Markus Gonaus over 10 years ago

After a couple of months I tried it again. But this time I deleted the whole configration and startet from scratch. And now it perfectly works.

So it seems as there was some problem in the upgrade process from Versions from before December.

Everyone who is affacted by this, simply delete your whole configuration and start ist from scratch.
Thanks to Mr. Sutton for taking this seriosly although I was not able to provide usefull information in time.

Also available in: Atom PDF