Hi All<div><br></div><div>Please ignore, I had misconfigured something in the dialplan!</div><div><br></div><div>Thanks.<br><br><div class="gmail_quote">On Tue, Jul 3, 2012 at 1:03 PM, Ben <span dir="ltr"><<a href="mailto:ben122uk@gmail.com" target="_blank">ben122uk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Freeswitch community!<div><br></div><div>Could someone advise on how you have the a-leg as a non-ZRTP client, and the b-leg as a ZRTP client, with trusted main-in-the-middle?</div>
<div><br></div><div>I have set up trusted man-in-the-middle with the server, which works well when making an outbound call from the ZRTP client to the standard SIP client. The INVITE from the ZRTP client includes the zrtp hash in the SDP info, which I'm presuming highlights to freeswitch that the call will be using ZRTP for this leg. The Freeswitch then decrypts the ZRTP ready for the b-leg. Everyone's happy.</div>
<div><br></div><div>However, when going the other way, the INVITE from the non-ZRTP device does not include zrtp hash. So the INVITE passed to the ZRTP client does not include a ZRTP hash, which then causes the ZRTP client to fail. I have tried getting around this by adding the following in the dialplan - </div>
<div><br></div><div><div><action application="set" data="zrtp_secure_media=true"/></div></div><div><br></div><div>But the freeswitch doesn't create the zrtp hash in the INVITE.</div><div><br>
</div><div>Is there something I can do in Freeswitch to say "all calls to this phone must use ZRTP (hash), whether the original INVITE uses ZRTP or not"?</div><div><br></div><div>Thanks in advance for the help!</div>
</blockquote></div><br></div>