Summary: | ASTERISK-20959: Create Stasis Core Module | ||||||||||
Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 | ||||||||
Date Opened: | 2013-01-18 11:28:36.000-0600 | Date Closed: | 2013-03-14 22:57:58 | ||||||||
Priority: | Major | Regression? | No | ||||||||
Status: | Closed/Complete | Components: | Core/Stasis | ||||||||
Versions: | Frequency of Occurrence | ||||||||||
Related Issues: |
| ||||||||||
Environment: | Attachments: | ||||||||||
Description: | Create the Stasis core module. This is partially already represented by the existing event subsystem, and will most likely entail modifications to the event subsystem to be able to:
* Pass channel state as pub/sub events * Pass bridge state as pub/sub events * Pass generic messages with a generic payload (JSON?), supporting message identification as well as responses to messages The API for this should be documented on the wiki. How objects are passed on the message bus should be specified, keeping in mind the trade offs between speed and flexibility. Note that stasis core may just be enhancements to event.h - or it may be better served as a separate/complementary set of APIs. | ||||||||||
Comments: | By: David M. Lee (dlee) 2013-03-14 22:57:58.318-0500 Fixed in r382685 |