[BC] Satellite Inet issues

[Dana Puopolo]

It does. UDP is a BROADCAST protocol. It sends out and that's it. Imagine it
like a radio transmitter. The sound goes out. Period.

VOIP audio is simply TWO UDP streams-one in each direction! They are 100%
INDEPENDENT of each other! Somewhere within your VOIP adapter or phone they
are summed into one output. It's too bad that we can't get to those points
within the chipset-imagine how good FOUR WIRE VOIP with no hybrid necessary
would sound on the air.

SIP (Session Initiation Protocol) is used to set up a VOIP connection and yes
it is TCP/IP based-it has to be because otherwise how would it know whether
things are ringing, you answered, etc.? This back and forth is necessary to
initiate the connection only however.

BUT once the connection is made, SIP goes away and the voice connection is
strictly UDP. Think of SIP as the dialer in a central office. The dialer makes
the connection then drops off so someone else can use it. That's why a huge
central office can work well with under 100 dialers in service.

http://en.wikipedia.org/wiki/Session_Initiation_Protocol

-D

From: Jeff Carter <broadcast at hidden-valley.com>

Wait, what?

I thought my VoIP system used UDP coming and going.  I thought the
point of doing this was that we didn't need to account for every
single packet the way TCP demands to number and arrange them, so the
connectionless nature of UDP was ideal.  Also, I thought this was why
it was used for internet audio streaming.

I'm almost positive the VoIP equipment literature said TCP was used to
set up the initial connection, but the actual packetized audio, both
sent and received, traveled via UDP.

Jeff/KD4RBG