SIP Protocol Stack

SIP and SDP Registration

Call A/V
use and Audio Video
Control Control
TCP or UDP Signaling

G.7xx H.26x
SIP SDP SIP SDP RTCP

RTP

TCP UDP

IP

Data Link Layer (Ethernet, ATM, FR, ...)

 SIP – Components
SIP Proxy SIP Redirect Location
Registrar
Server Server Server

IP

SIP SIP
User Agent SIP User Agent
Gateway

PSTN H.323
 SIP - Elements
sip:11111@tfk.de sip:22222@siemens.de

1 4 5
SIP User
SIP User tfk.de siemens.de Agent Server
Agent Client Proxy Proxy

3
2

DNS
 SIP-Server Functionalities
 Registrar
here a termination point can register
 Location-Server
here a subscriber can search another
one with the other‘s host address
 Proxy-Server
forwards requests to the expected
target address

SIP Server  Redirect-Server

forwards requests to the responsible
Server
SDP - Session Description Protocol
 Port Number
 Start and End Time of a Session
 Parameters for the Receiver
 Information about the used bandwidth during a
conference
 Information about the contact person who is
responsible for the session
 SIP - Forking

SIP User
Agent Server

SIP User SIP User

Agent Client Agent Server

SIP User
Agent Server

SIP User
Agent Server
 Comparison of SIP and H.323
Standard Organization ITU-T IETF

Terminal H.323 Terminal User Agent

Gatekeeper SIP-Server
Server (optional)
stateful stateful / stateless

Call Set-up H.225.RAS, H225.0 SIP

Call Control H.245 SDP

IP-Adress Resolution Gatekeeper DNS

Point – to - Multipoint - Forking

 Advantages of SIP
• Easy Implementation (in comparison to H.323)

• Easy Integration of other Internet Protocols (HTTP)

• Better Scalability (in comparison to H.323)

• Mobility (Forking)

• Modular Architecture (in contrast to H.323)

 Why is everyone making such a noise about SIP ?

 Because it comes from the IETF, it’s simple and easy to program
 Appeal with Internet Developer community

 Message example for SIP  Message example for H.323

INVITE sip:my.mother@aol.comSIP/2.0 8AFD659385BBFD9122FFAB

Via: SIP/2.0/UDP 192.190.132.20:3456 229D0E0000FB8AFD659385
Call-ID: a2e3a@192.190.132.20
From: sip: her.lazy_son@T-online.com BBFD9122FFAB229D0E0000FB
Content-type: application/sdp etc etc
Content-Length: 98

Fig. 5 (SN2050EU01SN_0014 NGN migration - IP direct access (SIP based), 9)

 SIP Request messages

INVITE starts a call set up

ACK acknowledges a 200 (OK) response
BYE releases a connection
CANCEL cancels an open request
REGISTER for registration at the Location Service
OPTIONS Request on what features are supported by
the counterpart
 SIP Response messages
Informational = Client-Error =
"100"; Trying "400"; Bad Request
"180"; Ringing
"181"; Call Is Being Forwarded "401"; Unauthorized
"182"; Queued
"402"; Payment Required
"183"; Session Progress
Success =
"403"; Forbidden
"200"; OK
Redirection = "404"; Not Found
"300"; Multiple Choices
"301"; Moved Permanently "405"; Method Not Allowed
"302"; Moved Temporarily
"305"; Use Proxy ...
"380"; Alternative Service
Global-Failure = Server-Error =
"600"; Busy Everywhere "500"; Internal Server Error
"603"; Decline "501"; Not Implemented
"502"; Bad Gateway
 Messages
• Messages = Requests + Responses INVITE sip:watson@boston.bell-tel.com SIP/2.0

Via: SIP/2.0/UDP kton.bell-tel.com

From: A. Bell <sip:a.g.bell@bell-tel.com>;tag=3
• Consist of To: T. Watson <sip:watson@bell-tel.com>
Call-ID: 662606876@kton.bell-tel.com
– request/status line, CSeq: 1 INVITE
Contact: <sip:a.g.bell@kton.bell-tel.com>
Subject: Mr. Watson, come here.
– header fields, Content-Type: application/sdp
Content-Length: ...
– and message body
v=0
o=bell 53655765 2353687637 IN IP4 128.3.4.5
s=Mr. Watson, come here.
t=3149328600 0
c=IN IP4 kton.bell-tel.com
m=audio 3456 RTP/AVP 0 3 4 5
a=rtpmap:0 PCMU/8000
a=rtpmap:3 GSM/8000
a=rtpmap:4 G723/8000
a=rtpmap:5 DVI4/8000

Fig. 9 (SN2050EU01SN_0014 NGN migration - IP direct access (SIP based), 17)

Layout of a SIP Request message

Method Request – URL SIP-Version

z.B. INVITE sip:22222@siemens.de SIP/2.0

Layout of a SIP Response message

SIP-Version Status-Code Reason-Phrase

z.B. SIP/2.0 200 OK

 SIP Connection Set Up – Without
Location Service
SIP User Agent SIP User Agent
Client (A – Side) 1. INVITE (Request) Server (B – Side)
2. 100 Trying (Response)
3. 180 Ringing (Response)
4. 200 OK (Response)
5. ACK (Request) Call is
accepted

The subscriber must

know the location of the
user agent
 SIP-Connection Release

SIP User Agent SIP User Agent

Client (A – Seite) 1. BYE (Request) Server (B – Seite)

2. 100 Trying (Response)

3. 200 OK (Response)
 SIP User Agent-Registration
SIP Server Location
(Registrar) Server

2. For example
LDAP

1. REGISTER

3. 200 OK 2. Saves the user agent‘s IP-

Address together with its URL
(Name or telephone number)

SIP User Agent

SIP Connection Set-up via Proxy Server
2. Translate the given
SIP-URL (Name or SIP Server Location
telephone number) (Proxy) Server
in a Location (IP-@).
E
VIT

ng
ng

3.
3a
gi
yi

I
.1
4a
IN

NV
Tr

i n

.1

00
R
00
1.

I
K

TE
0

80
5a
O
.1

Tr
18 .2

y in
0

Ri
1a

.
20

4b

ng
00

g
in
5b

g
K

6. ACK 7. ACK

SIP User Agent SIP User Agent

Client (A-Side) Server (B-Side)
SIP Connection Set-up – Redirect Mode
SIP Server Location
(Redirect) Server
2. Translate the given
URL (Name or
telefone number) into
a Location (IP-@).

E D
V
O
M
x 4. ACK
1. INVITE 30
3.

5. INVITE (Request)
6. 100 Trying (Response)
7. 180 Ringing (Response)
8. 200 OK (Response)
SIP User Agent 9. ACK (Request) SIP User Agent
Client (A – Side) Server (B – Side)
 SIP Call Setup – Forking by Proxy
SIP Server Location
2. Translate the given
(Proxy) Server
SIP-URL (Name or
telphone number)
into eine Location
(IP-@).
6a.
CA
NC
E L
3.
E

I
VIT

NV
K

IT
O
N

4.
00
1. I

20
.2

0
6b

O
5. The first 200 SIP User Agent

K
OK response Server B2
is accepted
and is
forwarded.
SIP User Agent SIP User Agent
Client (A-Side) Server B1

SIP Trace