- h323plus - lists.packetizer.com

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 04 Dec '07

04 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