Bugs item #2808444, was opened at 2009-06-18 09:52 Message generated for change (Tracker Item Submitted) made by sjames1958 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=637564&aid=2808444&group_id=104305
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Scenarios Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Stephen James (sjames1958) Assigned to: Nobody/Anonymous (nobody) Summary: <nop> not ignored before <recvCmd> Initial Comment: When a scenario starts with a <nop> followed by <recvCmd> and a command is received from other SIPP instance, I get an error "Unexpected control message received ...". Simply moving the <nop> after the recvCmd allows it to work. This does not seem to me to be correct behavior. When I have a <recv> following a <nop> the scenario works as expected. SIPp v3.1-TLS version svn570 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=637564&aid=2808444&group_id=104305 ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
