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
Adjusted invite_redirect and invice_redirect_tel_uri
kct based on the new rework done in review 65078 (MT55858)
Change-Id: I5aef6a26032f48d77325227160e150817000728d
SDP description check has been removed for invite_voicebox scenario
because not important and a upgrade of asterisk may lead to
kct failing.
Change-Id: Iac15edc08ec534a177658106b24f2d171474448b
We have to actualize the regex match for History-Info headers
after the following commit was applied in templates:
f47f6d590e49e75e4746090485848662ce118933
Change-Id: I9ceb83804d04d08b397c6a0a3c2db623e0df3507
We have to actualize the regex match for History-Info headers
of the responder01 after the following commit was applied in templates:
f47f6d590e49e75e4746090485848662ce118933
Change-Id: I99ad98ec6ea142bce566187e262ffd79c97750c4
Fix kct incoming_hih scenario to check privacy=history
instead of privacy=id as intruduced in commit
c82f9074ec537ea34f37d9ece2453f32732ff639
Change-Id: I9966665c64baef6276cb16789bcd6917ae580c95
incoming_hih scenario is sending this header inside file
scenarios/incoming_hih/sipp_scenario00.xml
This means, the caller do not wish to rely his
history info information to the callee.
This has been implemented with commit
743e05b642adbd05c935ad794b2e60ee91fbb222.
Thanks to this, KCT now must check that the
History Info header is anonymized without
showing the real caller.
Change-Id: I92481e31dcc070c43380ef19721bb5ed5afe7bf3
We need to actualize scenarios when checking usage fmtp description in SDP bodies,
due to late changes in the RTPEngine behavior
(when processing offer/answer with/without fmtp for the 101th event).
Change-Id: I47f97cba69345fb0fdce777831e7f23cc37a79b3
Now KCT can read from the registration section of the scenario.yml file the value 'ua'.
If this is set (and registration is set to yes), KCT will add in the registration xml files
meant for SIPP the header 'User Agent' with the value specified.
To demonstrate how it works the scenario invite_callforward has also been extended and
now it sends registrations with User-Agent: KCT SIPP, additionally it enables feature ua_reject_missing
to check if this header is present and also tests if in the sems loop the ua_reject_missing
is ignored (whitelisting sems).
Change-Id: I709a0e0c3532b8e5246834dc3566b26e95b5f3be
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
invite_allowip_soundset has also been extended to demonstrate
kamailio proxy handling P-Early-Media SIP Header.
- The first call is the same and demonstrates if the caller does not send
P-Early-Media header, ngcp will assume he's supporting early media and
he's gonna play the announce.
- The Second call is the same case but since P-Early-Media is "inactive"
kamailio wont sent the audio message and justs sends an error.
Change-Id: Ib989809ada070101b932deaf9ba8d2f5c1a92fe0
New scenario derived from invite_record_call to demostrate
play_announce_before_call_setup feature
Change-Id: I398a031cfd5ec4fc0ab7d9ef5a88be2990e8fa74
Add ROUTE_NCOS in invite_redirect and invite_redirect_uri tests
because of commit f5ff3fd7d70a988eb4d660d59a25101af778f29b in templates.
Change-Id: I66d69a57439da06b367f4227e740065cdd7b62a2
The following files have wrong progressing number since
the extra call registration shifted their value by 4.
For example the old 0003_test.yml.tt2 now is 0007_test.yml.tt2 but
0003_test.yml.tt2 is still there and needs to be removed.
0005_test.yml.tt2 is now 0009_test.yml.tt2
0008_test.yml.tt2 is now 0012_test.yml.tt2
0010_test.yml.tt2 is now 0014_test.yml.tt2
and so on
Change-Id: Ia70e3ee14c6abf0efac335435725de5e9ee76361
scenario incoming_peer implemented with 2 new calls showing
P-Early-Media handling with NCP placing this header
if missing back from the callee.
In particular the second call demonstrates how P-Early-Media
is parsed even with some spaces between parameters.
Change-Id: I5dbd823d9dfbeea01eb70a7e64889742d75ff518
2 Part
A continuation of: cfa796886d
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]
Change-Id: I2353bf3f4e4d227694e9a39e0ddda03cb446ef11
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]
Change-Id: Icc6f70957c932cadd8d9c81896038e6fd9b4374f
We need to update a list of the following scenarios:
- timer_session_supported
- timer_session_caller_only_supported
- timer_session_callee_only_supported
due to the latest changed in the way how we handle 'timer' in
Supported / Require headers.
Change-Id: If0ce782f945b27a27c99a460f3bd60a0fee92f57
play_announce_before_recording is now a quad state and no more
a boolean, changing user preference to the correspondant value.
Change-Id: I3da961d428a2e1c6f10957ba53ce1bf3ba200d35
Victor Seva
Donat Zenichev
Daniel Grotti
Alessio Garzi
Mohammed Ghettas
Fabricio Santolin da Silva
Marco Capetta