Summary: | ASTERISK-25624: AMI Event OriginateResponse bug | ||
Reporter: | sungtae kim (pchero) | Labels: | |
Date Opened: | 2015-12-11 19:00:13.000-0600 | Date Closed: | 2015-12-20 17:09:09.000-0600 |
Priority: | Major | Regression? | No |
Status: | Closed/Complete | Components: | Core/ManagerInterface Core/ManagerInterface/NewFeature |
Versions: | 11.20.0 13.6.0 | Frequency of Occurrence | Constant |
Related Issues: | |||
Environment: | Debian 8 jessie on virtual box | Attachments: | |
Description: | 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) {noformat} Action: Originate Channel: SIP/111-111-0001@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@trunk_test_1 Context: res_outbound Exten: 5ad6c7d8-535c-4cd3-b3e5-83ab420dcb56 Reason: 0 Uniqueid: <null> CallerIDNum: <unknown> CallerIDName: <unknown> {noformat} {noformat} Action: Originate Channel: SIP/111-111-0001@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@trunk_test_1 Context: Exten: Reason: 0 Uniqueid: <null> CallerIDNum: <unknown> CallerIDName: <unknown> {noformat} | ||
Comments: | By: Asterisk Team (asteriskteam) 2015-12-11 19:00:14.420-0600 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]. By: sungtae kim (pchero) 2015-12-12 08:45:15.116-0600 I've got a +1 from zuul. Should I add someone else to review the code? :) https://gerrit.asterisk.org/#/c/1805/ |