Internet Multimedia Architecture

Jim Chou and Thinh Nguyen

February 12, 2002

 Outline

Overview
Multimedia Applications
Signaling Protocols (SIP/SDP, SAP, H.323,
MGCP)
Streaming Protocols (RTP, RTSP, HTTP, etc.)
QoS (RSVP, Diff-Serv, IntServ)
Conclusions
 Multimedia protocol stack
Signaling Quality of Service Media Transport

Application daemon
MGCP/Megaco
Reservation Measurement
H.261, MPEG
H.323 SDP RTSP RSVP RTCP
SIP RTP

TCP UDP
network

IPv4, IPv6

kernel
link

PPP AAL3/4 AAL5 PPP

physical

Sonet ATM Ethernet V.34

 Multimedia applications

Audio
– Speech (CELP – type codecs)
– Music (MP3, WAV, WMA, Real)

Video (MPEG –1, 2, 4)

Streaming done using HTTP/TCP (MP3), or

RTP/UDP (Video).
 Multimedia applications (cont.)
Wireless network

Gateway
9.6 kbps

Media server
1 Mbps PSTN

28 kbps
 Signaling protocols

VoIP predominantly uses two:

– SIP/SDP
– H.323
 Session initiation protocol (SIP)

Developed in mmusic Group in IETF

– Proposed standard RFC2543, February 1999
– Work began 1995
– Part of Internet Multimedia Conferencing Suite (MBONE)
Main Functions
– Invite users to sessions
• Find the user’s current location, match with their capabilities and
preferences in order to deliver invitation
• Carry opaque session descriptions
– Modification of sessions
– Termination of sessions
 SIP overview
TRIP
Address lookup PSTN gateway lookup
LDAP

SIP SIP
SDP SDP
May Sets up
Next-Hop
trigger

DNS RSVP RSVP

RTP RTP
UDP UDP
 SIP components

User Agent Client (UAC)

– End systems
– Send SIP requests

User Agent Server (UAS)

– Listens for call requests
– Prompts user or executes program to determine response

User Agent
– UAC plus UAS
 SIP components (cont.)

Redirect Server
– Network server - redirects users to try other server

Proxy Server
– Network server - a proxy request to another server can “fork”
request to multiple servers, creating a search tree

Registrar
– Receives registrations regarding current user locations
 SIP architecture
Request
Response
Media columbia.edu
SIP Redirect
Server Location Service
2
berkeley.edu 3
sip.com
5
sip:alice@eecs.berkeley.edu 4
6
1
7 sales.sip.com
11
12 10
SIP Proxy
13 SIP Proxy
8
SIP Client 14 9
bob@mypc.sales.sip.com
SIP Client
(User Agent Server)
 Sip architecture (cont.)
SIP state-less proxies (near core of network)
– used for re-direction

SIP state-ful proxies (near periphery of network)

– Keeps track of state of call
– Useful for billing/logging, authentication

Routing
– Registration database, external database
– TRIP
 SIP architecture (cont.)
DB
On Startup, SIP UA Sends
REGISTER to Registrar
Registrar
Registration Data Provides SQL/LDAP/?

Addresses to Reach User

Registration Database Forms a Proxy Farm

Dynamic Routing Database of
Users
INVITE
Centralized Store is Desired for
Scalability
 SIP architecture (cont.)
SIP INVITE Can Contain Phone Numbers
– sip:17325551212@domain.com
– tel:17325551212

Do Not Correspond to Users on IP Network, but PSTN sip:19735551212@

Terminals tel:19735551212 longdistance.com

Call Must Be Routed to Gateway

1-732 regional.com

Gateways Often Arranged

Through Peering 1 longdistance.com

Which One to Use Based on Prefixes

international.com
(Domestic = gw1, Europe = gw2)

Route Table is Mapping From Prefixes to Next Hop IP

address/port/transport
Plus URL Rewrite Rules
 SIP architecture (cont.)
Gateways

Inter-domain Protocol for

Gateway Route Exchange
– Completed February 2000
Location
TRIP Supports Various Models
Server
ISP B
– Bilateral agreements TRIP
– Centralized settlements provider
End
Users

ISP A
Front
End
 SIP call flow example
USER A PROXY PROXY USER B

INVITE
407 Proxy Authenticate
ACK

INVITE
INVITE
100 Trying INVITE
100 Trying
180 Ringing
180 Ringing
180 Ringing 200 OK
200 OK
200 OK

ACK
ACK
ACK
BOTH WAY RTP
BYE
BYE
BYE
200 OK 200 OK
200 OK
 Session Description Protocol (SDP)

Used to specify client capabilities

Example (client can support MPEG-1 video

codec, and MP3 codecs)
 Session Anouncement Protocol
(SAP)
Originated around same time as SIP

Used to announce multimedia sessions

– Announcement goes to users in a multicast group
– Announcements can contain start time of session,
duration of session, etc.
Multimedia Gateway Control Protocol
(MGCP)
Decompose gateway into a controlling signalling
component and a controlled media component.

Can be used in phones or gateways in

conjunction with SIP
 H.323

May 1995 - H.323 work started

June 1996 - Decided by ITU-T

Designed for exchanging multimedia over IP

networks (4 versions of H.323)
 H.323 Components

Terminals
Gatekeepers
Gateways (H.323 to H.320/H.324/POTS)
MCUs
– Multipoint Controller (MC)
– Multipoint Processor (MP)
 H.323 Gatekeeper

Address Translation
– H.323 Alias to transport (IP) address based on terminal
registration
– “email-like” names possible
– “phone number like” names possible
Admission control
– Permission to complete call
– Can apply bandwidth limits
– Method to control LAN traffic
 H.323 Gatekeeper (cont.)

Management of gateway
– H.320, H.324, POTS, etc.
Call Signaling
– May route calls in order to provide supplementary
services or to provide Multipoint Controller
functionality
Call Management/Reporting/Logging
 H.323 Gateway

Provide world wide connectivity and

interoperability from LAN
– H.320, H.324, regular POTS telephones
Map Call Signaling (Q.931 to H.225.0)
Map Control (H.242/H.243 to H.245)
Media Mapping (FEC, multiplex, rate matching,
audio transcoding)
 H.323 MCU

Media Distribution
– Unicast - send media to one terminal (centralized in
MP; traditional model)
– Multicast - send to each receiver directly
– Hybrid - some of each
Manage Ad Hoc multipoint calls
– Join, invite, control of conference modes
Multiprotocol via Gateways
 H.323 protocol stack
Control Data Audio Video A/V Cntl Control

Gate-
G.7xx H.26x keeper
RTCP Reg,
H.225.0 H.245 T.120
Adm,
Status
RTP
(RAS)

TCP UDP

IP
 H.323 protocol stack (cont.)

H.323 - System Document

H.225.0 - Call Signaling, Packetization
– Gatekeeper Registration, Admission, and Status
H.245 - Control (also used in H.324, H.310)
T.120 - Data and Conference Control
 H.323 example

A Call Setup Example

a point to point call

One Gatekeeper using the Direct Call Model

 H.323 example (cont.)
GK

(2a) GK resolves “Bob”

to IP address through H.323
(1) ARQ registration or external
Can I call name service
“Bob”? (e.g. DNS, ULS, etc..)
(2b) Admission Policy
Applied
(3) ACF PictureTel

Yes, use this

IP Address
Bob
Bill
 H.323 example (cont.)
GK

(5) ARQ
May I answer?
(6) ACF
Yes
(4) SETUP (Create)

PictureTel

(7) ALERTING
(8) CONNECT (User answers)
Bob
Bill
 H.323 example (cont.)

PictureTel

(9) H.245 connection established

- Capability Exchange Bob

Bill
- Open Logical
Channels (audio, video)