oscam (1.20-10351~r10123-precise) precise; urgency=medium
* [r10123]
WebIf:
Fix typo
* [r10122]
sci readers.
revert to flush procedure like it was before. Since there are still reports off non working sci one some stb's.
flush back to 1 if it not works buffer flush done by reading it out.
* [r10121]
WebIf:
- set height for select in script.html If script not found.
* [r10120]
- Emm filtering cosmetics for dvbapi
* [r10119]
Some rework on emm provider matching the reader providers.
Hope I managed to minimize the cs378/camd35 4 digit provid effect!
* [r10118]
- More log output on emm filtersetting!
* [r10117]
- Even more EMM rework dvbapi module
* [r10116]
external reader
I saw that the loop implemented before even never worked. It just caused an oscam block voor 30 tries each seconds one during 60 seconds.
But actually did not a real retry to find the device. Now it will try 10 times 1 try each two seconds . Thats more then enough. If after those tries (20 sec) Device still not found reader will be disabled. And oscam can work with the avbl readers.
* [r10115]
external readers
Added webif ouput reader device error in case off device failure due to wrong configs or unplugged cable
* [r10114]
- DVBAPI: dont rely on data a filter is returning to discover if its the emm cat, better check if emmpid is 0x01
* [r10113]
- Dvbapi: removed emm cat filter from emm filter list too (why was it there in first place?!) -> should prevent cached filtered responses on some type receivers!
* [r10112]
external readers.
When an external reader cable was unplugged or wrongly configured, Oscam did not allowed clients login at all for other readers with waitforcards (default enabled) Now the reader of wich device can't be detected will be closed and set to disable then oscam can continu whitout that reader.
some small fixes smartreader.
* [r10111]
smartreader
Better log output if endpoint detection failed .
Requested in ticket #4052
* [r10110]
- Emm just compare last 4 digits of provid, this should fix sharereader!
* [r10109]
- Simplify dvbapi emm reader matching
- Re-introduced camd35/cs378 4 digits emm provid matching
* [r10108]
- Always start filtering on matching emmpid with correct caid and no provid
* [r10107]
- Emm rework since auprovid on sharereaders are changing constantly
* [r10106]
- Revert 10105 since sharereader do deliver 6 digit provid
* [r10105]
- Minor emm fixing since share readers use only 4 digits provid
* [r10104]
- dvbapi fix pmt6 listenfd to socket was openened but never closed on connection error -> opening new fd next run -> running eventually out of fd!
* [r10103]
- Another rework for emmpid selection versus au enabled readers
- Reanalyzed emm cat parsing -> updated viaccess and nagra parsing
* [r10102]
bulcrypt: Fix ticket #4055 (Bulsatcom removed CAID 5581).
Credits to kraiv and chepik from satsupreme forum.
* [r10101]
- Next rework of dvbapi emm handling:
If you have a card that is multiprovider dont set auprovid.
Just add idents, each ident should match the (emm) provid.
Example
Old seca2 card:
auprovid leave empty
idents:0100:00006a,00006c,00006d
* [r10100]
- Attempt to stop starting repeatingily new emmfilters if none are active on a demuxer
This behaviour is e.g. triggered if watching more than 1 channel from same provider
* [r10099]
- Removed extensive emm matching in dvbapi again (nobody except me used it and it was flooding dvbapi debug logging!)
- Tryfix dvbapi problem on multiecm-s channels (ticket 4056)
* [r10098]
- Viaccess is now using correct provid again on emm cat parsing (issue introduced 10097)
* [r10097]
Some more rework of dvbapi emm handling:
If emm cat is fetched dont filter the emmmpids in it against active au readers, that will be done later on too.
This way we avoid scenario that a new card cant find any valid emmpids and dont get any emm updates.
-- Andrey Pavlenko <email address hidden> Sun, 04 Jan 2015 11:42:37 +0300