I've seen these messages when doing multiple runs of the same sipp setup 
consecutively. The last run has not timed out yet (as sipp by default 
don't  have any good way of setting branch or tag value to something 
random). The second run uses the same branch and tag values which our 
proxy deems as a resent request and the confusion follows. But I've 
solved this problem with a workaround setting the branch and tag to 
something random inserted from csv.

thanks for the input
/Oscar


Boulkroune, Olivier (Non-HP:Atos Origin) wrote:
> Oscar,
>
> What do you mean by " messages it does not recognize as destined to itself" ? 
> How did you observe the behaviour you asked about ?
>  
> Regards,
> Olivier Boulkroune
>  
> -----Message d'origine-----
> De : Oscar Kené [mailto:[EMAIL PROTECTED] 
> Envoyé : lundi 16 avril 2007 09:33
> À : Boulkroune, Olivier (Non-HP:Atos Origin)
> Cc : [email protected]
> Objet : Re: [Sipp-users] sipp, sut
>
> Thanks,
> though I would expect any sip aware client by default to simply drop 
> messages it does not recognize as destined to itself.
>
> Maybe this is not the correct action?
>
> /Oscar
>
>
> Boulkroune, Olivier (Non-HP:Atos Origin) wrote:
>   
>> 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
>>   
>>     
>
>   


-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to