| Summary: | ASTERISK-23214: chan_sip WARNING message 'We are requesting SRTP for audio, but they responded without it' is ambiguous and wrong in some cases | ||
| Reporter: | Rusty Newton (rnewton) | Labels: | |
| Date Opened: | 2014-01-29 15:00:21.000-0600 | Date Closed: | 2015-02-25 17:04:39.000-0600 |
| Priority: | Minor | Regression? | |
| Status: | Closed/Complete | Components: | Channels/chan_sip/General |
| Versions: | SVN 1.8.25.0 11.7.0 12.0.0 | Frequency of Occurrence | Constant |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Following the tutorial here: https://wiki.asterisk.org/wiki/display/AST/Secure+Calling+Tutorial
At the point where you have Blink call Asterisk, but have not yet enabled "encryption=yes" for the peer, the call will fail and you'll see this message on the Asterisk CLI: {noformat} [Jan 29 14:33:23] WARNING[10930][C-00000003]: chan_sip.c:10538 process_sdp: We are requesting SRTP for audio, but they responded without it! {noformat} This happens when the remote client, Blink, sends SDP to Asterisk including SRTP offers, but Asterisk has encryption=no. Therefore the message makes no sense as "We" will likely be interpreted by the user as Asterisk itself. The message should be more explicit. Mark Michelson mentioned this message probably exists in code used commonly to various scenarios, so maybe something like "One party in the call has requested SRTP, but the other party is not capable." | ||
| Comments: | |||