Bug 42591

Summary:	Call1: Call1.Content should explain in which case we can have multiple streams
Product:	Telepathy	Reporter:	Xavier Claessens <xclaesse>
Component:	tp-spec	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	CC:	olivier.crete
Version:	unspecified	Keywords:	patch
Hardware:	Other
OS:	All
URL:	http://cgit.collabora.com/git/user/xclaesse/telepathy-spec.git/log/?h=call1-streams
Whiteboard:
i915 platform:		i915 features:

Description Xavier Claessens 2011-11-04 06:27:42 UTC

Call1.Content iface does not explain at all in which cases we get more than one stream.

If I understood correctly the cases are (correct me if I'm wrong):

1) If there are multiple participants, then we COULD have one stream per remote participant. But depending on protocols, we could still have only one stream with many remote contacts in the case it does MultiCast.

2) With jingle when calling a contact connected from multiple resources, while ringing we'll have one stream per resource. When one resource accept all other streams get removed.

3) something else?

Comment 1 Olivier Crête 2011-11-04 06:46:36 UTC

1. There could be multiple contacts per stream in the case it does multicast or in the case there is a server or something that does mixing or multiplexing.

2. I think when you do jingle forking, you would have multiple Endpoints, but a single stream.

Comment 2 Xavier Claessens 2011-11-07 07:09:21 UTC

Made a patch to add a rational.

Comment 3 Olivier Crête 2011-11-07 07:23:25 UTC

Jingle style forking is just a name I made up as its different from "SIP forking" (in which the server sends the same Invite to all the remote endpoints).

Comment 4 Xavier Claessens 2011-11-07 07:38:47 UTC

ok, merged.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.