Commit Graph

8 Commits

Author SHA1 Message Date
Raja Subramanian
0236ffc17f Include mid -> trackID in SDP. (#1256)
* Include mid -> trackID in SDP.

And send it in subscriber peer connection offer also. It can be useful
to clients even in dual peer connection case.

* generated protobuf

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-10-15 23:01:18 +05:30
Raja Subramanian
bfdbffc082 Use mapped SDP answer when using single peer connection mode. (#1255)
* Use mapped SDP answer when using single peer connection mode.

In single peer connection mode, the client does not get the
TR_ ids for tracks. That is because the transceiver is created with a
receiver when the offer is generated and a random id assigned. Once the
id is assigned, it is not updated. So, when client gets `onTrack`, the
id of the associated MediaStreamTrack is not the TR_ variety.

So, send the mapping of mid -> trackID in signalling when sending
answer. And used that on client side to find LK track ID for given mid.

Side note: Probably worth doing it for dual peer connection also when
subscriber sends offer so that we do not have to deduce it on client
side using some rules.

* generated protobuf

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-10-15 18:18:54 +05:30
Raja Subramanian
7f6468a6a0 join request as proto message (#1151)
* join request as proto message

* generated protobuf

* add join_publish

* generated protobuf

* comments

* generated protobuf

* simulcast not yet deprecated

* generated protobuf

* remove join_publish

* generated protobuf

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-08-07 11:00:07 +05:30
Raja Subramanian
1edabe8e86 Delete v2 signalling (#1150)
* Delete v2 signalling

* generated protobuf

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-08-06 08:46:41 +05:30
Raja Subramanian
7313a8195a Add last processed remote message id when adding to cache also as the… (#1144)
* Add last processed remote message id when adding to cache also as the returned message could be sent on the wire

* generated protobuf

* clean up

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-07-25 14:03:35 +05:30
Raja Subramanian
afef3ef967 HTTP DELETE to delete a participant session - relay signal message for (#1143)
* HTTP DELETE to delete a participant session - relay signal message for
that.

Also, doing a basic signal cache and building server message and client
message cache on top of it.

* generated protobuf

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-07-24 22:52:57 +05:30
Raja Subramanian
34c7a0eb63 More v2 stuff (#1141)
* More v2 stuff

- Adding `Trickle` to client -> server message. There should not be any
  tricklw from server -> client in v2. So, not adding it. Will add if
  needed later.
- Some utils to parse envelopes as we are moving in the direction of
  having an envelope of messages in the initial connect request to keep
  it modular. May change again later, but today's state is this.
- change relay signal to pass wire message back and forth.

* generated protobuf

* add utils

---------

Co-authored-by: github-actions <41898282+github-actions[bot]@users.noreply.github.com>
2025-07-24 10:02:30 +05:30
Raja Subramanian
52633eee69 Move signalling utils to protocol so that both server and Go SDK can use (#1138)
it.
2025-07-21 17:12:33 +05:30