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

[Damien Sandras <dsandras seconix com>]

Le mardi 03 juin 2008 à 12:30 +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
> > CC: ekiga-devel-list gnome org
> > Datum: Dienstag, 3. Juni 2008, 13:58
> > Le mardi 03 juin 2008 à 11:01 +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
> > > > 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 
> > 
> > OK, so without the flag, the user will not get what he
> > wants because the
> > answer from Asterisk does not contain the extended options.
> > Consequently, default parameters are being used.
> > 
> > So I think Robert's choice is correct. If the user
> > complains that it
> > does not get what he asked, he should complain to Asterisk
> > developers
> > and not Ekiga developers.
> > -- 
> >  _     Damien Sandras
> 
> I do fully agree. However since 500 uses asterisk, whats our plan to be able to easily demonstrate the new video capabilities?
> 

Good question :-/
-- 
 _     Damien Sandras
(o-      
//\    Ekiga Softphone : http://www.ekiga.org/
v_/_   NOVACOM         : http://www.novacom.be/
       FOSDEM          : http://www.fosdem.org/
       SIP Phone       : sip:dsandras ekiga net