Hello,
On Tue, Sep 5, 2017 at 4:08 PM, Richard Fuchs wrote:
> That's not currently supported (neither as an offerer nor as an accepter).
> AFAIK the usual mantra is to offer SRTP first and then fallback to RTP when
> a "not supported" (415) is received.
I tried the solution in a free minute toda
On 05.09.17 16:08, Richard Fuchs wrote:
> On 09/05/2017 02:32 AM, Daniel-Constantin Mierla wrote:
>> Hello,
>>
>> wondering if anyone has a quick answer to spare some time searching the
>> web or source code -- is there a way to offer optional SRTP (just SDES
>> is also fine) in SDP with RTPEngin
On 09/05/2017 02:32 AM, Daniel-Constantin Mierla wrote:
Hello,
wondering if anyone has a quick answer to spare some time searching the
web or source code -- is there a way to offer optional SRTP (just SDES
is also fine) in SDP with RTPEngine? The use case is when the target
device is not yet kno
Hello,
wondering if anyone has a quick answer to spare some time searching the
web or source code -- is there a way to offer optional SRTP (just SDES
is also fine) in SDP with RTPEngine? The use case is when the target
device is not yet known to support (or not) SRTP.
There are couple of ways in
