Skip to content
This repository has been archived by the owner on Mar 22, 2022. It is now read-only.

Different track ids between answers sdp and local tracks #857

Open
Qualcuno opened this issue Mar 10, 2022 · 0 comments
Open

Different track ids between answers sdp and local tracks #857

Qualcuno opened this issue Mar 10, 2022 · 0 comments

Comments

@Qualcuno
Copy link

Hi,
i found a mismatch between the ids of msid line in answer and the ids presents in the transceivers and locatracks of peer object.

This is an example:
considering only video, this is an msid line with the stream identifier (localStream_f63e346e-ba27-4134-9fc1-16bb77566099)
and the track identifier (75bf5eb4-d243-489d-8346-777e5e34b01f) of the answer

a=msid:localStream_f63e346e-ba27-4134-9fc1-16bb77566099 75bf5eb4-d243-489d-8346-777e5e34b01f

but if i try to explore the entier peer object, the trackid 75bf5eb4-d243-489d-8346-777e5e34b01f not exists anywhere.
if searched in
Peer.Transceivers
LocalVideoTrack
Sources and others
What i found is a different identifier associated to the LocalVideoTrack
3a1ecc0d-685c-4816-a077-8a2bad42dffe

I developed a my webrtc library on ios and android, and a=msid trackId and localtracks have same ids...

why in this library the ids are differents? is this a correct behavior?

I'm working on HL2 with 2.0.2 version of Webrtc library

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant