Hi,
I'm writing a few tests to run against Asterisk involving various transfer
scenarios and 3PCC Extended Mode has been a great way to allow me to pass
data between SIPp instances to facilitate these transfers.
The first test I wrote tests REFER transfers, runs rock solid, and involves
one master and one slave as well as two unassociated SIPp instances that do
nothing but receive calls and wait for a BYE.
The second test I wrote tests INVITE/Replaces transfers and involves one
master, one slave, and one unassociated SIPp instance to take calls. This
test functions as expected >75% of the time, but occasionally it will fail
when the SIPp instances fail to setup what I assume are the 3PCC sockets.
They produce this error message:
[Sep 27 10:01:56] WARNING[15613]: sipp:378 processEnded: 2012-09-27
10:01:56:019 1348758116.019852: Unable to connect a twin sipp socket
Use 'sipp -h' for details, errno = 111 (Connection refused).
At this point, the test falls apart. I have checked to ensure that the
ports specified in the slave_cfg file are not in use, but that seems to be
irrelevant.
I am currently using latest SIPp trunk from
https://sipp.svn.sourceforge.net/svnroot/sipp/sipp/trunk and am running the
test on a machine with the following setup:
Linux clyne 2.6.32-33-generic #72-Ubuntu SMP Fri Jul 29 21:07:13 UTC 2011
x86_64 GNU/Linux
(Ubuntu 10.04.3)
I am still trying to determine the differences between the two tests that
would cause them to exhibit different behaviors, but I thought someone here
might have seen this before and found a solution.
Thanks,
Will
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://ad.doubleclick.net/clk;258768047;13503038;j?
http://info.appdynamics.com/FreeJavaPerformanceDownload.html
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users
