Bug 22926

Summary:	StreamedMedia: more error codes
Product:	Telepathy	Reporter:	Simon McVittie <smcv>
Component:	tp-spec	Assignee:	Olivier Crête <olivier.crete>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	All
Whiteboard:
i915 platform:		i915 features:

Description Simon McVittie 2009-07-24 03:10:42 UTC

If negotiating a common codec fails, UIs cannot know and display why the call failed, because the spec currently only lists Unknown and EOS error codes for the StreamError signal.

Olivier, you also asked for "a bunch of other error codes": please draft a spec branch with the set of error codes you consider to be useful, including No_Suitable_Codec or something (the contents of whatever error enum you're translating from in Farsight2 would probably be a good start).

Comment 1 Olivier Crête 2009-07-24 07:46:00 UTC

From a quick look at the Fs2 list of possible errors we need:

Expected runtime errors:

CodecNegotiationFailed: Codec intersection is empty
ConnectionFailed: can't connect (or disconnected)

Installation problems:
NoCodecs: There are no codecs for this media type installed
NoCodecsLeft: All the codecs were disabled by the codec preferences (maybe this should be merged with the previous one)

Comment 2 Olivier Crête 2009-07-29 09:45:38 UTC

Branch at:
http://git.collabora.co.uk/?p=user/tester/telepathy-spec.git;a=shortlog;h=refs/heads/more-stream-errors

Comment 3 Olivier Crête 2009-08-17 10:03:43 UTC

This is fixed in 0.7.27.

Comment 4 Olivier Crête 2009-09-08 18:19:08 UTC

the telepathy-farsight implementation of the client-side part is in 0.0.10

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.