#115 <nop> not ignored before <recvCmd>

v3.4
closed-fixed
Rob Day
Scenarios (18)
5
2013-04-27
2009-06-18
No

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

Discussion

  • Rob Day

    Rob Day - 2012-12-15
    • assigned_to: Rob Day
    • milestone: --> v3.4
     
  • Rob Day

    Rob Day - 2013-04-27

    Thanks for finding this - I've just pushed a fix for this, which treats nop messages as optional.

     
  • Rob Day

    Rob Day - 2013-04-27
    • status: open --> closed-fixed
     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks