Found it. Here's the diff against the 09-14 build.
[EMAIL PROTECTED] sipp.2006-09-14]# diff -bruN call.cpp.orig call.cpp
--- call.cpp.orig 2006-09-21 14:47:51.195189629 -0400
+++ call.cpp 2006-09-21 14:47:56.692290936 -0400
@@ -2542,8 +2542,8 @@
search_index >= 0;
search_index--) {
if (scenario[search_index]->optional == OPTIONAL_FALSE) contig = false;
- if(MATCHES_SCENARIO(search_index) &&
- (contig || scenario[search_index]->optional == OPTIONAL_GLOBAL)) {
+ if(MATCHES_SCENARIO(search_index)) {
+ if (contig || scenario[search_index]->optional == OPTIONAL_GLOBAL) {
found = true;
break;
} else {
@@ -2561,6 +2561,7 @@
}
}
}
+ }
int test = (!found) ? -1 : scenario[search_index]->test;
/* test==0: No branching"
> 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.
-------------------------------------------------------------------------
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
