* FLOW_VARS or FLOW error, so possible
changes in kamailio.cfg are detected
* produce the _test.diff and .sip files
using the proper json
Change-Id: I39a003b3542283b4080f1c8e5004e826ae98f16e
* check.sh: remove none as the way to disable check results
added -t to indicate that
* run_tests.sh: add -T to enable cfgt
don't call anything related to cfgt if not enabled
* bench.sh: enable cfgt if check type is all or cfgt
Change-Id: I4c13297b55503f99241cf5553c5deceba0f5bbf6
no longer support of parsing of the kamailio log to produce flow info
* remove ulog_parser.pl, no longer used
* graph_flow.pl: remove -j option
* check.py: remove --yaml/--json options
* check.sh: remove SKIP_PARSE and JSON_KAM options
Change-Id: I0df00ffff3e7d8c2129cbbce12652ddff9730821
Lowered the rtpengine cancel delay from 2 to 1 second
Lowered the sleep time of the script check.sh from 5 to 2 seconds
Removed sleep time before check CDRs
This should speed up the test of basic scenarios of 4/5 minutes
Change-Id: I4f5fb539f7ab704f1aca6ddd2abf64db54b27ef1
* sipp_scenario00.xml => sipp_scenario00.msg
sipp_scenario_responder00.xml => sipp_scenario_responder00.msg
so sipp_scenario00_test.yml.tt2 and sipp_scenario_reponder00_test.yml.tt2
makes more sense
Change-Id: Iab9db5122774dbc32101195e639ab6fef9b23236
We are adding a new approach/tool used to check out SIP messages
received, and unlike the existing way of doing that (using what has come/gone in front of the Proxy),
the usage of sipp logs will be introduced.
The idea is that we are looking for received SIP messages at both
the originator(s) and recipient(s) side, and then using what we've gotten,
run checks based on _test.yml.tt2 templates prepared in advance for each scenario, example:
* sip_messages00_test.yml.tt2
* sip_messages_responder00_test.yml.tt2
- add missing options to help command
- bin/check.sh: use T option to select what to do with checks
- get_results.sh: remove deprecated -P -T options
Change-Id: I2d0084fa59694ffd009736205a092a35f6864669
This will allow to skip the whole provisioning if necessary
* use set_config.sh
* bin/check.sh: don't remove domain if SKIP is set
Change-Id: I0b2d165aced0ce7e57cfddef4c6308e8d7d27da6
* bin/sipp.sh: add option to set SIP SERVER_IP
* bin/check.sh: add option to set SIP SERVER_IP
* bin/scenario.pl: add server_ip info to scenario_ids.yml file
* bin/get_config.pl: add server_ip info to output
* bin/run_tests.sh: get server_ip from config and use it
Change-Id: If7a2284827df344eaecfdb5671146a9a79e81ea8
* bin/provide_scenario.sh: point of entry of provisioning
* bin/get_domains.pl: script helper to get domains defined at
scenario.yml
Change-Id: Ib1440f074b6f588c8a9dfac5dcf29d6b7459fb42
Since 3.6.0 sipp is throwing a warning that doesn't
change behavior but we detect an error file as failed
sipp execution for responders
So let's clean the known error from error files and
remove the empty ones after
See details at https://github.com/SIPp/sipp/issues/497
* bin/sipp.sh: add -e option to define error file
* bin/check.sh: use -e option with the proper filename
so there's no need to move the files later
Change-Id: I5ce4b73d858d928f4bc9ec89bfe8658fad48b6e6
* Automatic filenames (trace files, error files, etc..)
are now created in the current working directory instead
of in the directory of the scenario file.
* https://github.com/SIPp/sipp/releases/tag/v3.6.0
Change-Id: I06ad4c7196ea9087f5e04e289f09baf927ed1e01
Now that we are allowing cheking more that one message, be
sure that already OKed messages don't get compared
Change-Id: I152af70b6dca69fe935ca70f8d40acb599cbaff0
* bin/check.py: return different values depending on what section
check fails
reformat using black tool
Change-Id: Ie393766ba5df0951fb9f51c1c780cc5be8673fc7
* check for dirs with a scenario.yml file
* remove some shellcheck warnings:
SC2207: Prefer mapfile or read -a to split command output (or quote to avoid splitting).
Change-Id: I88b48fcc9668c3be26755472d6001f630a341fca
* fix delete perm registration: subscriber needs to exists
move delete before deletion of domain
* bench.sh: obey PROFILE environment variable
* bin/config_debug.pl: set tcp for one of the extra_sockets
Change-Id: I4650058f22ffcac68fa44913e1b03ecf090c2f28
Now we can define different module level of debug per scenario.
So we can have more info without changing the general config.yml
Change-Id: I64e5467eedf2c41827ab8de85835b0b6c09486eb
tool that reads info directly from scenario.yml
* check.sh: clean some shellcheck warnings
* bench.sh: fix group option
Change-Id: If736c42729e8fd32e964a5c9db7e47b289e916c8
* now it will be called *before* scenario is built
* introduced at b006dee9f8
TODO: move this external tool that can read scenario.yml info
directly
Change-Id: Ic85ceb2900ea137c96b7d3354d59439fa72a8a96
Add 'retrans: true' to the test.yml file and name
it '_test_retransmission.yml.tt2' instead of '_test.yml.tt2'
Change-Id: I2e83f773ed8a1ba537aedb61410db79fecbecf16
In case of sipp errors bin/check.sh was aborted without moving
the scenario_ids.yml, moving the json files and cleaning the
scenario's data if required.
Change-Id: Ibb1b5c1874476ff2f483488670f8c3953c38c58f
Call cfgt.clean RCP function at the end of the scenario execution
only if the json files were actually moved (SKIP_MOVE_JSON_KAM
not set). Otherwise the result will be to don't have any json
file generated.
Change-Id: I97f2b00516a8975c050f97a7ffecb47b2dceecd3
The option is triggered by run_tests.sh because it is already
taking care of the json file movement at the end of the scenarios
execution.
Change-Id: Ie609237b46c54734dc25f093351c89138a70d8f9
After JSON_KAM was enabled by default in commit 8618aa8 we lost
the possibility to disable it if necessary.
The option -J of bin/check.sh script now do the opposite: it is
used to disable JSON_KAM preference. Due to this change, the -J has
been removed from the script call in get_results.sh
Change-Id: I8ccc9d832ba808c72494dc27526e66ceff802a95
* This allows to run the same scenario without having to restart
kamailio-proxy every time
* set JSON_KAM as default
Change-Id: I0948095e318fa0220c16adfc52e124a9e6c35c67