Re: [sipX-dev] codec configuration
> -----Original Message-----
> From: sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx
> [mailto:sipx-dev-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of
> Krzeminski, Damian (BL60:9D30)
> Sent: Tuesday, June 30, 2009 12:09 PM
> To: sipx-dev@xxxxxxxxxxxxxxxxxxx
> Subject: [sipX-dev] codec configuration
>
> Bogdan is working on
> http://track.sipfoundry.org/browse/XX-5492, which is just a
> first step in providing a more user friendly way of
> configuring codecs.
> Currently every managed device has a different way of
> configuring codecs.
> That's because sipXconfig plug-ins closely follow device's
> data models.
>
> We want to improve it in two ways:
> (1) by providing a better UI that plug-ins can use to offer
> codecs configuration (that's what XX-5492 is about)
> (2) by providing a central place that administrator can use
> to configure a default list of codecs for all devices (that's
> _not_ XX-5492)
>
> Paul and I exchanged some ideas on the list about problem (2):
> I had this naive vision that sipXconfig will query all the
> plug-ins construct a full list of all the codecs and then
> will let administrator to select which codecs and in which
> order should be used.
>
> Once admin decides that, sipXconfig will - for each device
> and service separately - translate the global list into
> what's supported for a specific device or service; raising
> red flags if it turns out that the intersection of desired
> and supported lists is empty.
>
> We would probably still need to allow for overwriting the
> global list on a per-device (and group) basis. One use case I
> can think of: codec X has a buggy implementation on a
> specific device; admin wants to allow it in general but not
> for that device type.
A more common use case would be a far-away remote worker with a very
modest internet connection. Such a user would want to restrict itself
to using the codecs that provide highest compression.
>
> Does that seem like a reasonable approach?
It does.
