TITRE Adaptive Packet Video Streaming Over IP Networks - LaBRI

TCP/UDP port, our implementation uses TCP protocol because it is more suitable for signaling.
Whenever a new channel is requested, a new TCP, UDP socket is created. In our case, we use RTP
socket based on UDP for media transporting.
As example, the session establishment functionality is obtained through the setup of a DMIF
Signaling channel, and the exchange of DS_SessionSetup messages. This procedure works as
follows in case when DMIF initiates the communication:
1. The target peer is supposed to listen on a well known TCP port number (DMIF_PORT).
2. The originating peer (MPEG-4 DMIF Terminal) creates a TCP socket and connects to the
target peer, using the DMIF_PORT port number and TCP protocol.
3. The target peer accepts the connection: this connection carries the DMIF signaling channel.
4. The originating peer sends a DS_SessionSetupRequest message on the just established
connection.
5. The target peer replies with a DS_SessionSetupConfirm message.
More details on DMIF implementation in Java can be found in [178].
The MPEG-4 terminal is based on JMF 2.1 API (The Java Media Framework API) 1 [179]. JMF
API enables audio, video and other time-based media to be added to Java applications and applets.
This package, can capture, playback, stream and transcode multiple media formats.
The JMF 2.1 reference implementation can receive and transmit many RTP formats such as
(G.711, GSM mono, G.723, MPEG Layer I, II, III, H.261, H.263, etc.). Other formats can be
added via plug-ins.
6.3.3 SIP Terminal
We’ve implemented a simple SIP terminal (see Figure 6-12) which communicates using SIP
specification (INVITE, TRYING, RINGING, ACK, CANCEL, BYE) with other terminals.
1 The JMF 2.0 API was developed by Sun Microsystems, Inc. and IBM. The JMF 1.0 API was
developed by Sun Microsystems, Inc., Silicon Graphics Inc., and Intel Corporation.
153