| Summary: | ASTERISK-24802: stasis: set a channel variable on websocket disconnect error | ||
| Reporter: | Kevin Harwell (kharwell) | Labels: | ARI |
| Date Opened: | 2015-02-17 13:00:34.000-0600 | Date Closed: | 2015-04-09 14:00:09 |
| Priority: | Minor | Regression? | No |
| Status: | Closed/Complete | Components: | Applications/app_stasis Resources/res_ari |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | If there is an error on websocket write the websocket gets disconnected as it should, however it would be nice if a channel variable was set so the dialplan could be aware of the disconnect also. This could be especially useful when the error occurs on stasisstart. | ||
| Comments: | By: Ashley Sanders (asanders) 2015-04-09 14:00:09.283-0500 Added a new channel variable, STASISSTATUS, to advertise the status of Stasis such that any application on the other side is not left waiting indefinitely for Stasis to return in the event an error occurs that disrupts normal processing. The possible values for STASISSTATUS are: - 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 | ||