FreeSWITCH error handling of UNENCRYPTED_SRTCP parameter
We are working with an Avaya customer system that uses the UNENCRYPTED_SRTCP parameter from RFC 4568.
https://www.rfc-editor.org/rfc/rfc4568.html#section-6.3.2. The customer is not able to remove this parameter from their end and so it is appended to the end of the crypto suite used during SDP negotiation with our FreeSWITCH. We are running into some issues parsing UNENCRYPTED_SRTCP out. So, the request comes into Freeswitch looking like this in the SDP negotiation from the Avaya system.
a=crypto:5 AES_256_CM_HMAC_SHA1_80
inline:caaf9AoJBPzGFCdvXn/oOFOnZ3qRI6xIma6Gfsadgahahryhrsehshsf== UNENCRYPTED_SRTCP
We then see the following error in the Freeswitch logs.
............. 98.87% [ERR] switch_core_media.c:1445
Error! Parsing near UNENCRYPTED_SRTCP
............. 98.87% [INFO] switch_rtp.c:4369 Activating audio
Secure RTP SEND
............. 98.87% [INFO] switch_rtp.c:4347
Activating audio Secure RTP RECV
............. 98.87% [DEBUG] switch_core_sqldb.c:2778
Secure Type: srtp:sdes:AES_CM_256_HMAC_SHA1_80
............. 98.87% [DEBUG] switch_core_sqldb.c:2778
Secure Type: srtp:sdes:AES_CM_256_HMAC_SHA1_80
Media is established but the quality is poor with chop and stutter on an otherwise well working FreeSWITCH implementation. The issue happens when this UNENCRYPTED_SRTCP parameter is passed in like it is. This leads us to believe there is some kind of issue honoring the UNENCRYPTED_SRTCP parameter when it is coming into FreeSWITCH the way it is.
Does anyone have any ideas or experience around how to handle this type of UNENCRYPTED_SRTCP parameter that is being appended the way it is? It seems that this might be an interop issue between systems and RFC adherence/implementation that we are trying to overcome on the FreeSWITCH side of things if possible.
We see a single similar 10 year old question with no response or resolve regarding this UNENCRYPTED_SRTCP parameter.
https://lists.freeswitch.org/pipermail/freeswitch-users/2015-May/112910.htmlAny guidance or ideas are appreciated from the community and or FreeSWITCH development team.
Thank you