You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
logger.LogDebug($"Setting audio source format to {audioFormat.FormatID}:{audioFormat.Codec}{audioFormat.ClockRate} (RTP clock rate {audioFormat.RtpClockRate}).");
Copy file name to clipboardExpand all lines: src/net/RTP/RTPSession.cs
+11-6Lines changed: 11 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -175,7 +175,7 @@ public class RTPSession : IMediaSession, IDisposable
175
175
176
176
protectedRtpSessionConfigrtpSessionConfig;
177
177
178
-
privateBooleanm_acceptRtpFromAny=false;
178
+
privateboolm_acceptRtpFromAny=false;
179
179
privatestringm_sdpSessionID=null;// Need to maintain the same SDP session ID for all offers and answers.
180
180
privateulongm_sdpAnnouncementVersion=0;// The SDP version needs to increase whenever the local SDP is modified (see https://tools.ietf.org/html/rfc6337#section-5.2.5).
181
181
internalintm_rtpChannelsCount=0;// Need to know the number of RTP Channels
@@ -1050,17 +1050,17 @@ public virtual SetDescriptionResultEnum SetRemoteDescription(SdpType sdpType, SD
1050
1050
else
1051
1051
{
1052
1052
// As proved by Azure implementation, we need to send based on capabilities of remote track. Azure return SDP with only one possible Codec (H264 107)
1053
-
// but we receive frames based on our LocalRemoteTracks, so its possiblet o receive a frame with ID 122, for exemple, even when remote annoucement only have 107
1053
+
// but we receive frames based on our LocalRemoteTracks, so it's possible to receive a frame with ID 122, for exemple, even when remote annoucement only have 107
1054
1054
// Thats why we changed line below to keep local track capabilities untouched as we can always do it during send/receive moment
0 commit comments