audio-knife: request deferred parameters - #98
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
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.
Why
AudioFork ignores subsequent client text messages, including deferred parameters, until its socket is connected. Its
mod_audio_fork::connectFreeSWITCH client notification also omits the conversation ID, so clients need an explicit AudioKnife signal that identifies when to send deferred parameters for a conversation.Summary
sendParamstransport message after accepting a deferred start.3.7.1.Validation
cargo fmt -- --checkcargo testNote
This pull request was developed with assistance from an AI coding agent alongside the author.