Asterisk.conf Ignored?
Hi all
I’m trying to limit the maximum concurrent calls on my Asterisk to try and mitigate another problem I posted about earlier.
I’ve edited
/etc/asterisk/asterisk.conf
And uncommented this line, and put a value of 60 in there:
maxcalls = 60
in an effort to limit my Asterisk to 60 simultaneous calls.
I did a
core reload
in the CLI after doing that.
Any idea why my running instance totally ignores this setting? I still goes right ahead and services unlimited numbers of simultaneous calls – we have
90 extensions or so and it will happily service 90 simultaneous calls in spite of asterisk.conf clearly stating
maxcalls = 60
The “maxload” specification is also ignored, load can go anywhere the Asterisk instance keeps taking more calls despite load exceeding, for example
maxload = 10
in /etc/asterisk/asterisk.conf
What am I doing wrong that the asterisk binary is apparently ignoring settings in /etc/asterisk/asterisk.conf?
Thanks
Stefan
3 thoughts on - Asterisk.conf Ignored?
You should try to limit it in your sip trunks (is you are using SIP
trunks, of course)
Marcelo H. Terres
IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres
—
This limit is only valid for inbound calls:
Sets a maximum number of simultaneous inbound channels. No limit is set by default. Marcelo H. Terres
IM: mhterres@jabber.mundoopensource.com.br https://www.mundoopensource.com.br https://twitter.com/mhterres https://linkedin.com/in/marceloterres
—
I suppose asterisk.conf is not read on a reload. IIUC it is read before the rest of the configuration.
Another small thing that makes it slightly different:
In any other configuration file you can either have ‘#include relative/path’
or ‘#include /absolute/path’ to include files. A relative path would be relative to $astetcdir. However when reading asterisk.conf, $astetcdir is not set yet, and thus ‘#include relative/path’ would generally not work as expected.