Chapter 7

Multimedia Networking

A note on the use of these ppt slides:

We’re making these slides freely available to all (faculty, students, readers). Computer
They’re in PowerPoint form so you see the animations; and can add, modify,
and delete slides (including this one) and slide content to suit your needs. Networking: A Top
They obviously represent a lot of work on our part. In return for use, we only
ask the following: Down Approach
v If you use these slides (e.g., in a class) that you mention their source
(after all, we’d like people to use our book!)
6th edition
v If you post any slides on a www site, that you note that they are adapted Jim Kurose, Keith Ross
from (or perhaps identical to) our slides, and note our copyright of this Addison-Wesley
material.
March 2012
Thanks and enjoy! JFK/KWR

All material copyright 1996-2012

J.F Kurose and K.W. Ross, All Rights Reserved

Multmedia Networking 7-1

Multimedia networking: outline
7.1 multimedia networking applications
7.2 streaming stored video
7.3 voice-over-IP
7.4 protocols for real-time conversational
applications
7.5 network support for multimedia

Multmedia Networking 7-2

Multimedia networking: outline
7.1 multimedia networking applications
7.2 streaming stored video
7.3 voice-over-IP
7.4 protocols for real-time conversational
applications
7.5 network support for multimedia

Multmedia Networking 7-3

Multimedia: audio
v analog audio signal
sampled at constant rate
quantization quantized
§ telephone: 8,000 error value of
samples/sec analog value

audio signal amplitude

§ CD music: 44,100 analog
signal
samples/sec
v each sample quantized, i.e.,
rounded
§ e.g., 28=256 possible time
quantized values
sampling rate
§ each quantized value (N sample/sec)

represented by bits,
e.g., 8 bits for 256
values
Multmedia Networking 7-4
Multimedia: audio
v example: 8,000 samples/sec,
256 quantized values: 64,000
bps quantization
error
quantized
value of
v receiver converts bits back analog value

audio signal amplitude

to analog signal: analog

§ some quality reduction signal

example rates
v CD: 1.411 Mbps time

v MP3: 96, 128, 160 kbps sampling rate

(N sample/sec)
v Internet telephony: 5.3 kbps
and up

Multmedia Networking 7-5

Multimedia: video
spatial coding example: instead
of sending N values of same
color (all purple), send only two
values: color value (purple) and
number of repeated values (N)
v video: sequence of images
displayed at constant rate ……………………...…
……………………...…
§ e.g. 24 images/sec
v digital image: array of pixels
§ each pixel represented
by bits
v coding: use redundancy
within and between images frame i
to decrease # bits used to
encode image
§ spatial (within image) temporal coding example:
instead of sending
§ temporal (from one complete frame at i+1,
image to next) send only differences from
frame i

frame i+1
Multmedia Networking 7-6
 Multimedia: video
spatial coding example: instead
of sending N values of same
color (all purple), send only two
values: color value (purple) and
number of repeated values (N)
v CBR: (constant bit rate): video
encoding rate fixed ……………………...…
……………………...…
v VBR: (variable bit rate): video
encoding rate changes as
amount of spatial, temporal
coding changes
v examples:
§ MPEG 1 (CD-ROM) 1.5
Mbps frame i
§ MPEG2 (DVD) 3-6 Mbps
§ MPEG4 (often used in temporal coding example:
Internet, < 1 Mbps) instead of sending
complete frame at i+1,
send only differences from
frame i

frame i+1
Multmedia Networking 7-7
Multimedia networking: 3 application types

v streaming, stored audio, video

§ streaming: can begin playout before downloading entire
file
§ stored (at server): can transmit faster than audio/video
will be rendered (implies storing/buffering at client)
§ e.g., YouTube, Netflix, Hulu
v conversational voice/video over IP
§ interactive nature of human-to-human conversation
limits delay tolerance
§ e.g., Skype
v streaming live audio, video
§ e.g., live sporting event (futbol)

Multmedia Networking 7-8

Multimedia networking: outline
7.1 multimedia networking applications
7.2 streaming stored video
7.3 voice-over-IP
7.4 protocols for real-time conversational
applications
7.5 network support for multimedia

Multmedia Networking 7-9

Streaming stored video:
Cumulative data

2. video
sent
1. video 3. video received,
recorded network delay played out at client
(e.g., 30 (fixed in this (30 frames/sec) time
frames/sec) example)

streaming: at this time, client

playing out early part of video,
while server still sending later
part of video

Multmedia Networking 7-10

Streaming stored video: challenges
v continuous playout constraint: once client playout
begins, playback must match original timing
§ … but network delays are variable (jitter), so
will need client-side buffer to match playout
requirements
v other challenges:
§ client interactivity: pause, fast-forward,
rewind, jump through video
§ video packets may be lost, retransmitted

Multmedia Networking 7-11

 Streaming stored video: revisted
constant bit
rate video client video constant bit
Cumulative data

transmission reception rate video

playout at client
variable
network

buffered
video
delay

client playout time

delay

v client-side buffering and playout delay: compensate

for network-added delay, delay jitter

Multmedia Networking 7-12

 Client-side buffering, playout
buffer fill level,
Q(t)
variable fill playout rate,
rate, x(t) e.g., CBR r

client application
video server buffer, size B

client

Multmedia Networking 7-13

 Client-side buffering, playout
buffer fill level,
Q(t)
variable fill playout rate,
rate, x(t) e.g., CBR r

client application
video server buffer, size B

client

1. Initial fill of buffer until playout begins at tp

2. playout begins at tp,
3. buffer fill level varies over time as fill rate x(t) varies
and playout rate r is constant
Multmedia Networking 7-14
 Client-side buffering, playout
buffer fill level,
Q(t)
variable fill playout rate,
rate, x(t) e.g., CBR r

client application
video server buffer, size B

playout buffering: average fill rate (x), playout rate (r):

v x < r: buffer eventually empties (causing freezing of video
playout until buffer again fills)
v x > r: buffer will not empty, provided initial playout delay is
large enough to absorb variability in x(t)
§ initial playout delay tradeoff: buffer starvation less likely
with larger delay, but larger delay until user begins
watching
Multmedia Networking 7-15
Streaming multimedia: UDP
v server sends at rate appropriate for client
§ often: send rate = encoding rate = constant
rate
§ transmission rate can be oblivious to
congestion levels
v short playout delay (2-5 seconds) to remove
network jitter
v error recovery: application-level, timeipermitting
v RTP [RFC 2326]: multimedia payload types
v UDP may not go through firewalls

Multmedia Networking 7-16

Streaming multimedia: HTTP
v multimedia file retrieved via HTTP GET
v send at maximum possible rate under TCP

variable
rate, x(t)

video TCP send TCP receive application

file buffer buffer playout buffer
server client

v fill rate fluctuates due to TCP congestion control,

retransmissions (in-order delivery)
v larger playout delay: smooth TCP delivery rate
v HTTP/TCP passes more easily through firewalls
Multmedia Networking 7-17
Streaming multimedia: DASH
v DASH: Dynamic, Adaptive Streaming over HTTP
v server:
§ divides video file into multiple chunks
§ each chunk stored, encoded at different rates
§ manifest file: provides URLs for different chunks
v client:
§ periodically measures server-to-client bandwidth
§ consulting manifest, requests one chunk at a time
• chooses maximum coding rate sustainable given
current bandwidth
• can choose different coding rates at different points
in time (depending on available bandwidth at time)
Multmedia Networking 7-18
Streaming multimedia: DASH
v DASH: Dynamic, Adaptive Streaming over HTTP
v “intelligence” at client: client determines
§ when to request chunk (so that buffer starvation, or
overflow does not occur)
§ what encoding rate to request (higher quality when
more bandwidth available)
§ where to request chunk (can request from URL server
that is “close” to client or has high available
bandwidth)

Multmedia Networking 7-19

Content distribution networks
v challenge: how to stream content (selected from
millions of videos) to hundreds of thousands of
simultaneous users?

v option 1: single, large “mega-server”

§ single point of failure
§ point of network congestion
§ long path to distant clients
§ multiple copies of video sent over outgoing link
….quite simply: this solution doesn’t scale

Multmedia Networking 7-20

Content distribution networks
v challenge: how to stream content (selected from
millions of videos) to hundreds of thousands of
simultaneous users?

v option 2: store/serve multiple copies of videos at

multiple geographically distributed sites (CDN)
§ enter deep: push CDN servers deep into many access
networks
• close to users
• used by Akamai, 1700 locations
§ bring home: smaller number (10’s) of larger clusters in
POPs near (but not within) access networks
• used by Limelight
Multmedia Networking 7-21
 CDN: “simple” content access scenario
Bob (client) requests video http://netcinema.com/6Y7B23V
§ video stored in CDN at http://KingCDN.com/NetC6y&B23V

1. Bob gets URL for for video

http://netcinema.com/6Y7B23V
from netcinema.com 2. resolve http://netcinema.com/6Y7B23V
web page 2 via Bob’s local DNS
1
6. request video from 5
KINGCDN server, 4&5. Resolve
streamed via HTTP http://KingCDN.com/NetC6y&B23
via KingCDN’s authoritative DNS,
netcinema.com 3. netcinema’s DNS returns URL
4 which returns IP address of KIingCDN
http://KingCDN.com/NetC6y&B23V server with video
3

netcinema’s
authorative DNS KingCDN.com KingCDN
authoritative DNS Multmedia Networking 7-22
CDN cluster selection strategy
v challenge: how does CDN DNS select “good”
CDN node to stream to client
§ pick CDN node geographically closest to client
§ pick CDN node with shortest delay (or min # hops) to
client (CDN nodes periodically ping access ISPs,
reporting results to CDN DNS)
§ IP anycast

v alternative: let client decide - give client a list of

several CDN servers
§ client pings servers, picks “best”
§ Netflix approach

Multmedia Networking 7-23

Case study: Netflix
v 30% downstream US traffic in 2011
v owns very little infrastructure, uses 3rd party
services:
§ own registration, payment servers
§ Amazon (3rd party) cloud services:
• Netflix uploads studio master to Amazon cloud
• create multiple version of movie (different
endodings) in cloud
• upload versions from cloud to CDNs
• Cloud hosts Netflix web pages for user browsing
§ three 3rd party CDNs host/stream Netflix
content: Akamai, Limelight, Level-3
Multmedia Networking 7-24
 Case study: Netflix
upload copies of
Amazon cloud
multiple versions of
video to CDNs Akamai CDN

Netflix registration,
accounting servers
3. Manifest file
2. Bob browses returned for
requested video Limelight CDN
Netflix video 2
3
1

1. Bob manages
Netflix account
Level-3 CDN
4. DASH
streaming

Multmedia Networking 7-25

Multimedia networking: outline
7.1 multimedia networking applications
7.2 streaming stored video
7.3 voice-over-IP
7.4 protocols for real-time conversational
applications
7.5 network support for multimedia

Multmedia Networking 7-26

Voice-over-IP (VoIP)
v VoIP end-end-delay requirement: needed to maintain
“conversational” aspect
§ higher delays noticeable, impair interactivity
§ < 150 msec: good
§ > 400 msec bad
§ includes application-level (packetization,playout),
network delays
v session initialization: how does callee advertise IP
address, port number, encoding algorithms?
v value-added services: call forwarding, screening,
recording
v emergency services: 911
Multmedia Networking 7-27
VoIP characteristics
v speaker’s audio: alternating talk spurts, silent
periods.
§ 64 kbps during talk spurt
§ pkts generated only during talk spurts
§ 20 msec chunks at 8 Kbytes/sec: 160 bytes of data
v application-layer header added to each chunk
v chunk+header encapsulated into UDP or TCP
segment
v application sends segment into socket every 20
msec during talkspurt

Multmedia Networking 7-28

VoIP: packet loss, delay
v network loss: IP datagram lost due to network
congestion (router buffer overflow)
v delay loss: IP datagram arrives too late for playout
at receiver
§ delays: processing, queueing in network; end-system
(sender, receiver) delays
§ typical maximum tolerable delay: 400 ms
v loss tolerance: depending on voice encoding, loss
concealment, packet loss rates between 1% and
10% can be tolerated

Multmedia Networking 7-29

 Delay jitter
constant bit
rate client constant bit
Cumulative data

transmission reception rate playout

at client
variable
network

buffered
data
delay
(jitter)

client playout time

delay

v end-to-end delays of two consecutive packets:

difference can be more or less than 20 msec
(transmission time difference)
Multmedia Networking 7-30
VoIP: fixed playout delay
v receiver attempts to playout each chunk exactly q
msecs after chunk was generated.
§ chunk has time stamp t: play out chunk at t+q
§ chunk arrives after t+q: data arrives too late
for playout: data “lost”
v tradeoff in choosing q:
§ large q: less packet loss
§ small q: better interactive experience

Multmedia Networking 7-31

VoIP: fixed playout delay
§ sender generates packets every 20 msec during talk spurt.
§ first packet received at time r
§ first playout schedule: begins at p
§ second playout schedule: begins at p’
packets

packets loss
generated
packets
playout schedule
received
p' - r

playout schedule
p-r

time

r
Multmedia Networking 5-32
p p'
Adaptive playout delay (1)
v goal: low playout delay, low late loss rate
v approach: adaptive playout delay adjustment:
§ estimate network delay, adjust playout delay at
beginning of each talk spurt
§ silent periods compressed and elongated
§ chunks still played out every 20 msec during talk spurt
v adaptively estimate packet delay: (EWMA -
exponentially weighted moving average, recall TCP RTT
estimate):
di = (1-a)di-1 + a (ri – ti)

delay estimate small constant, time received - time sent

after ith packet e.g. 0.1 (timestamp)
measured delay of ith packet
Multmedia Networking 7-33
Adaptive playout delay (2)
v also useful to estimate average deviation of delay, vi :
vi = (1-b)vi-1 + b |ri – ti – di|
v estimates di, vi calculated for every received
packet, but used only at start of talk spurt

v for first packet in talk spurt, playout time is:

playout-timei = ti + di + Kvi
remaining packets in talkspurt are played out
periodically

Multmedia Networking 5-34

Adaptive playout delay (3)
Q: How does receiver determine whether packet is
first in a talkspurt?
v if no loss, receiver looks at successive timestamps
§ difference of successive stamps > 20 msec -->talk spurt
begins.
v with loss possible, receiver must look at both time
stamps and sequence numbers
§ difference of successive stamps > 20 msec and sequence
numbers without gaps --> talk spurt begins.

Multmedia Networking 7-35

VoiP: recovery from packet loss (1)
Challenge: recover from packet loss given small
tolerable delay between original transmission and
playout
v each ACK/NAK takes ~ one RTT
v alternative: Forward Error Correction (FEC)
§ send enough bits to allow recovery without
retransmission (recall two-dimensional parity in Ch. 5)

simple FEC
v for every group of n chunks, create redundant chunk by
exclusive OR-ing n original chunks
v send n+1 chunks, increasing bandwidth by factor 1/n
v can reconstruct original n chunks if at most one lost chunk
from n+1 chunks, with playout delay
Multmedia Networking 7-36
VoiP: recovery from packet loss (2)
another FEC scheme:
v “piggyback lower
quality stream”
v send lower resolution
audio stream as
redundant information
v e.g., nominal
stream PCM at 64 kbps
and redundant stream
GSM at 13 kbps
v non-consecutive loss: receiver can conceal loss
v generalization: can also append (n-1)st and (n-2)nd low-bit rate
chunk
Multmedia Networking 7-37
 VoiP: recovery from packet loss (3)

interleaving to conceal loss:

v audio chunks divided into
smaller units, e.g. four 5
msec units per 20 msec
audio chunk
v packet contains small units
from different chunks
v if packet lost, still have most
of every original chunk
v no redundancy overhead,
but increases playout delay
Multmedia Networking 7-38
Voice-over-IP: Skype
Skype clients (SC)
v proprietary application-
layer protocol (inferred
via reverse engineering)
§ encrypted msgs
Skype
v P2P components: login server supernode (SN)
§ clients: skype peers
connect directly to supernode
overlay
each other for VoIP call network
§ super nodes (SN):
skype peers with
special functions
§ overlay network: among
SNs to locate SCs
§ login server
Application Layer 2-39
P2P voice-over-IP: skype
skype client operation:
1. joins skype network by
contacting SN (IP address
cached) using TCP Skype
login server
2. logs-in (usename,
password) to centralized
skype login server
3. obtains IP address for
callee from SN, SN
overlay
§ or client buddy list
4. initiate call directly to
callee

Application Layer 2-40

Skype: peers as relays
v problem: both Alice, Bob
are behind “NATs”
§ NAT prevents outside peer
from initiating connection to
insider peer
§ inside peer can initiate
connection to outside

v relay solution:Alice, Bob maintain

open connection
to their SNs
§ Alice signals her SN to connect
to Bob
§ Alice’s SN connects to Bob’s
SN
§ Bob’s SN connects to Bob over
open connection Bob initially
initiated to his SN
Application Layer 2-41
Multimedia networking: outline
7.1 multimedia networking applications
7.2 streaming stored video
7.3 voice-over-IP
7.4 protocols for real-time conversational
applications: RTP, SIP
7.5 network support for multimedia

Multmedia Networking 7-42

Real-Time Protocol (RTP)

v RTP specifies packet v RTP runs in end

structure for packets systems
carrying audio, video v RTP packets
data encapsulated in UDP
v RFC 3550 segments
v RTP packet provides v interoperability: if two
§ payload type VoIP applications run
identification RTP, they may be able
§ packet sequence to work together
numbering
§ time stamping

Multmedia Networking 7-43

RTP runs on top of UDP
RTP libraries provide transport-layer interface
that extends UDP:
• port numbers, IP addresses
• payload type identification
• packet sequence numbering
• time-stamping

Multmedia Networking 5-44

RTP example
example: sending 64 kbps v RTP header indicates
PCM-encoded voice over type of audio encoding
RTP in each packet
v application collects § sender can change
encoded data in chunks, encoding during
e.g., every 20 msec = conference
160 bytes in a chunk v RTP header also
v audio chunk + RTP
contains sequence
header form RTP numbers, timestamps
packet, which is
encapsulated in UDP
segment

Multmedia Networking 7-45

RTP and QoS
v RTP does not provide any mechanism to ensure
timely data delivery or other QoS guarantees
v RTP encapsulation only seen at end systems (not
by intermediate routers)
§ routers provide best-effort service, making no
special effort to ensure that RTP packets arrive
at destination in timely matter

Multmedia Networking 7-46

RTP header
payload sequence Synchronization Miscellaneous
time stamp
type number Source ID fields
type

payload type (7 bits): indicates type of encoding currently being

used. If sender changes encoding during call, sender
informs receiver via payload type field
Payload type 0: PCM mu-law, 64 kbps
Payload type 3: GSM, 13 kbps
Payload type 7: LPC, 2.4 kbps
Payload type 26: Motion JPEG
Payload type 31: H.261
Payload type 33: MPEG2 video

sequence # (16 bits): increment by one for each RTP packet sent
v detect packet loss, restore packet sequence

Multmedia Networking 5-47

RTP header
payload sequence Synchronization Miscellaneous
time stamp
type number Source ID fields
type

v timestamp field (32 bits long): sampling instant of first

byte in this RTP data packet
§ for audio, timestamp clock increments by one for each
sampling period (e.g., each 125 usecs for 8 KHz sampling
clock)
§ if application generates chunks of 160 encoded samples,
timestamp increases by 160 for each RTP packet when
source is active. Timestamp clock continues to increase
at constant rate when source is inactive.

v SSRC field (32 bits long): identifies source of RTP

stream. Each stream in RTP session has distinct SSRC
Multmedia Networking 7-48
RTSP/RTP programming assignment
v build a server that encapsulates stored video
frames into RTP packets
§ grab video frame, add RTP headers, create UDP
segments, send segments to UDP socket
§ include seq numbers and time stamps
§ client RTP provided for you
v also write client side of RTSP
§ issue play/pause commands
§ server RTSP provided for you

Multmedia Networking 7-49

Real-Time Control Protocol (RTCP)
v works in conjunction v each RTCP packet
with RTP contains sender and/or
v each participant in RTP receiver reports
session periodically § report statistics useful to
sends RTCP control application: # packets
sent, # packets lost,
packets to all other interarrival jitter
participants v feedback used to control
performance
§ sender may modify its
transmissions based on
feedback

Multmedia Networking 7-50

 RTCP: multiple multicast senders
sender RTP
RTCP

RTCP
RTCP

receivers

v each RTP session: typically a single multicast address; all RTP

/RTCP packets belonging to session use multicast address
v RTP, RTCP packets distinguished from each other via distinct port
numbers
v to limit traffic, each participant reduces RTCP traffic as number of
conference participants increases
Multmedia Networking 5-51
RTCP: packet types
receiver report packets:
v fraction of packets lost, last
sequence number, average
interarrival jitter
sender report packets:
v SSRC of RTP stream,
current time, number of
packets sent, number of
bytes sent
source description packets:
v e-mail address of sender,
sender's name, SSRC of
associated RTP stream
v provide mapping between
the SSRC and the
user/host name
Multmedia Networking 7-52
RTCP: stream synchronization
v RTCP can synchronize v each RTCP sender-report
different media streams packet contains (for most
within a RTP session recently generated packet
v e.g., videoconferencing in associated RTP stream):
app: each sender § timestamp of RTP
generates one RTP packet
stream for video, one for § wall-clock time for
audio. when packet was
v timestamps in RTP created
packets tied to the video, v receivers uses association
audio sampling clocks to synchronize playout of
§ not tied to wall-clock audio, video
time

Multmedia Networking 7-53

RTCP: bandwidth scaling
RTCP attempts to limit its
traffic to 5% of session
bandwidth
example : one sender,
sending video at 2 Mbps
v RTCP attempts to limit
RTCP traffic to 100 Kbps
v RTCP gives 75% of rate
to receivers; remaining
25% to sender
v 75 kbps is equally shared
among receivers:
§ with R receivers, each receiver
gets to send RTCP traffic at
75/R kbps.
v sender gets to send RTCP
traffic at 25 kbps.
v participant determines RTCP
packet transmission period
by calculating avg RTCP
packet size (across entire
session) and dividing by
allocated rate
Multmedia Networking 7-54
SIP: Session Initiation Protocol [RFC 3261]
long-term vision:
v all telephone calls, video conference calls take
place over Internet
v people identified by names or e-mail addresses,
rather than by phone numbers
v can reach callee (if callee so desires), no matter
where callee roams, no matter what IP device
callee is currently using

Multmedia Networking 7-55

SIP services
v SIP provides v determine current IP
mechanisms for call address of callee:
setup: § maps mnemonic
§ for caller to let identifier to current IP
callee know she address
wants to establish a v call management:
call § add new media
streams during call
§ so caller, callee can
§ change encoding
agree on media type, during call
encoding
§ invite others
§ to end call § transfer, hold calls

Multmedia Networking 7-56

 Example: setting up call to known IP address
Bob
Alice

v Alice’s SIP invite message

167.180.112.24 193.64.210.89 indicates her port number, IP
INVITE bob
c=IN IP4 16
@193.64.21
7.180.112.2
0.89 address, encoding she prefers
m=audio 38
060 RTP/AV
4
P0 to receive (PCM µlaw)
port 5060 Bob's
terminal rings
200 OK
c=IN IP4 193.64.2
10.89 v Bob’s 200 OK message
P/AVP 3
port 5060
m=audio 4875 3 RT
indicates his port number, IP
ACK
address, preferred encoding
port 5060
(GSM)
µ Law audio
port 38060 v SIP messages can be sent
over TCP or UDP; here sent
GSM over RTP/UDP
port 48753

v default SIP port number is

time time
5060
Multmedia Networking 5-57
Setting up a call (more)
v codec negotiation: v rejecting a call
§ suppose Bob doesn’t § Bob can reject with
have PCM µlaw encoder replies “busy,” “gone,”
§ Bob will instead reply “payment required,”
with 606 Not “forbidden”
Acceptable Reply, listing v media can be sent
his encoders. Alice can over RTP or some
then send new INVITE other protocol
message, advertising
different encoder

Multmedia Networking 7-58

Example of SIP message
INVITE sip:bob@domain.com SIP/2.0
Via: SIP/2.0/UDP 167.180.112.24 v Here we don’t know
From: sip:alice@hereway.com Bob’s IP address
To: sip:bob@domain.com § intermediate SIP
Call-ID: a2e3a@pigeon.hereway.com
servers needed
Content-Type: application/sdp
Content-Length: 885 v Alice sends, receives
SIP messages using SIP
c=IN IP4 167.180.112.24 default port 506
m=audio 38060 RTP/AVP 0
v Alice specifies in
header that SIP client
Notes:
v HTTP message syntax
sends, receives SIP
v sdp = session description protocol messages over UDP
v Call-ID is unique for every call

Multmedia Networking 7-59

Name translation, user location
v caller wants to call v result can be based on:
callee, but only has § time of day (work,
callee’s name or e-mail home)
address. § caller (don’t want boss
to call you at home)
v need to get IP address of
callee’s current host: § status of callee (calls sent
to voicemail when callee
§ user moves around is already talking to
§ DHCP protocol someone)
§ user has different IP
devices (PC, smartphone,
car device)

Multmedia Networking 7-60

SIP registrar
v one function of SIP server: registrar
v when Bob starts SIP client, client sends SIP REGISTER
message to Bob’s registrar server

register message:
REGISTER sip:domain.com SIP/2.0
Via: SIP/2.0/UDP 193.64.210.89
From: sip:bob@domain.com
To: sip:bob@domain.com
Expires: 3600

Multmedia Networking 7-61

SIP proxy
v another function of SIP server: proxy
v Alice sends invite message to her proxy server
§ contains address sip:bob@domain.com
§ proxy responsible for routing SIP messages to callee,
possibly through multiple proxies
v Bob sends response back through same set of SIP
proxies
v proxy returns Bob’s SIP response message to Alice
§ contains Bob’s IP address
v SIP proxy analogous to local DNS server plus TCP
setup

Multmedia Networking 7-62

SIP example: jim@umass.edu calls keith@poly.edu
Poly SIP
2. UMass proxy forwards request registrar
to Poly registrar server
2 3 3. Poly server returns redirect response,
indicating that it should try keith@eurecom.fr

UMass 4. Umass proxy forwards request Eurecom SIP

SIP proxy to Eurecom registrar server registrar
4
7
1. Jim sends INVITE 6-8. SIP response returned to Jim 5. eurecom
message to UMass 8 5 registrar
6 forwards INVITE
SIP proxy. 1
to 197.87.54.21,
which is running
keith’s SIP
9 client
128.119.40.186
9. Data flows between clients
197.87.54.21
Multmedia Networking 7-63
Comparison with H.323
v H.323: another signaling
protocol for real-time,
interactive multimedia
v H.323: complete,
vertically integrated suite
of protocols for
multimedia conferencing:
signaling, registration,
admission control,
transport, codecs
v SIP: single component.
Works with RTP, but
does not mandate it. Can
be combined with other
protocols, services
v H.323 comes from the
ITU (telephony)
v SIP comes from IETF:
borrows much of its
concepts from HTTP
§ SIP has Web flavor;
H.323 has telephony
flavor
v SIP uses KISS principle:
Keep It Simple Stupid
Multmedia Networking 7-64