503 service error on incoming calls

Status
Not open for further replies.

scg_chris

New Member
Apr 15, 2020
11
1
3
Knoxville, TN
It seems the server stops working after about ~130 concurrent incoming calls hitting an IVR at a single time. I need the system to support 700+ concurrent calls at any given moment. We are currently in testing, but where can I look in FusionPBX setting for something that could be limiting call volumes.

Thanks!
 

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,498
413
83
When you get the 503, do you see an entry in the FreeSwitch log file?
What happens with the same number of concurrent calls but not hitting an IVR?

Have a look at your default settings in /etc/freeswitch/autoload_configs/switch.conf you may be hitting the sessions-per-second limit.
 

scg_chris

New Member
Apr 15, 2020
11
1
3
Knoxville, TN
I found this in the logs`2020-05-08 02:16:56.723819 [CRIT] switch_core_session.c:2357 Throttle Error! 87`

I did update the switch.conf.xml file to have 1000 sessions per second.

had to restart, but its working perfectly now! Thanks @Adrian Fretwell

Code:
freeswitch@ip-172-31-12-33> status
UP 0 years, 0 days, 0 hours, 19 minutes, 34 seconds, 798 milliseconds, 138 microseconds
FreeSWITCH (Version 1.10.2 -release-14-f7bdd3845a 64bit) is ready
2201 session(s) since startup
0 session(s) - peak 1080, last 5min 1080
0 session(s) per Sec out of max 1000, peak 71, last 5min 70
2000 session(s) max
min idle cpu 0.00/35.30
Current Stack Size/Max 240K/8192K
 

Attachments

  • 1588945760926.png
    1588945760926.png
    12 KB · Views: 23
Last edited:
  • Like
Reactions: Adrian Fretwell

Adrian Fretwell

Well-Known Member
Aug 13, 2017
1,498
413
83
Your seconds per second still shows max 30. You can look at and change the sessions-per-second values at the fs_cli with:
fsctl sps

or to set it:
fsctl sps 100
 
Status
Not open for further replies.