<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">If you have clients that are having issues, we should figure out if its our fault or theirs and make sure to get the appropriate bugs filed to get it fixed. This would be an example of a bad use of proxy media mode over actually fixing the issue. Furthermore, I suspect you are wrong that freeswitch not transcoding passing through a vpx stream causes video artifacts. A non transcoding vpx to vpx call would not modify the video stream in the same way that a vpx over proxy mode call would not.<div class=""><br class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 27, 2017, at 1:06 PM, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" class="">s.safarov@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="gmail_msg">Michael I am speaking about compatability of current fs master and sip client, not old freeswith.<br class="gmail_msg">
As example - about two months ago I tested linphone android build with FreeSwith. video artefacts is exits.</div><div dir="ltr" class="gmail_msg">Linphone is updated frequently, other sip clients may be not.</div><div dir="ltr" class="gmail_msg"><br class=""></div><span class="">
</span><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">пн, 27 февр. 2017, 20:54 Michael Jerris <<a href="mailto:mike@jerris.com" class="gmail_msg" target="_blank">mike@jerris.com</a>>:<br class="gmail_msg"></div></div><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">This doesn’t make any sense. The newer vpx should work better, but I’ve seen no bugs at all raised about them not being compatible. If that is the case, what we had previously in 1.5 (an unreleased development build) should not be used anymore.</div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"></div><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Feb 27, 2017, at 12:45 PM, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" class="gmail_msg" target="_blank">s.safarov@gmail.com</a>> wrote:</div><br class="m_-8046914668195174571m_-7217116496603218089Apple-interchange-newline gmail_msg"><div class="gmail_msg"><p dir="ltr" class="gmail_msg">About proxy media. This may be necessary when used video calls using vpx codec.</p><p dir="ltr" class="gmail_msg">Vpx 1.6 used in FreeSwith is not compatible with vpx 1.5<br class="gmail_msg">
Vpx 1.5 may be used in current sip clients <br class="gmail_msg">
</p>
<br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">пн, 27 февр. 2017, 20:30 Michael Jerris <<a href="mailto:mike@jerris.com" class="gmail_msg" target="_blank">mike@jerris.com</a>>:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="gmail_msg">if zrtp passthrough is not working, please open a lira on this issue. It should be corrected.</div><div style="word-wrap:break-word" class="gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div class="gmail_msg"><blockquote type="cite" class="gmail_msg"><div class="gmail_msg">On Feb 27, 2017, at 12:19 PM, Sergey Safarov <<a href="mailto:s.safarov@gmail.com" class="gmail_msg" target="_blank">s.safarov@gmail.com</a>> wrote:</div><br class="gmail_msg m_-8046914668195174571m_-7217116496603218089m_-368135354821914687Apple-interchange-newline"><div class="gmail_msg"><div dir="ltr" class="gmail_msg">Hello Michael </div><div dir="ltr" class="gmail_msg">I confirm that zrtp paththrue is not work as expected and required to enable proxy media from zrtp code match on sip device's </div><span class="gmail_msg">
</span><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">пн, 27 февр. 2017, 19:32 Michael Jerris <<a href="mailto:mike@jerris.com" class="gmail_msg" target="_blank">mike@jerris.com</a>>:<br class="gmail_msg"></div></div><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">what are “custom algorithms”?<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
> On Feb 26, 2017, at 9:01 PM, Richard Chan <<a href="mailto:richard@treeboxsolutions.com" class="gmail_msg" target="_blank">richard@treeboxsolutions.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
> Hi,<br class="gmail_msg">
><br class="gmail_msg">
> The use case is: customer wants the ability to use custom algorithms in their UAs (don't ask!?) without a crypto bridge in the B2BUA. Any suggestions? Originally, I thought proxy media would do the trick - pass media packets without any attempt at interpretation but I noticed RTCP wasn't being activated (I think it was back in the 1.2.x days, I have an ancient 1.2.5 that does activate RTCP). Any suggestions?<br class="gmail_msg">
><br class="gmail_msg">
> ( We haven't looked at ZRTP fully, but validating the session string/PIN seems to make it a non-starter in the customer's use case.)<br class="gmail_msg">
><br class="gmail_msg">
> Richard<br class="gmail_msg"></blockquote></div></div></blockquote></div></div></div></blockquote></div></div></blockquote></div></div></div></div></div></div></blockquote></div></div></blockquote></div><br class=""></div></div></body></html>