September 2009 - h323plus - lists.packetizer.com

Re: [h323plus] MyPhone 0.4 setup is incomplete
by Wilfried H 30 Sep '09

30 Sep '09

At 29.09.2009 21:37 you wrote: >For including Microsoft libraries in redistributable applications is >necessary License agreement etc (VS 2005 and 2008 have Express free of >charge license, VS 2003 and below don't) > >If you need $$$$71.dll files (msvcr71, msvp71 etc) you need Visual >Studio 2003 redistributable from Microsoft or copy from any aplication >that already have it. For example, u can copy "71"dlls from VMware >applications, or even from classic versions of World of Warcraft! > >You can put the DLL on google too and have a nice list of sites that >redistribute the single DLL as a 'backup' to not infringe law. Thank you for clarification. I thought downloading a dll from *somewhere* might be a security risk. Furthermore, there was a security update from Microsoft which updates mfc71.dll, and the mfc71.dll downloadable from the internet has a version number before this security update. I'll keep looking for a more up-to-date version of the dll. Wilfried

1 0

MyPhone 0.4 setup is incomplete
by Wilfried H 29 Sep '09

29 Sep '09

Hello, I downloaded the MyPhoneSetup04.exe and installed it, but it does not run (Windows XP Pro SP3) with error message "... MFC71.DLL not found ..." Please include the necessary dll's in the distribution. Wilfried

2 1

NAT Traversal document
by Simon Horne 26 Sep '09

26 Sep '09

Guys Both GnuGk and H323plus CVS now support Direct Media or H.460.18/.19/.23/.24 in both slow and fast connect. These 4 standards work together to allow media to traverse NAT without requiring the media to be proxied. This greatly increases the scalability of video conferencing systems within NAT environments with only a small proportion of media needing to be proxied. I have prepared a not-so technical document which explains Direct Media and how the 4 standards interwork. http://www.h323forum.org/specifications/ I have also released a new version of PacPhone v2,2 (H323plus v1.22 CVS) and a windows installer for GnuGk v2.3.1 (current CVS) and both are available from the PacPhone website (www.pacphone.com <http://www.pacphone.com/> ). Simon

1 0

4CIF support - OpenMCU urgent
by leandro.alvares＠caixa.gov.br 25 Sep '09

25 Sep '09

Hello all, I did these modifications in my openmcu 2.2.5 source code to enable 4CIF resolution. But now, the User Video Capability isn't presente anymore. 0:54.967 H245:b65ddb90 H245 Received open channel: R-3, state=Released 0:54.967 H245:b65ddb90 H323 CreateLogicalChannel - forward channel 0:54.967 H245:b65ddb90 H323 FindCapability: videoData 0:54.967 H245:b65ddb90 Codec Cannot have UserInputCapability in DataType 0:54.967 H245:b65ddb90 H323 CreateLogicalChannel - unknown data type 0:54.967 H245:b65ddb90 H245 Sending PDU [ip$10.192.37.69:40091/ip$10.192.37.69:30055] : Does anyone know what should I have to do to fix it? or to enable 4CIF? debianVC:/usr/local/src/openmcu-v2_2_5# diff conference.cxx.old conference.cxx < MCUVideoMixer::FillCIFYUVFrame(memberFrameStores.GetFrameStore(CIF_WIDTH, CIF_HEIGHT).data.GetPointer(), 0, 0, 0); --- > MCUVideoMixer::FillCIFYUVFrame(memberFrameStores.GetFrameStore(CIF4_WIDTH, CIF4_HEIGHT).data.GetPointer(), 0, 0, 0); debianVC:/usr/local/src/openmcu-v2_2_5# diff conference.h.mexido conference.h 348c348 < MCUSimpleVideoMixer(PBoolean forceScreenSplit = FALSE,H323Capability::CapabilityFrameSize _frameSize = H323Capability::cif4MPI); --- > MCUSimpleVideoMixer(PBoolean forceScreenSplit = FALSE,H323Capability::CapabilityFrameSize _frameSize = H323Capability::cifMPI); debianVC:/usr/local/src/openmcu-v2_2_5# diff mcu.cxx.old mcu.cxx 166c166 < frameSize = H323Capability::cifMPI; --- > frameSize = H323Capability::cif4MPI; debianVC:/usr/local/src/openmcu-v2_2_5.modificada# diff h323.cxx.old h323.cxx 817c817 < if (!InitGrabber(videoGrabber, CIF_WIDTH, CIF_HEIGHT)) { --- > if (!InitGrabber(videoGrabber, CIF4_WIDTH, CIF4_HEIGHT)) { Best Regards, Leandro ________________________________ De: Adrien Rudulier [mailto:rudz04@yahoo.ca] Enviada em: quarta-feira, 23 de setembro de 2009 01:50 Para: Leandro Oliveira Alvares Assunto: Re: RES: RES: 4CIF support - OpenMCU urgent I haven't worked on OpenMCU for a year and a half. Everything I know is from memory. However, I have never seen a call dropped. I might have changed the h263-1998 codec to resemble the h.263 codec that comes with OpenMCU. ________________________________ From: "leandro.alvares(a)caixa.gov.br" <leandro.alvares(a)caixa.gov.br> To: rudz04(a)yahoo.ca Sent: Tuesday, September 22, 2009 2:23:45 PM Subject: RES: RES: 4CIF support - OpenMCU urgent Hi Adrien, I really want to thanks your help. It is being appreciated a lot. I did some changes: debianVC:/usr/local/src/openmcu-v2_2_5# diff conference.cxx.old conference.cxx < MCUVideoMixer::FillCIFYUVFrame(memberFrameStores.GetFrameStore(CIF_WIDTH, CIF_HEIGHT).data.GetPointer(), 0, 0, 0); --- > MCUVideoMixer::FillCIFYUVFrame(memberFrameStores.GetFrameStore(CIF4_WIDTH, CIF4_HEIGHT).data.GetPointer(), 0, 0, 0); debianVC:/usr/local/src/openmcu-v2_2_5# diff conference.h.mexido conference.h 348c348 < MCUSimpleVideoMixer(PBoolean forceScreenSplit = FALSE,H323Capability::CapabilityFrameSize _frameSize = H323Capability::cif4MPI); --- > MCUSimpleVideoMixer(PBoolean forceScreenSplit = FALSE,H323Capability::CapabilityFrameSize _frameSize = H323Capability::cifMPI); debianVC:/usr/local/src/openmcu-v2_2_5# diff mcu.cxx.old mcu.cxx 166c166 < frameSize = H323Capability::cifMPI; --- > frameSize = H323Capability::cif4MPI; At this moment I can see at trace CIF4_MPI = 2 and CIF4_MPI = 1and in some moment I can see a resize function from 704*576 to 352*288 at OpalPlugin. (It's no good I think, it is forcing to use CIF resolution...) And when I join to a MCU room, The call is dropped by reason userProvidedVerifiedAndFailed. I'm sorry to bother you, but I'm trying to do this at 6 months, and nobody help me. ________________________________ De: Adrien Rudulier [mailto:rudz04@yahoo.ca] Enviada em: terça-feira, 22 de setembro de 2009 13:02 Para: Leandro Oliveira Alvares Assunto: Re: RES: 4CIF support - OpenMCU urgent You need to change all of the size parameters in openmcu from cif to 4cif. I am not sure what exactly needs to be done because I don't have access to the modified source code. ________________________________ From: "leandro.alvares(a)caixa.gov.br" <leandro.alvares(a)caixa.gov.br> To: rudz04(a)yahoo.ca Sent: Monday, September 21, 2009 11:52:28 AM Subject: RES: 4CIF support - OpenMCU urgent Hi Adrien, Thanks to reply, I think I'm using this plugin already, anyway I'll download the CVS version. But Adrien, What configuration should I have to do to enable 4CIF resolution? Do you know this? Because I'm setting the frameSize = H323Capability::cifMPI; parameter at mcu.cxx. Am I right? thanks a lot. regards, Leandro Oliveira Alvares ________________________________ De: Adrien Rudulier [mailto:rudz04@yahoo.ca] Enviada em: segunda-feira, 21 de setembro de 2009 04:46 Para: Leandro Oliveira Alvares Assunto: Re: 4CIF support - OpenMCU urgent You need to use the other H.263-1998 plugin. You can get it from the OPAL library. http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/opal/trunk/plugins/vide… Polycom PVX uses the 1998 version of the H.263 Codec. ________________________________ From: "leandro.alvares(a)caixa.gov.br" <leandro.alvares(a)caixa.gov.br> To: rudz04(a)yahoo.ca Sent: Wednesday, September 16, 2009 2:38:59 PM Subject: 4CIF support - OpenMCU urgent Hi Adrien, I have saw your post: I am currently using the newest versions (as of July 2, 2008) of ptlib(2.3.0), h323plus(1.20.5) and openmcu(2.2.4) from cvs on Ubuntu 8.04. I installed the plugins correctly and openmcu runs fine. However when using two polycom pvx clients to connect to openmcu using H.263 at 4CIF for both transmitting and receiving, the video is blocky and very distorted. There is no packet loss, the bitrate is set to 1920 kbps and the frame rate is a constant 30 fps for both transmitting and receiving. I was wondering if the problem is with openmcu or the pvx clients. Has anyone successfully used 4CIF resolution to be clear and smooth? Also, I had to massage the h.263 plugin code to get 4CIF to work with openmcu. Any help would greatly be appreciated. Adrien Rudulier Did you solve your problem? I'm having the same problem and I diddn't get some post to help me. I'm using the same softwares version than you. What did you do to enable 4CIF resolution? Thanks. Regards, Leandro ________________________________ Looking for the perfect gift? Give the gift of Flickr! <http://www.flickr.com/gift/> ________________________________ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! <http://downloads.yahoo.com/ca/internetexplorer/> ________________________________ The new Internet Explorer® 8 - Faster, safer, easier. Optimized for Yahoo! Get it Now for Free! <http://downloads.yahoo.com/ca/internetexplorer/>

2 1

4CIF support at OpenMCU
by leandro.alvares＠caixa.gov.br 22 Sep '09

22 Sep '09

Hi all, I finally did the modifications to enable the 4 CIF capability. In my trace, All entries has CIF4 = 2.. But the PVX client are not sending video, the OpenMCU doesn't receive video. I'm sending the modifications. Am I right? if not, What should I have to do? I'm still getting the PColCnv PColourConverter constructed: YUV420P 704x576 -> YUV420P 352x28 at trace. Any help will be appreciated. Thanks a lot. debianVC:/usr/local/src/openmcu-v2_2_5# diff conference.cxx.old conference.cxx < MCUVideoMixer::FillCIFYUVFrame(memberFrameStores.GetFrameStore(CIF_WIDTH , CIF_HEIGHT).data.GetPointer(), 0, 0, 0); --- > MCUVideoMixer::FillCIFYUVFrame(memberFrameStores.GetFrameStore(CIF4_WIDT H, CIF4_HEIGHT).data.GetPointer(), 0, 0, 0); debianVC:/usr/local/src/openmcu-v2_2_5# diff conference.h.mexido conference.h 348c348 < MCUSimpleVideoMixer(PBoolean forceScreenSplit = FALSE,H323Capability::CapabilityFrameSize _frameSize = H323Capability::cif4MPI); --- > MCUSimpleVideoMixer(PBoolean forceScreenSplit = FALSE,H323Capability::CapabilityFrameSize _frameSize = H323Capability::cifMPI); debianVC:/usr/local/src/openmcu-v2_2_5# diff mcu.cxx.old mcu.cxx 166c166 < frameSize = H323Capability::cifMPI; --- > frameSize = H323Capability::cif4MPI; debianVC:/usr/local/src/openmcu-v2_2_5# diff h323.cxx.old h323.cxx 817c817 < if (!InitGrabber(videoGrabber, CIF_WIDTH, CIF_HEIGHT)) { --- > if (!InitGrabber(videoGrabber, CIF4_WIDTH, CIF4_HEIGHT)) { Best regards, Leandro

1 0

SVN PTLib 2.7beta1 Compilation
by Marcos Fábio Jardini 22 Sep '09

22 Sep '09

Hello I make a fresh new download from SVN PTLib trunk (2.7beta1) and CVS SimplePlus. The two compiles fine. I only have one question: is P_DIRECTSHOW2 really being compiled? Because there is no vidinput_directx2[.h/.cxx] in VS2008 project/solution (the 2 existis in source and header folders). Even ptbuildops.h.in, when transformed, do not include P_DIRECTSHOW2 definition (greyed by an #IF 0). Can I force P_DIRECTSHOW2 and the two headers in project/solution, or is needed something more to do? Regards, Eng. Marcos F. Jardini ___________________ [[ 0--,, ]]

1 0

Compiling H323Plus 1.22 CVS Trunk, Visual Studio 2008
by Marcos Fábio Jardini 03 Sep '09

03 Sep '09

Hello people Reporting back: * PTLib 2.6 (SVN Trunk): All compile fine and now DirectShow and Application properly works on projects outside PTLib_samples_2008.sln * H323Plus 1.22 (CVS Trunk): H46018_h225.h Error "H46019UDPSocket::GetLocalAddress" makes access to members "m_locAddr" and "m_locPort" but the two members are guarded by macro H323_H46024A and the method not. Solution (?): put "H46019UDPSocket::GetLocalAddress" under H323_H46024A macro guardian like "[Get/Set]AlternateAddresses" ? -- ----- Jogue RPG, alimente o lado criativo!

2 6