Confirmed users
120
edits
Loop/Architecture/MVP: Difference between revisions
Jump to navigation
Jump to search
→WebSockets Connection for Call Progress
Ametaireau (talk | contribs) |
|||
| Line 152: | Line 152: | ||
== WebSockets Connection for Call Progress == | == WebSockets Connection for Call Progress == | ||
Several MVP use cases necessitate the ability to communicate information about the state of a call during its setup phase from the server to the clients, as well as a means to convey call setup control information from the clients to the server. These use cases include: | Several MVP use cases necessitate the ability to communicate information about the state of a call during its setup phase from the server to the clients, as well as a means to convey call setup control information from the clients to the server. These use cases include: | ||
* Caller informed when remote party is alerting ( | * Caller informed when remote party is alerting ({{bug|1015074}}, {{bug|1015087}}) | ||
* Caller informed when call setup fails ({{bug|1000240}}, {{bug|1000186}}) | * Caller informed when call setup fails ({{bug|1000240}}, {{bug|1000186}}) | ||
* Caller informed when remote party answers call (ahead of opentok signaling) | * Caller informed when remote party answers call (ahead of opentok signaling) | ||