|
From: Simon F. <sim...@gm...> - 2007-08-23 12:53:04
|
Again, many thanks for the information. Keep up the great work! Simon On 8/23/07, Charles P Wright <cpw...@us...> wrote: > > You need to use a trunk version for fill or assignstr to be supported. > Unfortunately, the 2.0 versions have a bug which does not report an error > when it encounters an unknown action. > > Charles > > "Simon Flannery" <sim...@gm...> wrote on 08/23/2007 04:26:33 AM: > > > Thank you very much for your prompt response Charles, > > > > It worked. However, I have a question or two. > > > > I tried using the [fill] keyword with SIPp v2.0.1-TLS-PCAP, version > > 20070521, built May 22 2007, 12:49:03, but I got the following error: > > > > Unsupported keyword 'fill text="sample"' in xml scenario file. > > > > Is the [fill] keyword supported? And in what versions? Or am I just > > not using it correctly? > > > > My next question relates to using assignstr as you suggested. Either > > my logic flow is incorrect or my usage of the assignstr is incorrect, > > but my messages generated using the following scenario file always > > seem to have a content size of 0 with no body. Any ideas? > > > > <?xml version="1.0" encoding="ISO-8859-1" ?> > > <!DOCTYPE scenario SYSTEM "sipp.dtd"> > > > > <scenario name="AS Send a Basic Message"> > > > > <nop next="2" chance="0.3" /> > > > > <label id="1" /> > > <nop next="3"> > > <action> > > <assignstr assign_to="1" value="Small message" /> > > </action> > > </nop> > > > > <label id="2" /> > > <nop> > > <action> > > <assignstr assign_to="1" value="Big message" /> > > </action> > > </nop> > > > > <label id="3" /> > > <send retrans="500" start_rtd="true"> > > <![CDATA[ > > > > MESSAGE sip:[field2]@[field1] SIP/2.0 > > To: [field3] <sip:[field2]@[field1]> > > From: [field0] > <sip:[field0]@[field1]>;tag=[call_number] > > Call-ID: [call_id] > > CSeq: [cseq] MESSAGE > > Max-Forwards: 69 > > Via: SIP/2.0/[transport] > [local_ip]:[local_port];branch=[branch] > > Route: <sip:172.23.195.186:7070;lr> > > Contact: [field0] > <sip:[field0]@[local_ip]:[local_port]> > > Accept-Contact: > > Content-Type: text/plain > > P-Asserted-Identity: <sip:[field0]@[field1]> > > User-Agent: PoC-client/OMA1.0 > > Content-Length: [len] > > > > [$1] > > > > ]]> > > </send> > > > > ... > > > > </scenario> > > > > > > Thanks in advance, > > > > Simon > > > > On 8/22/07, Charles P Wright <cpw...@us...> wrote: > > > > > > You can use a <nop> with a branch, something like: > > > > > > <nop next="1" chance=".3" /> > > > <send next="2"> > > > Small Message > > > </send> > > > <label id="1" /> > > > <send next="2"> > > > Big Message > > > </send> > > > <label id="2" /> > > > > > > You can also use a single message, and variables with either the > assignstr > > > action or the the [fill] keyword. > > > > > > Charles > > > > > > sip...@li... wrote on > > > 08/22/2007 02:02:08 PM: > > > > > > > > > > Hi dev's, > > > > > > > > I posted this at the user's mail-list but I need an answer as soon > > > > as possible. > > > > > > > > Does anyone know if it is possible to randomly preform a pre-emptive > > > > conditional branch? > > > > > > > > For example, the provided "branchc.xml" scenario first sends a SIP > > > > message then prefoms a conditional branch. It seems that SIPp can ONLY > > > > preform a conditional branch AFTER it has sent (or received) a > message, > > > > for example ONLY AFTER <send> or <recv>. > > > > > > > > How can I preform a pre-emptive conditional branch? > > > > > > > > For example I want to send a large (content body) SIP MESSAGE 30% of > > > > the time and a small SIP MESSAGE 70% of the time. How can this be > > > > done? > > > > > > > > Cheers, > > > > > > > > Simon > > > > > > > > Here is my scenario file: > > > > > > > > <?xml version="1.0" encoding="ISO-8859-1" ?> > > > > <!DOCTYPE scenario SYSTEM "sipp.dtd"> > > > > > > > > <scenario name="AS Send a Basic Message"> > > > > > > > > <nop> > > > > <action> > > > > <test assign_to="1" chance="0.70" /> > > > > </action> > > > > </nop> > > > > > > > > WHAT TO DO HERE???????????????????????????? > > > > > > > > <label id="1" /> > > > > <!-- In client mode (sipp placing calls), the Call-ID MUST be> > > > generated by sipp. To do so, use [call_id] keyword. --> > > > > <send retrans="500" start_rtd="true"> > > > > <![CDATA[ > > > > > > > > MESSAGE sip:[field2]@[field1] SIP/2.0 > > > > To: [field3] <sip:[field2]@[field1]> > > > > From: [field0] > > > <sip:[field0]@[field1]>;tag=[call_number] > > > > Call-ID: [call_id] > > > > CSeq: [cseq] MESSAGE > > > > Max-Forwards: 69 > > > > Via: SIP/2.0/[transport] > > > [local_ip]:[local_port];branch=[branch] > > > > Route: <sip:172.23.195.186:7070;lr> > > > > Contact: [field0] > > > <sip:[field0]@[local_ip]:[local_port]> > > > > Accept-Contact: > > > > Content-Type: text/plain > > > > P-Asserted-Identity: <sip:[field0]@[field1]> > > > > User-Agent: PoC-client/OMA1.0 > > > > Content-Length: [len] > > > > > > > > Hello World from the news desk. This is a small message. Hello > > > > World from the news desk. This is a small message. Hello World from > > > > the news desk. This is a small message. Hello World from the news > > > > desk. This is a small message. Hello World from the news desk. This is > > > > a small message. Hello World from the news desk. This is a small > > > > message. > > > > > > > > ]]> > > > > </send> > > > > > > > > <recv response="200" rtd="true" rrs="true" next="3" /> > > > > > > > > <label id="2" /> > > > > <!-- In client mode (sipp placing calls), the Call-ID MUST be> > > > generated by sipp. To do so, use [call_id] keyword. --> > > > > <send retrans="500" start_rtd="true"> > > > > <![CDATA[ > > > > > > > > MESSAGE sip:[field2]@[field1] SIP/2.0 > > > > To: [field3] <sip:[field2]@[field1]> > > > > From: [field0] > > > <sip:[field0]@[field1]>;tag=[call_number] > > > > Call-ID: [call_id] > > > > CSeq: [cseq] MESSAGE > > > > Max-Forwards: 69 > > > > Via: SIP/2.0/[transport] > > > [local_ip]:[local_port];branch=[branch] > > > > Route: <sip:172.23.195.186:7070;lr> > > > > Contact: [field0] > > > <sip:[field0]@[local_ip]:[local_port]> > > > > Accept-Contact: > > > > Content-Type: text/plain > > > > P-Asserted-Identity: <sip:[field0]@[field1]> > > > > User-Agent: PoC-client/OMA1.0 > > > > Content-Length: [len] > > > > > > > > Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. Hello World from the news desk. This is a big message. Hello > > > > World from the news desk. This is a big message. Hello World from the > > > > news desk. This is a big message. Hello World from the news desk. This > > > > is a big message. Hello World from the news desk. This is a big > > > > message. > > > > > > > > ]]> > > > > </send> > > > > > > > > <recv response="200" rtd="true" rrs="true" next="3" /> > > > > > > > > <label id="3" /> > > > > > > > > <pause distribution="fixed" value="2000" /> > > > > > > > > <!-- Definition of the response time repartition table (unit is ms). > --> > > > > <ResponseTimeRepartition value="10, 20, 30, 40, 50, 100, 150, 200" /> > > > > > > > > <!-- Definition of the call length repartition table (unit is ms). > --> > > > > <CallLengthRepartition value="10, 50, 100, 500, 1000, 5000, 10000" /> > > > > > > > > </scenario> > > > > > > > > > > > > ------------------------------------------------------------------------- > > > > This SF.net email is sponsored by: Splunk Inc. > > > > Still grepping through log files to find problems? Stop. > > > > Now Search log events and configuration files using AJAX and a > browser. > > > > Download your FREE copy of Splunk now >> http://get.splunk.com/ > > > > _______________________________________________ > > > > Sipp-devel mailing list > > > > Sip...@li... > > > > > https://lists.sourceforge.net/lists/listinfo/sipp-devel > > > > |