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

[kondik (JIRA)]

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

kondik commented on ASTERISK-14125:
-----------------------------------

I use Asterisk in 12.1.1. version and I have similar issue.
When I use Originate Action with Async=True then I receive OriginateResponse Event, but when call is no_answered the Response is "Failure" and "Reason" is always "0" instead of any other value like 1 (no answer) etc.

Could anyone confirm that this issue was fixed at 12.1.1. version or is still broken?

Thanks in advance
Konrad

> [patch] Asterisk Manager API Action Originate / OriginateResponse
> -----------------------------------------------------------------
>
>                 Key: ASTERISK-14125
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-14125
>             Project: Asterisk
>          Issue Type: Bug
>          Components: General
>            Reporter: Nicholas Blasgen
>         Attachments: manager-timeout1.diff
>
>
> I have the following issue.  When placing an outbound call with Asterisk Manager's Originate command, if the call times out, I get an OriginateResponse reason of `0` and `Failure` as the response.  I should be getting a "No Answer" response instead (code `4`) (at least in my mind a timeout should not be a failure).
> I've tested on the following platforms:
> Asterusj 1.4.20
> Asterisk 1.4.23
> Asterisk 1.4.24.1
> Asterisk 1.4 r191778
> Asterisk 1.4 r193870
> My test method was to initiate a Originate call to myself (Asterisk -> SIP -> PSTN) with a short 4 second timeout and look at the OriginateResponse that came back 4 seconds after starting that call.  ASYNC is set to True.
> Can someone tell me if this is really the expected outcome of a timeout?  I expect a Failure to mean the call was rejected by the remote side.  And since someone will end up looking into this, can we maybe get an update to the different "reason" codes?



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