Voximplant session execution lifetime is rather long compared to typical serverless functions, the session usually lasts longer than the calls the function controls. The session context is available throughout its lifetime.
We treat each call as a separate session and handle it separately from other calls.
VoxEngine session limits
An unanswered incoming call is disconnected in 60 seconds.
Session without calls and without ACD requests is terminated in 60 seconds.
Session without calls and with at least one ACD request is terminated in 120 minutes.
Callback execution time is limited to 1 second. This means that heavy computations should be moved to your own infrastructure and accessed via HTTP requests.
Max number of active timers is 100.
Timers and any other external resources are not available for the application after the 'Terminating' event has been triggered, but the application can make one more HTTP request to notify external system about the fact that the session is finished.
Max number of active HTTP requests is 3. Requests over the limit are queued, up to the total HTTP requests limit. Before 'Terminating' event is triggered, VoxEngine will wait up to 90 seconds for pending requests to complete and will execute corresponding callback functions. The rest queued requests are silently dropped without any callback functions execution.
Max number of simultaneous HTTP requests is 35. The limit includes both pending and queued requests. Initiating more requests will result in “Exceeded the HTTP connection count limit!” exception.
Max number of active SMTP requests is 2. Requests over the limit are queued, up to the total SMTP requests limit. Before 'Terminating' event is triggered, VoxEngine will wait up to 90 seconds for pending requests to complete and will execute corresponding callback functions. The rest queued requests are silently dropped without any callback functions execution.
Max number of simultaneous SMTP requests is 10. This limit counts both pending and queued requests. Initiating more requests will result in “Exceeded the SMTP connection count limit!” exception.
The size of HTTP response handled by VoxEngine is limited to 2 megabytes.
Session is limited to a total of 50 inbound and outbound call attempts. Both successful and failed calls are counted. New calls over the limit will fail with 'CallEvents.Failed' event where 'code' is 403 and 'reason' is a description string like "Call limit reached". Use the Call list module for a big number of outbound calls and the Conference module for a big number of participants in a single VoxEngine session.
Max number of “progressing” calls that are not answered yet at any given moment is limited to 10. Calls over the limit will fail with 'CallEvents.Failed' event where 'code' is 403 and 'reason' is a description string like "Call limit reached".
Single SIP header field is limited to 200 bytes.
Destinations that are more expensive than 20 cents per minute and calls to countries in Africa are blocked by default for security reasons. Please contact us at email@example.com to enable them. IMPORTANT: if these settings has been applied to your account, then all child accounts created afterwards will have these settings too.