[Bug 24935] New: Emit StreamError(..., Codec_Negotiation_Failed, ..) in more cases
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Nov 5 11:16:26 CET 2009
http://bugs.freedesktop.org/show_bug.cgi?id=24935
Summary: Emit StreamError(..., Codec_Negotiation_Failed, ..) in
more cases
Product: Telepathy
Version: unspecified
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: gabble
AssignedTo: telepathy-bugs at lists.freedesktop.org
ReportedBy: will.thompson at collabora.co.uk
If you try to add video to an existing audio call, but I don't support any of
the codecs you propose, TpFs calls Error(Codec_Negotiation_Failed, ...) on the
stream, and my Gabble correctly emits StreamError(...,
Codec_Negotiation_Failed, ...) for that stream. However, my Gabble just sends
you a content-remove with no reason.
Firstly, it should send a content-reject.
Secondly, as per
<http://mail.jabber.org/pipermail/jingle/2009-November/001112.html> it should
include <reason><failed-application/></reason> in the content-reject.
Thirdly, it should also include <failed-application/> when terminating a
session because none of the codecs in the initiate were supported.
Fourthly, it should react to session-terminate with <failed-application/> by
emitting StreamError(..., Codec_Negotiation_Failed, ...) for each stream before
ending the call.
This would allow the UI to tell the user what happened in more cases than it
currently can.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the telepathy-bugs
mailing list