Hi Arun and Juan, Sorry for the delayed response, I was on a long vacation. But now I am again focused on ooh323c. Here's the latest status. The media plug-in, as you guys found out, is a very simple implementation. It supports only windows and linux. To be precise, I have tested only on windows XP and RedHat linux 9. The windows version has a slightly better audio quality than the linux version. The purpose is to show how others can use their own rtp stack or some other open source rtp stack and codecs with ooh323c. ooh323c, at the moment, is only focused on providing a light weight 'C' based H.323/H.245 signalling. I have added support for FastStart and Tunneling and will release it soon. If you guys are looking for sompe specific things, let me know and I'll see if something can be done. regards, Vishal Phirke
Hello, Thanks for your interest. You can subscribe to the mailing list to get updates of the progress. For subscribing visit - http://lists.sourceforge.net/lists/listinfo/ooh323c-devel. The only available documentation is the one you get with the downloaded source. If you want to learn more about H.323 protocol then try digging into http://www.packetizer.com/. If you are interested in contributing to the code, then let me know and I'll co-ordinate with you. regards, Vishal Phirke ----- Original Message ----- From: K.B.Pawar To: ooh323c-devel@... Sent: Wednesday, January 12, 2005 10:08 PM Subject: [ooh323c-devel] want to become member Respected sir, I am Kashinath Pawar, currently started working on H.323 ... so while searching on open source code for H.323 protocol stack , i got u r code,it is excellent....... can u send me the call flow document for this soon? keep updating me on your progress. awaiting for your reply. Thanks and regards Kashinath Pawar E-mail kashinath.p@...
Hi All, I have uploaded 0.4 release. It supports faststart, tunneling. Also, completed feature request to allow configuration of RTP ip:port by application. The earlier release used to select local ip and local port as media endpoint, now it is possible for an application to configure a separate ip:port for media channels. This can be handy when signalling is done at one ip and media is terminated at a separate ip. Also, the call cleanup logic is improved. My next tasks are: 1. GateKeeper support 2. Timers for various message timeouts. And ofcourse lot of other small things..If anyone wants to contribute, do let me know. And even if you don't have time for contribution, but can give feedback, that will be great. I will try to setup CVS, so that everyone can get bleeding edge sources directly from CVS instead of waiting for a release. regards, Vishal Phirke
I cross compiled the ooh323c code. Everything is fine but when I tried
to execute the sample program on "Intel PXA27x Processor Developers'
Kit":
bash-2.05b# ./simple
Failed to load the media plug-in library - liboomedia.so
The weird part is "liboomedia.so" has been installed to /usr/lib
and I have added this directory to "ld.so.conf".
And I found that it is caused by the following lines:
media = 0;
/* Load the plugin library */
#ifdef _WIN32
media = LoadLibrary(name);
#else
media = dlopen(name, RTLD_NOW|RTLD_GLOBAL);
#endif
if(media == 0)
{
OOTRACEERR2("ERROR:Failed to load plug-in library %s\n", name);
return OO_FAILED;
}
It seems dlopen can't open the shared library correctly and makes
"media" equal 0 or it doesn't change the "media". Can anyone give me an
explanation on why this library can't be open? Thanks so much.
Liang
Hello members. OOH323C seems very attractive and better choice than OpenH323 if you have the limited resources of an embedded board. Everybody who has used OpenH323 knows its huge size and tremendous resource needs, easily acceptable in a cutting edge PC, but not in an embedded system. Thats why I'm working on 0.3.1 release to use it in an embedded board based on a MPC860 PowerPC running linux 2.4.26 at 66 MHz. Although I was not able to get the media plugin working in a PC with Suse 8, when I adapted it to use the DSP of my embedded board it started working. These past days I have been working on adding RAS support, mandatory in my application. I have a very tiny implementation of the protocol ( only GRQ, RRQ, and ARQ messages are supported). It has succeeded on registering with the GNU Gatekeeper and establishing calls with an OpenH323-based endpoint. Of course, this code is available to everybody who find it useful. Maybe Vishal ? Regards. -----Mensaje original----- De: ooh323c-devel-admin@... [mailto:ooh323c-devel-admin@...] En nombre de Vishal Phirke Enviado el: viernes, 21 de enero de 2005 23:35 Para: ooh323c-devel@... Asunto: [ooh323c-devel] Release 0.4 Hi All, I have uploaded 0.4 release. It supports faststart, tunneling. Also, completed feature request to allow configuration of RTP ip:port by application. The earlier release used to select local ip and local port as media endpoint, now it is possible for an application to configure a separate ip:port for media channels. This can be handy when signalling is done at one ip and media is terminated at a separate ip. Also, the call cleanup logic is improved. My next tasks are: 1. GateKeeper support 2. Timers for various message timeouts. And ofcourse lot of other small things..
hi.. i just working on H323 protocol stack, could you email me a patch ? and does you fixed some H.245 encoding and decoding ? On my XScale board, H.245 encoding and decoding could cause a crash here. your experience will be appreciate.. thanks in advance . > Hello members. > > OOH323C seems very attractive and better choice than OpenH323 if you > have the limited resources of an embedded board. Everybody who has used > OpenH323 knows its huge size and tremendous resource needs, easily > acceptable in a cutting edge PC, but not in an embedded system. Thats > why I'm working on 0.3.1 release to use it in an embedded board based on > a MPC860 PowerPC running linux 2.4.26 at 66 MHz. > > Although I was not able to get the media plugin working in a PC with > Suse 8, when I adapted it to use the DSP of my embedded board it started > working. > > These past days I have been working on adding RAS support, mandatory in > my application. I have a very tiny implementation of the protocol ( only > GRQ, RRQ, and ARQ messages are supported). It has succeeded on > registering with the GNU Gatekeeper and establishing calls with an > OpenH323-based endpoint. > > Of course, this code is available to everybody who find it useful. Maybe > Vishal ? > > Regards. > > > -----Mensaje original----- > De: ooh323c-devel-admin@... > [mailto:ooh323c-devel-admin@...] En nombre de Vishal > Phirke > Enviado el: viernes, 21 de enero de 2005 23:35 > Para: ooh323c-devel@... > Asunto: [ooh323c-devel] Release 0.4 > > > Hi All, > I have uploaded 0.4 release. It supports faststart, tunneling. Also, > completed feature request to allow configuration of RTP ip:port by > application. The earlier release used to select local ip and local port > as media endpoint, now it is possible for an application to configure a > separate ip:port for media channels. This can be handy when signalling > is done at one ip and media is terminated at a separate ip. Also, the > call cleanup logic is improved. My next tasks are: 1. GateKeeper support > > 2. Timers for various message timeouts. > And ofcourse lot of other small things..
hi, all. I got problem on my XScale embedded board. It seems it crash while it decoding H.245 packet. and i am trying to fix it. and jmgarcia, could you contribute your patch about RAS ? Regards. > Hello members. > > OOH323C seems very attractive and better choice than OpenH323 if you > have the limited resources of an embedded board. Everybody who has used > OpenH323 knows its huge size and tremendous resource needs, easily > acceptable in a cutting edge PC, but not in an embedded system. Thats > why I'm working on 0.3.1 release to use it in an embedded board based on > a MPC860 PowerPC running linux 2.4.26 at 66 MHz. > > Although I was not able to get the media plugin working in a PC with > Suse 8, when I adapted it to use the DSP of my embedded board it started > working. > > These past days I have been working on adding RAS support, mandatory in > my application. I have a very tiny implementation of the protocol ( only > GRQ, RRQ, and ARQ messages are supported). It has succeeded on > registering with the GNU Gatekeeper and establishing calls with an > OpenH323-based endpoint. > > Of course, this code is available to everybody who find it useful. Maybe > Vishal ? > > Regards. > > > -----Mensaje original----- > De: ooh323c-devel-admin@... > [mailto:ooh323c-devel-admin@...] En nombre de Vishal > Phirke > Enviado el: viernes, 21 de enero de 2005 23:35 > Para: ooh323c-devel@... > Asunto: [ooh323c-devel] Release 0.4 > > > Hi All, > I have uploaded 0.4 release. It supports faststart, tunneling. Also, > completed feature request to allow configuration of RTP ip:port by > application. The earlier release used to select local ip and local port > as media endpoint, now it is possible for an application to configure a > separate ip:port for media channels. This can be handy when signalling > is done at one ip and media is terminated at a separate ip. Also, the > call cleanup logic is improved. My next tasks are: 1. GateKeeper support > > 2. Timers for various message timeouts. > And ofcourse lot of other small things..
Hi Juan, That was the main driving factor behind ooh323c, to have something simple which will work well and also will be useful in embedded systems. We have used it successfully, to provide an efax based fax application on embedded systems. As far as media plug-in goes, ooh323c has a very simple implementation, which is just for demonstration purpose and has been tested on windows and Red hat linux platforms only. I am definitely interested in receiving your patch. regards, Vishal On Wed, 26 Jan 2005 12:36:02 +0100, Juan Manuel Garcia <jmgarcia@...> wrote: > > Hello members. > > OOH323C seems very attractive and better choice than OpenH323 if you > have the limited resources of an embedded board. Everybody who has used > OpenH323 knows its huge size and tremendous resource needs, easily > acceptable in a cutting edge PC, but not in an embedded system. Thats > why I'm working on 0.3.1 release to use it in an embedded board based on > a MPC860 PowerPC running linux 2.4.26 at 66 MHz. > > Although I was not able to get the media plugin working in a PC with > Suse 8, when I adapted it to use the DSP of my embedded board it started > working. > > These past days I have been working on adding RAS support, mandatory in > my application. I have a very tiny implementation of the protocol ( only > GRQ, RRQ, and ARQ messages are supported). It has succeeded on > registering with the GNU Gatekeeper and establishing calls with an > OpenH323-based endpoint. > > Of course, this code is available to everybody who find it useful. Maybe > Vishal ? > > Regards. > > -----Mensaje original----- > De: ooh323c-devel-admin@... > [mailto:ooh323c-devel-admin@...] En nombre de Vishal > Phirke > Enviado el: viernes, 21 de enero de 2005 23:35 > Para: ooh323c-devel@... > Asunto: [ooh323c-devel] Release 0.4 > > > Hi All, > I have uploaded 0.4 release. It supports faststart, tunneling. Also, > completed feature request to allow configuration of RTP ip:port by > application. The earlier release used to select local ip and local port > as media endpoint, now it is possible for an application to configure a > separate ip:port for media channels. This can be handy when signalling > is done at one ip and media is terminated at a separate ip. Also, the > call cleanup logic is improved. My next tasks are: 1. GateKeeper support > > 2. Timers for various message timeouts. > And ofcourse lot of other small things..
Hi Leon, Try the new release 0.4. And if you still see a crash, send me the log. regards, Vishal On Wed, 26 Jan 2005 20:51:18 +0800, Leon Zhang <zhangx@...> wrote: > hi, all. > I got problem on my XScale embedded board. > It seems it crash while it decoding H.245 packet. > and i am trying to fix it. > > and jmgarcia, could you contribute your patch about RAS ? > > Regards. > > > Hello members. > > > > OOH323C seems very attractive and better choice than OpenH323 if you > > have the limited resources of an embedded board. Everybody who has used > > OpenH323 knows its huge size and tremendous resource needs, easily > > acceptable in a cutting edge PC, but not in an embedded system. Thats > > why I'm working on 0.3.1 release to use it in an embedded board based on > > a MPC860 PowerPC running linux 2.4.26 at 66 MHz. > > > > Although I was not able to get the media plugin working in a PC with > > Suse 8, when I adapted it to use the DSP of my embedded board it started > > working. > > > > These past days I have been working on adding RAS support, mandatory in > > my application. I have a very tiny implementation of the protocol ( only > > GRQ, RRQ, and ARQ messages are supported). It has succeeded on > > registering with the GNU Gatekeeper and establishing calls with an > > OpenH323-based endpoint. > > > > Of course, this code is available to everybody who find it useful. Maybe > > Vishal ? > > > > Regards. > > > > > > -----Mensaje original----- > > De: ooh323c-devel-admin@... > > [mailto:ooh323c-devel-admin@...] En nombre de Vishal > > Phirke > > Enviado el: viernes, 21 de enero de 2005 23:35 > > Para: ooh323c-devel@... > > Asunto: [ooh323c-devel] Release 0.4 > > > > > > Hi All, > > I have uploaded 0.4 release. It supports faststart, tunneling. Also, > > completed feature request to allow configuration of RTP ip:port by > > application. The earlier release used to select local ip and local port > > as media endpoint, now it is possible for an application to configure a > > separate ip:port for media channels. This can be handy when signalling > > is done at one ip and media is terminated at a separate ip. Also, the > > call cleanup logic is improved. My next tasks are: 1. GateKeeper support > > > > 2. Timers for various message timeouts. > > And ofcourse lot of other small things..
RSS Feed1 | |
|---|---|
2 | |
1 | |
1 | |
2 | |
2 | |
3 | |
1 | |
1 | |
3 | |
7 | |
11 | |
5 | |
33 | |
34 | |
5 | |
4 | |
7 | |
4 | |
13 | |
21 | |
47 | |
28 | |
54 | |
30 | |
57 | |
48 | |
22 | |
56 | |
48 | |
47 | |
22 | |
13 | |
9 | |
7 | |
4 | |
21 | |
4 | |
16 | |
3 | |
1 |
