I think sipsorcery is an excellent implementation of the sip standard. I think it would be great to extract that part of the library, since it solves one problem and does it very well.
A separate library for media seems like a natural break. While the sip standard is relatively static, media will continue to evolve over time. Also, with .net there are considerations around memory use and garbage collection which would be nice to address in an isolated area.
I'm not too familiar with webrtc, although I agree that it is likely to be the most common use case for this library going forward. It would be nice to have that as a separate library, but if it complicates the implementation maybe it is not worth it.
Additionally, particularly with the media focused part of the library, I think it would be worth considering abandoning support for .net framework. The new support for memory efficiency in .net is great and it would be nice to embrace this.
I don't see any good reason to rename the ORG. You have built a strong brand, and it's a neat name.

Given the recent license discussion in #1140, is the plan to split the repository into multiple parts (and nugets) still the same ?

- WebRTC
- SIP (or VoIP)
- Core (or Net) for everything else. This could be broken down further for things like RTP, ICE, STUN, SDP etc. but that seems like extra work for marginal benefit.

I would suggest having a dedicated repository <OrgName>.Net.DtlsSrtp that would contain the current code under AGPL. It would still serve as a building block for that agree with the terms of usage of such license. As a result, it would look like this :

• OrgName.WebRTC as originally suggested
• OrgName.SIP as originally suggested (or .SIP .VoIP)
• OrgName.Net.DtlsSrtp for Dtls/Srtp under AGPL (or .Net .Core)
• OrgName.Net for remaining parts