For complete rtpengine documentation, take a look at the rtpengine README.md: https://github.com/sipwise/rtpengine There are new feature added with each new rpengine release. The opensips rtpemgine module documentation (with respect to flags) should be seen as a starting point.and the rtpengine README is the official documentation.. The opensips rtpengine module provides a mechanism to pass those flags as strings to the rtpengine instance. Maybe we should add this to the documentation.
Regards, Ovidiu Sas On Sat, May 16, 2020 at 3:37 PM Robert Dyck <rob.d...@telus.net> wrote: > > I am wanting to convert my config/script to use rtpengine instead of rtpproxy. > I think it would better deal with webrtc. After looking at some examples I > found, I see a couple of parameters that are not mentioned in the opensips > documentation. First there is the offer/answer option ice=force-relay and > secondly DTLS=passive. > > Are these options obsolete/deprecated/intentionally omitted? > > On the subject of DTLS I noticed that when I use ice=force in offer and answer > rtpengine sends new DTLS fingerprints to the parties. I appears to operate as > back-to-back DTLS agent. I know this because both UAs sent SHA-256 > fingerprints but they received SHA-1 fingerprints. This may have worked but > one UA will only accept SHA-256 and it drops the call. > > The documentation does not mention that the ice= option can influence DTLS. > > Regards, Rob > > > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users -- VoIP Embedded, Inc. http://www.voipembedded.com _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users