- h323plus - lists.packetizer.com

General WorkPlan for H323plus
by Simon Horne 25 Dec '07

25 Dec '07

Guys As you are aware the focus of H323plus is about the plus (new features/services) and less about architecture redesign allowing existing applications to be upgraded/improved without requiring wholesale code changes yet still have access to the latest and greatest features like H.239, H.350 etc. With the exception of the upcoming upgrade to PTLib 2.x we hope to continue in that vain. As most of you are aware I also have commitments to GnuGk and PacPhone so I am spread thin at the best of times but at the moment it is quite accute. I have 5 documents to be presented to the ITU meeting in Korea in January as well as other work which I hope to make an announcement on in the new year. Here are some the current work items. Migration to ptlib 2.x (ETA January) which has been previously discussed. Addition of GnuGK NAT Traversal. (ETA 1 week) This will allow the H323plus based applications to natively traverse NATs using GnuGk. The code has been tried and tested and working with PacPhone for over a year, I have just tidy up it and added better documentation. Note this is not the ITU standard method which is H.460.18/19. H.235.6. (ETA January) This is the defacto standard for H.323 Media encryption with support with polycom PVX, Tandberg and Codian. Thanks heaps to bian xuegong for helping sort it out. There is some new work at the ITU upgrading the encryption from AES128 to AES256 so hopefully that will be included. File Transfer. (ETA January) This is really cool. This allows the transfer of files via TFTP encaptulated in RTP frames allowing lightweight data transfer without the need for the T.120 framework overhead. Since it uses RTP it can use existing NAT Traversal mechanisms like GnuGk to traverse NATs. I am putting forward a submission to the ITU on this so watch out for that. H.460.presence (ETA Feburary) I have a submission to the ITU for scalable presence system I have been working on for sometime. I hope to have this finalised and committed by Feb. H.460.MMS (ETA ?) Multimedia Messaging. This is also up for submission to the ITU. This is a companion and extension on H.460.tm (Text Messaging) which is in the extensions directory of the CVS. There is an exciting year ahead for h323plus. Simon

1 0

H323plus and ptlib 2.x?
by Adam Williamson 25 Dec '07

25 Dec '07

So, second question :) I've now got h323plus built and in the distro. But it doesn't build against ptlib 2.x, only ptlib / pwlib 1.12. This means I have a fairly ugly mess of packages in Mandriva right now - separate packages for ptlib 2.x and pwlib 1.12 which conflict in lots of fun ways. I need both as current Opal wants ptlib 2.x, but h323plus wants pwlib / ptlib 1.12... I guess h323plus will be migrated to build okay against ptlib 2.x, right? Is there an ETA on this? Thanks! -- adamw

3 3

Trouble building h323plus with GCC 4.2.2
by Adam Williamson 25 Dec '07

25 Dec '07

Hi, there. I'm looking at migrating Mandriva from openh323 to h323plus, but I'm getting several errors trying to build it. Building against pwlib 1.12.0. The first set of errors is as follows: g++ -fPIC -D_REENTRANT -fno-exceptions -Wall -fPIC -DPIC -DNDEBUG -DPTRACING -I/home/adamw/rpm/BUILD/h323plus/include -I/usr/share/pwlib//include -O2 -g -pipe -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector --param=ssp-buffer-size=4 -fexceptions -fomit-frame-pointer -march=i586 -mtune=generic -fasynchronous-unwind-tables -DLDAP_DEPRECATED -c /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx -o /home/adamw/rpm/BUILD/h323plus/lib/obj_linux_x86_r/h350.o /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "(" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "(" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting ")" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "(" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "commObject" and ")" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "<" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting ">" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "(" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "&" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69:1: error: pasting "(" and "commObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "(" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "(" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting ")" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "(" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "commURIObject" and ")" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "<" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting ">" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "(" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "&" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80:1: error: pasting "(" and "commURIObject" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "(" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "(" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting ")" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "(" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "H323Identity" and ")" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "<" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting ">" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "(" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "&" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101:1: error: pasting "(" and "H323Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "(" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "(" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting ")" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "(" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "H235Identity" and ")" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "<" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting ">" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "(" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "&" and "H235Identity" does not give a valid preprocessing token /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114:1: error: pasting "(" and "H235Identity" does not give a valid preprocessing token With the help of one of our contributors, we fixed that one with the following patch to pwlib: -------------------- --- ptlib_v1_12_0/include/ptclib/pldap.h 2007-10-18 23:22:38.000000000 -0700 +++ ptlib_v1_12_0/include/ptclib/pldap.h.new 2007-12-22 04:56:25.000000000 -0800 @@ -597,9 +597,9 @@ }; #define LDAP_Schema(name) \ -static LDAPPluginServiceDescriptor<##name##_schema> ##name##_schema_descriptor; \ -PCREATE_PLUGIN(##name##_schema, PLDAPSchema, &##name##_schema_descriptor); \ -PWLIB_STATIC_LOAD_PLUGIN(##name##_schema, PLDAPSchema); \ +static LDAPPluginServiceDescriptor<name##_schema> name##_schema_descriptor; \ +PCREATE_PLUGIN(name##_schema, PLDAPSchema, &name##_schema_descriptor); \ +PWLIB_STATIC_LOAD_PLUGIN(name##_schema, PLDAPSchema); \ //////////////////////////////////////////////////////////////////////////////////////////// ----------------- But then we get some further errors in the same macros: -------------------- /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In function 'void PWLibPlugin_TriggerRegister(PPluginManager*)': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80: error: redefinition of 'void PWLibPlugin_TriggerRegister(PPluginManager*)' /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69: error: 'void PWLibPlugin_TriggerRegister(PPluginManager*)' previously defined here /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In function 'unsigned int PWLibPlugin_GetAPIVersion()': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:80: error: redefinition of 'unsigned int PWLibPlugin_GetAPIVersion()' /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69: error: 'unsigned int PWLibPlugin_GetAPIVersion()' previously defined here /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In function 'void PWLibPlugin_TriggerRegister(PPluginManager*)': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101: error: redefinition of 'void PWLibPlugin_TriggerRegister(PPluginManager*)' /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69: error: 'void PWLibPlugin_TriggerRegister(PPluginManager*)' previously defined here /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In function 'unsigned int PWLibPlugin_GetAPIVersion()': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:101: error: redefinition of 'unsigned int PWLibPlugin_GetAPIVersion()' /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69: error: 'unsigned int PWLibPlugin_GetAPIVersion()' previously defined here /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In function 'void PWLibPlugin_TriggerRegister(PPluginManager*)': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114: error: redefinition of 'void PWLibPlugin_TriggerRegister(PPluginManager*)' /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69: error: 'void PWLibPlugin_TriggerRegister(PPluginManager*)' previously defined here /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In function 'unsigned int PWLibPlugin_GetAPIVersion()': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:114: error: redefinition of 'unsigned int PWLibPlugin_GetAPIVersion()' /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:69: error: 'unsigned int PWLibPlugin_GetAPIVersion()' previously defined here /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In member function 'BOOL H350_Session::PostNew(const PString&, const std::list<PLDAPSchema, std::allocator<PLDAPSchema> >&)': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:226: error: 'class PLDAPSession::ModAttrib::Operation' is not a class or namespace /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx: In member function 'BOOL H350_Session::PostUpdate(const PString&, const std::list<PLDAPSchema, std::allocator<PLDAPSchema> >&)': /home/adamw/rpm/BUILD/h323plus/src/h350/h350.cxx:240: error: 'class PLDAPSession::ModAttrib::Operation' is not a class or namespace --------- which we've not yet been able to fix. Does anyone have a fix for this? Thanks. -- adamw

2 2

t38modem connecting to innovaphone IP400
by Marcus Robichon 20 Dec '07

20 Dec '07

Hi all, hope this list he correct list to ask fort he t38modem. We need the following due to virtualization of hardware: We use Hylafax as Fax solution. We try to implement t38modem to talk via H323 (T38) protocol to a innovaphone IP400 router. First we implemented the OpenH323 solution. We can connect to the innovaphone router and we can see that the router is calling. But after some seconds we get a I/O error back. Then we tried to upgrade the whole project to h323plus and the new release of t38modem (0.8.4). We tried the same but we get the same error message. Did anybody have a solution for this? Attached you get a logfile to see some "blabla" of t38modem. I cannot come along why this does not work. This is the string we are using to connect to the gatekeeper on innovaphone: t38modem -p ttyp0 -tttttt -g 172.16.25.19 -u HYLA -i 172.16.25.134 --redundancy H -P T.38-UDP --h245tunneldisable Have a nice day. Marcus Robichon

1 0

Video Codec Plugin Tutorial
by Abhishek Rohilla 19 Dec '07

19 Dec '07

H323Plus has now supported all the video codec as plugins. Can someone help me as to how to plug in video codecs into H323Plus. Earlier for H.263 we had to just add the capabilities as the codec class was there in the code. But now that thing does not work with H323Plus.

2 1

回复： H.235 AES problem continue
by Bian 11 Dec '07

11 Dec '07

Simon, The diffie-hellman is used to exchange shared secret which is then used to encrypt sessionKey. The sessionKey is used to encrypt media then. The secret shared (the key) I have got from standard key exchange procedure is equal to "H.235 encryption check code" displayed by PVX UI. It's difficult to think polycom using private mechanism. That means polycom cannot interoperate with other endpoints in standard way. The sharedSecret field within the H235Key structure uses the following fields: • algorithmOID: set to "X", "X1" for the 56-bit RC2-compatible, set to "Y", "Y1" for 56-bit DES or set to "Z", "Z1" for 168-bit Triple-DES or set to "Z3" for 128-bit AES. NOTE 1 – The session key encryption algorithm is the same as the negotiated media encryption algorithm. ( here is the answer? ) Each entity shall take appropriate least significant bits from the common shared Diffie-Hellman secret for the key encryption key (master key); i.e., the 56 least significant bits of the Diffie-Hellman secret for OID "X", OID "X1", OID "Y1" or OID "Y" and the 168 least significant bits of the Diffie-Hellman secret for OID "Z", OID "Z1" or OID "Z2" and the 128 least significant bits of the Diffie-Hellman secret for OID "Z3" or OID "Z2", see also Table 6. ( here is the answer? ) bian ----- 原始邮件 ---- 发件人： Simon Horne <s.horne(a)packetizer.com> 收件人： Bian <bianxg(a)yahoo.cn>; H323plus <h323plus(a)lists.packetizer.com> 已发送： 2007/12/11(周二), 下午8:58:15 主题： RE: [h323plus] H.235 AES problem continue Bian Polycom is not using H.235.6 key exchange and most certainly not using diffie-hellman. It is using symmetric key AES encryption which is AFAIK is NOT standard. The key material is encrypted using a private mechanism. Let me explain what this is > algorithmOID = 2.16.840.1.101.3.4.1.2 > // <"OID_Z3" which means using AES 128 CBC mode > paramS = { > // means IV is 0 > } > encryptedSessionKey = 16 octets { > c7 36 02 5c b7 ae b0 cc 97 c8 af bb d5 72 0f 19 AlgorithmOID has nothing to do with the encryptedSessionKey. The AlgorithmOID notifies the remote what cipher to use DES 3DES or AES. This is standard identifier. Basically this tells the remote to use AES. encryptionSessionKey is encrypted using an non-public known secret method. The only way you are going to decrypt this is if you know how the key is encrypted. AFAIK only polycom can provide you that information. It is not public knowledge. Simon ___________________________________________________________ 天生购物狂，狂抢购物券，你还等什么！ http://cn.mail.yahoo.com/promo/taobao20/index.php

1 0

H.235 AES problem continue
by Bian 11 Dec '07

11 Dec '07

Hi I have finished call procedure of H.235 and get same H.235 encryption check code with PVX. (See attach) This is the shared secret(PVX only display 8 bytes long, whereas the h.235.6 indicate 16 bytes long see below). As slave, local endpoint receive OpenLogicalChannel rerquest, which has a parameter H235_V3KeySyncMaterial. The param content is as below: { algorithmOID = 2.16.840.1.101.3.4.1.2 // <"OID_Z3" which means using AES 128 CBC mode paramS = { // means IV is 0 } encryptedSessionKey = 16 octets { c7 36 02 5c b7 ae b0 cc 97 c8 af bb d5 72 0f 19 .6.\.........r.. } } Then local endpoint begin to decrypt sessionKey from encryptedSessionKey using shared secret. But decryption is failed. Can anyone help to analyse where is the wrong. The below is piece of code decrypting sessionKey (using openssl-0.9.8g) ret = EVP_DecryptInit(&ctx, EVP_aes_128_cbc(), NULL, NULL); PAssert(ret, PLogicError); ret = EVP_CIPHER_CTX_set_key_length(&ctx, 16); PAssert(ret, PLogicError); ret = EVP_DecryptInit(&ctx, EVP_aes_128_cbc(), key, NULL); // IV is null here . key is same as PVX's H.235 encryption check code (PVX only display 8 bytes) PAssert(ret, PLogicError); ret = EVP_DecryptUpdate(&ctx, buffer, &outl, (unsigned char *)in.GetPointer(), 16);// but the "outl" returned is 0 which shall be 16 here I think. len += outl; ret = EVP_DecryptFinal(&ctx, buffer+len, &outl); // return 0 here, means error is found (Each entity shall take appropriate least significant bits from the common shared Diffie-Hellman secret for the key encryption key (master key); i.e., the 56 least significant bits of the Diffie-Hellman secret for OID "X", OID "X1", OID "Y1" or OID "Y" and the 168 least significant bits of the Diffie-Hellman secret for OID "Z", OID "Z1" or OID "Z2" and the 128 least significant bits of the Diffie-Hellman secret for OID "Z3" or OID "Z2", see also Table 6.) Bian ___________________________________________________________ 天生购物狂，狂抢购物券，你还等什么！ http://cn.mail.yahoo.com/promo/taobao20/index.php

2 1

Re: [h323plus] Errors while compliling PTLIB 1.12.0
by JF NP 04 Dec '07

04 Dec '07

Thank you for your fast response, Simon. I put that path, following PWLIB build instructions, but the problem stills. Any ideas?? ----- Mensaje original ---- De: Simon Horne <s.horne(a)packetizer.com> Para: JF NP <jfnp090274(a)yahoo.es> CC: H323plus <h323plus(a)lists.packetizer.com> Enviado: lunes, 3 de diciembre, 2007 22:28:17 Asunto: RE: [h323plus] Errors while compliling PTLIB 1.12.0 DIV { MARGIN:0px;} Make sure you put the pwlib/include path in the VC++ Directories include directory. In VS 2003 Menu tools > options > under projects in the options window > VC++ Directories. Simon -----Original Message----- From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com]On Behalf Of JF NP Sent: Tuesday, December 04, 2007 2:15 AM To: h323plus(a)lists.packetizer.com Subject: [h323plus] Errors while compliling PTLIB 1.12.0 Hi, When I try to compile PTLib (1.12.0) on a computer running Windows XP using VS 2003, I get the following errors (see below, after system configuration), can anybody help me?? This is what configure reports: Located Direct Sound Support at c:\archivos de programa\microsoft directx sdk (june 2007)\ Located DNS Resolver at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\ Located IPv6 Support at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\include\ Located QoS Support at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\include\ Located ODBC support at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\include\ Searching D:\ Located Open SSL at d:\desarrollo\veediaplatform\externaldependencies\openssl-0.9.7e\ Located Open SSL AES at d:\desarrollo\veediaplatform\externaldependencies\openssl-0.9.7e\ Features: Version enabled Byte Order enabled Semaphore Support enabled Plugin Support enabled DNS Resolver enabled Cyrus SASL DISABLED Open LDAP DISABLED due to absence of feature sasl Open SSL enabled Open SSL AES enabled Windows Open SSL DISABLED due to presence of feature openssl Windows Open SSL AES DISABLED due to absence of feature winssl Expat XML DISABLED Windows Expat XML DISABLED VXML DISABLED due to absence of feature expat|winexpat Jabber DISABLED due to absence of feature expat|winexpat XMLRPC DISABLED due to absence of feature expat|winexpat SOAP DISABLED due to absence of feature expat|winexpat Speech API DISABLED IPv6 Support enabled QoS Support enabled Simple DirectMedia Layer DISABLED Video Support enabled ASN Support enabled STUN Support enabled pipe channel Support enabled DTMF encoding/decoding support enabled WAV file support enabled SOCKS protocol support enabled FTP protocol support enabled SNMP protocol support enabled Telnet protocol support enabled remote connection support enabled Serial Support enabled POP3/SMTP Support enabled HTTP Support enabled HTTP service Support enabled Config file protocol support enabled Socket aggregation support enabled Video file support enabled Sound support enabled Direct Sound Support enabled ODBC support enabled Errors: ..\..\..\include\ptlib\pprocess.h(819) : error C2143: syntax error : missing ';' before '<' ..\..\..\include\ptlib\plugin.h(81) : error C2516: 'PFactory' : is not a legal base class ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ..\..\..\include\ptlib\plugin.h(115) : see reference to class template instantiation 'PDevicePluginFactory<_Abstract_T,_Key_T>' being compiled ..\..\..\include\ptlib\plugin.h(81) : error C2143: syntax error : missing ',' before '<' ..\..\..\include\ptlib\plugin.h(84) : error C2516: 'PFactory' : is not a legal base class ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ..\..\..\include\ptlib\plugin.h(84) : see reference to class template instantiation 'PDevicePluginFactory<_Abstract_T,_Key_T>::Worker' being compiled ..\..\..\include\ptlib\plugin.h(84) : error C2143: syntax error : missing ',' before '<' ..\..\..\include\ptlib\plugin.h(84) : error C2039: 'WorkerBase' : is not a member of 'operator``global namespace''' ..\..\..\include\ptlib\pfactory.h(475) : error C2904: 'PFactory' : name already used for a template in the current scope ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ..\..\..\include\ptlib\pfactory.h(475) : error C2920: redefinition : 'PFactory' : template class has already been declared as 'typedef int PFactory' ..\..\..\include\ptlib\pfactory.h(475) : see declaration of 'PFactory' ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ¿Chef por primera vez? - Sé un mejor Cocinillas. Entra en Yahoo! Respuestas. ______________________________________________ ¿Chef por primera vez? Sé un mejor Cocinillas. http://es.answers.yahoo.com/info/welcome

1 0

Automated answering machine for H.323 and SIP
by Craig Southeren 03 Dec '07

03 Dec '07

To all, A new automated test tool has been deployed for both H.323 and SIP users. We have made available different numbers that will provide different functions, such as the server time, your IP address, and echo test, in either SIP or H.323, and in a wide variety of codecs (G.711, Speex, ILBC etc) Numbers are available for SRV-enabled and non-SRV-enabled clients, and for with both numeric and text IDs. The numbers are all of the form: prot:dest@host where: prot = sip or h323 dest = time, addr, echo, tone, 2337, 8463 8063 or 3246 host = opalvoip.net (for SRV-enabled clients) or sip.opalvoip.net or h323.opalvoip.net the destinations are: time or 8463 announce the current server time addr or 2337 announce the clients (your) address tone or 8063 play a three element tone echo or 3246 enter an echo test For example, the destination h323:3246@opalvoip.net is a H.323 based echo test for a non-SRV client BTW: if you are wondering where the numbers come from, look for how to spell "time", "addr", "echo" and "tone" on a standard keypad! All this information is also in the Opal Wiki at: http://www.opalvoip.org/wiki/index.php?n=Main.AnsweringMachine 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

回复：回复：回复： Does H323plus support H.235
by Bian 03 Dec '07

03 Dec '07

See 8.6/H.235.6 The sharedSecret field within the H235Key structure uses the following fields: • algorithmOID: set to "X", "X1" for the 56-bit RC2-compatible, set to "Y", "Y1" for 56-bit DES or set to "Z", "Z1" for 168-bit Triple-DES or set to "Z3" for 128-bit AES. NOTE 1 – The session key encryption algorithm is the same as the negotiated media encryption algorithm. The shared secret is not used directly to encrypt the key exchange material to generate the cipher for media encryption, but used to enctypt the session key. Session key is then used to encrypt media. So, I think we can connect PVX or codian using AES through a standard way. However, Need some work to test this thought. Bian ----- 原始邮件 ---- 发件人： Simon Horne <s.horne(a)packetizer.com> 收件人： Bian <bianxg(a)yahoo.cn>; H323plus <h323plus(a)lists.packetizer.com> 已发送： 2007/12/1(周六), 下午8:16:20 主题： RE: [h323plus] 回复：回复： Does H323plus support H.235 The shared secret is used to encrypt the key exchange material to generate the cipher for media encryption. If the shared secret was public knowledge then anyone can intercept the key exchange and generate a key to decrypt the media. So unless Polycom or Codian wish to share that proprietry secret there is no way to connect via AES. Simon > -----Original Message----- > From: h323plus-bounces(a)lists.packetizer.com > [mailto:h323plus-bounces@lists.packetizer.com]On Behalf Of Bian > Sent: Saturday, December 01, 2007 11:19 AM > To: H323plus > Subject: [h323plus] 回复：回复： Does H323plus support H.235 > > > Simon > > I think PVX's key exchange mechanism is in a standard way. PVX > and Codian MCU can connect using AES. > > But I don't know how the shared secret is used to produce the session key. > > > Bian > > > -----Original Message----- > >Bian > > >No PacPhone AES uses a different key exchange mechanism to PVX. > Polycom uses > >a proprietry method. They should still connect unencrypted. > > >Simon > > > -----Original Message----- > > From: Bian [mailto:bianxg@yahoo.cn] > > Sent: Wednesday, November 28, 2007 12:35 PM > > To: Simon Horne > > Subject: 回复： [h323plus] Does H323plus support H.235 > > > > > > Simon > > > > I test PccPhone with PVX, but the AES is not opened. Does > > PacPhone can interoperate with PVX using AES? > > > > > > Bian > > > > > ___________________________________________________________ > 进入雅虎游戏嘉年华，赢取液晶显示器！ > http://cn.mail.yahoo.com/promo/carnival07/ ___________________________________________________________ 进入雅虎游戏嘉年华，赢取液晶显示器！ http://cn.mail.yahoo.com/promo/carnival07/

3 2

Errors while compliling PTLIB 1.12.0
by JF NP 03 Dec '07

03 Dec '07

Hi, When I try to compile PTLib (1.12.0) on a computer running Windows XP using VS 2003, I get the following errors (see below, after system configuration), can anybody help me?? This is what configure reports: Located Direct Sound Support at c:\archivos de programa\microsoft directx sdk (june 2007)\ Located DNS Resolver at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\ Located IPv6 Support at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\include\ Located QoS Support at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\include\ Located ODBC support at c:\archivos de programa\microsoft visual studio .net 2003\vc7\platformsdk\include\ Searching D:\ Located Open SSL at d:\desarrollo\veediaplatform\externaldependencies\openssl-0.9.7e\ Located Open SSL AES at d:\desarrollo\veediaplatform\externaldependencies\openssl-0.9.7e\ Features: Version enabled Byte Order enabled Semaphore Support enabled Plugin Support enabled DNS Resolver enabled Cyrus SASL DISABLED Open LDAP DISABLED due to absence of feature sasl Open SSL enabled Open SSL AES enabled Windows Open SSL DISABLED due to presence of feature openssl Windows Open SSL AES DISABLED due to absence of feature winssl Expat XML DISABLED Windows Expat XML DISABLED VXML DISABLED due to absence of feature expat|winexpat Jabber DISABLED due to absence of feature expat|winexpat XMLRPC DISABLED due to absence of feature expat|winexpat SOAP DISABLED due to absence of feature expat|winexpat Speech API DISABLED IPv6 Support enabled QoS Support enabled Simple DirectMedia Layer DISABLED Video Support enabled ASN Support enabled STUN Support enabled pipe channel Support enabled DTMF encoding/decoding support enabled WAV file support enabled SOCKS protocol support enabled FTP protocol support enabled SNMP protocol support enabled Telnet protocol support enabled remote connection support enabled Serial Support enabled POP3/SMTP Support enabled HTTP Support enabled HTTP service Support enabled Config file protocol support enabled Socket aggregation support enabled Video file support enabled Sound support enabled Direct Sound Support enabled ODBC support enabled Errors: ..\..\..\include\ptlib\pprocess.h(819) : error C2143: syntax error : missing ';' before '<' ..\..\..\include\ptlib\plugin.h(81) : error C2516: 'PFactory' : is not a legal base class ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ..\..\..\include\ptlib\plugin.h(115) : see reference to class template instantiation 'PDevicePluginFactory<_Abstract_T,_Key_T>' being compiled ..\..\..\include\ptlib\plugin.h(81) : error C2143: syntax error : missing ',' before '<' ..\..\..\include\ptlib\plugin.h(84) : error C2516: 'PFactory' : is not a legal base class ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ..\..\..\include\ptlib\plugin.h(84) : see reference to class template instantiation 'PDevicePluginFactory<_Abstract_T,_Key_T>::Worker' being compiled ..\..\..\include\ptlib\plugin.h(84) : error C2143: syntax error : missing ',' before '<' ..\..\..\include\ptlib\plugin.h(84) : error C2039: 'WorkerBase' : is not a member of 'operator``global namespace''' ..\..\..\include\ptlib\pfactory.h(475) : error C2904: 'PFactory' : name already used for a template in the current scope ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ..\..\..\include\ptlib\pfactory.h(475) : error C2920: redefinition : 'PFactory' : template class has already been declared as 'typedef int PFactory' ..\..\..\include\ptlib\pfactory.h(475) : see declaration of 'PFactory' ..\..\..\include\ptlib\pprocess.h(819) : see declaration of 'PFactory' ______________________________________________ ¿Chef por primera vez? Sé un mejor Cocinillas. http://es.answers.yahoo.com/info/welcome

2 1

PTLib change to ANSI bool
by Craig Southeren 03 Dec '07

03 Dec '07

To all, As previously announced, the trunk revision of PTLib has been changed to use ANSI bool instead of int BOOL. A summary of the changes, and the reasons and ramifications of them, can found in the Opal wiki at: http://www.opalvoip.org/wiki/index.php?n=Main.BoolChanges 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

回复：回复： Does H323plus support H.235
by Bian 01 Dec '07

01 Dec '07

Simon I think PVX's key exchange mechanism is in a standard way. PVX and Codian MCU can connect using AES. But I don't know how the shared secret is used to produce the session key. Bian > -----Original Message----- >Bian >No PacPhone AES uses a different key exchange mechanism to PVX. Polycom uses >a proprietry method. They should still connect unencrypted. >Simon > -----Original Message----- > From: Bian [mailto:bianxg@yahoo.cn] > Sent: Wednesday, November 28, 2007 12:35 PM > To: Simon Horne > Subject: 回复： [h323plus] Does H323plus support H.235 > > > Simon > > I test PccPhone with PVX, but the AES is not opened. Does > PacPhone can interoperate with PVX using AES? > > > Bian > ___________________________________________________________ 进入雅虎游戏嘉年华，赢取液晶显示器！ http://cn.mail.yahoo.com/promo/carnival07/

2 1

Does H323plus support H.235
by Bian 27 Nov '07

27 Nov '07

ToAll, Does anyone have experience implementing H.235 AES using h.323plus? Where can I begin? Regrads, Bian ___________________________________________________________ @yahoo.cn 新域名、无限量，快来抢注！ http://mail.yahoo.cn/

1 0

Re: [h323plus] Migration to ANSI bool in PTLib
by Craig Southeren 27 Nov '07

27 Nov '07

Simon Horne wrote: > To All > > I had requested slightly more time but alas :( > > h323plus (in conjunction with GnuGk) will migrate over the next week or so. > If you are using the PTLIB TRUNK please compile for backward compatibility > until Jan and I have completed h323plus and GnuGk translation. To assist, we'll try not to do much to PTLib until you are migrated. This means the development snapshot will be good for you to use. > Our apologies for not be able to co-ordinate this a little better. Thanks for your efforts - it is much appreciated :) 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 1

Migration to ANSI bool in PTLib
by Craig Southeren 27 Nov '07

27 Nov '07

To all, As described previously, PTLib is about to migrate the internal type PBoolean the ANSI type "bool". This will affect all member functions that use BOOL parameters and are overrides of standard PTLib and Opal functions. The reasons for this are to improve efficiency, and to improve compatibility with other libraries. Backwards compatibility is supported as follows: - The Unix configure option "--disable-ansi-bool" will enable the old "int BOOL" behaviour - The presence of the symbol P_USE_STANDARD_CXX_BOOL will indicate the new ANSI bool is being used, while the presence of P_USE_INTEGER_BOOL will indicate the old "int BOOL" behavior is in effect. - The new type PBoolean is be defined as either "bool" or "int" as required. The plan for migration to the new code will be in two steps: 1. A snapshot of the SVN current development trunk will be created, that does not include the PBoolean changes (PTLib 2.1.1/Opal 3.1.1) 2. We will then merge the PBoolean changes into the SVN head. This will be (PTLib 2.1.2/Opal 3.1.2) We'd like to do this in the next few days so we can move on to other pressing merge issues (yes Hannes - we are desperate to get your changes in! :) Please email opalvoip-devel(a)lists.sourceforge.net if you have any further questions or issues. Craig

1 0

Re: [h323plus] Visual Studio Express 2008
by Simon Horne 20 Nov '07

20 Nov '07

Jan I have CC'd this to the h323plus list. This is great to have Visual Studio 2008 support. If you get a chance send me the compile errors and will see if we can patch ptlib. :) Simon > -----Original Message----- > From: openh323gk-developer-bounces(a)lists.sourceforge.net > [mailto:openh323gk-developer-bounces@lists.sourceforge.net]On Behalf Of > Jan Willamowius > Sent: Wednesday, November 21, 2007 8:03 AM > To: openh323gk-developer(a)lists.sourceforge.net > Subject: [Openh323gk-developer] Visual Studio Express 2008 > > > Hi, > > for all those who want to try the new Express 2008: > I just compiled PWLib 1.12.0, H323Plus (CVS) and GnuGk (CVS) without > any issues. Just follow the instructions for Express 2005 and let 2008 > convert the build project. > > The only problem I ran into was the PWLib detected the TextToSpeech > API, but couldn't compile the PWlib support for it, so I had to > manually disable it. Your milage on this may vary. > > Regards, > Jan > > -- > Jan Willamowius, jan(a)willamowius.de, http://www.gnugk.org/ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________________ > > List: Openh323gk-developer(a)lists.sourceforge.net > Archive: > http://sourceforge.net/mailarchive/forum.php?forum_name=openh323gk -developer Homepage: http://www.gnugk.org/

2 1

Re: [h323plus] Introducing PBoolean - API change alert!!!
by Jan Willamowius 20 Nov '07

20 Nov '07

Hi, I guess making the change won't be very hard for GnuGk and we've already started using STL wherever possible. The one thing I'm concerend about is to keep backward compatibility with older PWLib releases. Some people use really old OpenH323/PWLib versions to compile GnuGk and would prefer to keep them. Currently we look at the version numbers to see which features are available. So if we can simply define PBoolean back to BOOL for the old releases, I'm fine with the change. If you add config options to change what kind of bool PTLib uses, please give us a config symbol so we can detect what to define PBoolean to. Regards, Jan -- Jan Willamowius, jan(a)willamowius.de, http://www.willamowius.de/

3 3

Improved QoS support in H323plus
by Simon Horne 19 Nov '07

19 Nov '07

To All I have updated QoS support in H323plus. DSCP (Diffserv) is now enabled by default (if compiled with DNS support). Transport QoS is now also negotiated between the parties during the capability exchange with the higher QoS value given precedence over the lower value for both direction media flow. The default values for DSCP are 46 (guaranteed) for audio and 26 (controlled load) for Video. You can change these by calling statics H323AudioCapability::SetDSCPvalue() and H323VideoCapability::SetDSCPvalue() from your application. You can also turn off the feature via a new function H323EndPoint::DisableH245QoS(). Simon No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.503 / Virus Database: 269.16.0/1137 - Release Date: 2007/11/18 5:15 PM

2 2

More background on changing BOOL to bool
by Craig Southeren 19 Nov '07

19 Nov '07

To all, Here is some background information on the proposed change of BOOL to bool. We're trying to move PTLib closer to the C++ standard, including STL, because that has many advantages. Not only will it reduce the size of the code, and increases compatibility with other libraries, but it will leverage off the enormous investment that other developers have made into the standard libraries and will increase the usefulness of PTLib by making the API less "proprietary" To do this, PTLib will require several changes. None of these will come without pain, but it is my personal opinion that the advantages will outweigh the disadvantages. These changes are: - Change BOOL to bool - Change PString to use std::string in some way - Change PArray to use std::vector, PDictionary to use std::map etc The change from BOOL to bool is probably the biggest change. We're hoping that the rest of the changes can be done transparently, but I think it is inevitable that there will be some API tweaks required. I'd be interested in hearing people's opinions on these thoughts, especially if the general consensus is that it is not worthwhile. 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

3 3

Re: [h323plus] Introducing PBoolean - API change alert!!!
by Simon Horne 18 Nov '07

18 Nov '07

Robert Can you explain exactly in simple english 1. What you have changed. I assume it's changing every BOOL to PBOOLEAN in ptlib? 2. So everyone in every program derived from ptlib/pwlib has to change their program or when they compile against upcoming releases of ptlib their program will no longer function properly. Is that correct? For what benefit? Compile time checks? moving from BOOL to ANSI bool? Though I have always wondered why BOOL was used in place of bool and globally replacing in h323plus is fairly easy however for the community as a whole who have developed complex applications from these libraries it's going to be extremely painful as backward compatibility is broken and worse with C++ virtual they will not even notice it has even occurred until they run the program. Not a very good situation at all. For this reason I STRONGLY STRONGLY recommend you don't make this change. IMHO it is something inherent with pwlib/ptlib and far too painful this late in the game (after 10+ years?) for minimal benefit for everyone involved. But of course, it already has been decided and the community have a week to agree and then it's done. This is what is truely unfortunate. Simon -----Original Message----- From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com]On Behalf Of Robert Jongbloed Sent: Monday, November 19, 2007 9:31 AM To: Opalvoip-devel(a)lists.sourceforge.net; h323plus(a)lists.packetizer.com Subject: [h323plus] Introducing PBoolean - API change alert!!! If you have written any programs based on PTLib/OpenH323/H323plus/OPAL, please read this, IT'S IMPORTANT!! Adam Butcher from Selex Communications submitted patches a while ago to change BOOL to PBoolean. The reason was so that PBoolean could be defined as the ANSI standard bool type and we get a whole pile of beneficial compile time checks. The process found a couple of places where a function had a BOOL return type but integer (tri-state) values were being returned! Well, Craig and I had thought of this for a while as being a "good thing" to do, but lack of time has always been an issue. Now, as we have been presented with all the hack work, it seems that this is it's time. Of course things are NEVER easy. The change has a nasty API issue that can silently stop user programs from working. It revolves around my #1 pet hate in C++, if you change the signature of a virtual function, overrides silently no longer override the virtual. For example: //------ in the library class OpalXXX { virtual void SomeFunction( PBoolean ); }; //------- in some unchanged dependent code in another application class MyXXX : public OpalXXX { virtual void SomeFunction( BOOL ); }; The function MyXXX::SomeFunction() will not be called as it should be. And the stupid compiler (NONE of the compilers) give any warnings or indication there is an issue. Way back in the preliminary versions of C++ they did have a keyword "override" which would do exactly what we want, error if the base class does not have the function being overridden as virtual. The original designers (Stroustrup et al) took out, for presumably good reasons, though I cannot for the life of me think what! There is even a number proposals, e.g. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2108.html, to put a variants of it back and Microsoft have even done so, http://msdn2.microsoft.com/en-us/library/41w3sh1c.aspx, on their latest compiler. Anyway we have to deal with existing compilers and this problem is really insidious, but we think the gains are worth the pain. And we have provided a work around for people. So, what we need from you guys is please check out the PTLib and OPAL in the branches: https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/branches/Bo oleanChange https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/branches/Boo leanChange and compile your programs against it. Now by default it will use the ANSI bool form of PBoolean, so any overrides of PTLib or OPAL functions must be changed to use PBoolean instead of BOOL. For those not using MFC, this is really easy, just do a complete search and replace everywhere of BOOL to PBoolean (or better yet, just bool) and that should do the job. Oh, you might like to search and replace TRUE to true and FALSE to false while you are at it, though you don't HAVE to do that. Now, for those that simply do not wish to make these changes, we have a backward compatibility option: use the --disable-ansi-bool option with configure (both Unix and Win32) and PBoolean is defined as BOOL instead of bool. This should (in theory) be 100% compatible with the previous signatures. So no changes to applications based on PTLib need be made. But we need you guys to CHECK THAT THIS IS OK! We are currently proposing to merge it into the trunk on Monday 26th of November, we are happy to extend that if asked, but will not wait forever, the back merging is really painful! P.S. A random note to developers, the PBoolean is only there for backward compatibility. It is recommended that any NEW functions all just use the bool keyword. Use lowercase true and false too. P.P.S. Sorry about all the shouting ... J Robert Jongbloed OPAL/OpenH323 Architect and Co-founder.

2 1

Introducing PBoolean - API change alert!!!
by Robert Jongbloed 18 Nov '07

18 Nov '07

If you have written any programs based on PTLib/OpenH323/H323plus/OPAL, please read this, IT'S IMPORTANT!! Adam Butcher from Selex Communications submitted patches a while ago to change BOOL to PBoolean. The reason was so that PBoolean could be defined as the ANSI standard bool type and we get a whole pile of beneficial compile time checks. The process found a couple of places where a function had a BOOL return type but integer (tri-state) values were being returned! Well, Craig and I had thought of this for a while as being a "good thing" to do, but lack of time has always been an issue. Now, as we have been presented with all the hack work, it seems that this is it's time. Of course things are NEVER easy. The change has a nasty API issue that can silently stop user programs from working. It revolves around my #1 pet hate in C++, if you change the signature of a virtual function, overrides silently no longer override the virtual. For example: //------ in the library class OpalXXX { virtual void SomeFunction( PBoolean ); }; //------- in some unchanged dependent code in another application class MyXXX : public OpalXXX { virtual void SomeFunction( BOOL ); }; The function MyXXX::SomeFunction() will not be called as it should be. And the stupid compiler (NONE of the compilers) give any warnings or indication there is an issue. Way back in the preliminary versions of C++ they did have a keyword "override" which would do exactly what we want, error if the base class does not have the function being overridden as virtual. The original designers (Stroustrup et al) took out, for presumably good reasons, though I cannot for the life of me think what! There is even a number proposals, e.g. http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n2108.html, to put a variants of it back and Microsoft have even done so, http://msdn2.microsoft.com/en-us/library/41w3sh1c.aspx, on their latest compiler. Anyway we have to deal with existing compilers and this problem is really insidious, but we think the gains are worth the pain. And we have provided a work around for people. So, what we need from you guys is please check out the PTLib and OPAL in the branches: https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/ptlib/branches/Boolean Change https://opalvoip.svn.sourceforge.net/svnroot/opalvoip/opal/branches/BooleanC hange and compile your programs against it. Now by default it will use the ANSI bool form of PBoolean, so any overrides of PTLib or OPAL functions must be changed to use PBoolean instead of BOOL. For those not using MFC, this is really easy, just do a complete search and replace everywhere of BOOL to PBoolean (or better yet, just bool) and that should do the job. Oh, you might like to search and replace TRUE to true and FALSE to false while you are at it, though you don't HAVE to do that. Now, for those that simply do not wish to make these changes, we have a backward compatibility option: use the --disable-ansi-bool option with configure (both Unix and Win32) and PBoolean is defined as BOOL instead of bool. This should (in theory) be 100% compatible with the previous signatures. So no changes to applications based on PTLib need be made. But we need you guys to CHECK THAT THIS IS OK! We are currently proposing to merge it into the trunk on Monday 26th of November, we are happy to extend that if asked, but will not wait forever, the back merging is really painful! P.S. A random note to developers, the PBoolean is only there for backward compatibility. It is recommended that any NEW functions all just use the bool keyword. Use lowercase true and false too. P.P.S. Sorry about all the shouting ... J Robert Jongbloed OPAL/OpenH323 Architect and Co-founder.

1 0

OpenAM now available in H323plus CVS
by Simon Horne 18 Nov '07

18 Nov '07

Guys Just a quick note that openAM has now been updated and available in the h323plus CVS. I would like to thank Jan Willamwius for the contribution and hopefully in the not too distant future we can tweak it to provide video voicemail for GnuGk. :-) Simon ----------------------- Simon Horne Principal Maintainer h323plus library www.h323plus.org h323:s.horne@packetizer.com

1 0

Question about interoperability of asterisk and GnuGk
by Giulio Gaio 15 Nov '07

15 Nov '07

Hi, I wonder if is it possible to register Asterisk as an endpoint to openh323 gatekeeper (GnuGk) because i want to merge the feature of an PBX ( asterisk ) in a h323 zone. More precisely, I'm working around an heterogeneous network (it' s a campus' network) in witch to an h323 MCU endpoint had to have the capability to be connected in both: - external PSTN via Cisco Gw users, - internal h323 users registered to GnuGK - user handled by an asterisk PBX. (You can imagine that theese are users from a minor building of the faculty that don't share the LAN of the main building). --- but this point isn't yet clear If some one can help me (Can asterisk register to GnuGK in some way), or tell me this is impossible, Thank you very much. Giulio ___________________________________ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html

5 5

Re: [h323plus] [Opalvoip-devel] Custom Video Frame Size
by Simon Horne 14 Nov '07

14 Nov '07

Robert Firstly I would like to thankyou for the fantastic work you did on upgrading the initial Video Plugin work on the openH323_plugins branch. On to this discussion. I asked a specific question on the removal of the frame size constraints in the encoder of the plugin codec. Now I don't want to break anything so from your indepth response about YUV files and SIP exchange example. I will assume its important so I will just leave it as it is for Opal. :-) Regards Simon -----Original Message----- From: h323plus-bounces(a)lists.packetizer.com [mailto:h323plus-bounces@lists.packetizer.com]On Behalf Of Robert Jongbloed Sent: Wednesday, 7 November 2007 2:15 PM To: Opalvoip-devel(a)lists.sourceforge.net Cc: 'H323plus' Subject: Re: [h323plus] [Opalvoip-devel] Custom Video Frame Size > -----Original Message----- > From: Simon Horne [mailto:s.horne@packetizer.com] .... > Getting back to the initial question. I want to move forward with > H.239 > support in h323plus so can I remove the fixed frame size constraints > from > the video plugins so the project can move forward or if that's not > recommended then, as I don't want to have different versions of the > video > plugins that break interoperability, can I put in a compiler > directive to > get us out of a pickle? Once these opal architectural glitches are > resolved > then the directive can be removed. I am confused, the underlying system in OPAL has never really had any "fixed size" constraints. There are two OpalMediaOptions for width and height and they can be any value. Now come CODECS can only do fixed sizes, eg H.261, and that was part of the complexity Matthias and I were struggling with. > I really am confused on the codec issues, and the discrete video > sizes with > H.261/H.263 and the generic capabilities etc. The way this is done in > H323plus is to detect the capabilities of the video device at > application > startup via the changes I made in the ptlib videodevice factory which > allows > the device capability list to be exposed without instantaneousing the > device. You use the device capabilities list to determine the maximum > frame > size available for the device so in this way you can detect and > support HD > webcams etc. There is a H323Endpoint function that then goes through > and > removes all the capabilities unsupported for that particular webcam. > Easy! If I am reading this right, you are using the capabilities of the camera, which is used for transmit channels, to determine the H.323 capabilities which controls the RECEIVE channels. Surely the capability should use the VideoOutputDevice? Or is this for transmitVideo capabilities only? Also, but what happens if you have a camera that only reports being able to do 320x240? Not sure this happens much anymore, but older cameras certainly used to. Again, if I am reading what you said right, you would not get H.261 or H.263 at all as they can't do that resolution. > On the OpenVideoChannel function callback the user can then set the > frame > size and fps on the wire. This sets the header height/width fields of > the > YUV420 frame which then goes back into the plugin codec to resize the > codec. > This is how it used to work in OpenH323 and it works just fine. The > problem > you refer to is, I guess, an open Opal issue perhaps?. Given recent events I would be VERY careful about gibes like this. Here is the problem as I see it, library neutral ... Leaving out for the moment the added complexity of requiring symmetric codecs, the receive and transmit video streams are completely independent. Let's start with the receiver; there are three entities at work: Video output device capabilities User/Application preferences Codec fundamentals As a rule most output devices can do any resolution/frame rate, however it is possible with the YUVFile driver to indicate that it MUST be a size, e.g. using the filename "fred_qcif.yuv". The User/Application may also have restrictions, most common is for PDA's where the screen size is such that you want to prevent 4CIF etc. The Codec fundamentals are the most complicated as they may just be a maximum (via profile/level for H.264/MPEG4 and CustomPictureFormat for H.263+) or a set of discrete values as required by H.261 and H.263. The presented capabilities sent to the remote must be derived from the above. I am not presenting a solution yet, just trying to state the problem in as complete a form as possible. For the transmit side we have four entities: Video input device capabilities User/Application preferences Codec fundamentals Remote capabilities So, when selecting our specific video parameters we want to try and get as close to the user preference as possible given the constraints indicated by the other three entities. One more random point: the Codec fundamentals are only known by the plug-in. So, the result of a long discussion with Matthias (and others, but Matthias was the main person) we came up with a first cut solution. To simplify matters an assumption that the video devices can be told to go to any resolution is made. As we have the PColourConverter functionality which (mostly) can do scale/crop as it converts, I think that is fair. Then we introduce the concept of "normalised" OpalMediaOptions and "custom" OpalMediaOptions. The normalised options are things like min/max width/height and the custom options are things like profile/level, or "QCIF MPI". Then two functions are to be added to the plug in to set the options in an instance from normalised to custom, and back from custom to normalised options. In the process the plug-in can also apply any other rules it might have, such as discrete sizes. And here is the sequence that I am stealing from the other thread describing how all the OpalMediaOptions get tweaked as they pass through the system: OK, nothing better than a concrete example: Media format on start up from a H.263 plug-in: Max Frame Width = 1408 Max Frame Height = 1152 Min Frame Width = 144 Min Frame Height = 96 Frame Width = 352 Frame Height = 288 Max Bit Rate = 384000 Target Bit Rate = 384000 Frame Time = 3000 SQCIF MPI = 1 QCIF MPI = 1 CIF MPI = 2 4CIF MPI = 3 16CIF MPI = 4 Annex D = 1 Then the user alters the following: Max Frame Width = 640 Max Frame Height = 480 Frame Width = 320 Frame Height = 240 Max Bit Rate = 128000 Frame Time = 6000 Then just before making a call the above, after user adjustment, is sent to the plug-in "from_normalised_options" function, the plug-in returns: Max Frame Width = 352 Max Frame Height = 288 Min Frame Width = 144 Min Frame Height = 96 Frame Width = 176 Frame Height = 144 Max Bit Rate = 128000 Target Bit Rate = 128000 Frame Time = 6000 SQCIF MPI = 2 QCIF MPI = 2 CIF MPI = 2 4CIF MPI = 5 16CIF MPI = 5 Annex D = 1 Note that as this particular H.263 implementation cannot do custom frame sizes, so all the frame sizes are adjusted appropriately. Some MPI's are set to an illegally large value (required for merging to work) and the new frame rate has made the MPI's that are left change upward. This is encoded to: m=video 5002 RTP/AVP 34 a=rtpmap:34 h263/90000 a=fmtp:34 CIF=2;QCIF=2;SQCIF=2;D=1 The remote replies: m=video 5002 RTP/AVP 34 a=rtpmap:34 h263/90000 a=fmtp:34 CIF=3;4CIF=3 I deliberately tried to be a "rude" UA and return a frame size that was never offered to make sure it all works. OPAL then constructs the following from the SDP: Max Frame Width = 640 Max Frame Height = 480 Min Frame Width = 144 Min Frame Height = 96 Frame Width = 320 Frame Height = 240 Max Bit Rate = 128000 Target Bit Rate = 128000 Frame Time = 6000 SQCIF MPI = 5 QCIF MPI = 5 CIF MPI = 3 4CIF MPI = 3 16CIF MPI = 5 Annex D = 0 Many of the above values are irrelevant at this stage and just inherited from the master format. OPAL then merges the sent options with the received options to get: Max Frame Width = 352 Max Frame Height = 288 Min Frame Width = 144 Min Frame Height = 96 Frame Width = 176 Frame Height = 144 Max Bit Rate = 128000 Target Bit Rate = 128000 Frame Time = 6000 SQCIF MPI = 5 QCIF MPI = 5 CIF MPI = 3 4CIF MPI = 5 16CIF MPI = 5 Annex D = 0 Here the MaxMerge operator adjusts the MPI's, and the AndMerge operator turns off Annex D. This is then passed to the plug-in "to_normalised_options" getting: Max Frame Width = 352 Max Frame Height = 288 Min Frame Width = 352 Min Frame Height = 288 Frame Width = 352 Frame Height = 288 Max Bit Rate = 128000 Target Bit Rate = 128000 Frame Time = 9009 SQCIF MPI = 5 QCIF MPI = 5 CIF MPI = 3 4CIF MPI = 5 16CIF MPI = 5 Annex D = 0 Where the Frame Size settles on its only possible value, and Frame Time gets adjusted to 10fps due to CPI MPI being 3. These options are then sent to the codec using set_codec_options and also merged with the YUV320P options so it can be used by the grabber. Robert Jongbloed OPAL/OpenH323 Architect and Co-founder.

3 2