This fix an issue when running KCT on a machine that have a few
particular settings that could invalidate some tests.
Change-Id: Ia693a515d85427f731c9b9209efe5138982da189
Since the 'proxy.skip_cf_loop' is disabled by default,
but we would like to use that config.yml option in our tests,
it's required to enable it, for all types of scenarios.
Change-Id: I694a5699f6e921c7f76219b2edf6d530990ac3da
Remove route ROUTE_CHECK_TIMER_SUPP_REQ because not
used anymore in the system
Remove check if variable $x_hdr(Supported) because not
used anymore in the config and thus not printed by cfgt
module in log files
Change-Id: I9335ed36fd04d053c188062455def9706d97e2d7
3 Part
A continuation of: cfa796886d
and: f8bc607696
We need to update a list of k-c-t scenarios because of
the last updates in a way how we process 'timer' extension in
the Supported / Require headers.
Now additionally in most of the scenarios we enter:
- route[ROUTE_CHECK_TIMER_SUPP_REQ]
- route[ROUTE_REMOVE_TIMER_SUPP_REQ]
In this commit we specificially fix the PBX and LNP scenarios.
Change-Id: I0d782f05573ffddb83fa7adf01bfab11e512e299
The names of the NCOS levels assigned in the scenarios_lnp:
* invite_ncos_black
* invite_ncos_white
were too long (more than the 30 allowed chars) preventing the
correct provisining of the scenarios.
Change-Id: Iec5ad8b7a8d051a56c6ab91a53877fd0587c5d60
It's been noticed that during nightly Jenkins runs,
scenarios LNP keep on failing because of: 'invite_ncos_black' and
'invite_ncos_white' scenarios.
Jenkins runs a mass configuration of the whole bunch of scenarios,
and then starts running them one by one.
The issue happens because of the same NCOS level names used by both
'invite_ncos_black' and 'invite_ncos_white' scenarios.
First Jenkins configures 'invite_ncos_black' and all needed NCOS
levels are added. Then Jenkins deletes and creates again the same
NCOS levels (which share the same names) for the 'invite_ncos_white'.
This leads to the fact, that NCOS levels exist,
but are not set for 'invite_ncos_black' in domain preferences.
Another problem is, that mass configuration of LNP scenarios
leads to the problem with lnp carrier id and lnp numbers during
the run, and Proxy component thinks that there are no entries
for certain scenarios or uses the wrong lnp entry. Same problem,
scenarios share the same name space for part of the objects.
This commit concerns change of the name space for NCOS levels.
Change-Id: I851e5a81384e46972996d93b7d03657fd1c6c63d
* when reading yaml, that value became hex
* lint yaml using visual code plugin
* TODO: introduce pre-commit and create rule for avoid this
issue in the future
Change-Id: I866024ba51b6bbec7449275bb6ea56e2f7e6bb4d
* we have more templates now
* make just one find call per scenario
* remove preds.json file left behind
Change-Id: Ic9983cd238b12134a97c94d2c7844c7391de7108
All ports 5080 are changed to 508[0|8] and all port 5085
are changed to 508[5|8].
This to allow to use the test als whtn b2b server is not
enabled.
Change-Id: Iec75fc5a92eb9bd09e1a0c4b2d2200df3006ed2e
A new start and return from ROUTE_PREPARE_CALLER_CLI route
is necessary because of the outbound_pai_display preference check
Change-Id: Idef80c761fe881e3e78a52fbed1add7fcd6ccf1c
After the fix to the NCOS checks in case of LNP re-routing number
was used, the test scenarios should be update accordingly.
Change-Id: I71aa3989c88006225f112009da1d944309b7f4fc
Victor Seva
Fabricio Santolin da Silva
Alessio Garzi
Donat Zenichev
Marco Capetta
Mohammed Ghettas
Andrew Pogrebennyk