Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Add_workflow_for_techpubs
AUTH2UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cd5909df, userName='null'}
AUTH1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c85b00e8, userName='null'}
REV5UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cca00892, userName='null'}
REV6UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26c7cd0042, userName='null'}
REV3

...

Noprint
Panel
borderColorgreen
bgColortransparent
borderWidth2

Back to Table of Contents 

Back to Media Services

Back to Supported Codecs and Transcoding

...

UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cafa0522, userName='null'}
REV1UserResourceIdentifier{userKey=8a00a02355cd1c2f0155cd26cafa0522, userName='null'}

Panel

In this section:

Table of Contents
maxLevel4

...

...

Video Codecs SIP

The

Spacevars
0

...

series4
relays all video codecs by default using static or dynamic payloads.  

Video Codecs H.323

The

Spacevars
0product
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).

Caption
0Table
1Supported 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

...

Info
titleNote

...

When using H.263/H.264, the endpoint must support RTCP to ensure quality video.

 

Video Bandwidth Allocation

The 

Spacevars
0product

...

 supports determining 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, the 

Spacevars
0product
switches between the new session based allocation and the original stream based methods.

The

...

Spacevars
0product
 includes the following advantages with using the session-based allocation method

...

:

Spacevars
0product

...

  • Allocates bandwidth at the session level and not at the individual stream level.
Spacevars
0product

...

  • Applies the PSP video bandwidth settings to a session and not to individual stream.
Spacevars
0product

...

  • Sets the session bandwidth to maximum video media bandwidth in H.323 / SIP calls.
Spacevars
0product

...

  • Enhances the CDR to track error bursts and to compute an estimated reduction factor.
Spacevars
0product

...

  • Allocates based on the minimum value of the video and session bandwidth.
Spacevars
0product

...

  • Enforces all streams to be present 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

...

a call with audio exists, 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 stream 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 stream could use all of the available session bandwidth.

Considering the scenarios described above, the bandwidth allocation is performed for the entire session and not on individual streams.

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

Pagebreak