[Sipp-users] RegEx
Hi, I am trying to use the regex to get the tag value from: sip:[EMAIL PROTECTED]:5060 ;tag=123.147.206.2105060+1+122+ac214fea I get the tag value in $6 if I use following regex, but I don't need $1 and $5: ereg regexp=sip:(.*);tag=(.*) search_in=hdr header=To: check_it=true assign_to=1,5,6 / How can I get only the tag value (without tag=) using just one variable? Thanks, Atul - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139
The dead calls should not keep SIPp open, but will be listed as tasks for 32 seconds. The dead calls help understanding the error logs, because otherwise they are listed as out-of-call messages, or even worse on a UAS as an unexpected message at index 0. The -m option should definitely work, I use it very often. Can you paste your command and a screen log? Charles [EMAIL PROTECTED] wrote on 07/14/2008 05:45:05 AM: Hi Charles, my testcases working fine with the latest SVN trunk but a other problem appears now. A scenario was be launched with the -m (n) option do not stop after n iterations. The scenario was be marked as a Dead call at the end, the following messages will be dicarded but the test never ends. A possible workaround for me is to define a explicit exit in any cases using the internal command stop_now. Wolfgang Deutsche Telekom AG Zentrum Technik Einführung Wolfgang Kanngießer Winterfeldtstraße 21, D-10781 Berlin -Ursprüngliche Nachricht- Von: Charles P Wright [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 9. Juli 2008 17:23 Wolfgang, I tried the scenario with the SVN trunk and did not get an error. Charles Kanngiesser, Wolfgang [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/07/2008 07:07 AM To sipp-users@lists.sourceforge.net cc Subject [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139 Hi all, recently I am asking for a error segmentation fault due to the external commands, i.e. action exec command=echo pass verdict.log/ /action The problem is still relevant but all scenarios worked properly until sipp2.0. There are any hints? Thanks,Wolfgang. Deutsche Telekom AG Zentrum Technik Einführung Wolfgang Kanngießer Winterfeldtstraße 21, D-10781 Berlin - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users - Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 ___ Sipp-users mailing list Sipp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sipp-users
Re: [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139
Hi Charles, here are the command and the resulting screenshot. As You can see the duration of the test could be 300 s. As attachement the scenario reg_001.xml too. x306a:/home/user# sipp -i 192.168.1.10 -sf reg_001.xml 192.168.1.50 -m 1 -nd -inf defvar.csv -trace_logs -trace_msg -trace_err Resolving remote host '192.168.1.50'... Done. -- Scenario Screen [1-9]: Change Screen -- Port Total-time Total-calls Transport 5060 302.29 s3 UDP Call limit reached (-m 1), 0.096 s period 4 ms scheduler resolution 0 callsPeak was 1 calls, after 55 s 0 Running, 3 Paused, 0 Woken up 26 dead call msg (discarded) 3 open sockets Messages Retrans Timeout Unexpected-Msg [ NOP ] -- REGISTER 3 0 0 0 -- 2003 0 [ NOP ] [ NOP ] -- Test Terminated - Statistics Screen --- [1-9]: Change Screen -- Start Time | 2008-07-14 16:39:11:0491216046351.049119 Last Reset Time| 2008-07-14 16:44:13:2501216046653.250229 Current Time | 2008-07-14 16:44:13:3501216046653.350345 -+---+-- Counter Name | Periodic value| Cumulative value -+---+-- Elapsed Time | 00:00:00:100 | 00:05:02:301 Call Rate |0.000 cps |0.010 cps -+---+-- Incoming call created |0 |3 OutGoing call created |0 |0 Total Call created | |3 Current Call |0 | -+---+-- Successful call|0 |3 Failed call|0 |0 -+---+-- Call Length| 00:00:00:000 | 00:00:00:000 -- Test Terminated 2008-07-14 16:44:10:9271216046650.927112: Dead call [EMAIL PROTECTED] (successful), received 'REGISTER sip:192.168.1.10:5060 SIP/2.0 Via: SIP/2.0/UDP 192.168.1.50;branch=z9hG4bKadedef452 Content-Length: 0 To: VoIP_IUT sip:[EMAIL PROTECTED]:5060 From: VoIP_IUT sip:[EMAIL PROTECTED]:5060;tag=c541a84b6564619 Call-ID: [EMAIL PROTECTED] CSeq: 1603878564 REGISTER Contact: VoIP_IUT sip:[EMAIL PROTECTED] User-Agent: MxSipApp/5.0.23.141 MxSF/v3.2.2.4 '. sipp: There were more errors, see 'reg_001_10098_errors.log' file x306a:/home/user# Wolfgang Deutsche Telekom AG Zentrum Technik Einführung Wolfgang Kanngießer Winterfeldtstraße 21, D-10781 Berlin The dead calls should not keep SIPp open, but will be listed as tasks for 32 seconds. The dead calls help understanding the error logs, because otherwise they are listed as out-of-call messages, or even worse on a UAS as an unexpected message at index 0. The -m option should definitely work, I use it very often. Can you paste your command and a screen log? Charles [EMAIL PROTECTED] wrote on 07/14/2008 05:45:05 AM: Hi Charles, my testcases working fine with the latest SVN trunk but a other problem appears now. A scenario was be launched with the -m (n) option do not stop after n iterations. The scenario was be marked as a Dead call at the end, the following messages will be dicarded but the test never ends. A possible workaround for me is to define a explicit exit in any cases using the internal command stop_now. Wolfgang Deutsche Telekom AG Zentrum Technik Einführung Wolfgang Kanngießer Winterfeldtstraße 21, D-10781 Berlin -Ursprüngliche Nachricht- Von: Charles P Wright [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 9. Juli 2008 17:23 Wolfgang, I tried the scenario with the SVN trunk and did not get an error. Charles Kanngiesser, Wolfgang [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 07/07/2008 07:07 AM To sipp-users@lists.sourceforge.net cc Subject [Sipp-users] SIPp3.1 - scenario breaks whith exitcode 139 Hi all, recently I am asking for a error segmentation fault due to the external commands, i.e. action exec command=echo pass verdict.log/ /action The problem is still relevant but all scenarios worked properly until sipp2.0. There are any hints? Thanks,Wolfgang. Deutsche Telekom AG Zentrum Technik Einführung Wolfgang Kanngießer Winterfeldtstraße
