Start two different session with janus client sometimes its give same preview in both the preview layer

[ChiragLiveu]

I have run two separate clients using two separate channels and web IDs but sometimes in the preview layer, I will get the same preview in both the instance in iOS & Android as well. I have debugged and checked each time I have passed two different webID to stream on the server side it takes two different requests and sends a proper preview but on the mobile side, it takes the same preview layer sometimes. I am using the streaming through a web socket take reference from the below link.

https://github.com/flutterjanus/flutter_janus_client/blob/master/example/lib/typed_examples/streaming.dart

[shivanshtalwar0]

is it still happening?

[ChiragLiveu]

Yes I have the still same problem can you please help me for the same.

[shivanshtalwar]

Okay so maybe try using streaming id for rtcrenderer map instead of track id in onTrack stream handler

[ParthSolankii]

is it still happening?

I am also having a similar problem, both the camera window are showing on the caller's mobile, But the receiver is not able to see the caller's window.
#151

[shivanshtalwar0]

in the latest commits this should be fixed let me know if you still face this

[shivanshtalwar0]

so #151 this fixed for you or not?

[ParthSolankii]

I am facing another issue in this while calling, that needs to be fixed. Not able to call again after disconnect the call.

…

On Wed, Jan 31, 2024, 18:56 Shivansh Talwar ***@***.***> wrote: in the latest commits this should be fixed let me know if you still face this — Reply to this email directly, view it on GitHub <#116 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7XA2SFHLDLEURCGAPS3IXDYRJBBJAVCNFSM6AAAAAAUP5KHCCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGMRQGM2DE> . You are receiving this because you commented.Message ID: <flutterjanus/flutter_janus_client/repo-discussions/116/comments/8320342@ github.com>

[shivanshtalwar0]

not sure of your codebase, but from what i understand if your session/ handle is detroyed using the same session and handle will not work, so either make sure session is not destroyed and attach a new handle every time you want to call again or update the existing handle with new handle value

[ParthSolankii]

What will be the best way to achieve continuously calling after disconnect the call ? i am sending hang-up data on hangup,

…

On Wed, Jan 31, 2024, 19:18 Shivansh Talwar ***@***.***> wrote: not sure of your codebase, but from what i understand if your session/ handle is detroyed using the same session and handle will not work — Reply to this email directly, view it on GitHub <#116 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A7XA2SEXNW3WGKJCWG72WA3YRJDTTAVCNFSM6AAAAAAUP5KHCCVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DGMRQGYYDQ> . You are receiving this because you commented.Message ID: <flutterjanus/flutter_janus_client/repo-discussions/116/comments/8320608@ github.com>

[shivanshtalwar0]

yes hangup tears up the internal peer-connection and also destroys the resources of that handle so to let users have call again
initialize pluginHandle again something like that by

initializePlugin(){
this.pluginHandle=await this.session.attach<VideoRoomPlugin>()
//rest of hooks associated to this.pluginHanlde like onMessage,onTrack and so on
}

so everytime you destroy or hangup make sure you call initialize() so all the state of plugin is fresh