- h323plus - lists.packetizer.com

H264 PLUGIN in h323plus
by ooi khai chin 24 Nov '09

24 Nov '09

Hi All, For the libx264, It directly fragment the encoded data if it larger than the maxpayloadsize (1.4KB by default). If I had encoded data 5.6K. Then, it will fragment and sent out, 4 times. Is it comply to H.323 standard? Because currently other voip (polycom, Mirial...) can't display my encoded data size greater than 1.4K. Thanks.

2 1

H264 PLUGIN in H323Plus
by ooi khai chin 24 Nov '09

24 Nov '09

Hi All, Currently, my H264 plugin able to work with polycom. I found that the media statistic(polycom PVX ) only show the frame rate video format, and display the image if my sending encoded data is not more than 1.4KB. In my code, I do the fragmentation once it greater than 1.4KB(like libx264 do). However, I had read some documentations and all of them mentioned about H.241 only support the single NAL unit mode(mode 0). I wonder how this mode handle if encoded data greater than 1.4KB(usually happen)??? Any Idea? Thanks.

3 3

H264 PLUGIN in H323Plus
by ooi khai chin 23 Nov '09

23 Nov '09

Hi All, I captured the capability exchange from difference voip software like(polycom, vcon...), it show only "0.0.8.241.0.0.1", which is defined as OpalPluginCodec_Identifier_H264_Generic. 1. What is the difference with the others like (default, RFC3984 interleave, RFC3984 non interleave)? Another things is that When I use my H.264 Encoder API, it only return me the encoded data and the encoded length. 2. So, is it considered as single NAL unit? How it can be comply to H.323 since the default MTU value in H.323 is 1400bytes (like fragmentation or other)? I try to increate the MTU value, but it cause me error.

2 1

Re: [h323plus] [Openh323gk-users] PTLIB PASN_BMPString handling changes and endpoint not registered.
by Simon Horne 18 Nov '09

18 Nov '09

Guys I need to make you aware of a change that causes different registration endpoint identifier lengths to be generated based on the version of ptlib used. GnuGK 2.3.0 (ptlib 2.4.5) registrationConfirm { ... endpointIdentifier = 9 characters { 0034 0033 0039 0035 005f 0065 006e 0064 4395_end 0070 p } GnuGk 2.3.1 (ptlib cvs) registrationConfirm { ... endpointIdentifier = 10 characters { 0034 0033 0039 0035 005f 0065 006e 0064 4395_end 0070 0000 p } While this may not look too much of a problem however if you are registering a h323plus endpoint built off a later version of PTLIB (like PacPhone) on a GnuGk with an earlier version of PTLIB then your endpoint will register but will not be able to make any calls and you will get an error about endpoint not registered. This is because the gatekeeper generated a 9 character endpointIdentifer while the endpoint will send a 10 digit identifier to the gatekeeper. I have patched the latest PacPhone preRelease to resolve the problem www.pacphone.com/downloads/PacPhoneSetup230.exe I will be applying a fix to the H323plus CVS shortly. Simon

1 0

Re: [h323plus] OpenMCU Codec issues
by Simon Horne 18 Nov '09

18 Nov '09

Josh Put the plugins in /usr/lib/ptlib they will automatically be read in at application startup. There is no need to recompile OpenMCU. Simon _____ From: Josh Barth [mailto:jbarth@buttechc.com] Sent: Wednesday, 18 November 2009 10:38 AM To: 'Simon Horne' Subject: RE: [h323plus] OpenMCU Codec issues So I still have the same issue, I have set the PTLIBPLUGINDIR env var. Should the structure then be /usr/local/lib/ptlib and then each of the libraries? Or should they exist in codecs/ or codecs/audio/ and codecs/video/ I am right in thinking once these are placed properly OpenMCU should pick them up? I don't have to place them, then recompile OpenMCU do I? Thanks very much, Josh From: Simon Horne [mailto:s.horne@packetizer.com] Sent: Tuesday, November 17, 2009 5:17 PM To: Josh Barth Subject: RE: [h323plus] OpenMCU Codec issues Josh The default directory for plugins should be /usr/lib/ptlib unless you set the environment variable PTLIBPLUGINDIR to point to your plugin directory. Simon _____ From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Josh Barth Sent: Wednesday, 18 November 2009 9:45 AM To: 'h323plus(a)lists.packetizer.com' Subject: [h323plus] OpenMCU Codec issues I have the ptlib, h323plus, plugins, and openmcu from h323plus.org I built each successfully, but I am not having any luck getting the additional codecs loaded when I launch OpenMCU, all I get is G.711. Did I not build something right? In order I built, ptlib, h323plus, openmcu, plugins Where should the codecs be located? (they are in /usr/local/lib/pwlib) These are modular correct, I don't need to re-compile h323plus or OpenMCU? Here is my trace: 0:00.081 OpenMCU Version 2.2.5 by H323plus on Unix Linux (2.6.26-2-sparc64-sparc64) at 2009/11/17 14:43:29.321 0:00.082 OpenMCU PWLib File handle high water mark set: 15 Thread unblock pipe 0:00.082 OpenMCU PWLib Created thread 0x162c78 H323 Listener:%0x 0:00.083 OpenMCU PWLib File handle high water mark set: 16 PTCPSocket 0:00.083 OpenMCU H323 Started listener Listener[ip$*:1720] 0:00.084 OpenMCU PWLib Thread high water mark set: 6 0:00.085 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.085 OpenMCU H323 Added capability: G.711-ALaw-64k <1> 0:00.085 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.086 OpenMCU H323 Added capability: G.711-uLaw-64k <2> 0:00.086 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.086 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-ALaw-64k{sw}" 0:00.087 OpenMCU H323 FindCapability: "G.711-uLaw-64k{sw}" 0:00.087 OpenMCU EXT No Extended Capabilities found to load 0:00.088 OpenMCU H323 FindCapability: "*-QCIF*" 0:00.088 OpenMCU H323 FindCapability: "*-SQCIF*" 0:00.088 OpenMCU H323 Added capability: UserInput/hookflash <3> 0:00.088 OpenMCU H323 Added capability: UserInput/basicString <4> 0:00.088 OpenMCU H323 Added capability: UserInput/dtmf <5> 0:00.089 OpenMCU H323 Added capability: UserInput/RFC2833 <6> 0:00.089 OpenMCU H323 Added capability: UserInput/Navigation <7> 0:00.089 OpenMCU H323 Added capability: UserInput/Softkey <8> 0:00.089 OpenMCU H323 Added capability: UserInput/PointDevice <9> 0:00.089 OpenMCU H323 Added capability: UserInput/Modal <10> 0:00.089 OpenMCU MCU Codecs (in preference order): Table: G.711-ALaw-64k <1> G.711-uLaw-64k <2> UserInput/hookflash <3> UserInput/basicString <4> UserInput/dtmf <5> UserInput/RFC2833 <6> UserInput/Navigation <7> UserInput/Softkey <8> UserInput/PointDevice <9> UserInput/Modal <10> Set: 0: 0: G.711-ALaw-64k <1> G.711-uLaw-64k <2> 1: 2: UserInput/hookflash <3> UserInput/basicString <4> UserInput/dtmf <5> UserInput/RFC2833 <6> UserInput/Navigation <7> UserInput/Softkey <8> UserInput/PointDevice <9> UserInput/Modal <10> 0:00.094 OpenMCU PWLib File handle high water mark set: 17 PTCPSocket 0:00.095 OpenMCU PWLib File handle high water mark set: 19 Thread unblock pipe 0:00.095 OpenMCU PWLib Created thread 0x168620 HTTP Service 0:00.095 H323 Listener:f6f8bb90 PWLib Started thread 0x162c78 H323 Listener:f6f8bb90 0:00.095 H323 Listener:f6f8bb90 H323 Awaiting TCP connections on port 1720 0:00.095 H323 Listener:f6f8bb90 TCP Waiting on socket accept on ip$*:1720

1 0

[OT] New chan_h323 now Asterisk will not load
by Mark Best 17 Nov '09

17 Nov '09

First off sorry if this is a bit off topic. I've changed the Asterisk code from BOOL to PBoolean and chan_h323 compiles, but now Asterisk 1.6.0.17 crashes when I attempt to start it. There is no /var/log/asterisk/full log to check. I moved the chan_h323.so out of the /usr/lib/asterisk/modules/ folder, but it's still crashes. Anyone have any experience with this sort of thing? Does a different version of 1.6/1.4 work better than another?

1 0

OpenMCU 2.2.5 BUG?
by leandro.alvares＠caixa.gov.br 17 Nov '09

17 Nov '09

Hi, I'm getting a green screen at openmcu 2.2.5. It doesn't happen when I'm using 2.2.3 version. Any suggestion will be appreciated. Thanks. Regards, Leandro

1 0

H264 Plugin in H323plus
by ooi khai chin 17 Nov '09

17 Nov '09

Hi All, currently, I had been compiled the h264plugin from opal project, together with libx264,avcodec and any stuff to make it work. when, I do a conference on both side using my own codec in MyPhone2, It work fined. The problem occur when I communicate with other voip software like polycom, VCON... In the polycom(PVX 8.0.2) media statistic, it show both side info as below: People Tx People Rx ------------------------------------------------------- Video Protocol: H.264 H.264 Video Rate: 320 320 Video Rate Used: 319 84 Video Frame Rate: 15 0 Video Packet Lost: 0 0 Video jitter: 0 2 Video Format: QVGA ----- Audio Protocol: G.711U G.711A Audio Rate: 64 64 Audio Packets Lost: 0 0 Audio Jitter: 0 0 The frame rate and video format got problem... Do I need to specify video format and video frame rate in H323plus (generic capability), Any Idea??? Thanks.

3 2

Re: [h323plus] ast_h323.h:104: error: 'BOOL' has not been declared
by Mark Best 17 Nov '09

17 Nov '09

First I tried a newer version of Ptlib. It appears Ptlib 2.7 isn't compatible with h323plus 1.21.0. I then tried Ptlib 2.6.6 which compiled with h323plus 1.21.0, but Asterisk still gave the 'BOOL' make error. I then moved forward to finding and replacing in the Asterisk code. Globally replacing the code didn't work, but finding and replacing just 'channels/h323/ast_h323.cxx' & 'channels/h323/ast_h323.h' seemed to do the trick. [root@localhost asterisk]# ldd /usr/lib/asterisk/modules/chan_h323.so libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00002ab1fd5db000) libm.so.6 => /lib64/libm.so.6 (0x00002ab1fd8db000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00002ab1fdb5e000) libpthread.so.0 => /lib64/libpthread.so.0 (0x00002ab1fdd6d000) libc.so.6 => /lib64/libc.so.6 (0x00002ab1fdf88000) /lib64/ld-linux-x86-64.so.2 (0x00000039bf200000) J From: Simon Horne [mailto:s.horne@packetizer.com] Sent: Monday, November 16, 2009 01:26 PM To: Mark Best Subject: RE: [h323plus] ast_h323.h:104: error: 'BOOL' has not been declared Mark do a global replace of BOOL with PBoolean. Simon ________________________________ From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Mark Best Sent: Tuesday, 17 November 2009 6:30 AM To: h323plus(a)lists.packetizer.com Subject: [h323plus] ast_h323.h:104: error: 'BOOL' has not been declared I'm trying to compile chan_h323 for Asterisk, I only get an error when I start the make on Asterisk. Can someone shed some light on this issue? (CentOS 5.4 x64) Here are my notes: yum -y install ncurses ncurses-devel openssl openssl-devel zlib zlib-devel bison bison-devel glibc gcc kernel-devel flex yum install gcc-c++ cd /usr/src wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-1.6.0.17.t ar.gz wget http://www.h323plus.org/source/download/h323plus-v1_21_0.tar.gz wget http://www.h323plus.org/source/download/ptlib-2.4.5.tar.bz2 tar zxvf asterisk-1.6.0.17.tar.gz mv asterisk-1.6.0.17/ ~/asterisk tar zxvf h323plus-v1_21_0.tar.gz bzip2 -cd ptlib-2.4.5.tar.bz2 | tar xvf - mv h323plus ~/h323plus mv ptlib-2.4.5 ~/ptlib export PTLIBDIR=$HOME/ptlib export OPENH323DIR=$HOME/h323plus export LD_LIBRARY_PATH=$OPENH323DIR/lib:$PTLIBDIR/lib cd $PTLIBDIR ./configure --prefix=/usr make make install cd $OPENH323DIR chmod +x configure ./configure --prefix=/usr make make opt cd lib cp libh323_linux_x86_64_.so.1.21-beta0 libh323_linux_x86_64_.so.1.21.0 cd .. make install cd ~/asterisk ./configure --prefix=/usr make menuselect [*] chan_h323 make [CC] chan_agent.c -> chan_agent.o [LD] chan_agent.o -> chan_agent.so [CC] chan_h323.c -> chan_h323.o ast_h323.h:104: error: 'BOOL' has not been declared ast_h323.h:156: error: 'BOOL' does not name a type ast_h323.h:157: error: 'BOOL' does not name a type ast_h323.h:159: error: 'BOOL' does not name a type ast_h323.cxx:2102: error: prototype for 'void MyH323Connection::MyHoldCall(PBoolean)' does not match any in class 'MyH323Connection' ast_h323.h:104: error: candidate is: void MyH323Connection::MyHoldCall(int) ast_h323.cxx:2370: error: 'BOOL' does not name a type ast_h323.cxx:2376: error: 'BOOL' does not name a type ast_h323.cxx:2387: error: 'BOOL' does not name a type make[2]: *** [ast_h323.o] Error 1 make[1]: *** [h323/libchanh323.a] Error 2 make: *** [channels] Error 2

1 0

ast_h323.h:104: error: 'BOOL' has not been declared
by Mark Best 16 Nov '09

16 Nov '09

I'm trying to compile chan_h323 for Asterisk, I only get an error when I start the make on Asterisk. Can someone shed some light on this issue? (CentOS 5.4 x64) Here are my notes: yum -y install ncurses ncurses-devel openssl openssl-devel zlib zlib-devel bison bison-devel glibc gcc kernel-devel flex yum install gcc-c++ cd /usr/src wget http://downloads.asterisk.org/pub/telephony/asterisk/asterisk-1.6.0.17.t ar.gz wget http://www.h323plus.org/source/download/h323plus-v1_21_0.tar.gz wget http://www.h323plus.org/source/download/ptlib-2.4.5.tar.bz2 tar zxvf asterisk-1.6.0.17.tar.gz mv asterisk-1.6.0.17/ ~/asterisk tar zxvf h323plus-v1_21_0.tar.gz bzip2 -cd ptlib-2.4.5.tar.bz2 | tar xvf - mv h323plus ~/h323plus mv ptlib-2.4.5 ~/ptlib export PTLIBDIR=$HOME/ptlib export OPENH323DIR=$HOME/h323plus export LD_LIBRARY_PATH=$OPENH323DIR/lib:$PTLIBDIR/lib cd $PTLIBDIR ./configure --prefix=/usr make make install cd $OPENH323DIR chmod +x configure ./configure --prefix=/usr make make opt cd lib cp libh323_linux_x86_64_.so.1.21-beta0 libh323_linux_x86_64_.so.1.21.0 cd .. make install cd ~/asterisk ./configure --prefix=/usr make menuselect [*] chan_h323 make [CC] chan_agent.c -> chan_agent.o [LD] chan_agent.o -> chan_agent.so [CC] chan_h323.c -> chan_h323.o ast_h323.h:104: error: 'BOOL' has not been declared ast_h323.h:156: error: 'BOOL' does not name a type ast_h323.h:157: error: 'BOOL' does not name a type ast_h323.h:159: error: 'BOOL' does not name a type ast_h323.cxx:2102: error: prototype for 'void MyH323Connection::MyHoldCall(PBoolean)' does not match any in class 'MyH323Connection' ast_h323.h:104: error: candidate is: void MyH323Connection::MyHoldCall(int) ast_h323.cxx:2370: error: 'BOOL' does not name a type ast_h323.cxx:2376: error: 'BOOL' does not name a type ast_h323.cxx:2387: error: 'BOOL' does not name a type make[2]: *** [ast_h323.o] Error 1 make[1]: *** [h323/libchanh323.a] Error 2 make: *** [channels] Error 2

1 0