Re: [Wengophone-devel] Crashing because of phapi.dll
Regarding problem 2 (see below), I changed phapi.c:@@ -3110,16 +3133,20 @@ if (ca->mses) {- if (!ph_msession_stopped(ca->mses))- {- ph_msession_stop(ca->mses,
phcfg.audio_dev);- }- - // cf allocation sequence for the ph_msession_s in phmedia.h- g_mutex_free(ca->mses->critsec_mstream_init);- free(ca->mses);+ if (!ph_msession_stopped(ca->mses))
+ {+ ph_msession_stop(ca->mses, phcfg.audio_dev);+ }+ + // cf allocation sequence for the ph_msession_s in phmedia.h+ if (ca->mses)+ {
+ if (ca->mses->critsec_mstream_init)+ g_mutex_free(ca->mses->critsec_mstream_init);+ free(ca->mses);+ }the problem does not appear any more. Instead problem 1 appears in very rare occasions (twice in a week with about 100 calls per day). Could anyone figure it out
why the r
tp variable is 0x000C? If it where NULL, I could to a if test, but so it's really untraceable. If someone has experience with WinDBG, I could send the whole information needed for tracing this down.
How can one catch the exceptions
raised by a thread inside a dll library
from a C++ wrapper
? If this would be possible, than the phapi wrapper could reinitialize the whole library.10xOn 5/23/06, Cantemir Mihu
<[EMAIL PROTECTED]> wrote:
>From my debug information all around my softphone, ph_call_media_stop is called only once (it could be it is called internally more than once). But asuming it is called twice, how can I avoid this? Using a critical section maybe? Do you think 2 different threads are executing this function, so it crashes (because there is a check:
if (ca->mses)... but still ca->mses is NULL when it crashes).10x
On 5/23/06, Jérôme WAGNER <[EMAIL PROTECTED]
> wrote:
Hello,
One way to explain this
kind of behaviour would be that ph_call_media_stop is called 2 times very
quickly.
phapi is not totally safe
on this point and I have already seen problems around such "2 API calls
in a row".
Can you add printf in
your code, or activate the SIP part of phdebug.h to see if indeed your call is
closed 2 times when the bug arises ?
Thank you,
Jérôme
De :
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
De la part de Cantemir
Mihu
Envoyé : mardi 23 mai 2006
13:35
À : wengo dev
Objet : [Wengophone-devel]
Crashing because of phapi.dll
Hello,
my softphone based on phapi, running on Windows does crash from time to time.
Therefore, I included a crash report generator, that generates so called
minidumps. With this dumps and the phapi source code, I am able to track the
exact line of crash. I found out three such lines:
1. in rtpmod.c, function void rtp_putq(queue_t *q, mblk_t *mp)
the line:
if (rtp->timestamp == tmprtp->timestamp)
causes ACCESS_VIOLATION, because the rtp variable is 0x000C
2. in phapi.c , function ph_call_media_stop(phcall_t *ca)
the line:
g_mutex_free(ca->mses->critsec
_mstream_init);
causes ACCESS_VIOLATION, because the ca-mses member is NULL, allthough there is
a check if (ca->mses) ???
3. in rtpsession.c, function rtp_session_create_packet (RtpSession * session,
gint header_size, char *payload, gint payload_size)
the line:
rtp->version = 2;
causes ACCESS_VIOLATION, because the rtp variable is NULL!
I cand send you the *.pdb files, if you need them and any other info. If you
have time, please tell me what could be the problem of this errors and how I
can avoid them. I tried using __try... __finally on error number 2 (which is
the most often), but without any success. How can I implement a exception
catcher in phapi.dll, so the program does not crash, but is able to reinitiate
phapi if necessary.
Thank you for your patient in reading this.
--
Best regards / Mit freundlichen Grüssen
Cantemir Mihu
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] sound gets inaudible after a few seconds talking (gnu/linux <-> winxp )
I had the same problem on Win XP when AEC was enabled. Actually I still have this problem. You think this can be related to the problem of Christophe?On 5/29/06, Julien Gilli <[EMAIL PROTECTED]> wrote: Hello,On 5/25/06, Christophe Prud'homme < [EMAIL PROTECTED]> wrote: Congratulations for Beta1 and waiting eagerly for beta2 Thank you! The sound while calling another wengo user gets inaudible after a short while. Somebody got this problem ? I don't remember someone reporting this problem, but I may have missed something. This has been reported in ticket #629 http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/629 Thank you very much for the bug report, we'll look into this! Best regards,-- Julien Gilli ___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Crashing because of phapi.dll
>From my debug information all around my softphone, ph_call_media_stop is called only once (it could be it is called internally more than once). But asuming it is called twice, how can I avoid this? Using a critical section maybe? Do you think 2 different threads are executing this function, so it crashes (because there is a check: if (ca->mses)... but still ca->mses is NULL when it crashes).10x On 5/23/06, Jérôme WAGNER <[EMAIL PROTECTED]> wrote: Hello, One way to explain this kind of behaviour would be that ph_call_media_stop is called 2 times very quickly. phapi is not totally safe on this point and I have already seen problems around such "2 API calls in a row". Can you add printf in your code, or activate the SIP part of phdebug.h to see if indeed your call is closed 2 times when the bug arises ? Thank you, Jérôme De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Cantemir Mihu Envoyé : mardi 23 mai 2006 13:35 À : wengo dev Objet : [Wengophone-devel] Crashing because of phapi.dll Hello, my softphone based on phapi, running on Windows does crash from time to time. Therefore, I included a crash report generator, that generates so called minidumps. With this dumps and the phapi source code, I am able to track the exact line of crash. I found out three such lines: 1. in rtpmod.c, function void rtp_putq(queue_t *q, mblk_t *mp) the line: if (rtp->timestamp == tmprtp->timestamp) causes ACCESS_VIOLATION, because the rtp variable is 0x000C 2. in phapi.c , function ph_call_media_stop(phcall_t *ca) the line: g_mutex_free(ca->mses->critsec _mstream_init); causes ACCESS_VIOLATION, because the ca-mses member is NULL, allthough there is a check if (ca->mses) ??? 3. in rtpsession.c, function rtp_session_create_packet (RtpSession * session, gint header_size, char *payload, gint payload_size) the line: rtp->version = 2; causes ACCESS_VIOLATION, because the rtp variable is NULL! I cand send you the *.pdb files, if you need them and any other info. If you have time, please tell me what could be the problem of this errors and how I can avoid them. I tried using __try... __finally on error number 2 (which is the most often), but without any success. How can I implement a exception catcher in phapi.dll, so the program does not crash, but is able to reinitiate phapi if necessary. Thank you for your patient in reading this. -- ---- Best regards / Mit freundlichen Grüssen Cantemir Mihu -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Crashing because of phapi.dll
Hello,my softphone based on phapi, running on Windows does crash from time to time. Therefore, I included a crash report generator, that generates so called minidumps. With this dumps and the phapi source code, I am able to track the exact line of crash. I found out three such lines: 1. in rtpmod.c, function void rtp_putq(queue_t *q, mblk_t *mp)the line:if (rtp->timestamp == tmprtp->timestamp)causes ACCESS_VIOLATION, because the rtp variable is 0x000C2. in phapi.c , function ph_call_media_stop(phcall_t *ca)the line:g_mutex_free(ca->mses->critsec_mstream_init);causes ACCESS_VIOLATION, because the ca-mses member is NULL, allthough there is a check if (ca->mses) ??? 3. in rtpsession.c, function rtp_session_create_packet (RtpSession * session, gint header_size, char *payload, gint payload_size)the line:rtp->version = 2;causes ACCESS_VIOLATION, because the rtp variable is NULL! I cand send you the *.pdb files, if you need them and any other info. If you have time, please tell me what could be the problem of this errors and how I can avoid them. I tried using __try... __finally on error number 2 (which is the most often), but without any success. How can I implement a exception catcher in phapi.dll, so the program does not crash, but is able to reinitiate phapi if necessary.Thank you for your patient in reading this.-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Bug report
I think this is a bug:if I register with phApi, make some calls, the unregister and register back, the next call I will answer will crash with an access violation. I traced it down to rtpport.h:g_mutex_lock (GMutex *mut)
{ WaitForSingleObject (mut->h, INFINITE);}static inline voidg_mutex_unlock (GMutex *mut){ ReleaseMutex (mut->h);}mut is NULL when this happens. If I do a simple check like
if (mut) WaitForSingleObject (mut->h, INFINITE);and if (mut) ReleaseMutex (mut->h);it does not crashes any more, but I think someone should investigate this to see if it is the proper way to fix this bug.
P.S. I'm on Windows, using phApi from the owengo-ng trunk.-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] WengoPhone SIP proxies
This RTPproxy is setup by Wengo, together with SER, isn't it? It has nothing to do with phapi or httptunnel?Thanks,CantiOn 5/9/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote:Cantemir Mihu wrote: > Hello,>> could anyone clarify this for me:> - the SIP registrar of WengoPhone is voip.wengo.fr> <http://voip.wengo.fr > (213.91.9.213 <http://213.91.9.213>)> - the SIP proxy (calls are routed through this?) is> vipsip.host.wengo.fr <http://vipsip.host.wengo.fr> (213.91.9.210> <http://213.91.9.210>) >> I made a call using WengoPhone and the RTP stream was originating from> nothing.host.wengo.fr <http://nothing.host.wengo.fr > (80.118.99.23> <http://80.118.99.23>). What is this? Does it have something to do> with the http tunnel? As I see from sso2.php , the tunnel IP's are> > 80.118.99.31 <http://80.118.99.31>"/>> 80.118.99.32 <http://80.118.99.32>"/>> > −> > 80.118.99.51 <http://80.118.99.51>"/>> 80.118.99.52 < http://80.118.99.52>"/>> 80.118.99.53 <http://80.118.99.53>"/>> 80.118.99.54 <http://80.118.99.54>"/>> >> So my question is why did I see this IP 80.118.99.23> < http://80.118.99.23> for the RTP stream?>I believe it's address of RTPProxy serverVadim> Thanks,>> --> > 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> -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] WengoPhone SIP proxies
Hello,could anyone clarify this for me:- the SIP registrar of WengoPhone is voip.wengo.fr (213.91.9.213)- the SIP proxy (calls are routed through this?) is vipsip.host.wengo.fr (213.91.9.210)I made a call using WengoPhone and the RTP stream was originating from nothing.host.wengo.fr (80.118.99.23). What is this? Does it have something to do with the http tunnel? As I see from sso2.php, the tunnel IP's are 80.118.99.31"/>80.118.99.32"/>− 80.118.99.51"/>80.118.99.52"/>80.118.99.53"/> 80.118.99.54"/>So my question is why did I see this IP 80.118.99.23 for the RTP stream? Thanks,-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Event.h boost::signal wrapper
Hello,thanks for integrating my patch.I have another question regarding the implementation of Subject/Observer pattern. I think if you used the code from here http://www.codeproject.com/cpp/FastDelegate.asp you would have saved the dependency of the whole boost library and would have a small performance improvement. I think the boost library is only used for this pattern. Including " FastDelegate.h" would be more easier to maintain, would reduce the compiled file size and it would make life easier for starting developers. Of course the Event class would have to be modified, but this is an easy task. Please share your opinion on this.Thank you,Cantemir MihuOn 4/21/06, Tanguy Krotoff <[EMAIL PROTECTED] > wrote:Cantemir Mihu wrote:> Thanks for the quick answer. I implemented the -= operator because I > don't want to inherit every observer from Trackable and because I want> to be in control of these events at every time.> I attached the diff file, but be aware, I'm not the best in writing code> :-) I have integrated your patch cf:http://dev.openwengo.com/trac/openwengo/trac.cgi/changeset/5109Have a nice week end --Tanguy Krotoff <[EMAIL PROTECTED]>http://openwengo.org-- 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] Event.h boost::signal wrapper
Hello,I'm interested in the Event class, which I find very usefull and handy. But from the comment inside Event.h I see: * timer.minuteEvent -= boost::bind(&Clock::showTime, &clock, _1, _2); * //timer.minuteEvent.disconnect(boost::bind(&Clock::showTime, &clock, _1)); * timer.tick();But there is no -= operator defined in the class. So I want to add one, but the SlotList list only holds functions, not connections. And to be able to use -= one would require the connection for the slot who is to be disconnected. I managed to do this by changing the SlotList typedef to include both the connection and the slot created when adding a slot with +=. Is there another easier way which I have overviewed? Thanks,-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Re: Memory leaks from phapi/exosip (again)
I decided it is easier to create a patch at least for my fixes. You will find this attached. But someone should see when ortp_exit() should be called from phapi, because ortp_init() is called in ph_media_init().
On 4/7/06, Cantemir Mihu <[EMAIL PROTECTED]> wrote:
I made a little mistake,For the first leak, the vl->contact should be released in phDelVLine in
phapi.c with:if (vl->contact) {
osip_free(vl->contact); vl->contact = 0;
}This actually should go to vline_free() from phapi.c
On 4/7/06, Cantemir Mihu <
[EMAIL PROTECTED]> wrote:Hello,I sent an email a long time ago mentioning some memory leaks from phapi. They are still here, it would be grate if someone could investigate them: (my comments below)
-- Block 52591 at 0x01EF1300: 43 bytes --
Call Stack: c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (210): osip_strdup c:\work\owengo-ng\wifo\phapi\phapi.c (1924): phAddVline2
Data: 3C 73 69 70 3A 30 30 39 39 39 39 35 30 30 30 30 30 30 30 30 31 40 31 39 32 2E 31 36 38 2E 31 30 [EMAIL PROTECTED] 2.168.10 35 2E 39 39 3A 35 30 37 31 3E 00
5.99:507 1>..-- Block 52431 at 0x01EEF808: 8 bytes -- Call Stack: c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\owengo-ng\wifo\libosip2\src\osip2\port_thread.c (94): osip_thread_create
c:\work\owengo-ng\wifo\phapi\phapi.c (2862): phInit Data: A8 55 00 00 90 0B 00 00 .U.. -- Block 52031 at 0x01BA4DE0: 4 bytes --
Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\phapi\phmedia-audio.c (2825): ph_media_audio_init
c:\work\owengo-ng\wifo\phapi\phmedia.c (317): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 44 56 00 00 DV..
-- Block 52030 at 0x01ACF3B0: 4 bytes -- Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\ortp\src\str_utils.c (55): mbdb_mutex_init
c:\work\owengo-ng\wifo\ortp\src\ortp.c (86): ortp_init c:\work\owengo-ng\wifo\phapi\phmedia.c (316): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 4C 56 00 00 LV..
-- Block 52029 at 0x01AF8C90: 4 bytes -- Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\ortp\src\str_utils.c (54): mbdb_mutex_init
c:\work\owengo-ng\wifo\ortp\src\ortp.c (86): ortp_init c:\work\owengo-ng\wifo\phapi\phmedia.c (316): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 54 56 00 00 TV..
I think in str_utils.c, ortp_exit() should call mbdb_mutex_cleanup() to release the two mutexes. This should fix at least the last two leaks.For the first leak, the vl->contact should be released in phDelVLine in
phapi.c with:if (vl->contact) { osip_free(vl->contact); vl->contact = 0; }The remaining two leaks are a little bit harder, AFAIK. Please tell me if this fixes will be included in the NG trunk repos.
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
phapi.c.diff
Description: Binary data
ortp.c.diff
Description: Binary data
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Re: Memory leaks from phapi/exosip (again)
I made a little mistake,For the first leak, the vl->contact should be released in phDelVLine in
phapi.c with:if (vl->contact) {
osip_free(vl->contact); vl->contact = 0;
}This actually should go to vline_free() from phapi.cOn 4/7/06, Cantemir Mihu <
[EMAIL PROTECTED]> wrote:Hello,I sent an email a long time ago mentioning some memory leaks from phapi. They are still here, it would be grate if someone could investigate them: (my comments below)
-- Block 52591 at 0x01EF1300: 43 bytes --
Call Stack: c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (210): osip_strdup c:\work\owengo-ng\wifo\phapi\phapi.c (1924): phAddVline2
Data: 3C 73 69 70 3A 30 30 39 39 39 39 35 30 30 30 30 30 30 30 30 31 40 31 39 32 2E 31 36 38 2E 31 30 [EMAIL PROTECTED] 2.168.10 35 2E 39 39 3A 35 30 37 31 3E 00
5.99:507 1>..-- Block 52431 at 0x01EEF808: 8 bytes -- Call Stack: c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\owengo-ng\wifo\libosip2\src\osip2\port_thread.c (94): osip_thread_create
c:\work\owengo-ng\wifo\phapi\phapi.c (2862): phInit Data: A8 55 00 00 90 0B 00 00 .U.. -- Block 52031 at 0x01BA4DE0: 4 bytes --
Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\phapi\phmedia-audio.c (2825): ph_media_audio_init
c:\work\owengo-ng\wifo\phapi\phmedia.c (317): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 44 56 00 00 DV..
-- Block 52030 at 0x01ACF3B0: 4 bytes -- Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\ortp\src\str_utils.c (55): mbdb_mutex_init
c:\work\owengo-ng\wifo\ortp\src\ortp.c (86): ortp_init c:\work\owengo-ng\wifo\phapi\phmedia.c (316): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 4C 56 00 00 LV..
-- Block 52029 at 0x01AF8C90: 4 bytes -- Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\ortp\src\str_utils.c (54): mbdb_mutex_init
c:\work\owengo-ng\wifo\ortp\src\ortp.c (86): ortp_init c:\work\owengo-ng\wifo\phapi\phmedia.c (316): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 54 56 00 00 TV..
I think in str_utils.c, ortp_exit() should call mbdb_mutex_cleanup() to release the two mutexes. This should fix at least the last two leaks.For the first leak, the vl->contact should be released in phDelVLine in
phapi.c with:if (vl->contact) { osip_free(vl->contact); vl->contact = 0; }The remaining two leaks are a little bit harder, AFAIK. Please tell me if this fixes will be included in the NG trunk repos.
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Memory leaks from phapi/exosip (again)
Hello,I sent an email a long time ago mentioning some memory leaks from phapi. They are still here, it would be grate if someone could investigate them: (my comments below)-- Block 52591 at 0x01EF1300: 43 bytes --
Call Stack: c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (210): osip_strdup c:\work\owengo-ng\wifo\phapi\phapi.c (1924): phAddVline2
Data: 3C 73 69 70 3A 30 30 39 39 39 39 35 30 30 30 30 30 30 30 30 31 40 31 39 32 2E 31 36 38 2E 31 30 [EMAIL PROTECTED] 2.168.10 35 2E 39 39 3A 35 30 37 31 3E 00
5.99:507 1>..-- Block 52431 at 0x01EEF808: 8 bytes -- Call Stack: c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\owengo-ng\wifo\libosip2\src\osip2\port_thread.c (94): osip_thread_create
c:\work\owengo-ng\wifo\phapi\phapi.c (2862): phInit Data: A8 55 00 00 90 0B 00 00 .U.. -- Block 52031 at 0x01BA4DE0: 4 bytes --
Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\phapi\phmedia-audio.c (2825): ph_media_audio_init
c:\work\owengo-ng\wifo\phapi\phmedia.c (317): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 44 56 00 00 DV..
-- Block 52030 at 0x01ACF3B0: 4 bytes -- Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\ortp\src\str_utils.c (55): mbdb_mutex_init
c:\work\owengo-ng\wifo\ortp\src\ortp.c (86): ortp_init c:\work\owengo-ng\wifo\phapi\phmedia.c (316): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 4C 56 00 00 LV..
-- Block 52029 at 0x01AF8C90: 4 bytes -- Call Stack: c:\work\owengo-ng\wifo\ortp\src\rtpport.h (216): g_malloc c:\work\owengo-ng\wifo\ortp\src\rtpport.h (415): g_mutex_new c:\work\owengo-ng\wifo\ortp\src\str_utils.c (54): mbdb_mutex_init
c:\work\owengo-ng\wifo\ortp\src\ortp.c (86): ortp_init c:\work\owengo-ng\wifo\phapi\phmedia.c (316): ph_media_init c:\work\owengo-ng\wifo\phapi\phapi.c (2816): phInit Data: 54 56 00 00 TV..
I think in str_utils.c, ortp_exit() should call mbdb_mutex_cleanup() to release the two mutexes. This should fix at least the last two leaks.For the first leak, the vl->contact should be released in phDelVLine in
phapi.c with:if (vl->contact) { osip_free(vl->contact); vl->contact = 0; }The remaining two leaks are a little bit harder, AFAIK. Please tell me if this fixes will be included in the NG trunk repos.
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Memory leaks in httptunnel library
Hello,I don't see any updates regarding this on NG trunk. How come?On 4/5/06, Julien Gilli <[EMAIL PROTECTED] > wrote:Hello, On 4/4/06, Cantemir Mihu < [EMAIL PROTECTED]> wrote: I just found some memory leaks in http_tunnel_init_host(): httpServerIP = strdup(hostIP)This strduped string is not released anywhere. Maybe this should go to http_tunnel_close() Thank you very much for pointing this out. Julien told me that, by further reading his code, he found more leaks of the same kind. In the future, feel free to create a patch using svn diff and create a Trac ticket with it attached. Thank you very much again.Best regards,-- Julien Gilli -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] 16 kHz resampling
Hello,what is the 16 kHz forced resampling used to? Did you notice strange behaviors with sound-card sampling at 8 kHz or something like that? Will this option be enabled as default from now on? -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Memory leaks in httptunnel library
Hello,I just found some memory leaks in http_tunnel_init_host(): httpServerIP = strdup(hostIP)This strduped string is not released anywhere. Maybe this should go to http_tunnel_close() -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: Removing curl and opensSSL - was: Re:[Wengophone-devel] Just want to call
Hello,I'm interested in this http tunnel server app. I want to test phapi with the use of a http tunnel, so how can I install myself such a tunnel server?Thank you.On 3/17/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote: Gianluca Sforna wrote:>Since there is some interest (at least from me...) for trying to>shorten the dependency list of wengophone, I this it's worth replaying>this email in a new thread...>This would be even _more_ valuable since libcurl is the directory >adding the most bloat to the source package.>>>It would be pretty difficult to use another tunnel package, because allothre tunnel serversdoes not support UDP tunneling If you're interested I have a open source version of tunnel serverit is not very well tested thoughVadim>-- Forwarded message -->From: Gianluca Sforna < [EMAIL PROTECTED]>>Date: Mar 17, 2006 11:06 AM>Subject: Re: [Wengophone-devel] Just want to call>To: mstute <[EMAIL PROTECTED]>>Cc: wengophone-devel@lists.openwengo.com>>>On 3/16/06, mstute <[EMAIL PROTECTED]> wrote: OpenSSL is a Curl dependency & Curl is a http-tunnel one. So if you configure>>phapi with use_tunnel = 0 you don't need all these libraries.>>Interesting... Does this means that if we remove http-tunnel, curl and >openSSL can go away???>For example, I can imagine replacing the (in house ?) developed>http-tunnel lib with something else; from a quick google tour:>> http://the-linux-academy.co.uk/downloads.htm>http://www.gnu.org/software/httptunnel/httptunnel.html>>could be candidates... >>cheers>>Gianluca>___>Wengophone-devel mailing list>Wengophone-devel@lists.openwengo.com >http://dev.openwengo.com/mailman/listinfo/wengophone-devel>___ Wengophone-devel mailing listWengophone-devel@lists.openwengo.comhttp://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Enabling VAD/CNG context based
Hello,this is what I did to enable VAD only if the CNG payload was negotiated:in ph_call_media_start() I changed if (phcfg.vad & 0x8000)to if ((phcfg.vad & 0x8000) && ca->cng)Additional, in ph_call_retrieve_payloads() I changedca->cng = !eXosip_retrieve_negotiated_specific_payload(ca->did, PH_MEDIA_CN_PT_STR, strlen(PH_MEDIA_CN_PT_STR)); toca->cng = (eXosip_retrieve_negotiated_specific_payload(ca->did, PH_MEDIA_CN_PT_STR, strlen(PH_MEDIA_CN_PT_STR)) != -1);But this should work either way. What I noticed about CNG, is that in the function ph_generate_comfort_noice(), ret = audio_stream_get_out_space(stream, &used); always returns -19952 and thus exits with "IOCTL error" and it does not generate a CNG noise.What could be the cause and solution of this? On 3/29/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote: Cantemir Mihu wrote: > Hello,>> is it possible to enable VAD/CNG only if CNG was negotiated between> both parties? If yes, how?> When I test it now, if I enable VAD/CNG on one side and call another> who does not support this feature, the first side has VAD enabled and > does not send voice packets, which on the other side appears very> annoying. The first side should disable VAD if CNG payload was not> negotiated.>> Thanks for your help.>Normally phApi tries to negotiatie the CNG payload... take a look in ph_call_retreive_payloadsbut frankly this is note very well testedVadim> --> > 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>-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Enabling VAD/CNG context based
Hello,is it possible to enable VAD/CNG only if CNG was negotiated between both parties? If yes, how?When I test it now, if I enable VAD/CNG on one side and call another who does not support this feature, the first side has VAD enabled and does not send voice packets, which on the other side appears very annoying. The first side should disable VAD if CNG payload was not negotiated. Thanks for your help.-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] CNG
Hello,I know this list is for development issues, but I want to ask about the CNG support:The CNG noise is generated only if the other party sends CNG packets informing about the noise level? If the CNG payload is not negotiated between A and B, and A uses silence supression (VAD), then B would hear nothing between the speech parts of A? I think this is not really good, B should hear some generated noise (if he wants to), even if A does not send CNG related RTP packets. I hope anyone understands what I'm trying to say and will reply with info.-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Miniua as echo tester
Hello, I tried to use Half Duplex (at least for testing), but I saw and mentioned a bug, and got this reply from Jérôme WAGNER: There might be a bug ; but the "PH_HDX_MODE_MIC" branch is not tested/used So I stopped trying using half duplex.About the 100% problem: did you see this on systems other than Windows? If no, then this could be a problem with PortAudio MME implementation which I'm using. By the way, how can I activate DirectSound instead of MME for WengoPhoneNG? Thanks again for all of your replies.On 3/23/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote: Cantemir Mihu wrote:> The problem could be either phApi or the portaudio library. > Do you think that upgrading portaudio would help here?>I strongly suspect that the problem is in echo canceller codeBut i know that phmedia-audio.c is strongly depended on various timingrelated fenomena... So if latest portaudio changes something in timingcharacteristics the problemmight go away...The best way IMO is not to use AEC but to use HALF DUPLEX mode (thiswill not work for echo server, for echo server simply use -noaec on miniua command line)Vadim> On 3/23/06, *Vadim Lebedev* <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote: >> Cantemir Mihu wrote:>> > thanks, it works OK.> > I'm still having the echo problem I mentioned before in another> > message thread. If I run miniua without the -noaec switch, after > some> > time CPU gets to 100% and nothing is understandable any more. What> > could be the problem and solution for this?> >> I've seen this behaviour couple of times... but for the moment i have > no idea what happens>> Vadim>> > Thank you.> >> > On 3/23/06, *Vadim Lebedev* < [EMAIL PROTECTED] > [EMAIL PROTECTED]>> > [EMAIL PROTECTED] [EMAIL PROTECTED] >>> wrote:> >> > Cantemir Mihu wrote:> >> > > Hello,> > >> > > is there any easy way to setup miniua as a echo tester? Or > is there> > > something else I could use for this on Windows?> > >> > > Thanks> > >> > If you launch miniua with -autoans argument it well > automatically> > answer> > incoming calls...> >> > Then if you can play with Windows Mixer settings to route> Speaker> > output > > to Input so yo'll have your echo server> >> > Vadim> >> > > --> > > > > > Best regards / Mit freundlichen Grüssen > > > Cantemir Mihu> > >> >> >>> > >> > >___ > > >Wengophone-devel mailing list> > > Wengophone-devel@lists.openwengo.com> Wengophone-devel@lists.openwengo.com>> > Wengophone-devel@lists.openwengo.com> Wengophone-devel@lists.openwengo.com>>> > >http://dev.openwengo.com/mailman/listinfo/wengophone-devel> < http://dev.openwengo.com/mailman/listinfo/wengophone-devel>> > >> >> >> >> > > > --> > > > Best regards / Mit freundlichen Grüssen> > Cantemir Mihu>>>>>> --> > Best regards / Mit freundlichen Grüssen > Cantemir Mihu-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Miniua as echo tester
Hello,is there any easy way to setup miniua as a echo tester? Or is there something else I could use for this on Windows? Thanks-- 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] phapi bug
Hello,I used the following config: hdxmode = PH_HDX_MODE_MICvad = 0noaec = 0If I start a call, I get an exception in ph_encode_and_send_audio_frame() -> ph_vad_update0(): s->pwr[] is NULL;Try to reproduce it and confirm if this is a known bug.-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Building miniua
Thank you, this did the trick.On 3/21/06, Julien Gilli <[EMAIL PROTECTED]> wrote: Hello,On 3/21/06, Cantemir Mihu < [EMAIL PROTECTED]> wrote: I tried to add /ENTRY:"wWinMainCRTStartup" to SConscript, but I think the problem is the /subsystem:windows switch. It should be subsystem:console. But how can I change this? Changing the last line of SOptions from WengoShowWindowsConsole(False) to WengoShowWindowsConsole(True) may temporarily fix the problem. I do not have any win32 box at hand, so i'm just guessing. Regards,-- Julien Gilli -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Building miniua
link /nologo /DEBUG /NODEFAULTLIB:MSVCRT.LIB /subsystem:windows /OUT:debug\wifo\miniua\miniua.exe /LIBPATH:debug\wifo\phapi /LIBPATH:wifo\phapi /LIBPATH:debug\wifo\eXosip /LIBPATH:wifo\eXosip /LIBPATH:debug\wifo\libosip2 /LIBPATH:wifo\libosip2 /LIBPATH:debug\wifo\ortp /LIBPATH:wi fo\ortp /LIBPATH:debug\wifo\phapi\ilbc /LIBPATH:wifo\phapi\ilbc /LIBPATH:debug\wifo\phapi\stun /LIBPATH:wifo\phapi\stun /LIBPATH:debug\wifo\phapi\gsm /LIBPATH:wifo\phapi\gsm /LIBPATH:debug\libs\global /LIBPATH:libs\global /LIBPATH:debug\libs\timer /LIBPATH:libs\timer /LIBPATH:deb ug\wifo\netlib /LIBPATH:wifo\netlib /LIBPATH:debug\libs\curl /LIBPATH:libs\curl /LIBPATH:debug\libs\openssl /LIBPATH:libs\openssl /LIBPATH:debug\libs\openssl\out32\msvc /LIBPATH:libs\openssl\out32\msvc /LIBPATH:debug\wifo\httptunnel /LIBPATH:wifo\httptunnel /LIBPATH:debug\libs\po rtaudio /LIBPATH:libs\portaudio /LIBPATH:debug\libs\portaudio\lib /LIBPATH:libs\portaudio\lib phapi.lib eXosip.lib ortp.lib osip.lib ilbc.lib stun.lib gsm.lib global.lib wtimer.lib netlib.lib httptunnel.lib wengocurl.lib openssl.lib libeay32.lib ssleay32.lib gdi32.lib urlmon.libportaudio.lib winmm.lib ws2_32.lib user32.lib shell32.lib advapi32.lib wininet.lib iphlpapi.lib strmiids.lib comsupp.lib ole32.lib debug\wifo\miniua\miniua.objMSVCRTD.lib(crtexew.obj) : error LNK2019: unresolved external symbol [EMAIL PROTECTED] referenced in function _WinMainCRTStartupdebug\wifo\miniua\miniua.exe : fatal error LNK1120: 1 unresolved externals scons: *** [debug\wifo\miniua\miniua.exe] Error 1120scons: building terminated because of errors.I tried to add /ENTRY:"wWinMainCRTStartup" to SConscript, but I think the problem is the /subsystem:windows switch. It should be subsystem:console. But how can I change this? -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] building miniua
I want to build miniua. I use scons miniua and receive these errors:phapi (internal)python24 (system)pyphapi (internal)scons: *** Two environments with different actions were specified for the same target: spxec.objFile "wifo\phapi\SConscript", line 324, in ?Please advise-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] DTMF
Hello,is dtmf sending supported in phApi? How is it used? rfc2833, inband or SIP info?as I can see from ph_msession_send_dtmf(), mode parameter is not used. So I guess it's inband, wright?-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] __PRETTY_FUNCTION__
I'm always making the same mistake: compiling before updating :(Now it's working.ThanksOn 3/15/06, Julien Gilli < [EMAIL PROTECTED]> wrote:Hello, On 3/15/06, Cantemir Mihu <[EMAIL PROTECTED]> wrote: what's with this __PRETTY_FUNCTION__ thing? Could you please tell me which revision you use? mstute has fixed this problem with changeset 4523: http://dev.openwengo.com/trac/openwengo/trac.cgi/changeset/4523 , but some of these macro uses might still be somewhere in the code. Thank you very much for your feedback! Regards,-- Julien Gilli -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] __PRETTY_FUNCTION__
what's with this __PRETTY_FUNCTION__ thing?cl /nologo /Zm200 /EHsc /GX /GR -Zi /LDd -Gm /DEBUG -D_DEBUG /MDd /W3 -w34100 -w34189 /wd4290 /TP /DMULTIIMWRAPPER=1 /DQT_CORE_LIB=1 /DQT_DL L=1 /DQT_GUI_LIB=1 /DQT_LARGEFILE_SUPPORT=1 /DQT_NO_KEYWORDS=1 /DQT_PLUGIN=1 /DQT_THREAD_SUPPORT=1 /DUNICODE=1 /DWIN32=1 /IC:\qt\4.1.1\include /Idebug\wengophone\src /Iwengophone\src /Idebug\libs\util\include /Ilibs\util\include /IC:\Boost\include\boost-1_33_1 /Idebug\libs\openss l\inc32\openssl /Ilibs\openssl\inc32\openssl /Idebug\libs\openssl\inc32 /Ilibs\openssl\inc32 /Idebug\libs\curl\include /Ilibs\curl\include /Idebug\libs\curl\lib /Ilibs\curl\lib /Idebug\libs\global\include /Ilibs\global\include /Idebug\libs\global\include\msvc /Ilibs\global\includ e\msvc /Idebug\libs\imwrapper\include /Ilibs\imwrapper\include /Idebug\wengoscons\libs\glib\include /Iwengoscons\libs\glib\include /Idebug\libs\sipwrapper\include /Ilibs\sipwrapper\include /Idebug\libs\wenbox\include /Ilibs\wenbox\include /Idebug\libs\shlibloader\include /Ilibs\s hlibloader\include /Idebug\libs\tinyxml /Ilibs\tinyxml /Idebug\libs\sound\include /Ilibs\sound\include /Idebug\libs\portaudio\pa_common /Ilibs\portaudio\pa_common /Idebug\wifo\netlib\include /Iwifo\netlib\include /Idebug\wifo\netlib /Iwifo\netlib /Idebug\wifo\httptunnel /Iwifo\ht tptunnel /IC:\qt\4.1.1\include /IC:\qt\4.1.1\include\Qt /IC:\qt\4.1.1\include\QtCore /IC:\qt\4.1.1\include\QtGui /IC:\qt\4.1.1\include\QtNetwork /IC:\qt\4.1.1\include\QtDesigner /IC:\qt\4.1.1\include\QtXml /IC:\qt\4.1.1\include\QtSvg /IC:\qt\4.1.1\include\ActiveQt /Idebug\libs\qt util\c:\qt\4.1.1\include /Ilibs\qtutil\c:\qt\4.1.1\include /Idebug\libs\qtutil\include /Ilibs\qtutil\include /Idebug\libs\webcam\include /Ilibs\webcam\include /Idebug\libs\pixertool\include /Ilibs\pixertool\include /Idebug\libs\ffmpeg /Ilibs\ffmpeg /Idebug\libs\ffmpeg\libavutil / Ilibs\ffmpeg\libavutil /Idebug\libs\ffmpeg\libavcodec /Ilibs\ffmpeg\libavcodec /Idebug\libs\trayicon\c:\qt\4.1.1\include /Ilibs\trayicon\c:\qt\4.1.1\include /Idebug\libs\trayicon /Ilibs\trayicon /Idebug\libs\imwrapper\src\multiim /Ilibs\imwrapper\src\multiim /Idebug\libs\sipwrapp er\src\phapi /Ilibs\sipwrapper\src\phapi /Idebug\wifo\phapi /Iwifo\phapi /Idebug\wifo\eXosip\include /Iwifo\eXosip\include /Idebug\wifo\libosip2\include /Iwifo\libosip2\include /Idebug\wifo\libosip2\include\osipparser2 /Iwifo\libosip2\include\osipparser2 /Idebug\wifo\libosip2\src \osipparser2 /Iwifo\libosip2\src\osipparser2 /Idebug\wifo\libosip2\src\osip2 /Iwifo\libosip2\src\osip2 /Idebug\wifo\ortp\src /Iwifo\ortp\src /Idebug\wifo\phapi\ilbc /Iwifo\phapi\ilbc /Idebug\wifo\phapi\stun /Iwifo\phapi\stun /Idebug\wifo\phapi\gsm /Iwifo\phapi\gsm /Idebug\libs\ti mer\include /Ilibs\timer\include /Idebug\libs\imwrapper\src\gaim /Ilibs\imwrapper\src\gaim /Idebug\libs\gaim\include /Ilibs\gaim\include /cwengophone\src\presentation\qt\QtWengoPhone.cpp /Fodebug\wengophone\src\presentation\qt\QtWengoPhone.obj QtWengoPhone.cppc:\work\owengo-ng\wengophone\src\presentation\qt\phonecall\QtPhoneCall.h(54) : warning C4100: 'displayName' : unreferenced formal parameterc:\work\owengo-ng\wengophone\src\presentation\qt\phonecall\QtPhoneCall.h(54) : warning C4100: 'userName' : unreferenced formal parameter c:\work\owengo-ng\wengophone\src\presentation\qt\phonecall\QtPhoneCall.h(54) : warning C4100: 'sipAddress' : unreferenced formal parameterc:\work\owengo-ng\wengophone\src\presentation\qt\phonecall\QtPhoneCall.h(53) : warning C4100: 'callId' : unreferenced formal parameter c:\work\owengo-ng\wengophone\src\presentation\qt\phonecall\QtPhoneCall.h(53) : warning C4100: 'lineId' : unreferenced formal parameterc:\work\owengo-ng\wengophone\src\presentation\qt\phonecall\QtPhoneCall.h(53) : warning C4100: 'state' : unreferenced formal parameter wengophone\src\presentation\qt\QtWengoPhone.cpp(205) : error C2065: '__PRETTY_FUNCTION__' : undeclared identifierwengophone\src\presentation\qt\QtWengoPhone.cpp(235) : error C3861: '__PRETTY_FUNCTION__': identifier not found, even with argument-dependen t lookupwengophone\src\presentation\qt\QtWengoPhone.cpp(275) : error C3861: '__PRETTY_FUNCTION__': identifier not found, even with argument-dependent lookupwengophone\src\presentation\qt\QtWengoPhone.cpp(341) : error C3861: '__PRETTY_FUNCTION__': identifier not found, even with argument-dependen t lookupwengophone\src\presentation\qt\QtWengoPhone.cpp(368) : error C3861: '__PRETTY_FUNCTION__': identifier not found, even with argument-dependent lookup-- 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
Re: [Wengophone-devel] phApi used in a queue
Hello,I think I found a bug in your code:void ph_release_call(phcall_t *ca){
ca->cid = -1; if (ph_call_hasaudio(ca))
{ ph_call_media_stop(ca); }
memset(ca, 0, sizeof(phcall_t));}
this should set -1 into ca->cid so ph_locate_call() will use this entry in ph_calls[] for the next call. But obviously the line:
memset(ca, 0, sizeof(phcall_t));
removes this -1 and sets it to 0. This is why ph_locate_call() will not find any useable entry in ph_calls[] and will fail, thus returning error code 500 on a new call.
Solution:void ph_release_call(phcall_t *ca)
{
if (ph_call_hasaudio(ca))
{
ph_call_media_stop(ca);
}
memset(ca, 0, sizeof(phcall_t));
ca->cid = -1;
}Please let me know if this is correct and has no obvious side effects.
On 2/23/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote:
Cantemir Mihu wrote:> Hello,>> I noticed this behavior: I have created a queue on Asterisk PBX where> I am the only one in this queue. If I call this Queue and enable some> automatically rejecting calls method, than the Asterisk will keep
> trying to call me in an endless loop. This is ok with the Asterisk,> but the phApi library is sending after some time the following response:> 500 Internal Server Error> After this starts, I am not be able to receive any other calls. It
> seems to remain in this state where it answers everything with> Internal Server Error.> I traced it down to here:>> ph_call_new() -> ph_locate_call() -> returns 0;Hi Cantemir,
It seems that the call table is completly full...Somehow you've managed to create more than PH_MAX_CALLS callsVadim-- 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
Re: [Wengophone-devel] A voice library bug
Finally I understood how things are working :-)I am now able to test Speex plugin and the AMR plugin. I guess you did some kind of testing before putting speex (alias G729) in front of the list. Which is the best codec in your opinion? I did only some simple tests between GSM and ILBC: GSM uses 2,14 kbytesiLBC uses 2,45 kbytes. From the quality they seem pretty equal. I also checked this links:http://lists.digium.com/pipermail/asterisk-users/2003-June/014788.html http://compare.ozvoip.com/codecs.phpbut I am dieing to hear your opinion on this.On 3/3/06, Julien Gilli <[EMAIL PROTECTED]> wrote: Hello, On 3/3/06, Cantemir Mihu <[EMAIL PROTECTED]> wrote: recompiled qtwengophone with the change you suggested, but it is the same. Only if I use noaec=1, it works fine. Ok, thanks for the report. I tried to record the sound output as an example, but with no success. I will try again when time allows it. Great, please let us know when you find some time to do it. Btw, is speex codec enabled by default in phApi? if i set the payload SPEEX/8000 as the first in the payload list, will it get used? (of course if the other party allows it) To use speex you need to build phapi's speex plugin using scons phspeexplugin, and you'll also need to place "SPEEX-WB" first in the audio_codecs member of the phConfig_t structure. Currently, a Wengo's platform limitation makes us alias SPEEX-WB as G726-64WB, so you'll also have to disable 'speexwb-replaces-g726wb' in SOptions (by giving it the value 0) if you want to use SPEEX-WB as codec name for speex. Otherwise, you'll have to use G726-64WB as codec name for speex in the audio_codecs member. The aliasing thingy is why G726-64WB is setup as first codec in libs/sipwrapper/src/phapi/PhApiWrapper.cpp at line 543, not SPEEX-WB. I hope it helps. Regards, -- Julien Gilli -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] A voice library bug
Hello,recompiled qtwengophone with the change you suggested, but it is the same. Only if I use noaec=1, it works fine.I tried to record the sound output as an example, but with no success. I will try again when time allows it. Btw, is speex codec enabled by default in phApi? if i set the payload SPEEX/8000 as the first in the payload list, will it get used? (of course if the other party allows it) On 3/3/06, Julien Gilli <[EMAIL PROTECTED]> wrote: On 3/3/06, Cantemir Mihu <[EMAIL PROTECTED] > wrote: I don't know what the best translation is for what I mean, but: by microphone effect I mean when you put your mic next to the speaker, and a "loop" is created so the sound rises in intensity. :-) Ok, i understand what you mean. Thank you very much for your clear explanation. I am using Windows, and I use only the configuration in phApi phcfg.noaec. Please tell me how can I activate/deactivate speex aec. You can change the following line: 'USE_SPXEC' : 1, to: 'USE_SPXEC' : 0, in wifo/phapi/SConscript at line 144. Please, let us know how it goes when you disable it. Thank you very much for your feedback. Regards,-- Julien Gilli -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] A voice library bug
Hi,I don't know what the best translation is for what I mean, but: by microphone effect I mean when you put your mic next to the speaker, and a "loop" is created so the sound rises in intensity. :-) The behavior is very random. I can't determine a average delay. From 3-4 seconds to 1-2 minutes, I guess.I am using Windows, and I use only the configuration in phApi phcfg.noaec. Please tell me how can I activate/deactivate speex aec. Thank you very much for your help.On 3/3/06, Jérôme WAGNER <[EMAIL PROTECTED]> wrote: Hello, Could you explain a bit more what you consider being a "microphone effect" ? What is the average delay after which the CPU goes to 100% ? The last time I heard that was under windows, while using the speex AEC : is that your configuration ? is the answer is yes, can you try disabling the speex AEC (it will fallback onto the "classic" aec) and do some tests again ? Jérôme De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] De la part de Cantemir Mihu Envoyé : vendredi 3 mars 2006 08:18 À : Openwengo Objet : [Wengophone-devel] A voice library bug Hello, I have tested qtwengophone a lot, especially phApi. If AEC is enabled (noaec=0), after a time (no specific moment), the CPU load of the application rises to 100% and stays there until the call is ended. With aec disabled (noaec=1), this problem does not appear. So my guess is the AEC algorithm or its implementation is kind of buggy. When this happens, the distortment of the voice is like a "microphony effect". At least it sounds like that. Maybe this is helpfull in reproducing this behavior. -- ---- Best regards / Mit freundlichen Grüssen Cantemir Mihu -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] A voice library bug
Hello,I have tested qtwengophone a lot, especially phApi. If AEC is enabled (noaec=0), after a time (no specific moment), the CPU load of the application rises to 100% and stays there until the call is ended. With aec disabled (noaec=1), this problem does not appear. So my guess is the AEC algorithm or its implementation is kind of buggy. When this happens, the distortment of the voice is like a "microphony effect". At least it sounds like that. Maybe this is helpfull in reproducing this behavior.-- 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] Problem in port audio on Windows
Hello,I am not able to hear anything on a call made with phApi, unless the changes from the patch are applied. It seems that my audio devices can't handle the channelCount, or there is another error involved somewhere. Anyway, with this changes made, everything works fine.
What do you think, what's the cause of this problems?Index: pa_win_wmme.c===--- pa_win_wmme.c (revision 4354)+++ pa_win_wmme.c (working copy)
@@ -1043,8 +1043,8 @@ outputDeviceInfo = hostApi->deviceInfos[ outputParameters->device ]; /* check that output device can support outputChannelCount */- if( outputChannelCount > outputDeviceInfo->maxOutputChannels )
- return paInvalidChannelCount;+// if( outputChannelCount > outputDeviceInfo->maxOutputChannels )+ // return paInvalidChannelCount; /* test for valid sample rate, see comment above */
winMmeOutputDeviceId = LocalDeviceIndexToWinMmeDeviceId( winMmeHostApi, outputParameters->device );@@ -1923,8 +1923,8 @@ for( i=0; i < deviceCount; ++i ) {- if( devices[i].channelCount < 1 || devices[i].channelCount
- > hostApi->deviceInfos[ devices[i].device ]->maxOutputChannels )+ if( devices[i].channelCount < 1 /*|| devices[i].channelCount+ > hostApi->deviceInfos[ devices[i].device ]->maxOutputChannels */)
return paInvalidChannelCount; } -- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Register to a different SIP proxy
Hello,where can I change the code so the NG version automatically registers on a different SIP server? 10x-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: r4341 - wengophone-ng/trunk/wifo/phapi
I want to confirm this, after using this patch I could not hear anything on calls made with phApi.Obviously, krp's attempt was not succesfully. Maybe he will find out why. Till then, someone should remove this changes from the trunk.
On 3/1/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
Please revert this patch , it will seriously screw things
Vadim
[EMAIL PROTECTED] wrote:
Please, do not reply to this mailing list, use wengophone-devel instead.
Author: krp
Date: 2006-02-28 18:35:30 +0100 (Tue, 28 Feb 2006)
New Revision: 4341
Modified:
wengophone-ng/trunk/wifo/phapi/phapi.c wengophone-ng/trunk/wifo/phapi/phmedia-audio.c wengophone-ng/trunk/wifo/phapi/phmedia-video.cLog:Remove the WEIRDO newstreams |= 1 << flag
Modified: wengophone-ng/trunk/wifo/phapi/phapi.c===--- wengophone-ng/trunk/wifo/phapi/phapi.c 2006-02-28 16:20:32 UTC (rev 4340)+++ wengophone-ng/trunk/wifo/phapi/phapi.c 2006-02-28 17:35:30 UTC (rev 4341)
@@ -673,7 +673,7 @@ int ph_call_hasaudio(phcall_t *ca) {- if (ca->mses && (ca->mses->activestreams & (1 << PH_MSTREAM_AUDIO1)))+ if (ca->mses && (ca->mses->activestreams & (PH_MSTREAM_AUDIO1)))
return 1;return 0;@@ -3134,7 +3134,7 @@ struct ph_mstream_params_s *msp = &s->streams[PH_MSTREAM_VIDEO1]; int ttype; - s->newstreams |= (1 << PH_MSTREAM_VIDEO1);
+ s->newstreams |= (PH_MSTREAM_VIDEO1);ttype = ca->nego_mflags & (PH_STREAM_VIDEO_RX | PH_STREAM_VIDEO_RX); @@ -3176,7 +3176,7 @@ { struct ph_mstream_params_s *msp = &s->streams[PH_MSTREAM_AUDIO1];
- s->newstreams |= (1 << PH_MSTREAM_AUDIO1);+ s->newstreams |= (PH_MSTREAM_AUDIO1); s->dtmfCallback = ph_wegot_dtmf; s->endCallback = ph_stream_ended;Modified: wengophone-ng/trunk/wifo/phapi/phmedia-
audio.c===--- wengophone-ng/trunk/wifo/phapi/phmedia-audio.c 2006-02-28 16:20:32 UTC (rev 4340)+++ wengophone-ng/trunk/wifo/phapi/phmedia-audio.c
2006-02-28 17:35:30 UTC (rev 4341)@@ -1715,7 +1715,7 @@ newstreams = s->newstreams; s->newstreams = 0; - if (!(newstreams & (1 << PH_MSTREAM_AUDIO1)))+ if (!(newstreams & (PH_MSTREAM_AUDIO1)))
{ PH_MSESSION_AUDIO_UNLOCK(); return 0;@@ -2054,7 +2054,7 @@sp->flags |= PH_MSTREAM_FLAG_RUNNING; sp->streamerData = stream;- s->activestreams |= (1 << PH_MSTREAM_AUDIO1);
+ s->activestreams |= (PH_MSTREAM_AUDIO1);DBG4_MEDIA_ENGINE("ph_mession_audio_start: s=%08x.stream=%08x\n", s, stream,0); @@ -2294,7 +2294,7 @@ phastream_t *stream = (phastream_t *) msp->streamerData;
int confflags = s->confflags; - s->activestreams &= ~(1 << PH_MSTREAM_AUDIO1);+ s->activestreams &= ~(PH_MSTREAM_AUDIO1);if (confflags) ph_msession_audio_conf_stop(s->confsession, s);
Modified: wengophone-ng/trunk/wifo/phapi/phmedia-video.c===--- wengophone-ng/trunk/wifo/phapi/phmedia-video.c 2006-02-28 16:20:32 UTC (rev 4340)
+++ wengophone-ng/trunk/wifo/phapi/phmedia-video.c 2006-02-28 17:35:30 UTC (rev 4341)@@ -280,7 +280,7 @@ ph_mstream_params_t *sp = &s->streams[PH_MSTREAM_VIDEO1]; - if (!(s->newstreams & (1 << PH_MSTREAM_VIDEO1)))
+ if (!(s->newstreams & (PH_MSTREAM_VIDEO1))) return 0;if (!sp->localport || !sp->remoteport)@@ -488,7 +488,7 @@ video_stream->mbCounter = 0; video_stream->rxtstamp = 0;
sp->flags |= PH_MSTREAM_FLAG_RUNNING;- s->activestreams |= (1 << PH_MSTREAM_VIDEO1);+ s->activestreams |= (PH_MSTREAM_VIDEO1); @@ -1083,10 +1083,10 @@ struct ph_mstream_params_s *msp = &s->streams[PH_MSTREAM_VIDEO1];
phvstream_t *stream = (phvstream_t *) msp->streamerData; - if (!(s->activestreams & (1 << PH_MSTREAM_VIDEO1)))+ if (!(s->activestreams & (PH_MSTREAM_VIDEO1))) return;
- s->activestreams &= ~(1 << PH_MSTREAM_VIDEO1);+ s->activestreams &= ~(PH_MSTREAM_VIDEO1); if (!stream)
___Wengophone-commit mailing list[EMAIL PROTECTED]
http://dev.openwengo.com/mailman/listinfo/wengophone-commit
___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: compiling ng
I did this in order to compile ng version:in wengoscons\libs\qt4\Sconscript I replacedthe lineqtdir = os.environ['QTDIR']withqtdir = 'c:\\qt\\4.1.0'And now it works :-)Hopefully this is understanable for someone else who finds a better method On 2/27/06, Cantemir Mihu <[EMAIL PROTECTED]> wrote: Anyone managed to fix ticket 341? This is very annoying for me, as I cannot compile openwengo :-((On 2/24/06, Julien Gilli < [EMAIL PROTECTED]> wrote: On 2/24/06, Cantemir Mihu <[EMAIL PROTECTED]> wrote: QTDIR="c:\qt\4.1.0"qtincludedir="c:\qt\4.1.0\include"qtlibdir="c:\qt\4.1.0\Do you mean QTINCLUDEDIR and QTLIBDIR (with capitalized letters)? >From the command line of cl I see that the /I parameters are messed up: /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtGuiThat's right, but there should be at least one path that is not messed up on each command line for Qt headers.A ticket about this issue has been created recently: http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/341 . Regards,-- Julien Gilli-- Julien Gilli ___Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: compiling ng
Anyone managed to fix ticket 341? This is very annoying for me, as I cannot compile openwengo :-((On 2/24/06, Julien Gilli < [EMAIL PROTECTED]> wrote: On 2/24/06, Cantemir Mihu <[EMAIL PROTECTED]> wrote: QTDIR="c:\qt\4.1.0"qtincludedir="c:\qt\4.1.0\include"qtlibdir="c:\qt\4.1.0\Do you mean QTINCLUDEDIR and QTLIBDIR (with capitalized letters)? >From the command line of cl I see that the /I parameters are messed up: /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtGuiThat's right, but there should be at least one path that is not messed up on each command line for Qt headers.A ticket about this issue has been created recently: http://dev.openwengo.com/trac/openwengo/trac.cgi/ticket/341 . Regards,-- Julien Gilli-- Julien Gilli ___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Which codec is used?
Hello,10x for the info.Vadim, I think this function should be included in phApi.h, don't you think?Does this function handle the actual negotiation: ph_call_retrieve_payloads(phcall_t *ca, eXosip_event_t *je, int flags) ?
How does the negotiation work? The first codec that is available for both parties is taken? Does the order in which codecs are added really matter?On 2/26/06,
Nguyen <[EMAIL PROTECTED]> wrote:
Hello,1. Call must be dropped. Error code maybe 488.2. phCall structure have a audio_payload_name attribute. I do guesssomething like this in phapi:MY_DLLEXPORT int getCallAudioCodec(int cid, char* codec, int codeclen)
{ phcall_t *ca = ph_locate_call_by_cid(cid); if (!ca)return -PH_BADCID;strncpy(codec,ca->audio_payload_name,codeclen);return 0;}3. Dunno :)On 2/24/06, Cantemir Mihu <
[EMAIL PROTECTED]> wrote:> Hello,>> As far as I know the codec used for a call is negotiated through SDP> messages.>> 1. What happens if the parties do not have the same codec (extreme case)?
> 2. How can I retrieve the used codec through PhApiWrapper for a specific> call? Is there any easy way? Does phApi allow retrieving this info?> 3. Do you have any info (docs, charts, links) on how this negotiation is
> handled in phApi/exosip/osip?>> Thanks>> --> > 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
>>--With best regards,Nguyen-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Re: Memory leaks
yes, I called phTerminate.On 2/24/06, [EMAIL PROTECTED] <[EMAIL PROTECTED] > wrote:Hi Cantemir,Cantemir Mihu wrote:> Hello,>> I'm sending this dirrectly to you, as you are the one developing > phApi. Am I right?>You're right, but please in future post to mailing list and if you wishcc me> This leaks are detected from Visual C++ .NET, with Visual Leak> Detector enabled. This appear when starting my app, then initialize a > line, register succesfull, then close the app.> Is this somewhere my fault? Do I have to call something to release> allocated resources?>Did you call phTerminate?Normally, there will be some unreleased memory allocated from ortp_init and ph_media_initVadim> The code for phApi is taken from OpenWengo NG tree with the latest> revision.>> Thanks in advance.>> WARNING: Visual Leak Detector detected memory leaks! > -- Block 57879 at 0x01B8D7E8: 5 bytes --> Call Stack:> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731):> osip_malloc> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (210): > osip_strdup> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_uri.c (907):> osip_uri_param_clone> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_via.c (475):> osip_via_clone > c:\work\owengo-ng\wifo\exosip\src\jresponse.c (109):> _eXosip_build_response_default> c:\work\owengo-ng\wifo\exosip\src\udp.c (122):> eXosip_send_default_answer> c:\work\owengo-ng\wifo\exosip\src\udp.c (164): send_default_answer > c:\work\owengo-ng\wifo\exosip\src\udp.c (2080):> eXosip_process_newrequest> c:\work\owengo-ng\wifo\exosip\src\udp.c (2294): eXosip_read_message> c:\work\owengo-ng\wifo\exosip\src\exosip.c (398): eXosip_execute > c:\work\owengo-ng\wifo\exosip\src\exosip.c (431): eXosip_thread> f:\vs70builds\3077\vc\crtbld\crt\src\threadex.c (241): _threadstartex> 0x7C80B50B (File and line number not available): GetModuleFileNameA > Data:> 35 30 36 3000> 5060 >> -- Block 57878 at 0x01B8D7A0: 6 bytes --> Call Stack:> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731): > osip_malloc> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (210):> osip_strdup> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_uri.c (905):> osip_uri_param_clone > c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_via.c (475):> osip_via_clone> c:\work\owengo-ng\wifo\exosip\src\jresponse.c (109):> _eXosip_build_response_default> c:\work\owengo-ng\wifo\exosip\src\udp.c (122): > eXosip_send_default_answer> c:\work\owengo-ng\wifo\exosip\src\udp.c (164): send_default_answer> c:\work\owengo-ng\wifo\exosip\src\udp.c (2080):> eXosip_process_newrequest> c:\work\owengo-ng\wifo\exosip\src\udp.c (2294): eXosip_read_message > c:\work\owengo-ng\wifo\exosip\src\exosip.c (398): eXosip_execute> c:\work\owengo-ng\wifo\exosip\src\exosip.c (431): eXosip_thread> f:\vs70builds\3077\vc\crtbld\crt\src\threadex.c (241): _threadstartex > 0x7C80B50B (File and line number not available): GetModuleFileNameA> Data:> 72 70 6F 7274 00> rport... >> -- Block 57877 at 0x01B8D758: 8 bytes -- > Call Stack:> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731):> osip_malloc> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_uri.c (774):> osip_uri_param_init > c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_uri.c (902):> osip_uri_param_clone> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_via.c (475):> osip_via_clone> c:\work\owengo-ng\wifo\exosip\src\jresponse.c (109): > _eXosip_build_response_default> c:\work\owengo-ng\wifo\exosip\src\udp.c (122):> eXosip_send_default_answer> c:\work\owengo-ng\wifo\exosip\src\udp.c (164): send_default_answer> c:\work\owengo-ng\wifo\exosip\src\udp.c (2080): > eXosip_process_newrequest> c:\work\owengo-ng\wifo\exosip\src\udp.c (2294): eXosip_read_message> c:\work\owengo-ng\wifo\exosip\src\exosip.c (398): eXosip_execute> c:\work\owengo-ng\wifo\exosip\src\exosip.c (431): eXosip_thread > f:\vs70builds\3077\vc\crtbld\crt\src\threadex.c (241): _threadstartex> 0x7C80B50B (File and line number not available): GetModuleFileNameA> Data:> A0 D7 B8 01E8 D7 B8 01 > >> -- Block 50730 at 0x01B5B508: 35 bytes --> Call Stack:> c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (731):> osip_malloc > c:\work\owengo-ng\wifo\libosip2\src\osipparser2\osip_port.c (210):> osip_strdup> c:\work\owengo-ng\wifo\phapi\phapi.c (1897): phAddVline2>> D
[Wengophone-devel] Which codec is used?
Hello,As far as I know the codec used for a call is negotiated through SDP messages. 1. What happens if the parties do not have the same codec (extreme case)?2. How can I retrieve the used codec through PhApiWrapper for a specific call? Is there any easy way? Does phApi allow retrieving this info? 3. Do you have any info (docs, charts, links) on how this negotiation is handled in phApi/exosip/osip?Thanks-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: compiling ng
QTDIR="c:\qt\4.1.0"qtincludedir="c:\qt\4.1.0\include"qtlibdir="c:\qt\4.1.0\From the command line of cl I see that the /I parameters are messed up: /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtGuiOn 2/24/06, Julien Gilli < [EMAIL PROTECTED]> wrote:Cantemir Mihu <[EMAIL PROTECTED]> writes: > Hello,i want to compiled a freshly updated working copy of ng tree. I thinkthe > scons does not set the qt include directories right. The command is scons> enable-video=0 enable-http-tunnel=0 qtwengophone Hello,Was QTDIR defined in some way for the command interpreter when you entered thecommand ?Regards,--Julien Gilli___Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Holding / Unholding call
Yes, you are right as usual :-)in PhoneCall.cpp I used this to receive the ResumeOk state: _phoneLine.resumeCall(_callId);
if (_state->getCode() == PhoneCallStateHoldOk::CODE) { _phoneLine.setPhoneCallState(_callId, PhoneCallStateResumeOk::CODE, CString(_T("")));
} //stateChangedEvent(this, _state->getCode());
instead of _phoneLine.resumeCall(_callId); //stateChangedEvent(this, _state->getCode());
On 2/23/06, Vadim Lebedev
<[EMAIL PROTECTED]> wrote:
Cantemir Mihu wrote:
i'm using phApi by using the PhApiWrapper taken from the
ng tree
I noticed another problem with phApi, but I will create a new mail for
that
Cantemir,
It seems to problem specific to phApuWrapper I'm positive that
phapi.dll DOES advertise the
application on RESUMEOK and HOLDOK
Best regards
Vadim
Thanks
On 2/22/06,
Vadim Lebedev <[EMAIL PROTECTED]>
wrote:
Cantemir Mihu wrote:
It seems that the phapi library is not sending any
PhoneCallStateResumeOk state changes. Is this a known problem?
I hold a call, then I resume it, and I receive no state changed event
Cantemir,
Are you calling directly phApi? if so from which tree did you take
it: ng or classic?
Vadim
Thanks for the help
--
Best regards / Mit freundlichen Grüssen
Cantemir Mihu
___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
--
Best regards / Mit freundlichen Grüssen
Cantemir Mihu
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] compiling ng
Hello,i want to compiled a freshly updated working copy of ng tree. I think the scons does not set the qt include directories right. The command is scons enable-video=0 enable-http-tunnel=0 qtwengophone The error is this:cl /nologo /Zm200 /EHsc /GX /GR -Zi /LDd -Gm /DEBUG -D_DEBUG /MDd /W3 -w34100 -w34189 /wd4290 /TP /DPHAPIWRAPPER=1 /DQT_CORE_LIB=1 /DQT_DLL=1 /DQT_GUI_LIB=1 /DQT_LARGEFILE_SUPPORT=1 /DQT_NO_KEYWORDS=1 /DQT_PLUGIN=1 /DQT_THREAD_SUPPORT=1 /DUNICODE=1 /DWIN32=1 /Idebug\wengophone\sr c\presentation\qt\"c:\qt\4.1.0"\include /Iwengophone\src\presentation\qt\"c:\qt\4.1.0"\include /Idebug\wengophone\src /Iwengophone\src /Idebug\libs\util\include /Ilibs\util\include /IC:\Boost\include\boost-1_33_1 /Idebug\libs\openssl\inc32\openssl /Ilibs\openssl\inc32\openssl /Id ebug\libs\openssl\inc32 /Ilibs\openssl\inc32 /Idebug\libs\curl\include /Ilibs\curl\include /Idebug\libs\curl\lib /Ilibs\curl\lib /Idebug\libs\global\include /Ilibs\global\include /Idebug\libs\global\include\msvc /Ilibs\global\include\msvc /Idebug\libs\imwrapper\include /Ilibs\imw rapper\include /Idebug\libs\sipwrapper\include /Ilibs\sipwrapper\include /Idebug\libs\wenbox\include /Ilibs\wenbox\include /Idebug\libs\shlibloader\include /Ilibs\shlibloader\include /Idebug\libs\tinyxml /Ilibs\tinyxml /Idebug\libs\sound\include /Ilibs\sound\include /Idebug\libs\ portaudio\pa_common /Ilibs\portaudio\pa_common /Idebug\wifo\netlib\include /Iwifo\netlib\include /Idebug\wifo\netlib /Iwifo\netlib /Idebug\wifo\httptunnel /Iwifo\httptunnel /Idebug\wengophone\src\"c:\qt\4.1.0"\include /Iwengophone\src\"c:\qt\4.1.0"\include /Idebug\wengophone\src\ "c:\qt\4.1.0"\include\Qt /Iwengophone\src\"c:\qt\4.1.0"\include\Qt /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtCore /Iwengophone\src\"c:\qt\4.1.0"\include\QtCore /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtGui /Iwengophone\src\"c:\qt\4.1.0"\include\QtGui /Idebug\wengophone\ src\"c:\qt\4.1.0"\include\QtNetwork /Iwengophone\src\"c:\qt\4.1.0"\include\QtNetwork /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtDesigner /Iwengophone\src\"c:\qt\4.1.0"\include\QtDesigner /Idebug\wengophone\src\"c:\qt\4.1.0"\include\QtXml /Iwengophone\src\"c:\qt\4.1.0"\include \QtXml /Idebug\wengophone\src\"c:\qt\4.1.0"\include\ActiveQt /Iwengophone\src\"c:\qt\4.1.0"\include\ActiveQt /Idebug\libs\qtutil\"c:\qt\4.1.0"\include /Ilibs\qtutil\"c:\qt\4.1.0"\include /Idebug\libs\qtutil\include /Ilibs\qtutil\include /Idebug\libs\qtutil\"c:\qt\4.1.0"\include / Ilibs\qtutil\"c:\qt\4.1.0"\include /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\Qt /Ilibs\qtutil\"c:\qt\4.1.0"\include\Qt /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\QtCore /Ilibs\qtutil\"c:\qt\4.1.0"\include\QtCore /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\QtGui /Ilibs\qtutil\"c:\qt\ 4.1.0"\include\QtGui /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\QtNetwork /Ilibs\qtutil\"c:\qt\4.1.0"\include\QtNetwork /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\QtDesigner /Ilibs\qtutil\"c:\qt\4.1.0"\include\QtDesigner /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\QtXml /Ilibs\qtutil \"c:\qt\4.1.0"\include\QtXml /Idebug\libs\qtutil\"c:\qt\4.1.0"\include\ActiveQt /Ilibs\qtutil\"c:\qt\4.1.0"\include\ActiveQt /Idebug\libs\webcam\include /Ilibs\webcam\include /Idebug\libs\pixertool\include /Ilibs\pixertool\include /Idebug\libs\ffmpeg /Ilibs\ffmpeg /Idebug\libs\ff mpeg\libavutil /Ilibs\ffmpeg\libavutil /Idebug\libs\ffmpeg\libavcodec /Ilibs\ffmpeg\libavcodec /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include /Iwengophone\src\presentation\qt\"c:\qt\4.1.0"\include /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\Qt /Iwen gophone\src\presentation\qt\"c:\qt\4.1.0"\include\Qt /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtCore /Iwengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtCore /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtGui /Iwengophone\src\presentation\ qt\"c:\qt\4.1.0"\include\QtGui /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtNetwork /Iwengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtNetwork /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtDesigner /Iwengophone\src\presentation\qt\"c:\qt\4 .1.0"\include\QtDesigner /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtXml /Iwengophone\src\presentation\qt\"c:\qt\4.1.0"\include\QtXml /Idebug\wengophone\src\presentation\qt\"c:\qt\4.1.0"\include\ActiveQt /Iwengophone\src\presentation\qt\"c:\qt\4.1.0"\include\Ac tiveQt /Idebug\libs\sipwrapper\src\phapi /Ilibs\sipwrapper\src\phapi /Idebug\wifo\phapi /Iwifo\phapi /Idebug\wifo\eXosip\include /Iwifo\eXosip\include /Idebug\wifo\libosip2\include /Iwifo\libosip2\include /Idebug\wifo\libosip2\include\osipparser2 /Iwifo\libosip2\include\osipparse r2 /Idebug\wifo\libosip2\src\osipparser2 /Iwifo\libosip2\src\osipparser2 /Idebug\wifo\libosip2\src\osip2 /Iwifo\libosip2\src\osip2 /Idebug\wifo\ortp\src /Iwifo\ortp\src /Idebug\wifo\phapi\ilbc /Iwifo\phapi\ilbc /Idebug\wifo\phapi\stun /Iwifo\phapi\stun /Idebug\wifo\phapi\gsm /Iwi f
[Wengophone-devel] phApi used in a queue
Hello,I noticed this behavior: I have created a queue on Asterisk PBX where I am the only one in this queue. If I call this Queue and enable some automatically rejecting calls method, than the Asterisk will keep trying to call me in an endless loop. This is ok with the Asterisk, but the phApi library is sending after some time the following response: 500 Internal Server ErrorAfter this starts, I am not be able to receive any other calls. It seems to remain in this state where it answers everything with Internal Server Error. I traced it down to here: ph_call_new() -> ph_locate_call() -> returns 0;Thanks for any help on this.-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Holding / Unholding call
i'm using phApi by using the PhApiWrapper taken from the ng treeI noticed another problem with phApi, but I will create a new mail for thatThanksOn 2/22/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote: Cantemir Mihu wrote: It seems that the phapi library is not sending any PhoneCallStateResumeOk state changes. Is this a known problem? I hold a call, then I resume it, and I receive no state changed event Cantemir, Are you calling directly phApi? if so from which tree did you take it: ng or classic? Vadim Thanks for the help -- Best regards / Mit freundlichen Grüssen Cantemir Mihu ___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Holding / Unholding call
It seems that the phapi library is not sending any PhoneCallStateResumeOk state changes. Is this a known problem? I hold a call, then I resume it, and I receive no state changed eventThanks for the help -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] phApi voice level low
Hello, it was both parties that where hearing it not loud enough. But the solution of Tanguy solved it:hdxmode was set to 1. Setting it to 0 made it loud enough :-)On 2/13/06, Vadim Lebedev <[EMAIL PROTECTED]> wrote: Cantemir Mihu wrote:> please, any suggestions would be appreciated.>Cantemir,Can you please be more specific? Is it YOU who does not hear loudenough or YOUR correspondentwho does not hear loud enough? Can you try to call 333 and to check if it is loud enough?ThanksVadim> -- Forwarded message --> From: *Cantemir Mihu* < [EMAIL PROTECTED]> [EMAIL PROTECTED]>>> Date: Feb 10, 2006 5:24 PM> Subject: phApi voice level low> To: wengophone-devel@lists.openwengo.com> wengophone-devel@lists.openwengo.com>>> Hello,>> can anyone tell me why the voice level of a call made with phApi very > low is? With other SIP softphones it is not a problem. I'm using> Windows and every volume levels are set to maximum. Where could I> check to see which volume it uses? I saw that ph_media_set_spkvol() > does nothing. Is this work in progress or what?>> --> > Best regards / Mit freundlichen Grüssen> Cantemir Mihu>> --> > 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> -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] phApi voice level low
please, any suggestions would be appreciated.-- Forwarded message --From: Cantemir Mihu <[EMAIL PROTECTED] >Date: Feb 10, 2006 5:24 PMSubject: phApi voice level lowTo: wengophone-devel@lists.openwengo.comHello,can anyone tell me why the voice level of a call made with phApi very low is? With other SIP softphones it is not a problem. I'm using Windows and every volume levels are set to maximum. Where could I check to see which volume it uses? I saw that ph_media_set_spkvol() does nothing. Is this work in progress or what? -- Best regards / Mit freundlichen GrüssenCantemir Mihu -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] phApi voice level low
Hello,can anyone tell me why the voice level of a call made with phApi very low is? With other SIP softphones it is not a problem. I'm using Windows and every volume levels are set to maximum. Where could I check to see which volume it uses? I saw that ph_media_set_spkvol() does nothing. Is this work in progress or what? -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: bug in phapi?
thanks, I did that. PS: When I try to send email to you, I get an error stating your inbox is full :-)On 2/8/06, Julien Gilli < [EMAIL PROTECTED]> wrote:Cantemir Mihu <[EMAIL PROTECTED]> writes: > it was my fault, sorry. I was working on 3992No problem ;-).> (But this is because I checked out from openwengo/trunk which later relocated> to openwengo/wengophone-ne/trunk or something like this. You're right. We'll continue to try to avoid this kind of changes in the future,unless it is necessary (it was in this case).> With tortoiseSVN I> relocated the working copy, but when doing an update I receive the following: >>> REPORT request failed on '/svn/openwengo/!svn/vcc/default'Cannot replace adirectory from within> Don't know what this means, nor how to resolve it.You should checkout NG again. Before doing that, please make sure that the changes you made to your local copy are in a safe place. You can do this bycreating a patch with the svn diff command.Regards,--Julien Gilli___ Wengophone-devel mailing listWengophone-devel@lists.openwengo.comhttp://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Re: bug in phapi?
it was my fault, sorry. I was working on 3992 :-((But this is because I checked out from openwengo/trunk which later relocated to openwengo/wengophone-ne/trunk or something like this. With tortoiseSVN I relocated the working copy, but when doing an update I receive the following: REPORT request failed on '/svn/openwengo/!svn/vcc/default'Cannot replace a directory from within Don't know what this means, nor how to resolve it. But I did a new checkout and I see the changes you mentioned.On 2/8/06, Julien Gilli < [EMAIL PROTECTED]> wrote:Cantemir Mihu <[EMAIL PROTECTED]> writes: > I noticed a strange behavior of calls: when registering to a outside registrarserver, the called party would not start a RTP media stream. So the caller couldnot hear anything. I traced this down to phapi.c > . There, in ph_call_media_start() is this code:if (je)strncpy(msp->remoteaddr, je->remote_sdp_audio_ip, sizeof(msp->remoteaddr));> I changed it to if (je) strncpy(msp->remoteaddr, je->remote_sdp_audio_ip, sizeof(msp->remoteaddr));elsestrncpy(msp->remoteaddr, ca->remote_sdp_audio_ip, sizeof(msp->remoteaddr));Hello,Which revision and which branch of phapi did you use? It seems that the code you mention has been modified the way you describe with changeset 4059,approximatively one week ago.Thank you very much for this report, looking forward to reading you to clarifythis issue.All the best, --Julien Gilli___Wengophone-devel mailing listWengophone-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] bug in phapi?
Hello,I noticed a strange behavior of calls: when registering to a outside registrar server, the called party would not start a RTP media stream. So the caller could not hear anything. I traced this down to phapi.c . There, in ph_call_media_start() is this code: if (je) strncpy(msp->remoteaddr, je->remote_sdp_audio_ip, sizeof(msp->remoteaddr)); I changed it to if (je) strncpy(msp->remoteaddr, je->remote_sdp_audio_ip, sizeof(msp->remoteaddr)); else strncpy(msp->remoteaddr, ca->remote_sdp_audio_ip, sizeof(msp->remoteaddr)); because when accepting a call je is always NULL (see phAcceptCall3() ). And now it works.The same should be set vor the video stream as well I think, but I haven't tested it with video enabled. Can someone explain why this behavior did not occur when using a server in the local LAN?-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] memory leaks in phApi?
I created a new project in visual c++ which uses the phapi.dll in debug mode. I also enabled Visual Leak Detector (http://www.codeproject.com/tools/visualleakdetector.asp ) for the project and this is what resulted after succesfully registering a line. I called phTerminate() before ending the problem, but the leaks remain.On 2/7/06, Julien Gilli <[EMAIL PROTECTED]> wrote: Hello,Cantemir Mihu wrote:> I found some memory leaks when calling phInit() and registering a line.[..snip..]>> -- Block 43341 at 0x01A847E8: 35 bytes --> Call Stack: > c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (731):> osip_malloc> c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (210):> osip_strdup> c:\work\openwengo\wifo\phapi\phapi.c (1885): phAddVline2 Which tools and which settings did you use to generate such messages?They seems to be pretty useful and i'd like to be able to reproduce themso that i can create a detailed ticket to track this issue. Thank you very much for the report.Regards,--Julien GilliOpenWengo, the free and multiplatform VoIP clienthttp://www.openwengo.com/___ Wengophone-devel mailing listWengophone-devel@lists.openwengo.comhttp://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re[2]: [Wengophone-devel] compile classic with qtfree
Here is a little error in one of the steps: Instead: >> >> in gui/MyWidgetFactory.h >> change >> >> #include "HomePageWidgetForm.h" >> #include "search/SearchPageWidgetForm.h" >> >> to >> #include "HomePageWidgetForm_posix.h" >> #include "search/SearchPageWidgetForm_posix.h" you must comment the #include "search/SearchPageWidgetForm.h" line. ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Answer to my previous post
The problem was that I compiled wengophone without video support. But in PhApiWrapper.cpp, this was declared:static const int MEDIA_FLAGS = PH_STREAM_AUDIO | PH_STREAM_VIDEO_RX | PH_STREAM_VIDEO_TX;so the phapi library started media streams for video as well, but did not close them after a call was ended. I think MEDIA_FLAGS should be set based on a wheter enable-video is specified or not. Am I right? -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Problems with phapi and wengophone NG
Hello,after ending a call, the qtwengophone keeps sending RTP data to the other party. After closing the call, 2 phapi threads and 2 wdmaudrv.dll threads remain open and send data to the other host who ended the call. How can I stop this? is there any method that should be called in the closing event of the call? This is very anoying, please help. Do you keep the phapi/exosip library up to date? did you do any modifications to the original exosip library?-- 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
Re: [Wengophone-devel] Openwengo-ng r4109 fails to compile (Linux dapper)
try with:scons enable-netlib=0 qtwengophoneOn 2/2/06, Eugene Edouard <[EMAIL PROTECTED]> wrote: Compile command:QTDIR=/usr QTLIBDIR=/usr/lib/qt4QTINCLUDEDIR=/usr/include/qt4 scons qtwengophone g++ -fno-common -g -Wall -frtti -fexceptions-DENABLE_NETLIB=1 -DPHAPI_DLL=1 -DQT_CORE_LIB=1-DQT_DLL=1 -DQT_GUI_LIB=1 -DQT_NO_KEYWORDS=1-DQT_PLUGIN=1 -DQT_THREAD_SUPPORT=1 -DUNICODE=1-Idebug/libs/util/include -Ilibs/util/include -Idebug/libs/curl/include -Ilibs/curl/include-Idebug/libs/curl/lib -Ilibs/curl/lib-Idebug/libs/global/include -Ilibs/global/include-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include-Idebug/wifo/phapi -Iwifo/phapi -Idebug/wifo/eXosip/include -Iwifo/eXosip/include-Idebug/wifo/libosip2/include -Iwifo/libosip2/include-Idebug/wifo/libosip2/include/osipparser2-Iwifo/libosip2/include/osipparser2-Idebug/wifo/libosip2/src/osipparser2 -Iwifo/libosip2/src/osipparser2-Idebug/wifo/libosip2/src/osip2-Iwifo/libosip2/src/osip2 -Idebug/wifo/ortp/src-Iwifo/ortp/src -Idebug/wifo/phapi/ilbc-Iwifo/phapi/ilbc -Idebug/wifo/phapi/stun-Iwifo/phapi/stun -Idebug/wifo/phapi/gsm -Iwifo/phapi/gsm -Idebug/libs/timer/include-Ilibs/timer/include -Idebug/wifo/httptunnel-Iwifo/httptunnel -Idebug/wifo/netlib/include-Iwifo/netlib/include -Idebug/wifo/netlib-Iwifo/netlib -Idebug/libs/portaudio/pa_common -Ilibs/portaudio/pa_common -Idebug/wengophone/src-Iwengophone/src -Idebug/libs/wenbox/include-Ilibs/wenbox/include -Idebug/libs/shlibloader/include-Ilibs/shlibloader/include -Idebug/libs/tinyxml-Ilibs/tinyxml -Idebug/libs/sound/include -Ilibs/sound/include -I/usr/include/qt4-I/usr/include/qt4/Qt -I/usr/include/qt4/QtCore-I/usr/include/qt4/QtGui -I/usr/include/qt4/QtNetwork-I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtXml-I/usr/mkspecs/linux-g++ -c -o debug/wengophone/src/model/sipwrapper/phapi/PhApiWrapper.owengophone/src/model/sipwrapper/phapi/PhApiWrapper.cppwengophone/src/model/sipwrapper/phapi/PhApiWrapper.cpp:In member function 'voidPhApiWrapper::detectNetworkConfig()': wengophone/src/model/sipwrapper/phapi/PhApiWrapper.cpp:147:error: 'is_udp_port_open' was not declared in thisscopewengophone/src/model/sipwrapper/phapi/PhApiWrapper.cpp:163:error: 'is_tcp_port_open' was not declared in this scopescons: ***[debug/wengophone/src/model/sipwrapper/phapi/PhApiWrapper.o]Error 1scons: building terminated because of errors.any idea ?___ Nouveau : téléphonez moins cher avec Yahoo! Messenger ! Découvez les tarifs exceptionnels pour appeler la France et l'international.Téléchargez sur http://fr.messenger.yahoo.com ___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] memory leaks in phApi?
I found some memory leaks when calling phInit() and registering a line. Is there any phApi function I must call to release this memory? This happened without even making a call. I think if I place a call then there are much more leaks. -- Block 43341 at 0x01A847E8: 35 bytes -- Call Stack: c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (210): osip_strdup c:\work\openwengo\wifo\phapi\phapi.c (1885): phAddVline2 -- Block 43314 at 0x01A84218: 8 bytes -- Call Stack: c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\openwengo\wifo\libosip2\src\osip2\port_thread.c (94): osip_thread_create c:\work\openwengo\wifo\phapi\phapi.c (2806): phInit-- Block 43248 at 0x01A7F580: 8 bytes -- Call Stack: c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_from.c (84): osip_from_init c:\work\openwengo\wifo\exosip\src\exosip.c (3596): eXosip_guess_contact_uri c:\work\openwengo\wifo\phapi\phapi.c (2788): phInit -- Block 43247 at 0x0157A858: 12 bytes -- Call Stack: c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_port.c (731): osip_malloc c:\work\openwengo\wifo\libosip2\src\osipparser2\osip_from.c (78): osip_from_init c:\work\openwengo\wifo\exosip\src\exosip.c (3596): eXosip_guess_contact_uri c:\work\openwengo\wifo\phapi\phapi.c (2788): phInit-- Block 43086 at 0x019CB278: 4 bytes -- Call Stack: c:\work\openwengo\wifo\ortp\src\rtpport.h (212): g_malloc c:\work\openwengo\wifo\ortp\src\rtpport.h (411): g_mutex_new c:\work\openwengo\wifo\ortp\src\str_utils.c (55): mbdb_mutex_init c:\work\openwengo\wifo\ortp\src\ortp.c (86): ortp_init c:\work\openwengo\wifo\phapi\phmedia.c (252): ph_media_init c:\work\openwengo\wifo\phapi\phapi.c (2760): phInit - Block 43085 at 0x01511188: 4 bytes -- Call Stack: c:\work\openwengo\wifo\ortp\src\rtpport.h (212): g_malloc c:\work\openwengo\wifo\ortp\src\rtpport.h (411): g_mutex_new c:\work\openwengo\wifo\ortp\src\str_utils.c (54): mbdb_mutex_init c:\work\openwengo\wifo\ortp\src\ortp.c (86): ortp_init c:\work\openwengo\wifo\phapi\phmedia.c (252): ph_media_init c:\work\openwengo\wifo\phapi\phapi.c (2760): phInit-- 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
Re: [Wengophone-devel] Small bug found?
I do not have a trac account. Please create one for me.10xOn 2/2/06, Julien Gilli <[EMAIL PROTECTED]
> wrote:Hello,Cantemir Mihu wrote:> in phmedia-audio.c, line 876
>> ph_printf("wrong audio payload: %s expecting %d\n", rtp->paytype,> stream->ms.payload);>> should be>> ph_printf("wrong audio payload: %d expecting %d\n", rtp->paytype,
> stream->ms.payload);>If you have a svn checkout, could you please generate a patch using svndiff, then create a ticket for this issue and attach the patch?If you don't have a Trac account yet, please tell me and i will create
one for you.Thank you very much for your help!All the best,--Julien Gilli___Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.comhttp://dev.openwengo.com/mailman/listinfo/wengophone-devel
-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Small bug found?
in phmedia-audio.c, line 876 ph_printf("wrong audio payload: %s expecting %d\n", rtp->paytype, stream->ms.payload);should be ph_printf("wrong audio payload:
%d expecting %d\n", rtp->paytype, stream->ms.payload);
or else I get a big exception :-)-- Best regards / Mit freundlichen GrüssenCantemir Mihu
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Changing SIP port
You could make it configurable, so the user is able to specify a desired port. Also the user agent name should be change-able (instead of phapi/exosip/version it could be wengophone/version). On 2/2/06, Philippe BERNERY <[EMAIL PROTECTED]> wrote: Julien Gilli wrote:> Hello,>> Cantemir Mihu wrote:>>>>> how can I change the UDP port the phone is going to listen for sip>> packets? It defaults to 5060, but I want to change it. >> Do you want to do such a thing to be able to use WengoPhone when another> app is listening on the 5060 UDP port? If so, Philippe and Julien are> working on something so that it is possible out of the box, AFAIK. > Philippe, can you confirm please?Yes we are currently working on network detection process which shouldchange automatically the UDP port if used.--Philippe BERNERY < [EMAIL PROTECTED]>http://dev.openwengo.com___Wengophone-devel mailing list Wengophone-devel@lists.openwengo.comhttp://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Setting local listening port
Hello,I found the answer to my previous email:in PhApiWrapper, before phInit is called, you must set the port like this: phConfig_t *phcfg = phGetConfig(); char port[16]; sprintf(port, "%d", registerPort); strcpy(phcfg->sipport, port);I hope this is usefull for somebody :)-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Changing SIP port
Hello,how can I change the UDP port the phone is going to listen for sip packets? It defaults to 5060, but I want to change it. The same with the RTP ports.Thank you.-- 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
Re: [Wengophone-devel] Compile release mode of NG version
scons-0.96.1On 1/31/06, Julien Gilli <[EMAIL PROTECTED]> wrote: Hello,Cantemir Mihu a écrit :> 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)>> http://pastebin.com/532188Thank you very much for having pasted the console output. It seems thatthe include paths are wrong. Which version of scons do you use?All the best,--Julien Gilli OpenWengo, the free and multiplatform VoIP clienthttp://dev.openwengo.com/___Wengophone-devel mailing list Wengophone-devel@lists.openwengo.comhttp://dev.openwengo.com/mailman/listinfo/wengophone-devel -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ 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
Thank you,but not of any help. I already compiled it successfully in debug mode with this command: scons qtwengophone wengocurl phapi avcodecNow I tried scons mode=release enable-video=0 qtwengophone with no success.On 1/31/06, Klaus Darilion <[EMAIL PROTECTED]> wrote: 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 regardsklaus>> http://pastebin.com/532188>>> On 1/31/06, *Julien Gilli* <[EMAIL PROTECTED] > [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> 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-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ 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
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)http://pastebin.com/532188 On 1/31/06, Julien Gilli <[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 wedon't get into the issue where we link the main executable binary withcurl 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 patienceYou're welcome!--Julien GilliOpenWengo, the free and multiplatform VoIP client http://dev.openwengo.com/___Wengophone-devel mailing listWengophone-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] Compile release mode of NG version
Hello,I'm very new to using Scons. Sorry for the silly question, but how can I compile NG version in release mode?Another question: If i set the option enable-video to 0, then the output will not depend on avcodec.dll ?Yet another question: what is wengocurl.dll? :)Thank you for your patience-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Phone call states
You could use ArgoUML from argouml.tigris.org.I did not use this very much, but it seems pretty good for such kind of jobs. On 1/31/06, Julien Gilli <[EMAIL PROTECTED]> wrote: Hello,Cantemir Mihu a écrit :> Thank you for clarifying this.>> Maybe you should replace the image on the wiki, so others won't use> the bad diagram.We should convert these images to UML or anything-else diagrams, so that we can actually use subversion to track changes.Does anyone know a better free tools than dia?All the best,--Julien GilliOpenWengo, the free and multiplatform VoIP client http://dev.openwengo.com/___Wengophone-devel mailing listWengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Phone call states
Thank you for clarifying this.Maybe you should replace the image on the wiki, so others won't use the bad diagram.On 1/31/06, Tanguy Krotoff < [EMAIL PROTECTED]> wrote:Cantemir Mihu wrote: > again about the different phone states: If I make a call to WP NG, then> I receive following debug messages for a conversation:>> PhoneCall: call state changed state=PCSIncoming> PhoneCall: call state changed state=PCSOk > PhoneCall: call accepted> PhoneCall: call state changed state=PCSClosed>> The PhoneCallStateRinging state does not appear. Why?Just discovered that my diagram is wrongfor an incoming call: PhoneCallStateIncomingPhoneCallStateTalkingfor an outgoing call:PhoneCallStateDialingPhoneCallStateRingingPhoneCallStateTalking(PhoneCallStateTalking was showing PhoneCallStateOk because PhoneCallStateTalking::toString() was returning a wrong string)SIP trace is for an incoming phone call is:- server -> client INVITE sip:client@ //PhoneCallStateIncoming- client -> server 180 Ringing //User clicks on accept call button- client -> server 200 OK- server -> client ACK sip:client@ //PhoneCallStateTalkingSo there is only 2 states (PhoneCallStateInconing &PhoneCallStateTalking) corresponding to the 2 SIP msg (INVITE & ACK) from the server. There is no need for a PhoneCallStateRinging whenreceiving a phone call.> So the right way to accept a call is:> on state incoming: start a ringing sound> the pick up with PhoneCall::accept() > then hang up with PhoneCall:close()>> Is thir right?You don't have to play a ringing sound since there is a ring back tone.So just do accept() and that's all.--Tanguy Krotoff < [EMAIL PROTECTED]>http://dev.openwengo.com-- 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
Re: [Wengophone-devel] Phone call states
Hello,again about the different phone states: If I make a call to WP NG, then I receive following debug messages for a conversation:PhoneCall: call state changed state=PCSIncomingPhoneCall: call state changed state=PCSOk PhoneCall: call acceptedPhoneCall: call state changed state=PCSClosedThe PhoneCallStateRinging state does not appear. Why?So the right way to accept a call is:on state incoming: start a ringing sound the pick up with PhoneCall::accept()then hang up with PhoneCall:close()Is thir right?10xOn 1/31/06, Tanguy Krotoff < [EMAIL PROTECTED]> wrote:Cantemir Mihu wrote:> thank you, very usefull reply. If you need more informations, more diagrams; just ask ;)--Tanguy Krotoff <[EMAIL PROTECTED]>http://dev.openwengo.com -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Phone call states
Hello,are the different PhoneCallStates anywhere described?Whatt is the flow of phone states? Please provide some info about these states.10x-- 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
Re[2]: [Wengophone-devel] German Wikipedia-Article about WengoPhone Classic
" Dieser Artikel wurde zur Löschung vorgeschlagen. Wenn du meinst, dass dieser Artikel nicht gelöscht werden sollte, beteilige dich bitte an der Diskussion auf der im Link unten angegebenen Seite. Über die Löschung wird nach sieben Tagen entschieden. Während dieser Zeit ist es natürlich möglich, den Artikel zu erweitern und zu verbessern. Falls du einer der Autoren des Artikels bist, lies dir bitte vorher Wikipedia:Was bedeutet ein Löschantrag durch und entferne den Löschantrag keinesfalls eigenmächtig." --- This article has been proposed for deletion. If you think that this article should not be deleted, please state your opinion at the discussion found at the link specified at the bottom of this text. The final deletion of this entry will be decided after 7 days. During this time, it is of course possible to extend and to improve the article. If you are one of the authors of this article, please read the article "Wikipedia:Was bedeutet ein Löschantrag" and do not remove the deletion request by yourself. - Hope this translation is helpfull. I'm speaking English and German, but none of them as good as Romanian :) Best regards/Mit freundlichen Grüssen Cantemir Mihu This is my answer to your e-mail: > > Hello, > Patrick Aljord wrote: >>I don't speak German but I think the article is about to be deleted >>http://de.wikipedia.org/wiki/WengoPhone_Classic >> > Could someone translate to english what is said on the top of the page > please? > All the best, ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Error after compiling build version of classic phone
I built it with the free qt3.3.5 library (on WindowsXP) by comenting out all references to qaxwidget and ieactiveX. also removed qaxcontainer reference from SCons files.It compiled succesfully, but when running the application I receive an assertion failed: _BLOCK_TYPE_IS_VALID(pHead->nBlockUse)in file dbgdel.cpp, line 52.Does anybody know what this could be? The console window contains only this: PA :: Input device found: Logitech USB Headset from host API: MME PA :: Input device found: Realtek AC97 Audio from host API: MMEPA :: Input device found: Logitech USB Headset from host API: MMEPA :: Input device found: Realtek AC97 Audio from host API: MME-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Compiling class phone
I found Qt 3.3.5 here: http://sourceforge.net/project/showfiles.php?group_id=49109downloaded it, compiled ok. Then I started compiling the wengo classic phone with: scons softphone-runtime softphoneA error appeared that it could not find qt335.lib. So I renamed qt3.lib (found in c:\qt\qt-3\lib) to qt355.lib. The compile continued but later I got a new error: build-wengo\win32-debug\softphone\gui\uic_HomePageWidgetForm.cc(16) : fatal erro r C1083: Cannot open include file: 'qaxwidget.h': No such file or directoryscons: *** [build-wengo\win32-debug\softphone\gui\uic_HomePageWidgetForm.obj] Er ror 2scons: building terminated because of errors.What am I doing wrong? Please help-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] sip library
Hello all,I wanted to ask for opinion regarding the sip library used: what's your experience with sipXtapi? I saw that u tried to use it, but then u used phapi. Is this correct? What problems did you had with sipXtapi? Thanks,-- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
[Wengophone-devel] Compiling wengophone classic
Hello,I'm trying to compile wengophone classic. I'm using Qt 4.1.0.here is the output:scons: Reading SConscript files ... rev:revunknownscons: done reading SConscript files.scons: Building targets ... cl /nologo /Zm200 /EHsc /GX /GR -Zi /LDd -Gm /DEBUG -D_DEBUG /MDd /W3 /TP /DDEBU G= /DQT_THREAD_SUPPORT= /DWIN32= /Ibuild-wengo\win32-debug\libs\systemperf /Ibuild-wengo\win32-debug\libs\systemperf\include /IC:\Qt\4.1.0\include /IC:\Qt\4.1.0 \include /c build-wengo\win32-debug\softphone\download\Download.cpp /Fobuild-wen go\win32-debug\softphone\download\Download.objDownload.cppc:\work\openwengo-classic\build-wengo\win32-debug\softphone\download\Download.h( 23) : fatal error C1083: Cannot open include file: 'qobject.h': No such file or directoryscons: *** [build-wengo\win32-debug\softphone\download\Download.obj] Error 2 scons: building terminated because of errors.Is this because I'm using Qt 4.1.0 and not 3.3.x as sugested in the wiki?-- 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] Debug mode of WengoPhone NG
Hello,I just finished compiling everything needed by WengoPhone (windows XP), and all seemes to be succesfull. I can start the qtwengophone.exe, I can log in, but it displays an empty grey page, and when I go to Tools->Configuration nothing is there. At the bottom of the window there is a "3" displayed ?? Can you please help? -- Best regards / Mit freundlichen GrüssenCantemir Mihu ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
