output was changed to json but the regex for filtering list: values
was not updated
* migrate fixtures to json
Change-Id: Ifa18e87ef935dae8e8fab75095591646101c06c1
The following scenario disclouse an issue with "ngcp_clean" lua
function in case of callee peer:
- A is a local subscriber with Peer_auth set and
force_outbound_call_to_peer set;
- B is a local subscriber with Peer_auth set and
force_outbound_call_to_peer set;
A calls B.
We clean and load callee preferences of B.
Call is detected as forced to PSTN.
We clean and load peer preferences.
When we set outbound peer_auth* values, the $xavp(callee_prefs)
still contains values from B (instead of peering preferences).
When we clean preferences for the callee peer, we only
clean "callee_peer_prefs" and not "callee_prefs".
"callee_prefs" are clean only in case of 'usr' or 'dom'
preferences.
This patch try to fix this problem in order to fix this
scenario with outbound user authentication.
Change-Id: I76dfa6f9e074b3d83ac67bd818e59233ca50492c
Added a new list element named "joined", which store a value
of 1 when the app register after the push in order to record
that the app has joined. Otherwise it contain a value of 0.
lua-redis >= 2.0.5~git20141117.880dda9-7~ is needed
Change-Id: Ie8121eaa5c1ce4a82b1c086b4b34c25213e8d4e8
We were using a mix of .new() and :new() and
that lead us to errors when calling new with parameters
Just be consistent and choose one
Change-Id: Icc2078efb377b80942b2fb518db52df339ecda6a
Unify redis interaction in a class
* allow passing partial config via new()
config will be merged using defined defaults so
missing keys will be appended using values from defaults
Change-Id: I486637e99e0e36fbe1f5a06c703c6b7d2fa77d77
The new function behaves like NGCPDlgCounters:is_in_set but
it uses a regex match to see if the key is contained in the list
Additionally added the helper function 'contains_regex' in the
utils.lua
* ignore vscode files
Change-Id: Iee89f5298ced10c2a9cdf7ebc19a4c0945b8cc9d
Running the test suite on bullseye/sid generates the following warning:
,---
====================================================================== warnings summary ================================================================>
/usr/lib/python3/dist-packages/_pytest/junitxml.py:446
/usr/lib/python3/dist-packages/_pytest/junitxml.py:446: PytestDeprecationWarning: The 'junit_family' default value will change to 'xunit2' in pytest 6>
https://docs.pytest.org/en/stable/deprecations.html#junit-family-default-value-change-to-xunit2
for more information.
_issue_warning_captured(deprecated.JUNIT_XML_DEFAULT_FAMILY, config.hook, 2)
-- Docs: https://docs.pytest.org/en/stable/warnings.html
`---
Adding a config file and setting the junit family explicitly fixes
silences the warning.
Change-Id: I929b0c4630769ed263be0aeb8776a0233954e599
* final value is fetched from provisioning using pref value as id
* config: list of preferences needed to be loaded by kamailio
so we wont load unnecessary data into shared memory
Change-Id: I92e4bbfbe7ba55a06e79384aaa0d792556a39e22
https://www.lua.org/manual/5.2/manual.html#8.3
> (Modules are not expected to set global variables anymore.)
EXPORT_ASSERT_TO_GLOBALS was just there for backwards compatibility
Change-Id: I11ac6d24746ca3c965b16ad523efff1f12ef0e9a
We are going to use both modules app_lua and app_lua_sr until we
solve the missing pieces on KEMI:
* KSR.pvx.xavp_get() returns a string like '<<xavp:%p>>' not a table like
sr.xavp.get()
* KEMI lacks of something like sr.xavp.get_keys() funtion
So, migrate everything that we can to KEMI and keep using sr approach
for just that two cases
- mocks/sr.lua: use same objects for same behaviour
Change-Id: I475ff8f820586cdc94c75bff7466238215e05673
The script collects all the callID from redis, then, one by one
it checks if callID exist in kamailo. At this time a call existing
in redis before may be destroyed in kamailio dlg.list. And so
script believe it's a stuck call.
Solution: collect CallID from REDIS and kamailio.dlg at the same
time, and compare afterwards.
Change-Id: I233a498e42bf5113b5b11ea688487e1840cd84a6
We also need to switch from python-xmlrunner to python3-pytest, as
the former is not present in Debian unstable/testing anymore (see
<https://bugs.debian.org/935688>), and does not provide python3
support in Debian buster anyway.
Change-Id: I8af9ead2755af2e24f5bedf53d8cd20c4ed63b85
In the new version of LuaUnit assertTrue() and assertFalse()
functions are changed to striclty evaluate that the data is
True or false.
Where necessary the fuctions have been substituted in the test
with the new assertEvalToTrue() or assertNil().
Change-Id: I0c728323752a4458e93f516c7529670433c516d1
* xavp caller_fax_prefs and callee_fax_prefs is
added and automatically fetched as a part of
caller_usr_load and callee_usr_load
* fax_prefs are load all related subscriber's
NOT NULL fax preferences from
provisioning.voip_fax_preferences
Change-Id: I2dcedf30433b3d5b94efa9292437a4e7501588a3
* fix default redis db when no config file
* fix call-id list from kamailio
* refesh Docker due to TT#5032
Change-Id: Ie8847b238e5a24b22baa48fc8c9b41e39397d84e
* fix pv mock to align kamailio behavior with pv_unset() for avps.
It removes only the first value not all, only when using '[*]'
pv_unset("$avp(name)") != pv_unset("$(avp(name)[*])")
pv_unset("$avp(name)") == pv_unset("$(avp(name)[0])")
pv_unset("$(avp(name)[1])") == pv_unset("$(avp(name)[0])")
Change-Id: I1aab2150d288da546b144388adb7b2f87ecfb069
* rename set_by_uuid to set_by_key as key can be anything now
* save uuid as an additional parameter inside the key entry
Change-Id: Ic63e11855d96931b2676b991d012197c35d8ca2f