Hi Simon and h323plus members,

 
I am sure my H.264 codec definition(in the plugin)  was set to 768kbps.
Also, I only load H.264 plugin in my H.323 application, no H.261 and no H.263.
 
When I do tracing on the changes on my MaxbitRate,
 
I notice that if i set 512kbps by calling the H323Connection::SetIntialBandwidth(),  
this function  will set the new value into each format in my plugin (H.264 QCIF, H.264 CIF, H.264 4CIF)  since it is true for 512< 768.
The problem is when I trace bandwidth value in  H323Channel::SetInitialBandwidth(), I find that It deduce 384kbps in total bandwidth of the overall bandwidth this system have. Not 512kbps.

which step is going wrong?
 
Thanks.
 
On Thu, Oct 28, 2010 at 8:09 PM, Simon Horne <s.horne@packetizer.com> wrote:

Kc

 

The codec definition (in the plugin) sets the upper BitRate limit for the codec. if you set a targetbitrate higher that the maxbitRate from the plugin codec then it is ignored.

 

For instance H.263 CIF will not exceed the 384k set in the codec definition. To fix just change the maxbitrate value in the plugin codec.

 

Simon

 

From: kc ooi [mailto:kcooi12345@gmail.com]
Sent: Thursday, October 28, 2010 8:49 PM
To: Simon Horne
Cc: h323plus@lists.packetizer.com
Subject: Re: [h323plus] Call Rate Issue using H323plus

 

Hi Simon and h323plus members,

 

I manage to get it work in the situation where SetInitialBandwidth is set to video type and less than 384kbits.

The other terminal will be notified and sending video below the limit.

 

But it fail when I set more than 384kbits, for example 512kbits or 1Mbits.

 

Is there  a default value that defines the limit?

 

Thanks.

 

 

  On Thu, Oct 28, 2010 at 9:01 AM, Simon Horne <s.horne@packetizer.com> wrote:


There has been some improvement in bandwidth management in the current CVS.

There are 2 parts 1 what we limit what we send and what we request the
remote to limit to.

When setting the local bandwidth this can be set by your derived
H323Connection::OpenVideoChannel function ie codec->SetMaxBitRate() .

To set the remote there is an improved function
H323Connection::SetInitialBandwidth(H323Capability::MainTypes & captype, int
bitRate)
Which you can call when you instance the connection object which will limit
the bandwidth of all advertised capabilities in the TCS to the value you
specify and that should limit the bandwidth the remote requests in the OLC
and hence what it will send.

Simon


-----Original Message-----
From: h323plus-bounces@lists.packetizer.com
[mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of kcooi12345
Sent: Wednesday, October 27, 2010 7:20 PM
To: h323plus@lists.packetizer.com
Subject: [h323plus] Call Rate Issue using H323plus

Hi All,

Does anyone know how to set the call rate for a conference?

In my H.323 application that use h323plus library, it use
384 kbits by default to create a conference.
I have try to use function SetInitialBandwidth(51200)for 512kbits call rate,
but it also fails.

Thanks.