Please send all questions to the list.  Future seekers may want to know 
this as well.

> From: KATWALA, KALPESH, ATTLABS [mailto:kk8...@att.com] 
> Sent: Monday, May 04, 2009 8:10 AM

> I'm trying to simulate multiple IP/port combination.  I saw your
> response to one of the Questions on the SIPp forum and wanted some
> details.
> 
> http://www.mail-archive.com/sipp-users@lists.sourceforge.net/msg03631.html
> 
> How / Where do I place these valuable suggestions you have?
> 
> [SNIP]
>    -ip_field        : Set which field from the injection file contains
> the IP
>                       address from which the client will send its
> messages.
>                       If this option is omitted and the '-t ui' option
> is
>                       present, then field 0 is assumed.
>                       Use this option together with '-t ui'
> [/SNIP]
> 
> [SNIP]
>    -t               : Set the transport mode:
>                       - u1: UDP with one socket (default),
>                       - un: UDP with one socket per call,
>                       - ui: UDP with one socket per IP address The IP
>                         addresses must be defined in the 
> injection file.
>                       - t1: TCP with one socket,
>                       - tn: TCP with one socket per call,
>                       - l1: TLS with one socket,
>                       - ln: TLS with one socket per call,
>                       - c1: u1 + compression (only if 
> compression plugin
>                         loaded),
>                       - cn: un + compression (only if 
> compression plugin
>                         loaded).  This plugin is not provided 
> with sipp.
> [/SNIP]

        These are command line options.  So you might have an injection file 
which reads:

[SNIP file="calls.inf"]
SEQUENTIAL
2104330001;192.168.9.21
2104330002;192.168.9.22
2104330003;192.168.9.21
2104330004;192.168.9.22
[/SNIP]

        So you would call sipp thus:

$ sipp -t ui -inf calls.inf -ip_field 1 [other sipp options]

        The first call will be placed to 210-433-0001 and sent out the 
interface on which 192.168.9.21 is configured.  In the scenario file, 
"[field0]" will be replaced with "2104330001", and "[field1]" will be replaced 
with "192.168.9.21".

        The second call will be placed to 210-433-0002 and sent out the 
interface on which 192.168.9.22 is configured.  In the scenario file, 
"[field0]" will be replaced with "2104330002", and "[field1]" will be replaced 
with "192.168.9.22".

        The third call will be placed to 210-433-0003 and sent out the 
interface on which 192.168.9.21 is configured.  In the scenario file, 
"[field0]" will be replaced with "2104330003", and "[field1]" will be replaced 
with "192.168.9.21".

        ...and so forth and so on.  Note that you do not ask sipp to do the 
matrixing - you must do that yoursef, so if you wanted each number to be called 
from each interface in the above scenario, you would:

[SNIP file="calls.inf"]
SEQUENTIAL
2104330001;192.168.9.21
2104330002;192.168.9.22
2104330003;192.168.9.21
2104330004;192.168.9.22
2104330001;192.168.9.22
2104330002;192.168.9.21
2104330003;192.168.9.22
2104330004;192.168.9.21
[/SNIP]


        HTH,

Mike

------------------------------------------------------------------------------
Register Now & Save for Velocity, the Web Performance & Operations 
Conference from O'Reilly Media. Velocity features a full day of 
expert-led, hands-on workshops and two days of sessions from industry 
leaders in dedicated Performance & Operations tracks. Use code vel09scf 
and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf
_______________________________________________
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

Reply via email to