[Home]

Summary:ASTERISK-24409: AMI action Originate not working when in sync mode
Reporter:Dafi Ni (dafi)Labels:
Date Opened:2014-10-10 07:03:01Date Closed:2014-10-10 08:52:37
Priority:MajorRegression?
Status:Closed/CompleteComponents:Core/ManagerInterface
Versions:12.5.0 Frequency of
Occurrence		Constant
Related
Issues:
duplicatesASTERISK-15992 [patch] Originate Action output is inconsistent with other manager actions
Environment:Linux KRA-WS-DAFI 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/LinuxAttachments:
Description:when trying orginate to extension/context/priority with proper values,
ami respond "Originate with 'Exten' requires 'Context' and 'Priority'."

there arent any console or log related writes.

here is ngrep:

{quote}

T 127.0.0.1:60497 -> 127.0.0.1:5038
id: 9.
ActionID: 9.
Action: Originate.
Async: false.
Channel: Local/7777@dialer_caller/n.
Exten: inc.
Context: dialer.
Priority: 0.
Timeout: 30.
.

#
T 127.0.0.1:5038 -> 127.0.0.1:60497
Response: Error.

#
T 127.0.0.1:5038 -> 127.0.0.1:60497
ActionID: 9.

#
T 127.0.0.1:5038 -> 127.0.0.1:60497
Message: Originate with 'Exten' requires 'Context' and 'Priority'.
{quote}


same action with Async = true works.

maybe referenced to ASTERISK-15992
Comments:By: Matt Jordan (mjordan) 2014-10-10 08:52:32.314-0500

The error message returned from AMI could probably be better, but your Originate action is invalid. Priorities begin with {{1}}, not {{0}}.

However, you are correct that specifying a priority of 0 does work when run asynchronously... which is indeed odd.

As it is, this is a duplicate of ASTERISK-15992.