Hi all,
It's taken me some time to get there, but here are my notes on the
cobranging discussion during the summit.
The discussion covered two topics:
1. Co-branding and configurability
2. SIP abstraction
The people at the session all stated what they were hoping to cover in
the discussion
Hello,
I believe WengoPhone is already not so bad at traversing firewalls. The
NetworkDiscovery state machine inside WengoPhone does quite some work to
traverse NATs.
A small application dedicated to NAT traversal is being written in the CoIP
branch in order to test only this feature so that
Hello Claudio,
Can you be a bit more specific ? are you using scons / cmake ?
I know that with the cmake buildsystem, default choices of internal /
external libs may not be the same as before.
What exactly was the experience that made you send this email ?
Thank you
Jerome
-Message
Claudio André wrote:
Hi,
Hi Claudio,
./build_make.sh --help
Usage: build_make.sh [--configure [debug|final]|--clean|--verbose|--help]
But if i try, ./build_make.sh --configure debug, i get.
Unknown Option --configure. Exit
The right seems to be
./build_make.sh --build debug
Thanks,
Hi there
A few weeks ago I reported a bug with the buddy-handling and jabber! Now
I'm using a new jabber-server (ejabberd) and again have some issues. =
The subscribed message is sent, but because the buddy is already on
the server-list, it's not added from the server and this way no
Hi Gianluca,
no, I am not counting wengo users. But I think that a lot of
broadband users are running with router/modems and that this presents
a problem for Wengo acceptance. IPv6 is the long term NAT solution,
but all products need to deploy a NAT solution for the short-term.
On
Hi Jerome,
I believe that Wengo is a good product because it is:
- standards-based (but Jabber Jingle would be good enhancement!)
- cross-platform
To be a killer product, it needs:
- video telephony to work out-of-the-box. Firewall/NAT traversal
is a key issue above many other features.
Jérôme WAGNER wrote:
Hello,
Osip could and must be synchronized with upstream version.
eXoSip has been highly modified on WengoPhone side and I doubt that a
re-synch would be easily possible.
At this stage, and talking about the code that is in the repository, I think
we should rename it to
On 1/29/07, Vadim Lebedev [EMAIL PROTECTED] wrote:
Jérôme WAGNER wrote:
Hello,
Osip could and must be synchronized with upstream version.
eXoSip has been highly modified on WengoPhone side and I doubt that a
re-synch would be easily possible.
At this stage, and talking about the code that is
Hi, i'm using cmake, on OW 2.1. Rev 943x to 9492
Since a few days ago, cmake is not able to find some libraries and
failed to build if these dev packages are not installed (+
libsndfile-dev, from previous message).
Well, i sent this message because i agree with [EMAIL PROTECTED] The
idea
I add one point to be a killer product.
- Internationalization. The software, the test call voice and the
service site (www.wengophone.com).
David Fennell wrote:
Hi Jerome,
I believe that Wengo is a good product because it is:
- standards-based (but Jabber Jingle would be good
Hi,
When I try to create an installer with release build, I get this error:
Creating library owwebcam.lib and object owwebcam.exp
C:\Program Files\CMake 2.4\bin\cmake.exe -DTARGET=owwebcam.dll
-DCMAKE
_CL_NOLOGO= -P C:/Program Files/CMake
2.4/share/cmake-2.4/Modules/CMakeVCManife
12 matches
Mail list logo
