[Freeswitch-users] Encryption modes on legs influencing each other

[Johannes Singler]

FS is a B2BUA.  However, the two legs of a regular call seem to influence
each other, e.g.

1. The caller offers an SDES-SRTP-encrypted connection with ICE.
2. FS offers to the callee a simple RTP connection (no SRTP, no ICE, as
configured in the dialplan), callee answers respectively.
3. FS answers caller, but without with neither "a:crypto" entries nor ICE
candidates.
4. Why is that?  Shouldn't it answer SDES-SRTP with ICE to the original
caller, respecting the original caller's offer?

When doing WebRTC from the caller (DTLS-SRTP with ICE), this actually works
fine (callee unchanged).

So what's the general scheme for choosing encryption on either side?

Related to that:
Can you enable ICE without completely enabling WebRTC (media_webrtc=true)
from the dialplan? That would help maybe...

-- 
Johannes Singler
Software Engineer

Qnective
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20151005/fbd5e8e3/attachment.html