This PR cannot be merged as it is, either re-worked by the author or another
developer.
The commit message does not have the format/content from CONTRIBUTING guide,
besides the first line format, the content of the commit message is not
strictly related to what it does.
Then, the patch seems
I have compiled this app_java module on my debian buster, there's still a
memory leak problem to solve :
core> [core/route.c:872]: fix_actions(): fixing xlog()
May 31 15:15:03 PROXY-TEST-01 /usr/sbin/kamailio[16509]: CRITICAL:
[core/mem/q_malloc.c:144]: qm_debug_check_frag(): BUG: qm: prev.
@linuxmaniac by the way I tried to send it to you through irc dcc transfer on
the kamailio freenode channel
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
@linuxmaniac I think that if you try to rebuild the debs and reinclude app_java
with this makefile with openjdk as dep what we'll obtain could be something
workable. and I could test it
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
@linuxmaniac here's the makefile
`include ../../Makefile.defs
auto_gen=
NAME=app_java.so
USE_GCJ ?= no
#DEFS += -DEXTRA_DEBUG
DIST = $(shell if [ -f "/etc/redhat-release" ]; then cat /etc/redhat-release |
sed "s/.*\([0-9]\)\.[0-9].*/\1/g"; fi)
ifeq ($(DIST),6)
JVM_PATH = $(shell dirname `find
> @xevilstar good to know that You want to contribute. First try to make
> app_java work again. From what I know it was not possible to build it with
> gcj so I removed the package.
>
> I'm not the maintainer of that module and I don't have any interest in it. If
> you manage to fix it and
@xevilstar good to know that You want to contribute. First try to make app_java
work again. From what I know it was not possible to build it with gcj so I
removed the package.
I'm not the maintainer of that module and I have any interest in it. If you
manage to fix it and make it work properly
core> [core/route.c:872]: fix_actions(): fixing xlog()
May 31 15:15:03 PROXY-TEST-01 /usr/sbin/kamailio[16509]: CRITICAL:
[core/mem/q_malloc.c:144]: qm_debug_check_frag(): BUG: qm: prev. fragm. tail
overwritten(55c775816cd0, abcdefed)[0x7f64aa9c9d80:0x7f64aa9c9db8]! Memory
allocator was called
The output of `kamctl trap` does not show any blocked process, the sip workers
are listening for network traffic. Either you did the trap command when the
blocking didn't happen or something else (e.g.firewall) was blocking the
traffic.
I noticed that you have children=2/tcp_children=2, so if
> The licensing remark was in general, referring to the fact that `not all
> modules are packaged` ... read carefully what I wrote.
>
> Also, note the remark that you can also contribute by making a pull request
> to the packaging specs. After all, this is an open source collaboration
>
May 31 13:07:05 PROXY-TEST-01 /usr/sbin/kamailio[5924]: INFO: pike [pike.c:97]:
pike_init(): PIKE - initializing
May 31 13:07:05 PROXY-TEST-01 /usr/sbin/kamailio[5924]: INFO: pike
[ip_tree.c:81]: init_lock_set(): probing 256 set size
May 31 13:07:05 PROXY-TEST-01 /usr/sbin/kamailio[5924]: INFO:
The licensing remark was in general, referring to the fact that `not all
modules are packaged` ... read carefully what I wrote.
Also, note the remark that you can also contribute by making a pull request to
the packaging specs. After all, this is an open source collaboration project,
everyone
Module: kamailio
Branch: 5.2
Commit: 2d2b993673d0296e6d9c08ff78b73341e407a37a
URL:
https://github.com/kamailio/kamailio/commit/2d2b993673d0296e6d9c08ff78b73341e407a37a
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2019-05-31T12:57:56+02:00
htable: fix a possible null pointer
I don't think there might be licensing problems using openjdk 11.0.3 2019-04-16
please make the deb
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Afaik, the official debian repo as well as the deb.kamailio.org have same
packages. Not all modules are packaged due to missing dependencies or licensing
constraints. app_java was removed because the gcc compiler suite removed the
one for java. Nobody took the time to look for a proper
Module: kamailio
Branch: master
Commit: 6f0b67b675dd18dce60fa3e5a4ece063216bbab5
URL:
https://github.com/kamailio/kamailio/commit/6f0b67b675dd18dce60fa3e5a4ece063216bbab5
Author: Henning Westerholt
Committer: Henning Westerholt
Date: 2019-05-31T12:42:21+02:00
htable: fix a possible null
I am using
deb http://deb.kamailio.org/kamailio51 buster main
deb-src http://deb.kamailio.org/kamailio51 buster main
yes I did apt-get update and imported the key
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
kamailio-java ... where is it ?
apt-cache search kamailio
kamailio-autheph-modules - authentication using ephemeral credentials for the
Kamailio SIP server
kamailio-berkeley-bin - Berkeley database module for Kamailio - helper program
kamailio-berkeley-modules - Berkeley database module for the
About the other memory related bug - could you maybe try with the packages from
the kamailio repository, if you get the same error here?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Closed #1970.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1970#event-2380548522___
Kamailio (SER) - Development Mailing List
As commented in the other issue: http://deb.kamailio.org/
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1969#issuecomment-497655121___
Actually there is a official repository maintained from several developers:
http://deb.kamailio.org/
If you are referring to the debian repository, please open a issue in their
tracker.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it
https://wiki.debian.org/DebianRepository/Setup
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1970#issuecomment-497642320___
Kamailio
please put the files in the right paths like
configs /etc/kamailio/
modules /usr/lib/x86_64-linux-gnu/kamailio/modules/
binaries /usr/sbin/
etc
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Since debian excludes some modules from the repo, I'd love to have an official
debian repository for buster and stretch with all modules to add to my
/etc/apt/sources.list
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
it would be nice to have an official kamailio debian repo with all the debs of
all the modules in the right paths
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
i'd prefer to keep the paths as those are now because I hate things like
/usr/local/etc/kamailio/etc around the servers
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
is there something that is not managing memory right ?
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/1969#issuecomment-497625862___
I recompiled the module forcing the header path in the sources (the version
matches since the source is the orig from which debian builds the package):
#include "/usr/lib/jvm/java-11-openjdk-amd64/include/jni.h"
now the error changed:
May 31 09:55:04 PROXY-TEST-01 /usr/sbin/kamailio[6191]:
Hi Alex,
yes it works (just verified this morning ;-).
I use this trick in several situation, in the event-route the message is
still editable.
It's in the onsend_route that you cannot modify it, IIRC.
Cheers,
Federico
On Fri, May 31, 2019 at 8:27 AM Alex Balashov
wrote:
> Federico,
>
> Does
Federico,
Does that actually work? I thought this route provides a hook to catch
the request, but does not necessarily apply any lump changes to the
outgoing message?
On Fri, May 31, 2019 at 07:27:34AM +0200, Federico Cabiddu wrote:
> Hi,
> to add headers to locally generated requests, as it's
31 matches
Mail list logo
