canmove, Confirmed users, Bureaucrats and Sysops emeriti
3,628
edits
Talkilla/SPA API: Difference between revisions
Jump to navigation
Jump to search
Add ICE capability information
(Add ICE capability information) |
|||
| Line 89: | Line 89: | ||
From Talkilla: event.data contains | From Talkilla: event.data contains | ||
{topic: "hangup", data: {peer: "+16501231234"}} | {topic: "hangup", data: {peer: "+16501231234"}} | ||
== Handling ICE Candidates == | |||
Firefox is capable of [http://tools.ietf.org/html/draft-rescorla-mmusic-ice-trickle-00 Trickle ICE]. After an initial call offer or answer, there may be additional ICE candidates. Hence these may be sent from either side. | |||
From the SPA: | |||
postMessage({topic: "ice:candidate", data: {peer: "+16501231234", candidate: <candidate>}}); | |||
From Talkilla: event.data contains: | |||
{topic: "ice:candidate", data: {peer: "+16501231234", candidate: <candidate>}}); | |||
<code><candidate></code> is an object containing parameters with values matching the [http://dev.w3.org/2011/webrtc/editor/webrtc.html#rtcicecandidate-type RTCIceCandidate] e.g. | |||
{candidate: "candidate string", sdpMid: "media stream id", sdpMLineIndex: 2} | |||
=Data Channel API Documentation= | =Data Channel API Documentation= | ||
This is still being defined | This is still being defined | ||