Just a rename of header P-Prev-Caller-UUID to prevent it
to be exposed to external endpoints.
Change-Id: Ibd73a9b8dd80ee8e0f17f7b1bf8d7058f482ad87
(cherry picked from commit 9a6a02a133)
Test "incoming_hih" adapter to change at 836972700a3794d74aefb6360a1a6c2f1f066d40.
Reason word must precede the cause inside new hih headers.
Change-Id: I0bb7d196b40d5d32cf82a59d545d30f46418bcc0
(cherry picked from commit dc65a1e7c7)
inbound/outbound no longer represent the "full" direction and belong
only to A leg, so they are renamed to a_inbound/a_outbound accordingly.
Change-Id: I09af00baee3dbf32b514130adfe7cf106b27bc86
Scenario invite_blockout_ncos now performs an additional test call
to test adm_ncos_exceptions, the second call must be accepted even if it matches
the ncos pattern because destination is listed into adm_ncos_exceptions new
user preference
Change-Id: Icc5f78d9b0c2982dc0ab34f5eba7505a156e42d4
Invite scenario now also checks P-Preferred-Identity
in cdr aggregated data (table accounting.cdr_tag_data)
Change-Id: I3ef20378a613e3cf809e92e0dc331acd3112d5d0
Because with the change 4f0cff6 we've started to
not allow malformed Contact headers, that makes no
sense for this k-c-t scenario. Essentially a malformed
Contact from now on will never reach out the Proxy.
Move scenario to the disabled folder.
Change-Id: Idde552e82c3a62dfdc3040f6a7fa5c0132383ae5
Leftovers of fixed ip address in file scenarios/invite_callforward_use_redirection/sipp_scenario_responder02_test.yml.tt2
are now templatized.
Change-Id: I43e028dfe8361757fa6fa85fe051d5e988e0fec4
This new scenario tests the new CF option "use redirection" meant to redirect a call
with a 302 reply.
Change-Id: Ifd24d7856a653aaca68acf1164efd92f961801af
It is necessary in case we need to test the call recording
like in the invite_record_call scenario.
Change-Id: Ic0e770b3dfef04e918c25392f0ee0c1627eb5fbc
* record_call preference usage in
scenarios/invite_record_call/prefs.json
is changed from
"record_call": true -> 1
because the preference is of enum type and expects the follwoing
values: NULL,0,1,2,3
Change-Id: If6a5060909d7c67ad2222f59127d94baf2d196a6
Message was not properly built. Everything after Contact was not
included due to an empty line when ua is empty
Change-Id: I1e0851149103851bfd9228d1cf840b02144230d7
Also set the transcode preferences for the peering,
since it has other domain from the local subscriber,
but by the scenario check has to get the PCMA.
Change-Id: I35501b3a10351af7fddbc227a4ff34628bf171ce
Current regexp inside file scenarios/invite_fritz_prefix_removal/0033_test.yml.tt2
checking P-App-Param header does not take into account param fast_ack which is only available
on PRO, causing CE runs to fail.
Work fast_ack is now optional.
Additionally it's a good idea to make the regexp more generic checking the other parameters
against letters instead of fixed numbers/words.
Change-Id: I02ae1d435d8012bbb091aa6d8c6a840b43377971
New scenario to check FROM anonymization and PAI removal
for calls from PSTN with Privacy: id header.
Change-Id: If61ec9af775ecf10151ed458fd1ce5e0a5f7b775
Check fritz prefix removal behaviour with emergency mappings.
Change-Id: I5de2337ce8ba7c193032b81c129b28c5fefeabf8
(cherry picked from commit ef4b381058a83f7f553e42518c52bef2bc5f799e)
New scenario scenarios/invite_fritz_prefix_removal
- Call 1: A new call is generated towards sip:+431112@invite-fritz-prefix-removal.scenarios.test
Due to fritz prefix removal feature it must be changed into 112@invite-fritz-prefix-removal.scenarios.test
- Call 2: A new call is generated towards sip:+4312000@invite-fritz-prefix-removal.scenarios.test (voicebox)
Due to fritz prefix removal feature it must be changed into 2000@invite-fritz-prefix-removal.scenarios.test
- Call 3: A new call is generated towards sip:0999112@invite-fritz-prefix-removal.scenarios.test
Even if 112 is part of the "special numbers" list in config.yml, the prefix removal cannot happen because 0999
is not in the prefixes list.
Change-Id: I8ca655faf31b9d07f8b103cb3c8cfd05d7bfb065
(cherry picked from commit 7c85a4d806fa4b6af6f71cf28322036baa3f566f)
Since we are mounting in read-only mode the code, we are getting
warnings from pytest executions not able to generate .pytest_cache
directory.
Just define CACHE_DIR in a volumen that is mounted as read-write
Change-Id: I9949877f4d86873f47778ae9a7cddffb45f3932c
Alessio Garzi
Donat Zenichev
Victor Seva
Sipwise Jenkins Builder
Marco Capetta
Kirill Solomko
Guillem Jover