diff options
| author | Alexander Traud <pabstraud@compuserve.com> | 2016-08-26 15:41:16 +0200 |
|---|---|---|
| committer | Alexander Traud <pabstraud@compuserve.com> | 2016-08-26 16:37:46 +0200 |
| commit | 858fa5eb2c96149fffda629b727f8009e3b367fc (patch) | |
| tree | 90d80328acce34c69af38269b67d20712c364186 | |
| parent | c6ed91a9c89de71b44045a53cfc73e1b12744cf8 (diff) | |
channel: No hung-up on failing security requirements.
In your Diaplan, if you specify
same => n,Set(CHANNEL(secure_bridge_media)=1)
same => n,Set(CHANNEL(secure_bridge_signaling)=1)
only the SIP channel driver chan_sip supports this. All other channels drivers
like res_pjsip fail. In case of failure, the original sRTP source code released
the whole channel, even if not hung-up, yet. This change does not release the
channel but instead hangs-up the channel.
ASTERISK-26306
Change-Id: I0489f0cb660fab6673b0db8af027d116e70a66db
| -rw-r--r-- | main/channel.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/main/channel.c b/main/channel.c index 1f18d53b1..94505ad0e 100644 --- a/main/channel.c +++ b/main/channel.c @@ -6093,7 +6093,7 @@ struct ast_channel *ast_request(const char *type, struct ast_format_cap *request if (set_security_requirements(requestor, c)) { ast_log(LOG_WARNING, "Setting security requirements failed\n"); - c = ast_channel_release(c); + ast_hangup(c); *cause = AST_CAUSE_BEARERCAPABILITY_NOTAVAIL; return NULL; } |