Ims 2

SIP Protocol
Overview
www.huawei.com
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

References
RFC 3261/3262/3263/3264/2327
HUAWEI user manual- Solution-IMS Interfaces and

Protocols-SIP
Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved. Page1
Objectives
Upon completion of this course, you will be able to:
Know the function and workflow of SIP protocol
Know the message structure of SIP
Understand the header fields in IMS SIP
Contents
1. SIP Overview
2. SIP Protocol
3. SIP Application in IMS
Whats SIP?
SIP: Session Initiation Protocol
Setting up, controlling and tearing down sessions
SIP is an IETF protocol for multi-media sessions
Sessions including text, video, voice, etc.
SIP is one of the Internet protocol
Text based like HTTP
Request/Reply protocol
Widely used for successful Internet
Can be based on UDP/TCP/SCTP, most of the case now use UDP
Session Related Protocols
SDP (Session Description Protocol)
Always is included in SIP message body
Session description (SDP) separated from Session management (SIP)
RTP (Real-time Transmission Protocol)
Media transmission e.g. voice, video
RTCP (Real-time Transmission Control Protocol)
Report and adjust the media transmission
Simplified SIP Network Architecture
Request Proxy Server
Determines Where to
Send the Signaling
Messages
User Agent SIP Request User Agent

(Client) SIP Request
(Server)
Sends SIP Receives SIP
Requests Requests
SIP Response SIP Response
Media Stream (RTP)
Logical Entities of SIP
SIP use client/server architecture
Logical SIP entities are:
User Agents (UA) Network Servers

User Agent Client (UAC): Register: Maintains the location of SIP
Initiates SIP requests users, sip clients needs to update the
User Agent Server (UAS): location using register request
Proxy: decides next hop and forwards
Returns SIP response
request
Both UAC and UAS can
Redirect: Accepts SIP request and
terminate a call
translates to new address
Transaction and Dialog
Transaction Dialog
comprises all messages Composed with more
from the 1st request and all
transactions
the response.
INVITE is the only command
At least includes one final
to create a Dialog.
response (not 1xx
Response) Identified by Call-ID, Local
Tag and Remote Tag
Use branch field in Via
header and Cseq header to
identify
Transaction and Dialog (Cont.)
Transaction Dialog
A request and all its Consist of several
response transactions
Invite
Invite T1
183
183 PRACK T2
200
T1
180 Ringing
180 Ringing 200
ACK T3
200 ok Bye T4
200
SIP URI
SIP URI : A SIP URI is in the same format as an E-mail
address
2 types of SIP URI

Address-of-record (AOR): It identifies a user, and is open to the
public, for instance -- SIP:admin@huawei.com
Full qualified domain name (FQDN) or IP address: It identifies a

device, for instance SIP:admin@172.19.1.193
Contents
1. SIP Overview
2. SIP Protocol
Contents
2. SIP Protocol
2.1 Message type
2.2 Message structure
2.3 Header fields
SIP Message Type -- Request
Basic Request Extended Request
INVITE: to initiate a session MESSAGE: is applied to IM
ACK: the response of INVITE SUBSCRIBE : to subscribe to a notify

event
CANCEL: to cancel a session
NOTIFY: to send a notify event
BYE: to terminate a session
UPDATE: to modify the session attributes
REGISTER: to register in a
at the establishment stage of a call
server
PUBLISH: to distribute its event state to
OPTIONS: for querying servers the status server
about their capabilities
PRACK: to indicate the reliability of a
temporary response
SIP Message Type -- Response
SIP response type:
1xx: Provisional -- request received, continuing to process the
request;
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 fulfill an apparently valid
request;
6xx: Global Failure -- the request cannot be fulfilled at any server.
SIP Basic Flow
Session setup Registration
Client A Proxy A Proxy B Client B Client A Proxy A

INVITE INVITE
Register
100 TRYING INVITE
100 TRYING 401 unauthorized
100 TRYING
Register
180 RINGING
180 RINGING 200 OK
180 RINGING 200 OK
200 OK
200 OK
Contents
2. SIP Protocol
2.1 Message type
2.3 Header fields
SIP Message Structure
SIP is a Text-
based protocol
and comprise
by 3 parts:
Request-Line
Header
Body
Request-line in SIP Request Message
Request-line = Method SP Request-URI SP SIP-Version CRLF
Example: INVITE sip:bob@huawei.com SIP/2.0

Method: This specification defines six method
REGISTER: for registering contact information
INVITE: for setting up sessions
ACK: for setting up sessions
CANCEL: for cancelling a session
BYE: for terminating sessions
OPTIONS: for querying servers about their capabilities
Request-URI: It indicates the user or service to which this request is

being addressed.
SIP-version
Start-line in SIP Response
Message
Status-line
Example: SIP/2.0 200 OK
SIP-version
Status-code
1xx
2xx
3xx
4xx
5xx
6xx
Reason-phase
SIP Message Header
Message-header:
Format: field-name: field-value
REGISTER sip:registrar.huawei.com SIP/2.0
Via: SIP/2.0/UDP bobspc.huawei.com:5060;branch=z9hG4bKnashds7

Max-Forwards: 70
To: Bob <sip:bob@huawei.com>
From: Bob <sip:bob@huawei.com>;tag=456248
Call-ID: 843817637684230@998sdasdh09
CSeq: 1826 REGISTER
Contact: <sip:bob@192.0.2.4>
Expires: 7200
Content-Length: 0
SIP Message Body
Optional, can be any protocol
Most implementations: SDP

SDP: Session description protocol, convey sufficient
information to calling and called party about the user
capabilities
SDP includes: Media to use; Media destination; Session name

and purpose; Contact information
SDP field have a required order
SIP Message Body -- SDP Example
v=0
o=HuaweiSoftX3000 868 868 IN IP4 10.216.9.200
s=Sip Call
c=IN IP4 10.216.6.108
t=0 0
m=audio 17368 RTP/AVP 8
a=rtpmap:8 PCMA/8000
SDP Parameter Name Remarks

Parameter
v Version number v=0
o Origin containing o=<user name> <session id> <version> <network type>
name <address type> <address>
s session name
c Connection Connection IP address for media (10.216.6.108)
t Time t=<start time> <stop time>
m Media Media format (audio); Port number(17368)
a Attribute Media encoding (PCM A Law); Sample rate (8000Hz)
Contents
2. SIP Protocol
2.1 Message type
2.3 Header fields
Header Fields Basic Headers
INVITE sip:66500002@191.169.1.110 SIP/2.0
From: <sip:44510000@191.169.1.116>;tag=1ccb6df3
To: <sip:66500002@191.169.1.110>
CSeq: 1 INVITE
Call-ID: 20973e49f7c52937fc6be224f9e52543@sx3000
Via:SIP/2.0/UDP server9.example.com;branch=z9hG4kb77ef4c23
Via: SIP/2.0/UDP 191.169.1.116:5061;branch=z9hG4bkbc427dad6
Record-Route:<sip:server9.example.com.lr>
Route:<sip:server10.example.com.lr>
Contact: <sip:44510000@191.169.1.116:5061>
Supported: 100rel,
Max-Forwards:70
User-agent: Flexit-IMS softphone V1.2D301SP03
Expires:120
Content-Length:230
Content-Type: application/sdp
Header Fields From & To
TO: the target of this request
FROM: the logical identity of the initiator of the request,

possibly the user's address-of-record
Example:
INVITE sip:bob@huawei.com SIP/2.0
From: Alice <sip:alice@atlanta.com>;tag=1928301774
SIP/2.0 180 Ringing

To: Bob <sip:bob@huawei.com>;tag=a6c85cf
From: Alice <sip:alice@atlanta.com>;tag=1928301774
Header Fields From & To (Cont.)
Request URI & From & To
REGISTER
destination
subscriber
From: Bob<sip:bob@huawei.com>;tag=456248
INVITE
callee
INVITE sip:ice@huawei.com SIP/2.0
To:Ice <sip:ice@huawei.com>
caller
Header Fields Contact
Contact
Provide an address for direct communication with the user.
Present in INVITE, ACK, and REGISTER requests, success

responses, call process responses, and redirection responses
Example:
Contact: <sip:44510000@191.169.1.116:5061>
Header Fields Call-ID & Cseq
Call-ID: a globally unique identifier
Call-ID and tags are used to identify a dialog.
Cseq: as a way to identify and order transactions
Consists of a sequence number and a method
Example:
Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
SIP/2.0 180 Ringing

Call-ID: a84b4c76e66710
CSeq: 314159 INVITE
Header Fields Record-Route and Route
Record-Route
Added by a proxy in a request to force subsequent requests in the
session to be routed through the proxy
Is used to create the Route header field in subsequent requests
Route
Is used to forcibly route a request through the listed set of proxies
Example: Example:
INVITE sip:bob@huawei.com SIP/2. INVITE sip:bob@huawei.com SIP/2.
Record-Route:<scscf.huawei.com.lr> Route:<scscf.huawei.com.lr>
Record-Route:<pcscf.huawei.com.lr>
Header Fields - Via
Via:
Identifies the route for the response
MUST contain a branch parameter: to identify the transaction
Example:
SIP/2.0 200 OK
Via: SIP/2.0/UDP server10.huawei.com; branch=z9hG4bKnashds8;
Via: SIP/2.0/UDP bigbox3.site3.atlanta.com;
branch=z9hG4bK77ef4c2312983.1;
Via: SIP/2.0/UDP pc33.atlanta.com;
branch=z9hG4bK776asdhds ;received=192.0.2.1
Header Fields - Supported
Supported
100rel extension provides an appropriate mechanism for the
reliable transportation of the 100 response
The acknowledgement request method for a provisional

response in 100rel is PRACK
100rel extension can be realized through the Supported

header fields
Example:
Supported: 100rel,
Header Fields - Content-length/Content-Type
Content-length
Indicates the size of the message body
If a message does not contain a message body, the value of the
Content-Length header field must be set to 0.
Example:
Content-Length: 142
Content-type
Indicates the media type of the message body sent to the recipient
Example:
Content-Type: application/sdp
Header Fields - Expires
Expires
Gives the relative time after which the message (or content) expires
For the REGISTER message

If the value of Expires fields
is 0, means this is the
DE-REGISTER request
Expires: 0
Header Fields - Max-Forwards & User-Agent
Max-Forwards: to limit the number of hops a request can
transit on the way to its destination
The error response is 483 (too many hops).
In request message
User-agent
contains information about the UAC originating the request
Example:
Max-Forwards: 70 Example:
User-agent: Flexit-IMS softphone V1.2D301
Header Fields - Extension Headers
Example
REGISTER sip:registrar.bplace.com SIP/2.0
Via: SIP/2.0/UDP 8.27.2.102:10226;branch=z9hG4bod840d0w
Via: SIP/2.0/UDP 8.27.22.224:5061;branch=z9hG4bKnashds7 ;received=192.0.2.4
To: B <sip:b@bplace.com>;
From: B <sip:b@bplace.com>;tag=456248
P-Access-Network-Info: 3GPP-UTRAN-TDD;utran-cell-id-3gpp=234151D0FCE
P-Visited-Network-ID: "8.27.2.102"
P-Charging-Vector: icid-value="8.27.2.102.3348465999.3157.14"
Call-ID: 217944815@8.27.22.224
CSeq: 1826 REGISTER
Contact: <sip:b@8.27.22.224:5061>;
Expires: 7200
Content-Length: 0
Some Extension Header Examples in
IMS
Extension Header Examples Function
P-Access-Network-Info Is used by the SIP UA to transfer access network
technologies to the service proxy
P-Visited-Network-ID Is used to relay the identification of the visited
domain to the registrar and proxy in the home realm
P-Charging-Vector Cooperates with the P-Charging-Function-Address
header field to transfer charging information over
the network
P-Asserted-Identity Formally indicate the calling party ID
Service-Route Used to inform the S-CSCF IP for P-CSCF during
Register
Path Used to inform the P-CSCF IP for S-CSCF during
Register
Contents
1. SIP Overview
2. SIP Protocol
Main Procedures in IMS Application
Registration
UA Registrar Server
register
200OK

Expires: 7200 SIP/2.0 200 OK
To: Bob<sip:bob@huawei.com>;tag=293k59kd
Expires: 7200
Session Setup/Release flow
Proxy
Server
UA1 UA2
INVITE
100 Trying
INVITE
100 Trying
180 Ring
180 Ring
200 OK
200 OK
ACK
ACK
RTP
BYE BYE
200 OK
200 OK
Media negotiation
caller UE callee UE
INVITEprovided by the first SDPrequired media type and all the codec
183first response from SDPsupported media type and the codec)
PRACKprovided by the second SDPnegotiated media type and the codec
200 OK( the second response from SDPconfirm to the media type and the codec negotiated)
Media negotiation
Offer & Answer example
Offer: Answer:
v=0 v=0
o=alice2890844526 2890844526 o=bob 2890844730 2890844730IN
IN IP4 host.anywhere.com IP4 host.example.com
s= s=
c=IN IP4 host.anywhere.com c=IN IP4 host.example.com
t=0 0 t=0 0
m=audio 49170 RTP/AVP 0 m=audio 49920 RTP/AVP 0
a=rtpmap:0 PCMU/8000 a=rtpmap:0 PCMU/8000
m=video 51372 RTP/AVP 31 m=video 0 RTP/AVP 31
a=rtpmap:31 H261/90000 m=video 53000 RTP/AVP 32
m=video 53000 RTP/AVP 32 a=rtpmap:32 MPV/90000.
a=rtpmap:32 MPV/90000
Route in IMS Session Signaling Flow
Important header
Route
Via
For response message routing
Record-route
For the following request routing
Example -- Request
Caller part Callee part

3.Invite 4.Invite
S-CSCF1 I-CSCF2 S-CSCF2

2.Invite 5.Invite
P-CSCF1 P-CSCF2
1.Invite 6.Invite
tom@home1.com ice@home2.com
(IP: 10.10.1.196) (IP: 10.10.1.197)
Route for the INVITE Request (1)
Request
1.invite (Caller---Calling PCSCF)
INVITE sip:ice@home2.hu SIP/2.0

Via:SIP/2.0/UDP 10.10.1.196:5060;BRANCH=8uetb
Max-Forwards:70
From:<sip:tom@home1.com>;tag=veli
To: <sip:ice@home2.hu SIP/2.0
Call-Id:sdgweituoweruoiweur
Cseq:12 INVITE
Contact:< sip: tom@10.10.1.196 :5060; transport=udp>
Request
2.invite (calling PCSCF------calling SCSCF)

Via:SIP/2.0/UDP pcscf1.visited1.fr;branch=9pctb
Via:SIP/2.0/UDP 10.10.1.196 :5060;branch=8uetb
Record-Route:<sip:pcscf1.visited1.fr;lr>
Route:<sip:orig@scscf1.home1.fr>
Max-Forwards:69
Cseq:12 INVITE
Request
3.invite (calling SCSCF-----called ISCSF)

Via:SIP/2.0/UDP scscf1.home1.fr;branch=agega1
Record-Route:<sip:scscf1.home1.fr;lr>
Max-Forwards:68
Cseq:12 INVITE
Request
4.invite (called ICSCF----called SCSCF)
Via:SIP/2.0/UDP icscf2.home1.fr;branch=geagi3
Route:<sip:scscf2.home2.hu;lr>
Max-Forwards:67
Cseq:12 INVITE
Request
5.invite (called SCSCF---called PCSCF)
Via:SIP/2.0/UDP scscf2.home2.hu;branch=cscth7
Record-Route:<sip:scscf2.home2.hu;lr>
Route:<sip:term@pcscf2.home2.hu;lr>
Max-Forwards:66
Cseq:12 INVITE
Request
6.invite (called PCSCF----callee)
INVITE sip: ice@10.10.1.197 :5060 SIP/2.0

Via:SIP/2.0/UDP pcscf2.home2.hu;branch=terdsf1
Record-Route: sip:pcscf2.home2.hu;lr
Max-Forwards:65
Cseq:12 INVITE
Contact:<sip: tom@10.10.1.196 :5060; transport=udp>
Route in IMS Session Signaling Flow -
Response
Example -- Response

4.183 3.183
S-CSCF1 I-CSCF2 S-CSCF2

5.183 2.183
P-CSCF1 P-CSCF2
6.183 1.183
(IP: 10.10.1.196) (IP: 10.10.1.197)
Response
1.183 (callee---CalledPCSCF)
SIP/2.0 183 Session in Progress

Via:SIP/2.0/UDP pcscf2.home2.hu;branch=terdsf1
Cseq:12 INVITE
Contact:<sip: ice@10.10.1.197:5060; transport=udp>
Response
2.183 (Called PCSCF----called SCSCF )
Via:SIP/2.0/UDP scscf2.home2.hu;branch=cscth7
Via:SIP/2.0/UDP 10.10.1.196:5060;branch=8uetb
Record-Route:<sip:pcscf2.home2.hu;lr>
Cseq:12 INVITE
Contact:<sip:ice@10.10.1.197:5060; transport=udp>
Response
3.183 (Called SCSCF-----called ICSCF)

Cseq:12 INVITE
Response
4.183 (Called ICSCF-----calling SCSCF)

Cseq:12 INVITE
Response
5.183 (Calling SCSCF------calling PCSCF)

Cseq:12 INVITE
Response
6.183 (Calling PCSCF-----caller )

Record-Route: sip:pcscf1.home2.hu;lr
Cseq:12 INVITE
Route in IMS Session Signaling Flow --
The Following Request
Example The following request
3.PRACK
S-CSCF1 S-CSCF2
2.PRACK 4.PRACK
I-CSCF2
P-CSCF1 P-CSCF2
1.PRACK 5.PRACK
(IP: 10.10.1.196) (IP: 10.10.1.197)
Step 3
PRACK (calling SCSCF---- Called SCSCF )
PRACK sip:ice@home2.hu SIP/2.0

Route:<sip:scscf2.home2.hu;lr>
Route:<sip:pcscf2.home2.hu;lr>
Cseq:12 INVITE
Contact:<sip:tom@10.10.1.196:5060
Summary
SIP is used to establish, modify and terminate a multimedia
conference, such as conference call over Internet. SIP can be
used to initiate sessions as well as inviting members to sessions
that have been advertised and established by other means.
SIP request messages: SIP messages sent by a client to the
server on the basis of designated operation for activation, which
include such messages as INVITE, PRACK, ACK, BYE, CANCEL,
UPDATE, etc.
SIP Response Messages: Used to display the status of the
requests sent by clients to the server, including the 1xx, 2xx, 3xx,
4xx, 5xx and 6xx.
The functions of each command in SIP call process should be
mastered as the key points.
Thank you
www.huawei.com

Ims 2

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Ims 2

Загружено:

Авторское право:

Доступные форматы

SIP Protocol

Copyright 2009 Huawei Technologies Co., Ltd. All rights reserved.

HUAWEI user manual- Solution-IMS Interfaces and

Know the message structure of SIP

Understand the header fields in IMS SIP

3. SIP Application in IMS

Setting up, controlling and tearing down sessions

SIP is an IETF protocol for multi-media sessions

Sessions including text, video, voice, etc.

SIP is one of the Internet protocol

Text based like HTTP

Widely used for successful Internet

Can be based on UDP/TCP/SCTP, most of the case now use UDP

SDP (Session Description Protocol)

Always is included in SIP message body

Session description (SDP) separated from Session management (SIP)

RTP (Real-time Transmission Protocol)

Media transmission e.g. voice, video

RTCP (Real-time Transmission Control Protocol)

Report and adjust the media transmission

User Agent SIP Request User Agent

SIP Response SIP Response

Media Stream (RTP)

Logical SIP entities are:

User Agents (UA) Network Servers

2 types of SIP URI

Full qualified domain name (FQDN) or IP address: It identifies a

3. SIP Application in IMS

2.2 Message structure

2.3 Header fields

INVITE: to initiate a session MESSAGE: is applied to IM

ACK: the response of INVITE SUBSCRIBE : to subscribe to a notify

Session setup Registration

Client A Proxy A Proxy B Client B Client A Proxy A

2.2 Message structure

2.3 Header fields

Example: INVITE sip:bob@huawei.com SIP/2.0

INVITE: for setting up sessions

ACK: for setting up sessions

CANCEL: for cancelling a session

BYE: for terminating sessions

OPTIONS: for querying servers about their capabilities

Request-URI: It indicates the user or service to which this request is

Via: SIP/2.0/UDP bobspc.huawei.com:5060;branch=z9hG4bKnashds7

Most implementations: SDP

SDP includes: Media to use; Media destination; Session name

SDP field have a required order

SDP Parameter Name Remarks

2.2 Message structure

2.3 Header fields

FROM: the logical identity of the initiator of the request,

SIP/2.0 180 Ringing

Present in INVITE, ACK, and REGISTER requests, success

SIP/2.0 180 Ringing

MUST contain a branch parameter: to identify the transaction

The acknowledgement request method for a provisional

100rel extension can be realized through the Supported

For the REGISTER message

3. SIP Application in IMS

REGISTER sip:registrar.huawei.com SIP/2.0

183first response from SDPsupported media type and the codec)

PRACKprovided by the second SDPnegotiated media type and the codec

For the following request routing