Question on upcoming changes for: "Queued call processing"
We just received a notice that Queued call processing is changing - i.e. "POST /call will enqueue the call for creation; the underlying transport (Twilio, Telnyx, etc.) is provisioned asynchronously i.e. not created immediately."
My question is that we utilize the Call api w/ the 'phoneCallProviderBypassEnabled' parameter as recommended in this document: https://docs.vapi.ai/calls/call-handling-with-vapi-and-twilio
With the upcoming changes for this Call API for outbound calls, with this have any noticeable impact on those of us using the call API with the phoneCallProviderBypassEnabled parameter to connect inbound calls?
My question is that we utilize the Call api w/ the 'phoneCallProviderBypassEnabled' parameter as recommended in this document: https://docs.vapi.ai/calls/call-handling-with-vapi-and-twilio
With the upcoming changes for this Call API for outbound calls, with this have any noticeable impact on those of us using the call API with the phoneCallProviderBypassEnabled parameter to connect inbound calls?
