From: <sri...@us...> - 2009-07-29 09:50:08
|
Revision: 588 http://sipp.svn.sourceforge.net/sipp/?rev=588&view=rev Author: srivanuj Date: 2009-07-29 09:49:53 +0000 (Wed, 29 Jul 2009) Log Message: ----------- Doc modification for check_it_inverse Modified Paths: -------------- doc/trunk/src/documentation/content/xdocs/doc/reference.xml Modified: doc/trunk/src/documentation/content/xdocs/doc/reference.xml =================================================================== --- doc/trunk/src/documentation/content/xdocs/doc/reference.xml 2009-07-28 13:50:38 UTC (rev 587) +++ doc/trunk/src/documentation/content/xdocs/doc/reference.xml 2009-07-29 09:49:53 UTC (rev 588) @@ -1458,7 +1458,13 @@ <td>check_it</td> <td>false</td> <td>if set to true, the call is marked as failed if - the regexp doesn't match.</td> + the regexp doesn't match. Can not be combined with check_it_inverse.</td> + </tr> + <tr> + <td>check_it_inverse</td> + <td>false</td> + <td>Inverse of check_it. iff set to true, the call is marked as failed if + the regexp does match. Can not be combined with check_it.</td> </tr> <tr> <td>assign_to</td> @@ -2434,6 +2440,11 @@ match (there might be several regexp that don't match during the call but the counter is increased only by one).</li> + <li>FailedRegexpShouldntMatch: + Number of failed calls because of regexp that shouldn't + match (there might be several regexp that shouldn't match + during the call but the counter is increased only by + one).</li> <li>FailedRegexpHdrNotFound: Number of failed calls because of regexp with hdr option but no matching header found.</li> @@ -2531,7 +2542,7 @@ <li>You can log sent and received SIP messages in <name_of_the_scenario>_<pid>_messages.log by using the command line parameter <code>-trace_msg</code>. The messages are time-stamped so that you can track them back.</li> - <li>You also can trace it using the <code>-trace_shortmsg</code> parameter. This logs the most important + <li>You also can trace it using the <code>-trace_shortmsg</code> parameter. This logs the most important values of a message as CSV into one line of the <scenario file name>_<pid>_shortmessages.log </li> <li>You can trace all unexpected messages or events in <name_of_the_scenario>_<pid>_errors.log by using the command line parameter <code>-trace_err</code>.</li> This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |