On Jun 19, 2009, at 12:08 PM, Alan Clark wrote:
I would think the right mechanism for this would be CCM (Codec Control messages), not header extensions.A parallel problem is the control (rather than indication) of volume and noise suppression in VoIP calls. 911 operators find that sometimes they do want noise suppression and sometimes they don't. Noise suppression can be helpful when they are trying to understand a caller in a noisy background environment however it can also suppress background noises that can help to understand the emergency situation (e.g. if they hearing kids laughing in the background the call may be a prank (which does happen quite frequently) but other sounds may indicate how serious a problem is or provide locationinformation).
Alan On 6/19/09 11:46 AM, "Colin Perkins" <csp at csperkins.org> wrote:On 15 Jun 2009, at 15:35, Emil Ivov wrote:We have just submitted the following draft: http://www.ietf.org/internet-drafts/draft-ivov-avt-slic-00.txt The draft proposes a solution for a problem that's been extensively discussed on the dispatch mailing list during the past few weeks. Itconcerned a means of transporting sound level in conferences in a waythat would allow presenting it to the user and extending the active speaker concept.I haven't been following dispatch, but this looks like a good use of the RTP header extension mechanism._______________________________________________ Audio/Video Transport Working Group avt at ietf.org https://www.ietf.org/mailman/listinfo/avt
Attachment:
PGP.sig
Description: PGP signature