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
New scenario to test CFT in combination with a parallel HG with 2 members.
The 2 members will keep rining until timeout is reached, then kamailio proxy
will initiate another call toward a new callee.
Change-Id: Id5db93f6068dac27e98bfc202a26b4bd2cf7f417
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
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ic9333ad40bee717c4681f7c4e01f1a2292981dfa
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ia9c2d32f2d4d5e7918eb415df5ef40e11a9f2c7f
> {"message":"Customer already has a pbx pilot subscriber.","code":"422"}
To avoid this error on provisioning all at once
Change-Id: Iaa0f519ae62e0b67c14bcd587b1e35c758afae3c
SCA notifications for multi-device case are now
working properly so we can reactivete those scenarios
Change-Id: Ic32b430c84dfb0036d63e33a5e651ef7e66939a2
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I038473a950350d8a3a2953fefbab02d310554558
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ieaaf6290acbabff0a420d26534c9fc5c76eb3178
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ia9628182aa19bcfcce8976a097d4f17e852b5ec3
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: If5337d34d703c4f946c34a74dac1b5692ef02e5d
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I0bfa4f1825b95b6d4af8bb3c5fae511a8beaaf1a
> {"message":"Customer already has a pbx pilot subscriber.","code":"422"}
To avoid this error on provisioning all at once
Change-Id: Icc36123a64e4f657d154a08eadc50e8f90e1f459
Regenerate from scratch all pbx scenarios.
This is needed because the pbx removal changed drastically
the flow and every pbx scenario is failing.
Temporarly moved scenarios
* incoming_shared_line
* invite_shared_line
to disabled folder in order to don't block the nightly tests.
Change-Id: I236bfc64b86e88809a55b04a9a92ab2e702f915d
Victor Seva
Alessio Garzi
Donat Zenichev
Mohammed Ghettas
Fabricio Santolin da Silva
Marco Capetta