Aaron Clauson

In theory the frame rate is being taken from the video stream in the mp4 file [via FFmpeg](https://github.com/sipsorcery-org/SIPSorceryMedia.FFmpeg/blob/151ef001ca04dc23e7fbc0bc2a5b011c1113a919/src/FFmpegVideoDecoder.cs#L151). If you want to manually adjust that rate there is currently no...

@ha-ves thanks for the update. Good for merge now just needs the conflcit resolved.

@ha-ves thanks for updating the PR. Have you been able to test H265 with Chrome, or any other browser, yet?

There is a [TCP ICE channel](https://github.com/sipsorcery-org/sipsorcery/blob/06a4d3403ebbd23d1af8bd402f83d9f2d7005ec6/src/net/ICE/RtpIceChannel.cs#L128) albeit with a very confusing base class. I have personally never used or tested that implementation. In the original implementation no TCP option was...

@bryanlimktscv (or anyone else) would you be able to confirm whether that PR allows ICE over TCP to now work?

Just in case it helps anyone the steps below worked for me after a lot of trial and error (I am not a Go developer and use it so infrequently...

If there's any further info please feel free to re-open this issue.

The RTCP handling in this library is very immature. RTCP feedback reports are recognised but currently [nothing is done with them](https://github.com/sipsorcery-org/sipsorcery/blob/2f59115b2c4d49ded9bc5cd3a6734bb10e5c4bb8/src/net/RTCP/RTCPSession.cs#L279). PR's welcome.

tACK b074ae1b4f52471a9d71e9431deebae5ec3d603e native Windows build. ``` c:\dev\github\bitcoin>mt.exe -nologo -inputresource:build\bin\Release\bitcoind.exe -validate_manifest Parsing of manifest successful. ```

re-tACK c0f41523973e33a8cd104a8ebf4906a4d99f3eed.