* simple POST via request function
* interface to store/retrieve/delete values from a list
at central redis
Change-Id: Ibae0f9b5c04dec3004b6d33e271866c722da3182
* 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
The 'duration' variable is a string but it was written as int,
causing kamailio to write error lines
Change-Id: I2df1524d331e9b1d54bb0bdb84c06f4280e14fae
> ngcp/fp.lua:30:121: line is too long (126 > 120)
> ngcp/pprof.lua:28:121: line is too long (158 > 120)
Change-Id: Icf87f29049b2cc4ce29e7c1f5c78d9f2a53572c0
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
* 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 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
Support for detecting SIP loops for kamailio.
Count on redis the combination of $fu;$tu;$ru in a period
of time
Change-Id: I3a34e3086490a26bbd4a6db8e4efc86145bfb017
The count argument influences the operation in the following ways:
* count > 0: Remove elements equal to value moving from head to tail.
* count < 0: Remove elements equal to value moving from tail to head.
* count = 0: Remove all elements equal to value.
Change-Id: Ia77b760fcada0027fe58a48f4b335d5c264e8917
if true it will check for duplication of keys at the list of counters used
when calling set(). Added is_in_set() to check if a key is already there
Change-Id: Ib1da91dd3cdb13c537577d8e36c1a22920112ce0