Opened 4 years ago

Last modified 4 years ago

#4424 new task

Clients Disconnect

Reported by: Best-Of-Me Owned by:
Priority: minor Component: Protocol - CCCam
Severity: medium Keywords: cccam, client, disconnect
Cc: Sensitive: no

Description

Revision

1.20 r11211

Issue Description

CCcam Clients lose the Connection

When the issue occurs

If many Clients are active (30 Clients)

How the issue is reproducable

At Primetime (If many Clients are active)

<Don't forget to ATTACH (NOT post here as text) a log file of oscam in debug mode (start oscam with -d255) and to remove the brackets around the fields! Otherwise, your ticket will be closed as you seem to be unable to read.>

Attachments (1)

oscam.log (58.4 KB) - added by Best-Of-Me 4 years ago.

Download all attachments as: .zip

Change History (7)

Changed 4 years ago by Best-Of-Me

Attachment: oscam.log added

comment:1 Changed 4 years ago by savan

(UserA: disconnected by remote server) which mean client is disconnected not by your cccam, its disconnected on remote cccam server and thats nothing wrong with your local cccam and allso you can do nothing about that! Only which is wrong on oscam is keepalive message. After my analyse of the original cccam protocol, server never sends keepalive, instead server sends only keepalive reaply to the cccam client keepalive request! On oscam booth client-server sending keepalive message which is wrong and not in original cccam! I am not analysed what is max waiting time for client keepalive on original cccam, on oscam its 12 secconds if I am not wrong, but think that oscam maintainers need to disable these cccam keepalive server side thing and stop sending keepalive message to the cccam client since it not exist on the original cccam protocol! On original cccam it working by next way: client sends keepalive -> server replies with keepalive -> dont know what is max waiting time for the keepalive reaply but if cccam client don't send it to the server than server disconnect these client, or vice versa - reaply with keepalive reaply to the client if client send keepalive message to the server... etc. Server never send keepalive to the client if client didn't send it first! Instead server disconnect client after max time waiting for the client keealive message. On oscam its diferent story and which I know somebody allready fixed client disconnections on oscam and its confirmed that there is no more client disconnects, only maybe somebody need to remove our server keepalive thing from oscam and make it like original cccam protocol.

Last edited 4 years ago by savan (previous) (diff)

comment:2 Changed 4 years ago by Best-Of-Me

I'm not sure like I have understood you correctly. You mean i can fix the Client CCcam disconnects if i disable the keepalive option of users in OScam?

comment:3 Changed 4 years ago by savan

Keep keepalive option checked! But problem on your cccam is not your cccam, problem is remote cccam!

comment:4 Changed 4 years ago by Best-Of-Me

But the remote CCcam is a simple CCcam 2.3.0 on a Enigma2 Receiver, what can go wrong there and how can i fix it? the keepalive option on oscam.user is already checked.

comment:5 Changed 4 years ago by savan

As you can see I have told here allready about problem in oscam design! Oscam sends keepalive message to the oscam client which is wrong thing since in original cccam protocol only client sends keepalive and server only respond to it with keepalive reaply, so sometimes it cause comunication isue which cause original cccam to disconnect from it. I have told about that in the forum but seems nobody going to fix that. In any way check option in global settings/cccam aka keep clients connected!

Last edited 4 years ago by savan (previous) (diff)

comment:6 Changed 4 years ago by Best-Of-Me

The keepalive option is aleady checked but it happens anyway

Note: See TracTickets for help on using tickets.