Tvheadend

Work same as newcam.
Share config to compare.

Hi. I dont think there is anything to share? I just add new CCcam and fill out details. It connects fine but always gives "Got unexpected ECM reply".

Maybe this is because there are many cards for many different providers on this CCcam and TVH doesnt like that? With my nlines they were just for my provider only.

Chris

I should clarify some things. The C-lines do work if I run them through OScam and work via CAPMT in TVH. Its just TVH cant seem to handle them. Makes me wonder if its a bug or something in TVH.

2018-11-14 11:39:39.562 cccam: srv3:12000: Ignore ECM request 81 (server is busy)
2018-11-14 11:39:39.562 cccam: srv2:17000: Ignore ECM request 81 (server is busy)
2018-11-14 11:39:39.562 cccam: srv1:13000: Ignore ECM request 81 (server is busy)

2018-11-14 11:18:24.104 cccam: srv3:12000: Got unexpected ECM reply (seqno: 1)
2018-11-14 11:18:24.104 cccam: srv2:17000: Got unexpected ECM reply (seqno: 1)
2018-11-14 11:18:24.112 cccam: srv1:13000: Got unexpected ECM reply (seqno: 1)

???

Still not see any config file.
maby oscam log

There is no problem using cccam through oscam. Shouldnt c-lines work through TVH without the need for oscam though?
I'm happy because I have it working, but I guess there is a bug with TVH and cccam.
The bottm 3 lines of the log posted above are what I see too.

Same here.

https://tvheadend.org/issues/5099

I've opted to configure OSCAM to read the CCCAM lines and configured it also as a newcamd server.
TVheadend connects to oscam in newcamd format.

Working for some weeks without an issue:

OSCAM:
config > newcamd
- port: 9201@1111:000000 (in the form: port@caid:000000 - the port to answer request, followed by the caid to answer in this port)
- key: 0101010101010101010101010101
- keep alive: on
- mgclient: on

More info in oscam docs.
Don't forget to define a reader per cccam line you want to connect to.

TVHEADEND:
configuration > CAs > Add > Type code word client (newcamd);
- client name: (whatever you want);
- username: (the user defined in oscam to access this newcamd connection - remember to have it configured in the same group as the newcamd server);
- password:
- hostname: localhost (as oscam is running in the same machine as tvheadend)
- port: 9201 (the port defined in oscam to answer requests for newcamd
- DES key: 01:01:01:01:01:01:01:01:01:01:01:01:01:01 (must be the same key defined in oscam for this newcamd connection)
- Update card (EMM): off
- Updates from one mux (EMM): off
- keepalive interval: 30

This way tvheadend connects to oscam in newcamd. Oscam connects to the readers (cccam lines) you want.
You can define and redefine oscam readers, without having to touch newcamd server or tvheadend configuration.

Any advantages using newcamd over linux dvbapi as the protocal for connecting oscam to tvh? I have been happy with linux dvb api.

in my case, dvbapi, had some sort of "bug" in which sometimes the connection was refused and even after a service restart, tvheadend refuses to connect - the turn around was to recover a previous tvheadend configuration.

With newcamd i've got the best stability.