<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">After review with the zoiper team, it looks like this re-invite is trying to force srtp, while using UDP, something which is generally bad security practice, and because of this, something that zoiper does not support. If you wish to create an SRTP call with zoiper you should do so at the start of the call, and using TLS for signaling for security.<div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On May 19, 2018, at 3:12 AM, Andrew Cassidy <<a href="mailto:andrew@cassidywebservices.co.uk" class="">andrew@cassidywebservices.co.uk</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Thanks Michael,<div class=""><br class=""></div><div class="">They're basically being all high and mighty about it. I've suggested that handling the call should be consistent, they either don't reject the reinvite, or they reject the initial invite but have told me this issue is "by design".</div><div class=""><br class=""></div><div class="">We have workarounds as previously mentioned so it's not the end of the world. I might have to reconsider whether I continue to use them in the long term.</div><div class=""><br class=""></div><div class="">Kind regards,<br class=""><br class=""><div class="gmail_quote"><div dir="ltr" class="">On Fri, 18 May 2018, 16:19 Michael Jerris, <<a href="mailto:mike@jerris.com" class="">mike@jerris.com</a>> wrote:<br class=""></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">After review of the sip trace, I’d report that one to the zoiper guys. There is no reason they should reject the call in that case.<br class="">
<br class="">
> On May 17, 2018, at 4:48 PM, Andrew Cassidy <<a href="mailto:andrew@cassidywebservices.co.uk" target="_blank" class="">andrew@cassidywebservices.co.uk</a>> wrote:<br class="">
> <br class="">
> Good afternoon All,<br class="">
> <br class="">
> I have experienced the following issue with Zoiper specifically (I have a support ticket open with them currently) and was wondering if it's something that could/should be fixed FreeSWITCH side.<br class="">
> <br class="">
> If rtp_secure_media is set to optional, and SRTP is disabled on Zoiper, when FreeSWITCH sends the Re-INVITE, it sends crypto lines. Zoiper then replies with a 514 Unsupported Media Type and the timer refresh fails, causing Zoiper to hang up the call.<br class="">
> <br class="">
> My current feeling is that as Zoiper ignored the crypto on the initial INVITE it should be them that then handles the Re-INVITE consistently by also ignoring the crypto lines but I'm not familiar enough with the RFCs to make a judgement.<br class="">
> <br class="">
> The workaround is to either enable SRTP in Zoiper or don't set rtp_secure_media to optional when Zoiper is in use.<br class="">
> <br class="">
> Kind regards,<br class="">
> <br class="">
=</blockquote></div></div></div></blockquote></div><br class=""></div></body></html>