[Sipp-users] Renaming the log files

2008-06-16 Thread Monica Sam -X (monsam - WIPRO at Cisco)
Hi,
 
Is there a way to rename the log files that get generated when we use
the trace_ options? We do SIP testing using SIPp and run automated
suites and it would be very useful to have the log files named after the
test case ID . One way is to, of course, name the scenario after the
test case ID.But is there some command line option which can do the
same?
 
Thanks,
Monica.
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


[Sipp-users] uac_pcap problem

2008-06-16 Thread jinline . adsl
Hello,

I setup sipp 3.1 on FreeBSD ,and setup libnet  before

make clean
make pcapplay

I  have this message
cpp -D__LINUX -pthread -DPCAPPLAY -I. -I/usr/local/include -c -o message.o message.cpp
cpp: "-c" is not a valid option to the preprocessor
Error code 1
stop in /usr/ports/benchmarks/sipp/work/sipp.svn


Any suggestion is welcome!  thanks--- 本郵件來自HiNet WebMail 
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


Re: [Sipp-users] How to set behavior for any received response except of 200 OK

2008-06-16 Thread Dhananjaya Reddy Eadala
in scenario, set the following:

recv response=200
/recv


If sipp receives other than 200, then it will exit automatically.


Dhana


On 6/16/08, Evgeny Miloslavsky [EMAIL PROTECTED] wrote:

  Hi All

 How do I cause my SIPP instance to exit the scenario for every received
 response except of 200 OK.





 Regards,

 * *

 *Evgeny Miloslavsky***

 *Systest Engineer*

 *Juniper Networks Solutions Israel LTD.*

 *Office: 972-9-9712355 / 7320*

 http://www.juniper.net/



 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


Re: [Sipp-users] How to set behavior for any received response except of 200 OK

2008-06-16 Thread Charles P Wright
SIPp won't exit but the call will fail.

If you want SIPp to exit, you'll need to do a regular expression match and 
an action that includes something like error message=Got something other 
than 200 /.

Charles




Dhananjaya Reddy Eadala [EMAIL PROTECTED] 
Sent by: [EMAIL PROTECTED]
06/16/2008 11:12 AM

To
Evgeny Miloslavsky [EMAIL PROTECTED]
cc
sipp-users@lists.sourceforge.net
Subject
Re: [Sipp-users] How to set behavior for any received response  except of 
200 OK






in scenario, set the following:
 
recv response=200
/recv
 
 
If sipp receives other than 200, then it will exit automatically.
 
 
Dhana

 
On 6/16/08, Evgeny Miloslavsky [EMAIL PROTECTED] wrote: 
Hi All
How do I cause my SIPP instance to exit the scenario for every received 
response except of 200 OK.
 
 
Regards,
 
Evgeny Miloslavsky
Systest Engineer
Juniper Networks Solutions Israel LTD.
Office: 972-9-9712355 / 7320
 
 

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users

-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users



-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


Re: [Sipp-users] SIPp 3.1 - SDP bug!?

2008-06-16 Thread Joby James
Hi All,

  I am getting the same error on our SBC.

Error code 0X000B from SDP parser, at offset 133 in an SDP  from side 1)
SDP Error: SDP not terminated with
*EOL *character SDP string ($$$ denotes error offset):v=0 o=user1 53655765
2353687637 IN IP4 200.200.1.10 s=- c=IN IP4 200.200.1.10 t=0 0 m=audio 1
RTP/AVP 0 a=rtpmap:0 PCMU/800$$$0

Is there any patch available to fix this problem? Any suggestions ?

Thanks in advance.

Regards,
Joby James.

On Fri, Jun 13, 2008 at 7:34 PM, Zarko Coklin [EMAIL PROTECTED]
wrote:

 Hi all!

 I think there is a bug in 3.1 SIPp. According to RFC 2327, section 6, all
 SDP text based
 bodies should end with CRLF (0x0d0a). Version 2.1 works OK. See below
 an excerpt from
 RFC 2327.

 Regards,
 Zarko Coklin

 ~~
 Text records such as the session name and information are bytes
 strings which may contain any byte with the exceptions of 0x00 (Nul),
 0x0a (ASCII newline) and 0x0d (ASCII carriage return). The sequence
 *CRLF (0x0d0a)* is used to end a record, although parsers should be
 tolerant and also accept records terminated with a single newline
 character. By default these byte strings contain ISO-10646
 characters in UTF-8 encoding, but this default may be changed using
 the `charset' attribute.
 ~~



 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users




-- 
Mobile: +919880696590
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


Re: [Sipp-users] SIPp 3.1 - SDP bug!?

2008-06-16 Thread Venkatesh
Are you are seeing these errors when using SIPp with the default scenarios?

Venkatesh

On Mon, Jun 16, 2008 at 9:23 PM, Joby James [EMAIL PROTECTED] wrote:

 Hi All,

   I am getting the same error on our SBC.

 Error code 0X000B from SDP parser, at offset 133 in an SDP  from side
 1) SDP Error: SDP not terminated with
 *EOL *character SDP string ($$$ denotes error offset):v=0 o=user1 53655765
 2353687637 IN IP4 200.200.1.10 s=- c=IN IP4 200.200.1.10 t=0 0 m=audio
 1 RTP/AVP 0 a=rtpmap:0 PCMU/800$$$0

 Is there any patch available to fix this problem? Any suggestions ?

 Thanks in advance.

 Regards,
 Joby James.

 On Fri, Jun 13, 2008 at 7:34 PM, Zarko Coklin [EMAIL PROTECTED]
 wrote:

 Hi all!

 I think there is a bug in 3.1 SIPp. According to RFC 2327, section 6, all
 SDP text based
 bodies should end with CRLF (0x0d0a). Version 2.1 works OK. See below
 an excerpt from
 RFC 2327.

 Regards,
 Zarko Coklin

 ~~
 Text records such as the session name and information are bytes
 strings which may contain any byte with the exceptions of 0x00 (Nul),
 0x0a (ASCII newline) and 0x0d (ASCII carriage return). The sequence
 *CRLF (0x0d0a)* is used to end a record, although parsers should be
 tolerant and also accept records terminated with a single newline
 character. By default these byte strings contain ISO-10646
 characters in UTF-8 encoding, but this default may be changed using
 the `charset' attribute.
 ~~



 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users




 --
 Mobile: +919880696590
 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users


-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users


Re: [Sipp-users] SIPp 3.1 - SDP bug!?

2008-06-16 Thread Joby James
Hi Venkatesh,

  I see this problem on both default(-sn uac) and manual (-sf uac.xml)
cases.
I am using sipp 3.1 version.

Thanks and regards,
Joby James.


On Tue, Jun 17, 2008 at 10:10 AM, Venkatesh [EMAIL PROTECTED] wrote:

 Are you are seeing these errors when using SIPp with the default scenarios?

 Venkatesh


 On Mon, Jun 16, 2008 at 9:23 PM, Joby James [EMAIL PROTECTED]
 wrote:

 Hi All,

   I am getting the same error on our SBC.

 Error code 0X000B from SDP parser, at offset 133 in an SDP  from side
 1) SDP Error: SDP not terminated with
 *EOL *character SDP string ($$$ denotes error offset):v=0 o=user1
 53655765 2353687637 IN IP4 200.200.1.10 s=- c=IN IP4 200.200.1.10 t=0 0
 m=audio 1 RTP/AVP 0 a=rtpmap:0 PCMU/800$$$0

 Is there any patch available to fix this problem? Any suggestions ?

 Thanks in advance.

 Regards,
 Joby James.

 On Fri, Jun 13, 2008 at 7:34 PM, Zarko Coklin [EMAIL PROTECTED]
 wrote:

 Hi all!

 I think there is a bug in 3.1 SIPp. According to RFC 2327, section 6, all
 SDP text based
 bodies should end with CRLF (0x0d0a). Version 2.1 works OK. See below
 an excerpt from
 RFC 2327.

 Regards,
 Zarko Coklin

 ~~
 Text records such as the session name and information are bytes
 strings which may contain any byte with the exceptions of 0x00 (Nul),
 0x0a (ASCII newline) and 0x0d (ASCII carriage return). The sequence
 *CRLF (0x0d0a)* is used to end a record, although parsers should be
 tolerant and also accept records terminated with a single newline
 character. By default these byte strings contain ISO-10646
 characters in UTF-8 encoding, but this default may be changed using
 the `charset' attribute.
 ~~



 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users




 --
 Mobile: +919880696590
 -
 Check out the new SourceForge.net Marketplace.
 It's the best place to buy or sell services for
 just about anything Open Source.
 http://sourceforge.net/services/buy/index.php
 ___
 Sipp-users mailing list
 Sipp-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/sipp-users





-- 
Mobile: +919880696590
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php___
Sipp-users mailing list
Sipp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sipp-users