You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Back to Table of Contents 

Back to Media Services

Back to Supported Codecs and Transcoding

In this section:

Related articles:

Video Codecs SIP

The

Unable to show "metadata-from": No such page "_space_variables"
relays all video codecs by default using static or dynamic payloads.  

Video Codecs H.323

The

Unable to show "metadata-from": No such page "_space_variables"
supports the following codecs for H.323-H.323 video peering scenarios (i.e. H.323-H.323 calls with an audio and video stream).

Supported Codecs for H.323-H.323 Video Peering

Codec VariantPayload Type
H.224Dynamic
H.26131/Dynamic
H.26334/Dynamic
H.263-1998Dynamic
H.263-2000Dynamic
H.264Dynamic
H.264-RCDODynamic
H.264-SVCDynamic
H.264-UCDynamic
When using H.263/H.264, the endpoint must support RTCP to ensure quality video.

Video Bandwidth Allocation

Unable to show "metadata-from": No such page "_space_variables"
is enhanced to determine a session bandwidth value when a video is present in a call and use the same session bandwidth value to allocate for the entire call. Since, a call is a multiplex of streams, the same bandwidth number is used to allocate the video stream. This is based on the assumption that at any point of time during a call, all the session bandwidth can also be used by the video. But, this happens if all the other streams are stopped or currently not in use. If there is a video in the call,
Unable to show "metadata-from": No such page "_space_variables"
switches between the new session based allocation and the original stream based methods.

The following are the advantages of using the new method (session based allocation method):

  • Unable to show "metadata-from": No such page "_space_variables"
    allocates bandwidth at the session level and not at the individual stream level.
  • Unable to show "metadata-from": No such page "_space_variables"
     applies the PSP video bandwidth settings to a session and not to individual stream.
  • Unable to show "metadata-from": No such page "_space_variables"
    sets the session bandwidth to maximum video codec bandwidth in H323 / SIP calls.
  • Unable to show "metadata-from": No such page "_space_variables"
    enhances the CDR to track error bursts and to compute an estimated reduction factor.
  • Unable to show "metadata-from": No such page "_space_variables"
    now allocates based on the minimum value of the video and session bandwidth and not the maximum.
  • Unable to show "metadata-from": No such page "_space_variables"
    enforces all the streams to be on the same LIF.

Managing Bandwidth Settings

The bandwidth signaling in SDP can be done at the session level, the media level or both. The majority of the endpoint implementation uses the session level signaling. When the bandwidth is signaled at the session level, the usage of the bandwidth across the stream varies in a call.

For example: If there is a call with audio, video and slides in it with the following conditions:

IfThen
the slide stream is not in use.the video stream consumes more bandwidth.
the slide stream is in use.the main video bandwidth gets reduced by the amount of bandwidth used by the slide stream.
the slide stream is paused and audio is in mute.the main video bandwidth uses all the available session bandwidth.

To avoid the above situations, the bandwidth allocation is done for the entire session and not on individual streams.

For information on SIP-SIP Video treatment, refer to Video Support.

  • No labels