Naturally, either way is stupid.<br><br>The whole idea of putting the transport in a uri param is equally stupid to using 2 different protocol names but since SIP is the descendant of http it they decided to stick with the stupidity of http/https and have sip/sips which is almost as if it was designed to break all software trying to keep up with url syntax.<br>
<br>If they are going to insist on using text params you&#39;d think something like transport=foo;security=tls would be even *more* flexable in case alternate methods to encrypt crop up.<br><br>This is, of course, the first step into a lengthy 12 hour discussion on how stupid SIP and url/text based<br>
protocols are.<br><br>I dare someone to crank up the pcap on a box doing SIP presence for 20 phones and &quot;read&quot;<br>the 1200 byte messages with all kinds of hyeroglyphic url syntax and embedded xml payloads and write<br>
up a paper on how much &quot;sense&quot; it makes to have it be &quot;readable&quot;.<br><br>PS<br><br>supposedly sofia can support sctp,<br>someone should try it.<br><br><br><br><div class="gmail_quote">On Mon, Dec 1, 2008 at 9:43 PM, Kristian Kielhofner <span dir="ltr">&lt;<a href="mailto:kkielhofner@star2star.com">kkielhofner@star2star.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On 12/1/08, Thomas Troy &lt;<a href="mailto:ttroy50@gmail.com">ttroy50@gmail.com</a>&gt; wrote:<br>

..snip..<br>
&gt;<br>
&gt; Out of interest do you have any links to anywhere this is discussed in terms<br>
&gt; of general sip implementations?<br>
&gt;<br>
<br>
Uh oh, here we go again...<br>
<br>
<a href="http://www.iana.org/assignments/sip-parameters" target="_blank">http://www.iana.org/assignments/sip-parameters</a><br>
<a href="http://tools.ietf.org/html/rfc3969" target="_blank">http://tools.ietf.org/html/rfc3969</a><br>
<br>
<a href="https://lists.cs.columbia.edu/pipermail/sip-implementors/2005-August/010047.html" target="_blank">https://lists.cs.columbia.edu/pipermail/sip-implementors/2005-August/010047.html</a><br>
<br>
Implementation wise, most devices tend to use transport=tls:<br>
<br>
SIPFoundry - From what I&#39;ve seen<br>
Snom<br>
SERs<br>
Asterisk (If you are using TLS)<br>
Cisco - I *believe* you can use either a SIPS URI or the transport=tls<br>
parameter for various SIP targets<br>
<br>
 &nbsp;As the RFC (basically) states (RFC3261, section 12.1.x),<br>
transport=tls was deprecated in RFC 3261 because you should also be<br>
able to do TLS over SCTP (RFC3436), which makes transport=tls a bit<br>
ambiguous. sips:user@domain;transport=tcp or<br>
sips:user@domain;transport=sctp is a bit more flexible.<br>
<br>
 &nbsp;I don&#39;t know if I&#39;ve ever seen anything default to SIPS URIs. &nbsp;I<br>
also don&#39;t think I&#39;ve ever specifically tried using them. &nbsp;However, my<br>
experience with TLS is admittedly somewhat limited so this shouldn&#39;t<br>
be taken as gospel. &nbsp;As you can see from the discussions on<br>
sip-implementors, this gets interesting when different devices are<br>
traversing a proxy using different URI schemes...<br>
<br>
 &nbsp;However, I suspect this won&#39;t become an issue until most SIP<br>
implementations support SCTP. &nbsp;That should be exciting! ;)<br>
<br>
<br>
--<br>
Kristian Kielhofner<br>
<a href="http://blog.krisk.org" target="_blank">http://blog.krisk.org</a><br>
<a href="http://www.submityoursip.com" target="_blank">http://www.submityoursip.com</a><br>
<a href="http://www.astlinux.org" target="_blank">http://www.astlinux.org</a><br>
<a href="http://www.star2star.com" target="_blank">http://www.star2star.com</a><br>
<br>
_______________________________________________<br>
Freeswitch-users mailing list<br>
<a href="mailto:Freeswitch-users@lists.freeswitch.org">Freeswitch-users@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-users</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-users" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-users</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
<br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>