Re: [Wengophone-devel] Qutecom
At first I would decrease the font size. And I think it is better to spend time adding content as to spend time for making a new theme. regards klaus Gustavo A. Díaz schrieb: Hi, I have graphics/art skills, so if you need to improve Joomla Theme, maybe I could help :) Cheers. 2008/3/20, Vadim Lebedev [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: Andreas Schneider wrote: Hi Vadim, I miss a simple html page on qutecom.org http://qutecom.org pointing out that it is a fork of wengophone and how to checkout the latest version with hg. If there is no progress with the page and new mailing list there should be at least some information on the page. -- andreas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com mailto:Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel Folks, Finally i've resolved problems i had with the new mailing-list qutecom-dev I'll do bulk inscription of current wengophone-devel members later today... So everybody will get a welcome message from the new list. I've have VERY preliminary version of new home page for qutecom but i'm VERY bad on web design so i am ashamed to publish it :( If somebody willing to take a look at www.qutecom.org/joomla http://www.qutecom.org/joomla and is ready to improve it please conatct me for admin password. It is done with joomla Thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com mailto:Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Gustavo A. Díaz GDNet Projects www.gdnet.com.ar http://www.gdnet.com.ar ___ 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
Re: [Wengophone-devel] Exceptions when Debugging with MS VS 2003 / 2005
I recently had this error message in another application in this scenario: 1. malloc a buffer 2. write into the buffer too much data (buffer overflow) 3. free the buffer -- here at this point I got this error message maybe it is similar in your case. regards klaus J. Christopher Pereira Z. schrieb: Hi: When debuging Wengo and Qutecom in MS VS 2003 and 2005, I allways get this message: Windows has triggered a breakpoint in hola.exe. This may be due to a corruption of the heap, and indicates a bug in hola.exe or any of the DLLs it has loaded. The output window may have more diagnostic information AFAIR, in 2003 the message was different (I guess it was called an exception). When triggered, Qutecom stops debugging just like a breakpoint. Does anybody now why this happens and how to avoid it? J. Christopher Pereira Area Informática IMATRONIX S.A. www.imatronix.com http://www.imatronix.com (+56) (9) 8573 4518 (+56) (32) 2 76 80 77 I am using the free version of SPAMfighter for private users. It has removed 35011 spam emails to date. Paying users do not have this message in their emails. Try SPAMfighter http://www.spamfighter.com/len for free now! ___ 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
Re: [Wengophone-devel] Special Chat info: Can we turn it off?
IMO this is a problem/bug of the SMS Gateway. IF the content-type is not text/plain or text/html it should ignore the MESSAGEs. The typing messages usually use a different content-type. regards klaus klaus Ralf Schlatterbeck wrote: Seems like the chat from wengo (via SIP/SIMPLE) is sending all sorts of meta-information to the peer. We have an SMS-Gateway here (accepting SIP/SIMPLE messages which are sent out to a mobile phone), where I sent two messages: - Hallo - Diese Message via [EMAIL PROTECTED] --vg Ralf This resulted in 22 (!) SMS to the target: - Hallo - is not typing (multiple times) - is typing (multiple times) - stops typing (multiple times) - Diese Message via [EMAIL PROTECTED] --vg Ralf - stops typing Can we somehow get rid of the meta-information (maybe as a config-option)? This will probably also irritate other SIP/SIMPLE peers? Ralf ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] buildbot scripts
Vadim Lebedev schrieb: Klaus Darilion wrote: Andreas Schneider schrieb: Klaus Darilion wrote: Hi Andreas! Hi Klaus, I tried to find out something about the mentioned AMR mode in speex, but could not find any information. Do you have more information about this? sorry wengophone's phapi has this mode. Search for PH_SPEEXWB_REPLACES_AMRWB in wifo. btw: does OW support AMR-NB too? Which mode - bandwidth-efficient or octed-aligend mode? regards klaus Folks on this AMR issue phapi supports AMR NB and WB as a plugin module Does this mean that there is an AMR plugin available? part of OW? klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] buildbot scripts
Andreas Schneider schrieb: Klaus Darilion wrote: Hi Andreas! Hi Klaus, I tried to find out something about the mentioned AMR mode in speex, but could not find any information. Do you have more information about this? sorry wengophone's phapi has this mode. Search for PH_SPEEXWB_REPLACES_AMRWB in wifo. btw: does OW support AMR-NB too? Which mode - bandwidth-efficient or octed-aligend mode? regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] G3 calls
I once tried with Asterisk and patches from sip.fontventa.com but video did not worked (I can't remember the details). Currently AFAIK only eyebeam/xlite works fine with Asterisk. regards klaus Vadim Lebedev schrieb: Roland Alton-Scheidl wrote: Some background information: osAlliance got some funding from a mobile phone operator (A1.net). Hi Roland, I'm very interested to know if you manage to place succesful video calls to G3 phones using wengophone Thanks Vadim ___ 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
Re: [Wengophone-devel] Openwengo REPO conversion
Vadim Lebedev schrieb: Hello I wonder if somebdoy can share experienc with conversion of OpenWeng repo to git or mercurial Not directly the answer you want to here, but maybe still interesting. I made a snapshot of the wengo SVN using this method: http://kev.coolcavemen.com/2007/04/how-to-backup-mirror-a-public-svn-repository/ klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: Why is it so calm
michel memeteau schrieb: Hi all ! Wengo has to carry on as it was about to become one of the standards Sip softphone on major OSes. 2008/1/6, Tanguy Krotoff [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]: On Jan 6, 2008 7:16 PM, Patrick Aljord [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Well, people using Windows and MacOS X don't care about using a 100% FOSS VoIP solution Maybe people under Linux care about communicate with their friends under Windows or MacOS X And this can be achieved easily if the same software can be used on different OS don't you think? the main problem with SIP today is that we don't have a click n Run friendly standard solution on Windows Mac OSX. Linux is full of great SIP solution , So for once I would not be too ashamed if Wengo for Linux was a bit less achieved. people on Linux have already Full friendly supported solution with several software ( Pidgin/Gajim for IM ; Ekiga for audio/video ) I recently tested IM with Pidgin and GAIM and IMO those SIP implementations are very bad. the Main problem is how to use existing Linux SIP solutions with friends on Windows mac ; OW was about to become THE solution , just few bugs still to correct ... BTW , the wengo company still advertise to its wengo experts to receive their calls on Wengophone , so it's still part of their businesss even if their flash interface might work even better than Wengo ( but takes 100% cpu all the time ! Flash effect ) , SO I think it would be the least for Wengo to keep up the hosting for the project ! For neuf/Wengo such hosting is nothing compared to other expenses .. isn't it ? If Wengo wont support OW anymore IMO it should be move to some other place (sourceforge, goggle code, novell forge, savannah, berlios ...) regards Klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] AMR questions
Andreas Schneider schrieb: Klaus Darilion wrote: Hi! I wonder how you deal with AMR license restrictions - does Wengo pays for the AMR license or is it the users task to get an AMR license? Hello, WengoPhone is developed in Europe, so we don't have any software patents here. If the user lives in a country which has software patents like the USA, the user needs a license to use WengoPhone. I do not think it is a software patent. I think the AMR patent is about the way how speech samples are compressed - and not how this encoding/decoding is done in a certain software ways. klaus This is a problem we should discuss. http://www.penguin.cz/~utx/amr states: AMR codecs incorporate several patents, held by Ericsson, Universite de Sherbrooke (VoiceAge) and Nokia. VoiceAge claims to provide patent portfolio for AMR codecs. Depending on law in your country, manufacturers and developers may need to get a license. Because it is a shared library, you may need a special contract for each one application, which links against this library, directly or indirectly. -- andreas ___ 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] AMR questions
Hi! I wonder how you deal with AMR license restrictions - does Wengo pays for the AMR license or is it the users task to get an AMR license? Further, does Openwengo also support octet-aligned mode? HAve you testet AMR compatibility with other AMR capable clients (Nokia E-series, Asterisk)? regards Klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Shouldn't include Route header in a REGISTER
Hi! Is is called a pre-defined route set. Although in this case the Route header is not necessary it is still valid. In your case, adding alias=mydomain.com to openser.cfg should solve your problems. (Because loose_route() will detect that the Route is itself, will remove the route header and then return false) regards klaus Iñaki Baz Castillo schrieb: Hi, I reported some days ago a bug in 2.1.2 version about a wrong Route header in the REGISTER message when using a non Wengo SIP accont. Because there have not been replies (not for any of the bug/suggestion I've reported) I'd like to tell it here since IMHO is an important issue: http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/1793 Regards. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] WengoPhone 2.1.1 release
Hi Dave - maybe I'm only failing in the configuration. In the Account settings, there are the following fields: login/username: I guess this is the username in the SIP AoR (public SIP URI) Password: the password SIP Domain/Realm: I guess this is the domain part in the SIP AoR (public SIP URI) - which is usually also used as authentication realm Displayname: the displayname in the From: header Advanced: Server: Proxy:Port I do not fully understand the meaning of the advanced section. Usually, the SIP domain should be enough - the client makes SRV lookups and gets the hostname and port of the SIP proxy. Sometimes, if a SIP client does not support SRV lookups or you want to manually route the SIP requests to a certain host/IPaddress you may also want to configure an outbound proxy. I guess this is what the Server/Proxy settings are for. But, sending to an outbound proxy should not change the domains in the SIP message. E.g, when I configure my SIP Account (sip:[EMAIL PROTECTED]) and leave the advanced section unchanged, then the SIP request is fine: REGISTER sip:nic.at43.at SIP/2.0 Via: SIP/2.0/UDP 10.10.0.50:5060;rport;branch=z9hG4bK2311978858 Route: sip:nic.at43.at:5060;lr From: sip:[EMAIL PROTECTED];tag=3773126573 To: sip:[EMAIL PROTECTED] Call-ID: [EMAIL PROTECTED] CSeq: 3 REGISTER Contact: sip:[EMAIL PROTECTED]:5060 Max-Forwards: 70 User-Agent: wengo/v1/wengophoneng/wengo/rev11668/trunk/ Expires: 0 Content-Length: 0 Then I configure in the advanced section an outbound proxy. Server: 83.136.32.160 Proxy: 83.136.32.160 Port 5060 In this case Openwengo sends the request to 83.136.32.160 with wrong headers: U 2007/07/12 10:55:09.411616 83.136.33.3:5060 - 83.136.32.160:5060 REGISTER sip:83.136.32.160 SIP/2.0 Via: SIP/2.0/UDP 10.10.0.50:5060;rport;branch=z9hG4bK3412740584 Route: sip:83.136.32.160:5060;lr From: sip:[EMAIL PROTECTED];tag=290849598 To: sip:[EMAIL PROTECTED] Call-ID: [EMAIL PROTECTED] CSeq: 1 REGISTER Contact: sip:[EMAIL PROTECTED]:5060 Max-Forwards: 70 User-Agent: wengo/v1/wengophoneng/wengo/rev11668/trunk/ Expires: 2940 Content-Length: 0 If the Server/Proxy settings are intended as outbound proxy settings, then they should only change the destination where the request is sent to and optional add a route header - but never change the RURI, From-URI and To-URI. Further I often see strange requests with user nobody. This nobody stuff is maybe again a proprietary wengo thing which I have no clue what is it good for. REGISTER sip:5.6.7.8 SIP/2.0 Via: SIP/2.0/UDP 10.10.0.50:5060;rport;branch=123456789 Route: sip:5.6.7.8;lr From: nobody sip:[EMAIL PROTECTED];tag=123456789 To: sip:[EMAIL PROTECTED] Call-ID: [EMAIL PROTECTED] Contact: sip:[EMAIL PROTECTED] CSeq: 2 REGISTER Content-Length: 0 regards klaus Dave Neary wrote: Hi Klaus, Klaus Darilion wrote: I configure openwengo for my SIP proxy: domain/realm: mydomain.foo Then I activate advanced section and set: server: mydomain.foo proxy: sip.mydomain.foo port 5060 [x] send via proxy But the REGISTER sent by openwengo to sip.mydomain.foo also uses sip.mydomain.foo in the RURI and in From: and To: instead of just using mydomain.foo. Just to be sure I understand what you're saying: You're expecting the REGISTER to use the SIP _server_ in From: and To: and it's using the proxy? (Not the realm) I don't know enough about the SIP protocol yet to know if the behaviour you expect is the correct behaviour - I'll let someone else (Minh?) comment on that. Cheers, Dave. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] WengoPhone 2.1.1 release
Don't know if this is a new bug or was also in older release. I configure openwengo for my SIP proxy: domain/realm: mydomain.foo Then I activate advanced section and set: server: mydomain.foo proxy: sip.mydomain.foo port 5060 [x] send via proxy But the REGISTER sent by openwengo to sip.mydomain.foo also uses sip.mydomain.foo in the RURI and in From: and To: instead of just using mydomain.foo. regards klaus Dave Neary wrote: Hi, The WengoPhone 2.1.1 from the OpenWengo project is now available for download. This is a bugfix release of the 2.1 series of the WengoPhone, which fixes a number of important problems, and updates the translations of 13 languages, bringing the number of fully translated languages to 15. OpenWengo is a project aimed toward providing the best possible communication over IP program, both easy to use and conforming to industry standards. The WengoPhone is an easy to use, fully-features softphone based on the SIP protocol, supporting multiple IM protocols, as well as providing support for PSTN calls and sending SMSes. A detailed list of the changes in this release is included below, and more information on contributing to the OpenWengo project, including the project's bug tracker, is available at http://dev.openwengo.org and more information about OpenWengo can be found at http://www.openwengo.org Source code, and binary releases for GNU/Linux, Windows and Mac are available for download: Sources: http://download.wengo.com/nightlybuilds/universal/sources/openwengo/2.1.1/wengophone-2.1.1.tar.bz2 MD5: http://download.wengo.com/nightlybuilds/universal/sources/openwengo/2.1.1/wengophone-2.1.1.md5 Windows: http://download.wengo.com/wengophone/release/2007-06-27/WengoPhone-2.1.1.exe Mac OS X: (Intel) http://download.wengo.com/wengophone/release/2007-06-27/WengoPhone-2.1.1-macosx-x86.dmg (PPC) http://download.wengo.com/wengophone/release/2007-06-27/WengoPhone-2.1.1-macosx-ppc.dmg GNU/Linux: (PortAudio build) http://download.wengo.com/wengophone/release/2007-06-27/WengoPhone-2.1.1-linux-bin-x86.tar.bz2 (Direct ALSA build) http://download.wengo.com/wengophone/release/2007-06-27/WengoPhone-2.1.1-linux-bin-alsa.tar.bz2 Changes in the 2.1.1 release: * Remove scons support * Moved build documentation from the wiki into the source tree * Avoid crash when deleting IM accounts (ticket #1665) * Fix problem with parsing of smileys in HTML tags (ticket #1671) * Add V4L palette fallback (ticket #1417) * Fix deadlock if we fail to connect to a SIP server (ticket #1662) * Fix some URLs for the Wengo platform * Avoid closing all QT apps during nsis install on Windows (ticket #1691) * Fix a deadlock on first launch of the application and switching profile * Modify configuration format to fix importation of Classic profiles * Update translations for Hebrew, Galicien, Czech, Dutch, Polish, Slovene, Kurdish, Turkish, Cantonese, Esperanto, Finnish, simplified Chinese and Danish Many thanks to Sam Revitch, Aurélien Gateau, Thomas Monjalon, Mathieu Stute, Julien Bossart, Quang Minh Phan, Dave Neary, Jérôme Wagner and the translators of Launchpad for their contributions to this release! Cheers, Dave. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Wengophone on web page - Qt and ActiveX?
Hi Vadim! Take a look at www.mbdsys.com/opensource/veronix Do you have any binaries available (for veronix or phclickdial)? regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Server resident contact list
Vadim Lebedev wrote: Hello, I've started to work on implementation of srever-resident contact list... Which protocol do you use for storing/retrieving? XCAP? (like eyebeam) regards klaus So I've dived into 2.1 sources and frankly my mind start boiling a little :):) Would some charitable soul explain (or point to existing explanation) me relationship between Profile, ProfileManager, Account, Contact, ContactList, ImContact ? Thanks a lot Vadim ___ 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
Re: [Wengophone-devel] Server resident contact list
Hi Vadim! Todes RFC 4662 also describes how the resources can be changed or is it only to inform about changes in the resource? regards klaus Vadim Lebedev wrote: Klaus Darilion wrote: Vadim Lebedev wrote: Hello, I've started to work on implementation of srever-resident contact list... Which protocol do you use for storing/retrieving? XCAP? (like eyebeam) Klaus, Not it based on RFC 4662 thanks Vadim ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] WengoPhone-2.1-rc2 and STUN
Hi! I've just installed WengoPhone-2.1-rc2 and wonder if STUN should work (using my own SIP proxy). I've also played around with network.nat.type settings but Ow does not use STUN. How can I activate STUN? thanks klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] SIMPLE compatibility
Hi! Have you ever tested OW's SIMPLe implementation with other SIP clients? I just tried it against eyebeam and eyebeam refuses the XML payload from OW: [07-04-20]10:16:10.689 | Error | Contacts | Pasing of Presence XML failed: Contact(DN:klaus3, URI: sip:[EMAIL PROTECTED]) Pres: , xml: ?xml version=1.0 encoding=UTF-8? presence entity=sip:[EMAIL PROTECTED] tuple id=azersdqre statusbasicopen/basicnoteDo Not Disturb/note/status contact priority=1sip:[EMAIL PROTECTED]/contact /tuple /presence | sua::CABPresenceSinkSip::ParseSingleContent FYI - this is the payload from OW: ?xml version=1.0 encoding=UTF-8? presence entity=sip:[EMAIL PROTECTED] tuple id=azersdqre statusbasicopen/basicnoteDo Not Disturb/note/status contact priority=1sip:[EMAIL PROTECTED]/contact /tuple /presence This is the payload from a PUBLISH from eyebeam. ?xml version='1.0' encoding='UTF-8'? presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity='sip:[EMAIL PROTECTED]' tuple id='tf135ab13' statusbasicopen/basic/status /tuple dm:person id='p0f475011' rpid:activitiesrpid:busy//rpid:activities dm:noteBusy/dm:note /dm:person /presence regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] SIMPLE compatibility
Hi! I've currently tested openser's new presence module (in version 1.2) with eyebeam 1.5, xlite 3.0 and kphonesi (from cvs) and everything works fine. Even XCAP works with xcap-lite. regards klaus Minh Phan wrote: Hi Klaus, We bought an Eyebeam version more than 2 years ago just to test the presence support with our SIP presence server. However, because the softphone crashed often and send mal-formed packets that we stoped trying. I don't know if it works better now but we haven't tried to support it again since then. Regards, Minh -Original Message- From: [EMAIL PROTECTED] [mailto:wengophone- [EMAIL PROTECTED] On Behalf Of Klaus Darilion Sent: vendredi 20 avril 2007 10:43 To: wengophone-devel@lists.openwengo.com Subject: [Wengophone-devel] SIMPLE compatibility Hi! Have you ever tested OW's SIMPLe implementation with other SIP clients? I just tried it against eyebeam and eyebeam refuses the XML payload from OW: [07-04-20]10:16:10.689 | Error | Contacts | Pasing of Presence XML failed: Contact(DN:klaus3, URI: sip:[EMAIL PROTECTED]) Pres: , xml: ?xml version=1.0 encoding=UTF-8? presence entity=sip:[EMAIL PROTECTED] tuple id=azersdqre statusbasicopen/basicnoteDo Not Disturb/note/status contact priority=1sip:[EMAIL PROTECTED]/contact /tuple /presence | sua::CABPresenceSinkSip::ParseSingleContent FYI - this is the payload from OW: ?xml version=1.0 encoding=UTF-8? presence entity=sip:[EMAIL PROTECTED] tuple id=azersdqre statusbasicopen/basicnoteDo Not Disturb/note/status contact priority=1sip:[EMAIL PROTECTED]/contact /tuple /presence This is the payload from a PUBLISH from eyebeam. ?xml version='1.0' encoding='UTF-8'? presence xmlns='urn:ietf:params:xml:ns:pidf' xmlns:dm='urn:ietf:params:xml:ns:pidf:data-model' xmlns:rpid='urn:ietf:params:xml:ns:pidf:rpid' xmlns:c='urn:ietf:params:xml:ns:pidf:cipid' entity='sip:[EMAIL PROTECTED]' tuple id='tf135ab13' statusbasicopen/basic/status /tuple dm:person id='p0f475011' rpid:activitiesrpid:busy//rpid:activities dm:noteBusy/dm:note /dm:person /presence regards klaus ___ 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
Re: [Wengophone-devel] Help with Wengophone part 2
Jérôme WAGNER wrote: Hello, This is a corner case of the network discovery algorithm : If the stun server cannot help (because it is offline for example), then we decide that the user is in the worst case scenario: full cone. Worst case is symmetric NAT, in which the client is not able to perform NAT traversal itself. Then the client should use private IP addresses in the SIP messages so that the SIP proxy can detect this NATed client and perform server-side NAT traversal. regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] roadmap and ideas
Jérôme WAGNER wrote: Hello, - Packaging - Bug screening - QA - Portability - Interoperability - Features Support for Location and Emergency Call Routing would be great. This includes several steps: 1. Getting the location. This can be done for example with DHCP Geo coordinates: http://ietf.org/rfc/rfc3825.txt http://www.ietf.org/internet-drafts/draft-schnizlein-geopriv-binary-lci-00.txt civil coordinates http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-09.txt or via L7 protocols like HELD or RELO: http://tools.ietf.org/wg/geopriv/draft-schulzrinne-geopriv-relo-00.txt http://www.ietf.org/internet-drafts/draft-winterbottom-http-location-delivery-03.txt 2. The next step would be to map an emergency service URN to the responsible PSAP (public safety access point). Possible service URNs are defined in http://www.ietf.org/internet-drafts/draft-ietf-ecrit-service-urn-05.txt This will be mapped to PSAP URIs (using the current location as input) using the LOST protocol (Probably there will be LOST servers provided for example by government): http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-01.txt 3. The SIP client will call the URI received from LOST and providing its location either using location-by-reference using the Geolocation header defined in http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-04.txt or sending the location as PIDF-LO object using a second body in the INVITE message: http://www.rfc-editor.org/rfc/rfc4119.txt I think this would be feature where openwengo could stand out from the crowd of other SIP phones. regards klaus - Communication over IP - Documentation - Construction tool - Audio optimization Feel free also to mention ideas that do not fit in these ;-) Thank you Jerome Ps: don’t bother mentioning the points from the thread “Things which should happen directly after2.0”. I am compiling them just now. ___ 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
Re: [Wengophone-devel] roadmap and ideas
On Thu, October 12, 2006 17:46, Gianluca Sforna said: On 10/12/06, Klaus Darilion [EMAIL PROTECTED] wrote: Support for Location and Emergency Call Routing would be great. This includes several steps: 1. Getting the location. This can be done for example with DHCP Geo coordinates: http://ietf.org/rfc/rfc3825.txt http://www.ietf.org/internet-drafts/draft-schnizlein-geopriv-binary-lci-00.txt civil coordinates http://www.ietf.org/internet-drafts/draft-ietf-geopriv-dhcp-civil-09.txt or via L7 protocols like HELD or RELO: http://tools.ietf.org/wg/geopriv/draft-schulzrinne-geopriv-relo-00.txt http://www.ietf.org/internet-drafts/draft-winterbottom-http-location-delivery-03.txt 2. The next step would be to map an emergency service URN to the responsible PSAP (public safety access point). Possible service URNs are defined in http://www.ietf.org/internet-drafts/draft-ietf-ecrit-service-urn-05.txt This will be mapped to PSAP URIs (using the current location as input) using the LOST protocol (Probably there will be LOST servers provided for example by government): http://www.ietf.org/internet-drafts/draft-ietf-ecrit-lost-01.txt 3. The SIP client will call the URI received from LOST and providing its location either using location-by-reference using the Geolocation header defined in http://www.ietf.org/internet-drafts/draft-ietf-sip-location-conveyance-04.txt or sending the location as PIDF-LO object using a second body in the INVITE message: http://www.rfc-editor.org/rfc/rfc4119.txt I think this would be feature where openwengo could stand out from the crowd of other SIP phones. Feature creep... could we have a working, standard compliant, SIP soft phone _before_ even thinking about stuff like this? What is not standard complient? There are lots of planned features of integrating lots of wrappers for lots of libraries (IM ...), conferencing, ... lots of planned features which others also have. Why not having a feature which others don't have yet? regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Wengo Crashes After Login
I asked the same one week ago - no answers :-( regards klaus George Lee wrote: Hi Experts, After login to wengo account, wengo crashes with the following error: --- Debug Error! Program: C:\wengong-dev\debug\qtwengophone.exe Module: 4.1.1 File c:\qt\qt-win-opensource-src-4.1.1\src\cirelib\global\qglobal.cpp Line: 2082 ASSERT failure in QMutex::unlock(): A mutex mist be unlocked in the same thread that locked it., file c:\qt\qt-win-opensource-src-4.1.1\src\corelib\thread\qmutex.cpp, line 248 --- Any ideas? - George ___ 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
Re: [Wengophone-devel] Wengo Shortcuts
Michael Werner wrote: When I tested Wengo this night i noticed a small but very annoying problem. In ICQ and other Instant Messanger i use the Alt + S shortcut to send messages . Wengo only needs the return button and this makes me crazy. I can't write multiple lines. My Chat Partner said me that this is the reason why he will still use Miranda. I would appreciate if i could change the Shortcuts in further Wengo releases. Most Chat programs supports Ctrl-Enter to make a line break - maybe openwengo too? klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] WengoPhone configuration
Gianluca Sforna wrote: On 8/24/06, Klaus Darilion [EMAIL PROTECTED] wrote: You can reverse engineer by blocking the https port. openwengo will fallback to http and you can use a packet sniffer to analyze the XML provisioning format. Considering this is an Open Source project, that sounds quite overkill... Reverse Engineering is done in 10 minutes (blocking https port under Windows can be easily done using the netdefender firewall). Writing an XLM file an put it on a webserver: 10 minutes That is nothing compared to writing your own sip client :-) Of course it would be best if these reverse engineered XML profile is published at the wiki, and the provisioning URL is a config option which can be changed without recompiling. regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] WengoPhone configuration
Leonardo José Reyes Diago wrote: Hello, i´m trying to configurate wengophone with another sip account i have,, i have change; network.proxy.port, network.proxy.server, network.sip.localport, network.sip.server, network.proxy.login and network.proxy.password to the sip account i have, but does'nt work, can someone tell me how can i configurate wengophone to another sip account? AFAIK openwengo fetches the SIP provisioning from the wengo server hia http/https. You have to change the URL (i think it was ws.wengo.fr) to point to your own webserver where you deliver the provisioning stuff. You can reverse engineer by blocking the https port. openwengo will fallback to http and you can use a packet sniffer to analyze the XML provisioning format. regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] windows build problems
Hi! I tried to build todays wengophone-ng (with Visual STudio.net 2003), but after 1 hour compiling it fails: Creating library debug\wengophone\src\presentation\qt\qtwengophone.lib and object debug\wengophone\src\presentation\qt\qtwengophone.exp LINK : warning LNK4098: defaultlib 'MSVCRTD' conflicts with use of other libs; use /NODEFAULTLIB:library LINK : warning LNK4098: defaultlib 'LIBCMTD' conflicts with use of other libs; use /NODEFAULTLIB:library debug\wengophone\src\presentation\qt\qtwengophone.exe : fatal error LNK1169: one or more multiply defined symbols found scons: *** [debug\wengophone\src\presentation\qt\qtwengophone.exe] Error 1169 scons: building terminated because of errors. 1. This somebody knows the problem? 2. I recognized afterwards, that during building (scons qtwengophone) QMAKESPEC was set to win32-g++. But nevertheless cl was used. Does this environment variable influence the build process? 3. How do I clean (like make clean)? thanks klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] How to download the source code of the wengo
Hi! I'm using the command line client from http://subversion.tigris.org/ and it works fine. regards klaus Shizhang Yan wrote: Hello, I am interested in this project of the wengo and I want to try to do something about it. And I tried to download it according the guide using the Tortoise SVN, but the username and password is not correct. I can login the web page (http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/TracGuide) using my user ID and password. Who can tell me how to download the source codes? I am using the Visual Studio to develop the programs. Thanks a lot in advance. Shi Zhang ___ 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
Re: [Wengophone-devel] 2.0 plans
Jérôme WAGNER wrote: Hello, We're currently trying to reach compatibility with more distributions (mstute is working on this). You're patch is under review. Maybe you can help on this in order to create a scons target for a Suse package. mstute is currently working on .deb and .rpm generation like we used to have in the classic version and any help on this subject is welcome in order support as many distros as we can. Other than that, there is multi-sip and file transfer on the way and all the Wengo code camp subjects. What is multi-sip? regards klaus Would you want to help on a specific subject ? Jérôme -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Andreas Schneider Envoyé : mardi 8 août 2006 16:21 À : wengophone-devel@lists.openwengo.com Objet : [Wengophone-devel] 2.0 plans -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I just want to know what the plans for WengoPhone 2.0 are. Get it working under Wine32 and Linux32? Fix most or all bugs? There is a race codition on x86_64 with the imwrapper code. So I've set multiimwrapper=0 which causes problems with the nullsipwrapper code. So where should we work on? -- andreas - -- http://www.cynapses.org/ - cybernetic synapses -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE2J3Gf94+j/M+P8YRAlPsAJ41D0FzrT01RFlOHq/oJ6/f5RLJ7wCffc1x mbajLRdi/rO4nePq/fg8ZU4= =It49 -END PGP SIGNATURE- ___ 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 mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] 2.0 plans
Jérôme WAGNER wrote: Hello, Multi-sip is the feature where you can add several SIP providers at the same time. O yeah, this one is good :-) btw: is there some description of the XML-provisioning format or do I have to reverse engineer? regards klaus Jérôme -Message d'origine- De : Klaus Darilion [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 août 2006 13:37 À : Jérôme WAGNER Cc : 'Andreas Schneider'; wengophone-devel@lists.openwengo.com Objet : Re: [Wengophone-devel] 2.0 plans Jérôme WAGNER wrote: Hello, We're currently trying to reach compatibility with more distributions (mstute is working on this). You're patch is under review. Maybe you can help on this in order to create a scons target for a Suse package. mstute is currently working on .deb and .rpm generation like we used to have in the classic version and any help on this subject is welcome in order support as many distros as we can. Other than that, there is multi-sip and file transfer on the way and all the Wengo code camp subjects. What is multi-sip? regards klaus Would you want to help on a specific subject ? Jérôme -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la part de Andreas Schneider Envoyé : mardi 8 août 2006 16:21 À : wengophone-devel@lists.openwengo.com Objet : [Wengophone-devel] 2.0 plans -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, I just want to know what the plans for WengoPhone 2.0 are. Get it working under Wine32 and Linux32? Fix most or all bugs? There is a race codition on x86_64 with the imwrapper code. So I've set multiimwrapper=0 which causes problems with the nullsipwrapper code. So where should we work on? -- andreas - -- http://www.cynapses.org/ - cybernetic synapses -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFE2J3Gf94+j/M+P8YRAlPsAJ41D0FzrT01RFlOHq/oJ6/f5RLJ7wCffc1x mbajLRdi/rO4nePq/fg8ZU4= =It49 -END PGP SIGNATURE- ___ 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 mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] X.509 authentification : A way to authenticate peers in SIP communications
Hi Julien! The usual way is the following: Use SIP over TLS to encrypt the SIP session from the SIP UA to its service provider and authenticate the SIP proxy to the SIP UA (you could also use mutual TLS to authenticate the SIP UA to the SIP proxy, but usually this is not done as SIP UAs have dynamic IP addresses and dynamic hostnames, thus certificates are difficult to use. To authenticate the SIP UA against the proxy digest authentication is fine). Use SIP over TLS to encrypt SIP signaling between service providers and authenticate the proxies (mutual TLS). To authenticate the peers end-to-end, you can use the SIP-Identity, e.g. draft-ietf-sip-identity. For securing the media, usually you will use SRTP. regards klaus Julien VEHENT wrote: Vadim Lebedev [EMAIL PROTECTED] a écrit : Julien VEHENT wrote: Hi there, We are two french students in Computer Security and we plan a project for our end-term studies. The general idea is to provide authentication in VoIP communication using X.509 certificates (already used in SSL TLS protocols). To do that, we want to modify SIP server and client source code and integrate a first level authentication (for example, using a challenge and one certificate for each peer) before or during SIP commands. The objective is, in a first time, to avoid register hijacking. Next, we plan to use certificates to authenticate peers before the NTP communications. Two functionalities would be added : -the peer's name who establishes the call will appear in the receiver client software -a strong authentication of peers So, we can explain it with a little graphical mockup like this one : I)SIP registration authentication +--+ |SIP registrar | +--+ / |/ (3) | .|SIP |request ||auth the |user .|register |x.509 ||two peers|successfully .|request |auth||using|registered .|(1) |(2) ||challenge|(4) .| / / / +--+ | Bob| +--+ II)SIP peers authentication ++ ++ ||--1. Pre-Invite with Bob cert---| A | | B |--2. OK, send Alice cert ---| L | | O |==3. authenticate peers| I | | B |--4. Alice accept the call--| C | ||---5. Bob ack, NTP call start---| E | ++ ++ For the moment, we are just brain storming but an idea we like is the development of a patch for OpenWengo project. That's why we are requesting your opinions. Best regards, julien Hi Julien, Are you aware that SIP standard allows transport of SIP packets inside SSL? And actually openwengo does support this mode of operation in almost standard way? Vadim Yes, I am. But what about performance ? I've read many times that SSL use in RTP communication bring many problems due to UDP requirement of the RTP protocol and TCP requirement of SSL protocol. Moreover, SSL use doesn't avoid register hijacking because users never force his use. It's like TLS over SMTP in fact... That's why we are just speaking about authentification. julien Julien VEHENT gpg: 0x7A7B6F2C sur keyserver.net web: www.linuxwall.info ___ 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
Re: [Wengophone-devel] wengo -- zap
On Tue, February 14, 2006 12:59, Alex Fritze said: Hi, I'm trying to get Wengo (the service) working with zap (the other Mozilla-based SIP client [1]), and I'm having a bit of trouble with Wengo's registration behaviour: Wengo persistently changes the host part of the contact I'm registering to 192.168.70.52:5060. So if I'm registering with a Contact header Contact: sip:[EMAIL PROTECTED]:5076;grid=8153284ae949e21af165927794204ac2, the registration will succeed (from Wengo's point of view), but the returned 200 response contains a Contact header Contact: sip:[EMAIL PROTECTED]:5060;grid=8153284ae949e21af165927794204ac2. Since this is a different address, zap will think that it is a binding from some other registered endpoint. Can someone enlighten me about this behaviour? Is it intended or is it a bug? The wengo behaviour is not standard conform. Maybe this is caused by a buggy NAT traversal technology used at wengo. regards klaus ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Compile release mode of NG version
Cantemir Mihu wrote: I cannot compile it. Could you have a look at this output please? (I'm on WindowsXP, and QT is installed under C:\qt\4.1.0) maybe this thread can help you. http://dev.openwengo.com/pipermail/wengophone-devel/2006-January/002057.html regards klaus http://pastebin.com/532188 On 1/31/06, *Julien Gilli* [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Hello, Cantemir Mihu a écrit : I'm very new to using Scons. Sorry for the silly question, but how can I compile NG version in release mode? Use the mode=release command line switch like this: QTDIR=/whatever scons mode=release qtwengophone Another question: If i set the option enable-video to 0, then the output will not depend on avcodec.dll ? Exactly. Yet another question: what is wengocurl.dll? :) It is curl with small changes added. We named it wengocurl so that we don't get into the issue where we link the main executable binary with curl and it actually links with the system's curl. The changes are being submitted upstream, but it has not been accepted yet by curl's maintainer. Thank you for your patience You're welcome! -- Julien Gilli OpenWengo, the free and multiplatform VoIP client http://dev.openwengo.com/ ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com mailto:Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen Grüssen Cantemir Mihu ___ 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] ng build experience report
Hi! For the first time I succeeded building and starting ng on Windows. Nevertheless, there were some steps of uncertainty, which I hope someone could describe the proper handling. I will post my installation protocol and ask the questions inline. pre requirements: - scons 0.96.1 installed - Visual Studio 2003 installed - boost 1.33 libraries installed - svn client installed 1. qt 4.1 http://www.trolltech.com/download.html?target=ftp://ftp.trolltech.com/qt/source/qt-win-opensource-src-4.1.0.zip unzip to C:\qt-win-opensource-src-4.1.0 2. qt4.1 patch for visual studio http://prdownloads.sourceforge.net/qtwin/acs4qt41.zip?download extract to C:\qt-win-opensource-src-4.1.0 3. open a visual studio command prompt cd C:\qt-win-opensource-src-4.1.0 installpatch41.bat mkdir qmake\tmp qconfigure msvc.net set QMAKESPEC=win32-msvc.net set QTDIR=c:\qt-win-opensource-src-4.1.0 set path=%QTDIR%\bin;%path% set INCLUDE=C:\boost_1_33_0;%INCLUDE% set LIB=C:\boost_1_33_0\bin\boost\libs;%LIB% I guess these are not the correct seeting to find the boost libraries, but I could not figure out the correct ones. 4. download openwengo cd \Dokumente und Einstellungen\darilion\Eigene Dateien\Visual Studio Projects mkdir openwengo cd openwengo svn --username guest --password guest --non-interactive co http://dev.openwengo.com/svn/openwengo/trunk cd trunk // clean up scons -c //build scons qtwengophone //broken build process copy libs\ffmpeg\binary-lib\avcodec.lib . this should be fixed - or is it necessary to set some library paths? scons qtwengophone now, the build fails because it does not find the boost libraries, e.g: libboost_thread-vc71-mt.lib, Browsing the boost libararies there are several of them (static, runtime, release, debug ...). This was my first problem: Which version of the boost libraries are needed? I used the ones which names looked most similar to the requested ones, e.g. for libboost_thread-vc71-mt.lib I used release\threading-multi\boost_thread-vc71-mt-1_33.lib Thus I copied them into the trunk directory: //copy boost libs copy C:\boost_1_33_0\bin\boost\libs\thread\build\boost_thread.dll\vc-7_1\release\threading-multi\boost_thread-vc71-mt-1_33.lib libboost_thread-vc71-mt.lib copy C:\boost_1_33_0\bin\boost\libs\serialization\build\boost_serialization.dll\vc-7_1\release\threading-multi\boost_serialization-vc71-mt-1_33.lib libboost_serialization-vc71-mt.lib copy C:\boost_1_33_0\bin\boost\libs\signals\build\boost_signals.dll\vc-7_1\release\threading-multi\boost_signals-vc71-mt-1_33.lib libboost_signals-vc71-mt.lib Now, the build fails again, requirering the debug versions, e.g. boost_thread-vc71-mt-gd-1_33.lib (Note: this time the version numer is in the file name). So, why are the libraries needed twice? I thought the default build is debug, so why are the release libraries needed in the prvious step? Nevertheless I again copied them into the trunk directory: copy C:\boost_1_33_0\bin\boost\libs\thread\build\boost_thread.dll\vc-7_1\debug\threading-multi\boost_thread-vc71-mt-gd-1_33.lib libboost_thread-vc71-mt-gd-1_33.lib copy C:\boost_1_33_0\bin\boost\libs\serialization\build\boost_serialization.dll\vc-7_1\debug\threading-multi\boost_serialization-vc71-mt-gd-1_33.lib libboost_serialization-vc71-mt-gd-1_33.lib copy C:\boost_1_33_0\bin\boost\libs\signals\build\boost_signals.dll\vc-7_1\debug\threading-multi\boost_signals-vc71-mt-gd-1_33.lib libboost_signals-vc71-mt-gd-1_33.lib Again the build files of missing libraries: copy debug\libs\curl\wengocurl.dll . Then (I think this was when starting openwenge) the boost libraries are needed as DLL. Why? Probably this is something I do not understand because of my lack of programming experience under Windows. But I always thought an application needs either static (.lib) or runtime (.dll) libraries, not both of them. Nevertheless, I again copied them into the trunk directory: copy C:\boost_1_33_0\bin\boost\libs\thread\build\boost_thread.dll\vc-7_1\release\threading-multi\boost_thread-vc71-mt-1_33.dll boost_thread-vc71-mt-1_33.dll copy C:\boost_1_33_0\bin\boost\libs\serialization\build\boost_serialization.dll\vc-7_1\release\threading-multi\boost_serialization-vc71-mt-1_33.dll boost_serialization-vc71-mt-1_33.dll copy C:\boost_1_33_0\bin\boost\libs\signals\build\boost_signals.dll\vc-7_1\release\threading-multi\boost_signals-vc71-mt-1_33.dll boost_signals-vc71-mt-1_33.dll copy libs\ffmpeg\binary-lib\avcodec.dll . copy debug\wifo\phapi\phapi.dll . ng needs several libraries to work (avcodec, phapi). What ist the correct location of these? Should they be copied into the same directory as the openwengo.exe? Or should an installer application take care of copying all the needed libaries into the applications directory (c:\program files\openwengo)? Finally, ng started :-) thanks klaus ___ Wengophone-devel mailing list
Re: [Wengophone-devel] unicap
Arne Caspari wrote: Vadim Lebedev wrote: Hi Arne, Thanks a lot for your input, Do you think it will be diffucult to port unicap to Wndows to develeop VfW and DirectShow backends? There is one issue that I forgot with a DirectShow plugin: Since you would need to link the plugin with a closed source library ( DirectShow ), you can not distribute it ( at least not in binary ) since unicap is GPLed. ( Just like openwengo ). AFAIK this is not a problem. If you link against GPL, your code also must be GPL. But you GPL application is allowed to link against other licensed libraries. Lots of Linux libraries are not GPL and will be used by GPL applications. There is lots of discussion on this topic. If I remember correct, then linkning against not GPL libraries is fine if they belong to the OS (e.g. there is lots of discussion of using openSSL in GPL application). regards klaus In this case I would need to make a license addition ( or rather exception ) to explicitly allow the linkage of this plugin. If I make this exception ( and I see no point why not to make such an exception ), you ( or the openwengo team ) would also need to make such an exception to your licensing terms, otherwise distributions would not be legally allowed to ship openwengo in binary ( at least the windows build would then have questionable licensing conditions ). The complicated thing is that I think every code contributor needs to accept these modified license terms. Since you have a windows build and use ( I guess ) DirectShow, you should already be in such a licensing situation. How is it handled by the current openwengo license? Boy, I hate licensing issues :-( /Arne ___ 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
