[SR-Users] No secure attributes from rtpengine in SRTP/RTP bridge mode

Richard Fuchs rfuchs at sipwise.com
Sun Apr 27 00:42:55 CEST 2014

On 04/26/14 18:24, Alexey Rybalko wrote:
> "Failed to set remote answer sdp: Called with a SDP without crypto
> enabled" (Chrome)
> RTPEngine log is attached.

Please try again with ICE=force instead of force_relay, or (more
conservatively) ICE=remove in the offer and ICE=force in the answer. You
will probably also need the option "rtcp-mux-demux" in the offer, as
your non-RTC endpoint doesn't support rtcp-mux and Chrome isn't likely
to be happy with its rtcp-mux offer being declined.

To answer your previous question: DTLS-SRTP does take priority over
SDES, and what you should see in the outgoing answer is only the setup
and fingerprint attributes, but no crypto attributes.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 880 bytes
Desc: OpenPGP digital signature
URL: <http://lists.sip-router.org/pipermail/sr-users/attachments/20140426/f6656c99/attachment.pgp>

More information about the sr-users mailing list