[asterisk-dev] [Code Review] 4519: Asterisk: stasis: set a channel variable on websocket disconnect error

[Ashley Sanders]

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviewboard.asterisk.org/r/4519/
-----------------------------------------------------------

(Updated March 25, 2015, 3:59 p.m.)


Review request for Asterisk Developers.


Changes
-------

Updated the description and testing done fields to depict:
A) The name of the channel variable is: STASISSTATUS, not STASIS_STATUS
B) The testing done field now contains a link and the blurb from the Testsuite test, for clarity.


Bugs: ASTERISK-24802
    https://issues.asterisk.org/jira/browse/ASTERISK-24802


Repository: Asterisk


Description (updated)
-------

When an error occurs while writing to a web socket, the web socket is disconnected and the event is logged. A side-effect of this, however, is that any application on the other side waiting for a response from Stasis is left hanging indefinitely (as there is no mechanism presently available for notifying interested parties about web socket error states in Stasis).

To remedy this scenario, this patch introduces a new channel variable: STASISSTATUS.

The possible values for STASIS_STATUS are:
INITIALIZING    - Indicates Stasis is starting
ACTIVE          - The channel is active in Stasis
SUCCESS         - The channel has exited Stasis without any failures
FAILED          - Something caused Stasis to croak. Some (not all) possible reasons for this: 
                    - The app registry is not instantiated; 
                    - The app requested is not registered; 
                    - The app requested is not active; 
                    - Stasis couldn't send a start message

 ***Note*** This is just the patch to the Asterisk source. The testsuite review is coming soon to a reviewboard near you (well, this reviewboard.)
https://reviewboard.asterisk.org/r/4520


Diffs
-----

  ./branches/13/res/res_stasis.c 433290 
  ./branches/13/apps/app_stasis.c 433290 

Diff: https://reviewboard.asterisk.org/r/4519/diff/


Testing (updated)
-------

The testing done for this issue can be found at: https://reviewboard.asterisk.org/r/4520/

The test in Testsuite exercises three scenarios to elicit updates to the STASISSTATUS channel variable:
1) The 'Babs' scenario: tests a nominal path of Stasis to verify the 'ACTIVE' state is correctly applied. For this test, a call is originated under normal conditions and then the system is polled for the value of STASIS_STATUS before the channel is hung up.
2) The 'Bugs' scenario: tests the situation where a call is originated requesting an app that was never registered in Stasis to verify the 'FAILED' state is correctly applied.
3) The 'Buster' scenario: tests the situation where an app that was registered in Stasis when call A was originated (and while call A is still active) but is no longer registered when call B is originated. Determines if the 'FAILED' state is correctly applied.


Thanks,

Ashley Sanders

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20150325/d6e65d78/attachment.html>