February 2011 - h323plus - lists.packetizer.com

crash when SessionID=0
by Marek Domaracky 13 Jun '11

13 Jun '11

Hi, I'm working on H.239 implementation and find out that devices might ask SessionID=0 for a new video channel. In particular I did a test with Mirial. I was checking the thread http://lists.packetizer.com/pipermail/h323plus/2009-December/001269.html and it's mentioned that the SessionID=0 is invalid. I know it's not following the standard as for RTPSession the range is from 1..255, but for compatibility, don't you think we should allow it? I did a test call from Mirial to Tandberg and Tandberg didn't have a problem with it. The lines involved are rtp.cxx from PAssert(id > 0 && id < 256, PInvalidParameter); to PAssert(id >= 0 && id < 256, PInvalidParameter); and h323.cxx // We must have a valid sessionID if (sessionID < 1 || sessionID > 255) to if (sessionID < 0 || sessionID > 255) Thanks, Marek

8 18

[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

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

"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

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

23 Feb '11

Robert Older cheaper webcams really behavior quite poorly. For instance 1. They support formats which only can be transformed to RGB24 (and nothing else) in DirectShow filters so then with good webcams you have to filter out and only use the formats that are known to transform to RGB24. (When it all should just work with YUV so there is no need to convert in PTLIB) 2. a couple I have seen supply undersize (or corrupt) image buffer when starting up hence why the directshow output device automatically throws the first few frames away. 3. They fall over when trying to set a video frame size within the camera limits but not exactly as they support. So you are limited to exact sizes. ie like 4CIF. Some webcam may support sizes above 4CIF but not 4CIF exactly (quite common). Some webcams you can adjust the output pin to get the size others the video will just simply fail without any warning. This is why the PVideoInputDevice::GetDeviceCapabilities was introduced so with the plugin you could choose a video size/rate the webcam did support thereby avoiding having to scale/crop etc. Thankfully the latest generation of webcams perform much better like the Microsoft LifeCam Cinema which gives reliable 720p@30 or the new Logitech C910 which provides 1080p@30 (with USB3) with the current DirectShow driver in PTLIB. But still we need to support these older webcams without hardcoding or maintaining a bad list. Simon -----Original Message----- From: Robert Jongbloed [mailto:robertj@voxlucida.com.au] Sent: 23 February 2011 14:33 To: 'Simon Horne'; 'Jan Willamowius'; opalvoip-devel(a)lists.sourceforge.net Cc: h323plus(a)lists.packetizer.com Subject: RE: [Opalvoip-devel] error H.263 Found it. The helper app has bit rate in kbps and OPAL does it in bps. A /1000 fixes the problem. Another question: What are peoples experiences with camera grabber frame rates? My el cheapo USB camera isn't apparently very good. When asked to do 10 fps, actually does 6.4 fps. When asked to do 25 fps, I get about 18 fps. Robert Jongbloed OPAL/OpenH323/PTLib Architect and Co-founder. > -----Original Message----- > From: Simon Horne [mailto:s.horne@packetizer.com] > Sent: Wednesday, 23 February 2011 1:18 PM > To: 'Robert Jongbloed'; 'Jan Willamowius'; opalvoip- > devel(a)lists.sourceforge.net > Cc: h323plus(a)lists.packetizer.com > Subject: RE: [Opalvoip-devel] error H.263 > > Robert > > You can also use the PTLIB_TRACE_CODECS environmental variable. > Found it enormously helpful debugging the X264 encoder. > > Simon > > -----Original Message----- > From: Robert Jongbloed [mailto:robertj@voxlucida.com.au] > Sent: 23 February 2011 11:55 > To: 'Simon Horne'; 'Jan Willamowius'; > opalvoip-devel(a)lists.sourceforge.net > Cc: h323plus(a)lists.packetizer.com > Subject: RE: [Opalvoip-devel] error H.263 > > The OPAL infrastructure is fine and all this works perfectly with the > IPP codecs (and another private H.264 implementation) for both SIP and > H.323 operation. > > I just wanted confirmation that the bit rate control was working in > the helper app, as a breakpoint at the right place showed the bit rate > and frame > rate where correctly negotiated and passed to helper app via the > SET_FRAME_RATE/SET_TARGET_BITRATE commands. > > Gotta dig deeper ... > > Robert Jongbloed > OPAL/OpenH323/PTLib Architect and Co-founder. > > > > -----Original Message----- > > From: Simon Horne [mailto:s.horne@packetizer.com] > > Sent: Tuesday, 22 February 2011 8:38 PM > > To: 'Jan Willamowius'; opalvoip-devel(a)lists.sourceforge.net > > Cc: h323plus(a)lists.packetizer.com > > Subject: Re: [Opalvoip-devel] error H.263 > > > > Jan > > > > You are correct . To match to a bandwidth the encoder must know > > frame size and rate. The plugin support is very much h323plus > > specific. You can calculate the frame size/rate by using the > > internal table or can use a supplied list of supported frame > > sizes/rates. These can be manually coded from largest to smallest or > > retrieved from the video input > device. > > DirectShow for instance supports retrieving the list of supported > > sizes > and > > rates via calling PVideoInputDevice:: GetDeviceCapabilities(). > > > > These can be passed to the codec via calling > > PLUGINCODEC_CONTROL_SET_FORMAT_OPTIONS. In h323plus the function to > > do > this > > is H323VideoCodec::SetSupportedFormats. The function returns the > > default frame size and rate for the given bitrate that is supported > > by the input device. Then you can set the input device with the > > returned frame size > /rate > > in the MyH323Endpoint::OpenVideoChannel. See Applications/SimplePlus > > for example of how that is done. > > > > The bandwidth (and level\MBPS etc) values for the X264 Encoder is > > set by PLUGINCODEC_CONTROL_SET_CODEC_OPTIONS which is called after > > the local and remote capabilities have been merged in h323plus. > > > > Then there is flowControl which does basically the same thing. You > > pass to the plugin a bitrate value via > > PLUGINCODEC_CONTROL_FLOW_OPTIONS it then returns a supported frame > > size/rate (internal or supplied earlier) then > you > > pass these value to the input device via calling PVideoInputDevice:: > > FlowControl(). > > > > The architecture of Opal has deviated a lot from its h323plus roots > > and I think there is a lot more things to consider to getting this > > to work with it. > > > > Simon > > > > -----Original Message----- > > From: Jan Willamowius [mailto:jan@willamowius.de] > > Sent: 22 February 2011 18:46 > > To: opalvoip-devel(a)lists.sourceforge.net > > Subject: Re: [Opalvoip-devel] error H.263 > > > > When I debugged a similar bandwidth issue on H323Plus a few months > > ago, I found that the bit rate setting was passed to the encoder > > correctly, but > to > > correctly meet this target the encoder needs to know the correct > > values of influencing parameters, like the frame rate. > > In my case the frame rate wasn't passed in correctly, so the encoder > > kept producing video at the wrong rate. > > > > I haven't fixed the issue back then, but worked around it. I'm not > > sure if anybody else has (or if the same applies to the OPAL version > > of the > codec). > > > > Regards, > > Jan > > > > Robert Jongbloed wrote: > > > Quick question on this helper app, do you know if the bit rate > > > control works with it? > > > > > > > > > > > > As far as I can tell, I am setting it to 256kbps and it is still > > > sending at 4Mbps. So, before I go digging deeper, I was hoping for > > > a bit of a sanity check. > > > > > > > > > > > > Thank you very much! > > > > > > > > > > > > Robert Jongbloed > > > > > > OPAL/OpenH323/PTLib Architect and Co-founder. > > > > > > > > > > > > From: Simon Horne [mailto:s.horne@packetizer.com] > > > Sent: Monday, 7 February 2011 10:01 PM > > > To: 'Robert Jongbloed'; 'ZAHRA dehghanianfard' > > > Cc: 'opal'; 'opal'; h323plus(a)lists.packetizer.com > > > Subject: RE: error H.263 > > > > > > > > > > > > I think both the opal and h323plus community can benefit. > > > > > > http://www.h323plus.org/source/download/ffmpeg_x264.zip > > > > > > > > > > > > Place all files in your application directory. > > > > > > The FFMPEG (with w32threads) and X264 is built with mingw/msys. > > > x264plugin_helper.exe is built with vs2008 and requires vs2008 runtime. > > > > > > > > > > > > Simon > > > > > > > > > > > > From: Robert Jongbloed [mailto:robertj@voxlucida.com.au] > > > Sent: 07 February 2011 15:48 > > > To: ZAHRA dehghanianfard > > > Cc: opal; opal > > > Subject: Re: [Opalvoip-devel] error H.263 > > > > > > > > > > > > The answer to your questions are: > > > > > > > > > > > > 1) Yes, but you need to compile it. > > > > > > 2) The result of compiling it is a DLL > > > > > > 3) You will have to figure out why it doesn't compile under windows. > > > > > > > > > > > > > > > > > > I have to admit to not being able to get the H.263 (or x264) > > > codecs to compile and work under Windows, though I have only tried > > > somewhat > briefly. > > > Unfortunately the authors of all the libraries mainly use Linux, > > > though it is my understanding that it can be compiled using > MinGW/Cygwin. > > > > > > > > > > > > > > > > > > I am sure the OPAL community would be incredibly grateful to > > > anyone that can provide a pre-built binary for the H.263 (and x264!) codec. > > > > > > > > > > > > > > > -------- > > > > > > Robert Jongbloed > > > > > > Vox Lucida Pty. Ltd. > > > > > > > > > > > > > > > > > > > > > > > > On 03/02/2011, at 5:33 PM, ZAHRA dehghanianfard wrote: > > > > > > > > > > > > > > > Hi robert. > > > > > > Many thanks for your last support; I need to use OpenPhone3.8.2 by > > > H.263 codec run. > > > > > > 1) Is OpenPhone 3.8.2 with Opal 3.8.2 & Ptlib2.8.2 support H.263 > > codec > > > inside? > > > > > > 2) If the above response is YES, Are you suggesting any H.263 DLL > > file? > > > > > > 3) I find a source that name is "H.263-1998" then I download that > and > > > compiles it but I find below Error inside: > > > > > > > > > > > > 1>------ Build started: Project: H.263-1998 (FFMPEG) Video Codec, > > > Configuration: Debug Win32 ------ > > > 1>Compiling... > > > 1>h263pframe.cxx > > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(155) : fatal > > > 1>error > > > C1083: Cannot open include file: 'libavcodec\avcodec.h': No such > > > file or directory > > > 1>h263-1998.cxx > > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(155) : fatal > > > 1>error > > > C1083: Cannot open include file: 'libavcodec\avcodec.h': No such > > > file or directory > > > 1>Generating Code... > > > 1>Build log was saved at > > > "file://c:\opal\plugins\Debug\H263-1998\BuildLog.htm > > > <file:///c:\opal\plugins\Debug\H263-1998\BuildLog.htm> " > > > 1>H.263-1998 (FFMPEG) Video Codec - 2 error(s), 0 warning(s) > > > ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped > > > ========== > > > > > > > > > > > > I try to solve this problem by download a "libavcodec" that use > > > some header & DLL file that I copy in > > > "C:\opal\plugin\video\common" but I take below > > > error: > > > > > > > > > > > > > > > > > > 1>------ Build started: Project: H.263-1998 (FFMPEG) Video Codec, > > > Configuration: Debug Win32 ------ > > > 1>Compiling... > > > 1>h263pframe.cxx > > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(185) : fatal > > > 1>error > > > C1189: #error : Libavcodec LIBAVCODEC_VERSION_INT too old. > > > 1>h263-1998.cxx > > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(185) : fatal > > > 1>error > > > C1189: #error : Libavcodec LIBAVCODEC_VERSION_INT too old. > > > 1>Generating Code... > > > 1>Build log was saved at > > > "file://c:\opal\plugins\Debug\H263-1998\BuildLog.htm > > > <file:///c:\opal\plugins\Debug\H263-1998\BuildLog.htm> " > > > 1>H.263-1998 (FFMPEG) Video Codec - 2 error(s), 0 warning(s) > > > ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped > > > ========== > > > > > > > > > > > > Please guide me to i can have H.263 codec with DLL & source over > > > OpenPhone > > > 3.8.2 here. > > > > > > I am in wait for your response. > > > > > > Best Regards. > > > > > > Zahra. > > > > -- > > Jan Willamowius, jan(a)willamowius.de, http://www.gnugk.org/ > > > > > ---------------------------------------------------------------------------- > > -- > > Index, Search & Analyze Logs and other IT data in Real-Time with > > Splunk Collect, index and harness all the fast moving IT data > > generated by your applications, servers and devices whether > > physical, virtual or in the > cloud. > > Deliver compliance at lower cost and gain new business insights. > > Free Software Download: http://p.sf.net/sfu/splunk-dev2dev > > _______________________________________________ > > Opalvoip-devel mailing list > > Opalvoip-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/opalvoip-devel > > > > > > > ---------------------------------------------------------------------------- > - > > - > > Index, Search & Analyze Logs and other IT data in Real-Time with > > Splunk Collect, index and harness all the fast moving IT data > > generated by your applications, servers and devices whether > > physical, virtual or in the > cloud. > > Deliver compliance at lower cost and gain new business insights. > > Free Software Download: http://p.sf.net/sfu/splunk-dev2dev > > _______________________________________________ > > Opalvoip-devel mailing list > > Opalvoip-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/opalvoip-devel

1 0

Modifying Q.931 IEs in setup PDU
by Paul Chitescu 23 Feb '11

23 Feb '11

Hello all! While trying to add code in Yate to set some important parameters - for the telephony business - I noticed my changes are overwritten by OpenH323 / H323Plus. I reimplemented H323Connection::OnSendSignalSetup() and changed the Q.931 fields in setupPDU. Unfortunately the following code (in h323.cxx) undoes my changes: if (!OnSendSignalSetup(setupPDU)) return EndedByNoAccept; // Do this again (was done when PDU was constructed) in case // OnSendSignalSetup() changed something. setupPDU.SetQ931Fields(*this, TRUE); setupPDU.GetQ931().GetCalledPartyNumber(remotePartyNumber); Is there any solid reason why setupPDU.SetQ931Fields(*this, TRUE) is called? Its default parameters are overwriting the type, plan, presentation and screening of the numbers. I also need to set separate type of number on caller and called party numbers. My plan is to patch OpenH323 / H323Plus to delete the extra SetQ931Fields(). Do you see any unintended consequences of such a change? Regards, Paul Chitescu

2 2

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

22 Feb '11

Robert You can also use the PTLIB_TRACE_CODECS environmental variable. Found it enormously helpful debugging the X264 encoder. Simon -----Original Message----- From: Robert Jongbloed [mailto:robertj@voxlucida.com.au] Sent: 23 February 2011 11:55 To: 'Simon Horne'; 'Jan Willamowius'; opalvoip-devel(a)lists.sourceforge.net Cc: h323plus(a)lists.packetizer.com Subject: RE: [Opalvoip-devel] error H.263 The OPAL infrastructure is fine and all this works perfectly with the IPP codecs (and another private H.264 implementation) for both SIP and H.323 operation. I just wanted confirmation that the bit rate control was working in the helper app, as a breakpoint at the right place showed the bit rate and frame rate where correctly negotiated and passed to helper app via the SET_FRAME_RATE/SET_TARGET_BITRATE commands. Gotta dig deeper ... Robert Jongbloed OPAL/OpenH323/PTLib Architect and Co-founder. > -----Original Message----- > From: Simon Horne [mailto:s.horne@packetizer.com] > Sent: Tuesday, 22 February 2011 8:38 PM > To: 'Jan Willamowius'; opalvoip-devel(a)lists.sourceforge.net > Cc: h323plus(a)lists.packetizer.com > Subject: Re: [Opalvoip-devel] error H.263 > > Jan > > You are correct . To match to a bandwidth the encoder must know frame > size and rate. The plugin support is very much h323plus specific. You > can calculate the frame size/rate by using the internal table or can > use a supplied list of supported frame sizes/rates. These can be > manually coded from largest to smallest or retrieved from the video input device. > DirectShow for instance supports retrieving the list of supported > sizes and > rates via calling PVideoInputDevice:: GetDeviceCapabilities(). > > These can be passed to the codec via calling > PLUGINCODEC_CONTROL_SET_FORMAT_OPTIONS. In h323plus the function to > do this > is H323VideoCodec::SetSupportedFormats. The function returns the > default frame size and rate for the given bitrate that is supported by > the input device. Then you can set the input device with the returned > frame size /rate > in the MyH323Endpoint::OpenVideoChannel. See Applications/SimplePlus > for example of how that is done. > > The bandwidth (and level\MBPS etc) values for the X264 Encoder is set > by PLUGINCODEC_CONTROL_SET_CODEC_OPTIONS which is called after the > local and remote capabilities have been merged in h323plus. > > Then there is flowControl which does basically the same thing. You > pass to the plugin a bitrate value via > PLUGINCODEC_CONTROL_FLOW_OPTIONS it then returns a supported frame > size/rate (internal or supplied earlier) then you > pass these value to the input device via calling PVideoInputDevice:: > FlowControl(). > > The architecture of Opal has deviated a lot from its h323plus roots > and I think there is a lot more things to consider to getting this to > work with it. > > Simon > > -----Original Message----- > From: Jan Willamowius [mailto:jan@willamowius.de] > Sent: 22 February 2011 18:46 > To: opalvoip-devel(a)lists.sourceforge.net > Subject: Re: [Opalvoip-devel] error H.263 > > When I debugged a similar bandwidth issue on H323Plus a few months > ago, I found that the bit rate setting was passed to the encoder > correctly, but to > correctly meet this target the encoder needs to know the correct > values of influencing parameters, like the frame rate. > In my case the frame rate wasn't passed in correctly, so the encoder > kept producing video at the wrong rate. > > I haven't fixed the issue back then, but worked around it. I'm not > sure if anybody else has (or if the same applies to the OPAL version > of the codec). > > Regards, > Jan > > Robert Jongbloed wrote: > > Quick question on this helper app, do you know if the bit rate > > control works with it? > > > > > > > > As far as I can tell, I am setting it to 256kbps and it is still > > sending at 4Mbps. So, before I go digging deeper, I was hoping for a > > bit of a sanity check. > > > > > > > > Thank you very much! > > > > > > > > Robert Jongbloed > > > > OPAL/OpenH323/PTLib Architect and Co-founder. > > > > > > > > From: Simon Horne [mailto:s.horne@packetizer.com] > > Sent: Monday, 7 February 2011 10:01 PM > > To: 'Robert Jongbloed'; 'ZAHRA dehghanianfard' > > Cc: 'opal'; 'opal'; h323plus(a)lists.packetizer.com > > Subject: RE: error H.263 > > > > > > > > I think both the opal and h323plus community can benefit. > > > > http://www.h323plus.org/source/download/ffmpeg_x264.zip > > > > > > > > Place all files in your application directory. > > > > The FFMPEG (with w32threads) and X264 is built with mingw/msys. > > x264plugin_helper.exe is built with vs2008 and requires vs2008 runtime. > > > > > > > > Simon > > > > > > > > From: Robert Jongbloed [mailto:robertj@voxlucida.com.au] > > Sent: 07 February 2011 15:48 > > To: ZAHRA dehghanianfard > > Cc: opal; opal > > Subject: Re: [Opalvoip-devel] error H.263 > > > > > > > > The answer to your questions are: > > > > > > > > 1) Yes, but you need to compile it. > > > > 2) The result of compiling it is a DLL > > > > 3) You will have to figure out why it doesn't compile under windows. > > > > > > > > > > > > I have to admit to not being able to get the H.263 (or x264) codecs > > to compile and work under Windows, though I have only tried somewhat briefly. > > Unfortunately the authors of all the libraries mainly use Linux, > > though it is my understanding that it can be compiled using MinGW/Cygwin. > > > > > > > > > > > > I am sure the OPAL community would be incredibly grateful to anyone > > that can provide a pre-built binary for the H.263 (and x264!) codec. > > > > > > > > > > -------- > > > > Robert Jongbloed > > > > Vox Lucida Pty. Ltd. > > > > > > > > > > > > > > > > On 03/02/2011, at 5:33 PM, ZAHRA dehghanianfard wrote: > > > > > > > > > > Hi robert. > > > > Many thanks for your last support; I need to use OpenPhone3.8.2 by > > H.263 codec run. > > > > 1) Is OpenPhone 3.8.2 with Opal 3.8.2 & Ptlib2.8.2 support H.263 > codec > > inside? > > > > 2) If the above response is YES, Are you suggesting any H.263 DLL > file? > > > > 3) I find a source that name is "H.263-1998" then I download that and > > compiles it but I find below Error inside: > > > > > > > > 1>------ Build started: Project: H.263-1998 (FFMPEG) Video Codec, > > Configuration: Debug Win32 ------ > > 1>Compiling... > > 1>h263pframe.cxx > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(155) : fatal > > 1>error > > C1083: Cannot open include file: 'libavcodec\avcodec.h': No such > > file or directory > > 1>h263-1998.cxx > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(155) : fatal > > 1>error > > C1083: Cannot open include file: 'libavcodec\avcodec.h': No such > > file or directory > > 1>Generating Code... > > 1>Build log was saved at > > "file://c:\opal\plugins\Debug\H263-1998\BuildLog.htm > > <file:///c:\opal\plugins\Debug\H263-1998\BuildLog.htm> " > > 1>H.263-1998 (FFMPEG) Video Codec - 2 error(s), 0 warning(s) > > ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped > > ========== > > > > > > > > I try to solve this problem by download a "libavcodec" that use some > > header & DLL file that I copy in "C:\opal\plugin\video\common" but I > > take below > > error: > > > > > > > > > > > > 1>------ Build started: Project: H.263-1998 (FFMPEG) Video Codec, > > Configuration: Debug Win32 ------ > > 1>Compiling... > > 1>h263pframe.cxx > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(185) : fatal > > 1>error > > C1189: #error : Libavcodec LIBAVCODEC_VERSION_INT too old. > > 1>h263-1998.cxx > > 1>c:\opal\plugins\video\h.263-1998\../common/ffmpeg.h(185) : fatal > > 1>error > > C1189: #error : Libavcodec LIBAVCODEC_VERSION_INT too old. > > 1>Generating Code... > > 1>Build log was saved at > > "file://c:\opal\plugins\Debug\H263-1998\BuildLog.htm > > <file:///c:\opal\plugins\Debug\H263-1998\BuildLog.htm> " > > 1>H.263-1998 (FFMPEG) Video Codec - 2 error(s), 0 warning(s) > > ========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped > > ========== > > > > > > > > Please guide me to i can have H.263 codec with DLL & source over > > OpenPhone > > 3.8.2 here. > > > > I am in wait for your response. > > > > Best Regards. > > > > Zahra. > > -- > Jan Willamowius, jan(a)willamowius.de, http://www.gnugk.org/ > > ---------------------------------------------------------------------------- > -- > Index, Search & Analyze Logs and other IT data in Real-Time with > Splunk Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, > virtual or in the cloud. > Deliver compliance at lower cost and gain new business insights. > Free Software Download: http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Opalvoip-devel mailing list > Opalvoip-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/opalvoip-devel > > > ---------------------------------------------------------------------------- - > - > Index, Search & Analyze Logs and other IT data in Real-Time with > Splunk Collect, index and harness all the fast moving IT data > generated by your applications, servers and devices whether physical, > virtual or in the cloud. > Deliver compliance at lower cost and gain new business insights. > Free Software Download: http://p.sf.net/sfu/splunk-dev2dev > _______________________________________________ > Opalvoip-devel mailing list > Opalvoip-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/opalvoip-devel

1 0