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

[kondik (JIRA)]

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

kondik commented on ASTERISK-23804:
-----------------------------------

Many thanks for your help.

I have installed Asterisk 12.3.0 and now it works!!!
So 12.1 version of Asterisk has a bug.

Regards,
Konrad

> 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)