Hi,

On our Production FreeSWITCH box:

FreeSWITCH Version 1.0.head (git-4c435ec 2011-03-14 11-54-08 -0500)

UP 0 years, 14 days, 6 hours, 28 minutes, 44 seconds, 474 milliseconds, 751 microseconds

12519 session(s) since startup

2 session(s) 0/30

1000 session(s) max

min idle cpu 0.00/100.00

At 14:30:37 a reloadxml command was issued.

At 14:30:43 the box started rejecting all calls with 503 error. 

At 14:38 it started working again. 

Looking at the code I see three conditions can trigger this behavior:

              if (sess_count >= sess_max || !sofia_test_pflag(profile, PFLAG_RUNNING) || !switch_core_ready()) {

                        nua_respond(nh, 503, "Maximum Calls In Progress", SIPTAG_RETRY_AFTER_STR("300"), TAG_END());

                        switch_log_printf(SWITCH_CHANNEL_LOG, SWITCH_LOG_CRIT, "No more sessions allowed at this time.\n");

                        goto done;

               }

Logs show it wasn’t lack of available sessions.  How can sofia_test_pflag(profile, PFLAG_RUNNING) or switch_core_ready() fail and busy the system?

Thoughts? Thx, Chris.