Developing Sip and Ims Applications (Ch4)

CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS
4.1 REQUIRED MATERIALS:

Some materials and requirements must be incorporated into the implementation and
testing. The following discusses the component necessary to fulfill the project
requirements.
4.1.1 SOFTWARE REQUIREMENTS

The software requirements for the applications are:
 Service Development Studio (SDS) 4.0
 Java 2 standard edition (J2SE)
 Java runtime environment (JRE)
4.1.2 HARDEWARE REQUIREMENTS

The hardware requirements for the applications are:
 Peer-to-peer network consist of two personal computers with microphones
and handsets for the voice over internet protocol (VOIP) application
4.2 OVERVIEW OF SDS [5]

The Service Development Studio (SDS) is a development environment based on the
Eclipse platform. It provides end-to-end support for the design, coding, and testing of
Value Added Services that leverage the capabilities of the IP Multimedia Subsystem
(IMS).
 Ericsson’s Service Development Studio provides end-to-end support for
design, coding, and testing of both the client side and the server side IMS
applications.
 SDS contains emulation of deployment environments for both the terminal
side (initially Symbian phones) and the server side (Session Initiation
Protocol Application Server (SIP AS)).
 SDS includes the IMS Client Platform (ICP), which is a client platform for
open terminal operating systems. ICP provides a high-level Application
Programming Interface (API) to develop client applications.
 SDS is a part of Ericsson’s IMS system and is verified and released with
each new Ericsson IMS System release.
25
4.3 WORK STRATEGY

To achieve the objectives of the project, there are three stages:
4.3.1 RESEARCH AND DATA GATHERING

The aim of the research is to know more about the IMS, its applications and the SIP
applications also to find the best simulator of the IMS system to develop the specified
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.2 DEVELOPING THE CODE OF THE APPLICATION

The code of applications is written using java programming language.
4.3.3 TESTING
In this stage the different applications are tested.
4.4 DEVELOPING CLIENT / SERVER APPLICATION:

The client points to a personal computer with windows operating system into which
client application is installed and the server points to the SIP AS (one of the main
components in the SDS) into which the sever application is deployed after been
created.
4.4.1 THE CODE OF THE APPLICATION

Both client application and server application are written using java programming
language (see APPENDIX A).
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
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!"
Hamid P-CSCF HSS DNS S-CSCF SIP-AS

(1) REGISTER
(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
(9) HSS lockup for security and

authorization information (10) MESSAGE
(11) MESSAGE
(12) MESSAGE
(13) MESSAGE
(14) 200 OK
(15) 200 OK
(16) 200 OK
(17) 200 OK
Figure 4.1 SIP sequence diagram for client/server application
27
4.4.3 RESULTS OF RUNNING CLIENT APPLICATION

REGISTER sip:ericsson.com SIP/2.0
Max-Forwards: 70
Supported: path
CSeq: 3347 REGISTER
Expires: 3600
Content-Length: 0
Contact:<sip:hamid@127.0.0.1:5070>;expires=3600
;+g.helloworld.ericsson.com;pgm.service.icp=oma
To: <sip:hamid@ericsson.com>
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
Figure 4.2 (1) REGISTER OF FIGUTRE 4.1
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
MESSAGE sip:greetings@ericsson.com SIP/2.0

Max-Forwards: 70
28
CSeq: 3405 MESSAGE

Content-Length: 15
Accept-Contact: *;+g.helloworld.ericsson.com
To: <sip:greetings@ericsson.com>
From: <sip:hamid@ericsson.com>;tag=23b2a2c-d4c.66e9
Route: <sip:orig@127.0.0.1:5082;lr>
Call-ID: c90-48c1-40a96dc5@127.0.0.1
Content-Type: text/plain
Via: SIP/2.0/UDP 127.0.0.1:5070;branch=z9hG4bK3347.66e9.d4c
''Hello,client:hamid!"
Figure 4.4 (3) MESSAGE OF FIGUTRE 4.1
MESSAGE sip:greetings@ericsson.com SIP/2.0

Max-Forwards: 69
CSeq: 3405 MESSAGE
Content-Length: 15
Record-Route: <sip:127.0.0.1:5072;from-tag=23b2a2c-d4c.66e9;lr>
P-Asserted-Identity: <sip:hamid@ericsson.com>
Route:<sip:mydomain.com;lr;call=orig>,<sip:127.0.0.1:5072;lr;
original-dialog-id=z9hG4bK2dd7ac083713461bf6d42d9baecb35a1-
MESSAGE>
To: <sip:greetings@ericsson.com>
Call-ID: c90-48c1-40a96dc5@127.0.0.1
Via:SIP/2.0/udp 127.0.0.1:5072;branch=z9hG4bK2dd7ac083713461bf6d42d9ba
ecb35a1, SIP/2.0/UDP 127.0.0.1:5070;branch=z9hG4bK3347.66e9.d4c;
''Hello,client:hamid!"
29
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;
Content-Length: 0
Call-ID: c90-48c1-40a96dc5@127.0.0.1
To: <sip:greetings@ericsson.com>;tag=fi9vy0kq-7
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
Content-Length: 0
Call-ID: c90-48c1-40a96dc5@127.0.0.1
To: <sip:greetings@ericsson.com>;tag=fi9vy0kq-7
MESSAGE sip:hamid@ericsson.com SIP/2.0

Max-Forwards: 69
CSeq: 1 MESSAGE
Content-Length: 13
P-Asserted-Identity: sip:helloworld@ericsson.com
From: <sip:greetings@ericsson.com>;tag=fi9vy0kq-8
Route: <sip:127.0.0.1:5072>
Call-ID: 127.0.0.1_4_3450536458975247396
Via:SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4
30
-9227-2bdb6aa61f51
Hello, World!

Max-Forwards: 69
CSeq: 1 MESSAGE
Content-Length: 13
Route: <sip:127.0.0.1:5072>
Call-ID: 127.0.0.1_4_3450536458975247396
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4-
9227-2bdb6aa61f51
Hello, World!

Max-Forwards: 68
CSeq: 1 MESSAGE
P-Called-Party-ID: <sip:hamid@ericsson.com>
Content-Length: 13
Record-Route: <sip:127.0.0.1:5072;from-tag=fi9vy0kq-8;lr>
Route: <sip:mydomain.com;lr;call=term_registered>,<sip:127.0.0.1:5072;lr;
original-dialog-id=z9hG4bKeeec75b749f79003be7a44299bd85968-
MESSAGE>
31
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
Hello, World!

Max-Forwards: 67
CSeq: 1 MESSAGE
Content-Length: 13
Route:<sip:127.0.0.1:5072;lr;original-dialog
id=z9hG4bKeeec75b749f79003be7a44299bd 85968-MESSAGE>
Call-ID: 127.0.0.1_4_3450536458975247396
Via: SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKdcac699f-1414
-4662-b0d8-b61259617ccb,SIP/2.0/udp 127.0.0.1:5072;
branch=z9hG4bKeeec75b749f79003be7a44299bd85968,
SIP/2.0/UDP 127.0.0.1:5060;branch=z9hG4bKb35c636d-941b
-4bd4-9227-2bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Hello, World!
Figure 4.11: (12) MESSAGE OF FIGUTRE 4.1
32
MESSAGE sip:hamid@127.0.0.1:5070 SIP/2.0

Max-Forwards: 66
CSeq: 1 MESSAGE
Content-Length: 13
Call-ID: 127.0.0.1_4_3450536458975247396
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=z9hG4bKeeec75b749f79003be7a44299bd85968,SIP/2.0/
UDP127.0.0.1:5060;branch=z9hG4bKb35c636d-941b-4bd4-
92272bdb6aa61f51;received_port_ext=5072;received=127.0.0.1
Hello, World!
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
Content-Length: 0
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
33
To: <sip:hamid@ericsson.com>;tag=23be108-d53.3ae2
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
Content-Length: 0
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
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
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
Max-Forwards: 70
Call-ID: 127.0.0.1_4_3450536458975247396
Figure 4.17: client application prints "Hello, World!" message
4.4.4 CONFIGURATIONS USED IN THE IMPLEMENTATION OF

THE ABOVE APPLICATION
 IP address of the S-CSCF 127.0.0.0 and the port 5072.
 IP address of the P-CSCF 127.0.0.0 and the port 5082.
 Contact address of the user <hamid@127.0.0.0:5070>.
 +g.helloworld.ericsson.com is the service identifier.
 In the domain name server (DNS), IP address of 127.0.0.0 with the port
5060 (IP address of the SIP AS) has the name <sip: mydomain.com>.
35
4.4.5 ANALYSIS OF THE RESULTS IN SECTION 4.4.3
 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.
 In figure 4.1 sequence number 4 show that the P-CSCF communicates

with the HSS and DNS to authorize the user and to determine S-CSCF
which allocated to the user.
 Figure 4.4 contains ACCEPT CONTACT header field which indicates

to accept session if the other end has +g.helloworld.ericsson.com
service.
36
 In figure 4.5 observed that, P-CSCF inserts P-ASSERTED IDENTITY

which contains authenticated and registered public user identity of the
user. The S-CSCF will also check the authentication and registration of
the public user identity indicated in the header (sequence number 9 in
figure 4.1). Because of these checks, the header serves as the main
identification of the user for the whole dialog. Also in figure 4.5
observed that S-CSCF inserts RECORD ROUTE header field which
indicates that the S-CSCF wants to remain in the signaling path for
subsequent SIP signaling and also observed that the S-CSCF inserts in
the MESSAGE request a Route header field that points to the AS in the
first place and the S-CSCF in the second place (also the same thing
happens in the sequence number 11 in figure 4.1). This is to allow the
AS to forward the request back to the same S-CSCF and this is happen
actually as shown in the sequence number 8 in figure 4.1
 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
4.5 DEVELOPING VOIP CALL (CLIENT/CLIENT

APPLICATION)
This application needs peer-to-peer network with two personal computers (clients)
each client supports the software mentioned in section 4.1.1 in addition to the client
application which installed in the both clients.
4.5.1 THE CODE OF THE APPLICATION

Client application is written using java programming language (see APPENDIX A).
In the code user graphic interface (GUI) is used, because of the buttons used in the
call (Callee URI button, Call button, End button …).
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.
1. Both clients hamid and salah register their public identity.
2. Then hamid makes a call by writing the contact address of salah

and then press Call Button, immediately a message appear to
hamid saying that ''ReadyprocessRemoteAlerting''.
3. Then salah receives a message that indicates there is a process

invitation and other message to accept or reject the incoming call,
salah then accepts call by pressing Yes Button.
4. Then immediately both clients receive a message saying that

''processcallconnected'' and now hamid can talk to salah and vice
versa.
38
hamid P-CSCF1 S-CSCF1 S-CSCS2 P-CSCF2 salah

(1) REGISTER (3) REGISTER
(2) 200 OK (4) 200 OK
(5) INVITE
(6) 100 TRYING

(7) INVITE
(8) 100 TRYING
(9) 180 RINGING

(10) 180 RINGING
(11) 183 SESSION PROGRESS
(12) 183 SESSION
PROGRESS
(13) UPDATE
(14) UPDATE
(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
(26) BYE
(27) BYE
( 28) BYE
(29) BYE
(30) BYE
(31) BYE
(32) BYE
(33) BYE
(34) BYE
(35) BYE
(36) BYE
(37) 408 REQUEST TIME

OUT
Figure 4.18: SIP sequence diagram for VOIP call
40
Figure 4.19: Registrar in SDS indicates hamid registered his pubic URI
Figure 4.20: result of number 2 in section 4.5.2
41
42
Figure 4.23: console view in the SDS contains the SIP transactions
4.5.3 RESULTS OF THE IMPLEMENTATION OF THE VOIP

CALL (RESULTANT SIP MESSAGES)

Max-Forwards: 70
Supported: path
CSeq: 30334 REGISTER
Expires: 3600
Content-Length: 0
Contact: <sip:hamid@192.168.1.3:5070>;expires=3600;
g.ericsson.voip-p2p="true";pgm.service.icp=oma
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
Figure 4.24 (1) REGISTER OF FIGURE 4.18
43
SIP/2.0 200 OK
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;
Figure 4.25: (2) 200 ok OF FIGURE 4.18

Max-Forwards: 70
Supported: path
Expires: 3600
Content-Length: 0
Contact: <sip:salah@192.168.1.2:5070>;expires=3600;g.ericsson.voip-
p2p="true";pgm.service.icp=oma
To: <sip:salah@ericsson.com>
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
Figure 4.26: (3) REGISTER OF FIGURE 4.18
SIP/2.0 200 OK
Expires: 3600
Date: Thu, 3 Jul 2008 10:03:22 GMT
Content-Length: 0
44
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;
Figure 4.27: (4) 200 ok OF FIGURE 4.18
INVITE sip:salah@192.168.1.2:5070 SIP/2.0

Max-Forwards: 70
Allow: INVITE,ACK,BYE,UPDATE
Supported: timer
CSeq: 29083 INVITE
Require: precondition
session-expires: 1800
Content-Length: 225
"Contact: <sip:hamid@192.168.1.3:5070>;g.ericsson.voip-p2p="true
"Accept-Contact: *;g.ericsson.voip-p2p="true
>To: <sip:salah@192.168.1.2:5070>
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=z9hG4bK28814.691e.719a
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
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
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
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>
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
46
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
c=IN IP4 192.168.1.3
a=sendrecv
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;
Content-Length: 0
Max-Forwards: 70
Call-ID: 1e26-14551-7f09268c@192.168.1.3
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
CSeq: 29083 INVITE
Content-Length: 0
Contact: <sip:salah@192.168.1.2:5070>;g.ericsson.voip-p2p="true"
To: <sip:salah@192.168.1.2:5070>;tag=21cc340-7315.29
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK2035e878213245f39b6bb
47
1f9c8af92d1,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
Figure 4.32: (9) 180 RINGING OF FIGURE 4.18
SIP/2.0 180 Ringing
Max-Forwards: 70
CSeq: 29083 INVITE
Content-Length: 0
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28814.691e.719a;
Figure 4.33: (10) 180 RINGING OF FIGURE 4.18
SIP/2.0 183 Session Progress
Max-Forwards: 70
CSeq: 29083 INVITE
Content-Length: 225
Call-ID: 1e26-14551-7f09268c@192.168.1.3
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;
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
48
s=-
c=IN IP4 192.168.1.2
t=0 0
c=IN IP4 192.168.1.2
a=sendrecv
Figure 4.34: (11) 183 SESSION PROGRESS OF FIGURE 4.18
SIP/2.0 183 Session Progress

Max-Forwards: 70
CSeq: 29083 INVITE
Content-Length: 225
Call-ID: 1e26-14551-7f09268c@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
c=IN IP4 192.168.1.2
a=sendrecv
49
Figure 4.35: (12) 183 SESSION PROGRESS OF FIGURE 4.18
UPDATE sip:salah@192.168.1.2:5070 SIP/2.0

Max-Forwards: 70
Supported: timer
CSeq: 29084 UPDATE
Content-Length: 225
Route: <sip:192.168.1.3:5071;from-tag=21ea87c-719a.691e;lr>
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28815.3d16.71a1
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
c=IN IP4 192.168.1.3
a=sendrecv
Figure 4.36: (13) UPDATE OF FIGURE 4.18
UPDATE sip:salah@192.168.1.2:5070 SIP/2.0

Max-Forwards: 69
Supported: timer
50
CSeq: 29084 UPDATE

Content-Length: 225
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bKdfe9c38b63b824f92a8efa39bc
b9b74b,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28815.3d16.71a1;
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.3
s=-
c=IN IP4 192.168.1.3
t=0 0
c=IN IP4 192.168.1.3
a=sendrecv
Figure 4.37: (14) UPDATE OF FIGURE 4.18
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
CSeq: 29084 UPDATE
session-expires: 1800;refresher=uas
Content-Length: 225
51
Call-ID: 1e26-14551-7f09268c@192.168.1.3
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;
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
c=IN IP4 192.168.1.2
a=sendrecv
Figure 4.38: (15) 200 OK OF FIGURE 4.18
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
CSeq: 29084 UPDATE
Content-Length: 225
Call-ID: 1e26-14551-7f09268c@192.168.1.3
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28815.3d16.71a1;
52
v=0
o=- 1111551202156 1111551202156 IN IP4 192.168.1.2
s=-
c=IN IP4 192.168.1.2
t=0 0
c=IN IP4 192.168.1.2
a=sendrecv
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
CSeq: 29083 INVITE
Content-Length: 0
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;
SIP/2.0 200 OK
Max-Forwards: 70
Supported: timer
53
CSeq: 29083 INVITE
Content-Length: 0
Call-ID: 1e26-14551-7f09268c@192.168.1.3
ACK sip:salah@192.168.1.2:5070 SIP/2.0

Route: <sip:192.168.1.3:5071;from-tag=21ea87c-719a.691e;lr>
CSeq: 29083 ACK
Via: SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28816.2ecb.71e5
Content-Length: 0
Max-Forwards: 70
Call-ID: 1e26-14551-7f09268c@192.168.1.3
ACK sip:salah@192.168.1.2:5070 SIP/2.0

CSeq: 29083 ACK
Via: SIP/2.0/udp 192.168.1.3:5071;branch=z9hG4bK1b8003fe4dce3156565227a6bc
8702ea,SIP/2.0/UDP 192.168.1.3:5070;branch=z9hG4bK28816.2ecb.71e5;
Max-Forwards: 69
Content-Length: 0
Call-ID: 1e26-14551-7f09268c@192.168.1.3
54
NOTE:
The SIP messages of the sequences from 21 to 37 in figure 4.18 are in APPENDIX B.
55
4.5.4 ANALYSIS OF THE RESULTS IN SECTION 4.5.3

 In figures 4.25 and 4.27 observed that P-ASSOCIATED-URI header
field is inserted and it points to the all URI allocated to the specified
user even not registered. In the VOIP application hamid and salah each
one of them has only one URI which listed in the P-ASSOCIATED-
URI header field.
 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
(narrowband speech codec). The c-line indicates Address type – there

are two address types, IP4 or IP6 and network address – this parameter
identifies the IP address or domain name where media are received
also in figure 4.28 in the message body the character ''o'' indicates that
the owner is hamid and consequently the session description in the
message body is generated by hamid. In order to know when all the
preconditions are met both user agents need to exchange session
descriptions and observed that the session description in the body of
the SIP message in figure 4.34 is generated by salah as indicated by
"o" character.
 Sequence number 8 in figure 4.18 is Provisional response indicates that

the associated request (i.e. (5) invite) was received and being
processed. Upon receipt of a provisional response, the request sender
(hamid) should stop retransmitting the request.
 In figure 4.18, sequence number 11 (183 Session Progress response)

traverses, according to SIP procedures to route responses, the same set
of proxies that the corresponding INVITE request traversed VIA and
RECORD-ROUTE header field contain the values that the IMS
terminal should have used in a response to the INVITE request.
 In figure 4.18 sequences number 15 and 16 tell hamid that UPDATE

request is received and sequences 17 and 18 are response to the
INVITE request and sequences 19 and 20 indicates that final response
(i.e. (18) OK) is received.
 In figure 4.18 observed that in sequence number 21 indicates that salah

ends the call by sending BYE request to hamid but salah as shown in
the figure resends the BYE request (because he does not receive 200
OK response from hamid) until its proxy sends him response that the
time of request is out.
57
58
59

Developing Sip and Ims Applications (Ch4)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Developing Sip and Ims Applications (Ch4)

Enviado por

Direitos autorais:

Formatos disponíveis

CHAPTER 4 DEVELOPING SIP AND IMS APPLICATIONS

4.1 REQUIRED MATERIALS:

4.1.1 SOFTWARE REQUIREMENTS

4.1.2 HARDEWARE REQUIREMENTS

4.2 OVERVIEW OF SDS [5]

4.3 WORK STRATEGY

4.3.1 RESEARCH AND DATA GATHERING

4.3.2 DEVELOPING THE CODE OF THE APPLICATION

4.4 DEVELOPING CLIENT / SERVER APPLICATION:

4.4.1 THE CODE OF THE APPLICATION

Hamid P-CSCF HSS DNS S-CSCF SIP-AS

(9) HSS lockup for security and

Figure 4.1 SIP sequence diagram for client/server application

4.4.3 RESULTS OF RUNNING CLIENT APPLICATION

MESSAGE sip:greetings@ericsson.com SIP/2.0

CSeq: 3405 MESSAGE

MESSAGE sip:greetings@ericsson.com SIP/2.0

MESSAGE sip:hamid@ericsson.com SIP/2.0

MESSAGE sip:hamid@ericsson.com SIP/2.0

MESSAGE sip:hamid@ericsson.com SIP/2.0

MESSAGE sip:hamid@ericsson.com SIP/2.0

MESSAGE sip:hamid@127.0.0.1:5070 SIP/2.0

Figure 4.17: client application prints "Hello, World!" message

4.4.4 CONFIGURATIONS USED IN THE IMPLEMENTATION OF

4.4.5 ANALYSIS OF THE RESULTS IN SECTION 4.4.3

 In figure 4.1 sequence number 4 show that the P-CSCF communicates

 Figure 4.4 contains ACCEPT CONTACT header field which indicates

 In figure 4.5 observed that, P-CSCF inserts P-ASSERTED IDENTITY

4.5 DEVELOPING VOIP CALL (CLIENT/CLIENT

4.5.1 THE CODE OF THE APPLICATION

1. Both clients hamid and salah register their public identity.

2. Then hamid makes a call by writing the contact address of salah

3. Then salah receives a message that indicates there is a process

4. Then immediately both clients receive a message saying that

hamid P-CSCF1 S-CSCF1 S-CSCS2 P-CSCF2 salah

(2) 200 OK (4) 200 OK

(6) 100 TRYING

(8) 100 TRYING

(9) 180 RINGING

(37) 408 REQUEST TIME

Figure 4.18: SIP sequence diagram for VOIP call

Figure 4.20: result of number 2 in section 4.5.2

Figure 4.21: result of number 3 in section 4.5.2

Figure 4.22: result of number 4 in section 4.5.2

4.5.3 RESULTS OF THE IMPLEMENTATION OF THE VOIP

REGISTER sip:ericsson.com SIP/2.0

Figure 4.24 (1) REGISTER OF FIGURE 4.18

Figure 4.25: (2) 200 ok OF FIGURE 4.18

INVITE sip:salah@192.168.1.2:5070 SIP/2.0

SIP/2.0 183 Session Progress

UPDATE sip:salah@192.168.1.2:5070 SIP/2.0

UPDATE sip:salah@192.168.1.2:5070 SIP/2.0

CSeq: 29084 UPDATE

ACK sip:salah@192.168.1.2:5070 SIP/2.0

ACK sip:salah@192.168.1.2:5070 SIP/2.0

4.5.4 ANALYSIS OF THE RESULTS IN SECTION 4.5.3

(narrowband speech codec). The c-line indicates Address type – there

 Sequence number 8 in figure 4.18 is Provisional response indicates that

 In figure 4.18, sequence number 11 (183 Session Progress response)

 In figure 4.18 sequences number 15 and 16 tell hamid that UPDATE

 In figure 4.18 observed that in sequence number 21 indicates that salah

Você também pode gostar