crypto in RTP/AVP is invalid per the spec. You are required to send two rtp profiles one with RTP/AVP or RTP/SAVP To get around this in your broken device you can set the variable sip_allow_crypto_in_avp or set profile param NDLB-allow-crypto-in-avp -- Brian West brian@freeswitch.org FreeSWITCH Solutions, LLC PO BOX PO BOX 2531 Brookfield, WI 53008-2531 Twitter: @FreeSWITCH_Wire T: +1.918.420.9266 | F: +1.918.420.9267 | M: +1.918.424.WEST iNUM: +883 5100 1420 9266 ISN: 410*543 On Feb 22, 2013, at 10:08 AM, Ken Rice <krice@freeswitch.org> wrote:
FreeSWITCH Support SIP/TLS, SRTP and ZRTP, the error message you are refering to below is where someone has improperly implemented SRTP and is sending the crypto headers in the wrong spots. See the Wiki for setting up secure calling.
Also please note, if you are going to use SRTP, you _must_ use SIP/TLS as the keys for SRTP are passed in the SDP of the SIP messaging. You can use ZRTP without using SIP/TLS as the key exchange for ZRTP happens as a DH exchange in the ZRTP stream, but if you want to protect the contents of the SIP messaging you’ll still want to use SIP/TLS.
K