[asterisk-bugs] [JIRA] (ASTERISK-25624) AMI Event OriginateResponse bug

Asterisk Team (JIRA) noreply at issues.asterisk.org
Fri Dec 11 19:00:33 CST 2015


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

Asterisk Team commented on ASTERISK-25624:
------------------------------------------

Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution.

A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report.

Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process].

> AMI Event OriginateResponse bug
> -------------------------------
>
>                 Key: ASTERISK-25624
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-25624
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/ManagerInterface, Core/ManagerInterface/NewFeature
>    Affects Versions: 13.6.0
>         Environment: Debian 8 jessie on virtual box
>            Reporter: sungtae kim
>
> When making call using AMI Originate, the OriginateResponse returns wrong message.(If the call failed)
> 2 things were wrong.
> - Uniqueid: <null>
> - Wrong parameters(Application, Data)
> {quote}Action: Originate
> Channel: SIP/111-111-0001 at trunk_test_1
> ChannelId: c92f5417-fb62-471e-bd39-fa789e8ab78c
> Async: true
> Timeout: 30000
> Exten: 5ad6c7d8-535c-4cd3-b3e5-83ab420dcb56
> OtherChannelId: 17111007-52a2-45ea-84ab-d1ee3ec396d5
> Context: res_outbound
> ActionId: a3ee82a3-49fa-48bc-bc37-a69c6c53a098
> Response: Success
> ActionID: a3ee82a3-49fa-48bc-bc37-a69c6c53a098
> Message: Originate successfully queued
> Event: OriginateResponse
> Privilege: call,all
> ActionID: a3ee82a3-49fa-48bc-bc37-a69c6c53a098
> Response: Failure
> Channel: SIP/111-111-0001 at trunk_test_1
> Context: res_outbound
> Exten: 5ad6c7d8-535c-4cd3-b3e5-83ab420dcb56
> Reason: 0
> Uniqueid: <null>
> CallerIDNum: <unknown>
> CallerIDName: <unknown>
> --------------------------------------
> Action: Originate
> Channel: SIP/111-111-0001 at trunk_test_1
> ChannelId: c92f5417-fb62-471e-bd39-fa789e8ab78c
> Async: true
> Timeout: 30000
> Application: Queue
> OtherChannelId: 17111007-52a2-45ea-84ab-d1ee3ec396d5
> Data: test 00
> ActionId: a3ee82a3-49fa-48bc-bc37-a69c6c53a098
> Response: Success
> ActionID: a3ee82a3-49fa-48bc-bc37-a69c6c53a098
> Message: Originate successfully queued
> Event: OriginateResponse
> Privilege: call,all
> ActionID: a3ee82a3-49fa-48bc-bc37-a69c6c53a098
> Response: Failure
> Channel: SIP/111-111-0001 at trunk_test_1
> Context: 
> Exten: 
> Reason: 0
> Uniqueid: <null>
> CallerIDNum: <unknown>
> CallerIDName: <unknown>
> {quote}



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



More information about the asterisk-bugs mailing list