Just have noticed something new today. Testing a local instance on CentOS 6.0 with FreeSWITCH Version 1.2.23~64bit. FreeSWITCH seems to be changing the max_sessions param automatically. This happens when typically I bridge around 1000 sessions and whatever value I set to sps and max_sessions, it comes down.
 
UP 0 years, 0 days, 0 hours, 37 minutes, 54 seconds, 362 milliseconds, 294 microseconds
FreeSWITCH (Version 1.2.23  64bit) is ready
74716 session(s) since startup
 976 session(s) - peak 1022, last 5min 985
112 session(s) per Sec out of max 400, peak 9053, last 5min 317 <- BTW This peak was never tried, not sure why it says 9053
 5000 session(s) max
min idle cpu 0.00/55.00
Current Stack Size/Max 240K/8192K
 
=======
followed by
=======
 
switch_core_session.c:2288 Over Session Limit! 1013
mod_sofia.c:4884 Error Creating Session
 
=======
And then
=======
 
freeswitch@internal> status
UP 0 years, 0 days, 0 hours, 38 minutes, 35 seconds, 372 milliseconds, 831 microseconds
FreeSWITCH (Version 1.2.23  64bit) is ready
76231 session(s) since startup
 560 session(s) - peak 1023, last 5min 1023
0 session(s) per Sec out of max 400, peak 9053, last 5min 317
 1013 session(s) max
min idle cpu 0.00/99.00
Current Stack Size/Max 240K/8192K
 
 
Is this something changed recently? Or some sort of server meltdown protection mechanism being forked :)