On 8/7/07, Simon Horne <s.horne@xxxxxxxx> wrote:
At 04:49 PM 7/08/2007, Hugo Pereira wrote:
>So, in openh323 how can what are the steps in order to implement a generic
>or a nonStandard capability and codec?
Exactly the same as in Opal, as the plugin support in OpenH323 was ported
from Opal and is designed to be interoperable. Unfortunately currently
neither the H.264 and MPEG4 plugins in Opal have been properly configured
to provide a guide so I suggest you look at the GSM-AMR audio plugin codec
to give you an idea of how generic capabilities are handled then take the
H.261 or H.263 video codec shell and create a generic video codec plugin.
In H.323 generic capabilities are identified by an OID so you need to
define the OID. If the capabiility code is working in the CVS (it was a few
months back) then you should be able to create a video capability without
needing to statically provision it.
I am trying to start from scratch from the amrcodec plugincodec interface, altering it in order to support a generic video. However, when i look for the h263 and h261 video codec i see too many dependencies to the h323 core!
My porpoise here was to build a generic or a non standard video codec without having to change the openh323 core. This is being a very difficult task. I am a little lost in so many code dependencies. Could you guide and give me a hand?
