will i get the entitlement update with these configs?

HI Fellas, my entitlements were due to expire yesterday which they did, when i looked at the status in Oscam it stated "no entitlements" however all channels cleared for the rest of the day which i thought was strange, today all channels have gone and am just wondering if im blocking the ecm to update entitlements, my configs are below and were compiled along with the help of some knowledgeable users on here so not sure if its that as some accept emms from clients for an update and others dont because im told cccam has the ability to receive emms itself for an update, im using Linux server Ubuntu 13.10 , OSCAM 1.20-unstable_svn build r8846 + cccam 2.1.3, omnikey, also got a spare box connected via cccam protocol in oscam.

oscam.config :

[global]
logfile = /var/log/oscam.log
nice = -1
preferlocalcards = 1

[newcamd]
port = xxxxx@0963:000000
key = 0102030405060708091011121314
keepalive = 1

[cccam]
port = xxxxx
version = 2.1.3
reshare = 0

[webif]
httpport = 16002
httpuser = admin
httppwd = admin
httprefresh = 30
httpallowed = 127.0.0.1,192.168.0.0-255.255.255.255

oscam.user :

[account]
user = linuxsat
pwd = support
group = 1
au = ***uk
caid = 0963
keepalive = 1
cccmaxhops = 0
cccreshare = 0

[account]
user = linuxsat1
pwd = support1
group = 1
au = ***uk
caid = 0963
keepalive = 1

oscam.server :

[reader]
label = ***uk
protocol = pcsc
device = 0
caid = 0963
detect = cd
group = 1
emmcache = 1,3,2
blockemm-unknown = 1
blockemm-g = 1
blockemm-s = 1
saveemm-u = 0
saveemm-s = 0

any help would be great! thanks in advance.

I forgot to say, i am aware this may just be a waiting game, waiting for the ECM to come through however i just want to be sure i will allow it through with my current configs opposed to having problems allowing it to write due to my setup.

thanks again!

HI Ten, thanks for the reply, no there are no restrictions on both the c line or the f line, what i don't understand is if the entitlements were meant to expire on a certain date, why weren't the ECM signal sent just before they expired to renew entitlements?

thanks.

i got *** to send me another card 2 months ago and entitlements were 2 months ahead and cleared fine in oscam, but didn't update before expiry, i left 2 boxes on a couple days before expiry, 1 box via cccam and another box via cccam user in oscam, left both boxes on sly 1 for 2 days straight also through the night so not sure why i didn't get it, this is what is in my log:

2013/12/04 22:21:19 8E71DC8 c [GET_CW] wait_time 0 caid 0963 prov 000000 srvid 0F1A rc 100 cacheex cl mode 0 ex1rdr 0
2013/12/04 22:21:19 8E71DC8 c request_cw stage=2 to reader ***uk ecm hash=DA9CBB779B905CF376369D4F558DDEDC
2013/12/04 22:21:19 8E71DC8 c start reader thread action 5
2013/12/04 22:21:19 8E70200 r data from add_job action=5 client r ***uk
2013/12/04 22:21:19 8E70200 r ***uk [videoguard2] classD3 ins54: status 90 00 = ok but cw=00 -> channel not subscribed
2013/12/04 22:21:19 8E70200 r add client job action 24 queue length 1 linuxsat
2013/12/04 22:21:19 8E71DC8 c ***uk [videoguard2] TRACE: ecm answer for ecm hash DA9CBB779B905CF376369D4F558DDEDC rc=4
2013/12/04 22:21:19 8E71DC8 c linuxsat (0963&000000/FFFF/0F1A/7D:DA9CBB779B905CF376369D4F558DDEDC): not found (92 ms) by ***uk
2013/12/04 22:21:21 8E71DC8 c [OSCAM-WORK] new event 1 occurred on fd 12 after 1936 ms inactivity
2013/12/04 22:21:21 8E71DC8 c matching_reader became slot attribute of 1
2013/12/04 22:21:21 8E71DC8 c [GET_CW] wait_time 0 caid 0963 prov 000000 srvid 0F1A rc 100 cacheex cl mode 0 ex1rdr 0
2013/12/04 22:21:21 8E71DC8 c request_cw stage=2 to reader ***uk ecm hash=A7ED0D46B0876112CEC277B61736520B
2013/12/04 22:21:21 8E71DC8 c start reader thread action 5
2013/12/04 22:21:21 8E70200 r data from add_job action=5 client r ***uk
2013/12/04 22:21:21 8E70200 r ***uk [videoguard2] classD3 ins54: status 90 00 = ok but cw=00 -> channel not subscribed
2013/12/04 22:21:21 8E70200 r add client job action 24 queue length 1 linuxsat
2013/12/04 22:21:21 8E71DC8 c ***uk [videoguard2] TRACE: ecm answer for ecm hash A7ED0D46B0876112CEC277B61736520B rc=4
2013/12/04 22:21:21 8E71DC8 c linuxsat (0963&000000/FFFF/0F1A/7D:A7ED0D46B0876112CEC277B61736520B): not found (92 ms) by ***uk
2013/12/04 22:21:25 8E71DC8 c [OSCAM-WORK] new event 1 occurred on fd 12 after 3522 ms inactivity
2013/12/04 22:21:25 8E71DC8 c matching_reader became slot attribute of 1
2013/12/04 22:21:25 8E71DC8 c [GET_CW] wait_time 0 caid 0963 prov 000000 srvid 125D rc 100 cacheex cl mode 0 ex1rdr 0
2013/12/04 22:21:25 8E71DC8 c request_cw stage=2 to reader ***uk ecm hash=AE66FC4E24A87E717FA60DEBBE0FB750
2013/12/04 22:21:25 8E71DC8 c start reader thread action 5
2013/12/04 22:21:25 8E70200 r data from add_job action=5 client r ***uk
2013/12/04 22:21:25 8E76F38 c [OSCAM-WORK] new event 1 occurred on fd 13 after 8000 ms inactivity
2013/12/04 22:21:25 8E76F38 c matching_reader became slot attribute of 1
2013/12/04 22:21:25 8E76F38 c [GET_CW] wait_time 0 caid 0963 prov 000000 srvid 125D rc 99 cacheex cl mode 0 ex1rdr 0
2013/12/04 22:21:25 8E70200 r ***uk [videoguard2] classD3 ins54: status 90 00 = ok but cw=00 -> channel not subscribed
2013/12/04 22:21:25 8E70200 r add client job action 24 queue length 1 linuxsat
2013/12/04 22:21:25 8E71DC8 c ***uk [videoguard2] TRACE: ecm answer for ecm hash AE66FC4E24A87E717FA60DEBBE0FB750 rc=4
2013/12/04 22:21:25 8E71DC8 c linuxsat (0963&000000/FFFF/125D/5F:AE66FC4E24A87E717FA60DEBBE0FB750): not found (78 ms) by ***uk
2013/12/04 22:21:25 8E76F38 c ***uk [videoguard2] TRACE: ecm answer for ecm hash AE66FC4E24A87E717FA60DEBBE0FB750 rc=4
2013/12/04 22:21:25 8E76F38 c linuxsat1 (0963&000000/FFFF/125D/5F:AE66FC4E24A87E717FA60DEBBE0FB750): not found (66 ms) by ***uk
2013/12/04 22:21:25 8E71DC8 c add client job action 24 queue length 0 linuxsat1
2013/12/04 22:21:31 B6800468 h WebIf: Received stale header from 192.168.1.5 (nonce=172dd5d1f1fec229c02974a3d4fe1fe2, expectednonce=82c71a33366b293ed3453cb80ee77da8, opaque=ee86e79e3de8b276b40eee5192672376).
2013/12/04 22:21:31 B6800468 h WebIf: Origin checked. Result: access from 192.168.1.5 => allowed

not really too sure what it all means, maybe you could get something from this? thanks again.

HI Meerkat, thanks for replying to my post, your right i did have this problem last time but i don't know what you mean by "leaving your entitlements until the last minute" i must be missing something? what can i do? is this something i can control? i thought you just leave everything on and an update will come through on its own, all thats in the cccam.config on the client box is ip / port / user / pass, by the way i am not accepting any emms from the clients as was told cccam can update on its own.

thanks again i appreciate the help.

HI again, just wanted to add the cccam client box im using is an openbox x5, i also have a dm800 original, would it be worth me adding the dm800 as a cccam client through oscam, maybe this box would be better at updating? thanks.

ok, so i used the activate channels process online and entered my box details(which im not sure was a good thing to do) and now even though the entitlements have been updated oscam is not clearing sport + movies + hd despite me having all entitlements, how come everyone else can update fine and i keep getting these problems!! :62:

meerkat, what do you do to update your card before it expires ? not sure what i was supposed to do, and also i dont have a 2nd card.

thanks.

Quote from Mee®kat

I use mgcamd only to update any cards i have in my possesion..always have/it is however dependant which caid i update/some fulltime open on unique and some on certain day/s and shared emm..

yes ok.. and i use oscam + cccam protocol to update my card, leaving it on sly1 when not watching and 3 days straight before expiry hoping for the emm to come through, so what are you doing differently to me as your messages imply i should be doing something more specific before expiry?

Quote from Mee®kat

If your serious about running this card then you need to take your finger out your backside and babysit your server...simple as...this is what you are supposed to do so if this too much of a hassle then your probably best to throw in the towel.

Sorry to be hard on you but i have just scrolled through your archive posts and it does seem that you have had a 2nd card due to a previous card possibly being hw paired also which is the reason for your new card?dont have time to properly read through all your posts right now but you are gonna have to do it all over again...so new card or try and pair your latest card to a box that does not accept the new software...until that happens your stuffed for premium channels on your server and pointless asking for any help really as you can simply update your card in the official stb now as its hw paired unfortunately.

MK

that's fine mate, sorry i misunderstood you i thought you were saying a 2nd card on another caid, yes that's correct i got another card and will have to try again, i wont be throwing in the towel, yes im finding it hard at times but i do still enjoy it, thanks for all your help so far and the hard talk! ha ;@)

Quote from thatfellow

I will start by saying that I feel for you m8, but the sympatyh has to end there..

You knew it was a waiting game but you still could not wait? I find it hard to believe that any member of this forum would actively seek to pair their card, There are dozens of threads warning about the new sly pairing..

yes i knew it was a waiting game in which i did wait, but after all the waiting the entitlements expired anyway, i wasn't on a quest to pair the card and am fully aware of slys new pairing method, the only reason i followed the activation procedure online was because i was confused by "meerkats" reply's implying i should have done something before the entitlements expired and also "tenbelow" suggested it to me.

Quote from thatfellow

EMM's are not being sent nearly as often as they used to be, you cant just have AU off for a month at a time and switch it on a few days before entitlements run out because the chances are that you have missed your update..
As long as you have your configs in order and a few trusted clients sending updates, that is all you can do.. Because you paired your card online, I would assume that any new cards sly would send you will also be pre-paired with your box details..
As Mee®kat mentioned, This hobby (especially with 0963) has turned into a card babysitting session. You cant just plug in your card and ignore it...
If you do manage to get sharing again, use your loaf and read up on the forum..

if what i have read is correct emms are sent every 2 weeks for 2-3 days, i didn't have au off and switched on just a few days before expiry, i leave au on in my setup always, i have posted my configs and the do seem in order however i dont accept any emms from clients, would you recommend this? i will try again and "use my loaf" i have read and now im at the point where i think ive read too much where im starting to confuse myself! thanks i do appreciate the help!

Quote from Mee®kat

Well for a start you should not be leaving your cards entitlements 3 days prior to expiration/thats 1 thing i dont do...

so when you do get the card entitlements updated to 8 weeks ahead, when do you attempt to get them updated again? when theres 6, 4, 2 weeks remaining ?

also when you say you dont leave it to the last few days to update, what do you do to update them? just leave it on sly1 via mgcamd hoping to catch the update when it comes through? because that is exactly what i do.

thanks.