Hello - I've just observed breakage in the recent SIPp builds for handling
unexpected messages.
This is a scenario that expects a 404, but receives a 200 to a register.
In build 2006-08-16, the received 200 is correctly tagged as unexpected.
In build sipp.2006-08-21, the 200 message is received (visible in -trace_msg
log) but is simply tossed, and not treated as unexpected, which doesn't
terminate the call, and forces sipp to spin in a retransmission loop.
The latest build (09-14) behaves as 08-21, so the breakage is still in the
latest build.
I've looked at the diff between these 2 builds, and nothing jumps out at me.
I'd appreciate if someone could investigate this issue.
[EMAIL PROTECTED] sipp.2006-08-16]# ./sipp -sf ../reg.xml -inf ../input.inf
67.1.100.93 -m 1
Resolving remote host '67.1.100.93'... Done.
------------------------------ Scenario Screen -------- [1-4]: Change Screen --
Call-rate(length) Port Total-time Total-calls Remote-host
10.0(0 ms)/1.000s 5060 0.10 s 1 67.1.100.93:5060(UDP)
Call limit reached (-m 1), 0.108 s period 2 ms scheduler resolution
0 concurrent calls (limit 30) Peak was 1 calls, after 0 s
0 out-of-call msg (discarded)
1 open sockets
Messages Retrans Timeout Unexpected-Msg
REGISTER ----------> 1 0 0
100 <---------- 1 0 1
404 <---------- E-RTD 0 0 0
------------------------------ Test Terminated --------------------------------
2006-09-21 12:18:55: Aborting call on unexpected message for Call-ID '[EMAIL
PROTECTED]': while expecting '100' response, received 'SIP/2.0 200 OK
Via: SIP/2.0/UDP 67.1.100.51:5060;received=67.1.100.51
Call-ID: [EMAIL PROTECTED]
From: <sip:[EMAIL PROTECTED]:5060>
To: <sip:[EMAIL PROTECTED]:5060>
CSeq: 1 REGISTER
Contact: <sip:[EMAIL PROTECTED]:5060>;transport=UDP;expires=300
Content-Length: 0
' .
=============
[EMAIL PROTECTED] sipp.2006-08-21]# ./sipp -sf ../reg.xml -inf ../input.inf
67.1.100.93 -m 1 -trace_err
Resolving remote host '67.1.100.93'... Done.
------------------------------ Scenario Screen -------- [1-5]: Change Screen --
Call-rate(length) Port Total-time Total-calls Remote-host
10.0(0 ms)/1.000s 5060 40.57 s 1 67.1.100.93:5060(UDP)
Call limit reached (-m 1), 0.557 s period 2 ms scheduler resolution
0 concurrent calls (limit 30) Peak was 1 calls, after 0 s
2 out-of-call msg (discarded)
1 open sockets
Messages Retrans Timeout Unexpected-Msg
REGISTER ----------> 1 9 1
100 <---------- 1 0 0
404 <---------- E-RTD 0 0 0
------------------------------ Test Terminated --------------------------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
