Feat/dial srtp encryption#13
Open
rhondahollis wants to merge 2 commits into
Open
Conversation
added 2 commits
May 22, 2026 16:12
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
1 participant
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.
Provide an SRTP encryption parameter on the dial verb.
This is part of a larger change that allows a user to select an SRTP encryption mode when making a call either via Create Call API or dial verb. It introduces an opt-in srtpEncryption property (sdes | dtls) that flows from REST createCall and the dial verb → X-Jambonz-SRTP header on the outbound INVITE → sbc-outbound, which selects an rtpengine profile accordingly.
This complete change came out of jambonz/jambonz-feature-server#1538