- Fix «== None» with «is None».
- Fix blank lines around class and defs.
- Fix spaces around comma.
- Fix ambiguous one character variable names.
Warned-by: pycodestyle
Change-Id: Iaf44a31341e4ae66082df3c519edd69a39db356c
- Update copyright years.
- Update Standards-Version to 4.7.2.
- Remove «Rules-Requires-Root: no» field, which is now the default.
- Remove «Priority: optional» field, which is now the default.
- Wrap and sort fields.
- Add spaces around operators in make variables.
Change-Id: Ib769f6f4a07c1bb35d78e3bd47b8aca76011adb6
Importing all functions is useless because Sipwise::API does not
define an import routine. This was tolerated on Debian 12, but
starting from Debian 13 (Perl v5.40.1) it produces a warning.
The warning is harmless, but using qw(all) is incorrect.
All scripts under bin/ have been patched to remove qw(all).
Change-Id: I98f9f63a250c86b1e55f8368724bd4a19bb969ba
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 syntax is discouraged, and it is not enabled by default any longer
starting with the 5.36 feature bundles. Stop using it so that we can
eventually bump our minimum required Perl version.
Fixes: Objects::ProhibitIndirectSyntax
Warned-by: perlcritic
Ref: https://metacpan.org/pod/feature#The-'indirect'-feature
Change-Id: I46ede719e6cf75fa3c5a69b467920b00acb388b2
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
Guillem Jover
Sipwise Jenkins Builder
Alessio Garzi
Donat Zenichev
Marco Capetta
Victor Seva
Fabricio Santolin da Silva