* $x_hdr now behaves correctly and get/set correct value
if header name in $x_hdr is specified as AVP_NAME_STR
Change-Id: I34978a44a0f8d4af2dd94f7999a561f76729987d
commit 814d5cc1f4f5b1e4b95737108dffc1e7d7bd566f
Author: Daniel-Constantin Mierla <miconda@gmail.com>
Date: Thu Feb 28 20:15:36 2019 +0100
tm: put back t in wait timer if still referenced more than once
- have a safety upper limit for putting back in wait timer
- special credits to Yufei Tao for testing and helping to troubleshoot
Change-Id: I998626945bca5793db84987acf10bbbfb15bb405
* pv_value_t format is now parsed only if the type is PV_VAL_STR
* pv_elem_free() is now called only if pv_value_t string was parsed,
otherwise it causes operation on an invalid pointer
Change-Id: Ic9d58fd5019732f24519d9d59da09c14a426afe6
commit 40d971af44b60b2c14dcc22693d41ec4ee4af33b
topos: execute event_route[topos:sending] with current sip message to be sent
- if drop is used, then the message processing with topos is skipped
- event route is executed after event_route[topos:outgoing]
- new parameter event_mode to control what event_route blocks are executed
Change-Id: I0eb49716c8e88af61470ec262128f30357444bb7
- Kamailio-Proxy requires redis-server for every operation
- Kamailio-LB uses redis only if kamailio.lb.security.topos.enable set to 'yes'
Change-Id: I50f8914d514ffacdf2d84f19b74e8e0af34faec8
* this module enables working with headers
in the kamailio config on the variable level
and only performing the real message header
changes once in the route exit block.
Change-Id: I97ab3ee72a429c3ea92b4bd72f57b822d6091e47
Those are the commits taken from upstream version to fix the issue:
- f21554c6befaddbc82016d5d498e11ab3720c404
- 5b223a2e8a92f351b8eab756f5256fda7645ff21
- 1aad02edc6b9ffb104900cbc624f0853166ae926
- 35dec4c20d78f49ba242229c877894d70c94705c
Change-Id: I538cf7141ad4311520ec9a6ceded71b99fb93626
Quoting from https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892538
| kamailio depends or build-depends on GCJ. GCJ has been dropped
| upstream since GCC 7, so we are dropping it from Debian. Thus please
| either drop support for GCJ if you are just building an alternative
| package with GCJ support (e.g. ant-gcj, ecj-gcj) or switch to
| default-jdk / default-jre as appropriate.
Adjusting to Debian's kamailio.git change as of::
| commit 2e2722970a2921dd149156dc7f19cba52299f868
| Author: Victor Seva <linuxmaniac@torreviejawireless.org>
| Date: Thu Mar 22 16:35:14 2018 +0100
|
| remove kamailio-java-modules (closes: #892538, #893701)
Change-Id: Id3e92a376292fd4c1e5f29c7e9a4fb52f2e55f60
Import commit fcf1d3d778a903852b6e21103a23bd7fd6e3bbc9 from upstream that
solves the issue with masking Contact in 302 response from UAS.
Change-Id: I13ffa4d17c80d6dbf2e509d82e30980931e54cbe
- allow_trusted() now can take optional parameter of value to match.
- provided parameter will be used instead of From header in match_res() and match_hash_table()
- documentation extended with 3-arguments allow_trusted() function description
Change-Id: I45226cbba489bd7a60e7d8481777401b4f52024f
* avp_subst(dst, subst_rx)
- "subst_rx" now supports pvars
in addition to the static string
e.g.:
- avp_subst("$avp(s:dst)", "$avp(s:my_subst)");
- avp_subst("$avp(s:dst)", "$(rU{uri.param,my_subst})");
- inline mixed pvars are not supported
- static subst values are precomplied during the module init
(as it was before)
- dynamic pvar subst regex is evaluated and compiled on
each avp_subst() call
- optimise internal param handling for static subst values,
they are stored as (fparam_t*)->type==FPARAM_SUBST
Change-Id: Iea7a91ba87b892edd6fa405aa7cc285d69d9caa9