In some SIP deployments, a commonly contacted remote endpoint exhibits incompatible behavior if certain RTP payload numbers are in use. As some of those endpoints come from a major hardware manufacturer, and used in certain large corporate deployments, it's worthwhile to have a media channel interface defining a property to blacklist codec IDs from being assigned by the stream engine. The type could be a(uau) or a{uau}, where the first u is Media_Stream_Type and the second u is for codec ID numbers.
I believe we already implemented this (in an ad-hoc way) in telepathy-sofiasip and telepathy-farsight, so we just need the spec to catch up?
(In reply to comment #1) > I believe we already implemented this (in an ad-hoc way) in telepathy-sofiasip > and telepathy-farsight, so we just need the spec to catch up? Right.
I don't see any support for this in telepathy-farsight, or indeed in telepathy-sofiasip? Could you propose a patch, please? Setting priority to low since nobody seems to have cared thus far :-P
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-spec/issues/13.
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.