[asterisk-bugs] [JIRA] (ASTERISK-24449) Reinvite for T.38 UDPTL fails if SRTP is enabled

[Rusty Newton (JIRA)]

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

Rusty Newton commented on ASTERISK-24449:
-----------------------------------------

Thanks [~anstein] ! Please see the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process] to move forward with the patch. Once you get the patch on [Reviewboard|https://wiki.asterisk.org/wiki/display/AST/Review+Board+Usage] you can edit this issue and add the URL to the Reviewboard URL field for reference.

> Reinvite for T.38 UDPTL fails if SRTP is enabled
> ------------------------------------------------
>
>                 Key: ASTERISK-24449
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24449
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Channels/chan_sip/T.38
>    Affects Versions: 11.13.0
>            Reporter: Andreas Steinmetz
>            Severity: Minor
>         Attachments: srtp-udptl.patch, udptl-ignore-srtp-v2.patch
>
>
> Asterisk does erroneously respect the SRTP setting for the SIP account when handling a reinvite for T.38 UDPTL.
> Furthermore there are ATAs like the Cisco SPA112 that, in a T.38 UDPTL reinvite response, send "a=crypto" lines which seems to be plain wrong.
> Quote from RFC4612:
> "Further, there are no procedures in place for encrypting and protecting the integrity ofthe UDPTL stream."
> Thus Asterisk needs to ignore anything related to SRTP when handling any T.38 UDPTL reinvite.



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