[asterisk-bugs] [JIRA] (ASTERISK-30019) AMI OriginateResponse's Reason is NOT correct

Asterisk Team (JIRA) noreply at issues.asterisk.org
Mon May 2 12:00:40 CDT 2022


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

Asterisk Team commented on ASTERISK-30019:
------------------------------------------

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

> AMI OriginateResponse's Reason is NOT correct
> ---------------------------------------------
>
>                 Key: ASTERISK-30019
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-30019
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: . I did not set the category correctly.
>    Affects Versions: 16.25.1
>         Environment: CentOS 7 + Asterisk 16
>            Reporter: Ryou, HyunSun
>            Assignee: Ryou, HyunSun
>
> when I make call using AMI Action(Originate), if action is not work, OriginateResponse's reason is always '0'
> when Phone is busy, I make a call with ami.
> but OriginateResponse's reason is always '0'
> - AMI Event
> 	Event: OriginateResponse
> 	Privilege: call,all
> 	ActionID: 1636182655_7#AP_agent2_5001_PD_c60f0ef
> 	Response: Failure
> 	Channel: PJSIP/5001 at IPPBX1
> 	Context: AgentLogin
> 	Exten: 5001
> 	Reason: 0
> 	Uniqueid: <unknown>
> 	CallerIDNum: 5001
> 	CallerIDName: <unknown>



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



More information about the asterisk-bugs mailing list