[asterisk-bugs] [JIRA] (ASTERISK-30052) add configuration setting to enable RTCP PLI, FIR and NACK independently from "webrtc" setting

[Asterisk Team (JIRA)]

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

Asterisk Team commented on ASTERISK-30052:
------------------------------------------

Suspended due to lack of activity. This issue will be automatically re-opened if the reporter posts a comment. If you are not the reporter and would like this re-opened please create a new issue instead. If the new issue is related to this one a link will be created during the triage process. Further information on issue tracker usage can be found in the Asterisk Issue Guidlines [1].

[1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines

> add configuration setting to enable RTCP PLI, FIR and NACK independently from "webrtc" setting
> ----------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-30052
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30052
>             Project: Asterisk
>          Issue Type: Improvement
>      Security Level: None
>          Components: Resources/res_pjsip_sdp_rtp
>    Affects Versions: 18.11.1
>         Environment: Sangoma FreePBX 14 and higher on Sangoma OS7
>            Reporter: Università di Bologna - CESIA VoIP
>            Assignee: Università di Bologna - CESIA VoIP
>              Labels: webrtc
>
> Asterisk's "webrtc" configuration setting in pjsip.conf enables several features required to correctly interface webrtc clients like:
> + dtls media
> + RTP MEDIA BUNDLE (RFC8843)
> + rtcp mux
> + avpf
> + ice
> and particularly
> + RTP PLI, FIR, NACK, CCM (RFC5104 on AVPF)
> In our application, webrtc is not exposed directly by Asterisk: for security reasons, we are deploying an external dedicated high-end commercial webrtc proxy that will be exposed on the internet.
> To interoperate correctly on video streams our application needs RFC5104 enabled to support frame retransmission/resynchronization.
> However, if we enable "webrtc" settings also the RFC8843 is automatically enabled: unfortunately, the webrtc proxy we are deploying does not support RFC8843 and does not work correctly.
> We ask if you think would be possible to develop a little patch to read a new "use_rfc5104" setting which enables the required features (fir, nack, etc...) independently from the "webrtc" setting. In this way, we can enable FIR, NACK, etc... without the need to enable RTP MEDIA BUNDLE.
> We tested positively this feature on our test environment and fully fix the issues.
> What about if we make a merge request for this purpose?
> Thank you in advance,
> Camillo Toselli - Università di Bologna



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