<br><br><div><span class="gmail_quote">2007/7/21, yannick <<a href="mailto:sevmek@free.fr">sevmek@free.fr</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>Well, as far as I know about this, this is technically a bad choice for<br>VoIP as it use TCP for transmitting datas. Theoretically speaking,<br>unlike UDP, the TCP module at the far end sends back an acknowledgement<br>
for packets which have been successfully received; a timer at the<br>sending TCP will cause a timeout if an acknowledgement is not received<br>within a reasonable round-trip time (or RTT), and the (presumably) lost<br>data will then be re-transmitted.
<br><br>Thus this will increase delay in the transmission as each packet will<br>wait for the acknowledgement. What will happen if one packet is lost ?<br>Does wengo workaround this in some way ?<br><br>I wonder how well the http tunnel works for wengo.
</blockquote><div><br>It works Well , and you can even call any sip adress since wengo 2.0, I understand what you meant about tcp , but microsoft use sip messaging over TCP and it works well for exemple. the http tunnel solution is still the only one for http proxy. it's also what google use for google talk. the point is that wengo http tunnel serve ris not open source I think.
<br></div><br></div><br clear="all"><br>-- <br>%<------------------------------------------------------->%<br>Michel memeteau<br>VOIP | Visio: <a href="mailto:sip:freechelmi@gizmoproject.com">sip:freechelmi@gizmoproject.com
</a><br>Fixe : 0491886375 !!! APARTIR du 15/09/2007 -> 0811956494<br>Mobile : 0624808051<br>jabber/GoogleTalk : <a href="mailto:freechelmi@jabber.fr">freechelmi@jabber.fr</a>