[Asterisk-video] H263 Jungle

Sergio Garcia Murillo sergio.garcia at fontventa.com
Mon Jan 7 06:24:01 CST 2008


Only that it's a bit incorrect.. :P

"The main problem with this is that UAs who don't understand RFC4629
will think that H263-1998 without annexes is actually H263+ as defined
in RFC2429, but based on RFC4629 it is H263. So this means that UAs that
implement RFC4629 could be incompatible with UAs that don't."

I'll be happy the day people understand what it's h263+ and h263++

http://en.wikipedia.org/wiki/H.263

Just by definition an h263 stream is a h263+ and a h263++ stream,
h263+ and h263++ defines new OPTIONAL annexes. The annexes used have 
to be signaled in the SDP.
So in theory, as asterisk doesn't keep track of those things, it only
"handles" h263 streams with RFC 2190 or 2429 packetization.

By the way, any one have tested the Olle's videocaps branch?

BR
Sergio

On Mon, 2008-01-07 at 13:04 +0100, Klaus Darilion wrote:
>                              From: 
> Klaus Darilion
> <klaus.mailinglists at pernau.at>
>                          Reply-To: 
> Development discussion of video
> media support in Asterisk
> <asterisk-video at lists.digium.com>
>                                To: 
> asterisk-video at lists.digium.com
>                           Subject: 
> [spam][Asterisk-video] H263 Jungle
>                              Date: 
> Mon, 07 Jan 2008 13:04:45 +0100
> 
> 
> Hi!
> 
> I just found this description about the H263 RTP payload types
> http://farsight.freedesktop.org/wiki/H263Jungle
> 
> regards
> klaus
> 
> ______________________________





More information about the asterisk-video mailing list