Daniel good morning,

The syslog I have is the standar centos installation. I don't understand what you mean. The benchmark module I haven't use yet.(I finding it a bit difficult to use :-( )
BUT
I found this:
In my kamailio.cfg I had some extra logging fields (acc extra accounting) in the mysql and also the cdr in mysql. That is giving heavy load in mysql and I see many call failing. I disabled that and now I have a CPS 40 with concurent calls 12.000. The failed calls are 11 only. This seems good.
But even I'm NOT logging CDRs in mysql I still see mysql in 70% CPU load and I don't understand why. I beleive that Kamailio when is starting up is getting into memory all mysql data, in my case from PDT,Dialplan and Dispatcher tables.

So the question now is why mysql is working so hard ?

I'm also sending you my kamailio.cfg because maybe you can see something I haven't mention..

Thanks for the great help ;-)

Alexandros


On Mon, Dec 14, 2009 at 7:28 PM, alex pappas <rebel.pappas@gmail.com> wrote:
Daniel i hope you are well.

Thank you for your help. I will check all these and get back to you asap.

Alex



On Mon, Dec 14, 2009 at 5:32 PM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,


On 12/14/09 1:50 PM, alex pappas wrote:
Daniel hi,

We don't have packet loss and the log level is 1.
Concerning the the asyncronous loging: This should be set before compilation?

"""""""""""""""""""""""
http://openser.blogspot.com/2008/10/asynchronous-syslogging.html
This functionality can be enabled with setting the define SYSLOG_ASYNC in the Makefile.defs file. The default is the normal log functionality from the system library, nothing changed if the define is not set.
no, it is not about this. By asynchronous syslog I meant the syslog config in the system, nothing related to source code of kamailio.

If the log level is 1 then you should not see many syslog messages.

Maybe is better to use the benchmark module to identify where is the delay coming from (if it is from kamailio config).

Cheers,
Daniel


"""""""""""""""""""""""""""""""""

Cheers

Alex


On Mon, Dec 14, 2009 at 2:31 PM, Daniel-Constantin Mierla <miconda@gmail.com> wrote:
Hello,


On 12/14/09 12:36 PM, alex pappas wrote:
Dear users,

I'm using kamailio in the following scenario:

1. A call comes in and is checked against PDT module. From this module depend from the prefix I'm getting back the domain which is used as the dialplan group.
2. After that the call is checked against Dialplan module using the previous value from PDT as Dialplan dpid. From the Dialplan module i get back  the the attributes values.
3. these attributes values are user in the dispathcher module where I continue with failover scenarios.

Also the script is working with a radius for accounting purposes.

This scenario works perfecttly and it is still in a testing mode.

An the problem:

I'm running SIPP against this scenario and until the CPS is 5 everything looks good. The scenario for SIPP is the simplest. uac and uas default. Uac is sending a call and uas is answering.
When the CPS goes above 9 then I have call failures. All the statistics are going down.
I'm cheking for CPU load or other system problems but I don't see anything strange. Does anyone understand why this is happening?
do you have high debug level? Is your syslog configured asyncronous?

Are network packets dropped from the network interface?

Cheers,
Daniel

--
Daniel-Constantin Mierla
* http://www.asipto.com/



-- 
Daniel-Constantin Mierla
* http://www.asipto.com/