Add timeout configuration for call transfers and minimum message threshold for analysis #72
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.
This PR introduces two significant enhancements to call handling functionality. First, it adds configurable timeout settings for dynamic call transfers, allowing better control over transfer behavior when destinations are unavailable (1-300 seconds range, default 60s). Second, it implements a minimum messages threshold feature for call analysis, enabling filtering of short or incomplete calls.
The changes primarily affect two documentation files: call-dynamic-transfers.mdx and call-analysis.mdx. The updates include comprehensive configuration examples, best practices for timeout settings, and detailed behavior explanations for both features.