Hello all,
I want to expose a quite unusual test case, that seems to illustrates a bug
in the sipp command-line application. I'm not sure that I'm posting to the
right discussion list. If not, please let me know.
I run sipp under XUbuntu, here is the response of a "sipp -v" command:
SIPp v2.0.1-TLS-PCAP, version 20070516, built May 18 2007, 11:25:38
In my scenario, I have a sipp client that sends calls to a proxy relaying to
an sipp server. The sipp client sends sequences of INVITE/ACK/BYE requests,
relayed by the proxy to the origin server. Under some conditions, the proxy
relaies the requests to the sipp server via three distincts ports (i.e. one
for the INVITE request, an other one for the ACK, and an other one for the
BYE). This is quite unusual, but it should work. Unfortunately, it doesn't
because the sipp server sends back the answer to the BYE request via the
port of the INVITE request... That is clearly a bug to me.
Here are also the command lines of the sipp server, and the client (just for
information).
sipp -t tn -sn uas -p 8182
sipp -t tn -r 1 -sn uac 127.0.0.1
Best regards,
Thierry Boileau
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users
