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
Fix scenario invite_force_outbound_calls_to_peer to work without
ROUTE_SET_CALLEE_DIALOG being executed.
Change-Id: I67579b590fc6d87766b10151a77c601b3f123eb2
We need to update a list of scenarios for k-c-t in the master repo, in order to let CE-trunk nightly runs (by Jenkins) be working again.
For now Jenkins marks CE-trunk build as failed, reason - not actual k-c-t scenarios.
Change-Id: I1a5152149b3bb066574655c74fff162a82ebc20b
Even if the video support is disabed by the callee, a codec has to be
provided in the reply. Addin coded 34 equel to the one received in the
initial INVITE.
The missing codec was causing SEMS to add an empty line after the
sdp m= line causing rtpengine to return:
error: Failed to parse SDP
Change-Id: I80227c9dd9a34a21b278d9b069d5af88eb504655
* 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
* sipp_scenario00.xml => sipp_scenario00.msg
sipp_scenario_responder00.xml => sipp_scenario_responder00.msg
so sipp_scenario00_test.yml.tt2 and sipp_scenario_reponder00_test.yml.tt2
makes more sense
Change-Id: Iab9db5122774dbc32101195e639ab6fef9b23236
We are adding a new approach/tool used to check out SIP messages
received, and unlike the existing way of doing that (using what has come/gone in front of the Proxy),
the usage of sipp logs will be introduced.
The idea is that we are looking for received SIP messages at both
the originator(s) and recipient(s) side, and then using what we've gotten,
run checks based on _test.yml.tt2 templates prepared in advance for each scenario, example:
* sip_messages00_test.yml.tt2
* sip_messages_responder00_test.yml.tt2
- add missing options to help command
- bin/check.sh: use T option to select what to do with checks
- get_results.sh: remove deprecated -P -T options
Change-Id: I2d0084fa59694ffd009736205a092a35f6864669
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I3d4799ce63859318fa59ac6326dd48bc33a44e24
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I5f72525f3b341d2d21fbf2cf9e12af01e1c9eda7
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I9fd0806a713551d76eea6738cbd03b34be36f593
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ifbf3a88f92b2d6183c792ee7acdf57ef927cb9cd
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I1c89268f60444e5ef400705f16cb0b457ebb5cf3
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: Ib39f68152d4da57d6104c2eab54d5232bc1f878e
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I521e6f68a206638cc28731d0d7bf726675c6a356
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: If803617720a36c19c82084d0d1b58d5ec23c7005
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I1a3640aecc33e8e1117f159542846255af5e088b
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I0d4121a1e496fc42fce57ac8df55db804a2841b1
* use server_ip from scenario_ids.yml
* Contact with <> format
* tests:
- add received Contact parameter as optional
Change-Id: I9cc04a40ab5b0f7eb4400808d082b1182a7b8fff