Session Initiation Protocol - SIP

Switching Core Network Signalling Rel.4

M14/U4

For public use – IPR applies

1 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP interfaces

MGCF
BICC / SIP SIP IMS
MSS
Nc Mg
MSS
P
SA

H248
H248

Mc
Mc
BS

P
NA
RA

GERAN
MGW MGW
Nb IP

UTRAN

For public use – IPR applies

4 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Important SIP specifications

IETF - RFC 3261 Session Initiation Protocol

IETF – RFC 2976 SIP Enhancement: INFO method

IETF – RFC 3262 SIP Enhancement: PRACK method

IETF – RFC 3311 SIP Enhancement: UPDATE method

ITU-T Q.1912.5 Interworking between SIP and BICC/ISUP

(SIP-I)

3GPP 24.228/229 SIP for IMS

For public use – IPR applies

5 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP message transport

Default if Default if
message length message length Selectable by
≤ 1300 bytes: > 1300 bytes MML:
SIP SIP SIP

UDP TCP SCTP

IP IP IP

L1 L1 L1

ZJNM:
…DEFTRA=<UDP,TCP,
SCTP,SCTPNM>;…

For public use – IPR applies

6 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP transactions
Client Server

MSS A MSS B

INVITE
transaction

100(Trying)

180(Ringing) requests

200(OK)

provisional
responses
transaction

ACK (=1xx)

final
responses
transaction

BYE (≠1xx)
200(OK)

For public use – IPR applies

7 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Supported SIP Methods

INVITE Session initiation.

ACK Acknowledging final responses to INVITE.

basic SIP

BYE Requesting the release of the call (used in speech phase).

CANCEL Transaction cancelling request.

OPTIONS Asking for capabilities (for example, allowed methods).

UPDATE Bearer-related information update/session refreshment.

enhancements

INFO Sending information that does not affect call state

(the main usage is tunneling ISUP messages that do
not have a corresponding SIP message; it is also
used to transfer out-of-band DTMF between MSC Servers).

PRACK For reliable provisional response.

For public use – IPR applies

8 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP Response categories
• A 3-digit integer response-code indicates the outcome of an attempt to
understand and satisfy a request

– 1xx Informational
request received, continuing to process the request (=provisional responses)

– 2xx Success
the action was successfully received, understood and accepted

– 3xx Redirection
further action needs to be taken in order to complete the request

– 4xx Client Error

the request contains bad syntax or cannot be fulfilled at this server

– 5xx Server Error

the server failed to fulfil an apparently valid request

– 6xx Global Failure

the request cannot be fulfilled at any server
For public use – IPR applies
9 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP Response codes, part 1

Supported SIP responses

1xx Provisional responses 3xx Redirection

100 Trying 300 Multiple Choices
180 Ringing 301 Moved Permanently
181 Call Is Being Forwarded 302 Moved Temporarily
182 Queued 305 Use Proxy
183 Session Progress 380 Alternative Service

2xx Successful outcome

200 OK

The list contains all possible response codes.

The ones that can not be sent by the MSS are
marked in italics.

For public use – IPR applies

10 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP Response codes, part 2
4xx Client Error
400 Bad Request
401 Unauthorized
403 Forbidden
404 Not Found
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout
410 Gone
411 Length Required
413 Request Entity Too Large
414 Request-URI Too Large
415 Unsupported Media Type
420 Bad Extension
421 Extension Required
422 Session Interval Too Small
480 Temporarily Not Available
For public use – IPR applies
11 © Nokia Siemens Networks
481 Call Leg/Transaction Does Not Exist
482 Loop Detected
483 Too Many Hops
484 Address Incomplete
485 Ambiguous
486 Busy Here
487 Request Cancelled
488 Not Acceptable Here
490 Request Updated
491 Request Pending
The list contains all possible response codes.
The ones that can not be sent by the MSS are
marked in italics.
Presentation / Author / Date / Document Number
SIP Response codes, part 3

5xx Server Error

500 Internal Server Error
501 Not Implemented
502 Bad Gateway
503 Service Unavailable
504 Gateway Timeout
505 SIP Version Not Supported
513 Message Too Large
580 Precondition Failure

6xx Global Failure

600 Busy Everywhere
603 Decline
604 Does not exist anywhere
606 Not Acceptable
The list contains all possible response codes.
The ones that can not be sent by the MSS are
marked in italics.

For public use – IPR applies

12 © Nokia Siemens Networks Presentation / Author / Date / Document Number
MSS – MSS call setup (simplified)

1
1

1
2
2
1
3 call setup
3
1
4

1
5 call established
6
call release
6

For public use – IPR applies

13 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SIP Addresses

SIP Addresses

SIP-URI

sip:user:password@host:port;uri-parameters
<sip:john@server.com>

SIPS-URI

telephone-URI

tel: phone-number
<tel:+392695550009>

For public use – IPR applies

14 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Elements of a SIP Request Message
A SIP Request consists of:
- a Request-Line,
- one or more Header fields,
- an empty line <CRLF>, indicating the end of the header fields, and
- an optional Message-Body.

For public use – IPR applies

15 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Elements of a SIP Request Message

Method <sp> Request-URI <sp> SIP-version

Request Line INVITE sip:bob@biloxi.com SIP/2.0

Via: SIP/2.0/UDP pc33.atlanta.com;branch=z9hG4bK776asdhds
Max-Forwards: 70
To: Bob <sip:bob@biloxi.com>
From: Alice <sip:alice@atlanta.com>;tag=1928301774
Message Header Call-ID: a84b4c76e66710@pc33.atlanta.com
CSeq: 314159 INVITE
Contact: <sip:alice@pc33.atlanta.com>
Content-Type: application/sdp
Content-Length: 142
<CRLF>

(142 Byte Message Body, not shown)

For public use – IPR applies

16 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Layout of a SIP Response Message
A SIP Response consists of:
- a Status Line,
- one or more Header fields,
- an empty line <CRLF>, indicating the end of the header fields, and
- an optional Message-Body.

For public use – IPR applies

17 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Elements of a SIP Response Message

SIP-Version <sp> Status-Code <sp> Reason-Phrase

Status Line SIP/2.0 200 OK

Via: SIP/2.0/UDP here.com:5060
From: BigGuy <sip:UserA@here.com>;tag=6744509153
To: LittleGuy <sip:UserB@there.com>;tag=8321234356
Call-ID: 12345601@here.com
Message Header CSeq: 1 INVITE
Contact: <sip:UserB@110.111.112.113>
Content-Type: application/sdp
Content-Length: 147
<CRLF>

(147 Byte Message Body, not shown)

For public use – IPR applies

18 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Tasks of a SIP message

A INVITE sip:bill@work.com SIP/2.0

A Defines purpose of
B To: Bill<sip:bill@work.com> message
B From: John<sip:john@home.com>
D Call-ID: 267343@192.168.1.212 B Declares who the message
E Via: SIP/2.0/UDP 192.168.1.212 relates to
B Contact: john@192.168.1.212
D CSeq: 1 INVITE
C Content-Type: application/SDP C Enables delivery of non-
C SIP media
Content-Length: 124

D Ensures request can be

v=0 related to other messages
C
o=192.168.1.212 IN IP4 192.168.1.212 in session
s= Call from John
c=IN IP4 192.168.1.212
E Records path
m=audio 5004 RTP/AVP 8 3 0

For public use – IPR applies

19 © Nokia Siemens Networks Presentation / Author / Date / Document Number
SDP Parameters

SDP-parameters:
v: protocol version
o: owner/creator and session identifier
s: session name
c: connection information
t: time the session is active
m: media name and transport address
a: zero or more media attribute lines
b: bandwidth information

For public use – IPR applies

20 © Nokia Siemens Networks Presentation / Author / Date / Document Number
Codecs represented in SIP
Codec SDP representation in SIP messages
EFR m=audio 1234 RTP/AVP 103
a=rtpmap:103 GSM-EFR/8000
FR m=audio 1234 RTP/AVP 3
a=rtpmap:3 GSM/8000
G.711 A-law m=audio 1234 RTP/AVP 8
a=rtpmap:8 PCMA/8000
G.711 u-law m=audio 1234 RTP/AVP 0
a=rtpmap:0 PCMU/8000
G.723.1 m=audio 1234 RTP/AVP 4
a=rtpmap:4 G723/8000
G.723.1 Annex A m=audio 1234 RTP/AVP 4
a=rtpmap:4 G723/8000
a=fmtp:4 annexa=yes
G.729a m=audio 1234 RTP/AVP 18
a=rtpmap:18 G729A/8000
G.729a Annex B m=audio 1234 RTP/AVP 18
a=rtpmap:18 G729A/8000
a=fmtp:18 annexb=yes
iLBC m=audio 1234 RTP/AVP 97
a=rtpmap:97 iLBC/8000
Clearmode m=audio 1234 RTP/AVP 100
a=rtpmap:100 CLEARMODE/8000

For public use – IPR applies

21 © Nokia Siemens Networks Presentation / Author / Date / Document Number
MSS-MSS call with ISUP encapsulation
MSS-A MSS-A

INVITE (IAM, SDP)

100 Trying
183 Session Progress (SDP)
PRACK encapsulated
ISUP messages
200 OK
183 Session Progress (ACM)

PRACK
200 OK
180 Ringing (CPG)
PRACK
200 OK
200 OK (ANM)
ACK

BYE (REL)
200 OK (RLC)

For public use – IPR applies

22 © Nokia Siemens Networks Presentation / Author / Date / Document Number
ISUP versions for encapsulation

base string used Protocol

itu-t18 ITU-T Q.761-4 (1988)

itu-t92+ ITU-T Q.761-4 (1992)
ansi88 ANSI T1.113-1988
ansi00 ANSI T1.113-2000
etsi121 ETS 300 121
etsi356 ETS 300 356
gr317 BELLCORE GR-317
ttc87 JT-Q761-4(1987-1992)
ttc93+ JT-Q761-4(1993-)

e.g. ZJNM:FQDN=“NAME.MSS.COM"::ISUPVR="itu-t92+";

For public use – IPR applies

23 © Nokia Siemens Networks Presentation / Author / Date / Document Number