Re: [Ekiga-devel-list] Video capabilities and asterisk (mostly)

[Matthias Schneider <ma30002000 yahoo de>]

--- Damien Sandras <dsandras seconix com> schrieb am Di, 3.6.2008:

> Von: Damien Sandras <dsandras seconix com>
> Betreff: Re: [Ekiga-devel-list] Video capabilities and asterisk (mostly)
> An: ma30002000 yahoo de
> CC: ekiga-devel-list gnome org
> Datum: Dienstag, 3. Juni 2008, 11:16
> Le mardi 03 juin 2008 à 09:14 +0000, Matthias Schneider a
> écrit :
> > 
> > 
> > --- Damien Sandras <dsandras seconix com>
> schrieb am Di, 3.6.2008:
> > 
> > > Von: Damien Sandras <dsandras seconix com>
> > > Betreff: Re: [Ekiga-devel-list] Video
> capabilities and asterisk (mostly)
> > > An: ma30002000 yahoo de
> > > Datum: Dienstag, 3. Juni 2008, 10:45
> > > Le mardi 03 juin 2008 à 08:44 +0000, Matthias
> Schneider a
> > > écrit :
> > > > 
> > > > 
> > > > --- Damien Sandras
> <dsandras seconix com>
> > > schrieb am Di, 3.6.2008:
> > > > 
> > > > > Von: Damien Sandras
> <dsandras seconix com>
> > > > > Betreff: Re: [Ekiga-devel-list] Video
> > > capabilities and asterisk (mostly)
> > > > > An: ma30002000 yahoo de
> > > > > Datum: Dienstag, 3. Juni 2008, 9:43
> > > > > Le mardi 03 juin 2008 à 06:49 +0000,
> Matthias
> > > Schneider a
> > > > > écrit :
> > > > > 
> > > > > > 
> > > > > > This setting is not RFC-compliant
> (you can
> > > consider
> > > > > asterisk broken on that point). The
> default for
> > > this
> > > > > setting was decided to be the RFC
> compliant one
> > > during the
> > > > > lenghty mail exchange we had on the
> capabilities
> > > (you were
> > > > > on CC). Robert was particularly against
> making a
> > > > > non-compliant setting a default
> setting. 
> > > > > > 
> > > > > 
> > > > > Ok, I did not follow that part of the
> discussion.
> > > > > 
> > > > > And what are the drawbacks of not using
> that
> > > option when
> > > > > compiling and
> > > > > calling asterisk ?
> > > > > -- 
> > > > >  _     Damien Sandras
> > > > 
> > > > This depends on the codec.
> > > > H.261: QCIF only, max. 30 fps.
> > > > H.263+: QCIF only, max. 15 fps.
> > > > H.264: baseline profile, level 1 only ->
> about 64
> > > kbit/s max., only QCIF
> > > > MPEG4: Simple Profile, LEvel 1, I suppose
> similar to
> > > H.264
> > > > THEROA: dont remember exactly, but I think
> it is still
> > > full capability.
> > > > 
> > > 
> > > OK, so it will always use those specific
> settings, whatever
> > > the
> > > negociation is. 
> > > -- 
> > No, 
> > the point is that asterisk HAS NOT any kinds of
> negotiation, thus we fall back to
> > the lowest possible means of transmission.
> > 
> 
> OK, but if we --enable-default-to-full-capabilities, what
> happens by
> comparison to not using that switch ? I mean, from the user
> point of
> view...
> 
> -- 
>  _     Damien Sandras
One example for H.264:

User selects 4CIF @30 fps and 512 kbit/s as desired resolution and bitrate and calls another enpoint. Depending on the other.s capabilities he/she gets:

asterisk without "full-capabilities option": -> level 1.0, QCIF @15fps and 64kbit/s
asterisk with "full-capabilities option": -> level 3.0,  4CIF @25fps, 512kbit/s
endpoint advertising baseline level 1.2 support: CIF @15fps,  384 kbit/s
endpoint advertising baseline level 2.0 support: CIF @30fps, 512 kbit/s 

Matthias




      __________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com