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

(Updated March 31, 2015, 10:58 a.m.)


Status
------

This change has been discarded.


Review request for Asterisk Developers.


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


Repository: testsuite


Description
-------

This review has been moved to gerrit: https://gerrit.asterisk.org/#/c/18/

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

This patch introduces a new channel variable: STASISSTATUS to give outside 
applications context when errors occur in Stasis that interrupt normal 
processing.

This test exercises three scenarios to elicit updates to the STASISSTATUS 
channel variable:
1) The 'Babs' scenario: tests the situation where a channel is originated under 
normal conditions and then the channel is hungup. For this case, the test 
verifies that Stasis 
   correctly assigns SUCCESS to STASISSTATUS.
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.


 ***Note*** This is a test. It is only a test. The review for the Asterisk 
source can be found at: https://reviewboard.asterisk.org/r/4519/


Diffs
-----

  ./asterisk/trunk/tests/rest_api/applications/tests.yaml 6547 
  
./asterisk/trunk/tests/rest_api/applications/stasisstatus/test_scenario_factory.py
 PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasisstatus/test_scenario.py 
PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasisstatus/test_case.py 
PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasisstatus/test-config.yaml 
PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasisstatus/run-test 
PRE-CREATION 
  
./asterisk/trunk/tests/rest_api/applications/stasisstatus/observable_object.py 
PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasisstatus/monitor.py 
PRE-CREATION 
  
./asterisk/trunk/tests/rest_api/applications/stasisstatus/configs/ast1/sip.conf 
PRE-CREATION 
  
./asterisk/trunk/tests/rest_api/applications/stasisstatus/configs/ast1/extensions.conf
 PRE-CREATION 
  ./asterisk/trunk/tests/rest_api/applications/stasisstatus/ari_client.py 
PRE-CREATION 

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


Testing
-------


Thanks,

Ashley Sanders

-- 
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev

Reply via email to