Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm interested in building an android app that calls another android app via the Asterisk server. It will be strictly SIP to SIP without connection to a PSTN.

I've read you can have thousands of concurrent calls based on the set up of this OP here: Performance of Asterisk Telephony System on Linux

So my next question is, I heard briefly that some systems administrators like to impose a limit on the number of concurrent calls. Is the advantage here mainly to control the bandwidth and resources used on the computer? Or are there other considerations?

share|improve this question
up vote 1 down vote accepted

Usual reasons I can think of to limit concurrent calls would be:

  • Limited bandwidth available. Better to have 100 good quality calls than 200 horrible ones
  • Possibly slow down or prevent DOS attacks from opening too many calls and bringing the server to its knees.
  • Limited processing power - if the calls require reencoding for different codexs at each end it can eat a lot of cpu cycles per call
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.