[Sipp-users] a couple of suggestions

[Scott E. S. <sco...@ya...>]

Good Afternoon-

I have used SIPp for awhile now, both for functional testing and load
testing. It has been extremely useful!

I have a couple of suggestions that would improve the usability for me,
perhaps for others, too. I am a tester, not a coder, so I can make
suggestions, not implement them.   :-)

Suggestion #1:
The automatic ACK of an unexpected response is good (I think there are cases
when an automatic BYE is sent, too.?), but if a scenario file has changed
the "From" header (perhaps making it a 10-digit phone number), then the
automatic ACK will be discarded by the SUT. Another command-line parameter
that works like -s (service), to denote the "localservice", would make the
tool and default scenarios much more versatile (for me  :-)). Of course,
this would cause changes to default scenarios, but I think it would make
them much more versatile.

Suggestion #2:
As I tried to work through this, I used the branching feature. I could then
send the proper ACK, but then the scenario would complete successfully
(after all, it did exactly what I told it). Perhaps It would be useful to be
able to specify the exit value as a send or recv attribute. say "exit=1". In
my case, I receive an "unexpected" 503, branch on it, send the ACK with
<send exit="1">, and then when that transaction ends, it returns "1". This
is only one example where an exit code may be useful; I know I have thought
of others.

SIPp is an excellent tool; I appreciate all the hard work and thought that
has been put in to it!

Regards,
Scott