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
* create test for blind transfer when option immediat release is set to
"no" (tests are put in disable folder)
Change-Id: Idf1500f2d5aef3d889800efd2e83f2ac6d42b283
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
The rtpengine project used to be called rtpengine-ng, and before that
mediaproxy-ng, which was an implementation using the same protocol as
the rtpproxy project. It's about time we rename the config.yml section
so that this is less confusing.
Change-Id: Ibb26b5537f0e0b739b148a2a30fbd3f998732b49
Due to a deprecation of the 'sems' config.yml block of settings,
we have to update the 'config_debug.pl' and let it handle configurations
using the remaining 'b2b' section.
Change-Id: Id7d114b85906ce4aae22e11a57a3a281d35c63ea
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_offline_soundset:
new scenario derived from invite_offline but with a soundset associated that
caused early media to be played before 480 offline error message.
The same 2 calls of invite_allowip_soundset have been implemented here.
Change-Id: Ib2131e7d3ce83d6253f6d716a78fe6026885c852
* 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
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
Implemented usage() function inside reorder_tests_tt2.sh to describe how to use it.
Additionally, 2 new options have been implemented:
- -m git|mv : if set the renaming is performed with "mv" command rather than "git mv", useful if you are not on a git directory
- -t : just outputs the renaming to stdout without really renaming (dry run)
Change-Id: I0be8a2d6468b66d365ec138a09e5ac5873bf694f
> Thu Feb 10 13:33:16 CET 2022 - Config files
> Thu Feb 10 13:33:16 CET 2022 - Added stir file keys
> 2022-02-10 13:33:16 spce: Error: Failed to call action 'apply' on 'spce' (see logs on 'spce')
> Thu Feb 10 13:33:17 CET 2022 - ngcpcfg apply returned 0
> Thu Feb 10 13:33:17 CET 2022 - Removed apicert.pem
> Thu Feb 10 13:33:17 CET 2022 - Setting config debug off
> ./set_config.sh: line 125: ./bin/config_debug.pl: No such file or directory
> ngcp-type: profile CE
Change-Id: Ifbe32da1539d2ce340687b8a0c5ceb7ad1a59ca6
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
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
Alessio Garzi
Mohammed Ghettas
dzenichev
Victor Seva
Sipwise Jenkins Builder
Guillem Jover
Fabricio Santolin da Silva
Marco Capetta