November 2009 - h323plus - lists.packetizer.com

PacPhone 2.3.0 Released
by Simon Horne 30 Nov '09

30 Nov '09

Guys www.pacphone.com PacPhone 2.3.0 has been released. It has been extensively tested with the latest GnuGk release. Special thanks to all the people who tested the pre-Release and provided feedback. Anyone has any questions let me know. Simon

1 0

missing RTP Frames
by Igor Pavlov 27 Nov '09

27 Nov '09

Hello. I missing RTP frames, when connect with my H264 plugin on connection speed greater then approximately 256 kBps. I inserted logging of rtp frames sequencenumber in function RTP_Session::SendReceiveStatus RTP_UDP::ReadDataPDU(RTP_DataFrame & frame); after call SendReceiveStatus status = ReadDataOrControlPDU(*dataSocket, frame, TRUE); and periodicaly I have holes in sequence of numbers. At the same time I have working sniffer, and I see that RTP packet missing in my logs is present in sniffers statistics. I tryed to find the place in h323plus sources where can I miss RTP packets, but couldn't find it :( The missed group of packets (even if length of group is 1 - single packet) always ends with rtp packet which have marker=0 Help me to find out the reason why I missing packets. Because of speed?

1 0

GNU Gatekeeper 2.3.1 released
by Jan Willamowius 26 Nov '09

26 Nov '09

Hi, a new stable version of the GNU Gatekeeper is now available. Source code and executables can be downloaded from http://www.gnugk.org/h323download.html Executables are available for - Linux (32 bit and 64 bit) - Windows (XP, Vista, Windows7, ...) - MacOSX (PPC and Intel) - Solaris 10 - FreeBSD - OpenBSD What's new in 2.3.1 ? - lots of interoperability fixes for H.460.18/.19 based on the feedback from the community - new routing policy "CatchAll" - new [ModeSelection] section to fine tune when to proxy calls - support for setting the proxy mode per call using Radius - support for ignoring case and alias type (calling "FOO" will match alias "foo") - H.460.23/.24 support updated to the now approved standard - many bug fixes, eg. for direct mode and URI dialing - a unified binary for MacOS X that works both on PPC and Intel - Firebird database driver updated - many small improvements in the manual See below for the full list of changes. Enjoy, Jan -- Jan Willamowius, jan(a)willamowius.de http://www.gnugk.org/ http://www.willamowius.de/gnugk-support.html Changes from 2.3.0 to 2.3.1 =========================== - Firebird database driver updated for Firebird 2.0.x and 2.1.x - BUGFIX(Toolkit.cxx) don't ignore ExternalIP settings when NetworkInterfaces= is set - BUGFIX(SoftPBX.cxx) make response messages more consistent - the old format (2.0) to specify neighbor gatekeepers is deprecated now and has been removed from the manual; it still works, but may be removed from future versions - BUGFIX(ProxyChannel.cxx) only close endpoints logical channel on CloseLogicalChannel, use [Proxy]SearchBothSidesOnCLC=1 to retain the old behavior - BUGFIX(Toolkit.cxx) Enable RewritePString to rewrite address correctly if unregistered full URI. - BUGFIX(Neighbor.cxx) srv policy now fails calls and doesn't pass them to the next policy if a SRV record exists for a domain, but doesn't have a destination for the call - allow to set proxy mode through 'proxy' variable in Radius h323-ivr-in attribute (thanks to Yuriy Georgiewskiy) - BUGFIX(Routing.cxx) let dns policy handle LRQs that resolve locally, so URI dialing from neighbors works - the manual has been improved (thanks to Robert Kulagowski) - set Radius VSA attribute h323_rtp_proxy in stop event (thanks to Yuriy Georgiewskiy) - BUGFIX(ProxyChannel.cxx) fix memory leak when creation of a fastStart channel fails - status port command DisconnectIP now also works with unregistered endpoints using the std port - BUGFIX(ProxyChannel.cxx) fix handling of H.460.19 RTP keepalive packets - new switch [Proxy]DisableRTPQueueing=1 - BUGFIX(ProxyChannel.cxx) fully initialize UDP proxy IPs and ports - BUGFIX(Routing.cxx) don't apply dns policy to aliases of type dialedDigits - BUGFIX(Toolkit.h/.cxx) use default IP for networks specified in InternalNetwork=, not ExternalIP - enable data execution protection on Windows versions that support it (starting with XP SP3) - BUGFIX(gk.cxx) make sure Windows service writes same trace format as application (including file and line) - BUGFIX(Neighbor.cxx) fix memory leak in srv policy, only send the local part of the alias in the LRQ - new switch [RoutedMode]H46018NoNat to disable H.460.18 if no NAT detected (default enabled) - new routing policy 'catchall' to route all calls to one alias or IP - new Radius attributes on stop: h323pddtime, h323ringtime, h323routeattempts - BUGFIX(Neighbor.cxx) fix srv policy for direct mode, don't send LRQ if SRV points to us - new switch [RoutedMode]TranslateSorensonSourceInfo=1 to convert the Sorenson VP200 caller information - BUGFIX(GkStatus.cxx) don't flush status port socket when access is denied to avoid blocking - new switches in [Gatekeeper::Main]: CompareAliasType and CompareAliasCase to switch off alias type and case matching - BUGFIX(Routing.cxx) fix dns policy for direct mode - BUGFIX(Neighbor.cxx) try next policy if SRV lookup fails - neighbor type (GnuGk|CiscoGk|ClarentGk|GlonetGk) is now case insensitive - features documented: [AssignedAliases::SQL], [AssignedGatekeepers::SQL] and [GkQoSMonitor::SQL] - BUGFIX(RasTbl.cxx) use rewritten number when decrementing prefix capacity counters, so they match the increment - feature to set a ClientAuthId in SqlAuth that is provided as %{client-auth-id} on all accounting events - new status port command ResetCallCounters - changed ProxyForSameNAT default from 0 to 1 (to avoid media failure uncertainty) - BUGFIX(RasSrv.cxx) IsReachable looks at correct route table. (virtual was ignored) - changed [RoutedMode]EnableH46024= to be consistent with H.460.18 switch - BUGFIX(RasSrv.cxx) RCF messages H.460 features now supported Features not GenericData - BUGFIX(ProxyChannel.cxx) H.460.19 working with Fast Connect - BUGFIX(RasSrv.cxx,ProxyChannel.cxx) Tandberg MXP interoperability fixes - BUGFIX(ProxyChannel.cxx) check capacity on routes supplied by authenticators (Radius, SQL etc.) - BUGFIX(RasSrv.cxx) avoid cutting off status messages after 1000 chars (problem in PString::Printf) - BUGFIX(ProxyChannel.cxx) fix for fastStart with H.460.19 - new switch [RoutedMode]EnableH.460.24=, which defaults to OFF - send RTCP statistics to Radius server (thanks to Yuriy Georgiewskiy) - BUGFIX(Toolkit.cxx) fix a crash in RewriteE164() when casting aliases - new config section [ModeSelection] to specify the routing/proxy mode by IP network

1 0

OpenMCU Codec issues
by Josh Barth 25 Nov '09

25 Nov '09

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

4 9

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

24 Nov '09

Hi All, regarding the H.241 documentation, it mention that H.264 plugin in H.323 only support single NAL mode. Then, I refer the RFC 3984, it state that single NAL mode only support type 1-23 NAL unit, no FU-A, no FU-B, ... Currently, I am using H.264 hardware encoder which used baseline profile, not libx264. My H.264 encoder(hardware) will only return the whole encoded data and it's total length, not each NAL and it's length. So, how can I make it comply to H.323 if no fragmentation is allowed in H.323? Thanks.

2 1

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 17 Nov '09

17 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 16 Nov '09

16 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

H323plus v 1.22 and ptlib 2.6.5
by Sebastian Peschko 13 Nov '09

13 Nov '09

I wonder if someone can help out here. I am having trouble with Asterisk Crashes caused by libpt and openh323 where I am using Asterisk 1.6.2rc5 and h323plus v1.19.0Beta7 and ptlib v1.12.0. In this config when compiling the 2 packages and then doing a make in the asterisk H323 directory it automatically activates the chan_h323 in the Menuselect options of Asterisk and allows me to compile asterisk with h323plus support. The problem I am having is that I am registering with a Nortel H323 GateKeeper and when this looses the registry for some or other reason as a backup I send the calls using a Gateway directly to the Nortel PBX. With this configuration in v1.4.23 it was working perfecttly with openh323 v1.18.0 and pwlib v1.10.3. The problem came when because of issues with openmfcr2 I needed to upgrade to 1.6 for the embedded openr2 support. For this reason I am no trying to compile Asterisk 1.6.2.0rc5 with the latest h323plus v1.22.0 and ptlib 2.6.5. At the moment once these 2 packages are compiled it does not allow me to activate or select chan_h323 in the Asterisk "make menuselect". How can this be activated? I hope someone can help. Sebastian

3 5

H.323v7 and H.460.23/.24 approved by the ITU
by Simon Horne 09 Nov '09

09 Nov '09

Guys Just a quick note. http://www.packetizer.com/ipmc/h323/whatsnew_v7.html It has been nearly 3 years from my first submission to final approval on H.460.23/.24 but finally it's done. H.323 now has a standard complete NAT traversal solution. Simon

2 1

simph323 - could not open sound device
by mattes 06 Nov '09

06 Nov '09

I am trying to get simph323 to work, but I having some trouble w/ the audio. Running h323plus-v1_21_0 with ptlib-2.4.5 on Linux. I run the following command: simph323 -s "HDA Intel" -n h323:192.168.15.163 H323> Could not open sound device HDA Intel - Check permissions or full duplex capability. Could not open sound device HDA Intel - Check permissions or full duplex capability. In call with Kattanekm Could not open sound device HDA Intel - Check permissions or full duplex capability. Could not open sound device HDA Intel - Check permissions or full duplex capability. .... running with trace enabled shows that the sound device is opened properly, but then it fails shortly after 0:04.512 H245:b7e3db90 H245 Default OnSelectLogicalChannels, FastStartDisabled 0:04.512 H245:b7e3db90 H323 FindCapability: G.711-ALaw-64k <1> 0:04.512 H245:b7e3db90 H323 Found capability: G.711-ALaw-64k <4> 0:04.513 H245:b7e3db90 H323 Selecting G.711-ALaw-64k <4> 0:04.513 H245:b7e3db90 H245 Opening channel: T-103 0:04.513 H245:b7e3db90 PWLib File handle low water mark set: 17 PUDPSocket 0:04.514 H245:b7e3db90 RTP_UDP Session 1 created: 192.168.15.153:5002-5003 ssrc=2757625043 0:04.514 H245:b7e3db90 RTP Adding session RTP_UDP 0:04.514 H245:b7e3db90 H323RTP Transmitter created using session 1 0:04.514 H245:b7e3db90 H323RTP OnSendingPDU 0:04.514 H245:b7e3db90 RTP OnSendingPDU 0:04.514 H245:b7e3db90 Codec G711 ALaw encoder created for at 64k, 240 samples 0:04.515 H245:b7e3db90 ALSA Open this=0x0x9627ea8 0:04.517 H245:b7e3db90 Alsa Buffer time is 85312 0:04.517 H245:b7e3db90 Alsa Period time is 85312 0:04.519 H245:b7e3db90 ALSA Device plughw:0 Opened 0:04.519 H245:b7e3db90 Codec Opened sound channel "HDA Intel" for recording at 8000 samples/second using 2x480 byte buffers. 0:04.519 H245:b7e3db90 ALSA setBuffers this=0x0x9627ea8 oshandle=0x9626698 init 1 0:04.519 H245:b7e3db90 psound isOPen basechannel 0x0x9627ea8 pchannel os_handle=-1 0:04.519 H245:b7e3db90 Codec channel 0x0x96243a8 isOpen=0 Could not open sound device HDA Intel - Check permissions or full duplex capability. 0:04.519 H245:b7e3db90 LogChan Transmit thread aborted (open fail) for G.711-ALaw-64k <4> 0:04.519 H245:b7e3db90 H323 OnSelectLogicalChannels, OpenLogicalChannel failed: G.711-ALaw-64k <4> Some debugging later I noticed that H323EndPoint::OpenAudioChannel() calls codec.AttachChannel() [codecs.cxx] and fails in channel->IsOpen(). Looking at ptlib/common/sound.cxx PSoundChannel it is baseChannel->PChannel::IsOpen() which returns FALSE For a quick test I changed the line to baseChannel->IsOpen() which makes it jump that hurdle and simph323 connects with the other h323 end and sound bits are exchanged. Here is the thing that puzzles me! I am using the same version of ptlib with opal (e.g. simpleopal) and don't see this problem. Code is build and run on the same machine. Any thoughts? mat

1 0

Opal H.264 plugin with OpenMCU and H323plus
by Prasad 06 Nov '09

06 Nov '09

Hi, I have taken latest code for ptlib, h323plus, avplugins from h323plus and H.264 plugin from opal. I manged to have video call on OpenMCU with H263. I found it has dependency on specific version of libavcoded, 0.4.7. For H264 I compiled the code and put the .so in $PWLIBPLUGINDIR, also I put libx264 in $LD_LIBRARY_PATH. But somehow H.264 codec is not getting loaded. The libraries are getting linked on start of openmcu but I cant see capabilities being added in OpenMCU traces. Is there any specific version of libx264 needed? I tried with version 78 and 67. Also, H264 requires avcoded too. Is this needed to be built with option --enable-libx264 ? -- Prasad

2 3

h323plus ptlib question
by mattes 06 Nov '09

06 Nov '09

http://www.h323plus.org/source/ mentions PTLib (req) 2.4.5 2009-02-23 Do later version of ptlib work too or is 2.4.5 required? mattes

2 1

Re: [h323plus] RES: Openmcu execution issues
by Sohil Shah 04 Nov '09

04 Nov '09

Hi, The following is my /root/.pwlib_config/openmcu.ini file [Parameters] Username=sohil Password=jU3x80DWeAo= Log Level=3 HTTP Certificate=server.pem HTTP Port=1421 Gatekeeper Mode=No gatekeeper Interface Array Size=0 Enable video=True Video frame rate=15 Video quality=4 Default room=room101 Room time limit=0 Connecting WAV File=/home/sohil/Desktop/opal/connecting.wav Entering WAV File=/home/sohil/Desktop/opal/entering.wav Leaving WAV File=/home/sohil/Desktop/opal/leaving.wav Call log filename=/home/sohil/Desktop/opal/mcu_log.txt Force split screen video=True Disable codecs=No I removed the line _HTTP Certificate=server.pem_ but still I am facing the same problem. Moreover as of now, I've also updated my firefox from 3.5.3 to 3.5.4 What exactly am I supposed to do with that ? -- Thanks& Regards, Sohil Shah On 11/03/2009 09:42 PM, leandro.alvares(a)caixa.gov.br wrote: > Hi, > Did you try to remove the certificate parameter in (by default) > /root/.pwlib_config/.ini or /root/.pwlib_config/openmcu.ini ? > regards, > Leandro. > > ------------------------------------------------------------------------ > *De:* h323plus-bounces(a)lists.packetizer.com > [mailto:h323plus-bounces@lists.packetizer.com] *Em nome de *Sohil Shah > *Enviada em:* terça-feira, 3 de novembro de 2009 13:39 > *Para:* h323plus(a)lists.packetizer.com > *Assunto:* [h323plus] Openmcu execution issues > > Hi, > I've compiled openmcu with all the dependencies. When I > execute openmcu -xc, I get the following error on termimal > > 2009/11/03 20:50:10.777 HTTP Service:b7c00a78 Error > HTTPS Accept failed: error:14094412:SSL > routines:SSL3_READ_BYTES:sslv3 alert bad certificate > 2009/11/03 20:50:10.790 HTTP Service:b7c00a78 Error HTTP > server creation/open failed. > > and I am unable to access https://127.0.0.1/1421 with following error > on browser. > > An error occurred during a connection to 127.0.0.1:1421. > > You have received an invalid certificate. Please contact the server > administrator or email correspondent and give them the following > information: > > Your certificate contains the same serial number as another > certificate issued by the certificate authority. Please get a new > certificate containing a unique serial number. > > (Error code: sec_error_reused_issuer_and_serial) > > Previously I also got some error related to server.pem. I tried to > delete the certificates of openmcu from browser properties but that > also didn't work. I also tried to enable and disable SSL 3.0 and TSL > 1.0 but that also didnt work. I understand that this is some > certification related issue but I'm not able to solve it. > My openmcu version is 2.2.1, Test machine Fedora 11 and Firefox web > browser version 3.5.3. > I hope openmcu issues are addressed on this mailing list. > > Let me know if you need more details. > -- > Thanks& Regards, > Sohil Shah > > > -- > ------------------------------------------------------------------------ > Disclaimer: This e-mail message and all attachments transmitted with > it are intended solely for the use of the addressee and may contain > legally privileged and confidential information. If the reader of this > message is not the intended recipient, or an employee or agent > responsible for delivering this message to the intended recipient, you > are hereby notified that any dissemination, distribution, copying, or > other use of this message or its attachments is strictly prohibited. > If you have received this message in error, please notify the sender > immediately by replying to this message and please delete it from your > computer. Any views expressed in this message are those of the > individual sender unless otherwise stated.Company has taken enough > precautions to prevent the spread of viruses. However the company > accepts no liability for any damage caused by any virus transmitted by > this email. > ------------------------------------------------------------------------ > > > > -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________

2 1

Openmcu execution issues
by Sohil Shah 03 Nov '09

03 Nov '09

Hi, I've compiled openmcu with all the dependencies. When I execute openmcu -xc, I get the following error on termimal 2009/11/03 20:50:10.777 HTTP Service:b7c00a78 Error HTTPS Accept failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate 2009/11/03 20:50:10.790 HTTP Service:b7c00a78 Error HTTP server creation/open failed. and I am unable to access https://127.0.0.1/1421 with following error on browser. An error occurred during a connection to 127.0.0.1:1421. You have received an invalid certificate. Please contact the server administrator or email correspondent and give them the following information: Your certificate contains the same serial number as another certificate issued by the certificate authority. Please get a new certificate containing a unique serial number. (Error code: sec_error_reused_issuer_and_serial) Previously I also got some error related to server.pem. I tried to delete the certificates of openmcu from browser properties but that also didn't work. I also tried to enable and disable SSL 3.0 and TSL 1.0 but that also didnt work. I understand that this is some certification related issue but I'm not able to solve it. My openmcu version is 2.2.1, Test machine Fedora 11 and Firefox web browser version 3.5.3. I hope openmcu issues are addressed on this mailing list. Let me know if you need more details. -- Thanks& Regards, Sohil Shah -- _____________________________________________________________________ Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated.Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email. _____________________________________________________________________

1 0

H.263 and H.264 at OpenMCU. Removing capability. Why?
by HUB Netsky 03 Nov '09

03 Nov '09

Hi, all. I'm trying to set up an MCU server on SLES11 x64 with latest patches. I've grabbed the latest snapshots of ptlib and opal libraries (from http://opalvoip.svn.sourceforge.net) and latest h323plus and OpenMCU (from http://h323plus.cvs.sourceforge.net). After successful compilation with debug flags and a slight modification of Makefiles to repair "make install", I'a able to launch openmcu. But it gives messages like these in the startup log: ============ quote of openmcu startup ============= 2009/11/03 15:00:37.682 OpenMCU Debug2 H323 Found capability: H.261-QCIF{sw} <25> 2009/11/03 15:00:37.683 OpenMCU Debug2 H323 Removing capability: H.261-QCIF{sw} <25> 2009/11/03 15:00:37.684 OpenMCU Debug2 H323 Found capability: H.261{sw} <26> 2009/11/03 15:00:37.684 OpenMCU Debug2 H323 Removing capability: H.261{sw} <26> 2009/11/03 15:00:37.685 OpenMCU Debug2 H323 Found capability: H.263{sw} <27> 2009/11/03 15:00:37.686 OpenMCU Debug2 H323 Removing capability: H.263{sw} <27> 2009/11/03 15:00:37.687 OpenMCU Debug2 H323 Found capability: MPEG4{sw} <28> 2009/11/03 15:00:37.688 OpenMCU Debug2 H323 Removing capability: MPEG4{sw} <28> ============ end of quote of openmcu startup ============= And when the final codec list is printed, it looks like this: ============ quote of openmcu startup ============= 1: H.261-CIF{sw} <24> 2: ============ end of quote of openmcu startup ============= And like the last message shows, OpenMCU doesn't use h263 and MPEG-4 codecs, only H.261 Codecs for H.264 are compiled too and placed just near the other (h261,h263) codecs, but aren't even being noticed by openmcu. I've tried both with h323plus/plugins and opal/plugins by creating symlinks to their ".so" files in "/usr/local/lib/ptlib" directory. The same result, though many audio codecs from opal are being successfully loaded. The questions are: 1. Why openmcu removes capabilities that were successfuly found? 2. Why openmcu doesn't load plugins in the plugin dir? Thanks for any response. Tell me, if any additional info is required. -- HUB

2 1