RST and others..
IMHO, the relationships defined in IP Telephony architectures like DCS
and DOSA around SIP and RTP streams are identical to the relationships
between an HTTP server that guides us through selectable MP3 streams.
In fact, SIP could be what allows MP3 Streaming to compete on a feature-
for-feature basis with RealAudio (ie. instream service selection or
So, given that this means that SIP has applications beyond simple IP
Telephony and extending into broadcasting, media streaming, and video-
conferencing, SIP servers will be the in the 00's what the web server
was in the 90's.
This leads us to Apache.org.
So am I wrong in thinking that Apache, as an HTTP server, lends itself
particularly well to being a SIP Call Agent? SIP and HTTP are identical
in that they are stateless, can pass MIME types, and do not sustain
connections. SIP has provision for a CGI architecture, as well.
Does anyone think I'm crazy, after reading the IETF doc, to figure that
a port of Apache code to SIP is simply a case of adding new message
types, modifying port numbers, and broadening CGI handling?
Making SIP Call Agents free from Apache.org would really open up the
world of call control to the masses, and would steal the bread and
butter of companies like Lucent, Telcordia, and Nortel right from their
Need some opinions..
Content-Type: text/x-vcard; charset=us-ascii;
Content-Description: Card for Ian Andrew Bell
org:Cisco Systems - Service Provider LOB;Telephony Internet Services Unit
adr;quoted-printable:version:2.1;;Building SJ-6/4=0D=0A375 East Tasman Drive ;San Jose;CA;95134;USA
note;quoted-printable:AOL Instant Messenger ID: ibell SJ=0D=0A=0D=0A
fn:Ian Andrew Bell