Yes, xlog statements have been left in place. Only the "log_extra"
parameter of acc was changed.
I've tested the $avp replacement and it does not look like it leaks pkg mem.
On Mon, Apr 22, 2013 at 9:49 AM, Daniel-Constantin Mierla wrote:
> Hello,
>
>
> On 4/19/13 12:42 PM, Tais Plougmann Han
Hello,
On 4/19/13 12:42 PM, Tais Plougmann Hansen wrote:
I had added $ai to acc log_extra like this:
modparam("acc", "log_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;"
"dst_ouser=$tU;dst_user=$rU;dst_domain=$rd"
"p_asserted_identity=$ai;remote_party_id=$re")
Once I commented ou
I had added $ai to acc log_extra like this:
modparam("acc", "log_extra",
"src_user=$fU;src_domain=$fd;src_ip=$si;"
"dst_ouser=$tU;dst_user=$rU;dst_domain=$rd"
"p_asserted_identity=$ai;remote_party_id=$re")
Once I commented out the last line, the leak vanished.
Apr 17 16:55:41 gws1 /u
Hello,
I looked quickly to the core and seems ok, I will check the accounting
later.
Do you simply account $ai or is any other attribute related to it?
If you have time to test, can you put the $ai in an avp during the
request processing and account that avp? If the leak is not shown
anymor
Hi,
I'm seeing a possible leak in parsing the P-Asserted-Identity, and possibly
P-Preferred-Identity headers in kamailio-3.3.4.
I have a server running in which one thread has currently most of the 8 MB
private memory allocated. At restart qm_sums reports parse_pai.c as sitting
on most of the mem
