OlegShklyarov

Seems so. Waiting for Zerody

maybe our time has come. To go to the factory

And when user has many channels? He should authorize in the browser first, extract cookies and then put them to the call? For each channels separately? 

> It's been solved. thank you How? Share you cure, please

Should we change the connectionWrapper? `this.connection = new WebcastPushConnection(uniqueId, options);`

> ``` > this.connection = new WebcastPushConnection(uniqueId, { > requestHeaders: { > "Cookie": "sessionid=f6324878b8b34dbb8f86f1a2aafe5a0a;", > }, > }); > ``` > > Only this here solved my problem, I didn't...

I just use this on a client side: ``` socket.connect(uniqueId, { requestHeaders: { "Cookie": "sessionid=7877777773c2fedf3923ce3c4;", }, enableWebsocketUpgrade:false, requestPollingIntervalMs: 500, ``` For how long is the session valid?

And if I will relog on that browser, session will be terminated?

They also banned my account where I took a session id from. Is not required anymore? Provided by the backend?

Maybe Tt is changing something again. They banned my sessionid account.