Scribd
Upload
35 views13 pages

SIP INVITE Message Breakdown Guide

The document discusses the structure and components of a SIP INVITE message. It is broken into two parts: 1. The start line contains the request type (INVITE), request URI, and SIP version. 2. The message headers provide routing, authentication, identification and session details. Key headers include Via, Max-Forwards, From, To, Call-ID, CSeq, Contact and Content-Type.

Uploaded by

俞一帆
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
35 views13 pages

SIP INVITE Message Breakdown Guide

The document discusses the structure and components of a SIP INVITE message. It is broken into two parts: 1. The start line contains the request type (INVITE), request URI, and SIP version. 2. The message headers provide routing, authentication, identification and session details. Key headers include Via, Max-Forwards, From, To, Call-ID, CSeq, Contact and Content-Type.

Uploaded by

俞一帆
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd

SIP

Agenda

SIP INVITE
SIP INVITE Message Body

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;ms-received-cid=B100>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(StartLine)
Request Line
RequestType: INVITE
Request-URI: sip:long@[Link];transport=tcp,
SIP URIAddress-of-Record(AOR)
SIP Version:2.0

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0

Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;


Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;ms-received-cid=B100>

Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100


Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
ViaSIP
ViaUA(User Agent)
ViaProxy
ViaUA

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;

Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;ms-received-cid=B100>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
Max-ForwardsSIP

Max-Forwards
Max-Forwards
70
Max-ForwardsSIP
483(Too Many Hops)

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;ms-received-cid=B100>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C

From:
<sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
From TagTo TagCall-IDdialogdialog
(Call)dialog
Call-ID
+@+IP

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;ms-received-cid=B100>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0

CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
CSeq: Command Sequence Number

CSeqREGISTERCSeq
32CSeq1
CSeq

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69

Contact: <sip:long@[Link];maddr=[Link];transport=tcp;>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
Contact: SIP/SIPS URIUA
UA
Record-Route
Contact
URI
ContactURIURI
<>

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100

Record-Route:
<sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB71394C
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
Record-Route:

Route
Record-Route
Record-Route

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB7
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE
Require: [Link]-multiparty

Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
Content-Type:
text/plainapplication/sdp
Content-Type
Content-Length:

SIPHTTP 1.1Chunked

SIP INVITE
INVITE sip:victor@[Link];transport=tcp SIP/2.0
Via: SIP/2.0/TCP [Link];branch=z9hG4bK381ACAFC.537D4376;branched=FALSE;
Max-Forwards: 69
Contact: <sip:long@[Link];maddr=[Link];transport=tcp;>
Via: SIP/2.0/TCP [Link]:11499;ms-received-port=2992;ms-received-cid=b100
Record-Route: <sip:[Link];transport=tcp>;tag=9B8AE5F9C759FB02F679AFD6CB7
From: <sip:long@[Link]>;tag=704b1683edd4438f85a34adb6201e078;epid=d9176cec0c
To: <sip:victor@[Link]>;epid=203e516cd9
Call-ID: d455d3faf197403482154b9a319f54e0
CSeq: 1 INVITE

Require: [Link]-multiparty
Content-Type: application/sdp
Content-Length: 134

SIP(Message Header)
Require:
UACRequireUAS

SIP INVITE Message Body


v=0
o=-0 0 IN IP4 [Link]
s=session
c=IN IP4 [Link]
t=0 0
m=message 5060 sip sip:victor@[Link]
Version Number,

Origin,/
Subject,
Connection Data,
Time,
Media(type, port, RTP/AVP Profile),

You might also like