Erik HortschandClaude Opus 4.8 67af635be7 rtc: route answer to publisher in single-PC / one-shot mode ...

Correct the previous nil-guard: dropping the answer prevents the crash but
breaks subscribe renegotiation. In single-PC (UseSinglePeerConnection) and
one-shot signalling modes the single publisher PC carries both directions;
when the server renegotiates to push a subscribed track it offers on that PC
(NegotiateSubscriber -> publisher.Negotiate -> signalSendOffer) and the client
replies with an answer. Route that answer to the publisher, matching every
other subscriber-path method in TransportManager (GetSubscriberRTT,
AddTrackLocal, AddSubscribedTrack, NegotiateSubscriber, ...).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-16 13:40:29 -07:00

..

agent

rtc: report participant kind code and details (#4534)

2026-05-18 23:20:52 -07:00

clientconfiguration

Check Less and LessEq in version compare. (#4532)

2026-05-18 12:38:49 +05:30

config

Add TURN permission handler. (#4505)

2026-05-06 23:43:11 +05:30

metric

Update mediatransportutil (#4115)

2025-11-28 21:51:53 +05:30

routing

Convert sort.Slice -> slices.SortFunc (#4472)

2026-04-23 15:12:24 +05:30

rtc

rtc: route answer to publisher in single-PC / one-shot mode

2026-07-16 13:40:29 -07:00

service

Metrics for participant active, i. e. fully established. (#4557)

2026-06-03 19:50:19 +05:30

sfu

Use NACKQuueInterface type. (#4538)

2026-05-21 23:00:51 +05:30

telemetry

Metrics for participant active, i. e. fully established. (#4557)

2026-06-03 19:50:19 +05:30

testutils

agent service: new protocol & namespaces (#2545)

2024-04-03 15:25:42 -07:00

utils

add more types to signum (#4473)

2026-04-23 15:41:55 +05:30