Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
25
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
First, simulator for the IMS- consists of numbers of toolkits in service creation and
runtime environment- is chosen but it is expensive (this was a trademark of IBM).
Then another program was chosen, which is the SDS.
4.3.3 TESTING
In this stage the different applications are tested.
As mentioned in section 4.2 ICP is used to create client applications for the windows
(2000/XP) and symbian mobile device. It provides a run time core that runs as a
background service on the terminals, transparent to the client applications.
26
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
The SIP servlet API (SSA) is the solution by the Java Community Process (JCP) to
access the SIP protocol and used for creating applications which run on the SIP
Application Server (AS).
4.4.2 SCENARIO
User hamid sends a REGISTER request.
User hamid then receives 200 OK response.
User hamid sends a MESSAGE request which its body contains
''Hello,client:hamid!" to sip:greetings@ericsson.com to trigger the
specified server application.
Then server sends back 200 OK response.
Then the server sends to hamid a MESSAGE which its body contains
"Hello, World!"
Hamid responds with 200 OK.
Finally client application prints on the screen (console view in the SDS) the
received message "Hello, World!"
(2) 200 OK
(3) MESSAGE
(4) HSS lockup and DNS Query to
authorize the user and determine S-CSCF
(5) MESSAGE
(6) 200 OK
(7) 200 OK
(8) MESSAGE
(11) MESSAGE
(12) MESSAGE
(13) MESSAGE
(14) 200 OK
(15) 200 OK
(16) 200 OK
(17) 200 OK
27
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
SIP/2.0 200 OK
CSeq: 3347 REGISTER
Expires: 3600
Date: Sat, 5 Jul 2008 07:19:35 GMT
Content-Length: 0
Contact:<sip:hamid@127.0.0.1:5070>;pgm.service.icp=oma;expires=3600
;+g.helloworld.ericsson.com
P-Associated-URI: <sip:hamid@ericsson.com>
To: <sip:hamid@ericsson.com>;tag=2148
From: <sip:hamid@ericsson.com>;tag=23bd274-d12.732a
Call-ID: 7541-f-67ea5e@127.0.0.1
Via:SIP/2.0/UDP 127.0.0.1:5070;branch=z9hG4bK3346.732a.d12;
received_port_ext=5082;received=127.0.0.1
Service-Route: <sip:orig@127.0.0.1:5082;lr>
Figure 4.3 (2) 200 ok OF FIGUTRE 4.1
28
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
''Hello,client:hamid!"
Figure 4.4 (3) MESSAGE OF FIGUTRE 4.1
''Hello,client:hamid!"
Figure 4.5 (5) MESSAGE OF FIGUTRE 4.1
29
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
SIP/2.0 200 OK
CSeq: 3405 MESSAGE
Via:SIP/2.0/udp 127.0.0.1:5072;branch=z9hG4bK2dd7ac083713461bf6d4
2d9baecb35a1, SIP/2.0/UDP 127.0.0.1:5070;branch=z9hG4bK3347.66e9.d4c;
received_port_ext=5082;received=127.0.0.1
Record-Route: <sip:127.0.0.1:5072;from-tag=23b2a2c-d4c.66e9;lr>
Content-Length: 0
Call-ID: c90-48c1-40a96dc5@127.0.0.1
To: <sip:greetings@ericsson.com>;tag=fi9vy0kq-7
From: <sip:hamid@ericsson.com>;tag=23b2a2c-d4c.66e9
Figure 4.6 (6) 200 ok OF FIGUTRE 4.1
SIP/2.0 200 OK
CSeq: 3405 MESSAGE
Via:SIP/2.0/UDP 127.0.0.1:5070;branch=z9hG4bK3347.66e9.d4c
;received_port_ext=5082;received=127.0.0.1
Record-Route: <sip:127.0.0.1:5072;from-tag=23b2a2c-d4c.66e9;lr>
Content-Length: 0
Call-ID: c90-48c1-40a96dc5@127.0.0.1
To: <sip:greetings@ericsson.com>;tag=fi9vy0kq-7
From: <sip:hamid@ericsson.com>;tag=23b2a2c-d4c.66e9
Figure 4.7 (7) 200 ok OF FIGUTRE 4.1
30
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
-9227-2bdb6aa61f51
Content-Type: text/plain
Hello, World!
Figure 4.8 (8) 200 ok OF FIGUTRE 4.1
Hello, World!
Figure 4.9 (10) MESSAGE OF FIGUTRE 4.1
31
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
From: <sip:greetings@ericsson.com>;tag=fi9vy0kq-8
To: <sip:hamid@ericsson.com>
Call-ID: 127.0.0.1_4_3450536458975247396
Via:SIP/2.0/udp 127.0.0.1:5072;branch=z9hG4bKeeec75b749f79003be7a44299b
d85968,SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKb35c636d-941b
-4bd4-9227-2bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Content-Type: text/plain
Hello, World!
Figure 4.10 (11) MESSAGE OF FIGUTRE 4.1
Hello, World!
Figure 4.11: (12) MESSAGE OF FIGUTRE 4.1
32
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Hello, World!
Figure 4.12 (13) MESSAGE OF FIGUTRE 4.1
SIP/2.0 200 OK
CSeq: 1 MESSAGE
Via:SIP/2.0/udp 127.0.0.1:5072;branch=z9hG4bK931e983e97d1fc9070056277b1b
6d9d3,SIP/2.0/UDP127.0.0.1:5060;branch=z9hG4bKdcac699f-1414-4662-b0d8
b61259617ccb;received_port_ext=5072;received=127.0.0.1,SIP/2.0/udp
127.0.0.1:5072;branch=z9hG4bKeeec75b749f79003be7a44299bd85
968,SIP/2.0/UDP127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4-9227
2bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Content-Length: 0
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
From: <sip:greetings@ericsson.com>;tag=fi9vy0kq-8
33
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
To: <sip:hamid@ericsson.com>;tag=23be108-d53.3ae2
Figure 4.13 (14) 200 ok OF FIGUTRE 4.1
SIP/2.0 200 OK
CSeq: 1 MESSAGE
Via:SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKdcac699f-1414-4662-
b0d8-b61259617ccb;received_port_ext=5072;received=127.0.0.1,SIP/2.0/udp
127.0.0.1:5072;branch=z9hG4bKeeec75b749f79003be7a44299bd85968,
SIP/2.0/UDP127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4-9227
2bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Content-Length: 0
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
From: <sip:greetings@ericsson.com>;tag=fi9vy0kq-8
To: <sip:hamid@ericsson.com>;tag=23be108-d53.3ae2
Figure 4.14 (15) 200 ok OF FIGUTRE 4.1
SIP/2.0 200 OK
CSeq: 1 MESSAGE
Via:SIP/2.0/udp 127.0.0.1:5072;branch=z9hG4bKeeec75b749f79003be7a44299b
d85968,SIP/2.0/UDP127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4-
9227-2bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Content-Length: 0
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
To: <sip:hamid@ericsson.com>;tag=23be108-d53.3ae2
From: <sip:greetings@ericsson.com>;tag=fi9vy0kq-8
Figure 4.15 (16) 200 ok OF FIGUTRE 4.1
SIP/2.0 200 OK
CSeq: 1 MESSAGE
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4-
9227-2bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Content-Length: 0
34
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
To: <sip:hamid@ericsson.com>;tag=23be108-d53.3ae2
From: <sip:greetings@ericsson.com>;tag=fi9vy0kq-8
Figure 4.16 (17) 200 ok OF FIGUTRE 4.1
35
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Figure 4.2 show that, REGISTER request has contact header field
which contains the SIP URI of the user hamid and can be used later by
each request that its TO header field is <sip:hamid@ericsson.com>
consequently TO header field URI is not used to route the request. It is
intended for human consumption and for filtering purposes. For
example, a user can have a private URI and a professional URI and
filter requests depending on which URI appears in the To field. Also
EXPIRES header field contains time in seconds after which
registration is finished.
Figure 4.3 show that, 200 OK response has the same cseq (3347) of
that in figure 4.2 to indicates this a response to the request in figure 4.2
also observed that, P-ASSOCIATED-URI is added to the response and
it contains a list of URIs allocated to the user hamid and not
necessarily registered, in this case only one URI availale which is
<sip:hamid@ericsson.com>. Also response contains SERVICE
ROUTE header field which in normal case includes a list of SIP server
URIs. Future SIP requests that the IMS terminal sends will be routed
via these SIP servers, in addition to the P-CSCF in the IMS the
Service-Route header field value always contains the address of the S-
CSCF of the user but in this case in figure 4.3, it contains only the
address of the P-CSCF.
36
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
In figures 4.6 and 4.7 observed that, RECORD ROUTE header field is
inserted and it points to the S-CSCF to tell the user that S-CSCF wants
to remain in the signaling path.
In figure 4.1 observed that the sequence number 13 goes directly from
S-CSCF to the user hamid and it doesn't goes to P-CSCF and then to
the user, this because S-CSCF as mentioned inserts RECORD ROUTE
header fields but P-CSCF does not.
In figure 4.1 observed that, the sequences 13,14 and 15 have the same
value in the VIA header field because the sequences 14 and 15 are
response to the sequence 13 and responses follow the same path that
their corresponding requests traversed.
37
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
4.5.2 SCENARIO
VOIP call is done between two clients: hamid and his personal computer has IP
address 192.168.1.3with ports 5070 and salah with his personal computer has IP
address 192.168.1.2 and ports 5070.
38
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
(5) INVITE
(15) 200 OK
(16) 200 OK
(17) 200 OK
(18) 200 OK
(19) ACK
(20) ACK
CONVERSATION
(21) BYE
(22) BYE
(23) BYE
(24) 200 OK
(25) BYE
39
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
(26) BYE
(27) BYE
( 28) BYE
(29) BYE
(30) BYE
(31) BYE
(32) BYE
(33) BYE
(34) BYE
(35) BYE
(36) BYE
40
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Figure 4.19: Registrar in SDS indicates hamid registered his pubic URI
41
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
42
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Figure 4.23: console view in the SDS contains the SIP transactions
43
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
SIP/2.0 200 OK
CSeq: 30334 REGISTER
Expires: 3600
Date: Thu, 3 Jul 2008 10:14:15 GMT
Content-Length: 0
Contact: <sip:hamid@192.168.1.3:5070>;
pgm.service.icp=oma;g.ericsson.voip-p2p="true";expires=3600
P-Associated-URI: <sip:hamid@ericsson.com>
To: <sip:hamid@ericsson.com>;tag=1570
From: <sip:hamid@ericsson.com>;tag=2208a84-767d.39bd
Call-ID: 2e46-2f-2777c6@192.168.1.3
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK30333.39bd.767d;
received_port_ext=5081;received=192.168.1.3
44
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Contact: <sip:salah@192.168.1.2:5070>;
pgm.service.icp=oma;g.ericsson.voip-p2p="true";expires=3600
P-Associated-URI: <sip:salah@ericsson.com>
To: <sip:salah@ericsson.com>;tag=2008
From: <sip:salah@ericsson.com>;tag=21c1b84-6e28.20e8
Call-ID: 3b09-10-11e661@192.168.1.2
Via: SIP/2.0/UDP 192.168.1.2:5070;branch=z9hG4bK28200.20e8.6e28;
received_port_ext=5081;received=192.168.1.2
Figure 4.27: (4) 200 ok OF FIGURE 4.18
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
m=audio 10004 RTP/AVP 98
c=IN IP4 192.168.1.3
45
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.28: (5) INVITE OF FIGURE 4.18
SIP/2.0 100 Trying
CSeq: 29083 INVITE
Via: SIP/2.0/UDP
192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;received_port_ext=5081;receive
d=192.168.1.3
Content-Length: 0
Call-ID: 1e26-14551-7f09268c@192.168.1.3
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
To: <sip:salah@192.168.1.2:507>
Figure 4.29: (6) 100 TRYING OF FIGURE 4.18
INVITE sip:salah@192.168.1.2:5070 SIP/2.0
Max-Forwards: 69
Allow: INVITE,ACK,BYE,UPDATE
Supported: timer
CSeq: 29083 INVITE
Require: precondition
P-Called-Party-ID: <sip:salah@192.168.1.2:5070>
Content-Length: 225
session-expires: 1800
Contact: <sip:hamid@192.168.1.3:5070>;g.ericsson.voip-p2p="true"
Record-Route: <sip:192.168.1.3:5071;from-tag=21ea87c-719a.691e;lr>
Accept-Contact: *;g.ericsson.voip-p2p="true"
P-Asserted-Identity: <sip:hamid@ericsson.com>
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
To: <sip:salah@192.168.1.2:5070>
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK2035e878213245f39b
6bb1f9c8af92d1,SIP/2.0/UDP192.168.1.3:5070;branch=z9hG4bK28814.69
1e.719a;received_port_ext=5081;received=192.168.1.3
Content-Type: application/sdp
46
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
m=audio 10004 RTP/AVP 98
c=IN IP4 192.168.1.3
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.30: (7) INVITE OF FIGURE 4.18
SIP/2.0 100 Trying
CSeq: 29083 INVITE
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK2035e878213245f39b6bb1f
9c8af92d1,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
received_port_ext=5081;received=192.168.1.3
Content-Length: 0
Max-Forwards: 70
Call-ID: 1e26-14551-7f09268c@192.168.1.3
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
To: <sip:salah@192.168.1.2:5070>
Figure 4.31: (8) 100 TRYNG OF FIGURE 4.18
SIP/2.0 180 Ringing
Max-Forwards: 70
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29083 INVITE
Content-Length: 0
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK2035e878213245f39b6bb
47
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
1f9c8af92d1,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
received_port_ext=5081;received=192.168.1.3
Figure 4.32: (9) 180 RINGING OF FIGURE 4.18
SIP/2.0 180 Ringing
Max-Forwards: 70
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29083 INVITE
Content-Length: 0
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
received_port_ext=5081;received=192.168.1.3
Figure 4.33: (10) 180 RINGING OF FIGURE 4.18
SIP/2.0 183 Session Progress
Max-Forwards: 70
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29083 INVITE
Content-Length: 225
Record-Route: <sip:192.168.1.3:5071;from-tag=21ea87c-719a.691e;lr>
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Content-Type: application/sdp
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK2035e878213245f39b6bb1
f9c8af92d1,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
received_port_ext=5081;received=192.168.1.3
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
48
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 10006 RTP/AVP 98
c=IN IP4 192.168.1.2
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.34: (11) 183 SESSION PROGRESS OF FIGURE 4.18
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 10006 RTP/AVP 98
c=IN IP4 192.168.1.2
a=sendrecv
a=rtpmap:98 AMR/8000/1
49
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.35: (12) 183 SESSION PROGRESS OF FIGURE 4.18
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
m=audio 10004 RTP/AVP 98
c=IN IP4 192.168.1.3
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.36: (13) UPDATE OF FIGURE 4.18
50
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
m=audio 10004 RTP/AVP 98
c=IN IP4 192.168.1.3
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.37: (14) UPDATE OF FIGURE 4.18
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29084 UPDATE
session-expires: 1800;refresher=uas
Content-Length: 225
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
51
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Content-Type: application/sdp
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bKdfe9c38b63b824f92a8efa39
bcb9b74b,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28815.3d16.71a1;
received_port_ext=5081;received=192.168.1.3
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 10006 RTP/AVP 98
c=IN IP4 192.168.1.2
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.38: (15) 200 OK OF FIGURE 4.18
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29084 UPDATE
session-expires: 1800;refresher=uas
Content-Length: 225
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Content-Type: application/sdp
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28815.3d16.71a1;
received_port_ext=5081;received=192.168.1.3
52
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
m=audio 10006 RTP/AVP 98
c=IN IP4 192.168.1.2
a=sendrecv
a=rtpmap:98 AMR/8000/1
a=fmtp:98 mode-set=0,1,2,3,4,5,6,7;octet-align=1
Figure 4.39: (16) 200 OK OF FIGURE 4.18
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29083 INVITE
session-expires: 1800;refresher=uas
Content-Length: 0
Record-Route: <sip:192.168.1.3:5071;from-tag=21ea87c-719a.691e;lr>
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK2035e878213245f39b6bb1f
9c8af92d1,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
received_port_ext=5081;received=192.168.1.3
Figure 4.40: (17) 200 OK OF FIGURE 4.18
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
53
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
Allow: INVITE,ACK,BYE,UPDATE
CSeq: 29083 INVITE
session-expires: 1800;refresher=uas
Content-Length: 0
Record-Route: <sip:192.168.1.3:5071;from-tag=21ea87c-719a.691e;lr>
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
Accept-Contact: *;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
received_port_ext=5081;received=192.168.1.3
Figure 4.41: (18) 200 OK OF FIGURE 4.18
54
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
From: <sip:hamid@ericsson.com>;tag=21ea87c-719a.691e
Figure 4.43: (20) 200 OK OF FIGURE 4.18
NOTE:
The SIP messages of the sequences from 21 to 37 in figure 4.18 are in APPENDIX B.
55
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
In figure 4.28 observed that ALLOW header field is inserted which lets
user agents to advertise the methods they support, but cannot be used
to express that a particular method is required for a particular dialog
also in figure 4.28 there are SUPPORTED and REQUIRE header
fields this because When a SIP dialog is being established the user
agent client lists all the names of the extensions it wants to use for that
dialog in a REQUIRE header field, and all the names of the extensions
it supports not listed previously in a SUPPORTED header field. Also
CONTENT TYPE header field is inserted and as shown in the figure it
contains the phrase ''application/sdp'', and that is mean the body of the
SIP message contains a description of the multimedia session using
session description protocol (SDP). SDP description consists of two
parts: session-level information and media-level information. ''V'' used
for Protocol version, ''o'': Owner of the session and session identifier
and it points to the IP address 192.168.1.3 which is the address of the
user hamid who sends the INVITE request, ''s'': name of the session, ''t''
time when the session is active and t=0 0 means this session is
supposed to take place at the moment this session description is
received, ''m'' media line and as shown in figure 4.28 it points media is
audio and this expected because the application is VOIP call also
contains the port number where these media can be received and the
transport protocol to use, either the User Datagram Protocol (UDP) or
Real-time Transport Protocol Audio and Video Profile (RTP/AVP)
Also character "a" indicates that the streams are bidirectional (i.e.,
users send and receive media) and this also expected because of the
VOIP call also ''a=rtpmap'' indicates that the codec name is AMR
56
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
57
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
58
CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
59