| Add_docset_workflow |
|---|
| AUTH1 | bscoggins |
|---|
| DEV1 | xantony |
|---|
| LDEV1 | bscoggins |
|---|
| SVT1 | radaikalam |
|---|
| LSVT1 | bscoggins |
|---|
|
The
relays all video codecs by default using static or dynamic payloads.
...
| Note |
|---|
| When using H.263/H.264, the endpoint must support RTCP to ensure quality video. |
Video Bandwidth Allocation
Prior to this release,
allocated bandwidth on a per stream basis without considering any signalling done by the endpoints at the session level. This resulted in significant over allocation in many cases. is now 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, 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):
- allocates bandwidth at the session level and not at the individual stream level.
- applies the PSP video bandwidth settings to a session and not to individual stream.
- sets the session bandwidth to maximum video codec bandwidth in H323 / SIP calls.
- enhances the CDR to track error bursts and to compute an estimated reduction factor.
- now allocates based on the minimum value of the video and session bandwidth and not the maximum.
- 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:
| If | Then |
|---|
| 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.