[asterisk-bugs] [JIRA] (ASTERISK-23804) Asterisk Manager API Action Originate / OriginateResponse

Richard Mudgett (JIRA) noreply at issues.asterisk.org
Thu May 29 11:22:45 CDT 2014


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

Richard Mudgett commented on ASTERISK-23804:
--------------------------------------------

The following commit corrected the regression that you are seeing:
{noformat}
r412581 | rmudgett | 2014-04-18 11:38:20 -0500 (Fri, 18 Apr 2014) | 25 lines

Originated calls: Fix several originate call problems.

* Restore the reason value set by pbx_outgoing_attempt() to use
AST_CONTROL_xxx values as all the consumers were expecting rather than
cause codes.

* Fixed the dial routines to set cause codes for more than just
ast_request() so pbx_outgoing_attempt() reason codes will function.

* Fix inconsistent locked_channel return status in pbx_outgoing_attempt().
The chanel may not have been locked or the channel may have been a stale
pointer.

* Fixed the OutgoingSpoolFailed channel to run dialplan whenever the
dialing fails for an originate exten and 1 < synchronous.

* Fix incorrect ast_cond_wait() usage in pbx_outgoing_attempt().
Indroduced by issue ASTERISK-22212 patch.

* Made struct pbx_outgoing use the ao2 lock instead of its own lock for
the cond wait mutex.  No sense in having two locks associated with the
same struct when only one is needed.

Review: https://reviewboard.asterisk.org/r/3421/
{noformat}


> Asterisk Manager API Action Originate / OriginateResponse
> ---------------------------------------------------------
>
>                 Key: ASTERISK-23804
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-23804
>             Project: Asterisk
>          Issue Type: Bug
>          Components: Core/ManagerInterface
>            Reporter: kondik
>            Assignee: kondik
>              Labels: Asterisk12
>
> I have the following issue.  
> When placing an outbound call with Asterisk Manager's Originate command, i.e:
> {code}
> Action: Originate
> Channel: Local/konrad at test
> Context: test
> Exten: 5000
> Priority: 1
> Callerid: 22222222
> Timeout: 10000
> Variable: VAR1=23,VAR2=24,VAR3=25
> ActionID: ABC45678901234567902
> Async: True
> {code}
> When the call to konrad at test is timeout or no_answered, I get an OriginateResponse reason of `0` and `Failure` as the response.  
> I should be getting a "No Answer" reason (should be "Reason: 1" ?? according to this: http://www.voip-info.org/wiki/view/Asterisk+Manager+API+Action+Originate)
> below my OriginateResponse event:
> {code}
> Event: OriginateResponse
> Privilege: call,all
> ActionID: ABC45678901234567902
> Response: Failure
> Channel: Local/konrad at test-00000078;1
> Context: test
> Exten: 5000
> Reason: 0
> Uniqueid: 1401368963.512
> CallerIDNum: 22222222
> CallerIDName: <unknown>
> {code}
> I've tested on the following platforms:
> Asterisk 12.1.1
> The same case is when the called number is BUSY then "Reason" is "0" also.
> Is any solution to fix this problem?
> Thanks in advance,
> Regards,
> Konrad



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



More information about the asterisk-bugs mailing list