Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-12-16 Thread Daniel-Constantin Mierla
Date: Mon, Jan 28, 2013 at 10:08 AM Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations? To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-12-12 Thread Sotas Development
to be properly cross compiled. Regards, Ovidiu Sas -- VoIP Embedded, Inc. http://www.voipembedded.com -- Forwarded message -- From: Sotas Development sotas...@gmail.com Date: Mon, Jan 28, 2013 at 10:08 AM Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-11-27 Thread Sotas Development
-Users] Kamailio stability/timing problem w.r.t. registrations? To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List sr-users@lists.sip-router.org Hi Ovidiu, Thanks for the warning! We did not yet have much success running the current master branch

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-11-27 Thread Ovidiu Sas
, Inc. http://www.voipembedded.com -- Forwarded message -- From: Sotas Development sotas...@gmail.com Date: Mon, Jan 28, 2013 at 10:08 AM Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations? To: SIP Router - Kamailio (OpenSER) and SIP

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-11-13 Thread Sotas Development
://www.voipembedded.com -- Forwarded message -- From: Sotas Development sotas...@gmail.com Date: Mon, Jan 28, 2013 at 10:08 AM Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations? To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-11-13 Thread Ovidiu Sas
-- VoIP Embedded, Inc. http://www.voipembedded.com -- Forwarded message -- From: Sotas Development sotas...@gmail.com Date: Mon, Jan 28, 2013 at 10:08 AM Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations? To: SIP Router - Kamailio (OpenSER

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-01-28 Thread Ovidiu Sas
sotas...@gmail.com Date: Mon, Jan 28, 2013 at 10:08 AM Subject: Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations? To: SIP Router - Kamailio (OpenSER) and SIP Express Router (SER) - Users Mailing List sr-users@lists.sip-router.org Hi Ovidiu, Thanks for the warning! We did

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-01-17 Thread Sotas Development
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.

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-01-17 Thread Ovidiu Sas
Hello Michiel , You should check with top to see the status of all kamailio processes. If you see processes that are using 100% CPU, you may have a deadlock. Connect with gdb to the process to investigate what's going on. Also, you are running on arm. How did you compiled kamailio: native or

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-01-17 Thread Sotas Development
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

Re: [SR-Users] Kamailio stability/timing problem w.r.t. registrations?

2013-01-17 Thread Ovidiu Sas
If you are running the stable version, there's need for heavy Makefile patching in order to properly cross compile (not to include and link to host libs). The trunk has everything fixed and it's cross-compiling properly for most of the modules. Make sure that your binaries are properly cross