In my use case I'm using SIPp to create only one call at a time (-m 1 -l 1 -r 1 -rp 1000). I expect that qq or Q or two SIGUSR1 events will cause SIPp to send BYE to a connected call or CANCEL to a ringing call. However, these events are being ignored.
The same happens when I do multiple sequential calls and SIPp has reached the last call. I have not tried concurrent calls.
Could it be that the test in line 486 of sipp.cpp should come after the if (quitting) block or should it skip the line quitting=1 when a Q command has increased the quitting variable?
In my use case I'm using SIPp to create only one call at a time (-m 1 -l 1 -r 1 -rp 1000). I expect that qq or Q or two SIGUSR1 events will cause SIPp to send BYE to a connected call or CANCEL to a ringing call. However, these events are being ignored.
The same happens when I do multiple sequential calls and SIPp has reached the last call. I have not tried concurrent calls.
Could it be that the test in line 486 of sipp.cpp should come after the if (quitting) block or should it skip the line quitting=1 when a Q command has increased the quitting variable?