<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>Re: pay attention to the real issue! in </title>
<link>http://www.dslreports.com/forum/r10996215</link>
<description></description>
<language>en</language>
<pubDate>Sun, 29 Nov 2009 03:06:40 EDT</pubDate>
<lastBuildDate>Sun, 29 Nov 2009 03:06:40 EDT</lastBuildDate>

<item>
<title>Re: UDP not TCP</title>
<link>http://www.dslreports.com/forum/remark,11020023</link>
<description><![CDATA[<A HREF="/useremail/u/995615"><b>tkdslr</b></A> :  <BLOCKQUOTE><SMALL>said by  Andromeda451 <A HREF="/useremail/u/986248"><IMG SRC="http://i.dslr.net/bb/profile.gif" ALT="See Profile" BORDER=0 WIDTH=16 HEIGHT=11></A>:</SMALL><HR>Isn't VOIP based on RTP wrapped up in a UDP wrapper? So a TCP ping test may not reflect the situation accurately?<br> <HR></BLOCKQUOTE><br><br>SIP uses both UDP and TCP.. ports 5060 & 5061<br>   It can use either protocol. It will use TCP when UDP fails. <br>see &raquo;<A HREF="http://www.vonage.com/corporate/press_news.php?PR=2003_04_17_0" >www.vonage.com/corporate/press_n&middot;&middot;&middot;_04_17_0</A><br><br>In a route looping scenario, after UDP attempts will fail, and the TCP fall back will also fail (in an identifiable pattern). <br><br>"Ping", generally uses an (ICMP) packet, which uses the IP layer of the TCP&UDP/IP protocol. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,11020023</guid>
<pubDate>Wed, 11 Aug 2004 04:06:37 EDT</pubDate>
</item>

<item>
<title>UDP not TCP</title>
<link>http://www.dslreports.com/forum/remark,11015475</link>
<description><![CDATA[<A HREF="/useremail/u/986248"><b>Andromeda451</b></A> : Isn't VOIP based on RTP wrapped up in a UDP wrapper? So a TCP ping test may not reflect the situation accurately?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,11015475</guid>
<pubDate>Tue, 10 Aug 2004 17:54:46 EDT</pubDate>
</item>

<item>
<title>Re: pay attention to the real issue!</title>
<link>http://www.dslreports.com/forum/remark,10996215</link>
<description><![CDATA[<A HREF="/useremail/u/995615"><b>tkdslr</b></A> :   "If these companies would simply spend as much time examining and improving their networks as they do blaming others for outages, the network would be flawless"<br><br>  I agree.. A quick ping test of the GLBX/Vonage routers indicates a very familiar fault. Vonage/GBLX connections are suffering from Routing loops.  :(<br><br>   Routing loops, where a packet goes bouncing back and forth between two routers until the TTL expires.  When it gets into a loop, that same packet grabs 100x the bandwidth until the TTL expires.  After that everything is normal for  some period of time (30secs to a minute) until the senders TCP protocol times out and issues a retry. <br><br>   If the routing loops get bad enough, then route flapping will also occur. ]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10996215</guid>
<pubDate>Sun, 08 Aug 2004 16:43:50 EDT</pubDate>
</item>

<item>
<title>pay attention to the real issue!</title>
<link>http://www.dslreports.com/forum/remark,10995395</link>
<description><![CDATA[<A HREF="/useremail/u/866319"><b>chrisbmoore</b></A> : If these companies would simply spend as much time examining and improving their networks as they do blaming others for outages, the network would be flawless!!]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10995395</guid>
<pubDate>Sun, 08 Aug 2004 14:40:27 EDT</pubDate>
</item>

</channel>
</rss>
