| Summary: | ASTERISK-24701: Stasis: Write timeout on WebSocket fails to fully disconnect underlying socket, leading to events being dropped with no additional information | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | |
| Date Opened: | 2015-01-16 10:35:06.000-0600 | Date Closed: | 2015-02-11 10:47:39.000-0600 |
| Priority: | Major | Regression? | |
| Status: | Closed/Complete | Components: | Resources/res_stasis |
| Versions: | 13.1.0 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | By default, the Websocket connection to an ARI application has a write timeout of 100ms. That's kind of short, and in an especially busy system, you'll get a disconnect if the client fails to keep up with a burst of messages.
The write timeout is configurable in {{ari.conf}}, so it can be bumped up. However, if a write timeout does occur, the following should happen: # The Websocket should be disconnected # {{res_stasis}} should be notified. A NOTICE should be displayed that a disconnect occurred. # When a Websocket reconnects for the application, at a minimum, it should receive the count of messages dropped since the last connection. | ||
| Comments: | |||