[asterisk-bugs] [JIRA] (ASTERISK-22490) ARI: Origination provides insufficient feedback

Rusty Newton (JIRA) noreply at issues.asterisk.org
Mon Sep 9 19:31:03 CDT 2013


Rusty Newton created ASTERISK-22490:
---------------------------------------

             Summary: ARI: Origination provides insufficient feedback
                 Key: ASTERISK-22490
                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-22490
             Project: Asterisk
          Issue Type: Bug
      Security Level: None
          Components: Resources/res_ari
    Affects Versions: 12.0.0-alpha1
            Reporter: David M. Lee


When a call is originated via ARI (i.e. {{POST /ari/channels?endpoint=SIP%2F1000&context=internal&extension=6000&priority=1&app=test&appArgs=foobar&callerId=queuething&timeout=20}}), there is currently no feedback from ARI until the dialed party answers. If there's an error on the call (busy, timeout), there's no feedback at all.

Partially, this is due to my understanding that the channel was not created until the dialed party answers, so the ARI {{/channels/\[channelId\]}} cannot be created until then. Apparently, though, AMI issues events on some sort of channel during the origination process, so that's not entirely accurate.

* If a channel is actually created early in the origination process, the channel's URI should be returned in a 201 response to the POST.
* Origination errors (busy, timeout, etc.) should be sent over the ARI /events WebSocket to indicate the failure.
* If the recipient blind transfers the call to someone else, this should be indicated by a WebSocket event, and an OriginationFailed/StasisStart should be sent when the call fails/is answered.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.asterisk.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira



More information about the asterisk-bugs mailing list