Talkilla/SPA API: Difference between revisions

Jump to navigation Jump to search
→‎Call Flows: Draft of call flows docs
m (Standard8 moved page Talkilla/SPA-documentation to Talkilla/SPA API: Better naming to go alongside the overview document)
(→‎Call Flows: Draft of call flows docs)
Line 123: Line 123:


  {topic: "hangup", data: {peer: <peer>, callid: <call id>}}
  {topic: "hangup", data: {peer: <peer>, callid: <call id>}}
==== User Initiates a Call Move ====
''This API only applies when the SPA advertises "move" in its capabilities''
Talkilla send the message:
{topic: "move", data: {peer: <peer>, callid: <call id>}}
When the SPA has accepted the move request:
{topic: "move-accept", data: {peer: <peer>, callid: <call id>}}
==== Call Hold ====
''This API only applies when the SPA advertises "hold" in its capabilities''
Either Talkilla or SPA can send a message:
{topic: "hold", data: {peer: <peer>, callid: <call id>}}
==== Receiving Call Resume from a Peer ====
''This API only applies when the SPA advertises "hold" in its capabilities''
The SPA can send a message:
{topic: "resume", data: {peer: <peer>, callid: <call id>, media: {
  audio: <boolean>, video: <boolean>}
}}
Note: The media parameter is a temporary option until Firefox supports session re-negotiation. On receiving a resume message, Talkilla will only enable the audio/video tracks according to the specified parameters.
==== Sending a Text Message ====
''This API only applies when the SPA advertises "nodatachannel" in its capabilities''
{topic: "chat:message", data: {nick:"webrtc@mailinator.com", message: <string>, date: <date>}}


=== Handling ICE Candidates ===
=== Handling ICE Candidates ===
canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628

edits

Navigation menu