I've been trying to get OpenWengo-NG to build ( and run ) for the last
six hours or so with little luck. I've tried both the RC2 tagged
revision as well as the head revision.
This page is a Wiki, but I don't know how to update it:
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/HowToBuild
I've been trying to get OpenWengo-NG to build ( and run ) for the last
six hours or so with little luck. I've tried both the RC2 tagged
revision as well as the head revision.
This page is a Wiki, but I don't know how to update it:
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/HowToBui
Tanguy,
I think better solution (performnce-wise) would be:
#define inline __inline
in case of MSVC
Vadim
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
(I cleaned up the email thread because it was getting too big)
(history) http://thread.gmane.org/gmane.comp.voip.wengophone.devel/2939/
(history) http://thread.gmane.org/gmane.comp.voip.wengophone.devel/2958/
I tried to summarize this discussion on a set of page for future
documentation :
* Gene
Jérôme WAGNER wrote:
Hello,
In phapi, phcfg structure contains a field specifying plugin directory
I'd suggest to to stuff all phapi plugins in this directory and use
absence/precense of predefined entrypoints to distinguish between different
plugin kinds
Yes I know that holding
Hello,
>In phapi, phcfg structure contains a field specifying plugin directory
>I'd suggest to to stuff all phapi plugins in this directory and use
>absence/precense of predefined entrypoints to distinguish between different
>plugin kinds
Yes I know that holding directories are dynamically de
Jérôme WAGNER wrote:
Andreas,
Plugins have to be in /usr/lib/application_name.
Under linux, could we also put Plugins under
/usr/lib/application_name/plugins ?
(like under windows)
Regarding the disambiguation and "planarization" of the directory structure,
I'd rather have only on
Hi,
Regarding our discussion with andreas about the
plugin directory architecture, could we try and list here all the known dynamic
extension points (something like a plugin) currently implemented in the
softphone ?
I have:
- wenbox
- phapi audio codecs
- phapi sip plugins (like
Andreas,
>> Plugins have to be in /usr/lib/application_name.
Under linux, could we also put Plugins under
/usr/lib/application_name/plugins ?
(like under windows)
Regarding the disambiguation and "planarization" of the directory structure,
I'd rather have only one level of directory that holds a
Yes it should. So it is something else.
I advise that you check your login/pwd against a working previously
installed wengophone. Do you have such a machine/installation ?
Jerome
-Message d'origine-
De : Andreas Schneider [mailto:[EMAIL PROTECTED]
Envoyé : mercredi 27 septembre 2006 18:
Jérôme WAGNER wrote:
> Hey,
> Be sure to use your SIP password if you're going through the wengo platform.
>
> The password you use to log on your selfcare is different. Your can get your
> SIP account via something like
>
> http://www.voip-info.org/wiki/view/Asterisk+settings+for+Wengo
> (sorry
Jérôme WAGNER wrote:
> Hello,
>
> I think plugins dir architecture should solve 2 problems :
>
> - the separation of extension points
> - the easiness of installation across extension points
>
> Let me explain :
>
> 1/ A plugin for the wenbox should not lie in a directory where we look for
> au
Hey,
Be sure to use your SIP password if you're going through the wengo platform.
The password you use to log on your selfcare is different. Your can get your
SIP account via something like
http://www.voip-info.org/wiki/view/Asterisk+settings+for+Wengo
(sorry for the shortcut but this is the quic
Hello,
I think plugins dir architecture should solve 2 problems :
- the separation of extension points
- the easiness of installation across extension points
Let me explain :
1/ A plugin for the wenbox should not lie in a directory where we look for
audio-codecs plugin
2/ a "file transfer" plu
Jérôme WAGNER wrote:
> Andreas,
>
> Do you see the 403 in an ethereal dump ?
>
> Looks like phapi keeps sending REGISTERs but certainly gets this 403 from
> the server.
It sends a REGISTER
sip:[EMAIL PROTECTED]
gets a 401
then it sends a again a regsiter and gets a
403 [WRONG PASSWORD]
Mayb
Andreas,
Do you see the 403 in an ethereal dump ?
Looks like phapi keeps sending REGISTERs but certainly gets this 403 from
the server.
It would be interesting to see with ethereal if as was said earlier on the
list you do not have a bad DNS request.
Jerome
-Message d'origine-
De : And
Jérôme WAGNER wrote:
> Hello,
>
> Depending on the platform you need to make a call and then close the
> softphone in order for the phlogger.log file to be created.
I can't make a call, cause I'm not connected
NAT type: prcone fw=·
REGPROGRESS reg=1 for vlid=1
REGPROGRESS reg=1 for vlid=1
REGPRO
Hello,
Depending on the platform you need to make a call and then close the
softphone in order for the phlogger.log file to be created.
Jerome
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Andreas
Schneider
Envoyé : mercredi 27 septembre 2006 16:21
À
Jérôme WAGNER wrote:
> Hello,
>
> To help on that, could you modify wifo/phapi/phlog.h and put a 1 on
>
> MEDIA_ENGINE
> SIP_NEGO
>
> And then paste the phlogger.log file that is generated by phAPI.
>
The file is empty.
> 403 is a "forbidden" error. Can you confirm you're using a correct acco
I was getting a similar error awhile back, though probably for a
different reason. When this happened, my sniffer captured no SIP
traffic going through. It turns out in my case, the SIP server's
host name could not be resolved. I had to fix the DNS to resolve this.
-Bruno
On Sep 27, 2
Hello Tomi,
You're most certainly right on these points and the boostrap is something
that should be worked on.
It will need a review of the different steps that are being done.
I suspect that some of the "double work" that you mention is due to a part
of the software that is used to migrate fro
Hello,
To help on that, could you modify wifo/phapi/phlog.h and put a 1 on
MEDIA_ENGINE
SIP_NEGO
And then paste the phlogger.log file that is generated by phAPI.
403 is a "forbidden" error. Can you confirm you're using a correct account ?
Jerome
-Message d'origine-
De : [EMAIL PROTEC
Hi,
WengoPhone starts now on x86_64 but it doesn't connect. I get
(error) 13:35:22 void PhApiCallbacks::registerProgress(int, int):
unknown phApi event=403
Here is the complete log:
http://pastie.caboo.se/15112
-- andreas
--
http://www.cynapses.org/ - cybernetic synapses
signatu
Hello Bruno,
Regarding the MacOSX
PowerPC 2 consecutive calls problem, I just commited something that looks like
a patch on the machine I have.
See http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/979
to better understand why I am not satisfied with the patch but why I need t
Hi..
I have noticed that the boot strap process of Ng is very slow.. Ng does a
several times same actions that should be done only once.. Like connecting
to google.com for testing internet connection.. Or sending Publish or other
SIP messages several times during the boot.. This not good..
Secon
Andreas Schneider wrote:
Hi,
I had the wenbox plugin problem. I've debugged wengophone with help from
str (thanks) and found 2 bugs. Could someone look at the patch if I can
commit it to svn?
The first is that we add the lib extension to the filename but pass the
filename without the lib exten
Hi,
I had the wenbox plugin problem. I've debugged wengophone with help from
str (thanks) and found 2 bugs. Could someone look at the patch if I can
commit it to svn?
The first is that we add the lib extension to the filename but pass the
filename without the lib extension to the following functi
Hi,
I want clear or lets say better directories for plugins. We could use
one directory for all plugins or use a base directory and subdirectories
for different parts.
The base directory
===
Linux
--
Hardcoded (cmake option):
_prefix/_libdir/wengophone (/usr/lib64/we
28 matches
Mail list logo
