OHMComm
OHMComm copied to clipboard
doe300
Platform-independent voice-over-IP peer-to-peer communication program
Currently there are several threads (RTP, RTCP, SIP, audio-loop) with everyone handling shutdown (of its own and triggering it for the whole program) differently. Overhaul triggering and executing shutdown: -...
- [ ] remove unused/obsolete parameters - [x] merge parameters for SIP and RTCP user-info (SDES) - [ ] make sure, all configuration modes support all new configuration (where necessary)...
Remove direct inclusion of opus and rtaudio or at least move into sub-projects, 1. since they are not compulsory anymore 2. so they don't bloat the repository 3. so they...
- [x] ~~Implement INFO [RFC 6086](https://tools.ietf.org/html/rfc6086): Just print INFO~~ Implemented [RFC 2976](https://tools.ietf.org/html/rfc2976) with basic support - [x] Implement capabilities [RFC 3840](https://tools.ietf.org/html/rfc3840): - Most can be set statically - Perhaps add...
SRTP (Secure Real Time Transport Protocol) is a profile for the RTP protocol. Thus, it should be possible to include it into our program by extending the RTPPackageHandler and providing...
add minimum number of buffered package before playing audio
Add implementation for [libgcrypt](https://directory.fsf.org/wiki/Libgcrypt) and [nettle](https://www.lysator.liu.se/~nisse/nettle/)?? Rewrite crypto-suits to be object-oriented, initialize/configure suite in constructor (see #76)
Add global variable with configured proxy (optional). If proxy is configured, all NetworkWrappers use the proxy to establish a connection/send packages Links: [RFC 1928 (Socks 5)](https://tools.ietf.org/html/rfc1928) https://stackoverflow.com/questions/18150561/send-and-receive-via-socks5-c
The current SIP implementation has a few weak points, namely: - session state: absolutely inaccurate and obscure, does not consider REGISTER, is set at various places, etc. - request-handling: currently...