[Asterisk-video] h263 again

[Klaus Darilion]

Thanks! Things are getting clearer now.

regards
klaus

Sergio Garcia Murillo schrieb:
> Hi Klaus,
> 
> H263 annexes supported by the terminal are sent in the H245TerminalCapabilitySet message.
> 
> I'm sending
>         capabilityTable = 4 entries {
>           [0]={
>             capabilityTableEntryNumber = 1
>             capability = receiveAndTransmitVideoCapability h263VideoCapability {
>               qcifMPI = 2
>               maxBitRate = 520
>               unrestrictedVector = FALSE
>               arithmeticCoding = FALSE
>               advancedPrediction = FALSE
>               pbFrames = FALSE
>               temporalSpatialTradeOffCapability = FALSE
>               errorCompensation = FALSE
>             }
>           }
> 
> So we will get a h263 base stream with no annexes. The stream is then encapsulated in rtp
> using rfc 2429 so the output rtp stream is both h263-1998 and h263-2000 (H263P in asterisk).
> 
> I don't use rfc 2190 (h263-1996) because it would require a deep inspect on the video 
> stream to find macroblocks/gob/slice boundaries to create the rtp packet.
> 
> BR
> Sergio
> 
> ----- Original Message -----
> From: Klaus Darilion [mailto:klaus.mailinglists at pernau.at]
> To: asterisk-video at lists.digium.com
> Sent: Fri, 11 Jan 2008 13:34:11 +0100
> Subject: [Asterisk-video] h263 again
> 
> Hi Sergio!
> 
> Do you know what version of H.263 is used for 3G video calls?
> 
> What is coming out of the 3G stream, H.263v1, v2 or v3 ? Is this static 
> or is there a handshake to agree on the video protocol?
> 
> 
> I see in h324m_gw:
> 
> 
> 
>                  case MEDIA_VIDEO:
>                          /*Check it's H263 */
>                          if (FrameGetCodec(frame)!=CODEC_H263)
>                                  /* exit */
>                                  return NULL;
> ...
>                          /* Set video type */
>                          send->frametype = AST_FRAME_VIDEO;
>                          /* Set codec value */
>                          send->subclass = AST_FORMAT_H263_PLUS | mark;
> 
> 
> 
> Thus, as RTP encoding H263-1998 is used - correct? If I understand 
> correctly this could mean that the stream is either H.263v2 or H.263v1 
> encoded as H263-1998. Is my assumption correct?
> 
> thanks
> klaus
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-video mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-video
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> --Bandwidth and Colocation Provided by http://www.api-digital.com--
> 
> asterisk-video mailing list
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-video