I'm a little confused as to what some of the exit codes mean and how you might intentionally cause SIPp to exit with those codes.

I'm writing a testing script that utilizes SIPp, and I want to be able to handle every failure appropriately, and I would like to be able to demonstrate how it handles those failures.

0 and 1 are of course no problem.  SIPp also seems to return 255 when it can't bind an address, which is fine.  The exit codes I'm having trouble generating are 97 and 99.

I would think that 97 would be caused by hitting 'q', but this always gives me a 0 exit code.

I'm not too clear on what 99 even means.  How can you have a normal exit without any calls processed?  Setting -m to 0 gives an exit code of 0, so that's not it.

Finally, does anyone know a way of causing a fatal error in SIPp?  I know it's a strange request, but I want to make sure I handle it correctly at least once.

Thanks.

-- Erik Lillethun

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to