<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16640" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY
style="WORD-WRAP: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space"
bgColor=#ffffff>
<DIV><FONT face=Arial size=2>> The a=encryption:optional tag is a Microsoft
extension held over(Snom has<BR>> removed it in recent beta builds I
have). We do not support it and will not. <BR>> Grandstream uses
RTP/SAVP, Snom will be doing RTP/SAVP in 7.1.33 (in beta), <BR>> Polycom does
the dual m= line for RTP/SAVP and RTP/AVP. Offering crypto in an <BR>>
RTP/AVP is wrong please refer to RFC3711 where it clearly states "The RTP
<BR>> specification establishes a registry of profile names for use by
higher-level <BR>> control protocols, such as the Session Description
Protocol (SDP), to refer to <BR>> transport methods. This profile registers
the name "RTP/SAVP"."</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>I understand. It is clear for me.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>> Chris,Heiko and I have had a few exchanges in
email...<BR>> He's a verynice guy very preceptive to the changes required to
support <BR>> this properly. He said he'll be trying out the two
m-linemethod soon.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Great news :) </FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=Arial size=2>Chris <BR></FONT></DIV></BODY></HTML>