Hello Oscar,
You probably observe this on some messages which are automatically sent by sipp, such as ACK answering to unexpected > 400 responses (you can check that by activating -trace_err ). Those messages are hard coded, that's why you see 'sipp' and 'sut' in the headers. You can use -nd (no default) option if you want to avoid this (see the online help http://sipp.sourceforge.net/doc/reference.html#Online+help+%28-h%29) for more details). Regards, Olivier Boulkroune Message: 2 Date: Tue, 10 Apr 2007 10:34:10 +0200 From: Oscar Ken? <[EMAIL PROTECTED]> Subject: [Sipp-users] sipp, sut To: [EMAIL PROTECTED] Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=ISO-8859-1; format=flowed In some cases I see sipp falling back to some default mode using "sipp" user in the From header and "sut" user in the To header. Why would it do this? Is there any way to suppress this behavior? I can't some up with any situation where this is useful. regards /Oscar ------------------------------------------------------------------------- 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
