from().
>
> Can you also provide the output for 'kamailio -I' (that's upper case i)?
>
> Cheers,
> Daniel
>
>
>
> On 11/27/13 4:44 PM, Ovidiu Sas wrote:
>
>> Try to attach gdb to the kamailio processes and run a full backtrace.
>>
>> Regards,
&g
Hi,
I want to build a Kamailio version without the usage of futex. First of all
I notice that the variable "use_futex" within Makefile.defs is hardcoded
to the value "yes". Why is that? I want to get rid of this and build
Kamailio without futex support. In the same file there are GCC options
like
thout atomic locks.
>
> Regards,
> Ovidiu Sas
>
> On Wed, Nov 13, 2013 at 10:40 AM, Sotas Development
> wrote:
> > Hi,
> >
> > Here's an update of this topic. We've tried again with the latest stable
> > version 4.0.4. Unfortunately the problem st
Hello All,
We are currently cross compiling Kamailio for powerpc and are encountering
an "issue", of which we want to know whether or not it is intentional. In
the modules/auth_diameter/diameter_msg.h of Kamailio 4.0.4 (latest) we
found the following line:
72: #error BIG endian detected!!
Bu
t; --
> VoIP Embedded, Inc.
> http://www.voipembedded.com
>
> ------ Forwarded message --
> From: Sotas Development
> Date: Mon, Jan 28, 2013 at 10:08 AM
> Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t.
> registrations?
> To: "SIP Router - Kama
Hi Ovidiu,
Thanks for the warning! We did not yet have much success running the
current master branch, though this may well be a resource problem on
the target platform.
For the moment, we decided to switch back to openser 1.3.5 and wait
for the official 4.0 release.
Regards,
Michiel Veldkamp
Hi Ovidiu,
Good points. We're not running out of memory, and all processes keep
running.
Top shows 0% or 1% CPU load for the Kamailio processes.
We cross-compile with the CodeSourcery toolchain. The default build options
drag in the file atomic_unknown.h, that produces the following compile
warni
Daniel,
> can you add an xlog() at the start of the main route block and log a
message for any
> request received? [...] You can put another xlog before the save()
function to see if
> registration requests are getting there. [...] You can switch to kamailio
flavour modules
> and see if reproduces
Hi,
We run Kamailio 3.2.3 (FLAVOUR=ser) on an embedded ARM platform in near-
default configuration.
In a duration test, we observe that at a certain moment Kamailio seems to
start ignoring all (re-)register messages, and eventually expires the
existing registrations.
We have not been able to rep
