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).
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)
Branch at: http://git.collabora.co.uk/?p=user/tester/telepathy-spec.git;a=shortlog;h=refs/heads/more-stream-errors
This is fixed in 0.7.27.
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.