This guide explains the limitations which relate to the number of simultaneous Incoming and Outgoing calls that can be triggered and/or received.
Outgoing SIP and API request calls
By default, each customer account can make 1 outgoing call per second (CPS). API requests for calls that exceed the CPS rate limit will be queued and executed as capacity is available.
If you require additional Outgoing call throughput, please check with your account manager.
There is no rate limit for in-call commands such as call forwarding, or conferencing. However, there could be limitations at the destination for these calls.
There are no limits on the rate at which projects can receive inbound calls. Every incoming call received at your Unifonic phone number corresponds to an HTTP request we submit to your webhook/request URL. We recommend users make sure their server is capable of handling the load if they are expecting a large amount of concurrent Incoming traffic.
Each customer account has its own set limit of concurrent channels. Each Channel is taken up for each active call. In the case of a Number Masking Call, two channels are used instead, one for the Incoming leg, and the other for the Outgoing leg. In general, to have more concurrent calls at a time, more channels will be required.
That said, it is important to understand that if the call CPS is 1, then having more channels does not necessarily translate to more concurrent calls. This is especially true if each call length/duration is not expected to be very long. For example, assuming a call takes up to 50 seconds duration. About 50 calls would have been placed at the 50th-second mark, at 1 Call per Second (CPS). As a result, 50 channels are in use. However, at the 51st second, the first call would have terminated, as a result, the first channel is now freed up. Thus, having more than 50 channels would begin to have diminishing marginal returns, as only the first 50 channels are ever really used for a conversation.
Updated 8 months ago