Re: [Wengophone-devel] Certificate Authentication
Hi Leonardo, Leonardo José Reyes Diago wrote: > For example, when i try to enter in: > https://dev.openwengo.org/svn/openwengo/wengophone-ng/trunk > > the navigator ask me if i accept the certificate. There's a domain mismatch in that certificate if you go to the .org address - the certificate was issued with dev.openwengo.com as the domain, and the .org is just an alias. Try using https://dev.openwengo.com/svn/openwengo/wengophone-ng/trunk - you should have the opportunity to accept the certificate permanently the first time you connect, and then you won't have to do so afterwards. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: FW: [Wengophone-devel] Performance Issue
Lukas Oberhuber wrote: Arelien, The patch I attached in the previous message already does what you suggest. I was mostly explaining what I had done, but I guess I didn't make that clear enough. Yes, it does. But I believe my solution is a bit nicer because it does not require adding another parameter to the various add*Item() methods while still ensuring the list is always sorted, without having to call sort() manually. I think my patch is pretty good to go into the code base. The next thing would probably be to work on the encode64 functions. I'm going to give it a look, just haven't had time to do so now. Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
RE: FW: [Wengophone-devel] Performance Issue
Aurelien, I now see what you are saying. Yes, that does look more elegant. I will try to implement (of course for me now it requires unwinding all the patch code so I might tackle a little later). -Lukas Lukas Oberhuber -Original Message- From: Aurélien Gâteau [mailto:[EMAIL PROTECTED] Sent: 19 December 2006 09:47 To: Lukas Oberhuber Cc: 'Jérôme WAGNER'; wengophone-devel@lists.openwengo.com Subject: Re: FW: [Wengophone-devel] Performance Issue Lukas Oberhuber wrote: > Arelien, > > The patch I attached in the previous message already does what you suggest. > I was mostly explaining what I had done, but I guess I didn't make that > clear enough. Yes, it does. But I believe my solution is a bit nicer because it does not require adding another parameter to the various add*Item() methods while still ensuring the list is always sorted, without having to call sort() manually. > I think my patch is pretty good to go into the code base. > > The next thing would probably be to work on the encode64 functions. I'm going to give it a look, just haven't had time to do so now. Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: FW: [Wengophone-devel] Performance Issue
Lukas Oberhuber wrote: Aurelien, I now see what you are saying. Yes, that does look more elegant. I will try to implement (of course for me now it requires unwinding all the patch code so I might tackle a little later). I understand :-/ As far as base64 is concerned, I had a look at it but I do not feel confortable enough with this code to change it myself. Since Tanguy Krotoff is the author of this code, I added him to Cc. I think he will be able to answer better than me. Aurélien ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Certificate Authentication
Thanks. In WengoAccount.cpp, the method discoverForSSO and the method discoverForSIP, try two ways to connect the server, with SSL and without SSL. If i want to connect with SSL i need a certificate to access the server. My question was, how i can add the certificate in the code of the softphone. Leonardo Reyes On 12/19/06, Dave Neary <[EMAIL PROTECTED]> wrote: Hi Leonardo, Leonardo José Reyes Diago wrote: > For example, when i try to enter in: > https://dev.openwengo.org/svn/openwengo/wengophone-ng/trunk > > the navigator ask me if i accept the certificate. There's a domain mismatch in that certificate if you go to the .org address - the certificate was issued with dev.openwengo.com as the domain, and the .org is just an alias. Try using https://dev.openwengo.com/svn/openwengo/wengophone-ng/trunk - you should have the opportunity to accept the certificate permanently the first time you connect, and then you won't have to do so afterwards. Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
RE: [Wengophone-devel] Portaudio
On Tue, 2006-12-19 at 12:59 +0100, Jerome WAGNER wrote: > One of the lurking ideas would be to code a separate sound API which both > phapi and the core NG would use. > > This could help a lot in the sharing of all audio resources between the 2 > worlds. > > No work has started on this yet, but I know mstute and pbernery have already > given it some thoughts. > > The same problem arises when you try to RING on an audio device using ALSA > on Linux. Phapi has already taken control of the device so the core NG > cannot play a ringing tone. > > Do you know of a clean pattern (an example of code in another project) where > "sharing a mutex" is done in a clean way ? > > The idea of pbernery and mstute was to force both libraries (phapi and the > NG model) to use a third library where the locks could be enforced in a > clean way. Yes, I agree. By "sharing a mutex" I meant a wrapper around portaudio, that would make it thread safe. Both AudioDeviceManager and phapi should use this wrapper (and so the same mutex). Would this wrapper be like your "third library", or were you thinking about something more complex? Maybe some wrapper around all usable audio libraries (eg for Mac)? Bye, Ludovico ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] warnings during wengophone 2.1 compilation
hi, when i compile wengophone 2.1 i have those error messages : :1:4: warning: missing whitespace after the macro name :1:4: warning: missing whitespace after the macro name Can someone explain me what they are and how to remove them ? thanks in advance Nicolas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
RE: [Wengophone-devel] Executable
-Original Message- From: Jaya Meghani Sent: Tuesday, December 19, 2006 9:33 AM To: 'Tanguy Krotoff' Subject: RE: [Wengophone-devel] Executable Yes, I am using VC++8.0 and NG/trunk branch... Thanks. -Original Message- From: Tanguy Krotoff [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 19, 2006 4:43 AM To: Jaya Meghani Cc: wengophone-devel@lists.openwengo.com Subject: Re: [Wengophone-devel] Executable which branch do you use? are you still using VC++8.0? -- Tanguy Krotoff <[EMAIL PROTECTED]> http://openwengo.org ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Compiling Wengo NG : config.h ?
I continue trying to compile wengo and now it reports me this error: c:\dev\trunk\wifo\srtp\include\err.h(49) : fatal error C1083: No se puede abrir el archivo incluir: 'config.h': No such file or directory scons: *** [release-symbols\wifo\sVoIP\src\crypto.obj] Error 2 scons: building terminated because of errors. What's the problem Thank you all. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
RE: [Wengophone-devel] Executable
Can any one please hepl for this error. Thanks, Jaya From: Ngo Duc Loi [mailto:[EMAIL PROTECTED] Sent: Monday, December 18, 2006 10:26 PM To: Jaya Meghani; Tanguy Krotoff Cc: wengophone-devel@lists.openwengo.com Subject: RE: [Wengophone-devel] Executable Dear Tanguy, and Jaya, When i execute the FIRST COMAND: "scons qtwengophone qtwengophone-translations owcrashreport wenboxplugin phspeexplugin phamrplugin multiimwrapper=1 phapiwrapper=0 mode=release nobuildid=0" I PASSED and DO NOT meet any error. When i execute the SECOND COMMAND, I meet these error Install file: "wengophone\src\presentation\qt\qtwengophone.pdb" as "release-symb ols\qtwengophone.pdb" scons: *** unsupported operand type(s) for +: 'NoneType' and 'str' scons: building terminated because of errors. I thinks, the command try to combine the 'NoneType' variance and 'str' variance, so they DONT know how to do, Pls tell me how to correct it, Thanks in AdVance, Loi Ngo Jaya Meghani <[EMAIL PROTECTED]> wrote: Hi, I executed the first line scons qtwengophone qtwengophone-translations owcrashreport wenboxplugin phspeexplugin phamrplugin multiimwrapper=1 phapiwrapper=0 mode=release nobuildid=0 I get following error: Install file: "release-symbols\libs\wenbox\src\yealink\wenboxplugin.dll" as "release-symbols\wenboxplugin.dll" Install file: "release-symbols\libs\wenbox\src\yealink\wenboxplugin.lib" as "release-symbols\wenboxplugin.lib" scons: *** [release-symbols\wenboxplugin.lib] Exception Traceback (most recent call last): File "C:\Python24\scons\SCons\Taskmaster.py", line 101, in execute self.targets[0].build() File "C:\Python24\scons\SCons\Node\__init__.py", line 201, in build apply(executor, (self, errfunc), kw) File "C:\Python24\scons\SCons\Executor.py", line 115, in __call__ apply(action, (self.targets, self.sources, env, errfunc), kw) File "C:\Python24\scons\SCons\Action.py", line 243, in __call__ stat = self.execute(target, source, env) File "C:\Python24\scons\SCons\Action.py", line 512, in execute return self.execfunction(target=target, source=rsources, env=env) File "C:\Python24\scons\SCons\Environment.py", line 82, in installFunc return install(target[0].path, source[0].path, env) File "C:\Python24\scons\SCons\Defaults.py", line 219, in copyFunc shutil.copy2(source, dest) File "C:\Python24\lib\shutil.py", line 92, in copy2 copyfile(src, dst) File "C:\Python24\lib\shutil.py", line 47, in copyfile fsrc = open(src, 'rb') IOError: [Errno 2] No such file or directory: 'release-symbols\\libs\\wenbox\\src\\yealink\\wenboxplugin.lib' scons: building terminated because of errors. You mentioned something about "Read the NSIS script to understand which dll are copied/needed" I didn't get it. Please excuse me for this I am new to SCONS. Very kind of you to help. Thanks, Jaya -Original Message- From: Tanguy Krotoff [mailto:[EMAIL PROTECTED] Sent: Monday, December 18, 2006 12:34 PM To: Tanguy Krotoff Cc: Jaya Meghani; Dave Neary; Tanguy Krotoff; wengophone-devel@lists.openwengo.com Subject: Re: [Wengophone-devel] Executable Tanguy Krotoff wrote: > scons qtwengophone qtwengophone-translations owcrashreport > wenboxplugin phspeexplugin phamrplugin multiimwrapper=1 phapiwrapper=0 > mode=release nobuildid=0" forgot the 2nd line: scons qtwengophone-nsis-installer qtwengophone-nsis-installer-without-pdb owcrashreport wenboxplugin multiimwrapper=1 phapiwrapper=0 mode=release nobuildid=0" this creates the setup*.exe package with all the dll inside. Read the NSIS script to understand which dll are copied/needed -- Tanguy Krotoff http://openwengo.org ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Compile issues and OpenWengo
Hi, It's clear from the various mails to the mailing list (and the activity on IRC) that compilation issues are the biggest barrier to entry that people have to the project at the moment. I would like to get everyone to put some effort into documenting the compilation of the Wengophone in the various configurations possible - some of this information won't have been written down yet, but a lot of the information is probably there somewhere. So - here's the current configuration of the Wengophone: 3 primary platforms (Windows, Mac, Linux) 3 active branches (trunk, 2.0, 2.1) 2 active build systems (scons, cmake) For each platform and branch, we should document whether the reccommended build system is scons or cmake. The objective is to remove scons support from trunk and the 2.1 branch altogether. Platform | | | | ---. | Win32 | Mac | Linux | Branch \| | | | -+---+---+---+ trunk| cmake | | | -+---+---+---+ 2.0 | scons | | scons | -+---+---+---+ 2.1 | cmake | | | -+---+---+---+ I'm not sure of the status on the blank squares - and I'm open to correction for the ones I've filled in. In Windows: (I'm afraid I'm no help here) What are the supported build environments? What special steps are required for each environment? What are the dependencies needed? Where can we get them? Which versions of the OS are supported? mingw? VC++? VisualStudio? Targets: Building the Wengophone Building an NSIS installer (is this possible & tested with cmake?) In Mac: What's the recommended development platform? XCode? What are the dependencies? Are there any special steps required? Linux: Are there compiler versions to avoid? (gcc 4.1 & boost) What are the dependencies? Where can I get them for each distribution? What special hacks do I need to do to install the phone? How can I generate a binary package? Main distributions (if we support these properly, the others will not be a problem): Debian Etch Debian testing Ubuntu 6.06 Ubuntu 6.10 Ubuntu testing Fedora Core 4 Fedora Core 5 RedHat Enterprise 5 SLED 10 OpenSuse 10.2 Mandriva 2007 Mandriva Cooker What architectures do we support? Do we have a list of 64 bit issues? How have people resolved their 64 bit build issues? If we can come up with one, or a series, of documents which answer all these questions, then it'll be considerably easier for people to get involved in this project. A good start will be to collect each of the build issues that have come up on the mailing list over the past few days, and start working on a FAQ. Does anyone have some time to help me with this? Cheers, Dave. -- Dave Neary OpenWengo Community Development Manager Email: [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Compiling Wengo NG : config.h ?
Hi Le mardi 19 décembre 2006 à 18:09 +0100, Gorka Pinillos a écrit : > I continue trying to compile wengo and now it reports me this error: > > c:\dev\trunk\wifo\srtp\include\err.h(49) : fatal error C1083: No se > puede abrir > el archivo incluir: 'config.h': No such file or directory > scons: *** [release-symbols\wifo\sVoIP\src\crypto.obj] Error 2 > scons: building terminated because of errors. > > What's the problem > Thank you all. The problem is from the rev 8909 I think. You use scons for compilation and this changeset introduce the generation of the config.h in the srtp library by the cmake construct system. Cmake generate this file from a template with correct values for all plateform supported by openwengo. This remplace a static config.h file only suitable for Windows plateform. So if you really need scons it's a bug that you can report, if not use cmake instead. Regards. Didier Link -- Didier Link <[EMAIL PROTECTED]> Jabber : [EMAIL PROTECTED] MSN : [EMAIL PROTECTED] Clé GPG : 75BAC9EE signature.asc Description: Ceci est une partie de message numériquement signée ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Compiling Wengo NG : config.h ?
Didier LINK wrote: > Hi > > Le mardi 19 décembre 2006 à 18:09 +0100, Gorka Pinillos a écrit : >> I continue trying to compile wengo and now it reports me this error: >> >> c:\dev\trunk\wifo\srtp\include\err.h(49) : fatal error C1083: No se >> puede abrir >> el archivo incluir: 'config.h': No such file or directory >> scons: *** [release-symbols\wifo\sVoIP\src\crypto.obj] Error 2 >> scons: building terminated because of errors. >> >> What's the problem >> Thank you all. > > The problem is from the rev 8909 I think. > > You use scons for compilation and this changeset introduce the > generation of the config.h in the srtp library by the cmake construct > system. > > Cmake generate this file from a template with correct values for all > plateform supported by openwengo. This remplace a static config.h file > only suitable for Windows plateform. > > So if you really need scons it's a bug that you can report, if not use > cmake instead. SCons will be removed from trunk soon. I don't think that the bug will be fixed, cause the static config.h was the bug :) -- andreas > > Regards. > > Didier Link > > > > > > ___ > Wengophone-devel mailing list > Wengophone-devel@lists.openwengo.com > http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
