Hi,
This problem comes from the use of libgaim. There is something wrong in
libgaim under windows that causes this.
Regards,
Minh
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of J.
Christopher Pereira Z.
Sent: jeudi 20 mars 2008 21:12
To: Minh Phan; wengophone-devel@lists.openwengo.com
Subject: Re: [Wengophone-devel] Exceptions when Debugging with MS VS 2003
/ 2005
Does this problem impact Qutecom's stability?
- Original Message -
From: Minh Phan [EMAIL PROTECTED]
To: 'J. Christopher Pereira Z.' [EMAIL
Hi Ray,
Do you have good reasons to use mingw to compile WengoPhone? If not, using
VC++ would save your time.
SFP is the module used for file transfer. It's not necessary if you don't
need file transfer function or if you don't use Wengo servers. To disable
it, you should look into the CMake
Dave,
It's not absolutely necessary but is it causing problem? Initializing it by
default is just easier to code. Initializing it on demand requires some
extra works.
Minh
-Original Message-
From: [EMAIL PROTECTED] [mailto:wengophone-
[EMAIL PROTECTED] On Behalf Of Dave Neary
Sent:
Hi,
OpenSER WengoPhone are enough to make use of WengoPhone's chat function.
You just need to config OpenSer to route the SIP message MESSAGE correctly.
Regards,
Minh
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of johnny
Laura
Sent:
2007/7/10, Minh Phan [EMAIL PROTECTED]:
OpenSER WengoPhone are enough to make use of WengoPhone's chat
function. You just need to config OpenSer to route the SIP message
MESSAGE correctly.
OK But features such as offline messages and group chat will not be
available.
These functions
Hi Vadim,
Thank you for the detailed list and sorry for the delay. Now that the branch
transport_refactoring has been merged to the trunk, we would like to
integrate your patches. Could you give us more details about the server
based chat rooms support? Which RFC or draft is based on ? Which
Hi List,
The branch transport_refactoring of phapi was merged to the trunk (of phapi
repository). This new version of phapi includes many new features,
including:
* TCP/TLS SIP transports supports.
* Easy customization of SIP message for interoperability with special
SIP
Yes, there is a SIP INVITE message with SDP. I think they are using SIP for
voice just like Yahoo and MSN in recent versions of their respective IM
networks.
Minh
-Original Message-
From: [EMAIL PROTECTED] [mailto:wengophone-
[EMAIL PROTECTED] On Behalf Of Philippe BERNERY
Sent:
Minh,
osip maintainer does not accept this patch, so i've reverted it and added
osip_message_replace_header to ow_osip and updated eXosip sources to use
it
Nice stuff. Thanks Vadim
Minh
___
Wengophone-devel mailing list
PROTECTED]
Sent: mardi 22 mai 2007 14:45
To: Minh Phan
Cc: wengophone-devel@lists.openwengo.com
Subject: Re: [Wengophone-devel] Re: miniua
Hi,
thank you Minh, you were right.
I have updated as you wrote but now I have this error:
...a lot of warning...
D:\wengophone-2.1
Hi Vadim,
Thank you for the clarification. That's a very good idea ! I'll give it a
try when I'll be back from vacation in 3 weeks.
Minh
_
From: Vadim Lebedev [mailto:[EMAIL PROTECTED]
Sent: vendredi 27 avril 2007 20:48
To: Minh Phan
Cc: 'OpenWengo'
Subject: Re: phapi-video
Hi Vadim,
Now I'm actually in vacation. Let me check it in 3 weeks when I'll be back.
Thanks,
Minh
-Original Message-
From: Vadim Lebedev [mailto:[EMAIL PROTECTED]
Sent: samedi 28 avril 2007 19:10
To: OpenWengo; 'Minh Phan'
Subject: [Fwd: [Wengophone-commit] r10943 - wifo/branches
.
Regards,
Minh
-Original Message-
From: Vadim Lebedev [mailto:[EMAIL PROTECTED]
Sent: vendredi 27 avril 2007 11:28
To: OpenWengo; 'Minh Phan'
Subject: Commits 10883, 10884
Hello,
Jerome, you reverted my commits 10883, 10884
Maybe you will be interested to reconsider... because
Are you sure that hLine is already valid at this moment?
If yes i'll fix the patch
Yes, it is.
Sorry minh, it is NO...
I'm right now in the debugger and hLine is == -1.
Sorry Vadim. There was a bug in phApiWrapper and I have fixed it @rev
10938. The hLine should be valid
?
-Original Message-
From: Vadim Lebedev [mailto:[EMAIL PROTECTED]
Sent: vendredi 27 avril 2007 18:45
To: OpenWengo; 'Quang Minh PHAN'
Subject: phapi-video
Minh,
I saw couple of patches related to video stuff,
so it made me think about ffmpeg.
I've recently ported my verona stuff
Hi Edouard,
We are using standard audio codec including G711, iLBC, speex, etc.
This page would gives you a more detailed list of audio codec available and
the related information.
http://en.wikipedia.org/wiki/Category:Audio_codecs
Regards,
Minh
_
From: [EMAIL
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
Sorry, the link is here
http://dev.openwengo.com/trac/openwengo/trac.cgi/wiki/OWEP_8101_phapi_refact
oring
Minh
-Original Message-
From: Luigi Bancaro [mailto:[EMAIL PROTECTED]
Sent: mardi 17 avril 2007 09:30
To: Minh Phan
Subject: Re: phapi and java
Ok Minh... I will write
Make sure that you have all the dependency of phapi.dll ((dlls that phapi
depends on) in the same directory as phapi.dll. If you compile the whole
WengoPhone, all these dlls are in the directory build\debug.
Minh
-Original Message-
From: [EMAIL PROTECTED] [mailto:wengophone-
[EMAIL
:[EMAIL PROTECTED]
Sent: lundi 16 avril 2007 11:06
To: [EMAIL PROTECTED]
Subject: phapi and java
Dear Minh Phan,
I write to ask you for some help with phapi.
I have to launch openwengo and start a videocall from a Java
application. Is it possible using phapi.dll? Is there a way
Hi,
You sould use the CoIP manager in the trunk of WengoPhone. That would allow
you to use more that one sip stack and switch between them quite easily.
Also, we are currently improving the transport layer of phapi. The PhAPI
stack will then support UDP, TCP and TLS with ICE. Our purpose is to
Hi Vadim,
It is pretty interesting patch,
but i would suggest to not to modify existing phAddVline? prototypes,
but add a new one with transporttype parameter.
This way you dont break existing programs
We want to keep backward compatibility in the transport_refactoring branch
but that
We want to keep backward compatibility in the transport_refactoring
branch
but that implies too much work as the whole eXosip API set will be
changed.
Hence, we decided not to keep it in that branch. Once the factoring
branch
will be released, there will be an svn tag of current phapi for
Hi Mayank,
That message is sent in order to detect local network configuration. It is
not the REGISTER for your Wengo SIP account. If we receive a response from
the server in reply to that register message, we then know that we can
connect directly to the SIP server. Otherwise, we may need to
:58
To: Minh Phan
Subject: RE: [Wengophone-devel] SIP messages while registering.
Thanks Minh,
Thanks for your detailed explanation, I was thinking that if we get 404 Not
found then, why are we sending nobody? but your explanation solves my
question.
Now one quick question.So
Hi Andreas,
Your patches have been applied to the rev 10103. Thank you!
Minh
-Original Message-
From: [EMAIL PROTECTED] [mailto:wengophone-
[EMAIL PROTECTED] On Behalf Of Andreas Schneider
Sent: dimanche 4 mars 2007 02:22
To: wengophone-devel@lists.openwengo.com
Subject:
-Original Message-
From: [EMAIL PROTECTED] [mailto:wengophone-
[EMAIL PROTECTED] On Behalf Of Jean-François Gaud
Sent: lundi 5 mars 2007 15:44
Cc: wengophone-devel@lists.openwengo.com
Subject: Re: [Wengophone-devel] Problematic fixes
Since then, I get some errors when compiling on
Hi Brian,
There are two solutions:
1. Compile PhAPI and write an application on top of it.
2. Modify GUI layer of WengoPhone.
If you just need a simple client that can make and receive phone calls, the
first solution is right for you. On the other hand, If you need a complete
user interface,
Hi,
I see the CODEC_PLUGIN_PATH_KEY value in Config.cpp of wengophone about
adding pluging codec
The CODEC_PLUGIN_PATH_KEY contain the path to the directory where all codec
plugins are stored.
but i dont know where to add the plugin codec to the compiled of wengo.
you have any ideas?
I don't
Hi zahid,
WengoPhone doesn't support g729 codec for now as it is not free to use.
Regards,
Minh
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Zahid
Ayar
Sent: dimanche 21 janvier 2007 04:25
To: wengophone-devel@lists.openwengo.com
Hi List,
For the future supports of miniua in PhAPI, as a survey, we would like to
know how many of you are actually using miniua (or know what it is and may
try it one day). Please let us know if you wish miniua to be maintained.
Regards,
Minh
___
Hi Vadim,
Great goal,
But i don't really understand the new system of error codes and new API
methods
I'm affraid with your current approach you are missing this goal
Well, let's talk about the error codes. In the old phapi, some function
return an int, some function return nothing
Hi Vadim, Great goal,But i don't really understand the new system of error codes and new APImethodsI'm affraid with your current approach you are missing this goal Well, let's talk about the error codes. In the old phapi, some functionreturn an int, some function return nothing (void),
(I resend this msg because the previous message was not very easy to read due to some font issue)Hi Vadim, Great goal,But i don't really understand the new system of error codes and new APImethodsI'm affraid with your current approach you are missing this goal Well, let's talk about the
Hi Vadim,
The main goals of refactoring phapi are:
1. To make it even easier to use.
2. To make it more extendable (Easier to add new functionalities with a new
Plugin system. Able to handle all kind of communication sessions (File
transfer, VNC, etc.), not only voice and video.
Please see more
Hi Vadim,
I'm under impression that you've wrote you own SIP parser, and SIP state
machine and
implemented a new version of phapi on top of it am i wrong?
It was done that way and it is being changed. The new code will use sip
state machine and sip parser of osip eXosip.
another
Thanks Vadim! I forgot that there could be many dialogs in a call :)
Minh
Minh,
I've fixed your fix in REV #7658 to scan all dialogs in the call
Vadim
-Original Message-
From: [EMAIL PROTECTED] [mailto:wengophone-
[EMAIL PROTECTED] On Behalf Of Marlon Mircevski
Sent:
Hi Vadim,
There was a little thing missing in your last commit. I fixed that in
REV#7665 :)
Minh
Thanks Vadim! I forgot that there could be many dialogs in a call :)
Minh
Minh,
I've fixed your fix in REV #7658 to scan all dialogs in the call
Vadim
-Original
Hi Sven,
Could you give more
details on the problem you have with the function osip_transaction_get_your_instance
? We believe that there is no
different between wifo-plugin and the trunk on the usage of that function.
Regards,
Minh
From:
[EMAIL PROTECTED]
Hi Sven,
To get the transaction without modifying exosip, you
can make this call: __osip_find_transaction
(eXosip.j_osip, sipevent, 0)
in udp.c, right after the call to osip_find_transaction_and_add_event(eXosip.j_osip, sipevent);
However, the modification you made to the function
Hi Sven,
Hi,
Asking about the SIP flow inside phapi: does ALL outgoing SIP messages
going
trough this callback osip_t.cb_send_message set via void
osip_set_cb_send_message (osip_t * cf, int (*cb) (osip_transaction_t *,
osip_message_t *, char *, int, int))?
Yes, all outgoing SIP
42 matches
Mail list logo
