Test "incoming_hih" adapter to change at 836972700a3794d74aefb6360a1a6c2f1f066d40.
Reason word must precede the cause inside new hih headers.
Change-Id: I0bb7d196b40d5d32cf82a59d545d30f46418bcc0
In this scenario, kamailio proxy is returning this reply
in one of the test:
SIP/2.0 400 Ivalid To Header
Via: SIP/2.0/UDP 10.20.29.2:51602;branch=z9hG4bK-195953-1-4;rport=51602
From: <sip:testuser1003@sanity.scenarios.test>;tag=195953SIPpTag001
To: 500;tag=244d833d81f839382236e956655c48a4.bef88c60
Call-ID: NGCP%sanity%///1-195953@10.20.29.2
CSeq: 3 REGISTER
Server: Sipwise NGCP LB trunk
Content-Length: 0
The word "Ivalid" is a typo from upstram kamailio.
At the time of writing this commit message I issued a PL
on github:
e13bc796db
Since I do not know when and if it will be accepted, I am changing the kct test in order
to accept also the word "Ivalid".
Change-Id: Ie51030fd0eca56d98a3ffbb40be0fae5260b293b
This new scenario checks the integrity of :
- Authorization header
- From header
- To header
- Contact header
Checks must be performed at LB level using
kamailio "sanity" module.
Change-Id: I870d5ec15ba584357c1b0bfc26f4aa5fcb47fa05
In the test we were setting peers max call limit to
-1 to prevent a call to a peer
0 to let the call go through a peer
Thsi is logically wrong and it is now fixed setting
the limits to 0 and 1.
Change-Id: Ia3ad63ea5db6981d87f402f35224703cc0a2fc73
New scenario to test registrations with contact: *.
The scenario checks that contact * is treated as special character
by kamailio proxy and ensures that the callee if offline.
Change-Id: I25dfd00278668120413b3f4da17559421bbfde1c
A new call has been added inside scenario incoming_peer.
In this new call a peer calls a subscriber which has the prefix 0043
inside adm_block_in_list because he does not want to get calls from this
particular prefix.
The call ends with a 403 Blocked by Admin reply from kamailio proxy.
Change-Id: Ia9f87837d2a6d655c5cb18d9de29abb3380f7939
Rtpengine now properly process the codec filtering and thus
the scenario has to be fixed accordingly. In particular:
* no video codec is blacklisted, so it should be represented
exactly like as it is received
* audio codec are properly filtered including the telephony-events
that doesn't have rate 8000.
Change-Id: I979f7e1d80c3dfe440f5351a3c95c3ed7beadc4c
This reverts commit 9d7257367d.
Reason for revert: the fix is not necessary in recent versions, because DTMF are properly filtered based on the rate of the codecs, and Video is part is fixed as well.
Change-Id: I985420a040b4be35c4de9cc129970262b018e1ac
This fix an issue when running KCT on a machine that have a few
particular settings that could invalidate some tests.
Change-Id: Ia693a515d85427f731c9b9209efe5138982da189
Scenario invite_hm has been extended to test new direction
b_outbound.
Kamailio proxy now is expected to create header OutboundBlegHeader with value
"blegvalue".
The new invite_hm scenario will provision an additional header manipulation and will
check if this header has been correctly produced by kamailio proxy.
Change-Id: Ibae2bb0e8dd4ee236c14517552c378f89a766e3a
Scenario invite_hm extended, it now dials a second call with
P-Asserted-Identity header so that the corresponding HM will reject the call
with a 456 error message.
Change-Id: Ie71666ad4478b47aebc3ceac851aff439ef4ac84
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
* 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)
Parameter fast_ack=no could be missing depending if we are running CE or PRO.
The regexp has been changed in order to accept both version with fast_ack and without.
Change-Id: I92b3cd043f301c145d820ad113eadf3471ba97e0
Alessio Garzi
Donat Zenichev
Marco Capetta
Victor Seva
Fabricio Santolin da Silva
Kirill Solomko