We want it for CDR fields setting. Currently CDR is written or such forcefully terminated calls, but it lacks some post-processing which we have in event_route[dialog:end].
Whoever is going to work on this - please leave your wallet info (e.g. paypal) for my thanksgiving.
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/190
I have found an instance where using an avp or xavp as the response variable for http_query will cause a segfault later in t_relay(). When I change the variable to a $var instead of an avp, there is no segfault.
I can only recreate it with a specific URL. If I try to reproduce it by simply sending a plain text response from a static page, it does not segfault.
The http_query command is as follows:
http_query("http://cnam.dashcs.com/?companyId=XXXXX&password=XXXXXXX&number=$avp(from_p…", "$avp(cnam)");
version: kamailio 4.3.0 (x86_64/linux) c6aa95
flags: STATS: Off, USE_TCP, USE_TLS, TLS_HOOKS, USE_RAW_SOCKS, DISABLE_NAGLE, USE_MCAST, DNS_IP_HACK, SHM_MEM, SHM_MMAP, PKG_MALLOC, F_MALLOC, DBG_F_MALLOC, USE_FUTEX, FAST_LOCK-ADAPTIVE_WAIT, USE_DNS_CACHE, USE_DNS_FAILOVER, USE_NAPTR, USE_DST_BLACKLIST, HAVE_RESOLV_RES
ADAPTIVE_WAIT_LOOPS=1024, MAX_RECV_BUFFER_SIZE 262144, MAX_LISTEN 16, MAX_URI_SIZE 1024, BUF_SIZE 65535, DEFAULT PKG_SIZE 8MB
poll method support: poll, epoll_lt, epoll_et, sigio_rt, select.
id: c6aa95
compiled on 13:39:06 Jun 10 2015 with gcc 4.8.2
---
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/212
Hello,
while investigating https://github.com/kamailio/kamailio/issues/212, I
noticed some potential issues in http_query() from utils module. Not
being the developer and not using this function myself that much so far,
I wanted to get others reviewing my remarks.
1) at line 168 in the modules/utils/functions.c, download_size is get
via CURL option and it is used in the following lines as size of
stream.buf, which is allocated with pkg, but set to have the size
stream.curr_size. For me it doesn't look safe to use download_size as
limit to walk through stream.buf
2) same for setting the value of PV, when CRLF is not found
download_size is used
3) in write_function(), it seems that for successive calls of the
function one extra byte is added to the size. It is intended for keeping
ending '\0', but should be enough only once. Could be harmless (few
extra bytes allocated, when not really needed), but is important to know
that actual value is up to stream.pos+1 (to include the '\0'), not to
stream.curr_size.
Are those above valid, or did I miss something?
Cheers,
Daniel
--
Daniel-Constantin Mierla
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
Book: SIP Routing With Kamailio - http://www.asipto.com
Hi,
i've noticed, that the current Debian-Packaging uses the current
directory as RUN_DIR for tools like kamcmd.
Due to this, i get the following error when running kamcmd (from the
Debian-Packages):
~# kamcmd
ERROR: connect_unix_sock:
connect(/home/carsten/build/ims/sip-router/debian/kamailio/var/run/kamailio//kamailio_ctl):
No such file or directory [2]
The default should be "/var/run/kamailio/kamailio_ctl", not
"/home/carsten/build/..." where i build the package....
Is there a proper way, to set the RUN_DIR correctly, when building packages?
I've noticed, it's the same for Debian Packages from the official repository....
Thanks,
Carsten
--
Carsten Bock
CEO (Geschäftsführer)
ng-voice GmbH
Schomburgstr. 80
D-22767 Hamburg / Germany
http://www.ng-voice.com
mailto:carsten@ng-voice.com
Office +49 40 5247593-0
Fax +49 40 5247593-99
Sitz der Gesellschaft: Hamburg
Registergericht: Amtsgericht Hamburg, HRB 120189
Geschäftsführer: Carsten Bock
Ust-ID: DE279344284
Hier finden Sie unsere handelsrechtlichen Pflichtangaben:
http://www.ng-voice.com/imprint/