Support Digital Devices CI Interfaces

Added by Jasmin Jessich about 1 year ago

Hello TVH and DD CI users!

I have implemented the support for the Digital Devices CI interfaces (see also https://tvheadend.org/issues/4477). Currently only one service can use the dedicated CI at a time. There is no MCD (Multi Channel Decoding) or MTD (Multi Tuner Decoding) implemented.

It is 95% working, but sometimes the CAM doesn't decrypt. This is no problem of the new code, but of the PID selection for CAMs in TVH general, I guess. I tried to find the reason, but TVH is too complicated in this area and I am not willing to spend hours and hours to analyse this part of TVH. The DD CI code is 100% finished and works, if the PIDs are set properly by TVH. This has been already tested by me and another TVH user.

I also asked Jaroslav for support, but he has currently no time, so I stopped the project at this stage. As long as I don't get more support, I am not willing to continue working on this! I am not using TVH at all and did this only, because a friend asked me to do this. Without proper support form any TVH developer the last 5% can't be implemented.

You can find the code at GitHub on the ddci branch:

https://github.com/jasmin-j/tvheadend/tree/ddci

I will not submit a pull request, because it is not 100% working. Once the last 5% are done, it can be integrated to TVH.

Have fun and BR,
Jasmin


Replies (42)

RE: Support Digital Devices CI Interfaces - Added by Mark Clarkstone about 1 year ago

Jasmin Jessich wrote:

.. snip ..
I will not submit a pull request, because it is not 100% working. Once the last 5% are done, it can be integrated to TVH.

Don't worry about that - open a PR anyway so people can discuss your changes on github :).

Have fun and BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich about 1 year ago

Mark Clarkstone wrote:

Don't worry about that - open a PR anyway so people can discuss your changes on github :).

I crated pull request 1031 (https://github.com/tvheadend/tvheadend/pull/1031).
It is open for comments now.
I created a new branch (ddci_phase1) for the review, so that the comments will keep after incorporating them into the main development branch (ddci) and squashing them.

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by sharky :-) 12 months ago

You merged branch to the master right ? Now it should possible to test my interface right ?

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 12 months ago

Yes, it should be all an master and work as expected for Phase 1.
Phase 1 means only ONE service can use the DD CI CAM.

Phase 2 is Multi Channel Decoding (MCD) where several services of the same mux can use the DD CI CAM.
I am not sure if I can implement Phase 2 before my vacation (15.12.2017..3.2.2018), but I will try.

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by sharky :-) 12 months ago

Hey Jasmin ,
I could compile the latest git. Tvh starts successfully .

CAM Module and Cine S6.5 are visible under tv adapters. yay
CAM Module recognized that I have pluged in a alphacrypt module ( module is green / ready state )
Enter my PIN and saved the configuration.

Tuning to a non decrypted channel works out of the box. *Yippie'

Tuning to a decrypted channel does not work. Do I have to assign anything ?

The following debug ist generated.

2017-11-29 00:15:56.849 mpegts: 10817.5V in DVB-S Network - tuning on STV090x Multistandard #0 : DVB-S #0
2017-11-29 00:15:57.368 subscription: 000F: "HTTP" subscribing to service "DVB-S Network/10817.5V/FOX HD", weight: 100, adapter: "STV090x Multistandard #0 : DVB-S #0", network: "DVB-S Network", mux: "10817.5V", provider: "DIGITAL+", profile="pass", hostname="192.168.10.33", client="VLC/2.2.6 LibVLC/2.2.6"
2017-11-29 00:15:59.334 subscription: 000F: service instance is bad, reason: No descrambler

Do I have to link the cam and the tuner or does it happen automatically ?

Thanks !

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 12 months ago

I could compile the latest git.

Did you compile with "./configure --enable-ddci" ?

You need to see in the configure output:
libdvben50221 yes
ddci yes

Tuning to a decrypted channel does not work. Do I have to assign anything ?

No, all is done automatically.

The following debug is generated.

This log says nothing!
You need to start TVH with:
./build.linux/tvheadend -l tvh.log --trace linuxdvb,ddci,en50221,dvbcam

The trace outout in tvh.log is the thing I need.
Then I can tell you more, but first be sure ddci is enabled in the configuration.

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by sharky :-) 12 months ago

Thank you, I think it was to late :-)

Just for documentation.

AUTOBUILD_CONFIGURE_EXTRA=--enable-ddci ./Autobuild.sh -j4

Decrypting is working !

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 12 months ago

sharky :-) wrote:

Decrypting is working !

Nothing else I would have expected :D

RE: Support Digital Devices CI Interfaces - Added by saen acro 12 months ago

sharky :-) wrote:

Just for documentation.

AUTOBUILD_CONFIGURE_EXTRA=--enable-ddci ./Autobuild.sh -j4

to be more correct

AUTOBUILD_CONFIGURE_EXTRA=--enable-ddci ./Autobuild.sh -j$(nproc)

/I have 16 cores ;) /

RE: Support Digital Devices CI Interfaces - Added by Daniel Scheller 12 months ago

FYI (for anyone using Gentoo):

https://github.com/gentoo/gentoo/pull/6399

(and, semi-related: https://github.com/gentoo/gentoo/pull/6401 - might come in handy for anyone wanting to test patches).

RE: Support Digital Devices CI Interfaces - Added by Alexander P 11 months ago

Thx to Jasmin to implement this feature in in TVH!

It works almost perfect, but maybe I found a bug in the current implementation.

In my setup I have two smartcards for decrypting my channels. One card can only be used in an AlphaCryptLight Module and the other one is handled by OSCAM. With the most recent version of the code, I'm now able to use the ACL in the DDCI. But after I inserted the ACL module, only ACL related channels are decrypted, but no channels, which should be handled by OSCAM... When I disconnect the ACL Module, OSCAM channels are decrypted as usual.

It seems, that for now it is not possible to have both ways of decrypting channels at the same time. Can someone confirm that?

RE: Support Digital Devices CI Interfaces - Added by saen acro 11 months ago

CAID filter list used?

RE: Support Digital Devices CI Interfaces - Added by Alexander P 11 months ago

Yes, tried it... same results...

Maybe the problem is, that the channels I want to descramble with OSCAM are also using the same CAID, which is handled by the card in my ACL...
(For german users: ACL with Sky V14, CAID 098C; OSCAM with HD+ HD01, CAID 1830)

RE: Support Digital Devices CI Interfaces - Added by saen acro 11 months ago

HD+ 1843 and 1860 work Perfect ;)
experiment with CAID selection

RE: Support Digital Devices CI Interfaces - Added by Alexander P 11 months ago

First Hit, Last Hit and All CAIDs...
No difference

CAID filter list: 098C

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 11 months ago

Alexander P wrote:

Thx to Jasmin to implement this feature in in TVH!

And also THX to Jaroslav for rewriting big parts of the dvbcam code to allow reusing it for DD CI!

If the problem still persists after you playing with the CAIDs, please activate the trace mode with "dvbcam" enabled and look if you find "first CAID XXXX selected" or "add CAID XXXX to selection" or "last CAID XXXX selected" when you tune.

When the text is printed, the DVB CAM (DD CI) is used for the service. If not, the service should be decoded by your OsCAM device. If it is not printed and the service is not decoded by OsCAM, we need to debug this further. But then it is a general problem and not located in the DD CI extensions.

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by Alexander P 11 months ago

I did some trial and error using the trace messages...

Switching between the different options in "CAID selection" seems only to have an effect to the the trace log message (first/last/add).

When my ACL module is not connected, there is no message like "first/last/add CAID 098C selected/to selection" and all HD+ channels are decrypted perfectly (with OSCam).

2017-12-29 17:48:47.082 [   INFO]:subscription: 0034: "192.168.0.31 [ kodi | Kodi Media Center ]" unsubscribing from "ProSieben HD", hostname="192.168.0.31", username="kodi", client="Kodi Media Center" 
2017-12-29 17:48:47.085 [   INFO]:mpegts: 11464.25H in Astra 19.2E - tuning on STV090x Multistandard : DVB-S #0
2017-12-29 17:48:47.338 [  TRACE]:dvbcam: start service 0x5594cd087c80
2017-12-29 17:48:47.338 [   INFO]:subscription: 0038: "192.168.0.31 [ kodi | Kodi Media Center ]" subscribing on channel "SAT.1 HD", weight: 150, adapter: "STV090x Multistandard : DVB-S #0", network: "Astra 19.2E", mux: "11464.25H", provider: "ProSiebenSat.1", service: "SAT.1 HD", profile="htsp", hostname="192.168.0.31", username="kodi", client="Kodi Media Center" 
2017-12-29 17:48:47.860 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/SAT.1 HD: cannot find active service entry
2017-12-29 17:48:47.861 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/SAT.1 HD: cannot find active service entry
2017-12-29 17:48:47.861 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/sixx HD Austria: cannot find active service entry
2017-12-29 17:48:47.861 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD Austria: cannot find active service entry
2017-12-29 17:48:47.931 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD Austria: cannot find active service entry
2017-12-29 17:48:48.004 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/ProSieben HD: cannot find active service entry
2017-12-29 17:48:48.074 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD: cannot find active service entry
2017-12-29 17:48:48.217 [WARNING]:TS: Astra 19.2E/11464.25H/SAT.1 HD: TELETEXT @ #32 Continuity counter error (total 1)
2017-12-29 17:48:48.244 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD: cannot find active service entry
2017-12-29 17:48:48.244 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/SIXX HD: cannot find active service entry
2017-12-29 17:48:59.493 [   INFO]:mpegts: 11464.25H in Astra 19.2E scan complete

After connecting my ACL module, the HD+ channel, that I've subscribed before is still decrypted via OSCam. But when I switch to a HD+ channel I get errors...

2017-12-29 17:52:25.441 [ NOTICE]:linuxdvb: dvbca0-0: CAM slot 0 status changed to module init
2017-12-29 17:52:26.238 [ NOTICE]:linuxdvb: dvbca0-0: CAM slot 0 status changed to module connected
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [  TRACE]:dvbcam: register cam 0x5594ce018280 caids_count 18
2017-12-29 17:52:27.738 [ NOTICE]:linuxdvb: dvbca0-0: CAM slot 0 status changed to module ready
2017-12-29 17:52:28.538 [   INFO]:en50221: dvbca0-slot0-app00020041/0004: CAM INFO: AlphaCrypt, 01, 4A20, 4A22
2017-12-29 17:53:06.986 [   INFO]:subscription: 003B: "192.168.0.31 [ kodi | Kodi Media Center ]" unsubscribing from "ProSieben HD", hostname="192.168.0.31", username="kodi", client="Kodi Media Center" 
2017-12-29 17:53:06.992 [   INFO]:mpegts: 11464.25H in Astra 19.2E - tuning on STV090x Multistandard : DVB-S #0
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: start service 0x5594cd087c80
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: dvbca0-0/0x5594cd087c80: match CAID 098C PID 6890 (1AEA)
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: dvbca0-0/0x5594cd087c80: add CAID 098C to selection
2017-12-29 17:53:07.255 [ NOTICE]:ddci: CAM ci0 assigned to 0x5594cd087c80
2017-12-29 17:53:07.255 [  TRACE]:dvbcam: dvbca0-0/0x5594cd087c80: add ECM PID 6890 (1AEA) for CAID 098C
2017-12-29 17:53:07.255 [   INFO]:subscription: 003D: "192.168.0.31 [ kodi | Kodi Media Center ]" subscribing on channel "SAT.1 HD", weight: 150, adapter: "STV090x Multistandard : DVB-S #0", network: "Astra 19.2E", mux: "11464.25H", provider: "ProSiebenSat.1", service: "SAT.1 HD", profile="htsp", hostname="192.168.0.31", username="kodi", client="Kodi Media Center" 
2017-12-29 17:53:07.664 [  TRACE]:dvbcam: 0x5594cd087c80: add EMM PID 4104 (1008) for CAID 098C
2017-12-29 17:53:07.737 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/ProSieben HD: cannot find active service entry
2017-12-29 17:53:07.783 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD Austria: cannot find active service entry
2017-12-29 17:53:07.807 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/sixx HD Austria: cannot find active service entry
2017-12-29 17:53:07.807 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD Austria: cannot find active service entry
2017-12-29 17:53:07.808 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/kabel eins HD: cannot find active service entry
2017-12-29 17:53:07.953 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/Pro7 MAXX HD: cannot find active service entry
2017-12-29 17:53:07.954 [  TRACE]:dvbcam: Astra 19.2E/11464.25H/SIXX HD: cannot find active service entry
2017-12-29 17:53:09.162 [   INFO]:en50221: dvbca0-0: ops menu: {"selectable":true}
2017-12-29 17:53:17.162 [WARNING]:subscription: 003D: service instance is bad, reason: No input detected
2017-12-29 17:53:17.164 [ NOTICE]:ddci: CAM ci0 unassigned from 0x5594cd087c80
2017-12-29 17:53:19.163 [ NOTICE]:subscription: 003D: No input source available for subscription "192.168.0.31 [ kodi | Kodi Media Center ]" to channel "SAT.1 HD" 
2017-12-29 17:53:21.163 [ NOTICE]:subscription: 003D: No input source available for subscription "192.168.0.31 [ kodi | Kodi Media Center ]" to channel "SAT.1 HD" 

It looks like DDCI itself is working pretty well, but the "decision" in TVH when to use what for decrypting has some issues...

RE: Support Digital Devices CI Interfaces - Added by saen acro 11 months ago

maby load-balance with active fail-back is needed ;)
CI = hop 0
Softcam = hop 1

of course this is code must be before before ddci and softcam

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 11 months ago

2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS) 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [   INFO]:en50221: dvbca0-slot0-app00030041/0002: CAM supported CAIDs: 098C (NDS) 098C (NDS)
2017-12-29 17:52:27.538 [  TRACE]:dvbcam: register cam 0x5594ce018280 caids_count 18

This looks strange to me. The CAM reports 18 CAIDs, but there is always the same printed. I guess Jaroslav needs to look at this. He recently added the en50221 handling to TVH and I guess there is something not correct, at least with the printing.

I am missing the DD CI traces. Please trace with these trace settings: "linuxdvb,ddci,en50221,dvbcam". This will log much more, so maybe you should write it to a logfile. This is how I start for debugging:

./build.linux/tvheadend -l tvh.log --trace linuxdvb,ddci,en50221,dvbcam

The result is then in the file "tvh.log" in the execution directory.

Why I needs that?
I am not sure if DD CI is used for the service, even if it is assigned.
If it is really used, then the CAM doesn't decode your service.

maby load-balance with active fail-back is needed ;)

As far as I understood the code, this should be already the case, when DD CI is used by a service (currently only one service per DD CI possible).
A DVB CAM is always searched first (highest priority) and DD CI is a DVB CAM.

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by Alexander P 10 months ago

Today I had some time for further debugging...
Here are the results of the logs: https://pastebin.com/CjdHJQjp

Log started with viewing a V14 (ACL) encrypted channel, than switching to a HD01 (oscam) encrypted channel (line 895), than disbaling the CI slot (line 1901).

I hope, this log will help you, because I have no idea what it means ^^

RE: Support Digital Devices CI Interfaces - Added by saen acro 10 months ago

Jasmin Jessich wrote:

[...]
This looks strange to me. The CAM reports 18 CAIDs, but there is always the same printed. I guess Jaroslav needs to look at this. He recently added the en50221 handling to TVH and I guess there is something not correct, at least with the printing.

I am missing the DD CI traces. Please trace with these trace settings: "linuxdvb,ddci,en50221,dvbcam". This will log much more, so maybe you should write it to a logfile. This is how I start for debugging:
[...]
The result is then in the file "tvh.log" in the execution directory.
BR,
Jasmin

this is fixed #4400

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 10 months ago

Alexander P wrote:

Here are the results of the logs: https://pastebin.com/CjdHJQjp

I am not sure if the problem is solved in the recent TVH version. If no, here is the
analysis of the logfile (sorry for the delay, but I am still on vacation):

2018-01-07 13:38:57.158 [  TRACE]:ddci: CAM ci0 recv rd(CAM ->):494592, wr:494592
2018-01-07 13:38:57.158 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):456950, wr:456950
---> This lines are telling us that the DD CI CAM is getting data and the data is read from
     the CAM, too.
     And I can tell you, the CAM was able to descramble it, because there is no line
     containing "scrambled packets from CAM".

2018-01-07 13:39:09.588 [ NOTICE]:ddci: CAM ci0 unassigned from 0x5594ca71e660
2018-01-07 13:39:09.588 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):508317, wr:508317
---> Now you stopped watching the service, which was using the CAM.

2018-01-07 13:39:10.099 [  TRACE]:dvbcam: start service 0x5594cd075ff0
2018-01-07 13:39:10.099 [  TRACE]:dvbcam: dvbca0-0/0x5594cd075ff0: match CAID 098C PID 6892 (1AEC)
2018-01-07 13:39:10.099 [  TRACE]:dvbcam: dvbca0-0/0x5594cd075ff0: add CAID 098C to selection
2018-01-07 13:39:10.099 [ NOTICE]:ddci: CAM ci0 assigned to 0x5594cd075ff0
2018-01-07 13:39:10.099 [  TRACE]:dvbcam: dvbca0-0/0x5594cd075ff0: add ECM PID 6892 (1AEC) for CAID 098C
---> Now you started a service, which requires a descrambler. TVH did select again the DD CI
     CAM, because of the CAID of the service. Because the DD CI CAM was not used at this time
     TVH was able to choose it (based on the CAID).

2018-01-07 13:39:11.694 [  TRACE]:en50221: dvbca0-slot0-app00400041/0006: display control sending reply
2018-01-07 13:39:11.994 [  TRACE]:en50221: 9F 88 03 0B 97 41 6C 70 68 61 43 72 79 70 74 9F .....AlphaCrypt.
2018-01-07 13:39:11.994 [  TRACE]:en50221: 88 03 01 20 9F 88 03 10 05 44 72 FC 63 6B 65 6E ... .....Dr.cken
2018-01-07 13:39:11.994 [  TRACE]:en50221: 20 53 69 65 20 4F 4B 20 9F 88 03 1C 53 69 65 20  Sie OK ....Sie 
2018-01-07 13:39:11.994 [  TRACE]:en50221: 68 61 62 65 6E 20 6B 65 69 6E 65 20 42 65 72 65 haben keine Bere
2018-01-07 13:39:11.994 [  TRACE]:en50221: 63 68 74 69 67 75 6E 67 9F 88 03 1E 64 69 65 73 chtigung....dies
2018-01-07 13:39:11.994 [  TRACE]:en50221: 65 73 20 50 72 6F 67 72 61 6D 6D 20 7A 75 20 65 es Programm zu e
2018-01-07 13:39:11.994 [  TRACE]:en50221: 6D 70 66 61 6E 67 65 6E 20 21 80 02 01 00       mpfangen !....
---> This tells us, that the CAM can't descramble the selected service.
Q: Why you define the CAID of a service which can't be descrambled by your CAM in the
CAID list?
2018-01-07 13:39:17.252 [  TRACE]:ddci: CAM ci0 recv rd(CAM ->):566496, wr:566496 
2018-01-07 13:39:17.252 [  TRACE]:ddci: CAM ci0 got 48624 scrambled packets from CAM
2018-01-07 13:39:17.252 [  TRACE]:ddci: CAM ci0 send buff rd(-> CAM):20892, wr:20892
---> This tells us, that DD CI sends/receives data to/from the CAM, but the CAM couldn't,
     descramble the TS stream. Which is clear, because the CAM told us already, that it will
     be not able to descramble the stream, with the CAID 098C.

There is a setting in the Alpha Crypt CAM to announce all CAIDs or only those, the smart
card does really support. You should set it to announce only the supported ones.

If you think there is still a problem in TVH, we need to dig deeper in this and add debug
outputs in the selection mechanism. In my opinion the code in dvbcam does what it should
do and does select the DD CI CAM based on the CAIDs and if it is free (currently only one
service per DD CI).

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by saen acro 10 months ago

@Jasmin Jessich
In current condition DD code not handle
http://en.aston-france.com/cams/conax-professional.php
or some of the "hybrid" cams with also can handle more then one service at time.

On other side, standard operators cam, can handle two services simultaneous,
to make PiP (Picture in Picture) work.

RE: Support Digital Devices CI Interfaces - Added by Jasmin Jessich 10 months ago

My answer was concerning the problem Alexander P. has observed.

saen acro wrote:

In current condition DD code not handle
http://en.aston-france.com/cams/conax-professional.php
or some of the "hybrid" cams with also can handle more then one service at time.

Äh yes, and?
I know that several CAMs can handle more than one service, but the first part of the DD CI integration to TVH was only ONE Service per CAM.
I already started to work om MCD (second step), but this will take some time (currently I am on vacation).

BR,
Jasmin

RE: Support Digital Devices CI Interfaces - Added by saen acro 10 months ago

Don't hurry back from vacation,
Don't get loaded with complicated mental activities,
Even rest for us.

Later we will recall for this ;)

1 2 (1-25/42)