old-www/HOWTO/VoIP-HOWTO-9.html

46 lines
1.9 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META NAME="GENERATOR" CONTENT="SGML-Tools 1.0.9">
<TITLE>VoIP Howto: Bandwidth consideration</TITLE>
<LINK HREF="VoIP-HOWTO-10.html" REL=next>
<LINK HREF="VoIP-HOWTO-8.html" REL=previous>
<LINK HREF="VoIP-HOWTO.html#toc9" REL=contents>
</HEAD>
<BODY>
<A HREF="VoIP-HOWTO-10.html">Next</A>
<A HREF="VoIP-HOWTO-8.html">Previous</A>
<A HREF="VoIP-HOWTO.html#toc9">Contents</A>
<HR>
<H2><A NAME="s9">9. Bandwidth consideration</A></H2>
<P>From all we said before we noticed that we still have not solved
problems about bandwidth, how to create a real time streaming of
data.
<P>We know we couldn't find a solution unless we enable a right
real-time manager protocol in each router we cross, so what do we
can do?
<P>First we try to use a very (as more as possible) high rate compression
algorithms (like LPC10 which only consumes a 2.5 kbps bandwidth,
about 313 bytes/s).
<P>Then we starts classify our packets, in TOS field, with the most
high priority level, so every router help us having urgently.
<P>Important: all that is not sufficient to guarantee our conversation
would always be ok, but without an great infrastructure managing
shaping, bandwidth reservation and so on, it is not possible to do
it, TCP/IP is not a real time protocol.
<P>A possible solution could be starts with little WAN at guaranteed
bandwidth and get larger step by step.
<P>We finally have to notice a thing: also the so called guaranteed
services like PSTN line could not manage all clients they have: for
example a GSM call is not able to manage more that some hundred or
some thousand of clients.
<P>Anyway for a starting service, limited to few users, VoIP can
be a valid alternative to classic PSTN service.
<HR>
<A HREF="VoIP-HOWTO-10.html">Next</A>
<A HREF="VoIP-HOWTO-8.html">Previous</A>
<A HREF="VoIP-HOWTO.html#toc9">Contents</A>
</BODY>
</HTML>