| Summary: | ASTERISK-19273: Store Asterisk Manager HTTP Sessions in persistent storage. | ||
| Reporter: | Shane Spencer (whardier) | Labels: | |
| Date Opened: | 2012-01-30 15:44:40.000-0600 | Date Closed: | 2012-01-30 16:35:03.000-0600 |
| Priority: | Trivial | Regression? | |
| Status: | Closed/Complete | Components: | Core/ManagerInterface/NewFeature |
| Versions: | Feature Tracker | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | In order to queue up events before a manager has a chance to reconnect and obtain a new session, I would recommend that sessions are stored to persistent storage, loaded when manager is loaded, and the starttime or sequence number reset. This would be very useful in situations where Asterisk is not reachable during a reboot/restart and the state history of events, rather than just querying for specific states when reconnecting which has no history, is needed. | ||
| Comments: | By: Matt Jordan (mjordan) 2012-01-30 16:34:53.782-0600 Features requests are no longer submitted to or accepted through the issue tracker. Features requests are openly discussed on the mailing lists [1] and Asterisk IRC channels and made note of by Bug Marshals. [1] http://www.asterisk.org/support/mailing-lists By: Shane Spencer (whardier) 2012-01-30 16:39:19.897-0600 Please remove feature request feature from bug tracker..? | ||