[asterisk-bugs] [JIRA] (ASTERISK-28855) PJSIP - Implement CHANNEL(secure_bridge_media)

[Asterisk Team (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-28855?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=250544#comment-250544 ] 

Asterisk Team commented on ASTERISK-28855:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur.

> PJSIP - Implement CHANNEL(secure_bridge_media)
> ----------------------------------------------
>
>                 Key: ASTERISK-28855
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-28855
>             Project: Asterisk
>          Issue Type: New Feature
>      Security Level: None
>          Components: Channels/chan_pjsip
>    Affects Versions: GIT
>            Reporter: Alexander Traud
>            Severity: Minor
>
> This is a follow-up from ASTERISK-26306 and ASTERISK-22920. Only the channel drivers ‘chan_iax2’ and ‘chan_sip’ support this right now.
> I need this, because first I call the remote party with RTP/SAVP. When that fails, I try again with RTP/AVP. I use this as a workaround because—although proposed for years and clarified in [RFC 8643|https://tools.ietf.org/html/rfc8643]—not every phone implementation or remote configuration allows RTP/AVP+crypto.
> There could be further use-cases. If you have one, comment, please.



--
This message was sent by Atlassian JIRA
(v6.2#6252)