Following Mike's advise, I've compiled the latest FS version 1.6.7 on a Raspi-2 device with the zrtp libs and setup:
./configure --enable-zrtp.
I've enabled zrtp in vars.XML and in dialplan and tried to make a regular zrtp call with several zrtp clients but failed to make it happen.

The fs_CLI log shows the zrtp hash and there is a statement that zrtp is detected BUT no zrtp session is starting with HELLO or anything else. It looks like the ZRTP module is not active.
>From fs_CLI I get zrtp_enabled=false.

I've also recompiled with ver 1.7 with same results.

When I'm recompiling back with ver 1.4 then zrtp is working.

Is there any issue with fs 1.6.7 on raspi-2 using zrtp?

Regards

Assaf

On Mar 28, 2016, at 18:13, Michael Jerris <mike@jerris.com> wrote:
did you try and see if this is the case with a current release instead of the old one?

On Mar 28, 2016, at 8:14 AM, Assaf Dahary <adahary@gmail.com> wrote:

Hi,

 

I would like to use FS (multiple) as a ZRTP client register on a the main FS.

 

I have already managed to setup a Gateway with user/pass on the FS client and register it on the main FS for regular incoming/outgoing calls (without ZRTP).

 

To enable ZRTP calls I setup the FS client/main as follow:

None ZRTP SIP phone -> FS client -> NAT Internet -> FS main -> CSipSimple ZRTP enabled).

 

FS Client (ver 1.4) :

ZRTP enabled globally in VARS and in dialplan.

Media proxy disabled on both internal and external profiles and in dialplan.

 

FS Main (ver 1.4):

Media proxy enabled – including late negotiation.

 

I forced the FS client and the CSipSimple to use only PCMU codec to avoid transcoding.

 

The problem is that on a call from the SIP phone via the FS client there are always CRC errors on the ZRTP log.

Only if the FS main is set to disable media proxy then there are no CRC errors – but then it becomes a MITM with incompatible SASs.

 

From reading other posts about FS and ZRTP CRC errors I assume that it happens because the FS client is not creating a zrtp hash in the invite SDP.

 

So my question is how to make the FS client to generate the zrtp hash in the invite SDP to act as real ZRTP enabled client? 

I've already tried to set the FS client internal/external/dialplan with several zrtp configs with no success.

 

I would appreciate any tip to resolve this issue.

 

Regards

 

Assaf  

 

 

The client FS 

 

_________________________________________________________________________
Professional FreeSWITCH Consulting Services: 
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org



Professional FreeSWITCH Consulting Services:
consulting@freeswitch.org
http://www.freeswitchsolutions.com

Official FreeSWITCH Sites
http://www.freeswitch.org
http://confluence.freeswitch.org
http://www.cluecon.com

FreeSWITCH-users mailing list
FreeSWITCH-users@lists.freeswitch.org
http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
http://www.freeswitch.org