Menu
▾
▴
Re: [Sipp-users] Not able to Complete call using SIPp and Opensips as Proxy server
|
From: Mayur K. <may...@gm...> - 2017-08-10 11:28:49
|
Hi Pavel,
Thanks for correcting me. With your inputs now I am able to send ACK and
BYE from sippclient(192.168.100.93:5065) to the Server (192.168.100.21:5070)
via the Opensips proxy server (192.168.100.93:5060).
I tried ereg and setdest like :
<nop>
<action>
<assignstr assign_to="url" value="[next_url]" />
<ereg regexp="sip:.*@([0-9A-Za-z\.]+):([0-9]+);transport=([A-Z]+)"
search_in="var" check_it="true" assign_to="dummy,host,port,transport"
variable="url" />
<setdest host="[$host]" port="[$port]" protocol="[$transport]" />
</action>
</nop>
but somehow that did not worked so I had done hardcoding as mentioned
below :
<action>
<assignstr assign_to="host" value="192.168.100.21" />
<assignstr assign_to="port" value="5070" />
<assignstr assign_to="transport" value="UDP" />
<setdest host="[$host]" port="[$port]" protocol="[$transport]" />
</action>
This did work and I was able to send ACK and BYE to the Server but a
problem still persists.
*The server used to send 200OK after the BYE which was not received in the
client side. *
Not sure how it is missing.
Request your help with the same.
Please see my files uac.xml, uas.xml Client side logs and server logs
below for a single call :
*uac.xml*
<scenario name="Basic Sipstone UAC">
<!-- In client mode (sipp placing calls), the Call-ID MUST be -->
<!-- generated by sipp. To do so, use [call_id] keyword.
-->
<send retrans="500">
<![CDATA[
INVITE sip:[service]@[remote_ip]:[remote_port] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:sipp@[local_ip]:[local_port]>;tag=[call_number]
To: sut <sip:[service]@[remote_ip]:[remote_port]>
Call-ID: [call_id]
CSeq: 1 INVITE
Contact: sip:sipp@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: [len]
v=0
o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip]
s=-
c=IN IP[media_ip_type] [media_ip]
t=0 0
m=audio [media_port] RTP/AVP 0
a=rtpmap:0 PCMU/8000
]]>
</send>
<recv response="100"
optional="true">
</recv>
<recv response="180" optional="true">
</recv>
<!-- By adding rrs="true" (Record Route Sets), the route sets -->
<!-- are saved and used for following messages sent. Useful to test -->
<!-- against stateful SIP proxies/B2BUAs. -->
<recv response="200" rtd="true">
<action>
<assignstr assign_to="host" value="192.168.100.21" />
<assignstr assign_to="port" value="5070" />
<assignstr assign_to="transport" value="UDP" />
<setdest host="[$host]" port="[$port]" protocol="[$transport]" />
</action>
</recv>
<!-- Packet lost can be simulated in any send/recv message by -->
<!-- by adding the 'lost = "10"'. Value can be [1-100] percent. -->
<send>
<![CDATA[
ACK sip:[service]@[remote_ip]:[remote_port] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:sipp@[local_ip]:[local_port]>;tag=[call_number]
To: sut <sip:[service]@[remote_ip]:[remote_port]>[peer_tag_param]
Call-ID: [call_id]
CSeq: 1 ACK
Contact: sip:sipp@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
]]>
</send>
<!-- This delay can be customized by the -d command-line option -->
<!-- or by adding a 'milliseconds = "value"' option here. -->
<pause/>
<!-- The 'crlf' option inserts a blank line in the statistics report. -->
<send retrans="500">
<![CDATA[
BYE sip:[service]@[remote_ip]:[remote_port] SIP/2.0
Via: SIP/2.0/[transport] [local_ip]:[local_port];branch=[branch]
From: sipp <sip:sipp@[local_ip]:[local_port]>;tag=[call_number]
To: sut <sip:[service]@[remote_ip]:[remote_port]>[peer_tag_param]
Call-ID: [call_id]
CSeq: 2 BYE
Contact: sip:sipp@[local_ip]:[local_port]
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
]]>
</send>
<recv response="200" crlf="true">
</recv>
<!-- definition of the response time repartition table (unit is ms) -->
<ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/>
<!-- definition of the call length repartition table (unit is ms) -->
<CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000"/>
</scenario>
*uas.xml*
<scenario name="Basic UAS responder">
<!-- By adding rrs="true" (Record Route Sets), the route sets -->
<!-- are saved and used for following messages sent. Useful to test -->
<!-- against stateful SIP proxies/B2BUAs. -->
<recv request="INVITE" crlf="true">
</recv>
<!-- The '[last_*]' keyword is replaced automatically by the -->
<!-- specified header if it was present in the last message received -->
<!-- (except if it was a retransmission). If the header was not -->
<!-- present or if no message has been received, the '[last_*]' -->
<!-- keyword is discarded, and all bytes until the end of the line -->
<!-- are also discarded. -->
<!-- -->
<!-- If the specified header was present several times in the -->
<!-- message, all occurences are concatenated (CRLF seperated) -->
<!-- to be used in place of the '[last_*]' keyword. -->
<send>
<![CDATA[
SIP/2.0 180 Ringing
[last_Via:]
[last_From:]
[last_To:];tag=[call_number]
[last_Call-ID:]
[last_CSeq:]
Contact: <sip:[local_ip]:[local_port];transport=[transport]>
Content-Length: 0
]]>
</send>
<send retrans="500">
<![CDATA[
SIP/2.0 200 OK
[last_Via:]
[last_From:]
[last_To:];tag=[call_number]
[last_Call-ID:]
[last_CSeq:]
Contact: <sip:[local_ip]:[local_port];transport=[transport]>
Content-Type: application/sdp
Content-Length: [len]
v=0
o=user1 53655765 2353687637 IN IP[local_ip_type] [local_ip]
s=-
c=IN IP[media_ip_type] [media_ip]
t=0 0
m=audio [media_port] RTP/AVP 0
a=rtpmap:0 PCMU/8000
]]>
</send>
<recv request="ACK"
optional="true"
rtd="true"
crlf="true">
</recv>
<recv request="BYE">
</recv>
<send>
<![CDATA[
SIP/2.0 200 OK
[last_Via:]
[last_From:]
[last_To:]
[last_Call-ID:]
[last_CSeq:]
Contact: <sip:[local_ip]:[local_port];transport=[transport]>
Content-Length: 0
]]>
</send>
<!-- Keep the call open for a while in case the 200 is lost to be -->
<!-- able to retransmit it if we receive the BYE again. -->
<pause milliseconds="4000"/>
<!-- definition of the response time repartition table (unit is ms) -->
<ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200"/>
<!-- definition of the call length repartition table (unit is ms) -->
<CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000"/>
</scenario>
*sipp Client log :*
---------------------------------------------- 2017-08-10 16:38:00.921018
UDP message sent (527 bytes):
INVITE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 139
v=0
o=user1 53655765 2353687637 IN IP4 192.168.100.93
s=-
c=IN IP4 192.168.100.93
t=0 0
m=audio 6000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
----------------------------------------------- 2017-08-10 16:38:00.922070
UDP message received [296] bytes :
SIP/2.0 100 Giving a try
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Server: OpenSIPS (1.8.8-notls (x86_64/linux))
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:00.922773
UDP message received [300] bytes :
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:00.922832
UDP message received [469] bytes :
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Type: application/sdp
Content-Length: 139
v=0
o=user1 53655765 2353687637 IN IP4 192.168.100.21
s=-
c=IN IP4 192.168.100.21
t=0 0
m=audio 6000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
----------------------------------------------- 2017-08-10 16:38:00.923089
UDP message sent (353 bytes):
ACK sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-4
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 1 ACK
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:01.924891
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:02.426867
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:03.427470
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:05.430368
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:09.431433
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:13.434139
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:17.435203
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:38:21.437538
UDP message sent (353 bytes):
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
*sipp Server log :*
---------------------------------------------- 2017-08-10 16:40:07.950997
UDP message received [634] bytes :
INVITE sip:Mayur@192.168.100.21:5070 SIP/2.0
Record-Route: <sip:192.168.100.93;lr>
Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bK0988.17166e14.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 69
Subject: Performance Test
Content-Type: application/sdp
Content-Length: 139
v=0
o=user1 53655765 2353687637 IN IP4 192.168.100.93
s=-
c=IN IP4 192.168.100.93
t=0 0
m=audio 6000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
----------------------------------------------- 2017-08-10 16:40:07.951285
UDP message sent (363 bytes):
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bK0988.17166e14.0,
SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:07.951347
UDP message sent (532 bytes):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bK0988.17166e14.0,
SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-0
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 1 INVITE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Type: application/sdp
Content-Length: 139
v=0
o=user1 53655765 2353687637 IN IP4 192.168.100.21
s=-
c=IN IP4 192.168.100.21
t=0 0
m=audio 6000 RTP/AVP 0
a=rtpmap:0 PCMU/8000
----------------------------------------------- 2017-08-10 16:40:07.952446
UDP message received [353] bytes :
ACK sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-4
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 1 ACK
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:08.954237
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:08.954371
UDP message sent (292 bytes):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:09.456640
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:09.456766
UDP message sent (292 bytes):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:10.457427
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:10.457570
UDP message sent (292 bytes):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:12.460262
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:12.460420
UDP message sent (292 bytes):
SIP/2.0 200 OK
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: <sip:192.168.100.21:5070;transport=UDP>
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:16.462010
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
-----------------------------------------------
Dead call 1-25700@192.168.100.93 received a UDP message:
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:20.465975
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
-----------------------------------------------
Dead call 1-25700@192.168.100.93 received a UDP message:
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
----------------------------------------------- 2017-08-10 16:40:24.467650
UDP message received [353] bytes :
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
-----------------------------------------------
Dead call 1-25700@192.168.100.93 received a UDP message:
BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-25700-1-6
From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
Call-ID: 1-25700@192.168.100.93
CSeq: 2 BYE
Contact: sip:sipp@192.168.100.93:5065
Max-Forwards: 70
Subject: Performance Test
Content-Length: 0
Regards
Mayur Koshal
On Wed, Aug 9, 2017 at 11:20 PM, sindelka <sin...@tt...> wrote:
> Hi Mayur,
>
> the client script *was* sending ACK (and BYE), but it was sending it to
> wrong address & port and with a wrong request-uri.
>
> By adding rrs="true" and using [next url] as request-uri you have fixed
> the contents of the request-uri but not the destination, as you can see
> from the Opensips log - the problem is not that it cannot handle the ACK,
> the problem is that it should not have never received it.
>
> To my knowledge sipp doesn't provide any more convenient means to change
> remote address and port than <ereg> and <setdest>, but the whole code
> necessary is given right in the manual
> <http://sipp.sourceforge.net/doc/reference.html>:
>
> So what you need to do is the following:
>
> After the <receive response="200" ... > following sending of the INVITE,
> add
>
> <nop>
> <action>
> <assignstr assign_to="url" value="[next_url]" />
> <ereg regexp="sip:.*@([0-9A-Za-z\.]+):([0-9]+);transport=([A-Z]+)" search_in="var" check_it="true" assign_to="dummy,host,port,transport" variable="url" />
> <setdest host="[$host]" port="[$port]" protocol="[$transport]" />
> </action>
> </nop>
>
> This is a generic approach which, however, assumes presence of port and
> transport in the Contact uri. There are even more generic ways capable of
> dealing with eventual absence of these items in the Contact uri, but if you
> do not need to be ready for anything that may arrive, just replace all that
> with the following, using the address and port known in advance:
>
> <nop>
> <action>
> <setdest host="192.168.100.93" port="5065" protocol="UDP" />
> </action>
> </nop>
>
> P.
>
>
> Dne 9.8.2017 v 18:56 Mayur Koshal napsal(a):
>
> Hi Pavel ,
>
> Thanks for the reply.
>
>
> As you mentioned the Client script was not sending ACK , I tried to make
> changes in the uac.xml adding <ereg> and <setdest> to extract the address
> and port but could not add the right expression in the xml successfully .
> maybe I was not able to figure out what exactly needs to be added.
> However I added router header to enable the client script sending the
> correct ip address and port .I added rrs="true" in the recv tags and
> also changed the ACK and BYE like ACK [next_url] SIP/2.0 n the first line
> should be and also made sure to insert the header of the message the route
> tags like [route].
> By doing I could see in the logs as shared below that the client was able
> to send the ACK to the correct address and port . But still the call was
> unsuccessfull.
>
> But as soon as the ack reached opensips it could not forward it to the
> server and thrown an error message :
> ERROR:core:parse_first_line: bad request first line
> and similar other error messages mentioned below.
>
> Below are the logs for the client for 1 call followed by opensips error
> log.
>
> I changed the opensips configuration file for enabling route header as
> mentioned on the book Building Telephony by Flavio and followed the same
> steps.
>
>
> Request help/ suggestion for the same please.
>
>
>
> *Logs :*
> *uac_logs*
>
> ----------------------------------------------- 2017-08-09 16:26:31.440174
> UDP message sent (527 bytes):
>
> INVITE sip:Mayur@192.168.100.93:5060 SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-0
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 INVITE
> Contact: sip:sipp@192.168.100.93:5065
> Max-Forwards: 70
> Subject: Performance Test
> Content-Type: application/sdp
> Content-Length: 139
>
> v=0
> o=user1 53655765 2353687637 IN IP4 192.168.100.93
> s=-
> c=IN IP4 192.168.100.93
> t=0 0
> m=audio 6000 RTP/AVP 0
> a=rtpmap:0 PCMU/8000
>
> ----------------------------------------------- 2017-08-09 16:26:31.441676
> UDP message received [296] bytes :
>
> SIP/2.0 100 Giving a try
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-0
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 INVITE
> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
> Content-Length: 0
>
>
> ----------------------------------------------- 2017-08-09 16:26:31.443678
> UDP message received [300] bytes :
>
> SIP/2.0 180 Ringing
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-0
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 INVITE
> Contact: <sip:192.168.100.21:5070;transport=UDP>
> Content-Length: 0
>
>
> ----------------------------------------------- 2017-08-09 16:26:31.444145
> UDP message received [469] bytes :
>
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-0
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 INVITE
> Contact: <sip:192.168.100.21:5070;transport=UDP>
> Content-Type: application/sdp
> Content-Length: 139
>
> v=0
> o=user1 53655765 2353687637 IN IP4 192.168.100.21
> s=-
> c=IN IP4 192.168.100.21
> t=0 0
> m=audio 6000 RTP/AVP 0
> a=rtpmap:0 PCMU/8000
>
> ----------------------------------------------- 2017-08-09 16:26:31.444244
> UDP message sent (363 bytes):
>
> ACK sip:192.168.100.21:5070;transport=UDP SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-4
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 ACK
> Contact: sip:sipp@192.168.100.93:5065
> Max-Forwards: 70
> Subject: Performance Test
> Content-Length: 0
>
>
> ----------------------------------------------- 2017-08-09 16:26:31.945586
> UDP message received [469] bytes :
>
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-0
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 INVITE
> Contact: <sip:192.168.100.21:5070;transport=UDP>
> Content-Type: application/sdp
> Content-Length: 139
>
> v=0
> o=user1 53655765 2353687637 IN IP4 192.168.100.21
> s=-
> c=IN IP4 192.168.100.21
> t=0 0
> m=audio 6000 RTP/AVP 0
> a=rtpmap:0 PCMU/8000
>
> ----------------------------------------------- 2017-08-09 16:26:31.945682
> UDP message sent (363 bytes):
>
> ACK sip:192.168.100.21:5070;transport=UDP SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-4
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 1 ACK
> Contact: sip:sipp@192.168.100.93:5065
> Max-Forwards: 70
> Subject: Performance Test
> Content-Length: 0
>
>
> ----------------------------------------------- 2017-08-09 16:26:31.945739
> UDP message sent (361 bytes):
>
> BYE sip:192.168.100.21:5070;transport=UDP SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-6
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 2 BYE
> Contact: sip:sipp@192.168.100.93:5065
> Max-Forwards: 70
> Subject: Performance Test
> Content-Length: 0
>
>
> ----------------------------------------------- 2017-08-09 16:26:31.946361
> UDP message received [295] bytes :
>
> SIP/2.0 404 Not here
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-6
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 2 BYE
> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
> Content-Length: 0
>
>
> -----------------------------------------------
> Unexpected UDP message received:
>
> SIP/2.0 404 Not here
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-6
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 2 BYE
> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
> Content-Length: 0
>
>
> ----------------------------------------------- 2017-08-09 16:26:31.946517
> UDP message sent (343 bytes):
>
> BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
> Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1--1
> From: sipp <sip:sipp@192.168.100.93:5065>;tag=1
> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
> Call-ID: 1-23944@192.168.100.93
> CSeq: 3 BYE
> Max-Forwards: 70
> Contact: <sip:sipp@192.168.100.93:5065;transport=UDP>
> Content-Length: 0
>
> ---------------------------------------------------------------
>
>
> *Opensips _ logs :*
>
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_first_line: bad request first line
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_first_line: at line 0 char 42:
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_first_line: parsed so far: ACK sip:192.168.100.21:5070;
> transport=UDP
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> INFO:core:parse_first_line: bad message
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_msg: message=<ACK sip:192.168.100.21:5070;transport=UDP
> SIP/2.0#015#012Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-4#015#012From:
> sipp <sip:sipp@192.168.100.93:5065>;tag=1#015#012To: sut <
> sip:Mayur@192.168.100.93:5060>;tag=1#015#012Call-ID:
> 1-23944@192.168.100.93#015#012CSeq
> <http://1-23944@192.168.100.93#015%23012CSeq>: 1 ACK#015#012Contact:
> sip:sipp@192.168.100.93:5065#015#012Max-Forwards
> <http://sip:sipp@192.168.100.93:5065#015%23012Max-Forwards>:
> 70#015#012Subject: Performance Test#015#012Content-Length:
> 0#015#012#015#012>
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:receive_msg: Unable to parse msg received from [
> 192.168.100.93:5065]
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23929]:
> incoming reply
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_first_line: bad request first line
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_first_line: at line 0 char 42:
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_first_line: parsed so far: ACK sip:192.168.100.21:5070;
> transport=UDP
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> INFO:core:parse_first_line: bad message
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:parse_msg: message=<ACK sip:192.168.100.21:5070;transport=UDP
> SIP/2.0#015#012Via: SIP/2.0/UDP 192.168.100.93:5065;branch=z9hG4bK-23944-1-4#015#012From:
> sipp <sip:sipp@192.168.100.93:5065>;tag=1#015#012To: sut <
> sip:Mayur@192.168.100.93:5060>;tag=1#015#012Call-ID:
> 1-23944@192.168.100.93#015#012CSeq
> <http://1-23944@192.168.100.93#015%23012CSeq>: 1 ACK#015#012Contact:
> sip:sipp@192.168.100.93:5065#015#012Max-Forwards
> <http://sip:sipp@192.168.100.93:5065#015%23012Max-Forwards>:
> 70#015#012Subject: Performance Test#015#012Content-Length:
> 0#015#012#015#012>
> Aug 9 16:26:31 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> ERROR:core:receive_msg: Unable to parse msg received from [
> 192.168.100.93:5065]
> Aug 9 16:26:34 stack-VirtualBox /usr/local/opensips_proxy/sbin/opensips[23928]:
> incoming reply
>
>
> *Regards*
> *Mayur*
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> On Mon, Aug 7, 2017 at 11:44 PM, sindelka <sin...@tt...> wrote:
>
>> Hello Mayur,
>>
>> what happens is that:
>>
>> - your client script sends the INVITE to the address & port of the
>> proxy,
>> - the proxy forwards the INVITE to the address & port where the UAS
>> script listens,
>> - the UAS script responds with 180 and 200 to the address & port from
>> which it has received the INVITE and indicates its own address and port in
>> the Contact uri of the responses,
>> - the proxy forwards the 180 and 200 to the client script and does
>> not modify the Contact uri while forwarding them.
>>
>> All the above is correct. What is not correct is that the client script
>> does not send the ACK (and later on the BYE) to the address and port
>> indicated in the Contact uri in the received 200 and keeps sending it to
>> the address & port indicated on the command line. This is, however, a
>> default behaviour of sipp, honestly mentioned in the documentation, which
>> needs to be manually changed by using <ereg> to extract the address and
>> port from the Contact uri received in the 200 followed by using <setdest>
>> to change the destination for the subsequent requests sent. Another way
>> could be to change Opensips configuration to make it force itself into the
>> rest of the dialog but
>>
>> - I am not sure whether this is possible with Opensips, and
>> - if done the standard SIP way, it would cause a need to handle a
>> Route header in the client script.
>>
>> The consequences are that
>>
>> - the ACK never reaches the UAS script because the Opensips does not
>> forward ACKs but RFC3261 gives it no means to inform the sender about that,
>> - the BYE never reaches the UAS script and the Opensips responds it
>> locally. Maybe 481 would be more appropriate than 404 in this case but that
>> won't help you much.
>>
>> Actually, there may be more to it, because I'm not sure whether, once you
>> fix the behaviour of the client script, the server script sends the 200 to
>> the BYE to the client script's address & port or whether it sends it to the
>> address & port from which the dialog has been initiated. Something is
>> telling me that you may need to use <ereg> to extract the proper address
>> and port from the Via and use <setdest> as well.
>>
>> A methodical remark: it is much easier to work with logs taken at
>> different machines if all of them come from the very same call and if time
>> on all the machines is synchronized. Also, the logs written by sipp itself
>> do not indicate the address and port of the remote source or destination of
>> the messages, so simultaneous capture using tcpdump and later analysis of
>> the captures using Wireshark is worth considering.
>>
>> Pavel
>>
>>
>> Dne 7.8.2017 v 19:05 Mayur Koshal napsal(a):
>>
>> Hi,
>>
>> I am using SIPp setup for making calls between client and server through
>> opensips as a proxy server. The set up is :
>>
>> Sipp Client -- 192.168.100.21 port 5065 | Opensips Proxy server --
>> 192.168.100.93 port 5060 | Sipp server : 192.168.100 .21 port 5070.
>>
>> I am using the commands :
>>
>> sipp Client side:
>>
>> ./sipp -sf uac.xml 192.168.100.93:5060 -trace_err -s Mayur -i
>> 192.168.100.21 -p 5065 -d 5000 -l 1 -m 10 -r 1 -rp 8000
>>
>>
>> sipp Server side :
>>
>> ./sipp -sf uas.xml -rsa 192.168.100.93:5060 -i 192.168.100.21 -p 5070
>> -trace_msg
>>
>>
>> where Mayur is the user I have added using ./opensipsctl ul add Mayur
>> sip:Mayur@192.168.100.21:5070
>>
>>
>>
>> While using this setup and starting the sipp server and opensips server
>> and then starting the client I get the below error :
>>
>>
>> *Aborting call on unexpected message for Call-Id '1-17537@192.168.100.21
>> <1-17537@192.168.100.21>': while expecting '200' (index 7), received
>> 'SIP/2.0 404 Not here*
>>
>>
>> I am not sure where I am going wrong. My opensips proxy server is
>> working fine and I have verified it by making a call with Jitsi clients.
>> The calls are successful.
>>
>> But when I use sipp not even one call is shown as completed and all the
>> calls are shown as failed.
>>
>>
>> *Request your help to complete the call using sipp. Below are the logs
>> from sipp client as well as server side.*
>>
>>
>> * Server side logs :*
>>
>> *uas_17530.message.log :*
>>
>>
>>
>> DP message received [634] bytes :
>>
>>
>>
>>
>>
>> INVITE sip:Mayur@192.168.100.21:5070 SIP/2.0
>>
>> Record-Route: <sip:192.168.100.93;lr>
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 69
>>
>> Subject: Performance Test
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6004 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:22:257.196
>>
>> UDP message sent (363 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 180 Ringing
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:22:257.256
>>
>> UDP message sent (532 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:22:758.892
>>
>> UDP message sent (532 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:23:759.899
>>
>> UDP message sent (532 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:25:762.033
>>
>> UDP message sent (532 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:29:764.327
>>
>> UDP message sent (532 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:28:33:765.071
>>
>> UDP message sent (532 bytes):
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.93:5060;branch=z9hG4bKec2e.cf353566.0,
>> SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>> *Client side log :*
>>
>>
>> *uac_17537error.log*
>>
>>
>>
>> sipp: The following events occured:
>>
>> 2017-08-04 16:28:27:270 1501844307.270724: Aborting call on
>> unexpected message for Call-Id '1-17537@192.168.100.21': while expecting
>> '200' (index 7), received 'SIP/2.0 404 Not here
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17537-1-6
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17537@192.168.100.21
>>
>> CSeq: 2 BYE
>>
>> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *uac_17802_messages.log*
>>
>> ---------------------------------------------- 2017-08-04
>> 16:40:42:112.698
>>
>> UDP message sent (527 bytes):
>>
>>
>>
>>
>>
>> INVITE sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 70
>>
>> Subject: Performance Test
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6004 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:42:113.228
>>
>> UDP message received [296] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 100 Giving a try
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:42:114.155
>>
>> UDP message received [300] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 180 Ringing
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:42:114.333
>>
>> UDP message received [469] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:42:114.412
>>
>> UDP message sent (353 bytes):
>>
>>
>>
>>
>>
>> ACK sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-4
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 ACK
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 70
>>
>> Subject: Performance Test
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:42:616.165
>>
>> UDP message received [469] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:42:616.238
>>
>> UDP message sent (353 bytes):
>>
>>
>>
>>
>>
>> ACK sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-4
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 ACK
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 70
>>
>> Subject: Performance Test
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:43:617.385
>>
>> UDP message received [469] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:43:617.498
>>
>> UDP message sent (353 bytes):
>>
>>
>>
>>
>>
>> ACK sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-4
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 ACK
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 70
>>
>> Subject: Performance Test
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:45:620.191
>>
>> UDP message received [469] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 200 OK
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-0
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 INVITE
>>
>> Contact: <sip:192.168.100.21:5070;transport=UDP>
>>
>> Content-Type: application/sdp
>>
>> Content-Length: 139
>>
>>
>>
>>
>>
>> v=0
>>
>> o=user1 53655765 2353687637 IN IP4 192.168.100.21
>>
>> s=-
>>
>> c=IN IP4 192.168.100.21
>>
>> t=0 0
>>
>> m=audio 6001 RTP/AVP 0
>>
>> a=rtpmap:0 PCMU/8000
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:45:620.285
>>
>> UDP message sent (353 bytes):
>>
>>
>>
>>
>>
>> ACK sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-4
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 1 ACK
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 70
>>
>> Subject: Performance Test
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:47:115.303
>>
>> UDP message sent (353 bytes):
>>
>>
>>
>>
>>
>> BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-6
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 2 BYE
>>
>> Contact: sip:sipp@192.168.100.21:5065
>>
>> Max-Forwards: 70
>>
>> Subject: Performance Test
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:47:115.751
>>
>> UDP message received [295] bytes :
>>
>>
>>
>>
>>
>> SIP/2.0 404 Not here
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-6
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 2 BYE
>>
>> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -----------------------------------------------
>>
>> Unexpected UDP message received:
>>
>>
>>
>>
>>
>> SIP/2.0 404 Not here
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1-6
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 2 BYE
>>
>> Server: OpenSIPS (1.8.8-notls (x86_64/linux))
>>
>> Content-Length: 0
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> ----------------------------------------------- 2017-08-04
>> 16:40:47:115.899
>>
>> UDP message sent (343 bytes):
>>
>>
>>
>>
>>
>> BYE sip:Mayur@192.168.100.93:5060 SIP/2.0
>>
>> Via: SIP/2.0/UDP 192.168.100.21:5065;branch=z9hG4bK-17802-1--1
>>
>> From: sipp <sip:sipp@192.168.100.21:5065>;tag=1
>>
>> To: sut <sip:Mayur@192.168.100.93:5060>;tag=1
>>
>> Call-ID: 1-17802@192.168.100.21
>>
>> CSeq: 3 BYE
>>
>> Max-Forwards: 70
>>
>> Contact: <sip:sipp@192.168.100.21:5065;transport=UDP>
>>
>> Content-Length: 0
>>
>>
>>
>> *----------------------------------------------------------------------------------------------------------------------*
>>
>>
>>
>> *Regards*
>>
>> *Mayur*
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>
>> _______________________________________________
>> Sipp-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/sipp-users
>>
>> ------------------------------------------------------------------------------
>> Check out the vibrant tech community on one of the world's most engaging
>> tech sites, Slashdot.org! http://sdm.link/slashdot
>> _______________________________________________ Sipp-users mailing list
>> Sip...@li... https://lists.sourceforge.net/
>> lists/listinfo/sipp-users
>
>
|