- h323plus - lists.packetizer.com

[Fwd: Re: Silk codec support]
by Łukasz Czekierda 17 Mar '11

17 Mar '11

Dear Simon, Robert and all H323Plus Team, Thanks for your very fast answer. I have successfully built ptlib, h323plus (1.22) with silk codec and simple. I put silk_ptplugin.dll, iLBC_ptplugin.dll and gsm0610_ptplugin.dll into c:\pwlib_plugins (then also to c:\ptlib_plugins). Simple runs OK on XP and Windows 7, quality of G.711 and iLBC (both 13k and 15k) is good, but neither gsm nor silk work. There are some static, MOS is about 1... Additionally, simple app logs SKP_Silk_Encode returned -4 every few seconds. Am I doing anything wrong? Regards, Łukasz -------- Wiadomość oryginalna -------- Robert I have checked the code into the h323plus CVS. There is no official ITU Generic identifier yet so it is using a Packetizer Identifer for the moment. You can contact me offlist to discuss. Simon -----Original Message----- From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Robert Jongbloed Sent: Wednesday, January 12, 2011 9:26 AM To: h323plus(a)lists.packetizer.com Subject: Re: [h323plus] Silk codec support I added SILK to OPAL a couple of months back. Unfortunately it was SIP only as I did not know what the H.245 encoding is for SILK, if any. Now that I see there is at least a proposed standard, this should be able to be finished in a few minutes. It would be really nice if the two systems could use the same code for this. Robert Jongbloed OPAL/OpenH323/PTLib Architect and Co-founder. > -----Original Message----- > From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus- > bounces(a)lists.packetizer.com] On Behalf Of Simon Horne > Sent: Tuesday, 11 January 2011 9:32 PM > To: 'Łukasz Czekierda' > Cc: h323plus(a)lists.packetizer.com > Subject: Re: [h323plus] Silk codec support > > Lukasz > > The issue is there is no definition of Silk in H.323 > > I wrote a submission to the ITU at the last meeting for inclusion > http://wftp3.itu.int/av-arch/avc-site/2009-2012/1011_Res/AVD-3994.zip > > The stumbling block is that SILK has defined dynamic payloads for each > bitrate for interop with Skype. In H.323 you cannot tell the remote > what payload to send, the remote will tell you want it will send. This > becomes an > issue if you are bridging to skype. There is a work around (submitted > by Avaya for a different issue but same meeting) to include in the > OLCack the payload that you expect the remote to send you. > > I have a development H.323 silk plugin (8k and 16k bitrate) and I will > commit them after the next stable release as it requires audio > capability merging which needs to be committed. The idea is there is 1 > silk capability > for the different bitrates (rather than a capability for each bitrate) > and you negotiate the actual bitrate by merging your local caps with > the caps in > the TCS. > > Simon > > > -----Original Message----- > From: h323plus-bounces(a)lists.packetizer.com > [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Lukasz Czekierda > Sent: Tuesday, January 11, 2011 7:42 PM > To: h323plus(a)lists.packetizer.com > Subject: [h323plus] Silk codec support > > Dear H.323Plus team, > > I have a question regarding support for skype's silk codec. Do you > plan to support it soon? Maybe you have already started development/integration? Do > you expect any obstacles? > > Best regards, > Łukasz Czekierda

2 2

Dropped H323 packets
by Dennis Muhlestein 16 Mar '11

16 Mar '11

I've been battling for some time go get all my call flows working with H323. A constantly re-appearing issue is that the kernel is dropping packets for part of the H323 protocol. The offending code is in nf_conntrack_h323_main.c I'll make one call, and the call will work, but the next the kernel will drop packets. I've worked around a number of these issues, but this one is stumping me currently. Call flow: Call a hold server through a gatekeeper (H.460.18/19 because we're NATted) Hold server transfers to another machine and call is completed. Problem: 1st call works. At transfer, Facility message is sent from hold server back to gatekeeper, gatekeeper forwards to phone. phone computer adds IP address of target phone even though that call is placed through a gatekeeper. Expect table has ip addresses of target phone and gatekeeper. 2nd call phone drops facility packet at transfer and call fails. Kernel message (I added a couple debugging messages just to be sure) <7>[ 312.181335] nf_ct_q931: process_q931 facility. <7>[ 312.181579] nf_ct_q931: Facility <4>[ 312.181915] nf_ct_q931: packet dropped <0>[ 312.182037] nf_ct_Q.931: dropping packetIN=eth0 OUT= MAC=38:e7:d8:7a:20:99:00:0b:86:42:1b:40:08:00:45:00:00:8b:3b:e1:40:00:3d:06:54:c4:0a:14:91:10:0a:14:07:90:06:b8:d1:a1:23:92:8b:34:1c:c5:d6:c4:80:18:00:fb:7b:9e:00:00:01:01:08:0a:1e:30:fe:d0:ff:ff:ff:b2:03:00:00:57:08:02:e0:b0:62:1c:00:7e:00:49:05:26:d0:06:00:08:91:4a:00:04:00:0a:14:91 SRC=10.20.145.16 DST=10.20.7.144 LEN=139 TOS=0x00 PREC=0x00 TTL=61 ID=15329 DF PROTO=TCP SPT=1720 DPT=53665 SEQ=596806452 ACK=482727620 WINDOW=251 RES=0x00 ACK PSH URGP=0 OPT (0101080A1E30FED0FFFFFFB2) Attached network trace 65.37.255.198 is the hold server. 10.20.145.16 is my test gatekeeper. 10.20.7.144 is my test phone. Here is what the expect table looks like after the 1st call: 235 l3proto = 2 proto=17 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=5024 235 l3proto = 2 proto=17 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=5025 229 l3proto = 2 proto=17 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=5023 229 l3proto = 2 proto=17 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=5022 229 l3proto = 2 proto=17 src=10.20.7.144 dst=10.20.145.16 sport=0 dport=6769 215 l3proto = 2 proto=6 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=1720 PERMANENT 234 l3proto = 2 proto=6 src=10.20.7.144 dst=10.20.145.16 sport=0 dport=1720 PERMANENT 235 l3proto = 2 proto=17 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=5027 234 l3proto = 2 proto=6 src=10.20.7.144 dst=10.20.145.12 sport=0 dport=1720 235 l3proto = 2 proto=17 src=10.20.145.16 dst=10.20.7.144 sport=0 dport=5026 The 2nd to bottom line I believe is the offending line. Perhaps h323 conntrack doesn't know about gatekeepers, or perhaps we could do something else to avoid this, but so far I haven't found a solution. Any thoughts? Bug? Kernel 2.6.32.17. Unfortunately, I don't have control over the target platform and this module will be used so I'm trying to find some way around this on the software side. Perhaps there is a way to send a fake packet that will clear the entry or something. I'm wondering if I can do anything on the h323 side in terms of PDUs I send that might persuade the kernel to drop the entry from the expect table. Thanks Dennis

2 3

problem with release build of latest h323plus with suggested ptlib
by Vladimir Fekete 02 Mar '11

02 Mar '11

Hello all, when I tried to build (windows 7, visual studio 2010, x86) last h323plus - 1.22.0 01/11/2011; against suggested ptlib - 2.8.3 23/12/2010; (both taken from the h323plus page) I've got an error in h323plus "release" build 1>src\h323pluginmgr.cxx(2114): error C2039: 'FlowControl' : is not a member of 'PVideoChannel' 1> C:\work\kitchen\ptlib\include\ptlib/video.h(53) : see declaration of 'PVideoChannel' and it is true, FlowControl really is not a member of PVideoChannel in ptlib 2.8.3 (I used to compile h323plus against higher versions of ptlib (such as 2.10.0) so I did not noticed this before. I also have not found any note about this in mailing list. Does anybody ran into same problem ? Best regards, Vladimir Fekete P.S. I'm testing different versions of ptlib/opal/h323plus because I'm trying to find release code of h323's h.264 video codec which would run with opal without problems

2 1

RTP Packet Issue
by kc ooi 02 Mar '11

02 Mar '11

Dear H323plus Team members, Recently, I have found some issue when I am doing H.323 testing with polycom system (eg. PVX 8.0.2) and checked the packet traffic using wireshark. I use RTP stream analysis of wireshark for viewing the result, and I notice that every packet(which is final slice of a frame, contain Marker=1) has a status of "Incorrect timestamp". 1. Why it behave like this? 2. Does it affect the receiving site during a conference meeting? 3. Is there any timeout for RTP packet handling(like dropping packet) in h323plus? Because I found out that it cause large packet loss during the conference compare to other h.323 system on the same situation(ie. same executing environment). Btw, I have done some enhancement on MyOutput display according to the suggestion of "Simon" to one of the h323 member, to avoid dropping packet. Thanks.

3 8

Re: [h323plus] ZRTP/SRTP enabling in OPAL/H323PLUS
by Simon Horne 02 Mar '11

02 Mar '11

H323plus has a H.235 factory loader and plugin features for H.235 which it shares with GnuGk. Currently baseline support and H.235.1 (Gatekeeper registration) are implemented. No media encryption yet. H.235.6 is to come. Simon From: Opal Developer [mailto:rdk.opaldev@gmail.com] Sent: 02 March 2011 08:35 To: Simon Horne Subject: Re: [h323plus] ZRTP/SRTP enabling in OPAL/H323PLUS Hi Simon, Thank you for the reply. Does the H323plus library have any sort of security built in. I see there are H325 files in the H323 project source files. Are these enabled? Thank you for your time. On Tue, Mar 1, 2011 at 12:44 PM, Simon Horne <s.horne(a)packetizer.com> wrote: Raghudeep Currently there is no intention to support ZRTP in H323plus. The industry adopted standard H.235.6 I hope to introduce in the coming months. SRTP (H.235.8) may come later. Simon From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com] On Behalf Of Opal Developer Sent: 02 March 2011 06:20 To: h323plus(a)lists.packetizer.com; opalvoip-devel(a)lists.sourceforge.net Subject: [h323plus] ZRTP/SRTP enabling in OPAL/H323PLUS Hi All. Has anyone succedded in enabling SRTP/ZRTP in OPAL/H323plus? It seems to be disabled in OPAL currently. Can you please share thoughts? I am using the Sirius release on Windows OS and Visial Studio. Any help is greatly appreciated. Thanks and regards, Raghudeep

1 0

ZRTP/SRTP enabling in OPAL/H323PLUS
by Opal Developer 01 Mar '11

01 Mar '11

Hi All. Has anyone succedded in enabling SRTP/ZRTP in OPAL/H323plus? It seems to be disabled in OPAL currently. Can you please share thoughts? I am using the Sirius release on Windows OS and Visial Studio. Any help is greatly appreciated. Thanks and regards, Raghudeep

2 1

"possible" bug in H323plus video codec for h.264
by Vladimir Fekete 25 Feb '11

25 Feb '11

Hello all, I've been playing with h.264-x264 plugin for a while and since I had no problems between h323plus vs h323plus nor OpenPhone 3.8.3 application I do have problems with video codec h.264 for h323 from recent h323 plus (e.g. version 1.22.0, 01/11/2011) and application based on recent opal (rev. 25192) I say "possible" because - as was said from few recent mails on mailing lists, opal and h323+ have similar root but they don't share plugins (necessarily). Nevertheless, when I tried to make a connection from OPAL application to h323+ based application, where both used h264-x264 plugin from h323plus video codecs (v. 1.22.0), my opal application crashed. I traced down the problem and fixed the lines in h264-x264.cxx and now it works for me. Problem was following : during the codec options set stage a method of OpalPluginMediaFormatInternal class is called. This one (opalpluginmgr.cxx) bool OpalPluginMediaFormatInternal::AdjustOptions(OpalMediaFormatInternal & fmt, OpalPluginControl & control) const call was made from void H323Capabilities::BuildPDU(const H323Connection & connection, H245_TerminalCapabilitySet & pdu) const line n.2706 (capability.GetWritableMediaFormat().ToCustomisedOptions();) in h323caps.cxx in method AdjustOptions there are 2 variables set inside : char ** input = fmt.GetOptions().ToCharArray(false); char ** output = input; and yes there are set *correctly* they are immediately followed by this line (in my case line n. 477 in opalpluginmgr.cxx) bool ok = control.Call(&output, sizeof(output)) != 0; which calls (opalpluginmgr.h) int OpalPluginControl::Call(void * parm, unsigned parmLen, void * context = NULL) const and that one calls int OpalPluginControl::Call(void * parm, unsigned * parmLen, void * context = NULL) const (these 2 methods are not same, difference is in the second parameter, one is not a pointer other is) and this second Call(..) calls to_customised_options from h264_x264.cxx static int to_customised_options(const struct PluginCodec_Definition * codec, void * _context, const char *, void * parm, unsigned * parmLen) and there is a line (in my case 837) const char ** option = (const char **)parm; and here is the problem. if you look at the chain : AdjustOptions > Call > the "other" Call > to_customised_options then you see that the output variable is transfered as : AdjustOptions &output char*** Call parm void * Call parm void * to_customised_options parm void* so in the end, parm is char *** and not char ** and this caused the crash How I fixed it changed "to_custoimized_options", file h323plus/plugins/video/H.264/h264-x264.cxx, line number 837 const char ** option = (const char **)parm; to const char ** option = *((const char ***)parm); and also (same function, same file, line 858) char ** options = (char **)parm; to char ** options = *((char ***)parm); recompiled h264 plugin and it works. Best regards, Vladimir Fekete P.S. I don't want to call it a bug because I'm not sure whether it's valid to mix h323plus codecs with opal (eg. separately they may work ok).

2 1

Re: [h323plus] [Opalvoip-devel] error H.263
by Simon Horne 25 Feb '11

25 Feb '11

Craig I missed this...Wow! Sorry I must of missed typed. Sorry openh323. H323plus uses much of the same code base and front end api ie H323EndPoint::OpenVideoChannel (which was the context of the comment) etc as openh323. Existing OpenH323 applications like YATE and GnuGk still work with h323plus. Opal interface has evolved differently over time. It is true h323plus plugin video api has its roots in Opal which were ported over a few years ago. For sometime after that the api's were identical which I helped maintain but things deviated over time. It happens. There was no malice or inference intended. Don't think for one minute I'm claiming anything over anything. In 2007 a decision was made that forced a split in the develop paths (and ultimate demise) of OpenH323. A group of developers went a different path and few chose another direction. We all come from the same origins. OpenH323... Sorry Craig if there was any claim or inference it was not intended. You kept OpenH323 alive for many years and both communities should be very thankful of the tremendous effort you put in sometimes in the most difficult of circumstances I'm certainly am sorry for my poor judgment in wording offended. Simon -----Original Message----- From: Craig Southeren [mailto:craigs@postincrement.com] Sent: 24 February 2011 13:05 To: Simon Horne Cc: 'Jan Willamowius'; opalvoip-devel(a)lists.sourceforge.net; h323plus(a)lists.packetizer.com Subject: Re: [Opalvoip-devel] error H.263 On 22/02/2011 8:38 PM, Simon Horne wrote: ..deleted > The architecture of Opal has deviated a lot from its h323plus roots ..deleted As Simon knows full well, Opal has no roots in H323plus. Opal and H323Plus both derive from OpenH323. Any claims to the contrary are a mistake or flamebait. On the subject of video plugins, Opal had video plugins before either OpenH323 or H323Plus. I know this because I wrote the code in Opal to support a customer who paid for it. The H323Plus developers chose to make their video plugins similar to Opal, but not the same. I imagine this is because they chose their own development path from the original OpenH323 code base, rather deriving from the already extant Opal design. In any case, the video codec plugin work in H323Plus appeared after the corresponding Opal code had already been deployed, so any claim that Opal was derived from H323Plus even in this specific area are not supported by the evidence. Craig -- ----------------------------------------------------------------------- Craig Southeren Post Increment - VoIP Consulting and Software craigs(a)postincrement.com.au www.postincrement.com.au Phone: +61 243654666 ICQ: #86852844 Fax: +61 243656905 MSN: craig_southeren(a)hotmail.com Mobile: +61 417231046 Jabber: craigs(a)jabber.org "Science is the poetry of reality." Richard Dawkins

1 0

Unable to connect more than one client
by Jérémy Subtil 24 Feb '11

24 Feb '11

Hi there, I compiled openmcu 2.2.5 on Computer A, along with ptlib 2.8.3 and h323plus 1.22. The server starts fine with all the expected codecs, and the output is the following: #openmcu -cd 2011/02/23 15:19:54.998 OpenMCU Message Starting service process "OpenMCU" v2.2.5 - error = 20 Daemon started with pid 2026 2011/02/23 15:19:55.006 H323 Listener:bebd6700 Info H323 Awaiting TCP connections on port 1720 2011/02/23 15:19:55.013 OpenMCU Info MCU Codecs (in preference order): Table: G.711-ALaw-64k <1> G.711-uLaw-64k <2> G.722.1-24k{sw} <3> G.722.1-32k{sw} <4> G.726-16k{sw} <5> G.726-24k{sw} <6> G.726-32k{sw} <7> G.726-40k{sw} <8> GSM-06.10{sw} <9> GSM-AMR{sw} <10> LPC-10{sw} <11> MS-GSM{sw} <12> MS-IMA-ADPCM{sw} <13> SpeexIETFNarrow-11k{sw} <14> SpeexIETFNarrow-15k{sw} <15> SpeexIETFNarrow-18.2k{sw} <16> SpeexIETFNarrow-24.6k{sw} <17> SpeexIETFNarrow-5.95k{sw} <18> SpeexIETFNarrow-8k{sw} <19> SpeexIETFWide-20.6k{sw} <20> SpeexWNarrow-8k{sw} <21> SpeexWide-20.6k{sw} <22> iLBC-13k3{sw} <23> iLBC-15k2{sw} <24> iLBC{sw} <25> H.261-CIF{sw} <26> H.263-CIF{sw} <30> H.239 Control <33> UserInput/hookflash <27> UserInput/basicString <28> UserInput/dtmf <29> UserInput/RFC2833 <31> UserInput/Navigation <32> UserInput/Softkey <34> UserInput/PointDevice <35> UserInput/Modal <36> Set: 0: 0: G.711-ALaw-64k <1> G.711-uLaw-64k <2> G.722.1-24k{sw} <3> G.722.1-32k{sw} <4> G.726-16k{sw} <5> G.726-24k{sw} <6> G.726-32k{sw} <7> G.726-40k{sw} <8> GSM-06.10{sw} <9> GSM-AMR{sw} <10> LPC-10{sw} <11> MS-GSM{sw} <12> MS-IMA-ADPCM{sw} <13> SpeexIETFNarrow-11k{sw} <14> SpeexIETFNarrow-15k{sw} <15> SpeexIETFNarrow-18.2k{sw} <16> SpeexIETFNarrow-24.6k{sw} <17> SpeexIETFNarrow-5.95k{sw} <18> SpeexIETFNarrow-8k{sw} <19> SpeexIETFWide-20.6k{sw} <20> SpeexWNarrow-8k{sw} <21> SpeexWide-20.6k{sw} <22> iLBC-13k3{sw} <23> iLBC-15k2{sw} <24> iLBC{sw} <25> 1: H.261-CIF{sw} <26> H.263-CIF{sw} <30> 2: H.239 Control <33> UserInput/hookflash <27> UserInput/basicString <28> UserInput/dtmf <29> UserInput/RFC2833 <31> UserInput/Navigation <32> UserInput/Softkey <34> UserInput/PointDevice <35> UserInput/Modal <36> 2011/02/23 15:19:55.015 OpenMCU Info Opened master socket for HTTP: 1420 2011/02/23 15:19:55.015 OpenMCU Info Service OpenMCU Started Computer B can connect successfully with Ekiga 3 as client: 2011/02/23 15:22:34.241 H323 Listener:bebd6700 Info H323TCP Started connection: host=10.1.9.153:30000, if=10.1.9.152:1720, handle=18 2011/02/23 15:22:34.274 H225 Answer:beb54700 Info H225 Set remote application name: " 3.2.7 (OPAL v3.6.8) 9/61" 2011/02/23 15:22:34.305 H225 Answer:beb54700 Info H323 CreateLogicalChannel - unknown data type 2011/02/23 15:22:34.305 H225 Answer:beb54700 Info H323 CreateLogicalChannel - unknown data type 2011/02/23 15:22:34.306 H225 Answer:beb54700 Info RTP_UDP Session 1 created: 10.1.9.152:5000-5001 ssrc=3028627343 2011/02/23 15:22:34.306 H225 Answer:beb54700 Info RTP Adding session RTP_UDP 2011/02/23 15:22:34.306 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 108 - error = 107 2011/02/23 15:22:34.307 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 108 - error = 107 2011/02/23 15:22:34.308 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 110 - error = 107 2011/02/23 15:22:34.308 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 110 - error = 107 2011/02/23 15:22:34.309 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 119 - error = 107 2011/02/23 15:22:34.310 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 119 - error = 107 2011/02/23 15:22:34.310 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 118 - error = 107 2011/02/23 15:22:34.310 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 118 - error = 107 2011/02/23 15:22:34.311 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 117 - error = 107 2011/02/23 15:22:34.311 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 117 - error = 107 2011/02/23 15:22:34.311 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 116 - error = 107 2011/02/23 15:22:34.312 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 116 - error = 107 2011/02/23 15:22:34.313 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 115 - error = 107 2011/02/23 15:22:34.313 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 115 - error = 107 2011/02/23 15:22:34.314 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 103 - error = 107 2011/02/23 15:22:34.314 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 103 - error = 107 2011/02/23 15:22:34.314 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 109 - error = 107 2011/02/23 15:22:34.315 H225 Answer:beb54700 Warning H323RTP Setting dynamic RTP payload type: 109 - error = 107 2011/02/23 15:22:34.316 H225 Answer:beb54700 Info RTP_UDP Session 2 created: 10.1.9.152:5002-5003 ssrc=2730609199 2011/02/23 15:22:34.316 H225 Answer:beb54700 Info RTP Adding session RTP_UDP 2011/02/23 15:22:34.326 H225 Answer:beb54700 Info H323 Available bandwidth exceeded 2011/02/23 15:22:34.326 H225 Answer:beb54700 Info H323 OnReceivedPDU gave error 7 2011/02/23 15:22:34.326 H225 Answer:beb54700 Info RTP Releasing session 2 2011/02/23 15:22:34.328 H225 Answer:beb54700 Info H323 Available bandwidth exceeded 2011/02/23 15:22:34.328 H225 Answer:beb54700 Info H323 OnReceivedPDU gave error 7 2011/02/23 15:22:34.328 H225 Answer:beb54700 Info RTP Releasing session 2 2011/02/23 15:22:34.328 H225 Answer:beb54700 Info H323 Answering call: AnswerCallNow 2011/02/23 15:22:34.328 H225 Answer:beb54700 Info H245 Default OnSelectLogicalChannels, FastStartResponse 2011/02/23 15:22:34.328 H225 Answer:beb54700 Info H323 Started sending logical channel: SpeexIETFWide-20.6k{sw} <20> 2011/02/23 15:22:34.329 H225 Answer:beb54700 Info H323 Started receiving logical channel: SpeexIETFWide-20.6k{sw} <20> 2011/02/23 15:22:34.329 LogChanTx:beac7700 Info H323RTP Transmit SpeexIETFWide-20.6k thread started: rate=320 time=20ms size=1*52=52 2011/02/23 15:22:34.329 H225 Answer:beb54700 Info H323 Started sending logical channel: H.261-CIF{sw} <26> 2011/02/23 15:22:34.329 LogChanRx:bea86700 Info H323RTP Receive SpeexIETFWide-20.6k thread started. 2011/02/23 15:22:34.329 LogChanRx:bea86700 Info RTP Jitter buffer created: size=101 delay=800-4000/800 (100ms) obj=0xc34160 2011/02/23 15:22:34.330 LogChanTx:bea45700 Info H323RTP Transmit H.261-CIF thread started: rate=29 time=0ms size=1*2000=2000 2011/02/23 15:22:34.331 LogChanTx:beac7700 Warning Cannot open WAV file /root/entering.wav - error = 2 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info H323 Started receiving logical channel: H.261-CIF{sw} <26> 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.331 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.332 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.333 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.333 H225 Answer:beb54700 Info RTP Releasing session 1 2011/02/23 15:22:34.333 H225 Answer:beb54700 Info RTP Releasing session 2 2011/02/23 15:22:34.333 H225 Answer:beb54700 Info RTP Releasing session 2 2011/02/23 15:22:34.333 LogChanRx:be9c3700 Info H323RTP Receive H.261-CIF thread started. 2011/02/23 15:22:34.341 H225 Answer:beb54700 Info H323 User Input RFC2833 payload type set to [pt=101] 2011/02/23 15:22:34.341 H225 Answer:beb54700 Info H245 MasterSlaveDetermination: local is master 2011/02/23 15:22:34.342 H225 Answer:beb54700 Info H225 Reading PDUs: callRef=3310 2011/02/23 15:22:34.358 RTP Jitter:bea04700 Info RTP First data: ver=2 pt=[pt=108] psz=52 m=1 x=0 seq=1749 ts=0 src=531892144 ccnt=0 2011/02/23 15:22:34.363 LogChanRx:be9c3700 Info RTP First data: ver=2 pt=H261 psz=969 m=1 x=0 seq=54377 ts=0 src=1679710377 ccnt=0 2011/02/23 15:22:34.364 LogChanRx:be9c3700 Info PVidDev SetFrameSize to 176x144 2011/02/23 15:22:34.365 H225 Answer:beb54700 Info H245 TerminalCapabilitySet Sent. 2011/02/23 15:22:36.356 RTP Jitter:bea04700 Info RTP Receive statistics: packets=101 octets=5252 lost=0 tooLate=0 order=0 avgTime=19 maxTime=21 minTime=19 jitter=7129523 maxJitter=33554431 2011/02/23 15:22:38.332 LogChanTx:beac7700 Info RTP Transmit statistics: packets=101 octets=5252 avgTime=40 maxTime=42 minTime=38 2011/02/23 15:22:38.356 RTP Jitter:bea04700 Info RTP Receive statistics: packets=201 octets=10452 lost=0 tooLate=0 order=0 avgTime=20 maxTime=21 minTime=19 jitter=11225 maxJitter=33554431 2011/02/23 15:22:40.354 RTP Jitter:bea04700 Info RTP Receive statistics: packets=301 octets=15652 lost=0 tooLate=0 order=0 avgTime=19 maxTime=21 minTime=19 jitter=17 maxJitter=33554431 2011/02/23 15:22:42.332 LogChanTx:beac7700 Info RTP Transmit statistics: packets=201 octets=10452 avgTime=40 maxTime=42 minTime=38 2011/02/23 15:22:42.354 RTP Jitter:bea04700 Info RTP Receive statistics: packets=401 octets=20852 lost=0 tooLate=0 order=0 avgTime=19 maxTime=21 minTime=19 jitter=0 maxJitter=33554431 2011/02/23 15:22:44.353 RTP Jitter:bea04700 Info RTP Receive statistics: packets=501 octets=26052 lost=0 tooLate=0 order=0 avgTime=20 maxTime=22 minTime=17 jitter=265213 maxJitter=33554431 … However, when I try to connect Computer C with Ekiga 3 as well, it fails and openmcu gets a strange beahior: endless log messages even when all clients are disconnected, unable to connect a single client again, unable to access the web interface anymore. The only thing I can do is to kill the daemon. Here is the log I get: 2011/02/23 15:23:26.932 H323 Listener:bebd6700 Info H323TCP Started connection: host=10.1.8.76:30000, if=10.1.9.152:1720, handle=35 2011/02/23 15:23:26.996 H225 Answer:be982700 Info H225 Set remote application name: " 3.2.7 (OPAL v3.6.8) 9/61" 2011/02/23 15:23:26.997 H225 Answer:be982700 Info H323 CreateLogicalChannel - unknown data type 2011/02/23 15:23:26.997 H225 Answer:be982700 Info H323 CreateLogicalChannel - unknown data type 2011/02/23 15:23:26.997 H225 Answer:be982700 Info RTP_UDP Session 1 created: 10.1.9.152:5004-5005 ssrc=529535172 2011/02/23 15:23:26.997 H225 Answer:be982700 Info RTP Adding session RTP_UDP 2011/02/23 15:23:26.998 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 111 - error = 22 2011/02/23 15:23:26.998 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 111 - error = 22 2011/02/23 15:23:26.999 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 113 - error = 22 2011/02/23 15:23:26.999 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 113 - error = 22 2011/02/23 15:23:27.001 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 119 - error = 22 2011/02/23 15:23:27.001 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 119 - error = 22 2011/02/23 15:23:27.001 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 118 - error = 22 2011/02/23 15:23:27.002 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 118 - error = 22 2011/02/23 15:23:27.003 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 117 - error = 22 2011/02/23 15:23:27.004 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 117 - error = 22 2011/02/23 15:23:27.005 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 116 - error = 22 2011/02/23 15:23:27.005 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 116 - error = 22 2011/02/23 15:23:27.006 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 99 - error = 22 2011/02/23 15:23:27.007 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 99 - error = 22 2011/02/23 15:23:27.007 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 106 - error = 22 2011/02/23 15:23:27.007 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 106 - error = 22 2011/02/23 15:23:27.008 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 112 - error = 22 2011/02/23 15:23:27.008 H225 Answer:be982700 Warning H323RTP Setting dynamic RTP payload type: 112 - error = 22 2011/02/23 15:23:27.009 H225 Answer:be982700 Info RTP_UDP Session 2 created: 10.1.9.152:5006-5007 ssrc=2416178601 2011/02/23 15:23:27.009 H225 Answer:be982700 Info RTP Adding session RTP_UDP 2011/02/23 15:23:27.018 H225 Answer:be982700 Info H323 Available bandwidth exceeded 2011/02/23 15:23:27.019 H225 Answer:be982700 Info H323 OnReceivedPDU gave error 7 2011/02/23 15:23:27.019 H225 Answer:be982700 Info RTP Releasing session 2 2011/02/23 15:23:27.020 H225 Answer:be982700 Info H323 Available bandwidth exceeded 2011/02/23 15:23:27.020 H225 Answer:be982700 Info H323 OnReceivedPDU gave error 7 2011/02/23 15:23:27.020 H225 Answer:be982700 Info RTP Releasing session 2 2011/02/23 15:23:27.021 H225 Answer:be982700 Info H323 Answering call: AnswerCallNow 2011/02/23 15:23:27.021 H225 Answer:be982700 Info H245 Default OnSelectLogicalChannels, FastStartResponse 2011/02/23 15:23:27.021 H225 Answer:be982700 Info H323 Started sending logical channel: SpeexIETFWide-20.6k{sw} <20> 2011/02/23 15:23:27.021 H225 Answer:be982700 Info H323 Started receiving logical channel: SpeexIETFWide-20.6k{sw} <20> 2011/02/23 15:23:27.021 LogChanTx:be941700 Info H323RTP Transmit SpeexIETFWide-20.6k thread started: rate=320 time=20ms size=1*52=52 2011/02/23 15:23:27.021 H225 Answer:be982700 Info H323 Started sending logical channel: H.261-CIF{sw} <26> 2011/02/23 15:23:27.022 LogChanRx:be900700 Info H323RTP Receive SpeexIETFWide-20.6k thread started. 2011/02/23 15:23:27.022 LogChanRx:be900700 Info RTP Jitter buffer created: size=101 delay=800-4000/800 (100ms) obj=0xc34310 2011/02/23 15:23:27.023 LogChanTx:be8bf700 Info H323RTP Transmit H.261-CIF thread started: rate=29 time=0ms size=1*2000=2000 2011/02/23 15:23:28.332 RTP Jitter:bea04700 Info RTP Receive statistics: packets=2701 octets=140452 lost=0 tooLate=0 order=0 avgTime=20 maxTime=22 minTime=17 jitter=3 maxJitter=33554431 2011/02/23 15:23:28.812 RTP Jitter:bea04700 Info RTP Jitter buffer full, throwing away oldest frame (839680) 2011/02/23 15:23:29.212 RTP Jitter:bea04700 Info RTP Jitter buffer continuously full, throwing away entire buffer. 2011/02/23 15:23:29.232 RTP Jitter:bea04700 Info RTP Jitter buffer full, threw away 21 oldest frames 2011/02/23 15:23:30.331 RTP Jitter:bea04700 Info RTP Receive statistics: packets=2801 octets=145652 lost=0 tooLate=0 order=0 avgTime=19 maxTime=21 minTime=19 jitter=0 maxJitter=33554431 2011/02/23 15:23:31.231 RTP Jitter:bea04700 Info RTP Jitter buffer full, throwing away oldest frame (878400) 2011/02/23 15:23:31.630 RTP Jitter:bea04700 Info RTP Jitter buffer continuously full, throwing away entire buffer. Note that I get the same behavior using other clients, like VidPhone for Windows or a Sony conferencing hardware. In addition, Computers A, B and C are on the same LAN. Do you have any ideas how I can get openmcu working? Cheers, Jeremy Subtil Systems Engineer at Smile http://www.smile.fr/en/

2 2

unavailable H.264 plugin and missing H.263 CIF4/16 capabilities
by Vladimir Fekete 24 Feb '11

24 Feb '11

Hello Simon, few days ago, you told us you confirm, that H.264 works (with h.239) for H323plus project. I was able to compile x264, ffmpeg and the plugin itself, however, when I put it into correct directory with all the dll files, none of the example applications can see it (but they see for example h261vic plugin located in the same directory as h264 plugin). I also tried to use trace (with application 'simple') and I see that capabilities are loaded, but not the H.264. MSVC says for debug version of myphonet, that the symbols from h264 dll were loaded and dll is in use (did not say what symbols). Hence I'd like to ask you - the file plugin-config.h which is located in two directory above H.264 project (as plugin-config.h.in) was changed to proper header file by ./configure command or you changed (created) it by hand ?(for windows) (my suspicion is, that symbols are not properly exported from the dll, but I don't know how to verify it) - are you aware of any reason why properly compiled h.264 dll and helper would not work with recent h323plus and ptlib ? I'm obviously missing something and I really would like to make it run (with h323plus for start and in the end with OPAL) To all, yes, you were right, the H.263 distortions and damage I saw are "problem" of OPAL, since h323plus myphone2 has no problem with it and I can see nice H.263 CIF picture. However, and this is true for opal and h323 plus, I'm unable to use higher resolutions e.g. CIF4, CIF16 and the custom one (capability for it is missing). So I'd like to ask : - is h323plus or OPAL capable of CIF4 and CIF16 with given codec(s) 263/264? (e.g. without necessity to drastically change the code), if so, could you, please, point me to any hint how to make it run (lines of code with comment, anything) - when we can expect OPAL will transform the h.263 and h.264 to it's plugin format ? (I would do it by myself, but first I have to see it running with h323plus, so I get time to look at the plugin format of opal and how to do it - unless some good soul wont outrun me) Many thanks ! Best regards, Vladimir Fekete

2 5