Hi Hideyuki,
I am assuming you are running on some sort of Linux environment? There
is an inbuilt limitation with most Linux environments which limit the
number of sockets, for example to 6 as you have found. This is not a
SIPp limitation, rather an operating system limitation to help protect
the
If you need to run both instances simultaneously, yes.
Regards,
Olivier Boulkroune
-Message d'origine-
De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 26 septembre 2007 20:05
À : Boulkroune, Olivier (Non-HP:Atos Origin)
Cc : [EMAIL PROTECTED];
Hello simon,
[EMAIL PROTECTED] said:
You should only need 1 or 2 SIPp instances for the UAC and UAS. A single SIPp
instance can handle many users by using a CSV injection file. Just put ALL
users in the one CSV file, not just BOB!
I tried that, but discovered that the .csv report files did
Hi Olav,
This may be way-off, but would loging a custom message to a file help?
For example:
recv request=INVITE crlf=true rrs=true
action
ereg regexp=.* search_in=hdr header=Some-New-Header:
assign_to=1 /
log message=From is [last_From]. Custom header is [$1]/
Instructions for accessing the latest subversion source are here:
http://sourceforge.net/svn/?group_id=104305 and here
http://sipp.sourceforge.net/wiki/index.php/Dev.
Charles
Pradeep Mohapatra [EMAIL PROTECTED] wrote on
09/27/2007 06:20:29 AM:
Hi Charles,
Thanks for your quick response.
Santosh,
If you have the time, you should consider posting these to the Scenarios
page of the Wiki at http://sipp.sourceforge.net/wiki/index.php/Scenarios.
Charles
[EMAIL PROTECTED] wrote on 09/27/2007 01:58:39 AM:
Hi Bharath,
I have attached two xml files, you can use these.
Hope this
There are two things that come to mind here, one that you can probably get
some reasonable information now; but will miss things like unexpected
messages. One thing that would make this nicer is if there were key words
like [rtd number=2], etc. The best way may be to use the error or short
[EMAIL PROTECTED] wrote on 09/27/2007 08:45:12 AM:
Registration works fine. And the INVITE package will send with the right
Port to the UAS.
But Sipp discard this massage because the CallID dosn't match
(reference.html#Unexpected+messages)
but i Need to Reset the callID because Register
Hi,
I have downloaded and compiled the 2.0.1 version of the source code on the
SUSE09 machince.
Linux2:/var/spool/pkg/sipp-2.0.1.src # make all
make OSNAME=`uname|sed -e s/CYGWIN.*/CYGWIN/` MODELNAME=`uname -m|sed
s/Power Macintosh/ppc/` sipp
make[1]: Entering directory
Is there a way with sipp to specify the interface from which the call is
generated? I have a dual interface machine on different networks and believe
the attempted call is heading out the wrong interface. Any input would be
appreciated. Thank you.
-
You can use the -i option.
Charles
[EMAIL PROTECTED] wrote on 09/27/2007 05:08:52 PM:
Is there a way with sipp to specify the interface from which the
call is generated? I have a dual interface machine on different
networks and believe the attempted call is heading out the wrong
11 matches
Mail list logo