feat: add async INVITE API#84
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In a telephony system, outgoing INVITE requests may take a long time to complete
(ringing, call forwarding, parallel forking, or no answer).
do_invite_async() allows starting an outgoing call without blocking the calling task.
This makes it possible to:
initiate multiple calls in parallel,
keep the control plane responsive while calls are ringing,
manage call state, timeouts, and cancellation externally.
The dialog is registered under an early dialog ID while the INVITE is in progress
and re-registered under the confirmed dialog ID on a successful (2xx) response,
preserving correct in-dialog request routing.