Hi Ricardo & all,
Thanks a lot for your answer.
I will get the lastest version in the trunk source code,
Unfortunatelly, i need to set the *source* IP and port of my sipp messages.
so it leads to the 100$ question: does the "setsrc" or "setsource" option also 
exists ?
:)
 
BR,
Cyrille> Date: Wed, 30 Jul 2008 15:31:57 +0100> From: [EMAIL PROTECTED]> To: 
[EMAIL PROTECTED]> Subject: Re: [Sipp-users] Force source IP & source Port at 
IP laye> > Hello,> > I think you had the same problem as me.> You can change 
the place here your sipp messages go to by specifying> the host and the port in 
the scenario file like this:> <nop>> <action>> <setdest host="112.12.12.12" 
port="5060" protocol="udp" />> </action>> <nop>> > This works in sipp with UDP, 
in TCP i don't know, never tried.> This will only work with the lastest version 
in the trunk source code,> the current binaries in the sourceforge stable 
version> will not recognized the setdest keyword.> > Ps:> If you are using 
windows get this version from the snapshots here:> 
http://sipp.sourceforge.net/snapshots/sipp-win32-2008-07-18.exe> > Hope it 
helps> Ricardo Fernandes> > > > On Wed, Jul 30, 2008 at 2:31 PM, Cyrille 
OLIVIER <[EMAIL PROTECTED]> wrote:> > Hi all,> > I worried a bit about this 
post ;)> > Actually, I don't need a very developped answer but just a short 
(but clear> > ;) ) one.> > Of course, if needed, i can detail more> >> > Best 
regards & thanks a lot,> > Cyrille> >> > ________________________________> > 
From: [EMAIL PROTECTED]> > To: [email protected]> > Date: Thu, 
10 Jul 2008 10:13:50 +0000> > Subject: [Sipp-users] Force source IP & source 
Port at IP layer> >> >> > Dear sipp-users,> >> > Again, I asked my requests 
about SIPp client using TCP:> > Is it possible to force sipp to use specific IP 
source & Port source, at IP> > layer, for "send" messages when TCP with single 
socket (option '-t t1' used)> > ?> > I tried many things:> >> > 1/ -bind_local: 
seems unuseful.> > 2/ -i x.x.x.x -p yyyy options: it's only for some SIP 
headers but not for IP> > packet header.> > 3/ <send -source_ip="x.x.x.x" 
-source_port="yyyy"> for INVITE message: does> > not seems to work.> > 4/ look 
for this subject in mailing list archives: some conversation are> > closed to 
my question but not similar at 100%> > ...> >> > Currently, I don't know which 
other workaround or things to do :(> > I would really appreciate any help about 
that> > Thanks a lot,> > BR,> > Cyrille> > ________________________________> > 
Discutez gratuitement avec vos amis en vidéo ! Téléchargez Messenger, c'est> > 
gratuit !> > ________________________________> > Avec Windows Live Messenger 
restez en contact avec tous vos amis !> > Téléchargez Messenger, c'est gratuit 
!> > -------------------------------------------------------------------------> 
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge> 
> Build the coolest Linux based applications with Moblin SDK & win great> > 
prizes> > Grand prize is a trip for two to an Open Source event anywhere in the 
world> > http://moblin-contest.org/redirect.php?banner_id=100&url=/> > 
_______________________________________________> > Sipp-users mailing list> > 
[email protected]> > 
https://lists.sourceforge.net/lists/listinfo/sipp-users> >> >
_________________________________________________________________
Retouchez, classez et partagez vos photos gratuitement avec le logiciel Galerie 
de Photos !
http://www.windowslive.fr/galerie/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Sipp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to