Привет помогите запустить rosscrypt каналы на 40Е у меня Drimbox 920hd, powervu идёт а rosscrypt неполучается не знаю где как прописать нужно в конфиге. Мой кочфиг не получается rosscrypt запустить.
I believe the dm920 is one of those receiver that have a driver problem and rosscrypt does not work on them.
Octagon sf4008, GI et11000, Mutant hd51, Dreambox 920 all seem to have the same SoC (broadcom 7251s) and suffer from the same driver issue. Read here for more details: _http://www.sat-universe.com/showthread.php?t=310350
Уважаемые,а как запустить етот оскам на ubuntu linux.Может получится прописать стрим для T2MI.На дриме не запускаются одновременно оскам и астра.Спасибо.
@vavaka and others. To make rosscrypt work with t2-mi channels, you have to add the rosscrypt caid as cached pid (C:A101) in the t2-mi service you have created in lamedb. You also have to change the output port in astra.conf and put the stream relay port. And also change the port in the user bouquets. Send me your lamedb (and lamedb5), astra.conf and user bouquet to do it for you. EDIT: Caid need to be in hex form, I edited it above.
nautilus7,Hi lamedb (and lamedb5), astra.conf and user bouquet attach Please show an example of what need to change them Добавлено 10 февраля | 2019г. | 16:05:22 As I understand it is necessary in services T2-MI c: 151000 to change to c: a101 ? In this case, T2-MI with this transponder does not go any also if to change port 9999 --> 17999 in all "make_channel" commands and in user's bouquets,that stops working normal Rossscript And T2-MI Rosscript also not working
No, you keep the cached pid c:151000 as it is (lowercase "c", without space), but you also add the caid value with C:A101 (capital "C" without space). It should look like this: c:151000,C:A101 You do this in all T2-MI muxes that have rosscrypt channels. =========================== astra.conf --> NO CHANGE ==================================================== In userbouquet you change the port for each channel to the stream relay prot 17999, for example: userbouquet.dbe0e.tv --> line 82 #SERVICE 1:0:1:3FC:DE6:193:0:0:0:0:http%3a//0.0.0.0%3a9999/rtrn/3558plp1:Россия 1 / Гтрк Самара (3558L) #DESCRIPTION Россия 1 / Гтрк Самара (3558L) change the port to the stream relay port: #SERVICE 1:0:1:3FC:DE6:193:0:0:0:0:http%3a//0.0.0.0%3a17999/rtrn/3558plp1:Россия 1 / Гтрк Самара (3558L) #DESCRIPTION Россия 1 / Гтрк Самара (3558L) ==================================================== In oscam-emu you have to make the stream server to listen to the t2-mi port 9999 instead of the enigma2 8001, so you change the source port: oscam-emu --> config --> stream relay -->Source Stream Port: 9999 oscam-emu --> config --> stream relay -->Relay Port: 17999 When you change the stream relay source port to 9999, it means that oscam-emu's stream relay will work only for T2-MI streams that come from astra-sm! This is a limitation of the current design of stream relay in oscam-emu. ==================================================== The stream goes like this: enigma streams at port 8001 --> astram-sm listens at port 8001 and streams at port 9999 --> oscam-emu's stream relay listens at port 9999 and streams at port 17999 --> enigma listens (through the custom user bouquet services) at port 17999. That's a triple streaming process!
After the changes are made, the channels in T2-MI stop working add in oscam.conf [streamrelay] stream_relay_ctab = FFFE,A101 stream_relay_enabled = 1 source stream port = 9999 relay port = 17999 What I'm doing wrong?
