* provide_next_network.pl helper to get sipp port and mport used
on that scenario
Entry point to provide the whole group of scenarios with different
port/mport assigned by scenario
Change-Id: Ie3cc83388afe089242830373643e32421db83e51
keep IP/port selections on scenario_ids.yml
* bin/scenario.pl creates scenario_ids.yml with IP/port info too
* bin/create_subscribers.yml reads scenario_ids.yml first now
different IP/port/mport for peers!!
Change-Id: If8f07174bcacbf093bcbb14cd81b876c36c7e404
Using incoming-foreign-dom.scenarios.test as domain produced errors in
our checks
> Argument "" isn't numeric in subtraction (-) at scenarios/incoming_foreign_dom/0003_test.yml.tt2 line 62.
* bin/create_subscribers.pl: replace '-' as '_' to avoid this problem
Change-Id: I0f9e5defbff238f313c19907ec60644a51f7f918
* 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
* single point of entry to get valid scenarios depending on PROFILE
GROUP and obeying SCENARIOS environment variable
Change-Id: I3dabf2b14c0c68f802287e1355f208ccb14224f6
force_inbound_calls_to_peer
* Test 1 : scenario for force_outbound_calls_to_peer
* Test 2 : scenario for force_inbound_calls_to_peer
Change-Id: Ic45f9edc66193aa5850d32ccc94659a95d4d4186
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
* test 1 : NGCP supporting session timer on caller and callee
* test 2 : NGCP supporting session timer on caller only
* test 3 : NGCP supporting session timer on callee only
Change-Id: Ic1e9bc9b18002014b952b93ff5e299faebfedef1
New scenario just to check that the no_404_fallback is working.
We are only checking the flow in this scenario and make sure that
the 404 not found message is relayed and no new fallback invite
is generated
Change-Id: I3ff436d27aa676e12ffdd52cba96c9a978f648d6
Script bin/generate_test_tt2.pl is not able to generate proper regexp
from a mixed Accept header field like for example:
Accept: application/pidf+xml

In this case there is no substitution and the final .tt2 file
does not escape the `+' sign causing the following test to fail
even if user agent are sendind the correct header.
Change-Id: I2a1d66d3482a8c87d9bf09bb2665951aa42c4722
Added scenario invite_callee_bye to test proxy and LB behaviour
when the calle sends a bye appending parameters in the user part
of the request uri as described in rfc 4904.
Change-Id: I35ee5fcc7cdaaf56f14bc9cf99d4b7baf10c822a
* 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
Victor Seva
Manuel Montecelo
Mohammed Ghettas
Sipwise Jenkins Builder
Marco Capetta
Alessio Garzi
Michael Prokop