| Summary: | ASTERISK-21182: Create documentation/specification for expected Stasis HTTP events | ||
| Reporter: | Matt Jordan (mjordan) | Labels: | Asterisk12 |
| Date Opened: | 2013-02-27 15:38:41.000-0600 | Date Closed: | 2013-07-17 08:21:36 |
| Priority: | Major | Regression? | No |
| Status: | Closed/Complete | Components: | Core/Stasis Resources/res_ari |
| Versions: | 12 | Frequency of Occurrence | |
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Create documentation in source for the expected events that Stasis HTTP will expose. This includes events for:
* Channels ** Lifetime (creation, hangup) ** State changes ** Dialing ** DTMF * Bridges ** Creation/destruction ** Channel entering/leaving ** Type changes? (not sure how much Stasis-HTTP will actually care about this) ** How do we want to expose two-party to multi-party transitions? * Media ** Start/stop/restart Define how we will handle: * Endpoint updates (if needed at all) * Local channel optimization * Local channels in general * Switching between bridges during transfers * Switching between bridges in two-party to multi-party transitions | ||
| Comments: | |||