Re: [OpenSIPStack] Call Capacity Stats

[<jo...@op...>]

I don't think you are hitting a call capacity limit but an OS limit.  
OpenSBC should not die in this kind of very forgiving test scenario in 
60 concurrent call.  For example, we have servers that accepts 300-400 
simultaneous connections and the only side effect of this is very high 
CPU usage not crashes.  10 CPS is well within OSBC capabilities.    I am 
suspecting that you still have a misconfiguration somewhere in terms of 
the number of per process file handles your system accepts.  ulimit -n 
is not always guarantee that actual os limits are adjusted due to 
misconfigurations somewhere.  Lastly, there were recent bug fixes that 
indeed caused crashes in OpenSBC commited within the last five days.  
You might want to checkout the latest.

Chris Veazey wrote:
> We are ramping from 1-10 call/sec in 1 call increments and 2 minute hold times. We see the OSBC processes die when we hit about ~60 concurrent calls. The time it takes for the OSBC processes to die depend on the number of call/sec. So 1call/sec we die at about 60-80 seconds. At 10 calls/sec, we die in 6-8 seconds.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> opensipstack-devel mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensipstack-devel
>
>
>
>