[asterisk-bugs] [JIRA] (ASTERISK-25819) AMI Hangup ignores hangup cause when channel is in process of origination
Rusty Newton (JIRA)
noreply at issues.asterisk.org
Mon Feb 29 13:31:57 CST 2016
[ https://issues.asterisk.org/jira/browse/ASTERISK-25819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rusty Newton updated ASTERISK-25819:
------------------------------------
Summary: AMI Hangup ignores hangup cause when channel is in process of origination (was: AMI Hangup ignores hangup cause)
> AMI Hangup ignores hangup cause when channel is in process of origination
> -------------------------------------------------------------------------
>
> Key: ASTERISK-25819
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-25819
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/General
> Affects Versions: 11.21.2
> Reporter: Dialapplet
> Severity: Minor
>
> When a channel is hung up from asterisk manager during a call and a cause code is specified all works fine. But, when I try to hung up a channel that is in process of origination, it is hung up with cause 19, ignoring the cause I put on the action.
> For example:
> I do this orginate:
> {quote}
> Action: Originate
> Async: true
> Channel: SIP/100
> ...
> {quote}
> The channel is created:
> {quote}
> Event: Newchannel
> Channel: SIP/100-00000005
> Uniqueid: 1456738121.6
> ...
> {quote}
> I do the hang up action with cause code 17 (When the phone is still ringing, just to reject the call):
> {quote}
> Action: Hangup
> Cause: 17
> Channel: SIP/100-00000005
> ActionID: Hangup-100
> {quote}
> I receive the response:
> {quote}
> ActionID: Hangup-100
> Response: Success
> Message: Channel Hungup
> {quote}
> But the hangup event doesn't contain cause code 17:
> {quote}
> Event: Hangup
> Cause: 19
> Channel: SIP/100-00000005
> Uniqueid: 1456738121.6
> ...
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list