Feature:Audio/video communication - Revision history

Raucao at 09:50, 5 May 2017

2017-05-05T09:50:44Z

Administrator: Fix typos

2016-04-22T12:23:14Z

Fix typos

Raucao at 13:31, 16 July 2015

2015-07-16T13:31:25Z

Raucao: /* Feature Ideas for Later™ */

2015-06-26T15:10:32Z

Feature Ideas for Later™

Raucao at 17:15, 25 June 2015

2015-06-25T17:15:16Z

Raucao: /* Features */

2015-06-06T15:34:31Z

Features

Raucao: /* Summary */

2015-06-06T15:32:30Z

Summary

Administrator: Administrator moved page Feature2:Audio/video communication to Feature:Audio/video communication without leaving a redirect

2015-03-23T18:10:29Z

Administrator moved page Feature2:Audio/video communication to Feature:Audio/video communication without leaving a redirect

imported>Administrator: Administrator moved page Feature: Audio/video communication to Feature2:Audio/video communication

2015-03-23T18:04:33Z

Administrator moved page Feature: Audio/video communication to Feature2:Audio/video communication

Administrator: Administrator moved page Feature: Audio/video communication to Feature2:Audio/video communication

2015-03-23T18:04:32Z

Administrator moved page Feature: Audio/video communication to Feature2:Audio/video communication

← Older revision		Revision as of 09:50, 5 May 2017
Line 1:		Line 1:
		+	== Please note ==
		+
		+	This feature is not on the immediate roadmap anymore. If you want to contribute (and you're prepared to lead the development of the entire feature), please contact the core team. Thanks.
		+
	== Summary ==		== Summary ==

@@ Line 36: / Line 36: @@
 * Peers can exchange some messages w/ each other (like "offer: i can do this codec" or "ice: i have this kind of nat")
-It is implemented on top of the existing IRC channels (via SockerHub) using special message formats, which will get parsed by the HC Client. For backwards compat (later), it could include a link to the SA app:
+It is implemented on top of the existing IRC channels (via SocketHub) using special message formats, which will get parsed by the HC Client. For backwards compatibility (later), it could include a link to the SA app:
      A → B [67p-rtc-invite] Here is your video call: https://playground.p67.io/rtc/bilfgneehlrieli

← Older revision		Revision as of 13:31, 16 July 2015
Line 46:		Line 46:

	* In order to be able to quickly launch meetings before having our own integration, we could create scripts for hal8000 to start new meetings at e.g. g2m, meet.jit.si, talky, palava.tv.		* In order to be able to quickly launch meetings before having our own integration, we could create scripts for hal8000 to start new meetings at e.g. g2m, meet.jit.si, talky, palava.tv.
		+
		+	== Notes ==
		+
		+	* http://socket.io/blog/socket.io-p2p

@@ Line 14: / Line 14: @@
 * Conferencing
 * Broadcasting
-* Call in to a WebRTC call via plain old phone system
+* Call in to a WebRTC call via plain old phone system (e.g. via [https://www.sipgate.io sipgate] or similar)
 ==== Stand Alone Application ====

← Older revision		Revision as of 17:15, 25 June 2015
Line 42:		Line 42:
	A → B [67p-rtc-params] (Signaling messages)		A → B [67p-rtc-params] (Signaling messages)
	...		...
		+
		+	== Before feature launch ==
		+
		+	* In order to be able to quickly launch meetings before having our own integration, we could create scripts for hal8000 to start new meetings at e.g. g2m, meet.jit.si, talky, palava.tv.

@@ Line 4: / Line 4: @@
 == Features ==
 === HyperChannel Integration ===
-A video stream (or audio symbol for non-video) will be integrated into the 67P UI (maybe in an extra tab?) You can also "pop-out" this UI component, which makes working on multiple screens easier (and requesting full screen simpler).
+A video stream (or audio symbol for non-video) will be integrated into the Hyperchannel UI (maybe in an extra tab?) You can also "pop-out" this UI component, which makes working on multiple screens easier (and requesting full screen simpler).
 === Feature Ideas for Later™ ===
@@ Line 20: / Line 18: @@
 ==== Stand Alone Application ====
-The WebRTC Stand Alone Application will be needed in the following cases:
+The WebRTC stand-alone application will be needed in the following cases:
 * One of the participants is not on HC, but using an IRC Client
 * Both parties are using IRC. The Server/Mod generates a room link on the SA app for them. Or maybe: Don't support this scenario?
-* Inviting people to an 1on1 chat that are not part of the current 67P organisation (maybe via email)
+* Inviting people to an 1on1 chat that are not part of the current Kosmos organisation (maybe via email)
 The SA application displays the video stream of the other party, however, some kind of text communication channel is still needed (people want to exchange links etc) - This will be done via IRC or WebRTC's DataChannels.

@@ Line 1: / Line 1: @@
 == Summary ==
-P comes with integrated video- and audio chat capabilities. In the beginning, this is limited to 1on1 calls, but we will support conferencing and/or broadcasting at a later point. WebRTC ([http://webrtc.org "Web Real-time Communication"]) is used to enable this. WebRTC currently works in Firefox, Chrome, FF and Chrome on Android, Opera and some lesser known browsers (e.g. Bowser on iOS). We might switch to ORTC ([http://ortc.org "Object RTC"]) at some point, which is a lower-level standard that will be supported in Internet Explorer also.
+Kosmos comes with integrated video- and audio chat capabilities. In the beginning, this is limited to 1on1 calls, but we will support conferencing and/or broadcasting at a later point. WebRTC ([http://webrtc.org "Web Real-time Communication"]) is used to enable this. WebRTC currently works in Firefox, Chrome, FF and Chrome on Android, Opera and some lesser known browsers (e.g. Bowser on iOS). We might switch to ORTC ([http://ortc.org "Object RTC"]) at some point, which is a lower-level standard that will be supported in Internet Explorer also.
 == Features ==

← Older revision		Revision as of 18:10, 23 March 2015
Line 1:		Line 1:
−	~~#REDIRECT~~ [[~~Feature2~~:~~Audio~~/video communication]]	+	== Summary ==
		+
		+	67P comes with integrated video- and audio chat capabilities. In the beginning, this is limited to 1on1 calls, but we will support conferencing and/or broadcasting at a later point. WebRTC ([http://webrtc.org "Web Real-time Communication"]) is used to enable this. WebRTC currently works in Firefox, Chrome, FF and Chrome on Android, Opera and some lesser known browsers (e.g. Bowser on iOS). We might switch to ORTC ([http://ortc.org "Object RTC"]) at some point, which is a lower-level standard that will be supported in Internet Explorer also.
		+
		+	== Features ==
		+
		+	67P RTC is an integrated featuren in HyperChannel. Only direct 1on1 calls will be implemented for now.
		+
		+	=== HyperChannel Integration ===
		+
		+	A video stream (or audio symbol for non-video) will be integrated into the 67P UI (maybe in an extra tab?) You can also "pop-out" this UI component, which makes working on multiple screens easier (and requesting full screen simpler).
		+
		+	=== Feature Ideas for Later™ ===
		+
		+	* Screensharing
		+	* Conferencing
		+	* Broadcasting
		+	* Call in to a WebRTC call via plain old phone system
		+
		+	==== Stand Alone Application ====
		+
		+	The WebRTC Stand Alone Application will be needed in the following cases:
		+
		+	* One of the participants is not on HC, but using an IRC Client
		+	* Both parties are using IRC. The Server/Mod generates a room link on the SA app for them. Or maybe: Don't support this scenario?
		+	* Inviting people to an 1on1 chat that are not part of the current 67P organisation (maybe via email)
		+
		+	The SA application displays the video stream of the other party, however, some kind of text communication channel is still needed (people want to exchange links etc) - This will be done via IRC or WebRTC's DataChannels.
		+
		+	== Technical Implementation ==
		+
		+	'''Components:''' Client/UI Integration, Signaling Backend (might be IRC/SH), TURN Relay, SFU/MCU for Conferencing > 4
		+
		+	=== Signaling ===
		+
		+	WebRTC requires "signaling" which serves two purposes:
		+	* Peers meet each other
		+	* Peers can exchange some messages w/ each other (like "offer: i can do this codec" or "ice: i have this kind of nat")
		+
		+	It is implemented on top of the existing IRC channels (via SockerHub) using special message formats, which will get parsed by the HC Client. For backwards compat (later), it could include a link to the SA app:
		+
		+	A → B [67p-rtc-invite] Here is your video call: https://playground.p67.io/rtc/bilfgneehlrieli
		+	B → A [67p-rtc-accept] Accepted
		+	A → B [67p-rtc-params] (Signaling messages)
		+	...

← Older revision		Revision as of 18:04, 23 March 2015
Line 1:		Line 1:
−	~~== Summary ==~~	+	#REDIRECT [[Feature2:Audio/video communication]]
−
−	~~67P comes with integrated video- and audio chat capabilities. In the beginning, this is limited to 1on1 calls, but we will support conferencing and/or broadcasting at a later point. WebRTC (~~[http://webrtc.org "Web Real-time Communication"]) is used to enable this. WebRTC currently works in Firefox, Chrome, FF and Chrome on Android, Opera and some lesser known browsers (e.g. Bowser on iOS). We might switch to ORTC ([~~http~~:/~~/ortc.org "Object RTC"]) at some point, which is a lower-level standard that will be supported in Internet Explorer also.~~
−
−	~~== Features ==~~
−
−	~~67P RTC is an integrated featuren in HyperChannel. Only direct 1on1 calls will be implemented for now.~~
−
−	~~=== HyperChannel Integration ===~~
−
−	A video stream (or audio symbol for non-video) will be integrated into the 67P UI (maybe in an extra tab?) You can also "pop-out" this UI component, which makes working on multiple screens easier (and requesting full screen simpler).
−
−	~~=== Feature Ideas for Later™ ===~~
−
−	* Screensharing
−	* Conferencing
−	* Broadcasting
−	* Call in to a WebRTC call via plain old phone system
−
−	~~==== Stand Alone Application ====~~
−
−	~~The WebRTC Stand Alone Application will be needed in the following cases:~~
−
−	* One of the participants is not on HC, but using an IRC Client
−	* Both parties are using IRC. The Server/Mod generates a room link on the SA app for them. Or maybe: Don't support this scenario?
−	* Inviting people to an 1on1 chat that are not part of the current 67P organisation (maybe via email)
−
−	~~The SA application displays the video stream of the other party, however, some kind of text~~ communication ~~channel is still needed (people want to exchange links etc) - This will be done via IRC or WebRTC's DataChannels.~~
−
−	~~== Technical Implementation ==~~
−
−	~~'''Components:''' Client/UI Integration, Signaling Backend (might be IRC/SH), TURN Relay, SFU/MCU for Conferencing > 4~~
−
−	~~=== Signaling ===~~
−
−	~~WebRTC requires "signaling" which serves two purposes:~~
−	* Peers meet each other
−	* Peers can exchange some messages w/ each other (like "offer: i can do this codec" or "ice: i have this kind of nat")
−
−	It is implemented on top of the existing IRC channels (via SockerHub) using special message formats, which will get parsed by the HC Client. For backwards compat (later), it could include a link to the SA app:
−
−	~~A → B [67p-rtc-invite] Here is your video call: https://playground.p67.io/rtc/bilfgneehlrieli~~
−	~~B → A [67p-rtc-accept~~] ~~Accepted~~
−	~~A → B [67p-rtc-params~~] ~~(Signaling messages)~~
−	~~...~~

← Older revision	Revision as of 18:04, 23 March 2015
(No difference)