Simultaneous call limitation

From Kolmisoft Wiki
Revision as of 09:33, 23 January 2013 by Aisteb (talk | contribs) (→‎About)
Jump to navigationJump to search

About

It is possible to limit simultaneous calls per provider/DID/user/device basis.
These settings limit simultaneous calls, not how many total calls the user/device/provider(/did) can make.
When no more calls can be made, the dialer hears the BUSY signal.

Provider



Prov.png

Call limit - describes how many simultaneous calls the provider can make. 0 (zero) means that calls are unlimited.

Hangupcause code 223 means that the provider can't make more simultaneous calls.

This limit is for outgoing calls through this provider.


User



MOR 0.8.png

Call limit - describes how many simultaneous calls the user can make. 0 (zero) means that calls are unlimited.

Hangupcause code 220 means that the user can't make more simultaneous calls.

Hangupcause code 222 means that a reseller (as a user) can't handle (allow to his users to make) more simultaneous calls.

This limit is for outgoing calls made by this user.

Device



Devlimit.png

Call limit - describes how many simultaneous calls the device can make. 0 (zero) means that calls are unlimited.

Hangupcause code 221 means that the device can't make more simultaneous calls.

This limit is for outgoing calls made by this device.


NOTE: MOR uses internal call limiting engine, so call limit which is shown in "sip show peer" output, has no relation to the Call Limit in the MOR GUI.

DID



Didlim.png

Call limit - describes how many simultaneous calls DID can receive. 0 (zero) means that calls are unlimited.

Hangupcause code 219 means that DID can't receive more simultaneous calls.

This limit is for incoming calls made to this DID.


Special case

When DID points to a device and the limit is reached, calls will be routed to the device via BUSY - Call Flow. This will ring another device or send a call to VoiceMail when the main device already has a call.