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. cheers
signature.asc
Description: OpenPGP digital signature
_______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
