Hello. I've faced an issue when using rtpengine module with tls transport. When UA originates a call it pointed set of crypto parameters in SDP, like that:
a=crypto:1 AES_CM_256_HMAC_SHA1_80 inline:PZASLY5HoxVo6Ljz2niwxqNJ+3A2mW71SgfL75cRFtShKQIvcKVF2Y39zGd1fQ== a=crypto:2 AES_CM_256_HMAC_SHA1_32 inline:LRjGKIj8wvfxDP68+5XOEmlvO2ufqxDkhJ3hUQRWzjFulFr2kBztgSjrPSSACw== a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:Nup7cVUaHGb+oQPf8gg1wDmjVJOZ5K+HZdhyovzz a=crypto:4 AES_CM_128_HMAC_SHA1_32 inline:rjLdKaMyQ7+YQWCcIFKkVRLd+GZxkUogGK/4i1L0 But when Opensips relays original message to UA2, rtpengine removes all the crypto suite strings except the first one. Unfortunately, there is no way to configure client's behaivior to send certain crypto suite. In other side, UA2, that is PBX, doesn't support all crypto suites except AES_CM_128_HMAC_SHA1_80 Is there a way to configure Opensips/rtpengine to choose specific crypto string or to leave crypto set without changing at all? Best Regards, Sergey Pysanko. [image: Mailtrack] <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&;> Sender notified by Mailtrack <https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&;> 01/14/22, 05:28:49 PM
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
