zoiper srtp crypto mismatch with freeswitch

0 votes

zoiper when using srtp sends the below crypto in SDP

a=crypto:5 AES_256_CM_HMAC_SHA1_80
a=crypto:6 AES_256_CM_HMAC_SHA1_32
a=crypto:3 AES_192_CM_HMAC_SHA1_80
a=crypto:4 AES_192_CM_HMAC_SHA1_32
a=crypto:1 AES_CM_128_HMAC_SHA1_80
a=crypto:2 AES_CM_128_HMAC_SHA1_32

whereas freeswitch prefers


so in this case only the below 2 match and the rest freeswitch says unsupported


the rest dont match because the placement of AES_CM_192 in FS and AES_192_CM in zoiper

may i ask why is this the case that zoiper is sending same crypto name with the text all misplaced making it impossible for FS to match and use?

asked Mar 26 in Android by xbipin (120 points)  

1 Answer

0 votes


We spoke to the FS team and found to be using diffent naming conventions for the negotiations. The 2 RFC´s use different names. Both Zoiper and FS will add a workaround to support both in future versions.

answered Mar 26 by Tsetso.Zdravkov (19,740 points)  
edited Mar 27 by Tsetso.Zdravkov

im on the latest master of FS so still not seeing the patch for this, i see the bug request FS-11052 created for FS but the pull request isnt public so cant manually patch FS to test it coz its not visible

I too am seeing this issue on Zoiper 5.2.19 and Freeswitch 1.6.20. Older Zoiper clients work with this version of Freeswitch, but apparently in Zoiper 5 and FS 1.6 both sides are incomatible with each other.

It doesn't look like Freeswitch will be compatible with Zoiper for a while as they've closed the code based for 2 years.

Ask your questions and receive answers from other members of the Zoiper Community.

Did you check our Help Section?

You are a Zoiper Biz or Premium customer? If so, click HERE to get premium support.
Top users 07/2018
  1. Tsetso.Zdravkov

    19740 Points

  2. Ivan

    18370 Points

  3. Joachim

    11480 Points

  4. Anton

    3910 Points

Latest tweets