Scrambled T2-MI - Astra 4A at 4.8°E

it certainly depends on the FW version
I have here GTMedia V7 Turbo and ApeBox C2 4K,both to my knowledge with Ali processors, but with older FW.
With both Rx the reception of the coded T2-MI on 5°E 12245 V is not possible, i.e. they are not read in.

hi! hope that all people are fine now...!!
are this mux or channels broadcasting #DESCRIPTION T2MI 12245V PLP0 DSNS¿?

Gregory90 said:

it certainly depends on the FW version
I have here GTMedia V7 Turbo and ApeBox C2 4K,both to my knowledge with Ali processors, but with older FW.
With both Rx the reception of the coded T2-MI on 5°E 12245 V is not possible, i.e. they are not read in.

Click to expand...

Yes, good idea upgrading to the latest FW. Have done this on the sx88, no change. Still uncertain though
about the correct Sid entry for the key section.

No use, however, I wasnt aware that Abertis 30 W doesnt use encrypted t2mi pids

EnoSat said:

ABERTIS not use T2MI, uses an encapsulated TS

Click to expand...

Abertis uses a double encapsulation with separate keys for each PID.

How does your question relate to the fact that this package has double encapsulation?

any help with the new position?

i have this, but for me not work....

lamedb:

02c6:00300000:107b:0055:1:0
pid 4716
p:ZEONBUD,c:151000,C:0000,f:05

astra conf:

zeonmx2 = make_t2mi_decap({
name = "ZEONBUD MX-2 Test",
input = "http://localhost:8001/1:0:C:2C6:107B:55:300000:0:0:0",
plp = 0,
pnr = 0,
pid = 4716,
})

make_channel({
name = "ZEONBUD MX 2 Test",
input = { "t2mi://zeonmx2", },
output = { "http://0.0.0.0:9999/zeobud/mx2a", },
})

bouquet:
#SERVICE 1:0:1:1:A:2C:0:0:0:0:http%3a//0.0.0.0%3a9999/zeobud/mx2a:Перший
#DESCRIPTION Перший

softcam key;
F D66E3074 00000000 xxxxxxxxxxxxxxxxxxx ;(...)

thanks in advanced if any forum member help me thanks a lot!!

New PID
4716 --> 4096

Added on latest update for ali boxes.

4096 px reported encrypted by Flysat.
Are there keys available (11111....or other?) Thanks a lot