From _hamlet at libero.it Mon May 2 15:59:15 2011 From: _hamlet at libero.it (Hamlet) Date: Mon, 2 May 2011 10:59:15 -0500 Subject: [Ekiga-list] Getting rid of the debug messages from the "presence" feature Message-ID: <201105021059.15838._hamlet@libero.it> Hello, I have a number of troubles with Ekiga from different causes (NAT, router, OS, servers, Ekiga itself), so I am using the debug output very often. I am not expert about the SIP protocol, and the output is flooded by many messages (like "SUBSCRIBE", I think) which are sent even when being idle and make hard for me to spot what is relevant and what is not. Is it possible to disable the feature which produces those messages? My guess is that they are sent around to ask which of my contacts are online and available and I think that in principle placing or receiving a call should work even without that. Thank you, -- Hamlet From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 2 21:59:58 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 02 May 2011 23:59:58 +0200 Subject: [Ekiga-list] Getting rid of the debug messages from the "presence" feature In-Reply-To: <201105021059.15838._hamlet@libero.it> References: <201105021059.15838._hamlet@libero.it> Message-ID: <4DBF295E.8010403@pu-pm.univ-fcomte.fr> On 02/05/11 17:59, Hamlet wrote: > Hello, > > I have a number of troubles with Ekiga from different causes (NAT, router, OS, > servers, Ekiga itself), so I am using the debug output very often. > I am not expert about the SIP protocol, and the output is flooded by many > messages (like "SUBSCRIBE", I think) which are sent even when being idle and > make hard for me to spot what is relevant and what is not. > Is it possible to disable the feature which produces those messages? My guess > is that they are sent around to ask which of my contacts are online and > available and I think that in principle placing or receiving a call should > work even without that. You are right: these messages are used only to fill the contact list with the presence (online etc.) There is no possibility in ekiga to turn off these messages. If you wish to remove those messages from debug output, I suggest you to modify http://git.gnome.org/browse/ekiga/plain/src/ekiga-debug-analyser so that it removes unwanted messages. Cheers, -- Eugen Dedu http://eugen.dedu.free.fr From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 3 13:41:14 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 03 May 2011 15:41:14 +0200 Subject: [Ekiga-list] Unable to Register SIP Server In-Reply-To: <609082.4248.qm@web33507.mail.mud.yahoo.com> References: <609082.4248.qm@web33507.mail.mud.yahoo.com> Message-ID: <4DC005FA.6000204@pu-pm.univ-fcomte.fr> On 09/04/11 10:04, Chin-Wen Lin wrote: > Hi, > > I am using the version 3.2.7 (ekiga-3.2.7-3.fc13.x86_64) > and trying to connect to the SIP server (Asterisk). > The server port is NOT 5060. > > Wireshare shows that the packet of SUBSCRIBE SIP Request use port 5060. > Is it a bug ? > Or any other setting I should change in addition to Registrar: > "great.sip.server:port_number"? Sorry to answer so late. The subscribe messages have nothing to do with registration. I suppose the subscribe message go with ekiga.net:5060, not with your SIP server, that's why they use port 5060. If you put :portNumber in Registrar, then the registration should work. If not, please send the debug output (-d 4). -- Eugen Dedu http://eugen.dedu.free.fr From davekoelmeyer at me.com Thu May 5 13:28:14 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Fri, 06 May 2011 01:28:14 +1200 Subject: [Ekiga-list] Question about call monitoring section on the Wiki Message-ID: <4DC2A5EE.7000101@me.com> Hi All, I've updated the following section of the Wiki: http://wiki.ekiga.org/index.php/Documentation#Monitor_a_call I have a few questions which need confirmation by the experts. 1) Are the bandwidth units for audio and video in KB/s or Kb/s? 2) There is an existing description for a parameter which apparently doesn't exist in the network traffic statistics pop-up window (which I've added a screengrab for), that is, "Round trip delay": "Round-trip delay: The required time for a packet to arrive at its destination and come back. You can see the round-trip delay during a call as a connection quality indicator together with the Lost and Late packets statistics. " Can this be removed, or is the round-trip delay reading to be found somewhere else in the interface, or was it present in an earlier version of Ekiga? 3) There is no description for the "Out of order packets" parameter which *is* visible in the network traffic statistics pop-up window. Could someone please give me a brief summary of what this is? Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ From Eugen.Dedu at pu-pm.univ-fcomte.fr Thu May 5 15:22:22 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Thu, 05 May 2011 17:22:22 +0200 Subject: [Ekiga-list] Question about call monitoring section on the Wiki In-Reply-To: <4DC2A5EE.7000101@me.com> References: <4DC2A5EE.7000101@me.com> Message-ID: <4DC2C0AE.5070202@pu-pm.univ-fcomte.fr> On 05/05/11 15:28, Dave Koelmeyer wrote: > Hi All, > > I've updated the following section of the Wiki: > > http://wiki.ekiga.org/index.php/Documentation#Monitor_a_call Good! > I have a few questions which need confirmation by the experts. > > 1) Are the bandwidth units for audio and video in KB/s or Kb/s? It's kB/s (kilobytes per sec). > 2) There is an existing description for a parameter which apparently > doesn't exist in the network traffic statistics pop-up window (which > I've added a screengrab for), that is, "Round trip delay": > > "Round-trip delay: The required time for a packet to arrive at its > destination and come back. You can see the round-trip delay during a > call as a connection quality indicator together with the Lost and Late > packets statistics. " > > Can this be removed, or is the round-trip delay reading to be found > somewhere else in the interface, or was it present in an earlier version > of Ekiga? Good question! Moreover, I commonly use RTT (Round Trip Time) instead of RTD (Round-trip delay time), I propose to change to RTT. Looking at the code, I know that the signal bar with 4 vertical bars is a graphic representation of the jitter (when there is no loss, no late packet, no out of order, highest means jitter < 50ms, lowest means jitter > 200 ms; otherwise 1 or 0 bars are shown). But about RTT I have no idea. Julien, do you know if it was used in the past? I looked at opal code and I do not see such information. > 3) There is no description for the "Out of order packets" parameter > which *is* visible in the network traffic statistics pop-up window. > Could someone please give me a brief summary of what this is? Out of order packet means that it is sent (after/)before another packet, but it arrives (before/)after the other packet. I suppose that what is inside parenthesis should be removed. It is difficult for me to find out in opal code (rtp.cxx, variable packetsOutOfOrder) what precisely it corresponds to. In ekiga, the percentage shown is the number of out of order audio and video packets divided by the total number of audio and video packets. Do not forget to remove pages you have integrated in Documentation/Manual, such as the section http://wiki.ekiga.org/index.php/Managing_Calls#Understanding_the_statistics. Thank you! -- Eugen From davekoelmeyer at me.com Fri May 6 13:44:39 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Sat, 07 May 2011 01:44:39 +1200 Subject: [Ekiga-list] Logitech Webcam C510 added to HCL Message-ID: <4DC3FB47.70709@me.com> A helpful community member has tested this on Windows, and I've added it to: http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Optional.29 Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Mon May 9 11:10:01 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Mon, 09 May 2011 23:10:01 +1200 Subject: [Ekiga-list] Level of H323 support in Ekiga / hardware video conferencing systems Message-ID: <4DC7CB89.1020002@me.com> Hi, How mature is the H323 support in Ekiga? I have access to a range of professional hardware H323 video conferencing systems (Polycom, Sony) which I may be able to perform limited testing on to gauge compatibility with Ekiga, but only if there is interest or support in gathering data for implementing any fixes needed. The more I read about Skype/GoogleTalk/Facebook etc., the more I think the ability for a desktop client like Ekiga to connect to expensive hardware systems is a very attractive feature. I'm also keen to expand the Wiki hardware compatibility with some hardware systems too. Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 9 12:29:47 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 09 May 2011 14:29:47 +0200 Subject: [Ekiga-list] Level of H323 support in Ekiga / hardware video conferencing systems In-Reply-To: <4DC7CB89.1020002@me.com> References: <4DC7CB89.1020002@me.com> Message-ID: <4DC7DE3B.4030201@pu-pm.univ-fcomte.fr> On 09/05/11 13:10, Dave Koelmeyer wrote: > Hi, > > How mature is the H323 support in Ekiga? I have access to a range of > professional hardware H323 video conferencing systems (Polycom, Sony) > which I may be able to perform limited testing on to gauge compatibility > with Ekiga, but only if there is interest or support in gathering data > for implementing any fixes needed. > > The more I read about Skype/GoogleTalk/Facebook etc., the more I think > the ability for a desktop client like Ekiga to connect to expensive > hardware systems is a very attractive feature. > > I'm also keen to expand the Wiki hardware compatibility with some > hardware systems too. Hi Dave, To my knowledge, H323 support is ok, but, looking at the bug tracker (https://bugzilla.gnome.org/buglist.cgi?quicksearch=product%3A%22ekiga%22+h323), there are some bugs which affect probably many people and prevent ekiga to be useful for them. Ptlib/opal developers say that H323 support is as good as SIP's. I do not use H323, I do not know it, I cannot test it (at least easily). Therefore, I can commit fixes only if a patch is given to me. Eugen From gastomaster at yahoo.com Fri May 6 19:39:20 2011 From: gastomaster at yahoo.com (Gabriel Hasbun) Date: Fri, 6 May 2011 20:39:20 +0100 (BST) Subject: [Ekiga-list] Not working at all. Message-ID: <507563.65058.qm@web24709.mail.ird.yahoo.com> "Could not connect to remote host" "Could not register sip:gasto at ekiga.net" When trying to make test call. What can I do? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 10 18:45:13 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 10 May 2011 20:45:13 +0200 Subject: [Ekiga-list] Not working at all. In-Reply-To: <507563.65058.qm@web24709.mail.ird.yahoo.com> References: <507563.65058.qm@web24709.mail.ird.yahoo.com> Message-ID: <4DC987B9.30400@pu-pm.univ-fcomte.fr> On 06/05/11 21:39, Gabriel Hasbun wrote: > "Could not connect to remote host" > > "Could not register sip:gasto at ekiga.net" When trying to make test call. What can I do? Indeed. Only the debug output (-d 4) can tell the precise error, if you send it to us or analyse it yourself. -- Eugen Dedu http://eugen.dedu.free.fr From halbtaxabo-njacobs at yahoo.com Thu May 12 13:21:26 2011 From: halbtaxabo-njacobs at yahoo.com (Nicholas Jacobs) Date: Thu, 12 May 2011 06:21:26 -0700 (PDT) Subject: [Ekiga-list] Error on Ekiga Interoperability page Message-ID: <620365.28709.qm@web65513.mail.ac4.yahoo.com> The Ekiga Interoperability page: http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F in the Mac OS section, lists X-Lite 3.2. However, as far as I can tell, only X-Lite 4.0 is available for Mac OS, here: http://download.cnet.com/X-Lite/3000-2349_4-44320.html If X-Lite 3.2 is compatible and X-Lite 4.0 is not, then X-Lite 4.0 should be mentioned in the "Which programs don't work with Ekiga?" section. Otherwise, mention of X-Lite 3.2 should just be replaced by X-Lite 4.0. Either way the page needs to be updated. (I can't check this myself because I don't have a Mac; I'm looking for something to recommend to a family member who does.) From papillion at gmail.com Thu May 12 20:36:23 2011 From: papillion at gmail.com (Anthony Papillion) Date: Thu, 12 May 2011 15:36:23 -0500 Subject: [Ekiga-list] Ekiga continually disconnects from SIPGate Message-ID: Hi Everyone, I'm hoping someone can help me because I'm experiencing a super frustrating problem that I need to solve involving a SIPGate DID and Ekiga. For some reason, even though Ekiga is showing that SIPGate is registered, SIPGate itself (in the control panel) constantly goes on and off line. Regardless of the status SIPGate has my phone at though, calls are simply not delivered. I had one come through but that was it. Since I have a router, I've done all the port forwarding and SIPGate is able to see me as online (sometimes) but other times it just isn't there. Can anyone help? I have AT&T residential ADSL service with a Linksys WRT54G wireless router. Thanks! Anthony From davekoelmeyer at me.com Thu May 12 21:39:05 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Fri, 13 May 2011 09:39:05 +1200 Subject: [Ekiga-list] Error on Ekiga Interoperability page In-Reply-To: <620365.28709.qm@web65513.mail.ac4.yahoo.com> References: <620365.28709.qm@web65513.mail.ac4.yahoo.com> Message-ID: <4DCC5379.7060307@me.com> On 13/05/11 01:21 AM, Nicholas Jacobs wrote: > The Ekiga Interoperability page: > http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F > in the Mac OS section, lists X-Lite 3.2. > However, as far as I can tell, only X-Lite 4.0 is available for Mac OS, here: > http://download.cnet.com/X-Lite/3000-2349_4-44320.html > > If X-Lite 3.2 is compatible and X-Lite 4.0 is not, then X-Lite 4.0 should be > mentioned in the "Which programs don't work with Ekiga?" section. > Otherwise, mention of X-Lite 3.2 should just be replaced by X-Lite 4.0. > Either way the page needs to be updated. > > (I can't check this myself because I don't have a Mac; I'm looking for > something to recommend to a family member who does.) > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Hi Nicholas, Thanks - I'll check that out and update the page soon as I can. Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Fri May 13 03:35:42 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Fri, 13 May 2011 03:35:42 +0000 (GMT) Subject: [Ekiga-list] Skype-ing out an open source future Message-ID: <1ca8e667-2507-4307-f79e-a4fcd9c1e21a@me.com> Ekiga gets a mention in this recent article: http://www.h-online.com/open/features/Skype-ing-out-an-open-source-future-1241617.html They also make some comments about Jitsi interoperability with Ekiga.net which are of some interest.? Cheers, Dave Koelmeyer -------------- next part -------------- An HTML attachment was scrubbed... URL: From b.gatessucks at gmail.com Thu May 12 08:27:01 2011 From: b.gatessucks at gmail.com (B.Gates-sucks) Date: Thu, 12 May 2011 09:27:01 +0100 Subject: [Ekiga-list] Could not register sip Message-ID: Hi, I just installed Ekiga 3.2.7 on Windows 7 64 bit and I get the message above. It works fine on my home machine running Fedora. Thanks. -Francesco -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- ../common/dyna.cxx(134) DYNA Error loading libavcodec ../common/dyna.cxx(134) DYNA Error loading C\libavcodec ../common/dyna.cxx(134) DYNA Error loading .\libavcodec ../common/dyna.cxx(134) DYNA Error loading /usr/local/lib\libavcodec ../common/dyna.cxx(134) DYNA Error loading avcodec-51 ../common/dyna.cxx(134) DYNA Error loading C\avcodec-51 ../common/dyna.cxx(134) DYNA Error loading .\avcodec-51 ../common/dyna.cxx(134) DYNA Error loading /usr/local/lib\avcodec-51 ../common/dyna.cxx(139) DYNA Successfully loaded 'avcodec-52' ../common/dyna.cxx(139) DYNA Successfully loaded 'avutil-50' ../common/dyna.cxx(390) H263+ DYNA Successfully loaded libavcodec library and verified functions h263-1998.cxx(2101) H.263 Codec Enabled with 4 definitions ../common/dyna.cxx(134) DYNA Error loading libavcodec ../common/dyna.cxx(134) DYNA Error loading C\libavcodec ../common/dyna.cxx(134) DYNA Error loading .\libavcodec ../common/dyna.cxx(134) DYNA Error loading /usr/local/lib\libavcodec ../common/dyna.cxx(134) DYNA Error loading avcodec-51 ../common/dyna.cxx(134) DYNA Error loading C\avcodec-51 ../common/dyna.cxx(134) DYNA Error loading .\avcodec-51 ../common/dyna.cxx(134) DYNA Error loading /usr/local/lib\avcodec-51 ../common/dyna.cxx(139) DYNA Successfully loaded 'avcodec-52' ../common/dyna.cxx(139) DYNA Successfully loaded 'avutil-50' ../common/dyna.cxx(390) H264 DYNA Successfully loaded libavcodec library and verified functions h264pipe_win32.cxx(294) H264 IPC PP: Found GPL process executable in .\plugins\h264_video_pwplugin_helper.exe h264pipe_win32.cxx(324) H264 IPC PP: Successfully created child process 7800 h264pipe_win32.cxx(104) H264 IPC PP: Successfully established communication with child process h264-x264.cxx(853) H264 Codec Enabled ../common/dyna.cxx(134) DYNA Error loading libavcodec ../common/dyna.cxx(134) DYNA Error loading C\libavcodec ../common/dyna.cxx(134) DYNA Error loading .\libavcodec ../common/dyna.cxx(134) DYNA Error loading /usr/local/lib\libavcodec ../common/dyna.cxx(134) DYNA Error loading avcodec-51 ../common/dyna.cxx(134) DYNA Error loading C\avcodec-51 ../common/dyna.cxx(134) DYNA Error loading .\avcodec-51 ../common/dyna.cxx(134) DYNA Error loading /usr/local/lib\avcodec-51 ../common/dyna.cxx(139) DYNA Successfully loaded 'avcodec-52' ../common/dyna.cxx(139) DYNA Successfully loaded 'avutil-50' ../common/dyna.cxx(390) MPEG4 DYNA Successfully loaded libavcodec library and verified functions mpeg4.cxx(1993) MPEG4 Codec Enabled 2011/05/12 09:19:38.717 0:00.210 ekiga Version 3.2.7 by on Windows 7 (v6.1.7601-i586 (Model=26 Stepping=5)) with PTLib (v2.6.7) at 2011/5/12 9:19:38.717 2011/05/12 09:19:38.717 0:00.210 ekiga Ekiga git revision: unknown 2011/05/12 09:19:38.719 0:00.212 ekiga PVidDirectShow PVideoInputDevice_DirectShow: constructor 2011/05/12 09:19:38.719 0:00.212 ekiga PVidDirectShow Enumerating Device Names 2011/05/12 09:19:38.730 0:00.223 ekiga PVidDirectShow PVideoInputDevice_DirectShow: destructor 2011/05/12 09:19:38.732 0:00.225 ekiga OpalMan Created manager. 2011/05/12 09:19:38.733 0:00.226 ekiga PVidDirectShow PVideoInputDevice_DirectShow: constructor 2011/05/12 09:19:38.733 0:00.226 ekiga PVidDirectShow Enumerating Device Names 2011/05/12 09:19:38.739 0:00.232 ekiga PVidDirectShow PVideoInputDevice_DirectShow: destructor 2011/05/12 09:19:38.741 0:00.234 ekiga OpalMan Attached endpoint with prefix pc 2011/05/12 09:19:38.741 0:00.234 ekiga OpalEP Created endpoint: pc 2011/05/12 09:19:38.762 0:00.255 ekiga PCSS Created PC sound system endpoint. Players: Default EKIGA *.wav Speakers (3- Logitech USB Heads Recorders: Default Microphone (Webcam 600) Microphone (3- Logitech USB Hea EKIGA *.wav 2011/05/12 09:19:38.765 0:00.258 ekiga OPAL SetMediaFormatOrder() 2011/05/12 09:19:38.765 0:00.258 ekiga OPAL SetMediaFormatMask() 2011/05/12 09:19:38.766 0:00.259 ekiga OpalMan Attached endpoint with prefix sip 2011/05/12 09:19:38.766 0:00.259 ekiga OpalEP Created endpoint: sip 2011/05/12 09:19:38.769 0:00.262 ekiga IfaceMon Initial interface list: 10.136.56.80 (Broadcom NetXtreme 57xx Gigabit Controller) 127.0.0.1 (Software Loopback Interface 1) 2011/05/12 09:19:38.769 0:00.262 ekiga SIP Created endpoint. 2011/05/12 09:19:38.769 0:00.263 Network In...nitor:4420 IfaceMon Started interface monitor thread. 2011/05/12 09:19:38.771 0:00.264 ekiga MonSock Created socket bundle for all interfaces. 2011/05/12 09:19:38.847 0:00.340 ekiga MonSock Created bundled UDP socket 10.136.56.80:5060 2011/05/12 09:19:38.847 0:00.340 ekiga OpalMan Added route "sip:.*=pc:*" 2011/05/12 09:19:38.847 0:00.340 Opal Listener:7888 Listen Started listening thread on udp$*:5060 2011/05/12 09:19:38.847 0:00.340 ekiga OpalMan Added route "pc:.*=sip:" 2011/05/12 09:19:38.847 0:00.340 ekiga OpalMan Attached endpoint with prefix h323 2011/05/12 09:19:38.848 0:00.340 ekiga OpalEP Created endpoint: h323 2011/05/12 09:19:38.848 0:00.341 ekiga OpalMan Attached endpoint with prefix h323s 2011/05/12 09:19:38.848 0:00.341 ekiga H323 Created endpoint. 2011/05/12 09:19:38.849 0:00.342 ekiga OpalMan Added route "h323:.*=pc:" 2011/05/12 09:19:38.849 0:00.342 Opal Listener:7224 Listen Started listening thread on tcp$*:1720 2011/05/12 09:19:38.849 0:00.342 Opal Listener:7224 Listen Waiting on socket accept on tcp$*:1720 2011/05/12 09:19:38.849 0:00.342 ekiga OpalMan Added route "pc:.*=h323:" 2011/05/12 09:19:38.933 0:00.426 ekiga SIP Changing SUBSCRIBE handler from Unavailable to Subscribing, target=sip:500 at ekiga.net, id=d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:38.933 0:00.426 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.933 0:00.426 ekiga SIP No SRV record found. 2011/05/12 09:19:38.936 0:00.429 ekiga OpalUDP Binding to interface: 0.0.0.0:5060 2011/05/12 09:19:38.936 0:00.429 ekiga SIP Created transport udp$86.64.162.35:5060 2011/05/12 09:19:38.937 0:00.430 ekiga OpalUDP Started connect to 86.64.162.35:5060 2011/05/12 09:19:38.937 0:00.430 ekiga OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:19:38.940 0:00.433 ekiga OpalMan Listener interfaces: associated transport=None udp$10.136.56.80:5060 2011/05/12 09:19:38.941 0:00.434 ekiga SIP Transaction created. 2011/05/12 09:19:38.943 0:00.436 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.943 0:00.436 ekiga SIP No SRV record found. 2011/05/12 09:19:38.943 0:00.436 ekiga SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:19:38.944 0:00.437 ekiga SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:38.945 0:00.438 ekiga OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:38.945 0:00.438 ekiga SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:19:38.945 0:00.438 ekiga SIP Changing SUBSCRIBE handler from Unavailable to Subscribing, target=sip:500 at ekiga.net, id=84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:38.945 0:00.438 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.946 0:00.439 ekiga SIP No SRV record found. 2011/05/12 09:19:38.946 0:00.439 ekiga OpalUDP Binding to interface: 0.0.0.0:5060 2011/05/12 09:19:38.946 0:00.439 ekiga SIP Created transport udp$86.64.162.35:5060 2011/05/12 09:19:38.946 0:00.439 ekiga OpalUDP Started connect to 86.64.162.35:5060 2011/05/12 09:19:38.946 0:00.439 ekiga OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:19:38.949 0:00.442 ekiga OpalMan Listener interfaces: associated transport=None udp$10.136.56.80:5060 2011/05/12 09:19:38.951 0:00.444 ekiga SIP Transaction created. 2011/05/12 09:19:38.953 0:00.446 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.953 0:00.446 ekiga SIP No SRV record found. 2011/05/12 09:19:38.953 0:00.446 ekiga SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:19:38.953 0:00.446 ekiga SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:38.954 0:00.447 ekiga OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:38.954 0:00.447 ekiga SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:19:38.954 0:00.447 ekiga SIP Changing SUBSCRIBE handler from Unavailable to Subscribing, target=sip:501 at ekiga.net, id=0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:38.955 0:00.448 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.955 0:00.448 ekiga SIP No SRV record found. 2011/05/12 09:19:38.955 0:00.448 ekiga OpalUDP Binding to interface: 0.0.0.0:5060 2011/05/12 09:19:38.955 0:00.448 ekiga SIP Created transport udp$86.64.162.35:5060 2011/05/12 09:19:38.955 0:00.448 ekiga OpalUDP Started connect to 86.64.162.35:5060 2011/05/12 09:19:38.955 0:00.448 ekiga OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:19:38.958 0:00.451 ekiga OpalMan Listener interfaces: associated transport=None udp$10.136.56.80:5060 2011/05/12 09:19:38.960 0:00.453 ekiga SIP Transaction created. 2011/05/12 09:19:38.962 0:00.455 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.962 0:00.455 ekiga SIP No SRV record found. 2011/05/12 09:19:38.962 0:00.455 ekiga SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:19:38.962 0:00.455 ekiga SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:38.962 0:00.455 ekiga OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:38.963 0:00.456 ekiga SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:19:38.963 0:00.456 ekiga SIP Changing SUBSCRIBE handler from Unavailable to Subscribing, target=sip:501 at ekiga.net, id=8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:38.963 0:00.456 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.963 0:00.456 ekiga SIP No SRV record found. 2011/05/12 09:19:38.963 0:00.456 ekiga OpalUDP Binding to interface: 0.0.0.0:5060 2011/05/12 09:19:38.963 0:00.456 ekiga SIP Created transport udp$86.64.162.35:5060 2011/05/12 09:19:38.964 0:00.457 ekiga OpalUDP Started connect to 86.64.162.35:5060 2011/05/12 09:19:38.964 0:00.457 ekiga OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:19:38.967 0:00.460 ekiga OpalMan Listener interfaces: associated transport=None udp$10.136.56.80:5060 2011/05/12 09:19:38.969 0:00.462 ekiga SIP Transaction created. 2011/05/12 09:19:38.971 0:00.464 ekiga DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:38.971 0:00.464 ekiga SIP No SRV record found. 2011/05/12 09:19:38.971 0:00.464 ekiga SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:19:38.972 0:00.465 ekiga SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:38.972 0:00.465 ekiga OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:38.972 0:00.465 ekiga SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:19:39.080 0:00.573 ekiga Ekiga version 3.2.7 2011/05/12 09:19:39.080 0:00.573 ekiga OPAL version 3.6.8 2011/05/12 09:19:39.080 0:00.573 ekiga PTLIB version 2.6.7 2011/05/12 09:19:39.080 0:00.573 ekiga GNOME support disabled 2011/05/12 09:19:39.080 0:00.573 ekiga Accelerated rendering support enabled 2011/05/12 09:19:39.080 0:00.573 ekiga DBUS support disabled 2011/05/12 09:19:39.080 0:00.573 ekiga GConf support disabled 2011/05/12 09:19:39.080 0:00.573 ekiga ESound support disabled 2011/05/12 09:19:39.272 0:00.765 ekiga MediaFormat Removing codecs SpeexIETFWide-20.6k,SpeexWB,SpeexWide-20.6k,G.711-uLaw-64k,G.711-ALaw-64k,H.264,theora,H.261,H.261-CIF,H.261-QCIF,H.263,H.263P,MPEG4 2011/05/12 09:19:39.272 0:00.765 ekiga OPAL SetMediaFormatMask(PCM-16-48kHz,CELT-48K,PCM-16-32kHz,CELT-32K,PCM-16-16kHz,G.722-64k,PCM-16,G.726-16k,G.726-24k,G.726-32k,G.726-40k,GSM-06.10,GSM-AMR,LPC-10,MS-GSM,MS-IMA-ADPCM,SpeexIETFNarrow-11k,SpeexIETFNarrow-15k,SpeexIETFNarrow-18.2k,SpeexIETFNarrow-24.6k,SpeexIETFNarrow-5.95k,SpeexIETFNarrow-8k,SpeexNB,SpeexWNarrow-8k,iLBC,iLBC-13k3,iLBC-15k2,YUV420P,RFC4175_YCbCr-4:2:0,RGB32,RGB24,RFC4175_RGB,SIP-IM,T.140,H.224/H323AnnexQ,H.224/HDLCTunneling,Linear-16-Stereo-48kHz) 2011/05/12 09:19:39.272 0:00.765 ekiga OPAL SetMediaFormatOrder(SpeexIETFWide-20.6k,SpeexWB,SpeexWide-20.6k,G.711-uLaw-64k,G.711-ALaw-64k,H.264,theora,H.261,H.261-CIF,H.261-QCIF,H.263,H.263P,MPEG4) 2011/05/12 09:19:39.285 0:00.778 ekiga MediaFormat Removing codecs SpeexIETFWide-20.6k,SpeexWB,SpeexWide-20.6k,G.711-uLaw-64k,G.711-ALaw-64k,H.264,theora,H.261,H.261-CIF,H.261-QCIF,H.263,H.263P,MPEG4 2011/05/12 09:19:39.286 0:00.779 ekiga OPAL SetMediaFormatMask(PCM-16-48kHz,CELT-48K,PCM-16-32kHz,CELT-32K,PCM-16-16kHz,G.722-64k,PCM-16,G.726-16k,G.726-24k,G.726-32k,G.726-40k,GSM-06.10,GSM-AMR,LPC-10,MS-GSM,MS-IMA-ADPCM,SpeexIETFNarrow-11k,SpeexIETFNarrow-15k,SpeexIETFNarrow-18.2k,SpeexIETFNarrow-24.6k,SpeexIETFNarrow-5.95k,SpeexIETFNarrow-8k,SpeexNB,SpeexWNarrow-8k,iLBC,iLBC-13k3,iLBC-15k2,YUV420P,RFC4175_YCbCr-4:2:0,RGB32,RGB24,RFC4175_RGB,SIP-IM,T.140,H.224/H323AnnexQ,H.224/HDLCTunneling,Linear-16-Stereo-48kHz) 2011/05/12 09:19:39.286 0:00.779 ekiga OPAL SetMediaFormatOrder(SpeexIETFWide-20.6k,SpeexWB,SpeexWide-20.6k,G.711-uLaw-64k,G.711-ALaw-64k,H.264,theora,H.261,H.261-CIF,H.261-QCIF,H.263,H.263P,MPEG4) 2011/05/12 09:19:39.299 0:00.792 ekiga VidInputCoreConfBridge Updating preview size and fps 2011/05/12 09:19:39.299 0:00.792 ekiga VidInputCore Setting new preview config: 320x240/30 2011/05/12 09:19:39.303 0:00.796 ekiga VidInputCoreConfBridge Updating preview size and fps 2011/05/12 09:19:39.303 0:00.796 ekiga VidInputCore Setting new preview config: 320x240/30 2011/05/12 09:19:39.310 0:00.803 ekiga VideoOutputCoreConfBridge Updating video view 2011/05/12 09:19:39.310 0:00.803 ekiga VideoOutputCoreConfBridge Updating zoom 2011/05/12 09:19:39.310 0:00.803 ekiga VideoOutputCoreConfBridge Updating Video Settings 2011/05/12 09:19:39.310 0:00.803 ekiga VideoOutputCoreConfBridge Updating Video Settings 2011/05/12 09:19:39.310 0:00.803 ekiga VideoOutputCoreConfBridge Updating Video Settings 2011/05/12 09:19:39.310 0:00.803 ekiga VideoOutputCoreConfBridge Updating Video Settings 2011/05/12 09:19:39.310 0:00.803 ekiga VidInputCoreConfBridge Updating preview size and fps 2011/05/12 09:19:39.310 0:00.803 ekiga VidInputCore Setting new preview config: 320x240/30 2011/05/12 09:19:39.314 0:00.807 ekiga VidInputCoreConfBridge Updating preview size and fps 2011/05/12 09:19:39.314 0:00.807 ekiga VidInputCore Setting new preview config: 320x240/30 2011/05/12 09:19:39.318 0:00.811 ekiga VidInputCoreConfBridge Updating device 2011/05/12 09:19:39.318 0:00.811 ekiga VidInputCore Setting device: Logitech Webcam 600 (PTLIB/DirectShow) 2011/05/12 09:19:39.318 0:00.811 ekiga GMVideoInputManager_ptlib Setting Device Logitech Webcam 600 (PTLIB/DirectShow) 2011/05/12 09:19:39.318 0:00.811 ekiga VidInputCoreConfBridge Updating device 2011/05/12 09:19:39.318 0:00.811 ekiga VidInputCore Setting device: Logitech Webcam 600 (PTLIB/DirectShow) 2011/05/12 09:19:39.318 0:00.811 ekiga GMVideoInputManager_ptlib Setting Device Logitech Webcam 600 (PTLIB/DirectShow) 2011/05/12 09:19:39.318 0:00.812 ekiga VidInputCoreConfBridge Updating device 2011/05/12 09:19:39.318 0:00.812 ekiga VidInputCore Setting device: Logitech Webcam 600 (PTLIB/DirectShow) 2011/05/12 09:19:39.319 0:00.812 ekiga GMVideoInputManager_ptlib Setting Device Logitech Webcam 600 (PTLIB/DirectShow) 2011/05/12 09:19:39.319 0:00.812 ekiga VidInputCoreConfBridge Updating image 2011/05/12 09:19:39.319 0:00.812 ekiga VidInputCoreConfBridge Updating preview 2011/05/12 09:19:39.319 0:00.812 ekiga VidInputCore Stopping Preview 2011/05/12 09:19:39.319 0:00.812 ekiga AudioOutputCoreConfBridge Updating device 2011/05/12 09:19:39.319 0:00.812 ekiga AudioOutputCore Setting device[0]: Default (PTLIB/WindowsMultimedia) 2011/05/12 09:19:39.319 0:00.812 ekiga GMAudioOutputManager_ptlib Setting Device[0] Default (PTLIB/WindowsMultimedia) 2011/05/12 09:19:39.319 0:00.812 ekiga AudioOutputCoreConfBridge Updating device 2011/05/12 09:19:39.319 0:00.812 ekiga AudioOutputCore Setting device[1]: Default (PTLIB/WindowsMultimedia) 2011/05/12 09:19:39.319 0:00.812 ekiga AudioInputCoreConfBridge Updating device 2011/05/12 09:19:39.319 0:00.812 ekiga AudioInputCore Setting device: Default (PTLIB/WindowsMultimedia) 2011/05/12 09:19:39.319 0:00.812 ekiga GMAudioInputManager_ptlib Setting Device Default (PTLIB/WindowsMultimedia) 2011/05/12 09:19:39.445 0:00.938 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:19:39.445 0:00.938 PTLib Housekeeper:7360 SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:39.446 0:00.939 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:39.455 0:00.948 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:19:39.455 0:00.948 PTLib Housekeeper:7360 SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:39.456 0:00.949 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:39.465 0:00.958 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:19:39.465 0:00.958 PTLib Housekeeper:7360 SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:39.466 0:00.959 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:39.473 0:00.966 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:19:39.473 0:00.966 PTLib Housekeeper:7360 SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:39.474 0:00.967 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:40.446 0:01.939 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:19:40.446 0:01.939 PTLib Housekeeper:7360 SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:40.447 0:01.940 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:40.456 0:01.949 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:19:40.456 0:01.949 PTLib Housekeeper:7360 SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:40.457 0:01.950 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:40.466 0:01.959 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:19:40.466 0:01.959 PTLib Housekeeper:7360 SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:40.467 0:01.960 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:40.474 0:01.967 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:19:40.474 0:01.967 PTLib Housekeeper:7360 SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:40.475 0:01.968 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:41.715 0:03.209 StunDetector:7864 STUN No response to STUN server 216.93.246.14:3478 2011/05/12 09:19:41.715 0:03.209 StunDetector:7864 OPAL STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 2011/05/12 09:19:41.716 0:03.209 PTLib Housekeeper:7360 PTLib Thread ended: name="StunDetector:7864", kernel=0.0us, user=0.0us, elapsed=2.406s (<0.1%) 2011/05/12 09:19:42.027 0:03.521 subscriber:7720 SIP Start REGISTER aor=s.ballmersucks at ekiga.net registrar=ekiga.net contact= authID=s.ballmersucks realm= expire=3600 restore=30 minRetry=0.000 maxRetry=0.000 2011/05/12 09:19:42.028 0:03.522 subscriber:7720 SIP Changing REGISTER handler from Unavailable to Subscribing, target=sip:s.ballmersucks at ekiga.net, id=d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:42.028 0:03.522 subscriber:7720 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:42.028 0:03.522 subscriber:7720 SIP No SRV record found. 2011/05/12 09:19:42.029 0:03.522 subscriber:7720 OpalUDP Binding to interface: 0.0.0.0:5060 2011/05/12 09:19:42.029 0:03.522 subscriber:7720 SIP Created transport udp$86.64.162.35:5060 2011/05/12 09:19:42.030 0:03.523 subscriber:7720 OpalUDP Started connect to 86.64.162.35:5060 2011/05/12 09:19:42.030 0:03.523 subscriber:7720 OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:19:42.446 0:03.939 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:19:42.446 0:03.940 PTLib Housekeeper:7360 SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:42.447 0:03.941 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:42.457 0:03.950 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:19:42.457 0:03.951 PTLib Housekeeper:7360 SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:42.458 0:03.951 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:42.467 0:03.960 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:19:42.467 0:03.961 PTLib Housekeeper:7360 SIP Sending PDU (579 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:42.468 0:03.961 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:42.475 0:03.968 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:19:42.475 0:03.969 PTLib Housekeeper:7360 SIP Sending PDU (580 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: "francescosiano" ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:42.476 0:03.970 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:44.431 0:05.925 subscriber:7720 STUN STUN server 216.93.246.14:3478 unexpectedly went offline. 2011/05/12 09:19:44.438 0:05.932 subscriber:7720 OpalMan Listener interfaces: associated transport=udp$10.136.56.80:5060 udp$10.136.56.80:5060 2011/05/12 09:19:44.439 0:05.933 subscriber:7720 SIP Transaction created. 2011/05/12 09:19:44.440 0:05.934 subscriber:7720 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:19:44.441 0:05.935 subscriber:7720 SIP No SRV record found. 2011/05/12 09:19:44.441 0:05.935 subscriber:7720 SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:19:44.441 0:05.935 subscriber:7720 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:44.441 0:05.936 subscriber:7720 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:44.442 0:05.936 subscriber:7720 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:19:44.442 0:05.936 PTLib Housekeeper:7360 PTLib Thread ended: name="subscriber:7720", kernel=0.0us, user=0.0us, elapsed=2.415s (<0.1%) 2011/05/12 09:19:44.942 0:06.436 PTLib Housekeeper:7360 SIP REGISTER transaction id=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:19:44.942 0:06.436 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:44.943 0:06.437 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:44.945 0:06.439 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9 2011/05/12 09:19:44.945 0:06.439 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Subscribing to Unavailable, target=sip:500 at ekiga.net, id=d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:44.945 0:06.439 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:19:44.953 0:06.447 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9 2011/05/12 09:19:44.953 0:06.447 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Subscribing to Unavailable, target=sip:500 at ekiga.net, id=84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:44.953 0:06.447 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:19:44.962 0:06.456 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9 2011/05/12 09:19:44.962 0:06.456 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Subscribing to Unavailable, target=sip:501 at ekiga.net, id=0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:44.962 0:06.456 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:19:44.971 0:06.465 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9 2011/05/12 09:19:44.971 0:06.465 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Subscribing to Unavailable, target=sip:501 at ekiga.net, id=8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:44.971 0:06.465 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:19:45.733 0:07.227 Opal Garbage:1548 SIP Transaction id=z9hG4bK4000a8b9-2404-1910-818a-b8ac6f2d04a9 destroyed. 2011/05/12 09:19:45.733 0:07.227 Opal Garbage:1548 SIP Transaction id=z9hG4bK4807a8b9-2404-1910-818c-b8ac6f2d04a9 destroyed. 2011/05/12 09:19:45.733 0:07.227 Opal Garbage:1548 SIP Transaction id=z9hG4bK58fca7b9-2404-1910-8189-b8ac6f2d04a9 destroyed. 2011/05/12 09:19:45.733 0:07.228 Opal Garbage:1548 SIP Transaction id=z9hG4bKc403a8b9-2404-1910-818b-b8ac6f2d04a9 destroyed. 2011/05/12 09:19:45.942 0:07.436 PTLib Housekeeper:7360 SIP REGISTER transaction id=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:19:45.942 0:07.436 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:45.943 0:07.437 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:47.942 0:09.436 PTLib Housekeeper:7360 SIP REGISTER transaction id=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:19:47.942 0:09.437 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:19:47.943 0:09.438 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:19:50.441 0:11.936 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for REGISTER transaction id=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9 2011/05/12 09:19:50.441 0:11.936 PTLib Housekeeper:7360 SIP Changing REGISTER handler from Subscribing to Unavailable, target=sip:s.ballmersucks at ekiga.net, id=d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:19:50.441 0:11.936 PTLib Housekeeper:7360 SIP Retrying REGISTER in 30 seconds. 2011/05/12 09:19:50.734 0:12.229 Opal Garbage:1548 SIP Transaction id=z9hG4bK0060b0b9-2404-1910-818d-b8ac6f2d04a9 destroyed. 2011/05/12 09:20:04.754 0:26.252 ekiga PTLib Thread ended: name="AudioEventScheduler:5488", kernel=0.0us, user=0.0us, elapsed=1831724745392s 2011/05/12 09:20:04.754 0:26.252 ekiga PTLib Thread ended: name="PreviewManager", kernel=0.0us, user=0.0us, elapsed=1831724745392s 2011/05/12 09:20:04.755 0:26.252 ekiga PTLib Thread ended: name="GMVideoOutputManager:3880", kernel=0.0us, user=0.0us, elapsed=1831724745392s 2011/05/12 09:20:04.755 0:26.252 ekiga PTLib Thread ended: name="VideoPreviewManager:708", kernel=0.0us, user=0.0us, elapsed=1831724745392s 2011/05/12 09:20:14.204 0:35.703 PTLib Housekeeper:7360 SIP Starting SUBSCRIBE for offline retry 2011/05/12 09:20:14.204 0:35.703 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Unavailable to Restoring, target=sip:501 at ekiga.net, id=8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:14.204 0:35.703 PTLib Housekeeper:7360 OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:20:14.204 0:35.704 PTLib Housekeeper:7360 SIP Transaction created. 2011/05/12 09:20:14.209 0:35.708 PTLib Housekeeper:7360 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:20:14.209 0:35.709 PTLib Housekeeper:7360 SIP No SRV record found. 2011/05/12 09:20:14.209 0:35.709 PTLib Housekeeper:7360 SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:20:14.209 0:35.709 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:14.210 0:35.710 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:14.210 0:35.710 PTLib Housekeeper:7360 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:20:14.710 0:36.209 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:20:14.710 0:36.210 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:14.711 0:36.211 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:14.933 0:36.432 PTLib Housekeeper:7360 SIP Starting SUBSCRIBE for offline retry 2011/05/12 09:20:14.933 0:36.432 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Unavailable to Restoring, target=sip:500 at ekiga.net, id=d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:14.933 0:36.433 PTLib Housekeeper:7360 OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:20:14.933 0:36.433 PTLib Housekeeper:7360 SIP Transaction created. 2011/05/12 09:20:14.937 0:36.436 PTLib Housekeeper:7360 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:20:14.937 0:36.437 PTLib Housekeeper:7360 SIP No SRV record found. 2011/05/12 09:20:14.937 0:36.437 PTLib Housekeeper:7360 SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:20:14.937 0:36.437 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:14.938 0:36.438 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:14.938 0:36.438 PTLib Housekeeper:7360 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:20:14.944 0:36.443 PTLib Housekeeper:7360 SIP Starting SUBSCRIBE for offline retry 2011/05/12 09:20:14.944 0:36.443 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Unavailable to Restoring, target=sip:500 at ekiga.net, id=84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:14.944 0:36.443 PTLib Housekeeper:7360 OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:20:14.944 0:36.443 PTLib Housekeeper:7360 SIP Transaction created. 2011/05/12 09:20:14.947 0:36.447 PTLib Housekeeper:7360 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:20:14.948 0:36.447 PTLib Housekeeper:7360 SIP No SRV record found. 2011/05/12 09:20:14.948 0:36.447 PTLib Housekeeper:7360 SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:20:14.948 0:36.448 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:14.950 0:36.449 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:14.950 0:36.450 PTLib Housekeeper:7360 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:20:14.954 0:36.453 PTLib Housekeeper:7360 SIP Starting SUBSCRIBE for offline retry 2011/05/12 09:20:14.954 0:36.453 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Unavailable to Restoring, target=sip:501 at ekiga.net, id=0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:14.954 0:36.453 PTLib Housekeeper:7360 OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:20:14.954 0:36.453 PTLib Housekeeper:7360 SIP Transaction created. 2011/05/12 09:20:14.958 0:36.458 PTLib Housekeeper:7360 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:20:14.959 0:36.458 PTLib Housekeeper:7360 SIP No SRV record found. 2011/05/12 09:20:14.959 0:36.458 PTLib Housekeeper:7360 SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:20:14.959 0:36.459 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:14.961 0:36.460 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:14.961 0:36.460 PTLib Housekeeper:7360 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:20:15.440 0:36.939 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:20:15.440 0:36.940 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:15.441 0:36.941 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:15.445 0:36.944 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:20:15.445 0:36.945 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:15.446 0:36.945 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:15.455 0:36.954 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:20:15.455 0:36.955 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:15.456 0:36.955 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:15.711 0:37.211 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:20:15.711 0:37.211 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:15.712 0:37.212 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:16.441 0:37.941 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:20:16.441 0:37.941 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:16.442 0:37.942 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:16.445 0:37.945 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:20:16.445 0:37.945 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:16.446 0:37.946 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:16.455 0:37.955 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:20:16.455 0:37.955 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:16.456 0:37.956 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:17.710 0:39.210 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:20:17.710 0:39.210 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:17.711 0:39.211 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:18.442 0:39.942 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:20:18.442 0:39.942 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:18.443 0:39.943 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:18.446 0:39.946 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:20:18.446 0:39.946 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:18.447 0:39.947 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:18.456 0:39.956 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:20:18.456 0:39.956 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:18.457 0:39.957 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:20.143 0:41.643 PTLib Housekeeper:7360 SIP Starting REGISTER for offline retry 2011/05/12 09:20:20.143 0:41.643 PTLib Housekeeper:7360 SIP Changing REGISTER handler from Unavailable to Restoring, target=sip:s.ballmersucks at ekiga.net, id=d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:20.143 0:41.644 PTLib Housekeeper:7360 OpalUDP Writing to interface 0 - "10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller" 2011/05/12 09:20:22.545 0:44.046 PTLib Housekeeper:7360 STUN STUN server 216.93.246.14:3478 unexpectedly went offline. 2011/05/12 09:20:22.552 0:44.053 PTLib Housekeeper:7360 OpalMan Listener interfaces: associated transport=udp$10.136.56.80:5060 udp$10.136.56.80:5060 2011/05/12 09:20:22.553 0:44.054 PTLib Housekeeper:7360 SIP Transaction created. 2011/05/12 09:20:22.555 0:44.056 PTLib Housekeeper:7360 DNS SRV Lookup ekiga.net service _sip._udp 2011/05/12 09:20:22.555 0:44.056 PTLib Housekeeper:7360 SIP No SRV record found. 2011/05/12 09:20:22.555 0:44.056 PTLib Housekeeper:7360 SIP Transaction remote address is udp$ekiga.net:5060 2011/05/12 09:20:22.555 0:44.056 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:22.556 0:44.057 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:22.556 0:44.057 PTLib Housekeeper:7360 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/12 09:20:22.616 0:44.117 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 4, timeout 4.000 2011/05/12 09:20:22.616 0:44.117 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=e406a8b9-2404-1910-818c-b8ac6f2d04a9 Call-ID: 8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:22.617 0:44.118 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:22.617 0:44.118 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9 2011/05/12 09:20:22.617 0:44.118 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Restoring to Unavailable, target=sip:501 at ekiga.net, id=8c04a8b9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:22.617 0:44.118 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:20:22.617 0:44.118 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 4, timeout 4.000 2011/05/12 09:20:22.617 0:44.118 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=f4fba7b9-2404-1910-8189-b8ac6f2d04a9 Call-ID: d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:22.618 0:44.119 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:22.618 0:44.119 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9 2011/05/12 09:20:22.618 0:44.119 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Restoring to Unavailable, target=sip:500 at ekiga.net, id=d4f8a7b9-2404-1910-8189-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:22.618 0:44.119 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:20:22.618 0:44.119 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 4, timeout 4.000 2011/05/12 09:20:22.618 0:44.119 PTLib Housekeeper:7360 SIP Sending PDU (560 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:500 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=dcffa7b9-2404-1910-818a-b8ac6f2d04a9 Call-ID: 84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/dialog-info+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: dialog;sla;ma Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:22.619 0:44.120 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:22.619 0:44.120 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9 2011/05/12 09:20:22.619 0:44.120 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Restoring to Unavailable, target=sip:500 at ekiga.net, id=84fda7b9-2404-1910-818a-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:22.619 0:44.120 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:20:22.619 0:44.120 PTLib Housekeeper:7360 SIP SUBSCRIBE transaction id=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 4, timeout 4.000 2011/05/12 09:20:22.619 0:44.120 PTLib Housekeeper:7360 SIP Sending PDU (559 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller SUBSCRIBE sip:501 at ekiga.net SIP/2.0 CSeq: 3 SUBSCRIBE Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=6003a8b9-2404-1910-818b-b8ac6f2d04a9 Call-ID: 0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 To: Contact: Accept: application/pidf+xml Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 300 Event: presence Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:22.620 0:44.121 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:22.620 0:44.121 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for SUBSCRIBE transaction id=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9 2011/05/12 09:20:22.620 0:44.121 PTLib Housekeeper:7360 SIP Changing SUBSCRIBE handler from Restoring to Unavailable, target=sip:501 at ekiga.net, id=0801a8b9-2404-1910-818b-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:22.620 0:44.121 PTLib Housekeeper:7360 SIP Retrying SUBSCRIBE in 30 seconds. 2011/05/12 09:20:22.620 0:44.121 PTLib Housekeeper:7360 SIP REGISTER transaction id=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 1, timeout 1.000 2011/05/12 09:20:22.620 0:44.121 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:22.621 0:44.122 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:22.734 0:44.235 Opal Garbage:1548 SIP Transaction id=z9hG4bK04ecdeb9-2404-1910-818d-b8ac6f2d04a9 destroyed. 2011/05/12 09:20:22.734 0:44.235 Opal Garbage:1548 SIP Transaction id=z9hG4bK1ce8deb9-2404-1910-818d-b8ac6f2d04a9 destroyed. 2011/05/12 09:20:22.734 0:44.235 Opal Garbage:1548 SIP Transaction id=z9hG4bKecefdeb9-2404-1910-818d-b8ac6f2d04a9 destroyed. 2011/05/12 09:20:22.734 0:44.235 Opal Garbage:1548 SIP Transaction id=z9hG4bKbccbddb9-2404-1910-818d-b8ac6f2d04a9 destroyed. 2011/05/12 09:20:23.616 0:45.117 PTLib Housekeeper:7360 SIP REGISTER transaction id=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 2, timeout 2.000 2011/05/12 09:20:23.616 0:45.117 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:23.617 0:45.118 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:25.616 0:47.117 PTLib Housekeeper:7360 SIP REGISTER transaction id=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9 timeout, making retry 3, timeout 4.000 2011/05/12 09:20:25.616 0:47.118 PTLib Housekeeper:7360 SIP Sending PDU (522 bytes) to: rem=udp$86.64.162.35:5060,local=udp$10.136.56.80:5060,if=10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 10.136.56.80:5060;branch=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9;rport User-Agent: Ekiga/3.2.7 From: ;tag=d0b1acb9-2404-1910-818d-b8ac6f2d04a9 Call-ID: d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 To: Contact: ;q=1 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 2011/05/12 09:20:25.617 0:47.118 PTLib Housekeeper:7360 OpalUDP Setting interface to 10.136.56.80%Broadcom NetXtreme 57xx Gigabit Controller 2011/05/12 09:20:26.143 0:47.644 PTLib Housekeeper:7360 SIP Set state Terminated_Timeout for REGISTER transaction id=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9 2011/05/12 09:20:26.143 0:47.645 PTLib Housekeeper:7360 SIP Changing REGISTER handler from Restoring to Unavailable, target=sip:s.ballmersucks at ekiga.net, id=d0b1acb9-2404-1910-818c-b8ac6f2d04a9 at nbukdsk150 2011/05/12 09:20:26.143 0:47.645 PTLib Housekeeper:7360 SIP Retrying REGISTER in 30 seconds. 2011/05/12 09:20:26.734 0:48.236 Opal Garbage:1548 SIP Transaction id=z9hG4bK4888eab9-2404-1910-818d-b8ac6f2d04a9 destroyed. From orschiro at googlemail.com Fri May 13 05:09:09 2011 From: orschiro at googlemail.com (orschiro at googlemail.com) Date: Fri, 13 May 2011 07:09:09 +0200 Subject: [Ekiga-list] Ekiga continually disconnects from SIPGate In-Reply-To: References: Message-ID: Open gconf-editor, navigate to apps->ekiga->general->nat and disable stun. Regards Robert 2011/5/12 Anthony Papillion : > Hi Everyone, > > I'm hoping someone can help me because I'm experiencing a super > frustrating problem that I need to solve involving a SIPGate DID and > Ekiga. > > For some reason, even though Ekiga is showing that SIPGate is > registered, SIPGate itself (in the control panel) constantly goes on > and off line. Regardless of the status SIPGate has my phone at though, > calls are simply not delivered. I had one come through but that was > it. > > Since I have a router, I've done all the port forwarding and SIPGate > is able to see me as online (sometimes) but other times it just isn't > there. > > Can anyone help? > I have AT&T residential ADSL service with a Linksys WRT54G wireless router. > > Thanks! > Anthony > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From oskiiiiii at riseup.net Fri May 13 08:40:46 2011 From: oskiiiiii at riseup.net (Oskiiiiii) Date: Fri, 13 May 2011 10:40:46 +0200 Subject: [Ekiga-list] Error on Ekiga Interoperability page In-Reply-To: <4DCC5379.7060307@me.com> References: <620365.28709.qm@web65513.mail.ac4.yahoo.com> <4DCC5379.7060307@me.com> Message-ID: <4DCCEE8E.1070807@riseup.net> Hi, I have a (I supose) well-known problem with Ekiga. The documentation says that you can start a private conference room by calling 501xxxx at ekiga.net, and then it says something about establishing a pin number to give to the other people wanting to join the conference. It seems that there is no way to set up this number. Ekiga does not ask for it ???? I supose there is a known problem, because I have search a lot, and I have find several post in several forums regarding to this issue, but I never found an answer ???? neither in forum nor in ekiga documentation. That very strange, as far as the post I found are relatively old. Why nobody has answered this in any forum? It seems like "The mistery of ekiga private rooms". Thanks a lot, sorry if there is a trivial answer to this, but I have spent a lot of time searching for a solution before posting. Regards -- ----------------------------------------------------------------------------- /"Si Eva hubiera escrito el G?nesis, ?c?mo ser?a la primera noche de amor del g?nero humano? Eva hubiera empezado por aclarar que ella no naci? de ninguna costilla, ni conoci? a ninguna serpiente, ni ofreci? manzanas a nadie, y que Dios nunca le dijo que parir?s con dolor y tu marido te dominar?. Que todas esas historias son puras mentiras que Ad?n cont? a la prensa"/ * Eduardo Galeano* ----------------------------------------------------------------------------- No estoy en Facebook, ni me interesa Facebook. No publico, por tanto, nada en Facebook. Sin embargo, no soy due?o de mi intimidad por culpa de Facebook. Ocurre que cuando publicas algo en Facebook, tu acuerdo con este implica que eres propietario intelectual del contenido, y que les cedes los derechos automaticamente. As? que no puedo controlar mi intimidad, porque t? puedes subir una foto m?a, en la que salga yo, o contenidos de mi propiedad a Facebook. Si ma?ana una foto en la que yo aparezca o un contenido de mi propiedad que tu hayas subido, es publicado en televisi?n, internet, prensa, etc., yo no puedo demandar a Facebook, porque adquiri? de ti los derechos de publicarlo. Si te podr?a demandar a t? por ceder derechos que no son tuyos, pero nunca lo har?a, porque si lees esto es que te tengo alg?n aprecio. En virtud a ese aprecio, y en la esperanza de que sea mutuo, te pido que no me publiques, etiquetes, ni me hagas part?cipe de ningun contenido que publiques en Facebook o cualquier otra red social comercial. Si?ntete libre, en cambio, de usar esto como firma de correo. Si quieres darte de baja en Facebook, de manera definitiva: /http://www.darsedebaja.net/de/facebook/ From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri May 13 09:29:19 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 13 May 2011 11:29:19 +0200 Subject: [Ekiga-list] Could not register sip In-Reply-To: References: Message-ID: <4DCCF9EF.6040402@pu-pm.univ-fcomte.fr> On 12/05/11 10:27, B.Gates-sucks wrote: > Hi, I just installed Ekiga 3.2.7 on Windows 7 64 bit and I get the message > above. > It works fine on my home machine running Fedora. You have some connectivity issues (firewall or Windows blocking your packets), could you check? 2011/05/12 09:19:41.715 0:03.209 StunDetector:7864 STUN No response to STUN server 216.93.246.14:3478 2011/05/12 09:19:41.715 0:03.209 StunDetector:7864 OPAL STUN server "stun.ekiga.net" replies Blocked, external IP 127.0.0.1 Probably http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga (and http://wiki.ekiga.org/index.php/Enable_port_forwarding_manually) are of interest. -- Eugen Dedu http://eugen.dedu.free.fr From herman at aeronetworks.ca Fri May 13 15:09:19 2011 From: herman at aeronetworks.ca (herman) Date: Fri, 13 May 2011 08:09:19 -0700 Subject: [Ekiga-list] Fedora 15: illegal instruction, core dumped Message-ID: <4DCD499F.6080003@aeronetworks.ca> Hi guys, Does anyone have Ekiga working on Fedora 15? Cheers, Herman From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri May 13 15:22:27 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 13 May 2011 17:22:27 +0200 Subject: [Ekiga-list] Fedora 15: illegal instruction, core dumped In-Reply-To: <4DCD499F.6080003@aeronetworks.ca> References: <4DCD499F.6080003@aeronetworks.ca> Message-ID: <4DCD4CB3.3070405@pu-pm.univ-fcomte.fr> On 13/05/11 17:09, herman wrote: > > Hi guys, > > Does anyone have Ekiga working on Fedora 15? Strange... Could you give us the backtrace? -- Eugen From herman at aeronetworks.ca Fri May 13 16:38:05 2011 From: herman at aeronetworks.ca (herman) Date: Fri, 13 May 2011 09:38:05 -0700 Subject: [Ekiga-list] Fedora 15: illegal instruction, core dumped References: <4DCD499F.6080003@aeronetworks.ca> <4DCD4CB3.3070405@pu-pm.univ-fcomte.fr> Message-ID: <4DCD5E6D.6050806@aeronetworks.ca> On 05/13/2011 07:22 PM, Eugen Dedu wrote: > > On 13/05/11 17:09, herman wrote: >> >> Hi guys, >> >> Does anyone have Ekiga working on Fedora 15? > > Strange... Could you give us the backtrace? > First I tried the regular version, then I tried the testing version, then I tried to compile it from source: So, I tried an update from the testing repos: # yum remove ekiga # yum install ekiga --enablerepo=updates-testing Then I ran it with: $ ekiga -d 4 Much patience is required, since it takes a heckavalongtime to start up, testing the NAT firewall and connection to ekiga.net It eventually comes, up, turns grey immediately and, wait for it, drum roll... Illegal instruction (core dumped) Bleh... So, I'm back to trying to figure out how to compile and install it from source. ---------- Post added at 03:30 PM ---------- Previous post was at 01:13 PM ---------- Sooooooooooo.... $ tar -zxvf ptlib-2.6.7.tar.gz $ tar -zxvf opal-3.6.8.tar.gz $ tar -zxvf ekiga-3.2.7.tar.gz $ cd pt[tab] $ make clean $ ./configure --prefix=/usr $ make $ su # make install # exit Rinse and repeat... ...and: /usr/include/ffmpeg/libavutil/common.h:165:47: error: 'UINT64_C' was not declared in this scope make[2]: *** [obj/h263-1998.o] Error 1 --- Now I installed the regular version again, and ran it with -d 4: [herman at leo ~]$ ekiga -d 1 2011/05/13 20:25:17.743 0:01.869 Version 3.2.7 by on Unix Linux (2.6.35.6-45.fc14.i686-i686) with PTLib (v2.6.7) at 2011/5/13 20:25:17.742 2011/05/13 20:25:17.759 0:01.884 Ekiga git revision: unknown 2011/05/13 20:25:18.684 0:02.809 HalManager_dbusPopulating full interface list failed - Method "getDevices" with signature "" on interface "org.freedesktop.NetworkManager" doesn't exist 2011/05/13 20:25:18.685 0:02.811 Detecting V4L2 devices 2011/05/13 20:30:10.754 4:54.879 VidinputCore Tried to set malformed device 2011/05/13 20:30:10.756 4:54.881 VidinputCore Tried to set malformed device 2011/05/13 20:30:10.756 4:54.882 VidinputCore Tried to set malformed device 2011/05/13 20:30:10.759 4:54.884 AudioOutputCoreTried to set malformed device 2011/05/13 20:30:10.760 4:54.885 AudioOutputCoreTried to set malformed device 2011/05/13 20:30:10.775 4:54.900 AudioInputCore Tried to set malformed device 2011/05/13 20:30:11.531 4:55.657 Ekiga version 3.2.7 2011/05/13 20:30:11.531 4:55.657 OPAL version 3.6.8 2011/05/13 20:30:11.531 4:55.657 PTLIB version 2.6.7 2011/05/13 20:30:11.532 4:55.657 GNOME support disabled 2011/05/13 20:30:11.532 4:55.657 Accelerated rendering support enabled 2011/05/13 20:30:11.532 4:55.657 DBUS support enabled 2011/05/13 20:30:11.532 4:55.658 GConf support enabled 2011/05/13 20:30:11.532 4:55.658 ESound support disabled 2011/05/13 20:30:13.198 4:57.323 Opal Liste...0xb69beb70 Listen UDP read error. 2011/05/13 20:30:27.613 5:11.739 Housekeeper:0xb69ffb70 SIP Attempt to write PDU to closed transport udp$86.64.162.35:5060 2011/05/13 20:30:44.165 5:28.290 Housekeeper:0xb69ffb70 SIP Attempt to write PDU to closed transport udp$86.64.162.35:5060 2011/05/13 20:31:00.556 5:44.682 Housekeeper:0xb69ffb70 SIP Attempt to write PDU to closed transport udp$86.64.162.35:5060 2011/05/13 20:31:00.567 5:44.692 Housekeeper:0xb69ffb70 SIP Attempt to write PDU to closed transport udp$86.64.162.35:5060 2011/05/13 20:31:00.569 5:44.695 Housekeeper:0xb69ffb70 SIP Attempt to write PDU to closed transport udp$86.64.162.35:5060 Segmentation fault (core dumped) -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Fri May 13 16:53:04 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Fri, 13 May 2011 18:53:04 +0200 Subject: [Ekiga-list] Fedora 15: illegal instruction, core dumped In-Reply-To: <4DCD5E6D.6050806@aeronetworks.ca> References: <4DCD499F.6080003@aeronetworks.ca> <4DCD4CB3.3070405@pu-pm.univ-fcomte.fr> <4DCD5E6D.6050806@aeronetworks.ca> Message-ID: <4DCD61F0.6040107@pu-pm.univ-fcomte.fr> On 13/05/11 18:38, herman wrote: > On 05/13/2011 07:22 PM, Eugen Dedu wrote: >> >> On 13/05/11 17:09, herman wrote: >>> >>> Hi guys, >>> >>> Does anyone have Ekiga working on Fedora 15? >> >> Strange... Could you give us the backtrace? >> > > First I tried the regular version, then I tried the testing version, > then I tried to compile it from source: > > So, I tried an update from the testing repos: > # yum remove ekiga > # yum install ekiga --enablerepo=updates-testing > > Then I ran it with: > $ ekiga -d 4 > > Much patience is required, since it takes a heckavalongtime to start up, > testing the NAT firewall and connection to ekiga.net The long wait for starting up is surely because of your DNS. There is a patch, but it works only on development version of ekiga... > It eventually comes, up, turns grey immediately and, wait for it, drum > roll... > Illegal instruction (core dumped) > > Bleh... > > So, I'm back to trying to figure out how to compile and install it from > source. > > ---------- Post added at 03:30 PM ---------- Previous post was at 01:13 > PM ---------- > > Sooooooooooo.... > $ tar -zxvf ptlib-2.6.7.tar.gz > $ tar -zxvf opal-3.6.8.tar.gz > $ tar -zxvf ekiga-3.2.7.tar.gz > > $ cd pt[tab] > $ make clean > $ ./configure --prefix=/usr > $ make > $ su > # make install > # exit > > Rinse and repeat... > > ...and: > /usr/include/ffmpeg/libavutil/common.h:165:47: error: 'UINT64_C' was not > declared in this scope > make[2]: *** [obj/h263-1998.o] Error 1 There are some problems with such non-free codecs. Until they get fixed, I propose you to just remove plugins/video/H.263-1998 from opal. > --- > Now I installed the regular version again, and ran it with -d 4: > [herman at leo ~]$ ekiga -d 1 [...] > write PDU to closed transport > udp$86.64.162.35:5060 > Segmentation fault (core dumped) Please use it inside gdb, as shown at http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze Thanks! Eugen From herman at aeronetworks.ca Fri May 13 17:56:40 2011 From: herman at aeronetworks.ca (herman) Date: Fri, 13 May 2011 10:56:40 -0700 Subject: [Ekiga-list] Fedora 15: illegal instruction, core dumped References: <4DCD499F.6080003@aeronetworks.ca> <4DCD4CB3.3070405@pu-pm.univ-fcomte.fr> <4DCD5E6D.6050806@aeronetworks.ca> <4DCD61F0.6040107@pu-pm.univ-fcomte.fr> Message-ID: <4DCD70D8.3060106@aeronetworks.ca> On 05/13/2011 08:53 PM, Eugen Dedu wrote: > > On 13/05/11 18:38, herman wrote: >> On 05/13/2011 07:22 PM, Eugen Dedu wrote: >>> >>> On 13/05/11 17:09, herman wrote: >>>> >>>> Hi guys, >>>> >>>> Does anyone have Ekiga working on Fedora 15? >>> >>> Strange... Could you give us the backtrace? >>> >> >> First I tried the regular version, then I tried the testing version, >> then I tried to compile it from source: >> >> So, I tried an update from the testing repos: >> # yum remove ekiga >> # yum install ekiga --enablerepo=updates-testing >> >> Then I ran it with: >> $ ekiga -d 4 >> >> Much patience is required, since it takes a heckavalongtime to start up, >> testing the NAT firewall and connection to ekiga.net > > The long wait for starting up is surely because of your DNS. There is > a patch, but it works only on development version of ekiga... > >> It eventually comes, up, turns grey immediately and, wait for it, drum >> roll... >> Illegal instruction (core dumped) >> >> Bleh... >> >> So, I'm back to trying to figure out how to compile and install it from >> source. >> >> ---------- Post added at 03:30 PM ---------- Previous post was at 01:13 >> PM ---------- >> >> Sooooooooooo.... >> $ tar -zxvf ptlib-2.6.7.tar.gz >> $ tar -zxvf opal-3.6.8.tar.gz >> $ tar -zxvf ekiga-3.2.7.tar.gz >> >> $ cd pt[tab] >> $ make clean >> $ ./configure --prefix=/usr >> $ make >> $ su >> # make install >> # exit >> >> Rinse and repeat... >> >> ...and: >> /usr/include/ffmpeg/libavutil/common.h:165:47: error: 'UINT64_C' was not >> declared in this scope >> make[2]: *** [obj/h263-1998.o] Error 1 > > There are some problems with such non-free codecs. Until they get > fixed, I propose you to just remove plugins/video/H.263-1998 from opal. > >> --- >> Now I installed the regular version again, and ran it with -d 4: >> [herman at leo ~]$ ekiga -d 1 > [...] >> write PDU to closed transport >> udp$86.64.162.35:5060 >> Segmentation fault (core dumped) > > Please use it inside gdb, as shown at > http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze > > Thanks! > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list OK, the trace is attached. Hope it helps! Cheers, Herman -------------- next part -------------- A non-text attachment was scrubbed... Name: gdb-ekiga.txt.gz Type: application/x-gzip Size: 11433 bytes Desc: not available URL: From herman at aeronetworks.ca Fri May 13 21:35:03 2011 From: herman at aeronetworks.ca (herman) Date: Fri, 13 May 2011 14:35:03 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory Message-ID: <4DCDA407.7080008@aeronetworks.ca> Hi guys, How can I resolve this problem on Fedora 14: In file included from /usr/include/libnotify/notify.h:28:0, from ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: No such file or directory compilation terminated. make[6]: *** [libnotify-main.lo] Error 1 [root at leo ekiga-3.2.7]# find /usr -name gtk.h /usr/include/gtk-2.0/gtk/gtk.h /usr/include/gtk-3.0/gtk/gtk.h So??? Cheers, Herman From papillion at gmail.com Sat May 14 02:14:56 2011 From: papillion at gmail.com (Anthony Papillion) Date: Fri, 13 May 2011 21:14:56 -0500 Subject: [Ekiga-list] Echo cancellation isn't working on 3.2.7 Message-ID: <4DCDE5A0.1010909@gmail.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 OS: Windows XP Professional Ekiga Version: 3.2.7 Hello Everyone, I'm experiencing a complete failure of echo cancellation on the current stable version of Ekiga. When I'm in a voice call (both parties have headsets on) both me and the person I'm talking to can hear our own voices coming back over the network. We've both made sure that both our input and output devices are the same and both confirmed that no sound is actually coming through the speakers. For the record, I've not tried to see if this problem occurs on Linux (but I will later). Also, for some reason, IM messages routinely fail to go through even if we are both online. My router is properly configured with port forwarding and I've disabled STUN. Can anyone help? Thanks! Anthony - -- Anthony Papillion Advanced Data Concepts Open Software Development and IT Services Office: (918) 919-4624 Mobile: (918) 320-9968 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (MingW32) iQIcBAEBCAAGBQJNzeWfAAoJEIeUq9QAeLbk7D0P/iu7vdJWmQXUetqURAtj6jma j3+NfmHuc6UtKf4fIPX6CJHBVoVzXsA3glK4Jz4CbyvoAk99VrSEMATHw4MrWef5 YmFgl3u/fW88VEZ2RuqNr6TcypiJj7M2WTIknpAmd5n/YJthp3iG1vqQ2dpxaWwI jUJPOYEY6nPzjWpi6GaM8O5h15XdmB6tAhsV/IJbiu7twDnWA5OrlkiWL0gDoKaa MXyaasmeorRp39Ga5r5RFe+D1+raUuOOVcaaRib0yh8MIpK2kIBGQiyhKEwzbyZt P/LnOtZpcy96GkH0uFRCMgH5rKR0Z7VqJsvRgq4uIw68Z+Re1os1sUfrdA+sZT2v k3a8gMxIu72idM43Myx0+qxGHbs3AHDkIs9QNVdzvjsDunceCPqxn+HQ1F4dYFan zcludpcHzGaEUtUWu5+XXRwFfJK//IqQA8Z6oHoI0sW4ENe8/4ihDo0W/HkJxl+C FXWvZj+YvIl6i4pUjZhLV3euFueRM6IMLa5dhofcwH7LnNuVTry3LP7XIZPxHyjL 4sU2gIHdPP7Qm+Dm5V3E6fwi04vjdUzatcHLLm4KH9xnTVcz+Ed82ZvUr2GjovRz BhSIcn2SNY+e1WMsXWdovxlzvlJSVPye/zJMHMw0prZ6Vc6yfn1hMS/xsdtR4+Gx +sdmxkT9d4ocHSZ1A9JF =GSFs -----END PGP SIGNATURE----- From oskiiiiii at riseup.net Mon May 16 07:31:29 2011 From: oskiiiiii at riseup.net (Oskiiiiii) Date: Mon, 16 May 2011 09:31:29 +0200 Subject: [Ekiga-list] Cannot set a conference room as private Message-ID: <4DD0D2D1.5040702@riseup.net> Sorry, on my last message I used a wrong thread for this. I start a new thread now. Hi, I have a (I supose) well-known problem with Ekiga. The documentation says that you can start a private conference room by calling 501xxxx at ekiga.net, and then it says something about establishing a pin number to give to the other people wanting to join the conference. It seems that there is no way to set up this number. Ekiga does not ask for it ???? I supose there is a known problem, because I have search a lot, and I have find several post in several forums regarding to this issue, but I never found an answer ???? neither in forum nor in ekiga documentation. That very strange, as far as the post I found are relatively old. Why nobody has answered this in any forum? It seems like "The mistery of ekiga private rooms". Thanks a lot, sorry if there is a trivial answer to this, but I have spent a lot of time searching for a solution before posting. Regards -- ----------------------------------------------------------------------------- /"Si Eva hubiera escrito el G?nesis, ?c?mo ser?a la primera noche de amor del g?nero humano? Eva hubiera empezado por aclarar que ella no naci? de ninguna costilla, ni conoci? a ninguna serpiente, ni ofreci? manzanas a nadie, y que Dios nunca le dijo que parir?s con dolor y tu marido te dominar?. Que todas esas historias son puras mentiras que Ad?n cont? a la prensa"/ * Eduardo Galeano* ----------------------------------------------------------------------------- No estoy en Facebook, ni me interesa Facebook. No publico, por tanto, nada en Facebook. Sin embargo, no soy due?o de mi intimidad por culpa de Facebook. Ocurre que cuando publicas algo en Facebook, tu acuerdo con este implica que eres propietario intelectual del contenido, y que les cedes los derechos automaticamente. As? que no puedo controlar mi intimidad, porque t? puedes subir una foto m?a, en la que salga yo, o contenidos de mi propiedad a Facebook. Si ma?ana una foto en la que yo aparezca o un contenido de mi propiedad que tu hayas subido, es publicado en televisi?n, internet, prensa, etc., yo no puedo demandar a Facebook, porque adquiri? de ti los derechos de publicarlo. Si te podr?a demandar a t? por ceder derechos que no son tuyos, pero nunca lo har?a, porque si lees esto es que te tengo alg?n aprecio. En virtud a ese aprecio, y en la esperanza de que sea mutuo, te pido que no me publiques, etiquetes, ni me hagas part?cipe de ningun contenido que publiques en Facebook o cualquier otra red social comercial. Si?ntete libre, en cambio, de usar esto como firma de correo. Si quieres darte de baja en Facebook, de manera definitiva: /http://www.darsedebaja.net/de/facebook/ _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list From herman at aeronetworks.ca Mon May 16 03:19:21 2011 From: herman at aeronetworks.ca (herman) Date: Sun, 15 May 2011 20:19:21 -0700 Subject: [Ekiga-list] socks proxy Message-ID: <0000174993@mail.aeronetworks.ca> Hi guys, I googled to no avail. Does anyone have information on how to set up Ekiga to use a Socks proxy? Cheers, H. -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc.philippe at viacesi.fr Mon May 16 11:26:10 2011 From: marc.philippe at viacesi.fr (PHILIPPE MARC) Date: Mon, 16 May 2011 11:26:10 +0000 Subject: [Ekiga-list] automatic call completed Message-ID: <6B39E82256FE1147B67276B68859B1F884ED30@SN2PRD0102MB105.prod.exchangelabs.com> Hi, I'm trying to use ekiga 3.2.6 under ubuntu 10.04 TLS. I'm able to register but i can connect to the echo test from ekiga but the call completed immediatly. I'm using a freebox not configured in router mode. y'ouve got the debug output at http://pastebin.ca/2061263 Can somebody tell me what's going on ? Cordialement, Marc Philippe 23 rue du Cagire 31100 Toulouse Tel : 0950693969 GSM : 0681569116 -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Mon May 16 13:52:26 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 17 May 2011 01:52:26 +1200 Subject: [Ekiga-list] automatic call completed In-Reply-To: <6B39E82256FE1147B67276B68859B1F884ED30@SN2PRD0102MB105.prod.exchangelabs.com> References: <6B39E82256FE1147B67276B68859B1F884ED30@SN2PRD0102MB105.prod.exchangelabs.com> Message-ID: <4DD12C1A.2000708@me.com> On 16/05/11 11:26 PM, PHILIPPE MARC wrote: > Hi, > > I'm trying to use ekiga 3.2.6 under ubuntu 10.04 TLS. I'm able to > register but i can connect to the echo test from ekiga but the call > completed immediatly. > I'm using a freebox not configured in router mode. > > y'ouve got the debug output at http://pastebin.ca/2061263 > > Can somebody tell me what's going on ? > I've just fired up my client to test this, and funnily enough I'm seeing the same thing on a known good configuration. Server issues? -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Mon May 16 13:56:49 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 17 May 2011 01:56:49 +1200 Subject: [Ekiga-list] automatic call completed In-Reply-To: <4DD12C1A.2000708@me.com> References: <6B39E82256FE1147B67276B68859B1F884ED30@SN2PRD0102MB105.prod.exchangelabs.com> <4DD12C1A.2000708@me.com> Message-ID: <4DD12D21.5060801@me.com> On 17/05/11 01:52 AM, Dave Koelmeyer wrote: > On 16/05/11 11:26 PM, PHILIPPE MARC wrote: >> Hi, >> >> I'm trying to use ekiga 3.2.6 under ubuntu 10.04 TLS. I'm able to >> register but i can connect to the echo test from ekiga but the call >> completed immediatly. >> I'm using a freebox not configured in router mode. >> >> y'ouve got the debug output at http://pastebin.ca/2061263 >> >> Can somebody tell me what's going on ? >> > > > I've just fired up my client to test this, and funnily enough I'm > seeing the same thing on a known good configuration. Server issues? > -- > Dave Koelmeyer > http://davekoelmeyer.wordpress.com/ No problems making a test call using the Sip2Sip echo test from Ekiga 3.2.7, looks like this might be confined to Ekiga.net? http://sip2sip.info/ -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Mon May 16 14:05:00 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 17 May 2011 02:05:00 +1200 Subject: [Ekiga-list] Connecting to Ekiga.net from non-Ekiga SIP clients Message-ID: <4DD12F0C.4000902@me.com> Hi All, While reading through the H-Online article I posted recently, they made reference to this: http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net I'm not au fait with the technical reasons for this, but is this an issue which could be resolved? At the very least this should probably be signposted a bit more prominently on the Wiki or similar, as those not aware of this issue could be trying to connect to Ekiga.net from the Mac OS platform using Blink for example, to chat with Ekiga.net users using the actual Ekiga client on supported platforms, only to not have it work for no apparent reason. -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 16 16:05:11 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 16 May 2011 18:05:11 +0200 Subject: [Ekiga-list] Echo cancellation isn't working on 3.2.7 In-Reply-To: <4DCDE5A0.1010909@gmail.com> References: <4DCDE5A0.1010909@gmail.com> Message-ID: <4DD14B37.6090605@pu-pm.univ-fcomte.fr> On 14/05/11 04:14, Anthony Papillion wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > OS: Windows XP Professional > Ekiga Version: 3.2.7 > > Hello Everyone, > > I'm experiencing a complete failure of echo cancellation on the current > stable version of Ekiga. When I'm in a voice call (both parties have > headsets on) both me and the person I'm talking to can hear our own > voices coming back over the network. > > We've both made sure that both our input and output devices are the same > and both confirmed that no sound is actually coming through the speakers. > > For the record, I've not tried to see if this problem occurs on Linux > (but I will later). Do you say that even with headsets you have echo? This is really strange! Echo cancellation does not work with 3.2.7, see https://bugzilla.gnome.org/show_bug.cgi?id=621094. But this applies only when you do NOT have headsets! > Also, for some reason, IM messages routinely fail to go through even if > we are both online. My router is properly configured with port > forwarding and I've disabled STUN. This should work... Only -d 4 (on both parties) can tell what happens: it is a matter of finding out if IM sent packets arrive at receiver. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 16 16:07:12 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 16 May 2011 18:07:12 +0200 Subject: [Ekiga-list] socks proxy In-Reply-To: <0000174993@mail.aeronetworks.ca> References: <0000174993@mail.aeronetworks.ca> Message-ID: <4DD14BB0.70601@pu-pm.univ-fcomte.fr> On 16/05/11 05:19, herman wrote: > Hi guys, > > I googled to no avail. Does anyone have information on how to set up Ekiga > to use a Socks proxy? This is strange, since ptlib has socks support. What $ grep SOCKS /usr/lib/pkgconfig/ptlib.pc shows in your machine? -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 16 16:10:14 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 16 May 2011 18:10:14 +0200 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory In-Reply-To: <4DCDA407.7080008@aeronetworks.ca> References: <4DCDA407.7080008@aeronetworks.ca> Message-ID: <4DD14C66.8010103@pu-pm.univ-fcomte.fr> On 13/05/11 23:35, herman wrote: > > Hi guys, > > How can I resolve this problem on Fedora 14: > In file included from /usr/include/libnotify/notify.h:28:0, > from ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: > /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: No > such file or directory > compilation terminated. > make[6]: *** [libnotify-main.lo] Error 1 > > [root at leo ekiga-3.2.7]# find /usr -name gtk.h > /usr/include/gtk-2.0/gtk/gtk.h > /usr/include/gtk-3.0/gtk/gtk.h > > So??? > > Cheers, > > Herman > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > This is strange. Could you give us the command line leading to this error (compoilation of libnotify-main.cpp)? For me, the following flag appears: -I/usr/include/gtk-2.0 hence it works. -- Eugen From herman at aeronetworks.ca Mon May 16 17:19:43 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 10:19:43 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> Message-ID: <4DD15CAF.4020400@aeronetworks.ca> On 05/16/2011 08:10 PM, Eugen Dedu wrote: > > On 13/05/11 23:35, herman wrote: >> >> Hi guys, >> >> How can I resolve this problem on Fedora 14: >> In file included from /usr/include/libnotify/notify.h:28:0, >> from ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: No >> such file or directory >> compilation terminated. >> make[6]: *** [libnotify-main.lo] Error 1 >> >> [root at leo ekiga-3.2.7]# find /usr -name gtk.h >> /usr/include/gtk-2.0/gtk/gtk.h >> /usr/include/gtk-3.0/gtk/gtk.h >> >> So??? >> >> Cheers, >> >> Herman >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> > > This is strange. Could you give us the command line leading to this > error (compoilation of libnotify-main.cpp)? For me, the following > flag appears: > -I/usr/include/gtk-2.0 > hence it works. > Hi, The platform is Fedora Core 14. After compiling ptlib-2.6.7 and opal-3.6.8 successfully, I did: $ tar -zxvf ekiga-3.2.7.tar.gz $ cd ekiga-3.2.7 $ ./configure --prefix=/usr $ make Hope that helps! Herman From anto.trande at gmail.com Mon May 16 17:21:10 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Mon, 16 May 2011 19:21:10 +0200 Subject: [Ekiga-list] ekiga - full cpu used Message-ID: Hi, i'm setting my ekiga 3.3.0 on Fedora 15. I use a D-Link DSL2640R router , with open forward ports 3478, 5000-5100, 1720 to bypass NAT. Sometimes echo test or conference room test doesn't function, but i believe that is normal (depend by server, i think) The calls instead, send or received, uses up CPU completely crashing Ekiga. Can i do something to resolve problem ? Thanks -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 16 17:23:25 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 16 May 2011 19:23:25 +0200 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory In-Reply-To: <4DD15CAF.4020400@aeronetworks.ca> References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> <4DD15CAF.4020400@aeronetworks.ca> Message-ID: <4DD15D8D.2030604@pu-pm.univ-fcomte.fr> On 16/05/11 19:19, herman wrote: > > On 05/16/2011 08:10 PM, Eugen Dedu wrote: >> >> On 13/05/11 23:35, herman wrote: >>> >>> Hi guys, >>> >>> How can I resolve this problem on Fedora 14: >>> In file included from /usr/include/libnotify/notify.h:28:0, >>> from ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >>> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: No >>> such file or directory >>> compilation terminated. >>> make[6]: *** [libnotify-main.lo] Error 1 >>> >>> [root at leo ekiga-3.2.7]# find /usr -name gtk.h >>> /usr/include/gtk-2.0/gtk/gtk.h >>> /usr/include/gtk-3.0/gtk/gtk.h >>> >>> So??? >>> >>> Cheers, >>> >>> Herman >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >> >> This is strange. Could you give us the command line leading to this >> error (compoilation of libnotify-main.cpp)? For me, the following flag >> appears: >> -I/usr/include/gtk-2.0 >> hence it works. >> > Hi, > > The platform is Fedora Core 14. > > After compiling ptlib-2.6.7 and opal-3.6.8 successfully, I did: > $ tar -zxvf ekiga-3.2.7.tar.gz > $ cd ekiga-3.2.7 > $ ./configure --prefix=/usr > $ make Re-execute "make V=1" and tell us what it shows. -- Eugen From herman at aeronetworks.ca Mon May 16 17:31:46 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 10:31:46 -0700 Subject: [Ekiga-list] socks proxy References: <0000174993@mail.aeronetworks.ca> <4DD14BB0.70601@pu-pm.univ-fcomte.fr> Message-ID: <4DD15F82.90402@aeronetworks.ca> On 05/16/2011 08:07 PM, Eugen Dedu wrote: > > On 16/05/11 05:19, herman wrote: >> Hi guys, >> >> I googled to no avail. Does anyone have information on how to set up >> Ekiga >> to use a Socks proxy? > > This is strange, since ptlib has socks support. What > $ grep SOCKS /usr/lib/pkgconfig/ptlib.pc > shows in your machine? > Pardon, I'm sure it has socks support, I just don't know what syntax to enter into the proxy setting. I cannot experiment, since I don't have Ekiga working on my netbook yet. I'm trying to read up on it beforehand. How do I tell Ekiga that the proxy is a socks proxy and not some other sort of proxy: socks://socks.example.com ??? From herman at aeronetworks.ca Mon May 16 17:41:03 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 10:41:03 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> <4DD15CAF.4020400@aeronetworks.ca> <4DD15D8D.2030604@pu-pm.univ-fcomte.fr> Message-ID: <4DD161AF.5090809@aeronetworks.ca> On 05/16/2011 09:23 PM, Eugen Dedu wrote: > make V=1 ... snip... libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. -I../../../../lib/engine/framework -I../../../../lib/engine/notification -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -pthread -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -g -O2 -Wall -Wextra -Winit-self -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal -Wshadow -MT libnotify-main.lo -MD -MP -MF .deps/libnotify-main.Tpo -c ../../../../lib/engine/components/libnotify/libnotify-main.cpp -fPIC -DPIC -o .libs/libnotify-main.o In file included from /usr/include/libnotify/notify.h:28:0, from ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: No such file or directory compilation terminated. make[6]: *** [libnotify-main.lo] Error 1 make[6]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components/libnotify' make[5]: *** [all-recursive] Error 1 make[5]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' make: *** [all] Error 2 [herman at leo ekiga-3.2.7]$ The header file is here: [herman at leo ekiga-3.2.7]$ find /usr -name gtk.h /usr/include/gtk-2.0/gtk/gtk.h /usr/include/gtk-3.0/gtk/gtk.h So something like -I/usr/include/gtk-2.0/gtk/ is missing. I could add that manually if you could tell me in which file makefile I should add it. Cheers, H. From herman at aeronetworks.ca Mon May 16 17:55:58 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 10:55:58 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> <4DD15CAF.4020400@aeronetworks.ca> <4DD15D8D.2030604@pu-pm.univ-fcomte.fr> <4DD161AF.5090809@aeronetworks.ca> Message-ID: <4DD1652E.3040407@aeronetworks.ca> On 05/16/2011 09:41 PM, herman wrote: > > > On 05/16/2011 09:23 PM, Eugen Dedu wrote: >> make V=1 > > .... snip... > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. > -I../../../../lib/engine/framework > -I../../../../lib/engine/notification -I/usr/include/sigc++-2.0 > -I/usr/lib/sigc++-2.0/include -pthread -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 > -I/usr/lib/dbus-1.0/include -g -O2 -Wall -Wextra -Winit-self > -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal > -Wshadow -MT libnotify-main.lo -MD -MP -MF ..deps/libnotify-main.Tpo > -c .../../../../lib/engine/components/libnotify/libnotify-main.cpp > -fPIC -DPIC -o .libs/libnotify-main.o > In file included from /usr/include/libnotify/notify.h:28:0, > from > .../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: > /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: > No such file or directory > compilation terminated. > make[6]: *** [libnotify-main.lo] Error 1 > make[6]: Leaving directory > `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components/libnotify' > make[5]: *** [all-recursive] Error 1 > make[5]: Leaving directory > `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' > make[2]: *** [all] Error 2 > make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' > make[1]: *** [all-recursive] Error 1 > make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' > make: *** [all] Error 2 > [herman at leo ekiga-3.2.7]$ > > > The header file is here: > [herman at leo ekiga-3.2.7]$ find /usr -name gtk.h > /usr/include/gtk-2.0/gtk/gtk.h > /usr/include/gtk-3.0/gtk/gtk.h > > So something like -I/usr/include/gtk-2.0/gtk/ is missing. > > I could add that manually if you could tell me in which file makefile > I should add it. > > Cheers, > > H. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Hmm, in file: lib/engine/components/libnotify/Makefile I see the following: GTK_CFLAGS = -pthread -I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 Should it be /usr/include/gtk-2.0/gtk/ ? From LBell at connexsustech.com Mon May 16 17:59:34 2011 From: LBell at connexsustech.com (Lisa Bell) Date: Mon, 16 May 2011 17:59:34 +0000 Subject: [Ekiga-list] remove me from the mailing list Message-ID: <3BC653616CAB1D45BC1A60CD5DF13A760EC25D9D@PRS-Exchange.millmrk.com> Best Wishes! Lisa R Bell Project Manager 913.248.6231 (voice) 913.248.0727 (fax) 816.769.7915 (cell) lbell at connexsustech.com ConneXsus Technology Solutions, LLC. 10314 Shawnee Mission Parkway Ste 260 Shawnee, KS 66203 -------------- next part -------------- An HTML attachment was scrubbed... URL: From fernandbuysse at gmail.com Mon May 16 18:06:33 2011 From: fernandbuysse at gmail.com (Fernand Buysse) Date: Mon, 16 May 2011 20:06:33 +0200 Subject: [Ekiga-list] remove me from the mailing list In-Reply-To: <3BC653616CAB1D45BC1A60CD5DF13A760EC25D9D@PRS-Exchange.millmrk.com> References: <3BC653616CAB1D45BC1A60CD5DF13A760EC25D9D@PRS-Exchange.millmrk.com> Message-ID: unsuscribe from mailinglist 2011/5/16 Lisa Bell > > > > > *Best Wishes!* > > * * > > *Lisa R Bell* > > Project Manager > > *913.248.6231 (voice) * > > *913.248.0727 (fax) * > > *816.769.7915 (cell)* > > *lbell at connexsustech.com* > > *ConneXsus Technology Solutions, LLC. * > > 10314 Shawnee Mission Parkway Ste 260 > > Shawnee, KS 66203 > > * * > > > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From herman at aeronetworks.ca Mon May 16 18:10:29 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 11:10:29 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> <4DD15CAF.4020400@aeronetworks.ca> <4DD15D8D.2030604@pu-pm.univ-fcomte.fr> <4DD161AF.5090809@aeronetworks.ca> <4DD1652E.3040407@aeronetworks.ca> Message-ID: <4DD16895.3030500@aeronetworks.ca> On 05/16/2011 09:55 PM, herman wrote: > > > On 05/16/2011 09:41 PM, herman wrote: >> >> >> On 05/16/2011 09:23 PM, Eugen Dedu wrote: >>> make V=1 >> >> .... snip... >> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. >> -I../../../../lib/engine/framework >> -I../../../../lib/engine/notification -I/usr/include/sigc++-2.0 >> -I/usr/lib/sigc++-2.0/include -pthread -I/usr/include/glib-2.0 >> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 >> -I/usr/lib/dbus-1.0/include -g -O2 -Wall -Wextra -Winit-self >> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal >> -Wshadow -MT libnotify-main.lo -MD -MP -MF ..deps/libnotify-main.Tpo >> -c .../../../../lib/engine/components/libnotify/libnotify-main.cpp >> -fPIC -DPIC -o .libs/libnotify-main.o >> In file included from /usr/include/libnotify/notify.h:28:0, >> from >> .../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: >> No such file or directory >> compilation terminated. >> make[6]: *** [libnotify-main.lo] Error 1 >> make[6]: Leaving directory >> `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components/libnotify' >> make[5]: *** [all-recursive] Error 1 >> make[5]: Leaving directory >> `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components' >> make[4]: *** [all-recursive] Error 1 >> make[4]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine' >> make[3]: *** [all-recursive] Error 1 >> make[3]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' >> make[2]: *** [all] Error 2 >> make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' >> make[1]: *** [all-recursive] Error 1 >> make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' >> make: *** [all] Error 2 >> [herman at leo ekiga-3.2.7]$ >> >> >> The header file is here: >> [herman at leo ekiga-3.2.7]$ find /usr -name gtk.h >> /usr/include/gtk-2.0/gtk/gtk.h >> /usr/include/gtk-3.0/gtk/gtk.h >> >> So something like -I/usr/include/gtk-2.0/gtk/ is missing. >> >> I could add that manually if you could tell me in which file makefile >> I should add it. >> >> Cheers, >> >> H. >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list > > Hmm, in file: lib/engine/components/libnotify/Makefile I see the > following: > > GTK_CFLAGS = -pthread -I/usr/include/gtk-2.0 > -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/cairo > -I/usr/include/gdk-pixbuf-2.0 -I/usr/include/pango-1.0 > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng12 > > Should it be /usr/include/gtk-2.0/gtk/ ? > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list OK I sort of figured it out, but I'm not good with the configuration system and has no idea how it really works, so I hacked the Makefile and added GTK_CFLAGS: libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) $(GTK_CFLAGS) It is busy compiling now - this little netbook is sloooooow - cross fingers... From herman at aeronetworks.ca Mon May 16 18:18:33 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 11:18:33 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> <4DD15CAF.4020400@aeronetworks.ca> <4DD15D8D.2030604@pu-pm.univ-fcomte.fr> <4DD161AF.5090809@aeronetworks.ca> <4DD1652E.3040407@aeronetworks.ca> <4DD16895.3030500@aeronetworks.ca> Message-ID: <4DD16A79.1080205@aeronetworks.ca> On 05/16/2011 10:10 PM, herman wrote: > > > On 05/16/2011 09:55 PM, herman wrote: >> >> >> On 05/16/2011 09:41 PM, herman wrote: >>> >>> >>> On 05/16/2011 09:23 PM, Eugen Dedu wrote: >>>> make V=1 >>> >>> .... snip... >>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. >>> -I../../../../lib/engine/framework >>> -I../../../../lib/engine/notification -I/usr/include/sigc++-2.0 >>> -I/usr/lib/sigc++-2.0/include -pthread -I/usr/include/glib-2.0 >>> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 >>> -I/usr/lib/dbus-1.0/include -g -O2 -Wall -Wextra -Winit-self >>> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal >>> -Wshadow -MT libnotify-main.lo -MD -MP -MF ..deps/libnotify-main.Tpo >>> -c .../../../../lib/engine/components/libnotify/libnotify-main.cpp >>> -fPIC -DPIC -o .libs/libnotify-main.o >>> In file included from /usr/include/libnotify/notify.h:28:0, >>> from >>> .../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >>> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: >>> No such file or directory >>> compilation terminated. >>> make[6]: *** [libnotify-main.lo] Error 1 >>> make[6]: Leaving directory >>> `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components/libnotify' >>> make[5]: *** [all-recursive] Error 1 >>> make[5]: Leaving directory >>> `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components' >>> make[4]: *** [all-recursive] Error 1 >>> make[4]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine' >>> make[3]: *** [all-recursive] Error 1 >>> make[3]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' >>> make[2]: *** [all] Error 2 >>> make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' >>> make[1]: *** [all-recursive] Error 1 >>> make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' >>> make: *** [all] Error 2 >>> [herman at leo ekiga-3.2.7]$ >>> >>> >>> The header file is here: >>> [herman at leo ekiga-3.2.7]$ find /usr -name gtk.h >>> /usr/include/gtk-2.0/gtk/gtk.h >>> /usr/include/gtk-3.0/gtk/gtk.h >>> >>> So something like -I/usr/include/gtk-2.0/gtk/ is missing. >>> >>> I could add that manually if you could tell me in which file >>> makefile I should add it. >>> >>> Cheers, >>> >>> H. >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >> >> Hmm, in file: lib/engine/components/libnotify/Makefile I see the >> following: >> >> GTK_CFLAGS = -pthread -I/usr/include/gtk-2.0 >> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 >> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 >> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 >> -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 >> -I/usr/include/freetype2 -I/usr/include/libpng12 >> >> Should it be /usr/include/gtk-2.0/gtk/ ? >> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list > OK I sort of figured it out, but I'm not good with the configuration > system and has no idea how it really works, so I hacked the Makefile > and added GTK_CFLAGS: > libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp > $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) > --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) > $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) $(GTK_CFLAGS) > > It is busy compiling now - this little netbook is sloooooow - cross > fingers... > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Aaaawww man. The compile finished with no errors, but make install failed: ...snip... scrollkeeper-update -p /var/lib/rarian -o /usr/share/omf/ekiga make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/help' make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/help' make[1]: Entering directory `/home/herman/Ekiga/ekiga-3.2.7' make[2]: Entering directory `/home/herman/Ekiga/ekiga-3.2.7' make[2]: Nothing to be done for `install-exec-am'. test -z "/usr/share/applications" || /bin/mkdir -p "/usr/share/applications" /usr/bin/install -c -m 644 ekiga.desktop '/usr/share/applications' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults gconftool-2 --makefile-install-rule ekiga.schemas 2>&1 > /dev/null gconftool-2 --shutdown ** GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: (connection->initialization_error == NULL) make[2]: *** [install-schemas] Aborted (core dumped) make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' make: *** [install-recursive] Error 1 [root at leo ekiga-3.2.7]# Well, this is not for a lack of trying, but with the configuration and make tools, I really don't know what I am doing... From herman at aeronetworks.ca Mon May 16 18:30:44 2011 From: herman at aeronetworks.ca (herman) Date: Mon, 16 May 2011 11:30:44 -0700 Subject: [Ekiga-list] fatal error: gtk/gtk.h: No such file or directory References: <4DCDA407.7080008@aeronetworks.ca> <4DD14C66.8010103@pu-pm.univ-fcomte.fr> <4DD15CAF.4020400@aeronetworks.ca> <4DD15D8D.2030604@pu-pm.univ-fcomte.fr> <4DD161AF.5090809@aeronetworks.ca> <4DD1652E.3040407@aeronetworks.ca> <4DD16895.3030500@aeronetworks.ca> <4DD16A79.1080205@aeronetworks.ca> Message-ID: <4DD16D54.7070708@aeronetworks.ca> On 05/16/2011 10:18 PM, herman wrote: > > > On 05/16/2011 10:10 PM, herman wrote: >> >> >> On 05/16/2011 09:55 PM, herman wrote: >>> >>> >>> On 05/16/2011 09:41 PM, herman wrote: >>>> >>>> >>>> On 05/16/2011 09:23 PM, Eugen Dedu wrote: >>>>> make V=1 >>>> >>>> .... snip... >>>> libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../../../.. >>>> -I../../../../lib/engine/framework >>>> -I../../../../lib/engine/notification -I/usr/include/sigc++-2.0 >>>> -I/usr/lib/sigc++-2.0/include -pthread -I/usr/include/glib-2.0 >>>> -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 >>>> -I/usr/lib/dbus-1.0/include -g -O2 -Wall -Wextra -Winit-self >>>> -Wswitch-default -Wswitch-enum -Wstrict-aliasing=2 -Wfloat-equal >>>> -Wshadow -MT libnotify-main.lo -MD -MP -MF >>>> ..deps/libnotify-main.Tpo -c >>>> .../../../../lib/engine/components/libnotify/libnotify-main.cpp >>>> -fPIC -DPIC -o .libs/libnotify-main.o >>>> In file included from /usr/include/libnotify/notify.h:28:0, >>>> from >>>> .../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >>>> /usr/include/libnotify/notification.h:28:21: fatal error: >>>> gtk/gtk.h: No such file or directory >>>> compilation terminated. >>>> make[6]: *** [libnotify-main.lo] Error 1 >>>> make[6]: Leaving directory >>>> `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components/libnotify' >>>> make[5]: *** [all-recursive] Error 1 >>>> make[5]: Leaving directory >>>> `/home/herman/Ekiga/ekiga-3.2.7/lib/engine/components' >>>> make[4]: *** [all-recursive] Error 1 >>>> make[4]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib/engine' >>>> make[3]: *** [all-recursive] Error 1 >>>> make[3]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' >>>> make[2]: *** [all] Error 2 >>>> make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/lib' >>>> make[1]: *** [all-recursive] Error 1 >>>> make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' >>>> make: *** [all] Error 2 >>>> [herman at leo ekiga-3.2.7]$ >>>> >>>> >>>> The header file is here: >>>> [herman at leo ekiga-3.2.7]$ find /usr -name gtk.h >>>> /usr/include/gtk-2.0/gtk/gtk.h >>>> /usr/include/gtk-3.0/gtk/gtk.h >>>> >>>> So something like -I/usr/include/gtk-2.0/gtk/ is missing. >>>> >>>> I could add that manually if you could tell me in which file >>>> makefile I should add it. >>>> >>>> Cheers, >>>> >>>> H. >>>> _______________________________________________ >>>> ekiga-list mailing list >>>> ekiga-list at gnome.org >>>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >>> Hmm, in file: lib/engine/components/libnotify/Makefile I see the >>> following: >>> >>> GTK_CFLAGS = -pthread -I/usr/include/gtk-2.0 >>> -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0 >>> -I/usr/include/cairo -I/usr/include/gdk-pixbuf-2.0 >>> -I/usr/include/pango-1.0 -I/usr/include/glib-2.0 >>> -I/usr/lib/glib-2.0/include -I/usr/include/pixman-1 >>> -I/usr/include/freetype2 -I/usr/include/libpng12 >>> >>> Should it be /usr/include/gtk-2.0/gtk/ ? >>> >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >> OK I sort of figured it out, but I'm not good with the configuration >> system and has no idea how it really works, so I hacked the Makefile >> and added GTK_CFLAGS: >> libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp >> $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) >> --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) >> $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) $(GTK_CFLAGS) >> >> It is busy compiling now - this little netbook is sloooooow - cross >> fingers... >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list > Aaaawww man. > > The compile finished with no errors, but make install failed: > ....snip... > scrollkeeper-update -p /var/lib/rarian -o /usr/share/omf/ekiga > make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/help' > make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7/help' > make[1]: Entering directory `/home/herman/Ekiga/ekiga-3.2.7' > make[2]: Entering directory `/home/herman/Ekiga/ekiga-3.2.7' > make[2]: Nothing to be done for `install-exec-am'. > test -z "/usr/share/applications" || /bin/mkdir -p > "/usr/share/applications" > /usr/bin/install -c -m 644 ekiga.desktop '/usr/share/applications' > GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults > gconftool-2 --makefile-install-rule ekiga.schemas 2>&1 > /dev/null > gconftool-2 --shutdown > ** > GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: > (connection->initialization_error == NULL) > make[2]: *** [install-schemas] Aborted (core dumped) > make[2]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory `/home/herman/Ekiga/ekiga-3.2.7' > make: *** [install-recursive] Error 1 > [root at leo ekiga-3.2.7]# > > Well, this is not for a lack of trying, but with the configuration and > make tools, I really don't know what I am doing... > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list OK, it turns out that the failed installer did install it, but it still crashes, same as before: 2011/05/16 22:27:29.785 7:58.436 Housekeeper:0xb6b7cb70 OpalUDP Setting interface to 192.168.168.1%vmnet8 2011/05/16 22:27:29.786 7:58.436 Housekeeper:0xb6b7cb70 SIP Transaction timers set: retry=0.500, completion=6.000 2011/05/16 22:27:29.787 7:58.437 Housekeeper:0xb6b7cb70 SIP SUBSCRIBE transaction id=z9hG4bK1056202b-577e-e011-94ca-00265eebdaf4 timeout, making retry 1, timeout 1.000 Segmentation fault (core dumped) So compiling Ekiga myself on the actual machine that I want to run it on, doesn't help. BTW, I tried Fedora 15 Beta 2 in a VM and there, Ekiga runs. Cheers, Herman From marc.philippe at viacesi.fr Mon May 16 08:01:06 2011 From: marc.philippe at viacesi.fr (PHILIPPE MARC) Date: Mon, 16 May 2011 08:01:06 +0000 Subject: [Ekiga-list] ekiga connection problem : status : 500 Server internal error Message-ID: <6B39E82256FE1147B67276B68859B1F884EC90@SN2PRD0102MB105.prod.exchangelabs.com> Hi, I'm trying to use ekiga 3.2.6 under ubuntu 10.04 TLS. I'm able to register but i can not connect to the echo test from ekiga. I'm using a freebox not configured in router mode. I monitered th connection with wireshark and you can see screenshot of it in the pictures attached to the mail. Can somebody tell me what's going on ? Cordialement, Marc Philippe 23 rue du Cagire 31100 Toulouse Tel : 0950693969 GSM : 0681569116 -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: (Untitled) - Graph Analysis_001.png Type: image/png Size: 34026 bytes Desc: (Untitled) - Graph Analysis_001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: (Untitled) - Wireshark_005.png Type: image/png Size: 195552 bytes Desc: (Untitled) - Wireshark_005.png URL: From davekoelmeyer at me.com Tue May 17 06:44:51 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 17 May 2011 06:44:51 +0000 (GMT) Subject: [Ekiga-list] Error on Ekiga Interoperability page In-Reply-To: <620365.28709.qm@web65513.mail.ac4.yahoo.com> Message-ID: <62abbed0-4bf1-c92b-dacb-d8f6fe6b1a89@me.com> Hi Nicholas, I've updated the page so that X-Lite 4.0 is the current compatible version. Tested okay making audio calls to an OpenIndiana Ekiga 3.2.7 client, using the Ekiga.net service. X-Lite seems to work well, although the built-in advertising is a bit of a? turn-off. If you see anything else out of place please let the list know - thanks again for pointing this out :) Cheers, Dave Koelmeyer On 13 May, 2011,at 01:21 AM, Nicholas Jacobs wrote: > The Ekiga Interoperability page: > http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F > in the Mac OS section, lists X-Lite 3.2. > However, as far as I can tell, only X-Lite 4.0 is available for Mac OS, here: > http://download.cnet.com/X-Lite/3000-2349_4-44320.html > > If X-Lite 3.2 is compatible and X-Lite 4.0 is not, then X-Lite 4.0 should be > mentioned in the "Which programs don't work with Ekiga?" section. > Otherwise, mention of X-Lite 3.2 should just be replaced by X-Lite 4.0. > Either way the page needs to be updated. > > (I can't check this myself because I don't have a Mac; I'm looking for > something to recommend to a family member who does.) > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Tue May 17 06:47:22 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 17 May 2011 06:47:22 +0000 (GMT) Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List Message-ID: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> Hi, We really should include the HCL to include laptops with built-in webcams, given how popular they now are vs. external webcams. I've started the ball rolling by adding the Dell Latitude 2100, which I've tested with Ekiga under Windows XP: http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Optional.29 Any others, please let me know and I'll add 'em ?:) Cheers, Dave Koelmeyer -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 07:38:12 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 09:38:12 +0200 Subject: [Ekiga-list] ekiga connection problem : status : 500 Server internal error In-Reply-To: <6B39E82256FE1147B67276B68859B1F884EC90@SN2PRD0102MB105.prod.exchangelabs.com> References: <6B39E82256FE1147B67276B68859B1F884EC90@SN2PRD0102MB105.prod.exchangelabs.com> Message-ID: <4DD225E4.5080000@pu-pm.univ-fcomte.fr> On 16/05/11 10:01, PHILIPPE MARC wrote: > Hi, > > I'm trying to use ekiga 3.2.6 under ubuntu 10.04 TLS. I'm able to register but i can not connect to the echo test from ekiga. > I'm using a freebox not configured in router mode. > > I monitered th connection with wireshark and you can see screenshot of it in the pictures attached to the mail. > > Can somebody tell me what's going on ? It was a problem with ekiga.net server. It works now, sorry for inconvenience. -- Eugen From davekoelmeyer at me.com Tue May 17 08:07:40 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 17 May 2011 20:07:40 +1200 Subject: [Ekiga-list] Cannot set a conference room as private In-Reply-To: <4DD0D2D1.5040702@riseup.net> References: <4DD0D2D1.5040702@riseup.net> Message-ID: <4DD22CCC.7080909@me.com> On 16/05/11 07:31 PM, Oskiiiiii wrote: > Sorry, on my last message I used a wrong thread for this. I start a new > thread now. > > Hi, > > I have a (I supose) well-known problem with Ekiga. The documentation > says that you can start a private conference room by calling > 501xxxx at ekiga.net, and then it says something about establishing a pin > number to give to the other people wanting to join the conference. > > It seems that there is no way to set up this number. Ekiga does not ask > for it ???? > > I supose there is a known problem, because I have search a lot, and I > have find several post in several forums regarding to this issue, but I > never found an answer ???? neither in forum nor in ekiga documentation. > That very strange, as far as the post I found are relatively old. > > Why nobody has answered this in any forum? It seems like "The mistery of > ekiga private rooms". > > Thanks a lot, sorry if there is a trivial answer to this, but I have > spent a lot of time searching for a solution before posting. > After doing a little bit of investigation myself as well as some tinkering, I have found the same unresolved threads as you - so I believe the situation must be that private conference rooms do not work as presently documented on the Wiki, or do not work at all. Eugen et al, this is something we can get some confirmation on so I can update the documentation accordingly, as it's confusing for users :) Thanks, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ From anto.trande at gmail.com Tue May 17 08:10:56 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 10:10:56 +0200 Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List In-Reply-To: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> References: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> Message-ID: Sure! Webcam on my Acer Aspire 6930G with Fedora Linux (14 / 15) and RHEL6, works fine. I'm using Ekiga 3.2.6/ Ekiga 3.3.0. 2011/5/17 Dave Koelmeyer > Hi, > > We really should include the HCL to include laptops with built-in webcams, > given how popular they now are vs. external webcams. > > I've started the ball rolling by adding the Dell Latitude 2100, which I've > tested with Ekiga under Windows XP: > > http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Optional.29 > > Any others, please let me know and I'll add 'em :) > > Cheers, > Dave Koelmeyer > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 08:33:21 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 10:33:21 +0200 Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List In-Reply-To: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> References: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> Message-ID: <4DD232D1.4040501@pu-pm.univ-fcomte.fr> On 17/05/11 08:47, Dave Koelmeyer wrote: > Hi, > > We really should include the HCL to include laptops with built-in webcams, given > how popular they now are vs. external webcams. > > I've started the ball rolling by adding the Dell Latitude 2100, which I've > tested with Ekiga under Windows XP: > > http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Optional.29 > > Any others, please let me know and I'll add 'em :) There are many computers out there. I think it is better to add cameras which do NOT work. What do you think? -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 08:34:38 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 10:34:38 +0200 Subject: [Ekiga-list] Error on Ekiga Interoperability page In-Reply-To: <4DCC5379.7060307@me.com> References: <620365.28709.qm@web65513.mail.ac4.yahoo.com> <4DCC5379.7060307@me.com> Message-ID: <4DD2331E.7080808@pu-pm.univ-fcomte.fr> On 12/05/11 23:39, Dave Koelmeyer wrote: > On 13/05/11 01:21 AM, Nicholas Jacobs wrote: >> The Ekiga Interoperability page: >> http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F >> in the Mac OS section, lists X-Lite 3.2. >> However, as far as I can tell, only X-Lite 4.0 is available for Mac >> OS, here: >> http://download.cnet.com/X-Lite/3000-2349_4-44320.html >> >> If X-Lite 3.2 is compatible and X-Lite 4.0 is not, then X-Lite 4.0 >> should be >> mentioned in the "Which programs don't work with Ekiga?" section. >> Otherwise, mention of X-Lite 3.2 should just be replaced by X-Lite 4.0. >> Either way the page needs to be updated. >> >> (I can't check this myself because I don't have a Mac; I'm looking for >> something to recommend to a family member who does.) >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list > Hi Nicholas, > > Thanks - I'll check that out and update the page soon as I can. Have you checked it, Dave? Here is Yannick's answer, his e-mail address is blacklisted for the moment :o) -- Eugen -------------- next part -------------- A non-text attachment was scrubbed... Name: Re: [Ekiga-list] Error on Ekiga Interoperability page.eml Type: application/x-message-display Size: 3218 bytes Desc: not available URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 08:51:26 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 10:51:26 +0200 Subject: [Ekiga-list] Cannot set a conference room as private In-Reply-To: <4DD22CCC.7080909@me.com> References: <4DD0D2D1.5040702@riseup.net> <4DD22CCC.7080909@me.com> Message-ID: <4DD2370E.1010506@pu-pm.univ-fcomte.fr> On 17/05/11 10:07, Dave Koelmeyer wrote: > On 16/05/11 07:31 PM, Oskiiiiii wrote: >> Sorry, on my last message I used a wrong thread for this. I start a new >> thread now. >> >> Hi, >> >> I have a (I supose) well-known problem with Ekiga. The documentation >> says that you can start a private conference room by calling >> 501xxxx at ekiga.net, and then it says something about establishing a pin >> number to give to the other people wanting to join the conference. >> >> It seems that there is no way to set up this number. Ekiga does not ask >> for it ???? >> >> I supose there is a known problem, because I have search a lot, and I >> have find several post in several forums regarding to this issue, but I >> never found an answer ???? neither in forum nor in ekiga documentation. >> That very strange, as far as the post I found are relatively old. >> >> Why nobody has answered this in any forum? It seems like "The mistery of >> ekiga private rooms". >> >> Thanks a lot, sorry if there is a trivial answer to this, but I have >> spent a lot of time searching for a solution before posting. >> > > After doing a little bit of investigation myself as well as some > tinkering, I have found the same unresolved threads as you - so I > believe the situation must be that private conference rooms do not work > as presently documented on the Wiki, or do not work at all. > > Eugen et al, this is something we can get some confirmation on so I can > update the documentation accordingly, as it's confusing for users :) I do not know anything about these rooms. I searched a bit for asterisk rooms too, without success. I commented out this info on wiki page. If someone has such knowledge, please reply. -- Eugen From anto.trande at gmail.com Tue May 17 09:04:15 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 11:04:15 +0200 Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List In-Reply-To: <4DD232D1.4040501@pu-pm.univ-fcomte.fr> References: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> <4DD232D1.4040501@pu-pm.univ-fcomte.fr> Message-ID: mmm If camera is NOT added at list, it may that is NOT tested too. :) 2011/5/17 Eugen Dedu > On 17/05/11 08:47, Dave Koelmeyer wrote: > >> Hi, >> >> We really should include the HCL to include laptops with built-in webcams, >> given >> how popular they now are vs. external webcams. >> >> I've started the ball rolling by adding the Dell Latitude 2100, which I've >> tested with Ekiga under Windows XP: >> >> http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Opti >> Any others, please let me know and I'll add 'em :) >> > > There are many computers out there. I think it is better to add cameras > which do NOT work. What do you think? > > -- > Eugen > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande "Fedora Ambassador" "Fedora Italian Translator" **mail*: mailto:sagitter at fedoraproject.org *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net *Jabber * :sagitter AT jabber.org *GPG Key: CFE3479C** * -------------- next part -------------- An HTML attachment was scrubbed... URL: From jdanharvey at hotmail.com Tue May 17 09:11:50 2011 From: jdanharvey at hotmail.com (John Harvey) Date: Tue, 17 May 2011 05:11:50 -0400 Subject: [Ekiga-list] "Could not connect to remote host" Message-ID: Running Ekiga 3.2.7 on Linux Mint 10 "Julia" 32-bit, when I make a test call to either 500 at ekiga.net or 501 at ekiga.net, I get no ringing and after ~20 seconds, the call terminates with the message "could not connect to remote host". I ran "ekiga -d 4 2>ekiga-output.txt" and tried the test call again. The resulting output report is attached. I have no idea if I have port 5060 forwarded, and I don't have access to the router itself. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ekiga-output.txt.7z Type: application/x-7z-compressed Size: 10138 bytes Desc: not available URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 09:30:33 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 11:30:33 +0200 Subject: [Ekiga-list] socks proxy In-Reply-To: <4DD15F82.90402@aeronetworks.ca> References: <0000174993@mail.aeronetworks.ca> <4DD14BB0.70601@pu-pm.univ-fcomte.fr> <4DD15F82.90402@aeronetworks.ca> Message-ID: <4DD24039.1070602@pu-pm.univ-fcomte.fr> On 16/05/11 19:31, herman wrote: > > On 05/16/2011 08:07 PM, Eugen Dedu wrote: >> >> On 16/05/11 05:19, herman wrote: >>> Hi guys, >>> >>> I googled to no avail. Does anyone have information on how to set up >>> Ekiga >>> to use a Socks proxy? >> >> This is strange, since ptlib has socks support. What >> $ grep SOCKS /usr/lib/pkgconfig/ptlib.pc >> shows in your machine? >> > Pardon, I'm sure it has socks support, I just don't know what syntax to > enter into the proxy setting. I cannot experiment, since I don't have > Ekiga working on my netbook yet. I'm trying to read up on it beforehand. > > How do I tell Ekiga that the proxy is a socks proxy and not some other > sort of proxy: > socks://socks.example.com ??? > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > I see at http://opalvoip.svn.sourceforge.net/viewvc/opalvoip/ptlib/branches/v2_6/src/ptclib/socks.cxx?revision=22107&view=markup that info about the existence of a socks proxy is taken from registry on Windows, HKEY_CURRENT_USER\\Software\\Microsoft\\Windows\\CurrentVersion PString str = config.GetString("Internet Settings", "ProxyServer", ""); Have you set the proxy there? There is no proxy to be set in ekiga. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 09:32:56 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 11:32:56 +0200 Subject: [Ekiga-list] "Could not connect to remote host" In-Reply-To: References: Message-ID: <4DD240C8.3030005@pu-pm.univ-fcomte.fr> On 17/05/11 11:11, John Harvey wrote: > > Running Ekiga 3.2.7 on Linux Mint 10 "Julia" 32-bit, when I make a test call to either 500 at ekiga.net or 501 at ekiga.net, I get no ringing and after ~20 seconds, the call terminates with the message "could not connect to remote host". I ran "ekiga -d 4 2>ekiga-output.txt" and tried the test call again. The resulting output report is attached. I have no idea if I have port 5060 forwarded, and I don't have access to the router itself. This is http://wiki.ekiga.org/index.php/Troubleshooting#I_register.2C_but_the_communication_cannot_be_established Remove some unused codecs from Preferences, such as G726 ones, and retry. -- Eugen From jdanharvey at hotmail.com Tue May 17 09:41:16 2011 From: jdanharvey at hotmail.com (John Harvey) Date: Tue, 17 May 2011 05:41:16 -0400 Subject: [Ekiga-list] "Could not connect to remote host" In-Reply-To: <4DD240C8.3030005@pu-pm.univ-fcomte.fr> References: , <4DD240C8.3030005@pu-pm.univ-fcomte.fr> Message-ID: I got the expected error output, and removing all the G726 codecs fixed the problem. Thanks. > Date: Tue, 17 May 2011 11:32:56 +0200 > From: Eugen.Dedu at pu-pm.univ-fcomte.fr > To: ekiga-list at gnome.org > Subject: Re: [Ekiga-list] "Could not connect to remote host" > > On 17/05/11 11:11, John Harvey wrote: > > > > Running Ekiga 3.2.7 on Linux Mint 10 "Julia" 32-bit, when I make a test call to either 500 at ekiga.net or 501 at ekiga.net, I get no ringing and after ~20 seconds, the call terminates with the message "could not connect to remote host". I ran "ekiga -d 4 2>ekiga-output.txt" and tried the test call again. The resulting output report is attached. I have no idea if I have port 5060 forwarded, and I don't have access to the router itself. > > This is > http://wiki.ekiga.org/index.php/Troubleshooting#I_register.2C_but_the_communication_cannot_be_established > > Remove some unused codecs from Preferences, such as G726 ones, and retry. > > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 09:55:23 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 11:55:23 +0200 Subject: [Ekiga-list] Fedora 15: illegal instruction, core dumped In-Reply-To: <4DCD70D8.3060106@aeronetworks.ca> References: <4DCD499F.6080003@aeronetworks.ca> <4DCD4CB3.3070405@pu-pm.univ-fcomte.fr> <4DCD5E6D.6050806@aeronetworks.ca> <4DCD61F0.6040107@pu-pm.univ-fcomte.fr> <4DCD70D8.3060106@aeronetworks.ca> Message-ID: <4DD2460B.1080206@pu-pm.univ-fcomte.fr> On 13/05/11 19:56, herman wrote: > On 05/13/2011 08:53 PM, Eugen Dedu wrote: >> >> On 13/05/11 18:38, herman wrote: >>> On 05/13/2011 07:22 PM, Eugen Dedu wrote: >>>> >>>> On 13/05/11 17:09, herman wrote: >>>>> >>>>> Hi guys, >>>>> >>>>> Does anyone have Ekiga working on Fedora 15? >>>> >>>> Strange... Could you give us the backtrace? >>>> >>> >>> First I tried the regular version, then I tried the testing version, >>> then I tried to compile it from source: >>> >>> So, I tried an update from the testing repos: >>> # yum remove ekiga >>> # yum install ekiga --enablerepo=updates-testing >>> >>> Then I ran it with: >>> $ ekiga -d 4 >>> >>> Much patience is required, since it takes a heckavalongtime to start up, >>> testing the NAT firewall and connection to ekiga.net >> >> The long wait for starting up is surely because of your DNS. There is >> a patch, but it works only on development version of ekiga... >> >>> It eventually comes, up, turns grey immediately and, wait for it, drum >>> roll... >>> Illegal instruction (core dumped) >>> >>> Bleh... >>> >>> So, I'm back to trying to figure out how to compile and install it from >>> source. >>> >>> ---------- Post added at 03:30 PM ---------- Previous post was at 01:13 >>> PM ---------- >>> >>> Sooooooooooo.... >>> $ tar -zxvf ptlib-2.6.7.tar.gz >>> $ tar -zxvf opal-3.6.8.tar.gz >>> $ tar -zxvf ekiga-3.2.7.tar.gz >>> >>> $ cd pt[tab] >>> $ make clean >>> $ ./configure --prefix=/usr >>> $ make >>> $ su >>> # make install >>> # exit >>> >>> Rinse and repeat... >>> >>> ...and: >>> /usr/include/ffmpeg/libavutil/common.h:165:47: error: 'UINT64_C' was not >>> declared in this scope >>> make[2]: *** [obj/h263-1998.o] Error 1 >> >> There are some problems with such non-free codecs. Until they get >> fixed, I propose you to just remove plugins/video/H.263-1998 from opal. >> >>> --- >>> Now I installed the regular version again, and ran it with -d 4: >>> [herman at leo ~]$ ekiga -d 1 >> [...] >>> write PDU to closed transport >>> udp$86.64.162.35:5060 >>> Segmentation fault (core dumped) >> >> Please use it inside gdb, as shown at >> http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_stack_backtrace_from_a_crash_or_freeze > OK, the trace is attached. Hope it helps! It helps, but is not sufficient :o) It is the same crash as https://bugs.launchpad.net/ubuntu/+source/ekiga/+bug/375725. It is a bug in opal. Unfortunately, opal version used by ekiga 3.2.7 is too old, hence its developers do not work on it anymore. I am sorry, but the only solution I see is that you wait a few days, when I can propose you to use the new ekiga release, 3.3.1. If I do not reply this week, come back to me. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 10:00:00 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 12:00:00 +0200 Subject: [Ekiga-list] Connecting to Ekiga.net from non-Ekiga SIP clients In-Reply-To: <4DD12F0C.4000902@me.com> References: <4DD12F0C.4000902@me.com> Message-ID: <4DD24720.3090009@pu-pm.univ-fcomte.fr> On 16/05/11 16:05, Dave Koelmeyer wrote: > Hi All, > > While reading through the H-Online article I posted recently, they made > reference to this: > > http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net I found this explanation very clear!! > I'm not au fait with the technical reasons for this, but is this an > issue which could be resolved? > > At the very least this should probably be signposted a bit more > prominently on the Wiki or similar, as those not aware of this issue > could be trying to connect to Ekiga.net from the Mac OS platform using > Blink for example, to chat with Ekiga.net users using the actual Ekiga > client on supported platforms, only to not have it work for no apparent > reason. Yes, I think the best place is at http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription -- Eugen From anto.trande at gmail.com Tue May 17 10:33:41 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 12:33:41 +0200 Subject: [Ekiga-list] chat Message-ID: If try to send a textual message to another acconut, the phrase doesn't seem to be displayed. PS. Screenshot on attachment. -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screenshot-26.png Type: image/png Size: 16146 bytes Desc: not available URL: From lars.nooden at gmail.com Tue May 17 10:36:49 2011 From: lars.nooden at gmail.com (=?ISO-8859-1?Q?Lars_Nood=E9n?=) Date: Tue, 17 May 2011 13:36:49 +0300 Subject: [Ekiga-list] Private conferences Message-ID: <4DD24FC1.4080007@gmail.com> When connecting to conference rooms (501xxxx at ekiga.net), I was expecting to be prompted for a PIN. How do I enable a private conference on Ekiga.net? /Lars Nooden "... each subsidiary should have method to track Linux threats and that these should be reported back to Redmond..." p 10. Plaintiff's Exhibit 8592 http://groklaw.net/pdf/iowa/www.iowaconsumercase.org/011607/8000/PX08592.pdf From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 10:37:20 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 12:37:20 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: Message-ID: <4DD24FE0.3060506@pu-pm.univ-fcomte.fr> On 17/05/11 12:33, Antonio Trande wrote: > If try to send a textual message to another acconut, the phrase doesn't seem > to be displayed. What ekiga version do you use? Send us -d 4 output please. -- Eugen From anto.trande at gmail.com Tue May 17 10:54:31 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 12:54:31 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD24FE0.3060506@pu-pm.univ-fcomte.fr> References: <4DD24FE0.3060506@pu-pm.univ-fcomte.fr> Message-ID: Ekiga 3.3.0 . Happen with Ekiga 3.2.6 too. 2011/5/17 Eugen Dedu > On 17/05/11 12:33, Antonio Trande wrote: > >> If try to send a textual message to another acconut, the phrase doesn't >> seem >> to be displayed. >> > > What ekiga version do you use? Send us -d 4 output please. > > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: output.txt.tar.gz Type: application/x-gzip Size: 18259 bytes Desc: not available URL: From davekoelmeyer at me.com Tue May 17 12:16:05 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Wed, 18 May 2011 00:16:05 +1200 Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List In-Reply-To: References: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> <4DD232D1.4040501@pu-pm.univ-fcomte.fr> Message-ID: <4DD26705.6030506@me.com> 2011/5/17 Eugen Dedu > > > On 17/05/11 08:47, Dave Koelmeyer wrote: > > Hi, > > We really should include the HCL to include laptops with > built-in webcams, given > how popular they now are vs. external webcams. > > I've started the ball rolling by adding the Dell Latitude > 2100, which I've > tested with Ekiga under Windows XP: > > http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Opti > Any others, please let me know and I'll add 'em :) > > > There are many computers out there. I think it is better to add > cameras which do NOT work. What do you think? > > -- > Eugen > Hi Eugen, I would agree with Antonio in that it would be more helpful to be explicit about which laptop camera devices work or do not work. Another reason is that it's nice to have an HCL with up-to-date information based on community feedback (the existing webcams are all rather old models), as it's a positive way to show prospective users that it's an active, thriving project :) Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 12:34:27 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 14:34:27 +0200 Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List In-Reply-To: <4DD26705.6030506@me.com> References: <94c8634e-fa7c-46ee-ea73-b45a83424637@me.com> <4DD232D1.4040501@pu-pm.univ-fcomte.fr> <4DD26705.6030506@me.com> Message-ID: <4DD26B53.2030003@pu-pm.univ-fcomte.fr> On 17/05/11 14:16, Dave Koelmeyer wrote: > 2011/5/17 Eugen Dedu > >> >> On 17/05/11 08:47, Dave Koelmeyer wrote: >> >> Hi, >> >> We really should include the HCL to include laptops with >> built-in webcams, given >> how popular they now are vs. external webcams. >> >> I've started the ball rolling by adding the Dell Latitude >> 2100, which I've >> tested with Ekiga under Windows XP: >> >> http://wiki.ekiga.org/index.php/Tested_hardware#Cameras_.28Opti >> >> Any others, please let me know and I'll add 'em :) >> >> >> There are many computers out there. I think it is better to add >> cameras which do NOT work. What do you think? >> >> -- Eugen >> > > Hi Eugen, > > I would agree with Antonio in that it would be more helpful to be > explicit about which laptop camera devices work or do not work. Another > reason is that it's nice to have an HCL with up-to-date information > based on community feedback (the existing webcams are all rather old > models), as it's a positive way to show prospective users that it's an > active, thriving project :) Ok... I put mine on the Web page. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 13:22:18 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 15:22:18 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: Message-ID: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> On 17/05/11 12:33, Antonio Trande wrote: > If try to send a textual message to another acconut, the phrase doesn't seem > to be displayed. > > PS. Screenshot on attachment. Trace does not show any message sent. The problem is that when you type ENTER, ekiga does not see it: the cursor is on the second line. Have you modified ENTER key? What gdk and gtk do you use? -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 13:23:09 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 15:23:09 +0200 Subject: [Ekiga-list] Private conferences In-Reply-To: <4DD24FC1.4080007@gmail.com> References: <4DD24FC1.4080007@gmail.com> Message-ID: <4DD276BD.4030502@pu-pm.univ-fcomte.fr> On 17/05/11 12:36, Lars Nood?n wrote: > When connecting to conference rooms (501xxxx at ekiga.net), I was expecting > to be prompted for a PIN. How do I enable a private conference on > Ekiga.net? I do not know, sorry. -- Eugen From anto.trande at gmail.com Tue May 17 13:29:24 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 15:29:24 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> Message-ID: 2011/5/17 Eugen Dedu > On 17/05/11 12:33, Antonio Trande wrote: > >> If try to send a textual message to another acconut, the phrase doesn't >> seem >> to be displayed. >> >> PS. Screenshot on attachment. >> > > Trace does not show any message sent. The problem is that when you type > ENTER, ekiga does not see it: the cursor is on the second line. > > Have you modified ENTER key? What gdk and gtk do you use? No, absolutely. I use gtk. *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From anto.trande at gmail.com Tue May 17 13:37:23 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 15:37:23 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> Message-ID: gtk3-3.0.9-1 gdk-pixbuf2-2.23.3-1.fc15.x86_64 2011/5/17 Antonio Trande > > > 2011/5/17 Eugen Dedu > >> On 17/05/11 12:33, Antonio Trande wrote: >> >>> If try to send a textual message to another acconut, the phrase doesn't >>> seem >>> to be displayed. >>> >>> PS. Screenshot on attachment. >>> >> >> Trace does not show any message sent. The problem is that when you type >> ENTER, ekiga does not see it: the cursor is on the second line. >> >> Have you modified ENTER key? What gdk and gtk do you use? > > > No, absolutely. > I use gtk. > > > > *Antonio Trande > > > * > *Homepage*: http://www.computer-legacy.net > *Sip Address* : sip:sagitter AT ekiga.net > * > * > * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 13:46:01 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 15:46:01 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> Message-ID: <4DD27C19.8030309@pu-pm.univ-fcomte.fr> On 17/05/11 15:37, Antonio Trande wrote: > gtk3-3.0.9-1 > gdk-pixbuf2-2.23.3-1.fc15.x86_64 > > 2011/5/17 Antonio Trande > >> >> >> 2011/5/17 Eugen Dedu >> >>> On 17/05/11 12:33, Antonio Trande wrote: >>> >>>> If try to send a textual message to another acconut, the phrase doesn't >>>> seem >>>> to be displayed. >>>> >>>> PS. Screenshot on attachment. >>>> >>> >>> Trace does not show any message sent. The problem is that when you type >>> ENTER, ekiga does not see it: the cursor is on the second line. >>> >>> Have you modified ENTER key? What gdk and gtk do you use? >> >> >> No, absolutely. >> I use gtk. Ok. I think you have to wait a bit, we are preparing a GTK3 port, and probably we will see that the ENTER key should be treated differently. Recall us in let's say 10 days. (If you are ready to compile ekiga yourself, I can tell you a modification to try.) -- Eugen From anto.trande at gmail.com Tue May 17 14:00:42 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 16:00:42 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD27C19.8030309@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> Message-ID: > > Ok. I think you have to wait a bit, we are preparing a GTK3 port, and > probably we will see that the ENTER key should be treated differently. > Recall us in let's say 10 days. > > OK (If you are ready to compile ekiga yourself, I can tell you a modification > to try.) > Sure! -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 17 14:10:41 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 17 May 2011 16:10:41 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> Message-ID: <4DD281E1.1050300@pu-pm.univ-fcomte.fr> On 17/05/11 16:00, Antonio Trande wrote: >> >> Ok. I think you have to wait a bit, we are preparing a GTK3 port, and >> probably we will see that the ENTER key should be treated differently. >> Recall us in let's say 10 days. >> >> > OK > > (If you are ready to compile ekiga yourself, I can tell you a modification >> to try.) >> > > Sure! Well, install ptlib and opal development packages, get ekiga 3.2.6 sources and compile it and execute it. Once it works, I will tell you where to add a few lines of code (function message_activated_cb in lib/engine/gui/gtk-frontend/chat-area.cpp). If you run into troubles, it is better to wait until we check it ourselves... -- Eugen From anto.trande at gmail.com Tue May 17 18:15:26 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Tue, 17 May 2011 20:15:26 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD281E1.1050300@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> Message-ID: Ok, compiling Ekiga 3.2.6 after* $ ./configure --prefix=/usr *command*: * > > *================ Final configuration ===================* > * Installing into prefix : /usr* > > * GNOME support : unneeded* > * GConf support : enabled* > * Evolution-Data-Server support : enabled* > * NOTIFY support : enabled* > * LDAP support : enabled* > > * XVideo support : enabled* > > * H.323 support : yes* > > * DBUS support : enabled* > * DBUS service support : enabled* > * mDNS/DNS-SD support : enabled* > > *The following features are experimental -- you've been warned:* > * GStreamer support : disabled* > * KAddressBook support : disabled* > * KDE support : disabled* > * XCAP support : disabled* > > * OS Type : linux-gnu* > * Machine Type : i686* > * Byte Order : little endian* > > * If all settings are OK, type make and make install * > *=======================================================* > * $ make *command fails with error: In file included from /usr/include/libnotify/notify.h:28:0, > from > ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: > /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: File o > directory non esistente > compilation terminated. > Is this the problem that cause chat malfunctioning ? Thanks. -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From drmesmith at yahoo.com Wed May 18 01:04:47 2011 From: drmesmith at yahoo.com (Mark Smith) Date: Tue, 17 May 2011 20:04:47 -0500 Subject: [Ekiga-list] ekiga behind two routers Message-ID: <4DD31B2F.4040101@yahoo.com> I have an ooma telo connected directly to the internet and a d-link dir-601 router connected to the ooma telo. I can't get ekiga to work behind this combination. I have tried port forwarding in the d-link router and in the ooma telo. Is it possible to get ekiga to work behind two nat routers and how do you do it? From stuart at gathman.org Wed May 18 02:09:05 2011 From: stuart at gathman.org (Stuart Gathman) Date: Tue, 17 May 2011 22:09:05 -0400 Subject: [Ekiga-list] ekiga behind two routers In-Reply-To: <4DD31B2F.4040101@yahoo.com> References: <4DD31B2F.4040101@yahoo.com> Message-ID: <4DD32A41.2050703@gathman.org> On 05/17/2011 09:04 PM, Mark Smith wrote: > I have an ooma telo connected directly to the internet and a d-link > dir-601 router connected to the ooma telo. I can't get ekiga to work > behind this combination. I have tried port forwarding in the d-link > router and in the ooma telo. Is it possible to get ekiga to work > behind two nat routers and how do you do it? STUN does not work in this situation - because the STUN is too smart for its own good (or maybe the S stands for Stupid). You would think a broker for a STUN-like protocol would simply pass on the public IP and ports seen by the broker - but maybe I'm missing something. You cannot use ekiga.net, because it requires STUN, and also barfs on private IPs in the SIP trace headers (which I understand is an RFC violation - it is supposed to ignore them). Port forwarding on both routers would work with normal STUN, but fails for ekiga.net because of the 2nd problem. I have 2 routers at home to isolate the WAP from the home LAN. However, I turn off "network detection" (STUN), and use Ekiga just fine with aptela.com, and diamondcard.us (ekiga callout). These service do not require STUN. I connect to family and friends by running openvpn - and ekiga works fine over a VPN. This also solves the lack of SRTP support in ekiga. (Your contact has to be connected to your VPN also.) I think that the ultimate solution is getting (you and your contacts) on IP6. Then all the NAT problems go away. From davekoelmeyer at me.com Wed May 18 06:32:42 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Wed, 18 May 2011 06:32:42 +0000 (GMT) Subject: [Ekiga-list] Laptop webcams on the Ekiga Hardware Compatibility List In-Reply-To: Message-ID: On 17 May, 2011,at 08:10 PM, Antonio Trande wrote: > Sure! > > Webcam on my Acer Aspire 6930G with Fedora Linux (14 / 15) and RHEL6, works fine. > I'm using Ekiga 3.2.6/ Ekiga 3.3.0. > Added - thanks! :) Cheers, Dave Koelmeyer? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 18 09:23:44 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 18 May 2011 11:23:44 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> Message-ID: <4DD39020.1040703@pu-pm.univ-fcomte.fr> On 17/05/11 20:15, Antonio Trande wrote: > Ok, compiling Ekiga 3.2.6 after* $ ./configure --prefix=/usr *command*: > > * >> >> *================ Final configuration ===================* >> * Installing into prefix : /usr* >> >> * GNOME support : unneeded* >> * GConf support : enabled* >> * Evolution-Data-Server support : enabled* >> * NOTIFY support : enabled* >> * LDAP support : enabled* >> >> * XVideo support : enabled* >> >> * H.323 support : yes* >> >> * DBUS support : enabled* >> * DBUS service support : enabled* >> * mDNS/DNS-SD support : enabled* >> >> *The following features are experimental -- you've been warned:* >> * GStreamer support : disabled* >> * KAddressBook support : disabled* >> * KDE support : disabled* >> * XCAP support : disabled* >> >> * OS Type : linux-gnu* >> * Machine Type : i686* >> * Byte Order : little endian* >> >> * If all settings are OK, type make and make install * >> *=======================================================* >> > > * $ make *command fails with error: > > In file included from /usr/include/libnotify/notify.h:28:0, >> from >> ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: File o >> directory non esistente >> compilation terminated. >> > > Is this the problem that cause chat malfunctioning ? No. This is another problem, introduced recently. I will re-compile it myself, to see where the problem lies. Please wait. -- Eugen From herman at aeronetworks.ca Wed May 18 09:59:12 2011 From: herman at aeronetworks.ca (herman) Date: Wed, 18 May 2011 02:59:12 -0700 Subject: [Ekiga-list] chat References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> Message-ID: <4DD39870.506@aeronetworks.ca> On 05/18/2011 01:23 PM, Eugen Dedu wrote: > > On 17/05/11 20:15, Antonio Trande wrote: >> Ok, compiling Ekiga 3.2.6 after* $ ./configure --prefix=/usr *command*: >> >> * >>> >>> *================ Final configuration ===================* >>> * Installing into prefix : /usr* >>> >>> * GNOME support : unneeded* >>> * GConf support : enabled* >>> * Evolution-Data-Server support : enabled* >>> * NOTIFY support : enabled* >>> * LDAP support : enabled* >>> >>> * XVideo support : enabled* >>> >>> * H.323 support : yes* >>> >>> * DBUS support : enabled* >>> * DBUS service support : enabled* >>> * mDNS/DNS-SD support : enabled* >>> >>> *The following features are experimental -- you've been warned:* >>> * GStreamer support : disabled* >>> * KAddressBook support : disabled* >>> * KDE support : disabled* >>> * XCAP support : disabled* >>> >>> * OS Type : linux-gnu* >>> * Machine Type : i686* >>> * Byte Order : little endian* >>> >>> * If all settings are OK, type make and make install * >>> *=======================================================* >>> >> >> * $ make *command fails with error: >> >> In file included from /usr/include/libnotify/notify.h:28:0, >>> from >>> ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >>> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: >>> File o >>> directory non esistente >>> compilation terminated. >>> >> >> Is this the problem that cause chat malfunctioning ? > > No. This is another problem, introduced recently. I will re-compile > it myself, to see where the problem lies. Please wait. > In the Makefile, GTK_CFLAGS is missing from the libnotify-main.lo stanza: libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 18 10:15:07 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 18 May 2011 12:15:07 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD39870.506@aeronetworks.ca> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> Message-ID: <4DD39C2B.90902@pu-pm.univ-fcomte.fr> On 18/05/11 11:59, herman wrote: > > On 05/18/2011 01:23 PM, Eugen Dedu wrote: >> >> On 17/05/11 20:15, Antonio Trande wrote: >>> Ok, compiling Ekiga 3.2.6 after* $ ./configure --prefix=/usr *command*: >>> >>> * >>>> >>>> *================ Final configuration ===================* >>>> * Installing into prefix : /usr* >>>> >>>> * GNOME support : unneeded* >>>> * GConf support : enabled* >>>> * Evolution-Data-Server support : enabled* >>>> * NOTIFY support : enabled* >>>> * LDAP support : enabled* >>>> >>>> * XVideo support : enabled* >>>> >>>> * H.323 support : yes* >>>> >>>> * DBUS support : enabled* >>>> * DBUS service support : enabled* >>>> * mDNS/DNS-SD support : enabled* >>>> >>>> *The following features are experimental -- you've been warned:* >>>> * GStreamer support : disabled* >>>> * KAddressBook support : disabled* >>>> * KDE support : disabled* >>>> * XCAP support : disabled* >>>> >>>> * OS Type : linux-gnu* >>>> * Machine Type : i686* >>>> * Byte Order : little endian* >>>> >>>> * If all settings are OK, type make and make install * >>>> *=======================================================* >>>> >>> >>> * $ make *command fails with error: >>> >>> In file included from /usr/include/libnotify/notify.h:28:0, >>>> from >>>> ../../../../lib/engine/components/libnotify/libnotify-main.cpp:41: >>>> /usr/include/libnotify/notification.h:28:21: fatal error: gtk/gtk.h: >>>> File o >>>> directory non esistente >>>> compilation terminated. >>>> >>> >>> Is this the problem that cause chat malfunctioning ? >> >> No. This is another problem, introduced recently. I will re-compile it >> myself, to see where the problem lies. Please wait. >> > In the Makefile, GTK_CFLAGS is missing from the libnotify-main.lo stanza: > libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp > $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile > $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) > $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) Indeed. This is because libnotify devs removed this -I flag with libnotify 0.7.2 (see http://git.gnome.org/browse/libnotify/commit/?id=0eb56b2f) in order to allow it to be compiled with applications using gtk3, and also with application using gtk2 (they use different -I flag). I will add it to Makefile. -- Eugen From anto.trande at gmail.com Wed May 18 10:32:26 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Wed, 18 May 2011 12:32:26 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD39C2B.90902@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> Message-ID: Therefore, shall i add *$(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) *into *make file* before to start compiling ?* * > > Indeed. This is because libnotify devs removed this -I flag with libnotify > 0.7.2 (see http://git.gnome.org/browse/libnotify/commit/?id=0eb56b2f) in > order to allow it to be compiled with applications using gtk3, and also with > application using gtk2 (they use different -I flag). > -- > Eugen > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From herman at aeronetworks.ca Wed May 18 10:57:00 2011 From: herman at aeronetworks.ca (herman) Date: Wed, 18 May 2011 03:57:00 -0700 Subject: [Ekiga-list] chat References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> Message-ID: <4DD3A5FC.8080607@aeronetworks.ca> On 05/18/2011 02:32 PM, Antonio Trande wrote: > Therefore, shall i add > > *$(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) > --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) > $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) > > *into /make file/ before to start compiling ?* > > * > > Indeed. This is because libnotify devs removed this -I flag with > libnotify 0.7.2 (see > http://git.gnome.org/browse/libnotify/commit/?id=0eb56b2f) in > order to allow it to be compiled with applications using gtk3, and > also with application using gtk2 (they use different -I flag). > > -- > Eugen > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > -- > *Antonio Trande > * > *Homepage*: http://www.computer-legacy.net > > *Sip Address* : sip:sagitter AT ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list In file: lib/engine/components/libnotify/Makefile, add GTK_CFLAGS like this: libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) $(GTK_CFLAGS) Then it should compile. -------------- next part -------------- An HTML attachment was scrubbed... URL: From anto.trande at gmail.com Wed May 18 11:19:17 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Wed, 18 May 2011 13:19:17 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD3A5FC.8080607@aeronetworks.ca> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> Message-ID: Same error. make file is attachment. 2011/5/18 herman > On 05/18/2011 02:32 PM, Antonio Trande wrote: > > Therefore, shall i add > > *$(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile > $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) > $(AM_CXXFLAGS) $(CXXFLAGS) > > *into *make file* before to start compiling ?* > > * > > Indeed. This is because libnotify devs removed this -I flag with libnotify > 0.7.2 (see http://git.gnome.org/browse/libnotify/commit/?id=0eb56b2f) in > order to allow it to be compiled with applications using gtk3, and also with > application using gtk2 (they use different -I flag). > > -- > Eugen > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > -- > *Antonio Trande > * > *Homepage*: http://www.computer-legacy.net > *Sip Address* : sip:sagitter AT ekiga.net > > > _______________________________________________ > ekiga-list mailing listekiga-list at gnome.orghttp://mail.gnome.org/mailman/listinfo/ekiga-list > > In file: lib/engine/components/libnotify/Makefile, add GTK_CFLAGS like > this: > libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp > $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile > $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) > $(AM_CXXFLAGS) $(CXXFLAGS) $(GTK_CFLAGS) > > Then it should compile. > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande "Fedora Ambassador" "Fedora Italian Translator" **mail*: mailto:sagitter at fedoraproject.org *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net *Jabber * :sagitter AT jabber.org *GPG Key: CFE3479C** * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Makefile Type: application/octet-stream Size: 20802 bytes Desc: not available URL: From Bart.Vandewoestyne at telenet.be Wed May 18 11:53:04 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Wed, 18 May 2011 13:53:04 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client Message-ID: <20110518115304.GA4163@simba> Hello all, I'm trying to use the native Android 2.3.4 SIP client (on my Samsung Google Nexus S) with my Ekiga.net account. Apparently, nothing about it is listed on http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android so I hope I can help here in testing. I tried adding my Ekiga.net account using (in Android) -> Menu -> Settings -> Call settings -> Internet call settings -> Accounts -> Add account There, I add the following info: Username: MyFirstName.MyLastName Password: Server: ekiga.net Set as primary account: selected Under the Optional settings I did not touch anything, so I have Authentication username: Display name: Outbound proxy address: Port number: 5060 Transport type: UDP Send keep-alive: Automatic With these settings, I cannot seem to register myself, I get the error "Primary account. Account registration failed: (Not Acceptable (606)); will try later" Am I doing something wrong here or can the native Android 2.3.4 SIP client not work with Ekiga accounts yet? If not, then maybe somebody can tell me what features are missing in order to get Ekiga up and running, so we can submit a feature request at http://source.android.com/source/report-bugs.html ? Wouldn't that be a nice step forward? Kind regards, Bart -- "Share what you know. Learn what you don't." From thedogfarted at gmail.com Wed May 18 12:35:07 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Wed, 18 May 2011 15:35:07 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110518115304.GA4163@simba> References: <20110518115304.GA4163@simba> Message-ID: Hi, On Wed, May 18, 2011 at 2:53 PM, Bart Vandewoestyne > With these settings, I cannot seem to register myself, I get the > error > > "Primary account. Account registration failed: (Not Acceptable > (606)); will try later" > > > Am I doing something wrong here or can the native Android 2.3.4 > SIP client not work with Ekiga accounts yet? ?If not, then maybe > somebody can tell me what features are missing in order to get > Ekiga up and running, so we can submit a feature request at > http://source.android.com/source/report-bugs.html ? ?Wouldn't > that be a nice step forward? Most likely it is neither you nor the Android SIP client. The ekiga.net server has an overly restrictive configuration, which prevents any sufficiently up-to-date SIP client from registering from behind NAT. There have been numerous posts on the list regarding this. Best -- Ian From Bart.Vandewoestyne at telenet.be Wed May 18 12:46:27 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Wed, 18 May 2011 14:46:27 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: References: <20110518115304.GA4163@simba> Message-ID: <20110518124627.GA4444@simba> On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Ruk???ns wrote: > > Most likely it is neither you nor the Android SIP client. The > ekiga.net server has an overly restrictive configuration, which > prevents any sufficiently up-to-date SIP client from registering from > behind NAT. There have been numerous posts on the list regarding this. Hmm... having googled around a bit, my guess would rather be that i cannot register because the native Android 2.3.4 SIP client seems not to support STUN. Couldn't this be the major problem for me not being able to register instead of an 'overly restrictive configuration' of the ekiga.net server? If others agree that this lack of STUN support is most likely the reason why my registration fails, then it seems like a good idea to vote for http://code.google.com/p/android/issues/detail?id=15685 or maybe even add some comments there. This might speedup the STUN support in the native Android 2.3.4 SIP client, thereby making Ekiga much more accessible to the mobile world... Kind regards, Bart -- "Share what you know. Learn what you don't." From herman at aeronetworks.ca Wed May 18 13:37:17 2011 From: herman at aeronetworks.ca (herman) Date: Wed, 18 May 2011 06:37:17 -0700 Subject: [Ekiga-list] chat References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> Message-ID: <4DD3CB8D.7020204@aeronetworks.ca> On 05/18/2011 03:19 PM, Antonio Trande wrote: > Same error. > make file is attachment. > The Makefile is still wrong. That is why. libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) -MT libnotify-main.lo -MD -MP -MF -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 18 14:06:41 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 18 May 2011 16:06:41 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD3CB8D.7020204@aeronetworks.ca> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> Message-ID: <4DD3D271.5040308@pu-pm.univ-fcomte.fr> On 18/05/11 15:37, herman wrote: > On 05/18/2011 03:19 PM, Antonio Trande wrote: >> Same error. >> make file is attachment. >> > > The Makefile is still wrong. That is why. > > libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp > $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile > $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) > $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) -MT libnotify-main.lo -MD -MP -MF I would say the final solution is the following: in lib/engine/components/libnotify/Makefile.am, replace AM_CXXFLAGS = $(SIGC_CFLAGS) $(NOTIFY_CFLAGS) with AM_CXXFLAGS = $(SIGC_CFLAGS) $(NOTIFY_CFLAGS) $(GTK_CFLAGS) and re-execute everything (./configure and make clean and make). Please try and tell us if it works. -- Eugen From anto.trande at gmail.com Wed May 18 14:16:43 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Wed, 18 May 2011 16:16:43 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD3CB8D.7020204@aeronetworks.ca> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> Message-ID: Ok. Sorry but i'm not expert about it. $ ./configure --prefix=/usr ---> done now, i open *make* file on "*lib/engine/components/libnotify*" directory and at line #372 add *$(GTK_CFLAGS)* libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp > $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) --mode=compile > $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) $(AM_CPPFLAGS) $(CPPFLAGS) > $(AM_CXXFLAGS) $(CXXFLAGS) *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP > -MF $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f > '$(libnotify_dir)/libnotify-main.cpp' || echo > '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp > $(am__mv) $(DEPDIR)/libnotify-main.Tpo $(DEPDIR)/libnotify-main.Plo > Is it correct ? If i run $make, get /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): undefined > reference to symbol 'XGetWindowAttributes' > /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO > /usr/lib/libX11.so.6 so try adding it to the linker command line > /usr/lib/libX11.so.6: could not read symbols: Invalid operation > collect2: ld returned 1 exit status > -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From herman at aeronetworks.ca Wed May 18 16:02:28 2011 From: herman at aeronetworks.ca (herman) Date: Wed, 18 May 2011 09:02:28 -0700 Subject: [Ekiga-list] chat References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> Message-ID: <4DD3ED94.4050006@aeronetworks.ca> On 05/18/2011 06:16 PM, Antonio Trande wrote: > Ok. Sorry but i'm not expert about it. > > $ ./configure --prefix=/usr ---> done > > now, i open /make/ file on "/lib/engine/components/libnotify/" > directory and at line #372 add *$(GTK_CFLAGS)* > > libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp > $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) > --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) > $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) > *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP -MF > $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f > '$(libnotify_dir)/libnotify-main.cpp' || echo > '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp > $(am__mv) $(DEPDIR)/libnotify-main.Tpo > $(DEPDIR)/libnotify-main.Plo > > > Is it correct ? > > > If i run $make, get > > /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): > undefined reference to symbol 'XGetWindowAttributes' > /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO > /usr/lib/libX11.so.6 so try adding it to the linker command line > /usr/lib/libX11.so.6: could not read symbols: Invalid operation > collect2: ld returned 1 exit status > > That was correct and then the thing moved on to the next problem. I think that you need to install the X11-dev packages. -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 18 16:59:57 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 18 May 2011 18:59:57 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD3ED94.4050006@aeronetworks.ca> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> Message-ID: <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> On 18/05/11 18:02, herman wrote: > On 05/18/2011 06:16 PM, Antonio Trande wrote: >> Ok. Sorry but i'm not expert about it. >> >> $ ./configure --prefix=/usr ---> done >> >> now, i open /make/ file on "/lib/engine/components/libnotify/" >> directory and at line #372 add *$(GTK_CFLAGS)* >> >> libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp >> $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) >> --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) >> $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) >> *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP -MF >> $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f >> '$(libnotify_dir)/libnotify-main.cpp' || echo >> '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp >> $(am__mv) $(DEPDIR)/libnotify-main.Tpo >> $(DEPDIR)/libnotify-main.Plo >> >> >> Is it correct ? >> >> >> If i run $make, get >> >> /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): >> undefined reference to symbol 'XGetWindowAttributes' >> /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO >> /usr/lib/libX11.so.6 so try adding it to the linker command line >> /usr/lib/libX11.so.6: could not read symbols: Invalid operation >> collect2: ld returned 1 exit status >> >> > That was correct and then the thing moved on to the next problem. > > I think that you need to install the X11-dev packages. No, you should add -lX11 on the command line which fails, for ex. replace in lib/Makefile: libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ by libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ and re-execute make. -- Eugen From anto.trande at gmail.com Wed May 18 17:22:55 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Wed, 18 May 2011 19:22:55 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> Message-ID: 2011/5/18 Eugen Dedu > On 18/05/11 18:02, herman wrote: > >> On 05/18/2011 06:16 PM, Antonio Trande wrote: >> >>> Ok. Sorry but i'm not expert about it. >>> >>> $ ./configure --prefix=/usr ---> done >>> >>> now, i open /make/ file on "/lib/engine/components/libnotify/" >>> directory and at line #372 add *$(GTK_CFLAGS)* >>> >>> libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp >>> $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) >>> --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) >>> $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) >>> *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP -MF >>> $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f >>> '$(libnotify_dir)/libnotify-main.cpp' || echo >>> '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp >>> $(am__mv) $(DEPDIR)/libnotify-main.Tpo >>> $(DEPDIR)/libnotify-main.Plo >>> >>> >>> Is it correct ? >>> >>> >>> If i run $make, get >>> >>> /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): >>> undefined reference to symbol 'XGetWindowAttributes' >>> /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO >>> /usr/lib/libX11.so.6 so try adding it to the linker command line >>> /usr/lib/libX11.so.6: could not read symbols: Invalid operation >>> collect2: ld returned 1 exit status >>> >>> >>> That was correct and then the thing moved on to the next problem. >> >> I think that you need to install the X11-dev packages. >> > > No, you should add -lX11 on the command line which fails, for ex. replace > in lib/Makefile: > libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ > by > libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ > > and re-execute make. > > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > Don't work. libtool: unrecognized option `-lX11' > In* make* file into */lib *directory, i've changed: libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ ---> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * ** * -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 18 18:29:37 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 18 May 2011 20:29:37 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> Message-ID: <4DD41011.8090508@pu-pm.univ-fcomte.fr> On 18/05/11 19:22, Antonio Trande wrote: > 2011/5/18 Eugen Dedu > >> On 18/05/11 18:02, herman wrote: >> >>> On 05/18/2011 06:16 PM, Antonio Trande wrote: >>> >>>> Ok. Sorry but i'm not expert about it. >>>> >>>> $ ./configure --prefix=/usr ---> done >>>> >>>> now, i open /make/ file on "/lib/engine/components/libnotify/" >>>> directory and at line #372 add *$(GTK_CFLAGS)* >>>> >>>> libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp >>>> $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) >>>> --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) >>>> $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) >>>> *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP -MF >>>> $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f >>>> '$(libnotify_dir)/libnotify-main.cpp' || echo >>>> '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp >>>> $(am__mv) $(DEPDIR)/libnotify-main.Tpo >>>> $(DEPDIR)/libnotify-main.Plo >>>> >>>> >>>> Is it correct ? >>>> >>>> >>>> If i run $make, get >>>> >>>> /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): >>>> undefined reference to symbol 'XGetWindowAttributes' >>>> /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO >>>> /usr/lib/libX11.so.6 so try adding it to the linker command line >>>> /usr/lib/libX11.so.6: could not read symbols: Invalid operation >>>> collect2: ld returned 1 exit status >>>> >>>> >>>> That was correct and then the thing moved on to the next problem. >>> >>> I think that you need to install the X11-dev packages. >>> >> >> No, you should add -lX11 on the command line which fails, for ex. replace >> in lib/Makefile: >> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ >> by >> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ >> >> and re-execute make. >> >> -- >> Eugen >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> > > > Don't work. > > libtool: unrecognized option `-lX11' >> > > In* make* file into */lib *directory, i've changed: > > libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ ---> > libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ Sorry, add -lX11 on the next line instead. -- Eugen From anto.trande at gmail.com Wed May 18 19:03:04 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Wed, 18 May 2011 21:03:04 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD41011.8090508@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> <4DD41011.8090508@pu-pm.univ-fcomte.fr> Message-ID: Another error!* [?][?] /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): undefined reference to symbol 'XShmQueryExtension' /usr/bin/ld: note: 'XShmQueryExtension' is defined in DSO /usr/lib/libXext.so.6 so try adding it to the linker command line /usr/lib/libXext.so.6: could not read symbols: Invalid operation collect2: ld returned 1 exit status* 2011/5/18 Eugen Dedu > On 18/05/11 19:22, Antonio Trande wrote: > >> 2011/5/18 Eugen Dedu >> >> On 18/05/11 18:02, herman wrote: >>> >>> On 05/18/2011 06:16 PM, Antonio Trande wrote: >>>> >>>> Ok. Sorry but i'm not expert about it. >>>>> >>>>> $ ./configure --prefix=/usr ---> done >>>>> >>>>> now, i open /make/ file on "/lib/engine/components/libnotify/" >>>>> directory and at line #372 add *$(GTK_CFLAGS)* >>>>> >>>>> libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp >>>>> $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) >>>>> --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) >>>>> $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) >>>>> *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP -MF >>>>> $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f >>>>> '$(libnotify_dir)/libnotify-main.cpp' || echo >>>>> '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp >>>>> $(am__mv) $(DEPDIR)/libnotify-main.Tpo >>>>> $(DEPDIR)/libnotify-main.Plo >>>>> >>>>> >>>>> Is it correct ? >>>>> >>>>> >>>>> If i run $make, get >>>>> >>>>> /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): >>>>> undefined reference to symbol 'XGetWindowAttributes' >>>>> /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO >>>>> /usr/lib/libX11.so.6 so try adding it to the linker command line >>>>> /usr/lib/libX11.so.6: could not read symbols: Invalid operation >>>>> collect2: ld returned 1 exit status >>>>> >>>>> >>>>> That was correct and then the thing moved on to the next problem. >>>>> >>>> >>>> I think that you need to install the X11-dev packages. >>>> >>>> >>> No, you should add -lX11 on the command line which fails, for ex. replace >>> in lib/Makefile: >>> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ >>> by >>> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ >>> >>> and re-execute make. >>> >>> -- >>> Eugen >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >>> >> >> Don't work. >> >> libtool: unrecognized option `-lX11' >> >>> >>> >> In* make* file into */lib *directory, i've changed: >> >> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ ---> >> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ >> > > Sorry, add -lX11 on the next line instead. > > > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 330.gif Type: image/gif Size: 96 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: 361.gif Type: image/gif Size: 226 bytes Desc: not available URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 18 19:16:06 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 18 May 2011 21:16:06 +0200 Subject: [Ekiga-list] chat In-Reply-To: References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> <4DD41011.8090508@pu-pm.univ-fcomte.fr> Message-ID: <4DD41AF6.70507@pu-pm.univ-fcomte.fr> Add also -lXext On 18/05/11 21:03, Antonio Trande wrote: > Another error!* [?][?] > > /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): undefined > reference to symbol 'XShmQueryExtension' > /usr/bin/ld: note: 'XShmQueryExtension' is defined in DSO > /usr/lib/libXext.so.6 so try adding it to the linker command line > /usr/lib/libXext.so.6: could not read symbols: Invalid operation > collect2: ld returned 1 exit status* > > > 2011/5/18 Eugen Dedu > >> On 18/05/11 19:22, Antonio Trande wrote: >> >>> 2011/5/18 Eugen Dedu >>> >>> On 18/05/11 18:02, herman wrote: >>>> >>>> On 05/18/2011 06:16 PM, Antonio Trande wrote: >>>>> >>>>> Ok. Sorry but i'm not expert about it. >>>>>> >>>>>> $ ./configure --prefix=/usr ---> done >>>>>> >>>>>> now, i open /make/ file on "/lib/engine/components/libnotify/" >>>>>> directory and at line #372 add *$(GTK_CFLAGS)* >>>>>> >>>>>> libnotify-main.lo: $(libnotify_dir)/libnotify-main.cpp >>>>>> $(LIBTOOL) --tag=CXX $(AM_LIBTOOLFLAGS) $(LIBTOOLFLAGS) >>>>>> --mode=compile $(CXX) $(DEFS) $(DEFAULT_INCLUDES) $(INCLUDES) >>>>>> $(AM_CPPFLAGS) $(CPPFLAGS) $(AM_CXXFLAGS) $(CXXFLAGS) >>>>>> *$(GTK_CFLAGS)* -MT libnotify-main.lo -MD -MP -MF >>>>>> $(DEPDIR)/libnotify-main.Tpo -c -o libnotify-main.lo `test -f >>>>>> '$(libnotify_dir)/libnotify-main.cpp' || echo >>>>>> '$(srcdir)/'`$(libnotify_dir)/libnotify-main.cpp >>>>>> $(am__mv) $(DEPDIR)/libnotify-main.Tpo >>>>>> $(DEPDIR)/libnotify-main.Plo >>>>>> >>>>>> >>>>>> Is it correct ? >>>>>> >>>>>> >>>>>> If i run $make, get >>>>>> >>>>>> /usr/bin/ld: ../lib/engine/.libs/libekiga_engine.a(xvwindow.o): >>>>>> undefined reference to symbol 'XGetWindowAttributes' >>>>>> /usr/bin/ld: note: 'XGetWindowAttributes' is defined in DSO >>>>>> /usr/lib/libX11.so.6 so try adding it to the linker command line >>>>>> /usr/lib/libX11.so.6: could not read symbols: Invalid operation >>>>>> collect2: ld returned 1 exit status >>>>>> >>>>>> >>>>>> That was correct and then the thing moved on to the next problem. >>>>>> >>>>> >>>>> I think that you need to install the X11-dev packages. >>>>> >>>>> >>>> No, you should add -lX11 on the command line which fails, for ex. replace >>>> in lib/Makefile: >>>> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ >>>> by >>>> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ >>>> >>>> and re-execute make. >>>> >>>> -- >>>> Eugen >>>> _______________________________________________ >>>> ekiga-list mailing list >>>> ekiga-list at gnome.org >>>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>>> >>>> >>> >>> Don't work. >>> >>> libtool: unrecognized option `-lX11' >>> >>>> >>>> >>> In* make* file into */lib *directory, i've changed: >>> >>> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) \ ---> >>> libekiga_la_LINK = $(LIBTOOL) --tag=CC $(AM_LIBTOOLFLAGS) -lX11 \ >>> >> >> Sorry, add -lX11 on the next line instead. >> >> >> -- >> Eugen >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> > > > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From anto.trande at gmail.com Wed May 18 19:36:00 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Wed, 18 May 2011 21:36:00 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD41AF6.70507@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> <4DD41011.8090508@pu-pm.univ-fcomte.fr> <4DD41AF6.70507@pu-pm.univ-fcomte.fr> Message-ID: OK. Ekiga 3.2.6 has been compiled and installed, but after *#make install*appear ... > > > >> test -z "/usr/share/applications" || /bin/mkdir -p >> "/usr/share/applications" >> /usr/bin/install -c -m 644 ekiga.desktop '/usr/share/applications' >> GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults gconftool-2 >> --makefile-install-rule ekiga.schemas 2>&1 > /dev/null >> gconftool-2 --shutdown >> ** >> GLib-GIO:ERROR:gdbusconnection.c:2270:initable_init: assertion failed: >> (connection->initialization_error == NULL) >> make[2]: *** [install-schemas] Annullato (core dumped) >> make[2]: Leaving directory `/home/toky/Downloads/Scaricati/ekiga-3.2.6' >> make[1]: *** [install-am] Errore 2 >> make[1]: Leaving directory `/home/toky/Downloads/Scaricati/ekiga-3.2.6' >> make: *** [install-recursive] Errore 1 >> > Anyway, Ekiga works !? -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From herman at aeronetworks.ca Wed May 18 20:33:02 2011 From: herman at aeronetworks.ca (herman) Date: Wed, 18 May 2011 13:33:02 -0700 Subject: [Ekiga-list] chat References: <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> <4DD41011.8090508@pu-pm.univ-fcomte.fr> <4DD41AF6.70507@pu-pm.univ-fcomte.fr> Message-ID: <4DD42CFE.9010908@aeronetworks.ca> On 05/18/2011 11:36 PM, Antonio Trande wrote: > OK. > > Ekiga 3.2.6 has been compiled and installed, but after /#make install/ > appear I have also seen this install problem, but on my machine Ekiga doesn't work. After all this same compiling hassle. If it works for you, be happy! -------------- next part -------------- An HTML attachment was scrubbed... URL: From pcgodshall at gmail.com Wed May 18 21:13:51 2011 From: pcgodshall at gmail.com (Paul & Cathy Godshall) Date: Wed, 18 May 2011 17:13:51 -0400 Subject: [Ekiga-list] chat In-Reply-To: <4DD42CFE.9010908@aeronetworks.ca> References: <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> <4DD41011.8090508@pu-pm.univ-fcomte.fr> <4DD41AF6.70507@pu-pm.univ-fcomte.fr> <4DD42CFE.9010908@aeronetworks.ca> Message-ID: unsubscribe, please On Wed, May 18, 2011 at 4:33 PM, herman wrote: > On 05/18/2011 11:36 PM, Antonio Trande wrote: > > OK. > > Ekiga 3.2.6 has been compiled and installed, but after *#make install*appear > > I have also seen this install problem, but on my machine Ekiga doesn't > work. After all this same compiling hassle. If it works for you, be happy! > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedogfarted at gmail.com Wed May 18 21:31:49 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Thu, 19 May 2011 00:31:49 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110518124627.GA4444@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> Message-ID: On Wed, May 18, 2011 at 3:46 PM, Bart Vandewoestyne wrote: > On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Ruk???ns wrote: >> >> Most likely it is neither you nor the Android SIP client. The >> ekiga.net server has an overly restrictive configuration, which >> prevents any sufficiently up-to-date SIP client from registering from >> behind NAT. There have been numerous posts on the list regarding this. > > Hmm... having googled around a bit, my guess would rather be that > i cannot register because the native Android 2.3.4 SIP client > seems not to support STUN. ?Couldn't this be the major problem > for me not being able to register instead of an 'overly > restrictive configuration' of the ekiga.net server? > > If others agree that this lack of STUN support is most likely the > reason why my registration fails, then it seems like a good idea > to vote for Judging from http://www.onsip.com/blog/leo/2011/01/05/our-evaluation-of-android-gingerbreads-native-sip-calling-with-the-nexus-s it seems that the Android SIP client is working fine from behind NAT - the SIP traces show a private IP in Via header, and a public one in Contact. Most likely your registration fails because ekiga.net is apparently configured to require a public IP in both Via and Contact headers. I cannot be 100% sure without seeing the actual SIP messages, but I guess a private IP in Via is why your registration fails. And sending 606 Not Acceptable Anywhere to REGISTER is a violation of the SIP standard on it's own. -- Ian From rowens at ptd.net Wed May 18 22:02:02 2011 From: rowens at ptd.net (Rob Owens) Date: Wed, 18 May 2011 18:02:02 -0400 Subject: [Ekiga-list] ekiga behind two routers In-Reply-To: <4DD32A41.2050703@gathman.org> References: <4DD31B2F.4040101@yahoo.com> <4DD32A41.2050703@gathman.org> Message-ID: <20110518220201.GA7879@aurora.owens.net> On Tue, May 17, 2011 at 10:09:05PM -0400, Stuart Gathman wrote: > On 05/17/2011 09:04 PM, Mark Smith wrote: > > I have an ooma telo connected directly to the internet and a d-link > > dir-601 router connected to the ooma telo. I can't get ekiga to work > > behind this combination. I have tried port forwarding in the d-link > > router and in the ooma telo. Is it possible to get ekiga to work > > behind two nat routers and how do you do it? > STUN does not work in this situation - because the STUN is too smart for > its own good (or maybe the S stands for Stupid). You would think a > broker for a STUN-like protocol would simply pass on the public IP and > ports seen by the broker - but maybe I'm missing something. > > You cannot use ekiga.net, because it requires STUN, and also barfs on > private IPs in the SIP trace headers (which I understand is an RFC > violation - it is supposed to ignore them). Port forwarding on both > routers would work with normal STUN, but fails for ekiga.net because of > the 2nd problem. > > I have 2 routers at home to isolate the WAP from the home LAN. However, > I turn off "network detection" (STUN), and use Ekiga just fine with > aptela.com, and diamondcard.us (ekiga callout). These service do not > require STUN. > iptel.org also does not require STUN. They offer free SIP addresses. -Rob From davekoelmeyer at me.com Wed May 18 22:34:22 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Wed, 18 May 2011 22:34:22 +0000 (GMT) Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: Message-ID: <8c6143f9-5c18-4208-9979-807a21f5ec4f@me.com> On 19 May, 2011,at 12:35 AM, J?nis Ruk??ns wrote: > Hi, > > On Wed, May 18, 2011 at 2:53 PM, Bart Vandewoestyne > > With these settings, I cannot seem to register myself, I get the > > error > > > > "Primary account. Account registration failed: (Not Acceptable > > (606)); will try later" > > > > > > Am I doing something wrong here or can the native Android 2.3.4 > > SIP client not work with Ekiga accounts yet? If not, then maybe > > somebody can tell me what features are missing in order to get > > Ekiga up and running, so we can submit a feature request at > > http://source.android.com/source/report-bugs.html ? Wouldn't > > that be a nice step forward? > > Most likely it is neither you nor the Android SIP client. The > ekiga.net server has an overly restrictive configuration, which > prevents any sufficiently up-to-date SIP client from registering from > behind NAT. There have been numerous posts on the list regarding this. I imagine this isn't a trivial issue to fix, but all the same do we know who looks after Ekiga.net and w?ould this be something that could be addressed? Cheers, Dave -------------- next part -------------- An HTML attachment was scrubbed... URL: From drmesmith at yahoo.com Wed May 18 22:56:49 2011 From: drmesmith at yahoo.com (Mark Smith) Date: Wed, 18 May 2011 17:56:49 -0500 Subject: [Ekiga-list] ekiga behind two routers In-Reply-To: <4DD32A41.2050703@gathman.org> References: <4DD31B2F.4040101@yahoo.com> <4DD32A41.2050703@gathman.org> Message-ID: <4DD44EB1.6060808@yahoo.com> On 05/17/11 21:09, Stuart Gathman wrote: > On 05/17/2011 09:04 PM, Mark Smith wrote: >> I have an ooma telo connected directly to the internet and a d-link >> dir-601 router connected to the ooma telo. I can't get ekiga to work >> behind this combination. I have tried port forwarding in the d-link >> router and in the ooma telo. Is it possible to get ekiga to work >> behind two nat routers and how do you do it? > STUN does not work in this situation - because the STUN is too smart for > its own good (or maybe the S stands for Stupid). You would think a > broker for a STUN-like protocol would simply pass on the public IP and > ports seen by the broker - but maybe I'm missing something. > > You cannot use ekiga.net, because it requires STUN, and also barfs on > private IPs in the SIP trace headers (which I understand is an RFC > violation - it is supposed to ignore them). Port forwarding on both > routers would work with normal STUN, but fails for ekiga.net because of > the 2nd problem. > > I have 2 routers at home to isolate the WAP from the home LAN. However, > I turn off "network detection" (STUN), and use Ekiga just fine with > aptela.com, and diamondcard.us (ekiga callout). These service do not > require STUN. > > I connect to family and friends by running openvpn - and ekiga works > fine over a VPN. This also solves the lack of SRTP support in ekiga. > (Your contact has to be connected to your VPN also.) > > I think that the ultimate solution is getting (you and your contacts) on > IP6. Then all the NAT problems go away. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Thanks for all the good information. Are there any plans to address the problems with ekiga.net? From Bart.Vandewoestyne at telenet.be Thu May 19 07:50:08 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Thu, 19 May 2011 09:50:08 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> Message-ID: <20110519075008.GA9541@simba> On Thu, May 19, 2011 at 12:31:49AM +0300, J??nis Ruk???ns wrote: > > Judging from http://www.onsip.com/blog/leo/2011/01/05/our-evaluation-of-android-gingerbreads-native-sip-calling-with-the-nexus-s > it seems that the Android SIP client is working fine from behind NAT - > the SIP traces show a private IP in Via header, and a public one in > Contact. > > Most likely your registration fails because ekiga.net is apparently > configured to require a public IP in both Via and Contact headers. I > cannot be 100% sure without seeing the actual SIP messages, but I > guess a private IP in Via is why your registration fails. > > And sending 606 Not Acceptable Anywhere to REGISTER is a violation of > the SIP standard on it's own. OK, so if I get things right, there are two possible reasons for me not being able to register with ekiga.net with the native Android 2.3.4 SIP client, namely: 1) it is because the native Android 2.3.4 SIP client does not support a STUN server yet. 2) it is a problem with the ekiga.net server configuration. I would be glad to help out here, but I'm not really sure how I can help. My educated guess is that I should somehow be able to grab the SIP messages from and to my Android phone, but I have no idea how I can do this. I have some basic familiarity with wireshark on Linux, but I have never done packet sniffing on an Android phone. If somebody knows, please let me know how I can get to the real SIP-traffic, so we can diagnose this problem more in depth. Kind regards, Bart -- "Share what you know. Learn what you don't." From anto.trande at gmail.com Thu May 19 09:14:35 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Thu, 19 May 2011 11:14:35 +0200 Subject: [Ekiga-list] chat In-Reply-To: <4DD27C19.8030309@pu-pm.univ-fcomte.fr> References: <4DD2768A.9020400@pu-pm.univ-fcomte.fr> <4DD27C19.8030309@pu-pm.univ-fcomte.fr> Message-ID: Wait your news about GTK3 port in order to put in operation chat. Thank you very much guys! 2011/5/17 Eugen Dedu > On 17/05/11 15:37, Antonio Trande wrote: > >> gtk3-3.0.9-1 >> gdk-pixbuf2-2.23.3-1.fc15.x86_64 >> >> 2011/5/17 Antonio Trande >> >> >>> >>> 2011/5/17 Eugen Dedu >>> >>> On 17/05/11 12:33, Antonio Trande wrote: >>>> >>>> If try to send a textual message to another acconut, the phrase doesn't >>>>> seem >>>>> to be displayed. >>>>> >>>>> PS. Screenshot on attachment. >>>>> >>>>> >>>> Trace does not show any message sent. The problem is that when you type >>>> ENTER, ekiga does not see it: the cursor is on the second line. >>>> >>>> Have you modified ENTER key? What gdk and gtk do you use? >>>> >>> >>> >>> No, absolutely. >>> I use gtk. >>> >> > Ok. I think you have to wait a bit, we are preparing a GTK3 port, and > probably we will see that the ENTER key should be treated differently. > Recall us in let's say 10 days. > > (If you are ready to compile ekiga yourself, I can tell you a modification > to try.) > > > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- *Antonio Trande * *Homepage*: http://www.computer-legacy.net *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Thu May 19 10:26:43 2011 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 19 May 2011 12:26:43 +0200 Subject: [Ekiga-list] ekiga behind two routers In-Reply-To: <4DD44EB1.6060808@yahoo.com> References: <4DD31B2F.4040101@yahoo.com> <4DD32A41.2050703@gathman.org> <4DD44EB1.6060808@yahoo.com> Message-ID: <4DD4F063.9050108@seconix.com> Le 19/05/11 00:56, Mark Smith a ?crit : > On 05/17/11 21:09, Stuart Gathman wrote: >> On 05/17/2011 09:04 PM, Mark Smith wrote: >>> I have an ooma telo connected directly to the internet and a d-link >>> dir-601 router connected to the ooma telo. I can't get ekiga to work >>> behind this combination. I have tried port forwarding in the d-link >>> router and in the ooma telo. Is it possible to get ekiga to work >>> behind two nat routers and how do you do it? >> STUN does not work in this situation - because the STUN is too smart for >> its own good (or maybe the S stands for Stupid). You would think a >> broker for a STUN-like protocol would simply pass on the public IP and >> ports seen by the broker - but maybe I'm missing something. >> >> You cannot use ekiga.net, because it requires STUN, and also barfs on >> private IPs in the SIP trace headers (which I understand is an RFC >> violation - it is supposed to ignore them). Port forwarding on both >> routers would work with normal STUN, but fails for ekiga.net because of >> the 2nd problem. >> >> I have 2 routers at home to isolate the WAP from the home LAN. However, >> I turn off "network detection" (STUN), and use Ekiga just fine with >> aptela.com, and diamondcard.us (ekiga callout). These service do not >> require STUN. >> >> I connect to family and friends by running openvpn - and ekiga works >> fine over a VPN. This also solves the lack of SRTP support in ekiga. >> (Your contact has to be connected to your VPN also.) >> >> I think that the ultimate solution is getting (you and your contacts) on >> IP6. Then all the NAT problems go away. >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list > Thanks for all the good information. Are there any plans to address > the problems with ekiga.net? The problem is that if we do not check for private IP addresses, users will be able to call eachother, but RTP trafic will not go through. That means users will complain of "no audio" problems... Is that preferable ? Damien From anto.trande at gmail.com Thu May 19 13:40:59 2011 From: anto.trande at gmail.com (Antonio Trande) Date: Thu, 19 May 2011 15:40:59 +0200 Subject: [Ekiga-list] Ekiga call: audio/video in jerkily Message-ID: Hi. Calling other account (with test-number doesn't occur) audio is in jerkily. I asked myself if is a insufficient internet band problem. Can you tell me more ? Thanks -- *Antonio Trande * *Sip Address* : sip:sagitter AT ekiga.net * * -------------- next part -------------- An HTML attachment was scrubbed... URL: From LBell at connexsustech.com Thu May 19 13:52:29 2011 From: LBell at connexsustech.com (Lisa Bell) Date: Thu, 19 May 2011 13:52:29 +0000 Subject: [Ekiga-list] chat In-Reply-To: <4DD42CFE.9010908@aeronetworks.ca> References: <4DD27C19.8030309@pu-pm.univ-fcomte.fr> <4DD281E1.1050300@pu-pm.univ-fcomte.fr> <4DD39020.1040703@pu-pm.univ-fcomte.fr> <4DD39870.506@aeronetworks.ca> <4DD39C2B.90902@pu-pm.univ-fcomte.fr> <4DD3A5FC.8080607@aeronetworks.ca> <4DD3CB8D.7020204@aeronetworks.ca> <4DD3ED94.4050006@aeronetworks.ca> <4DD3FB0D.4070000@pu-pm.univ-fcomte.fr> <4DD41011.8090508@pu-pm.univ-fcomte.fr> <4DD41AF6.70507@pu-pm.univ-fcomte.fr> <4DD42CFE.9010908@aeronetworks.ca> Message-ID: <3BC653616CAB1D45BC1A60CD5DF13A760EC27D8B@PRS-Exchange.millmrk.com> How do I STOP getting these emails? I clicked the link and unsubscribed four times. Please take my email off your list. Thank you Lisa From: ekiga-list-bounces at gnome.org [mailto:ekiga-list-bounces at gnome.org] On Behalf Of herman Sent: Wednesday, May 18, 2011 3:33 PM To: ekiga-list at gnome.org Subject: Re: [Ekiga-list] chat On 05/18/2011 11:36 PM, Antonio Trande wrote: OK. Ekiga 3.2.6 has been compiled and installed, but after #make install appear I have also seen this install problem, but on my machine Ekiga doesn't work. After all this same compiling hassle. If it works for you, be happy! -------------- next part -------------- An HTML attachment was scrubbed... URL: From thedogfarted at gmail.com Thu May 19 19:25:40 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Thu, 19 May 2011 22:25:40 +0300 Subject: [Ekiga-list] ekiga behind two routers In-Reply-To: <4DD4F063.9050108@seconix.com> References: <4DD31B2F.4040101@yahoo.com> <4DD32A41.2050703@gathman.org> <4DD44EB1.6060808@yahoo.com> <4DD4F063.9050108@seconix.com> Message-ID: Hello, Damien On Thu, May 19, 2011 at 1:26 PM, Damien Sandras wrote: > The problem is that if we do not check for private IP addresses, users will > be able to call eachother, but RTP trafic will not go through. > > That means users will complain of "no audio" problems... > > Is that preferable ? In my opinion it's better to have "no audio" in some cases rather than not being able to use the service at all. Rejecting private IPs in Contact header is perfectly reasonable (although the response shouldn't be 6xx, but I admit that's nitpicking), but a private IP in Via should be fine. My reasoning is that if the client lists it's public address in Contact, then apparently it *is* employing some kind of NAT traversal, hopefully for RTP as well. Also a private IP in Via allows the server to work around the tricky case of both users being behind the same NAT (the server can send a redirect to the private IP). Thanks, -- Ian From Eugen.Dedu at pu-pm.univ-fcomte.fr Thu May 19 20:10:18 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Thu, 19 May 2011 22:10:18 +0200 Subject: [Ekiga-list] Ekiga call: audio/video in jerkily In-Reply-To: References: Message-ID: <4DD5792A.9010505@pu-pm.univ-fcomte.fr> On 19/05/11 15:40, Antonio Trande wrote: > Hi. > > Calling other account (with test-number doesn't occur) audio is in jerkily. > I asked myself if is a insufficient internet band problem. If with echo number audio is fine and with other numbers audio is not fine, then either the audio codec is not the same (for echo it is PCMA/U), or the network is faulty. Try use Speex 16 or PCMA/U. Try also reduce video resolution, and even check off all video codecs entirely. -- Eugen From Bart.Vandewoestyne at telenet.be Thu May 19 20:48:10 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Thu, 19 May 2011 22:48:10 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110519075008.GA9541@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> Message-ID: <20110519204810.GA13193@simba> On Thu, May 19, 2011 at 09:50:08AM +0200, Bart Vandewoestyne wrote: > > OK, so if I get things right, there are two possible reasons for > me not being able to register with ekiga.net with the native > Android 2.3.4 SIP client, namely: > > 1) it is because the native Android 2.3.4 SIP client does not > support a STUN server yet. > > 2) it is a problem with the ekiga.net server configuration. > > I would be glad to help out here, but I'm not really sure how I > can help. My educated guess is that I should somehow be able to > grab the SIP messages from and to my Android phone, but I have no > idea how I can do this. I have some basic familiarity with > wireshark on Linux, but I have never done packet sniffing on an > Android phone. > > If somebody knows, please let me know how I can get to the real > SIP-traffic, so we can diagnose this problem more in depth. OK. I've played a bit around with tcpdump on my dd-wrt Asus RT-N16 router and this is what I did: * turned off my Android phone * issued the following command: root at asus:~# tcpdump -i eth1 host 192.168.1.138 -w sip_capture.pcap * turned on my Android phone and played a bit around * turned off my android phone * CTRL+C the tcpdump command The output (to be visualised with e.g. wireshark) is here: http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap All I can see is that the following is happening: 1) an UDP packet is being sent to ekiga.net 2) ekiga.net replies with a SIP message 606 Not Acceptable I cannot judge why sending of 1) results in a 606 Acceptable... I hope more experienced people can tell me what's going wrong here: is the problem on my side (not having STUN support) or is the problem on the ekiga.net server side? Kind regards, Bart -- "Share what you know. Learn what you don't." From Eugen.Dedu at pu-pm.univ-fcomte.fr Thu May 19 20:57:11 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Thu, 19 May 2011 22:57:11 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110519204810.GA13193@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> Message-ID: <4DD58427.6020606@pu-pm.univ-fcomte.fr> On 19/05/11 22:48, Bart Vandewoestyne wrote: > On Thu, May 19, 2011 at 09:50:08AM +0200, Bart Vandewoestyne wrote: >> >> OK, so if I get things right, there are two possible reasons for >> me not being able to register with ekiga.net with the native >> Android 2.3.4 SIP client, namely: >> >> 1) it is because the native Android 2.3.4 SIP client does not >> support a STUN server yet. >> >> 2) it is a problem with the ekiga.net server configuration. >> >> I would be glad to help out here, but I'm not really sure how I >> can help. My educated guess is that I should somehow be able to >> grab the SIP messages from and to my Android phone, but I have no >> idea how I can do this. I have some basic familiarity with >> wireshark on Linux, but I have never done packet sniffing on an >> Android phone. >> >> If somebody knows, please let me know how I can get to the real >> SIP-traffic, so we can diagnose this problem more in depth. > > OK. I've played a bit around with tcpdump on my dd-wrt Asus > RT-N16 router and this is what I did: > > * turned off my Android phone > * issued the following command: > root at asus:~# tcpdump -i eth1 host 192.168.1.138 -w sip_capture.pcap > * turned on my Android phone and played a bit around > * turned off my android phone > * CTRL+C the tcpdump command > > The output (to be visualised with e.g. wireshark) is here: > > http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap > > All I can see is that the following is happening: > > 1) an UDP packet is being sent to ekiga.net > 2) ekiga.net replies with a SIP message 606 Not Acceptable There is a problem with your output. Captured packet is truncated to 62 bytes, so the full SIP packet is not shown. Could you retry tcpdump to have full packets in the file? -- Eugen From Bart.Vandewoestyne at telenet.be Thu May 19 21:15:58 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Thu, 19 May 2011 23:15:58 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <4DD58427.6020606@pu-pm.univ-fcomte.fr> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> Message-ID: <20110519211558.GA13495@simba> On Thu, May 19, 2011 at 10:57:11PM +0200, Eugen Dedu wrote: > > There is a problem with your output. Captured packet is truncated > to 62 bytes, so the full SIP packet is not shown. > > Could you retry tcpdump to have full packets in the file? I've updated the file, i think we now have the full information. The new version is at the same url, namely http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap Please let me know if this is enough info to debug my problem. If not, then let me know what to do. I'm glad to be able to help here! Regards, Bart -- "Share what you know. Learn what you don't." From Bart.Vandewoestyne at telenet.be Thu May 19 21:30:49 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Thu, 19 May 2011 23:30:49 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110519211558.GA13495@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> Message-ID: <20110519213049.GB13495@simba> On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote: > > I've updated the file, i think we now have the full information. > The new version is at the same url, namely > > http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap > > Please let me know if this is enough info to debug my problem. > If not, then let me know what to do. I'm glad to be able to help > here! OK. I've done some more searching, and this is what I have so far. If I try with Ekiga on my laptop, then this is how a typical REGISTER message looks like: REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport User-Agent: Ekiga/3.2.7 From: ;tag=282f826b-cb80-e011-82e5-00216b30c960 Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960 at maverick To: Contact: ;q=1, ;q=0.500 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 If I use my Android phone, then i have REGISTER sip:ekiga.net SIP/2.0 Call-ID: 261a54f294918a1eae37a14f2dc7dc89 at 192.168.1.138 CSeq: 8429 REGISTER From: "Bart.Vandewoestyne" ;tag=4156217873 To: "Bart.Vandewoestyne" Via: SIP/2.0/UDP 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Content-Length: 0 The most important differences that I notice are: * Ekiga uses the public WAN address of my router in the Via header, whereas my android phone has the local LAN address and port. * Ekiga uses both the public WAN address and the local LAN address in the Contact header, whereas my Android phone simply sets the '*'-symbol. My question to this list is still the same: Is this a bug or a missing feature (STUN) in the native Android client, or is the problem on the ekiga.net server side? Regards, Bart -- "Share what you know. Learn what you don't." From thedogfarted at gmail.com Thu May 19 22:32:03 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Fri, 20 May 2011 01:32:03 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110519213049.GB13495@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> Message-ID: On Fri, May 20, 2011 at 12:30 AM, Bart Vandewoestyne wrote: > On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote: >> >> I've updated the file, i think we now have the full information. >> The new version is at the same url, namely >> >> http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap >> >> Please let me know if this is enough info to debug my problem. >> If not, then let me know what to do. ?I'm glad to be able to help >> here! > > OK. ?I've done some more searching, and this is what I have so > far. ?If I try with Ekiga on my laptop, then this is how a typical > REGISTER message looks like: > > > REGISTER sip:ekiga.net SIP/2.0 > CSeq: 2 REGISTER > Via: SIP/2.0/UDP 178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport > User-Agent: Ekiga/3.2.7 > From: ;tag=282f826b-cb80-e011-82e5-00216b30c960 > Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960 at maverick > To: > Contact: ;q=1, ;q=0.500 > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > If I use my Android phone, then i have > > > REGISTER sip:ekiga.net SIP/2.0 > Call-ID: 261a54f294918a1eae37a14f2dc7dc89 at 192.168.1.138 > CSeq: 8429 REGISTER > From: "Bart.Vandewoestyne" ;tag=4156217873 > To: "Bart.Vandewoestyne" > Via: SIP/2.0/UDP 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport > Max-Forwards: 70 > User-Agent: SIPAUA/0.1.001 > Contact: * > Expires: 0 > Content-Length: 0 > > > The most important differences that I notice are: > > * Ekiga uses the public WAN address of my router in the Via header, whereas my > ?android phone has the local LAN address and port. > > * Ekiga uses both the public WAN address and the local LAN address in the > ?Contact header, whereas my Android phone simply sets the '*'-symbol. > > My question to this list is still the same: > > Is this a bug or a missing feature (STUN) in the native Android client, or is the problem on the ekiga.net server side? This is something I didn't expect at all - the message your phone sends actually asks ekiga.net to unregister everyone from sip:Bart.Vandewoestyne at ekiga.net. I can only guess why. It could be that the phone is trying to ensure it is only device registered. Whatever the reason, I expected at least two REGISTER messages - the first with the private IP in both Via and Contact (to discover it's public IP), followed by a second one with the public IP in Contact. The unregister could be a bug, but it is also possible that the phone is using it as a way to get the public IP, but doesn't send the second REGISTER because of the 606 error code. -- Ian From Bart.Vandewoestyne at telenet.be Thu May 19 22:56:52 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Fri, 20 May 2011 00:56:52 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> Message-ID: <20110519225652.GA13909@simba> On Fri, May 20, 2011 at 01:32:03AM +0300, J??nis Ruk???ns wrote: > > > If I use my Android phone, then i have > > > > REGISTER sip:ekiga.net SIP/2.0 > > Call-ID: 261a54f294918a1eae37a14f2dc7dc89 at 192.168.1.138 > > CSeq: 8429 REGISTER > > From: "Bart.Vandewoestyne" ;tag=4156217873 > > To: "Bart.Vandewoestyne" > > Via: SIP/2.0/UDP 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport > > Max-Forwards: 70 > > User-Agent: SIPAUA/0.1.001 > > Contact: * > > Expires: 0 > > Content-Length: 0 > > [...] > > This is something I didn't expect at all - the message your phone > sends actually asks ekiga.net to unregister everyone from > sip:Bart.Vandewoestyne at ekiga.net. I can only guess why. I'm not a SIP-protocol expert. Can you explain me how you see this for the above message? Is it because of the asterisk in the Contact header? I have searched, but couldn't find the meaning of the * in the Contact header. > It could be that the phone is trying to ensure it is only > device registered. Whatever the reason, I expected at least > two REGISTER messages - the first with the private IP in both > Via and Contact (to discover it's public IP), followed by a > second one with the public IP in Contact. OK. I'll play a bit more around, getting myself more comfortable with tcpdump and wireshark for my SIP-protocol debugging... > The unregister could be a bug, but it is also possible that the > phone is using it as a way to get the public IP, but doesn't > send the second REGISTER because of the 606 error code. OK. And for as far as I understand it from http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net http://mail.gnome.org/archives/ekiga-list/2010-October/msg00040.html http://mail.gnome.org/archives/ekiga-list/2010-October/msg00041.html ekiga.net should not sent this 606 error, right? So the conclusion is that the problem is actually on the ekiga.net server side and I have to hope that it gets fixed? Regards, Bart -- "Share what you know. Learn what you don't." From Bart.Vandewoestyne at telenet.be Thu May 19 23:02:59 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Fri, 20 May 2011 01:02:59 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <8c6143f9-5c18-4208-9979-807a21f5ec4f@me.com> References: <8c6143f9-5c18-4208-9979-807a21f5ec4f@me.com> Message-ID: <20110519230259.GB13909@simba> On Wed, May 18, 2011 at 10:34:22PM +0000, Dave Koelmeyer wrote: > > >Most likely it is neither you nor the Android SIP client. The > >ekiga.net server has an overly restrictive configuration, which > >prevents any sufficiently up-to-date SIP client from registering from > >behind NAT. There have been numerous posts on the list regarding this. > > I imagine this isn't a trivial issue to fix, but all the same do we know who looks after Ekiga.net and w???ould this be something that could be addressed? > > Cheers, > Dave Dave, According to the info on http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#FAQ it is Damien Sandras who looks after ekiga.net I've searched the mailing list archives for mails from Damien about this issue, but haven't found any the last few months. It would be nice to know what he thinks of the issue in this thread and how it can be fixed... I hope he has the time and is willing to fix it... In my opinion, it would really be a Big step forward for the Open Source VoIP community if the native Android 2.3.4 SIP client could register and work with ekiga.net accounts... Regards, Bart -- "Share what you know. Learn what you don't." From thedogfarted at gmail.com Thu May 19 23:12:16 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Fri, 20 May 2011 02:12:16 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110519230259.GB13909@simba> References: <8c6143f9-5c18-4208-9979-807a21f5ec4f@me.com> <20110519230259.GB13909@simba> Message-ID: On Fri, May 20, 2011 at 2:02 AM, Bart Vandewoestyne wrote: > On Wed, May 18, 2011 at 10:34:22PM +0000, Dave Koelmeyer wrote: >> >> >Most likely it is neither you nor the Android SIP client. The >> >ekiga.net server has an overly restrictive configuration, which >> >prevents any sufficiently up-to-date SIP client from registering from >> >behind NAT. There have been numerous posts on the list regarding this. >> >> I imagine this isn't a trivial issue to fix, but all the same do we know who looks after Ekiga.net and w???ould this be something that could be addressed? >> >> Cheers, >> Dave > > Dave, > > According to the info on > http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#FAQ > it is Damien Sandras who looks after ekiga.net > > I've searched the mailing list archives for mails from Damien > about this issue, but haven't found any the last few months. > > It would be nice to know what he thinks of the issue in this > thread and how it can be fixed... ?I hope he has the time and is > willing to fix it... See http://mail.gnome.org/archives/ekiga-list/2011-May/msg00105.html > In my opinion, it would really be a Big step forward for the Open > Source VoIP community if the native Android 2.3.4 SIP client > could register and work with ekiga.net accounts... Well, I'm not so sure about Android anymore, but removing the private Via restriction would allow sofia-sip based clients (Empathy, Maemo, probably some Nokia phones) to work with ekiga.net -- Ian From thedogfarted at gmail.com Thu May 19 23:45:58 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Fri, 20 May 2011 02:45:58 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110519225652.GA13909@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> Message-ID: On Fri, May 20, 2011 at 1:56 AM, Bart Vandewoestyne wrote: > On Fri, May 20, 2011 at 01:32:03AM +0300, J??nis Ruk???ns wrote: >> >> > If I use my Android phone, then i have >> > >> > REGISTER sip:ekiga.net SIP/2.0 >> > Call-ID: 261a54f294918a1eae37a14f2dc7dc89 at 192.168.1.138 >> > CSeq: 8429 REGISTER >> > From: "Bart.Vandewoestyne" ;tag=4156217873 >> > To: "Bart.Vandewoestyne" >> > Via: SIP/2.0/UDP 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport >> > Max-Forwards: 70 >> > User-Agent: SIPAUA/0.1.001 >> > Contact: * >> > Expires: 0 >> > Content-Length: 0 >> > [...] >> >> This is something I didn't expect at all - the message your phone >> sends actually asks ekiga.net to unregister everyone from >> sip:Bart.Vandewoestyne at ekiga.net. I can only guess why. > > I'm not a SIP-protocol expert. ?Can you explain me how you see > this for the above message? ?Is it because of the asterisk in the > Contact header? ?I have searched, but couldn't find the meaning > of the * in the Contact header. The * in Contact header is allowed only when unregistering (Expires: 0) and means every IP that is currently registered at the particular address in To header. For example, if you have logged in from let's say laptop and work, the above will force both of those clients to log out (given that the server allows it). >> It could be that the phone is trying to ensure it is only >> device registered. ?Whatever the reason, I expected at least >> two REGISTER messages - the first with the private IP in both >> Via and Contact (to discover it's public IP), followed by a >> second one with the public IP in Contact. > > OK. ?I'll play a bit more around, getting myself more comfortable > with tcpdump and wireshark for my SIP-protocol debugging... > >> The unregister could be a bug, but it is also possible that the >> phone is using it as a way to get the public IP, but doesn't >> send the second REGISTER because of the 606 error code. > > OK. ?And for as far as I understand it from > > ?http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net > ?http://mail.gnome.org/archives/ekiga-list/2010-October/msg00040.html > ?http://mail.gnome.org/archives/ekiga-list/2010-October/msg00041.html > > ekiga.net should not sent this 606 error, right? > > So the conclusion is that the problem is actually on the > ekiga.net server side and I have to hope that it gets fixed? I'm not so sure about this particular case anymore (because of the unregister), but in general, yes, it shouldn't. First, 6xx errors are considered "global", and second, it definitely shouldn't give an error on Via. Like I said, the idea is to send the first message to discover one's public address (the server inlcludes it in the response), and then send a second one which should succeed. Keeping the private IP in Via allows some server side tricks to traverse the NAT. If you're willing to experiment, I can give you an access to my own server at work (I'm using it for testing - writing SIP software is what I'm getting paid for). You won't be able to call anyone but at least we'll see if the phone sends the second REGISTER. Let me know if you're up to that, I'll send you the details tomorrow. Cheers -- Ian From dford at ansur.demon.co.uk Wed May 18 14:27:21 2011 From: dford at ansur.demon.co.uk (David Ford) Date: Wed, 18 May 2011 15:27:21 +0100 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110518124627.GA4444@simba> References: <20110518115304.GA4163@simba> <20110518124627.GA4444@simba> Message-ID: <4DD3D749.4000801@ansur.demon.co.uk> On 18/05/11 13:46, Bart Vandewoestyne wrote: > On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Ruk???ns wrote: >> Most likely it is neither you nor the Android SIP client. The >> ekiga.net server has an overly restrictive configuration, which >> prevents any sufficiently up-to-date SIP client from registering from >> behind NAT. There have been numerous posts on the list regarding this. > Hmm... having googled around a bit, my guess would rather be that > i cannot register because the native Android 2.3.4 SIP client > seems not to support STUN. Couldn't this be the major problem > for me not being able to register instead of an 'overly > restrictive configuration' of the ekiga.net server? > > If others agree that this lack of STUN support is most likely the > reason why my registration fails, then it seems like a good idea > to vote for > > http://code.google.com/p/android/issues/detail?id=15685 > > or maybe even add some comments there. This might speedup the > STUN support in the native Android 2.3.4 SIP client, thereby > making Ekiga much more accessible to the mobile world... > > Kind regards, > Bart > STUN is now depreciated - it has been recognised that it really doesn't work very well. David From Bart.Vandewoestyne at telenet.be Fri May 20 08:02:01 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Fri, 20 May 2011 10:02:01 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: References: <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> Message-ID: <20110520080201.GA16495@simba> On Fri, May 20, 2011 at 02:45:58AM +0300, J??nis Ruk???ns wrote: > > [...] > I'm not so sure about this particular case anymore (because of the > unregister), but in general, yes, it shouldn't. First, 6xx errors are > considered "global", and second, it definitely shouldn't give an error > on Via. > > Like I said, the idea is to send the first message to discover one's > public address (the server inlcludes it in the response), and then > send a second one which should succeed. Keeping the private IP in Via > allows some server side tricks to traverse the NAT. > > If you're willing to experiment, I can give you an access to my own > server at work (I'm using it for testing - writing SIP software is > what I'm getting paid for). You won't be able to call anyone but at > least we'll see if the phone sends the second REGISTER. Let me know if > you're up to that, I'll send you the details tomorrow. Nice to hear that people are getting payd for fun jobs like writing SIP software ;-) As for the testing: I also have a SIP account with diamondcard.us and poivy.com and for these accounts I have no problem registering with my Android 2.3.4 phone (not using STUN that is). I've played around with tcpdump and wireshark yesterday evening and iirc this was what was happening with both these accounts: 1) Android phone sends a REGISTER message 2) registrar sends back an error message (something with not authorized or credentials missing or so... if i recall correctly, it was a 401 Unauthorized message...) 3) Android phone sends second REGISTER message, now including some login info (and probably some kind of authentication stuff) 4) registrar sends back 200 OK. This was also from behind my Asus RT-N16 router running dd-wrt. I'm at work now and can't experiment, but I'll make a tcpdump of this flow this evening and put the .pcap file online somewhere. Please be patient for let's say 10 hours ;-) Knowing that these registrations work, confirms my suspision that the problem is really on the ekiga.net server side and not with my phone. From the above, i deduce that one should also be able to make it work *without* a STUN server. Having the STUN support possibility in the Android client would of course also be nice, as that would maybe be a trick to circumvent the ekiga.net server config problem. Damien? What's your opinion on changing the ekiga.net config so that these issues get resolved? Kind regards, Bart -- "Share what you know. Learn what you don't." From ncassanova11 at gmail.com Sun May 22 20:23:08 2011 From: ncassanova11 at gmail.com (Nikolai Cassanova) Date: Sun, 22 May 2011 16:23:08 -0400 Subject: [Ekiga-list] question about sip protection Message-ID: I wanted to know, when we talk through sip protocol, can people over Internet listen to our conversations or are all conversation through sip encrypted and no one over the Internet can get access to conversations. -------------- next part -------------- An HTML attachment was scrubbed... URL: From papillion at gmail.com Sun May 22 20:28:19 2011 From: papillion at gmail.com (Anthony Papillion) Date: Sun, 22 May 2011 15:28:19 -0500 Subject: [Ekiga-list] question about sip protection In-Reply-To: References: Message-ID: I don't believe they are encrypted because there are a few SIP clients that expressly tout that they encrypt. I don't think Ekiga does. Anthony On 5/22/11, Nikolai Cassanova wrote: > I wanted to know, when we talk through sip protocol, can people over > Internet listen to our conversations or are all conversation through sip > encrypted and no one over the Internet can get access to conversations. > -- Sent from my mobile device Anthony Papillion Advanced Data Concepts Get real about your software/web development and IT Services Phone: (918) 919-4624 Does your business need to reduce its phone bill? I can help! Email me and ask me how! From ncassanova11 at gmail.com Sun May 22 20:33:20 2011 From: ncassanova11 at gmail.com (Nikolai Cassanova) Date: Sun, 22 May 2011 16:33:20 -0400 Subject: [Ekiga-list] question about sip protection In-Reply-To: References: Message-ID: Is there anyway an end user such as my self can encrypt my own sip when I talk to family and friends through sip to pots or when they call me from pots to my sip address? On May 22, 2011 4:28 PM, "Anthony Papillion" wrote: > I don't believe they are encrypted because there are a few SIP clients > that expressly tout that they encrypt. I don't think Ekiga does. > > Anthony > > On 5/22/11, Nikolai Cassanova wrote: >> I wanted to know, when we talk through sip protocol, can people over >> Internet listen to our conversations or are all conversation through sip >> encrypted and no one over the Internet can get access to conversations. >> > > -- > Sent from my mobile device > > Anthony Papillion > Advanced Data Concepts > Get real about your software/web development and IT Services > Phone: (918) 919-4624 > > Does your business need to reduce its phone bill? I can help! > Email me and ask me how! > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From papillion at gmail.com Sun May 22 20:50:43 2011 From: papillion at gmail.com (Anthony Papillion) Date: Sun, 22 May 2011 15:50:43 -0500 Subject: [Ekiga-list] question about sip protection In-Reply-To: References: Message-ID: There's no way to encrypt SIP to POTS that I know of since the POTS end doesn't know how to decrypt it. SIP to SIP can be done though. I think SIPCommunicator encrypts IIRC. On 5/22/11, Nikolai Cassanova wrote: > Is there anyway an end user such as my self can encrypt my own sip when I > talk to family and friends through sip to pots or when they call me from > pots to my sip address? > On May 22, 2011 4:28 PM, "Anthony Papillion" wrote: >> I don't believe they are encrypted because there are a few SIP clients >> that expressly tout that they encrypt. I don't think Ekiga does. >> >> Anthony >> >> On 5/22/11, Nikolai Cassanova wrote: >>> I wanted to know, when we talk through sip protocol, can people over >>> Internet listen to our conversations or are all conversation through sip >>> encrypted and no one over the Internet can get access to conversations. >>> >> >> -- >> Sent from my mobile device >> >> Anthony Papillion >> Advanced Data Concepts >> Get real about your software/web development and IT Services >> Phone: (918) 919-4624 >> >> Does your business need to reduce its phone bill? I can help! >> Email me and ask me how! >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Sent from my mobile device Anthony Papillion Advanced Data Concepts Get real about your software/web development and IT Services Phone: (918) 919-4624 Does your business need to reduce its phone bill? I can help! Email me and ask me how! From computer.ted at gmail.com Mon May 23 00:24:50 2011 From: computer.ted at gmail.com (Ted McCune) Date: Sun, 22 May 2011 17:24:50 -0700 Subject: [Ekiga-list] Poor Sound Message-ID: Running Debian 6, Intel HDA onboard audio, ALSA sound system, Ekiga3.2.7, Diamondcard SIP account. When calling phones the person I'm calling says I'm "beeping in and out" and I hear an echo and the sound quality is bad. Everything works perfectly in Skype on the same machine. In the advanced settings there are a ton of codecs and I don't understand any of them or how to use them. I only call land lines so what is the best way to set up the software for landline phones? I just tried Twinkle and it works fine there. Why would Skype and Twinkle work while Ekiga does not? -- Ted McCune -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Mon May 23 01:05:22 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Mon, 23 May 2011 01:05:22 +0000 (GMT) Subject: [Ekiga-list] Poor Sound In-Reply-To: Message-ID: On 23 May, 2011,at 12:24 PM, Ted McCune wrote: > Running Debian 6, Intel HDA onboard audio, ALSA sound system, Ekiga3.2.7, Diamondcard SIP account. > > When calling phones the person I'm calling says I'm "beeping in and out" and I hear an echo and the sound quality is bad. > > Everything works perfectly in Skype on the same machine. > > In the advanced settings there are a ton of codecs and I don't understand any of them or how to use them. Hi Ted, For the sound issue, the first thing I'd suggest is simply making a call to the Ekiga.net echo test service, and see what the sound quality is like there (e.g. does it echo or cut in/out etc.). For the audio codecs, I find it easiest to enable PCMU, PCMA,and Speex only for starters. Cheers, Dave? -------------- next part -------------- An HTML attachment was scrubbed... URL: From computer.ted at gmail.com Mon May 23 01:30:41 2011 From: computer.ted at gmail.com (Ted McCune) Date: Sun, 22 May 2011 18:30:41 -0700 Subject: [Ekiga-list] Poor Sound In-Reply-To: References: Message-ID: Thanks, I'll play around with the codecs. From reading it looks like Speex is probably best for regular phone calls. I've read some about the other codecs and while the specs might interest a software engineer they dont really tell me which is best for what. I suppose most of that is for calling other SIP clients not POTS telephones. On Sun, May 22, 2011 at 6:05 PM, Dave Koelmeyer wrote: > > > On 23 May, 2011,at 12:24 PM, Ted McCune wrote: > > Running Debian 6, Intel HDA onboard audio, ALSA sound system, Ekiga3.2.7, > Diamondcard SIP account. > > When calling phones the person I'm calling says I'm "beeping in and out" > and I hear an echo and the sound quality is bad. > > Everything works perfectly in Skype on the same machine. > > In the advanced settings there are a ton of codecs and I don't understand > any of them or how to use them. > > > > > Hi Ted, > > For the sound issue, the first thing I'd suggest is simply making a call to > the Ekiga.net echo test service, and see what the sound quality is like > there (e.g. does it echo or cut in/out etc.). > > For the audio codecs, I find it easiest to enable PCMU, PCMA,and Speex only > for starters. > > Cheers, > Dave > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Ted McCune -------------- next part -------------- An HTML attachment was scrubbed... URL: From computer.ted at gmail.com Mon May 23 05:10:30 2011 From: computer.ted at gmail.com (Ted McCune) Date: Sun, 22 May 2011 22:10:30 -0700 Subject: [Ekiga-list] Poor Sound Message-ID: Well, I'm thinking it's not the softphones I'm trying to use it's the hotel's terrible wireless connection. I think I'll try this when I get back home on a real Internet connection. Thanks for the help. -- Ted McCune -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Mon May 23 12:35:22 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 24 May 2011 00:35:22 +1200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110520080201.GA16495@simba> References: <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> Message-ID: <4DDA548A.6020307@me.com> On 20/05/11 08:02 PM, Bart Vandewoestyne wrote: > Damien? What's your opinion on changing the ekiga.net config so > that these issues get resolved? > > Kind regards, > Bart My concern is that for the end-user this is undermining the usefulness of Ekiga.net, and therefore adoption of Ekiga as a SIP client. I have tested *four* different Mac OS SIP clients from behind a NAT router, and all four of them cannot and will not connect to Ekiga.net: - Jistsi (aka Sip Communicator) - Telephone - Blink - X-Lite 4 For the end-user, I can easily see this as a case of interoperability with Ekiga users potentially not being worth the effort, so move on to something else. It makes evangelising Ekiga for me (and SIP as an alternative to Skype for example) very challenging, when the promoted back-end service is broken with regards to cross-client interoperability. Some further discussion about this with a view to knowing if it can be resolved would be really useful at this point. -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ From thedogfarted at gmail.com Mon May 23 13:49:42 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Mon, 23 May 2011 16:49:42 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <4DDA548A.6020307@me.com> References: <20110518124627.GA4444@simba> <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <4DDA548A.6020307@me.com> Message-ID: On Mon, May 23, 2011 at 3:35 PM, Dave Koelmeyer wrote: > On 20/05/11 08:02 PM, Bart Vandewoestyne wrote: >> >> Damien? ?What's your opinion on changing the ekiga.net config so >> that these issues get resolved? >> >> Kind regards, >> Bart > > My concern is that for the end-user this is undermining the usefulness of > Ekiga.net, and therefore adoption of Ekiga as a SIP client. I have tested > *four* different Mac OS SIP clients from behind a NAT router, and all four > of them cannot and will not connect to Ekiga.net: > > - Jistsi (aka Sip Communicator) > - Telephone > - Blink > - X-Lite 4 You can add Empathy and Nokia N900 to that list. > For the end-user, I can easily see this as a case of interoperability with > Ekiga users potentially not being worth the effort, so move on to something > else. It makes evangelising Ekiga for me (and SIP as an alternative to Skype > for example) very challenging, when the promoted back-end service is broken > with regards to cross-client interoperability. > > Some further discussion about this with a view to knowing if it can be > resolved would be really useful at this point. Promoting SIP as an alternative to Skype will always be challenging, due to: 1) The large user base of Skype, and different protocols being used. Although there is an official Skype/SIP gateway, it is paid service, buggy and limited in functionality (you cannot simply call any Skype user). 2) NAT issues. In theory they are applying to Skype as well, but by installing Skype you're agreeing that your computer can be used for relaying other users' traffic, something that's not that easy with SIP. Setting up a dedicated server for media relay however can be expensive, and it doesn't scale well. Also I think that the average user's mindset plays a role here. For the non-computer savvy Jane Doe, VoIP and Skype are synonyms, just like PC and Windows, or, until recently, the Internet and IE. People will use whatever comes preinstalled, and one has to convince them that the alternative is significantly better. Of course sub-par services don't do any good here, but in the same time you cannot expect Damien to provide a media relay server, given that the service is gratis. Just my $.02 -- Ian From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 23 18:11:23 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 23 May 2011 20:11:23 +0200 Subject: [Ekiga-list] Poor Sound In-Reply-To: References: Message-ID: <4DDAA34B.30203@pu-pm.univ-fcomte.fr> On 23/05/11 03:05, Dave Koelmeyer wrote: > > > On 23 May, 2011,at 12:24 PM, Ted McCune wrote: > >> Running Debian 6, Intel HDA onboard audio, ALSA sound system, Ekiga3.2.7, >> Diamondcard SIP account. >> >> When calling phones the person I'm calling says I'm "beeping in and out" and I >> hear an echo and the sound quality is bad. >> >> Everything works perfectly in Skype on the same machine. >> >> In the advanced settings there are a ton of codecs and I don't understand any >> of them or how to use them. > > > > Hi Ted, > > For the sound issue, the first thing I'd suggest is simply making a call to the > Ekiga.net echo test service, and see what the sound quality is like there (e.g. > does it echo or cut in/out etc.). > > For the audio codecs, I find it easiest to enable PCMU, PCMA,and Speex only for > starters. More important is the order of codecs. By default, it is speex16, iLBC-H323only, PCMU, PCMA, hence it should be ok. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Mon May 23 18:13:06 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Mon, 23 May 2011 20:13:06 +0200 Subject: [Ekiga-list] question about sip protection In-Reply-To: References: Message-ID: <4DDAA3B2.4080005@pu-pm.univ-fcomte.fr> There is no encryption in ekiga currently, look for zrtp (and srtp?) On 22/05/11 22:28, Anthony Papillion wrote: > I don't believe they are encrypted because there are a few SIP clients > that expressly tout that they encrypt. I don't think Ekiga does. > > Anthony > > On 5/22/11, Nikolai Cassanova wrote: >> I wanted to know, when we talk through sip protocol, can people over >> Internet listen to our conversations or are all conversation through sip >> encrypted and no one over the Internet can get access to conversations. >> > From computer.ted at gmail.com Mon May 23 20:31:26 2011 From: computer.ted at gmail.com (Ted McCune) Date: Mon, 23 May 2011 13:31:26 -0700 Subject: [Ekiga-list] Poor Sound In-Reply-To: <4DDAA34B.30203@pu-pm.univ-fcomte.fr> References: <4DDAA34B.30203@pu-pm.univ-fcomte.fr> Message-ID: What seems to be happening on the other end is: "The quick fox jumped over the brown log." Comes through on the other end as; "The qu f jump ov th br log." Like chunks of data are hitting the bit bucket somewhere. Maybe a buffer or just a really bad Internet connection. On Mon, May 23, 2011 at 11:11 AM, Eugen Dedu < Eugen.Dedu at pu-pm.univ-fcomte.fr> wrote: > On 23/05/11 03:05, Dave Koelmeyer wrote: > >> >> >> On 23 May, 2011,at 12:24 PM, Ted McCune wrote: >> >> Running Debian 6, Intel HDA onboard audio, ALSA sound system, >>> Ekiga3.2.7, >>> Diamondcard SIP account. >>> >>> When calling phones the person I'm calling says I'm "beeping in and out" >>> and I >>> hear an echo and the sound quality is bad. >>> >>> Everything works perfectly in Skype on the same machine. >>> >>> In the advanced settings there are a ton of codecs and I don't >>> understand any >>> of them or how to use them. >>> >> >> >> >> Hi Ted, >> >> For the sound issue, the first thing I'd suggest is simply making a call >> to the >> Ekiga.net echo test service, and see what the sound quality is like there >> (e.g. >> does it echo or cut in/out etc.). >> >> For the audio codecs, I find it easiest to enable PCMU, PCMA,and Speex >> only for >> starters. >> > > More important is the order of codecs. By default, it is speex16, > iLBC-H323only, PCMU, PCMA, hence it should be ok. > > -- > Eugen > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Ted McCune -------------- next part -------------- An HTML attachment was scrubbed... URL: From rowens at ptd.net Mon May 23 20:39:20 2011 From: rowens at ptd.net (Rob Owens) Date: Mon, 23 May 2011 16:39:20 -0400 Subject: [Ekiga-list] question about sip protection In-Reply-To: References: Message-ID: <20110523203920.GB11815@aurora.owens.net> Twinkle also offers encryption for sip to sip. On Sun, May 22, 2011 at 03:50:43PM -0500, Anthony Papillion wrote: > There's no way to encrypt SIP to POTS that I know of since the POTS > end doesn't know how to decrypt it. SIP to SIP can be done though. I > think SIPCommunicator encrypts IIRC. > > On 5/22/11, Nikolai Cassanova wrote: > > Is there anyway an end user such as my self can encrypt my own sip when I > > talk to family and friends through sip to pots or when they call me from > > pots to my sip address? > > On May 22, 2011 4:28 PM, "Anthony Papillion" wrote: > >> I don't believe they are encrypted because there are a few SIP clients > >> that expressly tout that they encrypt. I don't think Ekiga does. > >> > >> Anthony > >> > >> On 5/22/11, Nikolai Cassanova wrote: > >>> I wanted to know, when we talk through sip protocol, can people over > >>> Internet listen to our conversations or are all conversation through sip > >>> encrypted and no one over the Internet can get access to conversations. > >>> > >> > >> -- > >> Sent from my mobile device > >> > >> Anthony Papillion > >> Advanced Data Concepts > >> Get real about your software/web development and IT Services > >> Phone: (918) 919-4624 > >> > >> Does your business need to reduce its phone bill? I can help! > >> Email me and ask me how! > >> _______________________________________________ > >> ekiga-list mailing list > >> ekiga-list at gnome.org > >> http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > -- > Sent from my mobile device > > Anthony Papillion > Advanced Data Concepts > Get real about your software/web development and IT Services > Phone: (918) 919-4624 > > Does your business need to reduce its phone bill? I can help! > Email me and ask me how! > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From jvankort at gmx.com Mon May 23 21:05:26 2011 From: jvankort at gmx.com (jvankort) Date: Mon, 23 May 2011 14:05:26 -0700 (PDT) Subject: [Ekiga-list] How to get ATA phone to ring? Message-ID: <1306184726394-3545491.post@n4.nabble.com> I bought a diamondcard personal number. I bought a Linksys PAP2 ATA. I bought a phone to connect to the ATA. Incoming calls loop around the planet and ring the phone at my house instead of where the ATA phone is located. Result is, I can call out but no-one can call me. How can I make this work? -- View this message in context: http://ekiga.1756082.n4.nabble.com/How-to-get-ATA-phone-to-ring-tp3545491p3545491.html Sent from the Ekiga General mailing list archive at Nabble.com. From raptorman18 at gmail.com Tue May 24 03:12:25 2011 From: raptorman18 at gmail.com (Paul Jones) Date: Mon, 23 May 2011 23:12:25 -0400 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall Message-ID: <4DDB2219.7090403@gmail.com> Hi, new to list and to Ekiga and SIP in general. Basically, I'm asking if running multiple computers with Ekiga behind the same NAT firewall, and each machine will be a different user with a different user account. Basically, the way I'm trying to do it is by specifying a port other than 5060 for the other computer. I've been using port 5046 for the other machine, and forwarding that port to the other machine, and changing the Ekiga setting in gconf-editor. But this does not seem to work for me. By "not work", i mean, the presence notification seems to work, but the echo-test does not work properly, because i can't see the "remote" video. (i test the presence notification by having myself in my own buddy list) So, am I going about it wrong, or is what I'm trying just not possible. Thank you so much, Paul From davekoelmeyer at me.com Tue May 24 05:25:41 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Tue, 24 May 2011 05:25:41 +0000 (GMT) Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDB2219.7090403@gmail.com> Message-ID: On 24 May, 2011,at 03:12 PM, Paul Jones wrote: > Hi, new to list and to Ekiga and SIP in general. > > Basically, I'm asking if running multiple computers with Ekiga behind > the same NAT firewall, and each machine will be a different user with a > different user account. > > Basically, the way I'm trying to do it is by specifying a port other > than 5060 for the other computer. I've been using port 5046 for the > other machine, and forwarding that port to the other machine, and > changing the Ekiga setting in gconf-editor. But this does not seem to > work for me. > > By "not work", i mean, the presence notification seems to work, but the > echo-test does not work properly, because i can't see the "remote" video. > > (i test the presence notification by having myself in my own buddy list) > > So, am I going about it wrong, or is what I'm trying just not possible. Hi Paul, I might be misunderstanding this, but does this help? http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate Cheers, Dave? -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 24 12:16:09 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 24 May 2011 14:16:09 +0200 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: References: Message-ID: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> On 24/05/11 07:25, Dave Koelmeyer wrote: > > > On 24 May, 2011,at 03:12 PM, Paul Jones wrote: > >> Hi, new to list and to Ekiga and SIP in general. >> >> Basically, I'm asking if running multiple computers with Ekiga behind >> the same NAT firewall, and each machine will be a different user with a >> different user account. >> >> Basically, the way I'm trying to do it is by specifying a port other >> than 5060 for the other computer. I've been using port 5046 for the >> other machine, and forwarding that port to the other machine, and >> changing the Ekiga setting in gconf-editor. But this does not seem to >> work for me. >> >> By "not work", i mean, the presence notification seems to work, but the >> echo-test does not work properly, because i can't see the "remote" video. >> >> (i test the presence notification by having myself in my own buddy list) >> >> So, am I going about it wrong, or is what I'm trying just not possible. > > Hi Paul, > > I might be misunderstanding this, but does this help? > > http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate You're right, but this tells that the two internal computers cannot communicate to each other. However, they should communicate simultaneously with computers from Internet, such as echo test for ex. Changing 5060 port is not needed for that. If only one computer runs ekiga, does it work? Finally, be sure to use 3.2.7, since it fixed a bug like this. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 24 12:17:43 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 24 May 2011 14:17:43 +0200 Subject: [Ekiga-list] How to get ATA phone to ring? In-Reply-To: <1306184726394-3545491.post@n4.nabble.com> References: <1306184726394-3545491.post@n4.nabble.com> Message-ID: <4DDBA1E7.6060808@pu-pm.univ-fcomte.fr> On 23/05/11 23:05, jvankort wrote: > I bought a diamondcard personal number. > I bought a Linksys PAP2 ATA. > I bought a phone to connect to the ATA. > Incoming calls loop around the planet and ring the phone at my house instead > of where the ATA phone is located. > > Result is, I can call out but no-one can call me. How can I make this work? I would say that this is a parameter of Internet provider, have you looked at your router configuration? -- Eugen From raptorman18 at gmail.com Tue May 24 18:23:57 2011 From: raptorman18 at gmail.com (Paul Jones) Date: Tue, 24 May 2011 14:23:57 -0400 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> Message-ID: <4DDBF7BD.1030504@gmail.com> On 05/24/2011 08:16 AM, Eugen Dedu wrote: > On 24/05/11 07:25, Dave Koelmeyer wrote: >> >> >> On 24 May, 2011,at 03:12 PM, Paul Jones wrote: >> >>> Hi, new to list and to Ekiga and SIP in general. >>> >>> Basically, I'm asking if running multiple computers with Ekiga behind >>> the same NAT firewall, and each machine will be a different user >>> with a >>> different user account. >>> >>> Basically, the way I'm trying to do it is by specifying a port other >>> than 5060 for the other computer. I've been using port 5046 for the >>> other machine, and forwarding that port to the other machine, and >>> changing the Ekiga setting in gconf-editor. But this does not seem to >>> work for me. >>> >>> By "not work", i mean, the presence notification seems to work, but >>> the >>> echo-test does not work properly, because i can't see the "remote" >>> video. >>> >>> (i test the presence notification by having myself in my own buddy >>> list) >>> >>> So, am I going about it wrong, or is what I'm trying just not >>> possible. >> >> Hi Paul, >> >> I might be misunderstanding this, but does this help? >> >> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >> > > You're right, but this tells that the two internal computers cannot > communicate to each other. > > However, they should communicate simultaneously with computers from > Internet, such as echo test for ex. Changing 5060 port is not needed > for that. > > If only one computer runs ekiga, does it work? Finally, be sure to > use 3.2.7, since it fixed a bug like this. > Hi, i just looked at this again. I turned on ekiga in one computer, then turned it on in the other. ON the first computer, everything worked, I could see that my user on the machine was on, i could see that the user on the other machine was also online. Echo test also worked, (i got "remote video"). However, on the second computer, echo test still worked like it did on the first machine, but presence didn't seem to work at all. I didn't get grey for people offline and green for people online, i just got the little people things, if you understand my description. The user I had on that machine (machine 2), was online according to machine 1, but not according to machine 2, since I had the user i was using on machine 2, in my contact list on machine 2. I'm assuming that if presence works and echo test works, the machine is functioning in such a way where it can make and receive calls. IN response to the other response, the Avahi implementation of Lan calling works perfectly to contact both computers, and it always has. I should also describe my network connection a little more. I have a modem and a router that both have NAT, so I'm double NATed. Right now, to get Ekiga to work on any computer I have to forward port 5060 UDP on the modem (only the modem), and Ekiga will work (with the problems I"m describing in these posts of course). However, Ekiga always has displayed the notification on startup where it says it cannot detect the network settings although it is working, once again, with the problems I am describing above and in these posts. I don't like putting the router into Access point mode and I don't have the password that I would need to put the modem into bridge mode. I can forward the ports in the router and the modem, but my router seems to have a quirk, where if I forward anything in the router, I can't connect to IRC, gmail, gtalk, or things like that from any computer. (I know, that's weird, and has nothing to do with what we are talking about in this topic.) Hopefully, I've done a better job of describing the situation over here. Thanks for listening and helping! Paul From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 24 19:10:40 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 24 May 2011 21:10:40 +0200 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDBF7BD.1030504@gmail.com> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> Message-ID: <4DDC02B0.1070000@pu-pm.univ-fcomte.fr> On 24/05/11 20:23, Paul Jones wrote: > On 05/24/2011 08:16 AM, Eugen Dedu wrote: >> On 24/05/11 07:25, Dave Koelmeyer wrote: >>> >>> >>> On 24 May, 2011,at 03:12 PM, Paul Jones wrote: >>> >>>> Hi, new to list and to Ekiga and SIP in general. >>>> >>>> Basically, I'm asking if running multiple computers with Ekiga behind >>>> the same NAT firewall, and each machine will be a different user >>>> with a >>>> different user account. >>>> >>>> Basically, the way I'm trying to do it is by specifying a port other >>>> than 5060 for the other computer. I've been using port 5046 for the >>>> other machine, and forwarding that port to the other machine, and >>>> changing the Ekiga setting in gconf-editor. But this does not seem to >>>> work for me. >>>> >>>> By "not work", i mean, the presence notification seems to work, but >>>> the >>>> echo-test does not work properly, because i can't see the "remote" >>>> video. >>>> >>>> (i test the presence notification by having myself in my own buddy >>>> list) >>>> >>>> So, am I going about it wrong, or is what I'm trying just not >>>> possible. >>> >>> Hi Paul, >>> >>> I might be misunderstanding this, but does this help? >>> >>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>> >> >> You're right, but this tells that the two internal computers cannot >> communicate to each other. >> >> However, they should communicate simultaneously with computers from >> Internet, such as echo test for ex. Changing 5060 port is not needed >> for that. >> >> If only one computer runs ekiga, does it work? Finally, be sure to >> use 3.2.7, since it fixed a bug like this. >> > Hi, i just looked at this again. I turned on ekiga in one computer, then > turned it on in the other. ON the first computer, everything worked, I > could see that my user on the machine was on, i could see that the user > on the other machine was also online. Echo test also worked, (i got > "remote video"). Do you use 3.2.7? -- Eugen From raptorman18 at gmail.com Tue May 24 22:08:30 2011 From: raptorman18 at gmail.com (Paul Jones) Date: Tue, 24 May 2011 18:08:30 -0400 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDC02B0.1070000@pu-pm.univ-fcomte.fr> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> <4DDC02B0.1070000@pu-pm.univ-fcomte.fr> Message-ID: <4DDC2C5E.8090002@gmail.com> On 05/24/2011 03:10 PM, Eugen Dedu wrote: > On 24/05/11 20:23, Paul Jones wrote: >> On 05/24/2011 08:16 AM, Eugen Dedu wrote: >>> On 24/05/11 07:25, Dave Koelmeyer wrote: >>>> >>>> >>>> On 24 May, 2011,at 03:12 PM, Paul Jones >>>> wrote: >>>> >>>>> Hi, new to list and to Ekiga and SIP in general. >>>>> >>>>> Basically, I'm asking if running multiple computers with Ekiga >>>>> behind >>>>> the same NAT firewall, and each machine will be a different user >>>>> with a >>>>> different user account. >>>>> >>>>> Basically, the way I'm trying to do it is by specifying a port >>>>> other >>>>> than 5060 for the other computer. I've been using port 5046 for the >>>>> other machine, and forwarding that port to the other machine, and >>>>> changing the Ekiga setting in gconf-editor. But this does not >>>>> seem to >>>>> work for me. >>>>> >>>>> By "not work", i mean, the presence notification seems to work, but >>>>> the >>>>> echo-test does not work properly, because i can't see the "remote" >>>>> video. >>>>> >>>>> (i test the presence notification by having myself in my own buddy >>>>> list) >>>>> >>>>> So, am I going about it wrong, or is what I'm trying just not >>>>> possible. >>>> >>>> Hi Paul, >>>> >>>> I might be misunderstanding this, but does this help? >>>> >>>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>>> >>>> >>> >>> You're right, but this tells that the two internal computers cannot >>> communicate to each other. >>> >>> However, they should communicate simultaneously with computers from >>> Internet, such as echo test for ex. Changing 5060 port is not needed >>> for that. >>> >>> If only one computer runs ekiga, does it work? Finally, be sure to >>> use 3.2.7, since it fixed a bug like this. >>> >> Hi, i just looked at this again. I turned on ekiga in one computer, then >> turned it on in the other. ON the first computer, everything worked, I >> could see that my user on the machine was on, i could see that the user >> on the other machine was also online. Echo test also worked, (i got >> "remote video"). > > Do you use 3.2.7? > Oh sorry, yes, it is 3.2.7 on both machines. Machine 1 is debian squeeze on 32 bit and machine 2 is debian Sid on 64 bit. PJ I may have taken ekiga from Sid on the squeeze machine but that shouldn't matter here. From thedogfarted at gmail.com Tue May 24 23:04:10 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Wed, 25 May 2011 02:04:10 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110524201116.GA13058@simba> References: <20110519075008.GA9541@simba> <20110519204810.GA13193@simba> <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> Message-ID: (Bringing this back to the mailing list) On Tue, May 24, 2011 at 11:11 PM, Bart Vandewoestyne wrote: > OK. ?The tcpdump I did with my android phone is online at > > http://www.kuleuven-kortrijk.be/~bartv/android.pcap > > I've configured 4 SIP accounts and they all try to register. > These are my findings: > > 1) For you server, I see a 400 Bad Contact address server > response, and as I understand it, this is because of the private > IP in the Contact header in the REGISTER message. > > 2) registration for sip.poivy.com and sip.diamondcard.us seem to > work, even with the private IP in the Contact header. Right. > 3) registration at ekiga.net fails, server returns a 606 Not > Acceptable, probably because of the private IP in the Via header. First one ("unregister others") because of the Via, the second because of the Contact. Your previous ekiga.net trace was missing the second REGISTER message, which led me to believe that Via was the main fault. > My main questions are: > > * Do you see a bug in the Android 2.3.4 client? ?Can it send > ?REGISTER messages with private IP's in the Via and Contact > ?header or is this not allowed? >From the traces it looks like it doesn't support any way to traverse NAT. It is not really a bug, but rather important missing feature, something they should do. IPv6 is not going to take over IPv4 any time soon, and there are other good reasons to use NAT (eg. my provider charges me for each public IP). > * Is ekiga.net wrong by returning the 606 Not Acceptable? > > If ekiga.net is wrong, I still feel we should try to convince the > ekiga.net admins to make it work... it will be a big step forward > for Ekiga on the Android/mobile market. Technically ekiga.net is wrong about the Via (but not Contact), but with no NAT support in phone (either classic STUN or ICE, or whatever), it doesn't make any difference to you. As Damien told in another post, you will experience audio problems (almost certainly). But the cool thing about SIP is you're not tied to a single provider. You can call anyone with a SIP address no matter what your provider is. If the phone has no NAT support, there are multiple providers with media relay, select the one(s) you like, and configure to use their outbound proxy. At least audio should work fine. Cheers -- Ian From Bart.Vandewoestyne at telenet.be Wed May 25 07:06:04 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Wed, 25 May 2011 09:06:04 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: References: <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> Message-ID: <20110525070603.GA15810@simba> On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Ruk???ns wrote: > > [...] > From the traces it looks like it doesn't support any way to traverse > NAT. It is not really a bug, but rather important missing feature, > something they should do. Wait a second... then why do the registrations at sip.poivy.com and sip.diamondcard.us work? Doesn't this mean that my SIP-client *is* somehow able to traverse NAT? (I'm afraid i'm missing technical background about NAT-traversal here to be able to answer this question myself :-( > Technically ekiga.net is wrong about the Via (but not Contact), but > with no NAT support in phone (either classic STUN or ICE, or > whatever), it doesn't make any difference to you. As Damien told in > another post, you will experience audio problems (almost certainly). > > But the cool thing about SIP is you're not tied to a single provider. > You can call anyone with a SIP address no matter what your provider > is. If the phone has no NAT support, there are multiple providers with > media relay, select the one(s) you like, and configure to use their > outbound proxy. At least audio should work fine. OK. So let me try to summarize the conclusions of this discussion: 1) The ekiga.net server is wrong in returning a 606 Not Acceptable because of a private IP in the Contact header of the REGISTER message. We have to wait for the ekiga.net admins to fix this. It is not at all clear how trivial this fix is. 2) If I want my Android 2.3.4 native SIP client to work with ekiga.net, I will have to wait until it supports STUN, ICE or another NAT traversal technology. 3) I can register with another SIP account (e.g. my poivy or diamondcard account), but then this means I won't be reachable at my ekiga.net SIP-address... and to be honest, because i support the Open Source philosophy, i would really like it if people could call me at my ekiga.net address and not some other address from a commercial provider... 4) I can try another SIP-client on android, like CSipSimple or Sipdroid. It will need some more testing to see if these work with ekiga.net... More on this later :-) Regards, Bart -- "Share what you know. Learn what you don't." From herman at aeronetworks.ca Wed May 25 00:06:05 2011 From: herman at aeronetworks.ca (herman) Date: Tue, 24 May 2011 17:06:05 -0700 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 nativeSIP-client References: <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> Message-ID: <0000177117@mail.aeronetworks.ca> > Wed May 25 2011 12:06:04 AM MST from "Bart Vandewoestyne" > Subject: Re: [Ekiga-list] Ekiga.net account >with Android 2.3.4 nativeSIP-client > > On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Rukš??ns wrote: > > >>[...] >> From the traces it looks like it doesn't support any way to traverse >> NAT. It is not really a bug, but rather important missing feature, >> something they should do. >> > >> >> > >>There is a good description of the Ekiga problems on the Jitsi web site: > >>http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net > >> >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Wed May 25 07:35:45 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Wed, 25 May 2011 19:35:45 +1200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110525070603.GA15810@simba> References: <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> Message-ID: <4DDCB151.50502@me.com> On 25/05/11 07:06 PM, Bart Vandewoestyne wrote: > > 4) I can try another SIP-client on android, like CSipSimple or > Sipdroid. It will need some more testing to see if these work > with ekiga.net... More on this later :-) Hi Bart, FWIW Sipdroid is what I use on a Motorola Milestone, and it works fine with Ekiga.net If you observe anything of note while trying out different SIP clients, would be useful to know so we can update the Android compatibility list at: http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ From Bart.Vandewoestyne at telenet.be Wed May 25 07:59:12 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Wed, 25 May 2011 09:59:12 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <4DDCB151.50502@me.com> References: <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> <4DDCB151.50502@me.com> Message-ID: <20110525075912.GB16279@simba> On Wed, May 25, 2011 at 07:35:45PM +1200, Dave Koelmeyer wrote: > > Hi Bart, > > FWIW Sipdroid is what I use on a Motorola Milestone, and it works > fine with Ekiga.net > > If you observe anything of note while trying out different SIP > clients, would be useful to know so we can update the Android > compatibility list at: > > http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android Hmm... I just tried creating an account so that I could update the information, but apparently creating accounts does not work (or I am not allowed to do it...) If somehow I can get an account to edit that info, I would be happy to try and keep it up-to-date and add all possible info concerning Android (2.3.4) compatibility. Regards, Bart -- "Share what you know. Learn what you don't." From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 25 08:05:08 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 25 May 2011 10:05:08 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110525075912.GB16279@simba> References: <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> <4DDCB151.50502@me.com> <20110525075912.GB16279@simba> Message-ID: <4DDCB834.6020709@pu-pm.univ-fcomte.fr> On 25/05/11 09:59, Bart Vandewoestyne wrote: > On Wed, May 25, 2011 at 07:35:45PM +1200, Dave Koelmeyer wrote: >> >> Hi Bart, >> >> FWIW Sipdroid is what I use on a Motorola Milestone, and it works >> fine with Ekiga.net >> >> If you observe anything of note while trying out different SIP >> clients, would be useful to know so we can update the Android >> compatibility list at: >> >> http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android > > Hmm... I just tried creating an account so that I could update > the information, but apparently creating accounts does not work > (or I am not allowed to do it...) > > If somehow I can get an account to edit that info, I would be > happy to try and keep it up-to-date and add all possible info > concerning Android (2.3.4) compatibility. Created. -- Eugen From Bart.Vandewoestyne at telenet.be Wed May 25 11:56:52 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Wed, 25 May 2011 13:56:52 +0200 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <4DDCB834.6020709@pu-pm.univ-fcomte.fr> References: <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> <4DDCB151.50502@me.com> <20110525075912.GB16279@simba> <4DDCB834.6020709@pu-pm.univ-fcomte.fr> Message-ID: <20110525115652.GA17601@simba> On Wed, May 25, 2011 at 10:05:08AM +0200, Eugen Dedu wrote: > > >If somehow I can get an account to edit that info, I would be > >happy to try and keep it up-to-date and add all possible info > >concerning Android (2.3.4) compatibility. > > Created. Thanks Eugen! I've updated the information at http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android with all that I know. Please check and if certain things are not well done or well written, please correct. I'll keep on experimenting with Android and update the info when necessary. Kind regards, Bart -- "Share what you know. Learn what you don't." From fbsdmon at gmail.com Wed May 25 14:41:25 2011 From: fbsdmon at gmail.com (fbsdmon) Date: Wed, 25 May 2011 07:41:25 -0700 (PDT) Subject: [Ekiga-list] Is ekiga 3.2.7 supposed to work on Windows 7 64 Bit? In-Reply-To: <1300920420951-3401008.post@n4.nabble.com> References: <201012121713.28720.gstengel@gmx.net> <201012161612.58489.gstengel@gmx.net> <1300920420951-3401008.post@n4.nabble.com> Message-ID: <1306334485499-3549906.post@n4.nabble.com> I have the exact same problem on HP DM4 and would love to hear about a solution/workaround! -- View this message in context: http://ekiga.1756082.n4.nabble.com/Is-ekiga-3-2-7-supposed-to-work-on-Windows-7-64-Bit-tp3084392p3549906.html Sent from the Ekiga General mailing list archive at Nabble.com. From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 25 15:06:31 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 25 May 2011 17:06:31 +0200 Subject: [Ekiga-list] Is ekiga 3.2.7 supposed to work on Windows 7 64 Bit? In-Reply-To: <1306334485499-3549906.post@n4.nabble.com> References: <201012121713.28720.gstengel@gmx.net> <201012161612.58489.gstengel@gmx.net> <1300920420951-3401008.post@n4.nabble.com> <1306334485499-3549906.post@n4.nabble.com> Message-ID: <4DDD1AF7.2080006@pu-pm.univ-fcomte.fr> On 25/05/11 16:41, fbsdmon wrote: > I have the exact same problem on HP DM4 and would love to hear about a > solution/workaround! Get the debug output (-d 4) and look inside if you have the same error as https://bugzilla.gnome.org/show_bug.cgi?id=626515#c3 If yes, I do not have any workaround, sorry! Well, maybe: wait a bit and try using latest ekiga for windows (3.3.1), to be released shortly... (but I think there are little chances). -- Eugen From spacefreak18 at gmail.com Tue May 24 20:53:09 2011 From: spacefreak18 at gmail.com (Paul Jones) Date: Tue, 24 May 2011 16:53:09 -0400 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDC02B0.1070000@pu-pm.univ-fcomte.fr> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> <4DDC02B0.1070000@pu-pm.univ-fcomte.fr> Message-ID: <6ADFED60-A3C3-4152-B40D-C845686711CE@gmail.com> Oh sorry, yes, it is 3.2.7. Machine 1 is debian squeeze on 32 bit and machine 2 is debian Sid on 64 bit. PJ I may have taken ekiga from Sid on the squeeze machine but that shouldn't matter here. On May 24, 2011, at 15:10, Eugen Dedu wrote: > On 24/05/11 20:23, Paul Jones wrote: >> On 05/24/2011 08:16 AM, Eugen Dedu wrote: >>> On 24/05/11 07:25, Dave Koelmeyer wrote: >>>> >>>> >>>> On 24 May, 2011,at 03:12 PM, Paul Jones wrote: >>>> >>>>> Hi, new to list and to Ekiga and SIP in general. >>>>> >>>>> Basically, I'm asking if running multiple computers with Ekiga behind >>>>> the same NAT firewall, and each machine will be a different user >>>>> with a >>>>> different user account. >>>>> >>>>> Basically, the way I'm trying to do it is by specifying a port other >>>>> than 5060 for the other computer. I've been using port 5046 for the >>>>> other machine, and forwarding that port to the other machine, and >>>>> changing the Ekiga setting in gconf-editor. But this does not seem to >>>>> work for me. >>>>> >>>>> By "not work", i mean, the presence notification seems to work, but >>>>> the >>>>> echo-test does not work properly, because i can't see the "remote" >>>>> video. >>>>> >>>>> (i test the presence notification by having myself in my own buddy >>>>> list) >>>>> >>>>> So, am I going about it wrong, or is what I'm trying just not >>>>> possible. >>>> >>>> Hi Paul, >>>> >>>> I might be misunderstanding this, but does this help? >>>> >>>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>>> >>> >>> You're right, but this tells that the two internal computers cannot >>> communicate to each other. >>> >>> However, they should communicate simultaneously with computers from >>> Internet, such as echo test for ex. Changing 5060 port is not needed >>> for that. >>> >>> If only one computer runs ekiga, does it work? Finally, be sure to >>> use 3.2.7, since it fixed a bug like this. >>> >> Hi, i just looked at this again. I turned on ekiga in one computer, then >> turned it on in the other. ON the first computer, everything worked, I >> could see that my user on the machine was on, i could see that the user >> on the other machine was also online. Echo test also worked, (i got >> "remote video"). > > Do you use 3.2.7? > > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 25 16:42:43 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 25 May 2011 18:42:43 +0200 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDBF7BD.1030504@gmail.com> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> Message-ID: <4DDD3183.4060906@pu-pm.univ-fcomte.fr> On 24/05/11 20:23, Paul Jones wrote: > On 05/24/2011 08:16 AM, Eugen Dedu wrote: >> On 24/05/11 07:25, Dave Koelmeyer wrote: >>> >>> >>> On 24 May, 2011,at 03:12 PM, Paul Jones wrote: >>> >>>> Hi, new to list and to Ekiga and SIP in general. >>>> >>>> Basically, I'm asking if running multiple computers with Ekiga behind >>>> the same NAT firewall, and each machine will be a different user >>>> with a >>>> different user account. >>>> >>>> Basically, the way I'm trying to do it is by specifying a port other >>>> than 5060 for the other computer. I've been using port 5046 for the >>>> other machine, and forwarding that port to the other machine, and >>>> changing the Ekiga setting in gconf-editor. But this does not seem to >>>> work for me. >>>> >>>> By "not work", i mean, the presence notification seems to work, but >>>> the >>>> echo-test does not work properly, because i can't see the "remote" >>>> video. >>>> >>>> (i test the presence notification by having myself in my own buddy >>>> list) >>>> >>>> So, am I going about it wrong, or is what I'm trying just not >>>> possible. >>> >>> Hi Paul, >>> >>> I might be misunderstanding this, but does this help? >>> >>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>> >> >> You're right, but this tells that the two internal computers cannot >> communicate to each other. >> >> However, they should communicate simultaneously with computers from >> Internet, such as echo test for ex. Changing 5060 port is not needed >> for that. >> >> If only one computer runs ekiga, does it work? Finally, be sure to >> use 3.2.7, since it fixed a bug like this. >> > Hi, i just looked at this again. I turned on ekiga in one computer, then > turned it on in the other. ON the first computer, everything worked, I > could see that my user on the machine was on, i could see that the user > on the other machine was also online. Echo test also worked, (i got > "remote video"). > > However, on the second computer, echo test still worked like it did on > the first machine, but presence didn't seem to work at all. I didn't get > grey for people offline and green for people online, i just got the > little people things, if you understand my description. The user I had > on that machine (machine 2), was online according to machine 1, but not > according to machine 2, since I had the user i was using on machine 2, > in my contact list on machine 2. > > I'm assuming that if presence works and echo test works, the machine is > functioning in such a way where it can make and receive calls. > > IN response to the other response, the Avahi implementation of Lan > calling works perfectly to contact both computers, and it always has. > > I should also describe my network connection a little more. I have a > modem and a router that both have NAT, so I'm double NATed. Right now, > to get Ekiga to work on any computer I have to forward port 5060 UDP on > the modem (only the modem), and Ekiga will work (with the problems I"m > describing in these posts of course). However, Ekiga always has > displayed the notification on startup where it says it cannot detect the > network settings although it is working, once again, with the problems I > am describing above and in these posts. > > I don't like putting the router into Access point mode and I don't have > the password that I would need to put the modem into bridge mode. I can > forward the ports in the router and the modem, but my router seems to > have a quirk, where if I forward anything in the router, I can't connect > to IRC, gmail, gtalk, or things like that from any computer. (I know, > that's weird, and has nothing to do with what we are talking about in > this topic.) So to resume: everything works on both computers, except the presence on computer 2. Well, in this case, the best is to wait a bit until a new unstable release appears and test it, because several changes were made to presence. By the way, since you received the dialog box with the error, I think you can call, but you cannot be called :o( Try using 520 at ekiga.net and see if you are called. -- Eugen From thedogfarted at gmail.com Wed May 25 17:52:43 2011 From: thedogfarted at gmail.com (=?UTF-8?B?SsSBbmlzIFJ1a8WhxIFucw==?=) Date: Wed, 25 May 2011 20:52:43 +0300 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <20110525070603.GA15810@simba> References: <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> Message-ID: On Wed, May 25, 2011 at 10:06 AM, Bart Vandewoestyne wrote: > On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Ruk???ns wrote: >> >> [...] >> From the traces it looks like it doesn't support any way to traverse >> NAT. It is not really a bug, but rather important missing feature, >> something they should do. > > Wait a second... then why do the registrations at sip.poivy.com > and sip.diamondcard.us work? ?Doesn't this mean that my > SIP-client *is* somehow able to traverse NAT? (I'm afraid i'm > missing technical background about NAT-traversal here to be able > to answer this question myself :-( No, it doesn't mean that the client is able to "traverse" NAT. It means that either the *server* is able to traverse NAT by relaying the audio, or you will have no audio in an actual call (either incoming or both ways). The technical background is that when you make a call, the phone sends an INVITE message, telling the other end your IP and the port where to send audio. However, if you're behind NAT, that IP and port is generally not reachable from the outside world. Which means that with no NAT support, the audio sent by the other end will not reach you. The same applies to the called phone, if it is behind NAT as well, you will have no audio at all. There are several ways to counter this: 1) "classic" STUN - the phone can discover the corresponding public IP and port by contacting a STUN server, and then uses it in the INVITE. However this doesn't work for more complex types of NAT, and the whole thing is a bit sketchy. Therefore "classic" STUN has been deprecated for some time. 2) ICE - instead of contacting a dedicated STUN server, the endpoints communicate between themselves to find out each others public IPs and ports used for audio. This works in most cases, except when both parties are behind a very restrictive NAT. 3) Dedicated media relay server - instead of sending audio directly to the other party, the audio is sent through a dedicated server with a public IP. This works even with no NAT support in the client, but is very costly to the provider (in terms of bandwidth, hardware and money). If the phone supports either STUN or ICE, it is usually indicated by a public IP in the Contact address. I'm pretty sure diamondcard.us have a relay server, thus they don't care whether the IP is public or private. Ekiga.net doesn't have a relay server, therefore it's reasonable that it rejects registrations with private IPs. Cheers -- Ian From raptorman18 at gmail.com Wed May 25 18:07:24 2011 From: raptorman18 at gmail.com (Paul Jones) Date: Wed, 25 May 2011 14:07:24 -0400 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDD3183.4060906@pu-pm.univ-fcomte.fr> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> <4DDD3183.4060906@pu-pm.univ-fcomte.fr> Message-ID: <4DDD455C.7060001@gmail.com> On 05/25/2011 12:42 PM, Eugen Dedu wrote: > On 24/05/11 20:23, Paul Jones wrote: >> On 05/24/2011 08:16 AM, Eugen Dedu wrote: >>> On 24/05/11 07:25, Dave Koelmeyer wrote: >>>> >>>> >>>> On 24 May, 2011,at 03:12 PM, Paul Jones >>>> wrote: >>>> >>>>> Hi, new to list and to Ekiga and SIP in general. >>>>> >>>>> Basically, I'm asking if running multiple computers with Ekiga >>>>> behind >>>>> the same NAT firewall, and each machine will be a different user >>>>> with a >>>>> different user account. >>>>> >>>>> Basically, the way I'm trying to do it is by specifying a port >>>>> other >>>>> than 5060 for the other computer. I've been using port 5046 for the >>>>> other machine, and forwarding that port to the other machine, and >>>>> changing the Ekiga setting in gconf-editor. But this does not >>>>> seem to >>>>> work for me. >>>>> >>>>> By "not work", i mean, the presence notification seems to work, but >>>>> the >>>>> echo-test does not work properly, because i can't see the "remote" >>>>> video. >>>>> >>>>> (i test the presence notification by having myself in my own buddy >>>>> list) >>>>> >>>>> So, am I going about it wrong, or is what I'm trying just not >>>>> possible. >>>> >>>> Hi Paul, >>>> >>>> I might be misunderstanding this, but does this help? >>>> >>>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>>> >>>> >>> >>> You're right, but this tells that the two internal computers cannot >>> communicate to each other. >>> >>> However, they should communicate simultaneously with computers from >>> Internet, such as echo test for ex. Changing 5060 port is not needed >>> for that. >>> >>> If only one computer runs ekiga, does it work? Finally, be sure to >>> use 3.2.7, since it fixed a bug like this. >>> >> Hi, i just looked at this again. I turned on ekiga in one computer, then >> turned it on in the other. ON the first computer, everything worked, I >> could see that my user on the machine was on, i could see that the user >> on the other machine was also online. Echo test also worked, (i got >> "remote video"). >> >> However, on the second computer, echo test still worked like it did on >> the first machine, but presence didn't seem to work at all. I didn't get >> grey for people offline and green for people online, i just got the >> little people things, if you understand my description. The user I had >> on that machine (machine 2), was online according to machine 1, but not >> according to machine 2, since I had the user i was using on machine 2, >> in my contact list on machine 2. >> >> I'm assuming that if presence works and echo test works, the machine is >> functioning in such a way where it can make and receive calls. >> >> IN response to the other response, the Avahi implementation of Lan >> calling works perfectly to contact both computers, and it always has. >> >> I should also describe my network connection a little more. I have a >> modem and a router that both have NAT, so I'm double NATed. Right now, >> to get Ekiga to work on any computer I have to forward port 5060 UDP on >> the modem (only the modem), and Ekiga will work (with the problems I"m >> describing in these posts of course). However, Ekiga always has >> displayed the notification on startup where it says it cannot detect the >> network settings although it is working, once again, with the problems I >> am describing above and in these posts. >> >> I don't like putting the router into Access point mode and I don't have >> the password that I would need to put the modem into bridge mode. I can >> forward the ports in the router and the modem, but my router seems to >> have a quirk, where if I forward anything in the router, I can't connect >> to IRC, gmail, gtalk, or things like that from any computer. (I know, >> that's weird, and has nothing to do with what we are talking about in >> this topic.) > > So to resume: everything works on both computers, except the presence > on computer 2. Well, in this case, the best is to wait a bit until a > new unstable release appears and test it, because several changes were > made to presence. > > By the way, since you received the dialog box with the error, I think > you can call, but you cannot be called :o( Try using 520 at ekiga.net > and see if you are called. > Hi, thanks for responding. Just to clairfy it's not always machine 2 as in my example, just whichever machine was the second to start ekiga. Which is machine 2 in my example, and I'll continue to use it like that for future examples. Alright, when I do echo test 520 from machine 2, the reply call goes to machine 1. Also, I do not get any remote video when doing echo test 520 from either machine, audio does work though. Secondly, after I do a 520 echo test, if I try a normal 500 echo test afterward, sometimes nothing works, i don't even hear the operator. Remote video doesn't seem to work on echo test 520 even with only one machine. Remote audio does work though. Usually remote video works with the 500 echo test on both machines regardless or the order they were started up in. So, it seems only machine 1 will be callable, and calls to machine 2 will be routed to machine 1. And some calls me, I will not be able to see their video? Does that help any? PJ From Eugen.Dedu at pu-pm.univ-fcomte.fr Wed May 25 18:17:16 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Wed, 25 May 2011 20:17:16 +0200 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDD455C.7060001@gmail.com> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> <4DDD3183.4060906@pu-pm.univ-fcomte.fr> <4DDD455C.7060001@gmail.com> Message-ID: <4DDD47AC.1090605@pu-pm.univ-fcomte.fr> On 25/05/11 20:07, Paul Jones wrote: > On 05/25/2011 12:42 PM, Eugen Dedu wrote: >> On 24/05/11 20:23, Paul Jones wrote: >>> On 05/24/2011 08:16 AM, Eugen Dedu wrote: >>>> On 24/05/11 07:25, Dave Koelmeyer wrote: >>>>> >>>>> >>>>> On 24 May, 2011,at 03:12 PM, Paul Jones >>>>> wrote: >>>>> >>>>>> Hi, new to list and to Ekiga and SIP in general. >>>>>> >>>>>> Basically, I'm asking if running multiple computers with Ekiga >>>>>> behind >>>>>> the same NAT firewall, and each machine will be a different user >>>>>> with a >>>>>> different user account. >>>>>> >>>>>> Basically, the way I'm trying to do it is by specifying a port >>>>>> other >>>>>> than 5060 for the other computer. I've been using port 5046 for the >>>>>> other machine, and forwarding that port to the other machine, and >>>>>> changing the Ekiga setting in gconf-editor. But this does not >>>>>> seem to >>>>>> work for me. >>>>>> >>>>>> By "not work", i mean, the presence notification seems to work, but >>>>>> the >>>>>> echo-test does not work properly, because i can't see the "remote" >>>>>> video. >>>>>> >>>>>> (i test the presence notification by having myself in my own buddy >>>>>> list) >>>>>> >>>>>> So, am I going about it wrong, or is what I'm trying just not >>>>>> possible. >>>>> >>>>> Hi Paul, >>>>> >>>>> I might be misunderstanding this, but does this help? >>>>> >>>>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>>>> >>>>> >>>> >>>> You're right, but this tells that the two internal computers cannot >>>> communicate to each other. >>>> >>>> However, they should communicate simultaneously with computers from >>>> Internet, such as echo test for ex. Changing 5060 port is not needed >>>> for that. >>>> >>>> If only one computer runs ekiga, does it work? Finally, be sure to >>>> use 3.2.7, since it fixed a bug like this. >>>> >>> Hi, i just looked at this again. I turned on ekiga in one computer, then >>> turned it on in the other. ON the first computer, everything worked, I >>> could see that my user on the machine was on, i could see that the user >>> on the other machine was also online. Echo test also worked, (i got >>> "remote video"). >>> >>> However, on the second computer, echo test still worked like it did on >>> the first machine, but presence didn't seem to work at all. I didn't get >>> grey for people offline and green for people online, i just got the >>> little people things, if you understand my description. The user I had >>> on that machine (machine 2), was online according to machine 1, but not >>> according to machine 2, since I had the user i was using on machine 2, >>> in my contact list on machine 2. >>> >>> I'm assuming that if presence works and echo test works, the machine is >>> functioning in such a way where it can make and receive calls. >>> >>> IN response to the other response, the Avahi implementation of Lan >>> calling works perfectly to contact both computers, and it always has. >>> >>> I should also describe my network connection a little more. I have a >>> modem and a router that both have NAT, so I'm double NATed. Right now, >>> to get Ekiga to work on any computer I have to forward port 5060 UDP on >>> the modem (only the modem), and Ekiga will work (with the problems I"m >>> describing in these posts of course). However, Ekiga always has >>> displayed the notification on startup where it says it cannot detect the >>> network settings although it is working, once again, with the problems I >>> am describing above and in these posts. >>> >>> I don't like putting the router into Access point mode and I don't have >>> the password that I would need to put the modem into bridge mode. I can >>> forward the ports in the router and the modem, but my router seems to >>> have a quirk, where if I forward anything in the router, I can't connect >>> to IRC, gmail, gtalk, or things like that from any computer. (I know, >>> that's weird, and has nothing to do with what we are talking about in >>> this topic.) >> >> So to resume: everything works on both computers, except the presence >> on computer 2. Well, in this case, the best is to wait a bit until a >> new unstable release appears and test it, because several changes were >> made to presence. >> >> By the way, since you received the dialog box with the error, I think >> you can call, but you cannot be called :o( Try using 520 at ekiga.net >> and see if you are called. >> > Hi, thanks for responding. Just to clairfy it's not always machine 2 as > in my example, just whichever machine was the second to start ekiga. > Which is machine 2 in my example, and I'll continue to use it like that > for future examples. > > Alright, when I do echo test 520 from machine 2, the reply call goes to > machine 1. Also, I do not get any remote video when doing echo test 520 > from either machine, audio does work though. Secondly, after I do a 520 > echo test, if I try a normal 500 echo test afterward, sometimes nothing > works, i don't even hear the operator. 520 is audio-only, so no problem. > Remote video doesn't seem to work on echo test 520 even with only one > machine. Remote audio does work though. > > Usually remote video works with the 500 echo test on both machines > regardless or the order they were started up in. > > So, it seems only machine 1 will be callable, and calls to machine 2 > will be routed to machine 1. And some calls me, I will not be able to > see their video? If audio works, then video works too. I think it is a known issue that you cannot have two ekiga inside the same NAT which get called correctly... I will investigate this later. -- Eugen From raptorman18 at gmail.com Wed May 25 18:25:20 2011 From: raptorman18 at gmail.com (Paul Jones) Date: Wed, 25 May 2011 14:25:20 -0400 Subject: [Ekiga-list] Running Multiple Computers with Ekiga behind same NAT firewall In-Reply-To: <4DDD47AC.1090605@pu-pm.univ-fcomte.fr> References: <4DDBA189.7020200@pu-pm.univ-fcomte.fr> <4DDBF7BD.1030504@gmail.com> <4DDD3183.4060906@pu-pm.univ-fcomte.fr> <4DDD455C.7060001@gmail.com> <4DDD47AC.1090605@pu-pm.univ-fcomte.fr> Message-ID: <4DDD4990.6010207@gmail.com> On 05/25/2011 02:17 PM, Eugen Dedu wrote: > On 25/05/11 20:07, Paul Jones wrote: >> On 05/25/2011 12:42 PM, Eugen Dedu wrote: >>> On 24/05/11 20:23, Paul Jones wrote: >>>> On 05/24/2011 08:16 AM, Eugen Dedu wrote: >>>>> On 24/05/11 07:25, Dave Koelmeyer wrote: >>>>>> >>>>>> >>>>>> On 24 May, 2011,at 03:12 PM, Paul Jones >>>>>> wrote: >>>>>> >>>>>>> Hi, new to list and to Ekiga and SIP in general. >>>>>>> >>>>>>> Basically, I'm asking if running multiple computers with Ekiga >>>>>>> behind >>>>>>> the same NAT firewall, and each machine will be a different user >>>>>>> with a >>>>>>> different user account. >>>>>>> >>>>>>> Basically, the way I'm trying to do it is by specifying a port >>>>>>> other >>>>>>> than 5060 for the other computer. I've been using port 5046 >>>>>>> for the >>>>>>> other machine, and forwarding that port to the other machine, >>>>>>> and >>>>>>> changing the Ekiga setting in gconf-editor. But this does not >>>>>>> seem to >>>>>>> work for me. >>>>>>> >>>>>>> By "not work", i mean, the presence notification seems to >>>>>>> work, but >>>>>>> the >>>>>>> echo-test does not work properly, because i can't see the >>>>>>> "remote" >>>>>>> video. >>>>>>> >>>>>>> (i test the presence notification by having myself in my own >>>>>>> buddy >>>>>>> list) >>>>>>> >>>>>>> So, am I going about it wrong, or is what I'm trying just not >>>>>>> possible. >>>>>> >>>>>> Hi Paul, >>>>>> >>>>>> I might be misunderstanding this, but does this help? >>>>>> >>>>>> http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router#I_have_2_Ekiga_behind_a_NAT_using_STUN:_they_can.27t_communicate >>>>>> >>>>>> >>>>>> >>>>> >>>>> You're right, but this tells that the two internal computers cannot >>>>> communicate to each other. >>>>> >>>>> However, they should communicate simultaneously with computers from >>>>> Internet, such as echo test for ex. Changing 5060 port is not needed >>>>> for that. >>>>> >>>>> If only one computer runs ekiga, does it work? Finally, be sure to >>>>> use 3.2.7, since it fixed a bug like this. >>>>> >>>> Hi, i just looked at this again. I turned on ekiga in one computer, >>>> then >>>> turned it on in the other. ON the first computer, everything worked, I >>>> could see that my user on the machine was on, i could see that the >>>> user >>>> on the other machine was also online. Echo test also worked, (i got >>>> "remote video"). >>>> >>>> However, on the second computer, echo test still worked like it did on >>>> the first machine, but presence didn't seem to work at all. I >>>> didn't get >>>> grey for people offline and green for people online, i just got the >>>> little people things, if you understand my description. The user I had >>>> on that machine (machine 2), was online according to machine 1, but >>>> not >>>> according to machine 2, since I had the user i was using on machine 2, >>>> in my contact list on machine 2. >>>> >>>> I'm assuming that if presence works and echo test works, the >>>> machine is >>>> functioning in such a way where it can make and receive calls. >>>> >>>> IN response to the other response, the Avahi implementation of Lan >>>> calling works perfectly to contact both computers, and it always has. >>>> >>>> I should also describe my network connection a little more. I have a >>>> modem and a router that both have NAT, so I'm double NATed. Right now, >>>> to get Ekiga to work on any computer I have to forward port 5060 >>>> UDP on >>>> the modem (only the modem), and Ekiga will work (with the problems I"m >>>> describing in these posts of course). However, Ekiga always has >>>> displayed the notification on startup where it says it cannot >>>> detect the >>>> network settings although it is working, once again, with the >>>> problems I >>>> am describing above and in these posts. >>>> >>>> I don't like putting the router into Access point mode and I don't >>>> have >>>> the password that I would need to put the modem into bridge mode. I >>>> can >>>> forward the ports in the router and the modem, but my router seems to >>>> have a quirk, where if I forward anything in the router, I can't >>>> connect >>>> to IRC, gmail, gtalk, or things like that from any computer. (I know, >>>> that's weird, and has nothing to do with what we are talking about in >>>> this topic.) >>> >>> So to resume: everything works on both computers, except the presence >>> on computer 2. Well, in this case, the best is to wait a bit until a >>> new unstable release appears and test it, because several changes were >>> made to presence. >>> >>> By the way, since you received the dialog box with the error, I think >>> you can call, but you cannot be called :o( Try using 520 at ekiga.net >>> and see if you are called. >>> >> Hi, thanks for responding. Just to clairfy it's not always machine 2 as >> in my example, just whichever machine was the second to start ekiga. >> Which is machine 2 in my example, and I'll continue to use it like that >> for future examples. >> >> Alright, when I do echo test 520 from machine 2, the reply call goes to >> machine 1. Also, I do not get any remote video when doing echo test 520 >> from either machine, audio does work though. Secondly, after I do a 520 >> echo test, if I try a normal 500 echo test afterward, sometimes nothing >> works, i don't even hear the operator. > > 520 is audio-only, so no problem. > >> Remote video doesn't seem to work on echo test 520 even with only one >> machine. Remote audio does work though. >> >> Usually remote video works with the 500 echo test on both machines >> regardless or the order they were started up in. >> >> So, it seems only machine 1 will be callable, and calls to machine 2 >> will be routed to machine 1. And some calls me, I will not be able to >> see their video? > > If audio works, then video works too. > > I think it is a known issue that you cannot have two ekiga inside the > same NAT which get called correctly... I will investigate this later. > Oh, thanks for clearing that up about audio-only. I would think it would be possible to have 2 machines running it maybe needing to use different ports for the two machines. Anyway, thanks for looking into it. And of course, as soon as a new unstable version is available I will install it as soon as possible and report back if any issue is solved. Thanks very much, Paul (can't wait for ipv6) From ncassanova11 at gmail.com Wed May 25 20:14:00 2011 From: ncassanova11 at gmail.com (Nikolai Cassanova) Date: Wed, 25 May 2011 16:14:00 -0400 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: <4DDCB834.6020709@pu-pm.univ-fcomte.fr> References: <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> <4DDCB151.50502@me.com> <20110525075912.GB16279@simba> <4DDCB834.6020709@pu-pm.univ-fcomte.fr> Message-ID: <4DDD6308.3000800@gmail.com> I was reading the results of your test with ekiga.net on android 2.3.4 built in sip, which i use for my daily life only on tmobile-usa 3g network. I think you can get ekiga.net to work with android but it would have to be through a middle man. That middle man would have to be pbxes.org which is what i use as my sip provider on android 2.3.4 built in sip client. It registers and connects fine, but for people to call you on ekiga.net you would have to go to pbxes.org and forward the incoming call going to your sip address at pbxes.org to ekiga.net and vice versa. So if someone calls your ekiga.net sip address it would be forwarded to your pbxes.org sip address then you would be able to pick up phone call on your android 2.3.4 device's sip client which would be registered to your pbxes.org sip address. In terms of calling other people on sip you could simply just return the call and use pbxes.org web browser system settings to tell people that the incoming call-id would show your ekiga.net sip address instead of your pbxes.org sip address. Basically what i think could solve your problem would be to use another sip provider to forward and direct your calling through your ekiga.net sip address. Hope this helps. Also if you are still certain about using a third party app over the built in sip client which i use to do on my android phone before android got built in sip, both sipdroid and csipsimple are fantastic. I think I will have to give csipsimple more thumbs up and praise because i feel that app is a little more polished than sipdroid and also they have in there settings an actual pre-made settings for users who use ekiga, so getting ekiga registered with that sip client is easier in my opinion, they also have actually a whole bunch of sip providers settings already pre-made for users. On 05/25/2011 04:05 AM, Eugen Dedu wrote: > On 25/05/11 09:59, Bart Vandewoestyne wrote: >> On Wed, May 25, 2011 at 07:35:45PM +1200, Dave Koelmeyer wrote: >>> >>> Hi Bart, >>> >>> FWIW Sipdroid is what I use on a Motorola Milestone, and it works >>> fine with Ekiga.net >>> >>> If you observe anything of note while trying out different SIP >>> clients, would be useful to know so we can update the Android >>> compatibility list at: >>> >>> http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android >> >> Hmm... I just tried creating an account so that I could update >> the information, but apparently creating accounts does not work >> (or I am not allowed to do it...) >> >> If somehow I can get an account to edit that info, I would be >> happy to try and keep it up-to-date and add all possible info >> concerning Android (2.3.4) compatibility. > > Created. > From drmesmith at yahoo.com Thu May 26 01:39:04 2011 From: drmesmith at yahoo.com (Mark Smith) Date: Wed, 25 May 2011 18:39:04 -0700 (PDT) Subject: [Ekiga-list] ekiga behind two routers In-Reply-To: Message-ID: <333261.69732.qm@web65715.mail.ac4.yahoo.com> I tried registering with ideasip since the ideasip echo test number on the ekiga fun numbers list worked. But ekiga will not work with ideasip. I also tried iptel as one poster suggested. It works just fine. --- On Thu, 5/19/11, J?nis Ruk??ns wrote: > From: J?nis Ruk??ns > Subject: Re: [Ekiga-list] ekiga behind two routers > To: "Ekiga mailing list" > Date: Thursday, May 19, 2011, 2:25 PM > Hello, Damien > > On Thu, May 19, 2011 at 1:26 PM, Damien Sandras > wrote: > > The problem is that if we do not check for private IP > addresses, users will > > be able to call eachother, but RTP trafic will not go > through. > > > > That means users will complain of "no audio" > problems... > > > > Is that preferable ? > > In my opinion it's better to have "no audio" in some cases > rather than > not being able to use the service at all. Rejecting private > IPs in > Contact header is perfectly reasonable (although the > response > shouldn't be 6xx, but I admit that's nitpicking), but a > private IP in > Via should be fine. > > My reasoning is that if the client lists it's public > address in > Contact, then apparently it *is* employing some kind of NAT > traversal, > hopefully for RTP as well. Also a private IP in Via allows > the server > to work around the tricky case of both users being behind > the same NAT > (the server can send a redirect to the private IP). > > Thanks, > -- > Ian > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From jvankort at gmx.com Thu May 26 06:53:17 2011 From: jvankort at gmx.com (Jan Van_Kort) Date: Wed, 25 May 2011 23:53:17 -0700 Subject: [Ekiga-list] How to get ATA phone to ring? In-Reply-To: <4DDBA1E7.6060808@pu-pm.univ-fcomte.fr> References: <1306184726394-3545491.post@n4.nabble.com> <4DDBA1E7.6060808@pu-pm.univ-fcomte.fr> Message-ID: <4DDDF8DD.9020909@gmx.com> Router has ports 5060-5061 udp, 53-53 and 69-69 udp and 10000-20000 udp and all forwarded to ATA IP. ATA is set to a static IP . I've downloaded every paper I can find on the subject. I hired a so-called specialist in 'SIP' phones to come and help. We even tried making the IP as the DMZ on router. Phone still does not receive calls. Do Diamondcard personal #'s require a computer running Ekiga on network in order for ATA phone to function properly? People on our CableTV system are using Skype and Vonage with no special equipment or effort on the cable systems part to make their phones work. Eugen Dedu wrote: > On 23/05/11 23:05, jvankort wrote: >> I bought a diamondcard personal number. >> I bought a Linksys PAP2 ATA. >> I bought a phone to connect to the ATA. >> Incoming calls loop around the planet and ring the phone at my house >> instead >> of where the ATA phone is located. >> >> Result is, I can call out but no-one can call me. How can I make >> this work? > > I would say that this is a parameter of Internet provider, have you > looked at your router configuration? > From bnc at netspeed.com.au Fri May 27 00:28:08 2011 From: bnc at netspeed.com.au (bnc) Date: Fri, 27 May 2011 10:28:08 +1000 Subject: [Ekiga-list] How to get ATA phone to ring? In-Reply-To: <4DDDF8DD.9020909@gmx.com> References: <1306184726394-3545491.post@n4.nabble.com> <4DDBA1E7.6060808@pu-pm.univ-fcomte.fr> <4DDDF8DD.9020909@gmx.com> Message-ID: <20110527102808.71b068da@bnc.JUSTUS> Jan, I currently run an ATA at home similar to yours, I just set the ATA up and it just worked, no need to forward anything. Then I tried to do what you want to do, except that I just wanted to use ekiga. I believe I got the same issue, but do not think it is a problem. If you look at it from the ISP's perspective they end up with a voice packet that has to be delivered, they see a registered device(your home phone) and send it to port 5060. The fact that you then come along and register another IP address does not matter because the ISP will only recognise the first one. i.e. all incoming calls for that phone number will go to the first IP address. The way you could prove this is to turn the home phone off and see if you get incoming calls. The way I resolved the problem was to get a new number for the machine I take on the road. My isp allows free calls on the same network so I can phone home for free:) YMMV Brian PS. my current setup on the road is EEEPC-EKIGA-3GWireless-PhoneNo. On Wed, 25 May 2011 23:53:17 -0700 Jan Van_Kort wrote: > Router has ports 5060-5061 udp, 53-53 and 69-69 udp and 10000-20000 > udp and all forwarded to ATA IP. ATA is set to a static IP . I've > downloaded every paper I can find on the subject. I hired a > so-called specialist in 'SIP' phones to come and help. We even tried > making the IP as the DMZ on router. Phone still does not receive > calls. > > Do Diamondcard personal #'s require a computer running Ekiga on > network in order for ATA phone to function properly? > People on our CableTV system are using Skype and Vonage with no > special equipment or effort on the cable systems part to make their > phones work. > > Eugen Dedu wrote: > > On 23/05/11 23:05, jvankort wrote: > >> I bought a diamondcard personal number. > >> I bought a Linksys PAP2 ATA. > >> I bought a phone to connect to the ATA. > >> Incoming calls loop around the planet and ring the phone at my > >> house instead > >> of where the ATA phone is located. > >> > >> Result is, I can call out but no-one can call me. How can I make > >> this work? > > > > I would say that this is a parameter of Internet provider, have you > > looked at your router configuration? > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From stuart at gathman.org Fri May 27 03:13:54 2011 From: stuart at gathman.org (Stuart Gathman) Date: Thu, 26 May 2011 23:13:54 -0400 Subject: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client In-Reply-To: References: <4DD58427.6020606@pu-pm.univ-fcomte.fr> <20110519211558.GA13495@simba> <20110519213049.GB13495@simba> <20110519225652.GA13909@simba> <20110520080201.GA16495@simba> <20110524201116.GA13058@simba> <20110525070603.GA15810@simba> Message-ID: <4DDF16F2.3000403@gathman.org> On 05/25/2011 01:52 PM, J?nis Ruk??ns wrote: > If the phone supports either STUN or ICE, it is usually indicated by a > public IP in the Contact address. I'm pretty sure diamondcard.us have > a relay server, thus they don't care whether the IP is public or > private. Ekiga.net doesn't have a relay server, therefore it's > reasonable that it rejects registrations with private IPs. But only if the private IP is in the Contact address. In the cases we are complaining about, the Contact is a public IP, but ekiga.net rejects it anyway. From tiberiu.breana at gmail.com Fri May 27 18:05:45 2011 From: tiberiu.breana at gmail.com (Tiberiu Breana) Date: Fri, 27 May 2011 21:05:45 +0300 Subject: [Ekiga-list] Modifying sent SDP data? Message-ID: Hello. I'm doing a project that tries to connect a User Agent (Ekiga), an openSIPS server and a freeRADIUS server. My tutor wants me to find out if we can customize the data transfer between the user agent and the SIP server. How open-source is Ekiga? Can I, for example, somehow modify the SDP data sent (like adding new parameters)? If so, how? Through config files or by modifying source code? Any information is greatly appreciated. Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: From zoubidoo at hotmail.com Fri May 27 11:02:44 2011 From: zoubidoo at hotmail.com (Parker Jones) Date: Fri, 27 May 2011 23:02:44 +1200 Subject: [Ekiga-list] Screen-sharing Message-ID: Hello, Does Ekiga have any plans for screen-sharing? It doesn't appear to be mentioned in the features list or the roadmap. Skype has screen-sharing, so users have to give up this functionality if they switch to Ekiga. Cheers, Parker -------------- next part -------------- An HTML attachment was scrubbed... URL: From mikecmour at yahoo.com Sat May 28 02:02:05 2011 From: mikecmour at yahoo.com (Michael Seymour) Date: Fri, 27 May 2011 19:02:05 -0700 (PDT) Subject: [Ekiga-list] Compatibility Message-ID: <619845.59237.qm@web112020.mail.gq1.yahoo.com> Hi, will this work on my android phone? I am running Android 2.2. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From davekoelmeyer at me.com Sat May 28 03:51:30 2011 From: davekoelmeyer at me.com (Dave Koelmeyer) Date: Sat, 28 May 2011 15:51:30 +1200 Subject: [Ekiga-list] Compatibility In-Reply-To: <619845.59237.qm@web112020.mail.gq1.yahoo.com> References: <619845.59237.qm@web112020.mail.gq1.yahoo.com> Message-ID: <4DE07142.4080301@me.com> On 28/05/11 02:02 PM, Michael Seymour wrote: > Hi, will this work on my android phone? I am running Android 2.2. > Thank you. > > Hi Michael, There isn't a native Ekiga client for Android, but there are several compatible SIP clients you can use. See here for more information: http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android Cheers, -- Dave Koelmeyer http://davekoelmeyer.wordpress.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From Bart.Vandewoestyne at telenet.be Sat May 28 08:38:29 2011 From: Bart.Vandewoestyne at telenet.be (Bart Vandewoestyne) Date: Sat, 28 May 2011 10:38:29 +0200 Subject: [Ekiga-list] Compatibility In-Reply-To: <619845.59237.qm@web112020.mail.gq1.yahoo.com> References: <619845.59237.qm@web112020.mail.gq1.yahoo.com> Message-ID: <20110528083829.GA2090@simba> On Fri, May 27, 2011 at 07:02:05PM -0700, Michael Seymour wrote: > Hi, will this work on my android phone? I am running Android 2.2. > Thank you. See http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android Regards, Bart -- "Share what you know. Learn what you don't." From Eugen.Dedu at pu-pm.univ-fcomte.fr Sat May 28 09:19:39 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sat, 28 May 2011 11:19:39 +0200 Subject: [Ekiga-list] Modifying sent SDP data? In-Reply-To: References: Message-ID: <4DE0BE2B.90208@pu-pm.univ-fcomte.fr> On 27/05/11 20:05, Tiberiu Breana wrote: > Hello. I'm doing a project that tries to connect a User Agent (Ekiga), an > openSIPS server and a freeRADIUS server. > > My tutor wants me to find out if we can customize the data transfer between > the user agent and the SIP server. > How open-source is Ekiga? Can I, for example, somehow modify the SDP data > sent (like adding new parameters)? > If so, how? Through config files or by modifying source code? > > Any information is greatly appreciated. Thanks! There is no config file. You need to modify opal library. See the ekiga wiki for how to compile ptlib, opal and ekiga. -- Eugen From Eugen.Dedu at pu-pm.univ-fcomte.fr Sat May 28 09:20:45 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Sat, 28 May 2011 11:20:45 +0200 Subject: [Ekiga-list] Screen-sharing In-Reply-To: References: Message-ID: <4DE0BE6D.2060304@pu-pm.univ-fcomte.fr> On 27/05/11 13:02, Parker Jones wrote: > > Hello, > > Does Ekiga have any plans for screen-sharing? It doesn't appear to be mentioned in the features list or the roadmap. > > Skype has screen-sharing, so users have to give up this functionality if they switch to Ekiga. It is a useful functionality. Please make a bug report so that we do not forget it. -- Eugen From tiberiu.breana at gmail.com Mon May 30 15:34:34 2011 From: tiberiu.breana at gmail.com (Tiberiu Breana) Date: Mon, 30 May 2011 18:34:34 +0300 Subject: [Ekiga-list] Modifying sent SDP data? In-Reply-To: <4DE0BE2B.90208@pu-pm.univ-fcomte.fr> References: <4DE0BE2B.90208@pu-pm.univ-fcomte.fr> Message-ID: Thanks for your reply. I've browsed almost all the sources and couldn't find anything related to packet construction. Where exactly can I find this? There is no config file. You need to modify opal library. See the ekiga > wiki for how to compile ptlib, opal and ekiga. > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ncassanova11 at gmail.com Mon May 30 16:08:47 2011 From: ncassanova11 at gmail.com (Nikolai Cassanova) Date: Mon, 30 May 2011 12:08:47 -0400 Subject: [Ekiga-list] Nikolai Cassanova: Question: with Microsoft buying Skype and people looking for an alternative to Skype will sip be the choice for people migrating away from skype In-Reply-To: References: Message-ID: Hi, quick question read article on zdnet that talks about alternatives to Skype now that some users are getting fed up with Skype and the recent news that Microsoft bought Skype have some users thinking they should leave Skype and look for another alternative to VoIP. In the article the author brings up the other choices and mentions sip (Ekiga, iptel and other sip providers) and also xmpp. Now here is my thing with people looking for an alternative to Skype shouldn't the best choice be sip as it is open, very simple to use and has the ability to call any other sip provider network, meaning you can call someone from Ekiga.net even though your sip provider is pbxes.org. Second question if sip is not number 1 alternative to Skype, why isn't it? I mean it basically very similar to Skype in that a user only needs to download sip client install the client and then register your sip address and tadaa you can instantly make calls to any other sip user and also send instant messages to other sip users. To me that is the same thing as Skype only thing sip is better b/c its open source and sip to sip no matter where you are in the world is free and you don't have to pay for it to call someone in another country as long as they are using sip its free. With that said is the reason for Skype's popularity even though there are alternatives, advertisement? Is Skype popular because it was advertised all over and that's why they have such a large user base? And If thats the case then should sip like ekiga be more advertised now to make people around the world know there are options to voip beside Skype? Also another point that I would like to make about sip is that it is more mobile and more people slowly but surely are starting to use sip clients on there smart phone, allowing cell phones with data plans to utilize voip. Also I feel with the new integration of an native sip client in android 2.3 os (gingerbread) on android cell phones that more people will start to use sip widely. Another thing to point out is that if google by chance uses google voice (which to me is a pbx system a little similar to asterisk when it comes to controlling where you want your phone calls directed to) in terms of sip portability by allowing google voice users to have there own sip address hosted by google (i.e: xxxxxxxxx at sip.voice.google.com) would also allow sip to boost numbers but that would all have to be up to google and how they decide to keep enhancing google voice. -------------- next part -------------- An HTML attachment was scrubbed... URL: From geo.cherchetout at laposte.net Tue May 31 09:05:24 2011 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 31 May 2011 11:05:24 +0200 Subject: [Ekiga-list] Missing library in Mandriva Message-ID: <4DE4AF54.1000607@laposte.net> Hello, I am trying to install Ekiga-3.2.7 in Mandriva 2010.2. Running ./configure, i get messages about missing libraries. 1) No package 'sigc++-2.0' found. Solved by urpmi libsigc++2.0-devel. 2) No package 'libebook-1.2' found. I have only libebook9 and not any devel package with libebook in his name found in known repositories. Where can i get this package from ? Or another compatible library ? From geo.cherchetout at laposte.net Tue May 31 12:09:19 2011 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 31 May 2011 14:09:19 +0200 Subject: [Ekiga-list] Missing library in Mandriva In-Reply-To: <4DE4AF54.1000607@laposte.net> References: <4DE4AF54.1000607@laposte.net> Message-ID: <4DE4DA6F.8000807@laposte.net> Le 31/05/2011 11:05, *geo cherchetout* a ?crit : > 2) No package 'libebook-1.2' found. I have only libebook9 and not any devel > package with libebook in his name found in known repositories. > > Where can i get this package from ? Or another compatible library ? I found that libedataserver-devel provides libebook-1.2.so but urpmi says this package (and libnspr-devel) can't be selected because they depend of packages older that installed ones. What ones is not indicated. :-( Is it relevant to force installation with --allow-nodeps option ? Is libebook-1.2 really essential ? If not, what option could i give to configure for it to ignore libebook-1.2 ? From craig at southeren.com Mon May 30 17:41:53 2011 From: craig at southeren.com (Craig Southeren) Date: Mon, 30 May 2011 10:41:53 -0700 Subject: [Ekiga-list] Modifying sent SDP data? In-Reply-To: References: <4DE0BE2B.90208@pu-pm.univ-fcomte.fr> Message-ID: <4DE3D6E1.9080303@southeren.com> These kinds of questions are better asked on the Opal list (opalvoip at sourceforge.net) which is the SIP library used by Ekiga. There is a way to set arbitrary headers in the outgoing SIP using URL options. I can't remember the exact syntax - robertj at voxlucida.com.au will be able to help you. Craig On 30/05/2011 8:34 AM, Tiberiu Breana wrote: > Thanks for your reply. I've browsed almost all the sources and > couldn't find anything related to packet construction. Where exactly > can I find this? > > > There is no config file. You need to modify opal library. See > the ekiga wiki for how to compile ptlib, opal and ekiga. > -- > Eugen > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- An HTML attachment was scrubbed... URL: From Eugen.Dedu at pu-pm.univ-fcomte.fr Tue May 31 14:04:26 2011 From: Eugen.Dedu at pu-pm.univ-fcomte.fr (Eugen Dedu) Date: Tue, 31 May 2011 16:04:26 +0200 Subject: [Ekiga-list] Missing library in Mandriva In-Reply-To: <4DE4DA6F.8000807@laposte.net> References: <4DE4AF54.1000607@laposte.net> <4DE4DA6F.8000807@laposte.net> Message-ID: <4DE4F56A.4020300@pu-pm.univ-fcomte.fr> On 31/05/11 14:09, geo cherchetout wrote: > Le 31/05/2011 11:05, *geo cherchetout* a ?crit : > >> 2) No package 'libebook-1.2' found. I have only libebook9 and not any devel >> package with libebook in his name found in known repositories. >> >> Where can i get this package from ? Or another compatible library ? > > I found that libedataserver-devel provides libebook-1.2.so but urpmi says > this package (and libnspr-devel) can't be selected because they depend of > packages older that installed ones. What ones is not indicated. :-( > > Is it relevant to force installation with --allow-nodeps option ? > > Is libebook-1.2 really essential ? If not, what option could i give to > configure for it to ignore libebook-1.2 ? libebook is not essential, it is about integration with evolution. Add --disable-eds to configure and tell us if it works. -- Eugen From geo.cherchetout at laposte.net Tue May 31 14:39:11 2011 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 31 May 2011 16:39:11 +0200 Subject: [Ekiga-list] Missing library in Mandriva In-Reply-To: <4DE4F56A.4020300@pu-pm.univ-fcomte.fr> References: <4DE4AF54.1000607@laposte.net> <4DE4DA6F.8000807@laposte.net> <4DE4F56A.4020300@pu-pm.univ-fcomte.fr> Message-ID: <4DE4FD8F.9010204@laposte.net> Le 31/05/2011 16:04, *Eugen Dedu* a ?crit : >> Is libebook-1.2 really essential ? If not, what option could i give to >> configure for it to ignore libebook-1.2 ? > > libebook is not essential, it is about integration with evolution. Add > --disable-eds to configure and tell us if it works. $ PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --disable-eds works. :-) Thank you for the help. From gio_6b at yahoo.it Tue May 31 17:01:40 2011 From: gio_6b at yahoo.it (Giorgio) Date: Tue, 31 May 2011 19:01:40 +0200 Subject: [Ekiga-list] Missing library in Mandriva In-Reply-To: <4DE4FD8F.9010204@laposte.net> References: <4DE4AF54.1000607@laposte.net> <4DE4DA6F.8000807@laposte.net> <4DE4F56A.4020300@pu-pm.univ-fcomte.fr> <4DE4FD8F.9010204@laposte.net> Message-ID: <4DE51EF4.50807@yahoo.it> to geo cherchetout I'm using Mandriva 2010.2 64 bit, your is 32 or 64 bit ? I've tried Ekiga 3.2.6 from repositories with no luck. Echo isn't working. I'm interested in 3.2.7 because I hope it can solve my audio problems. Please let me know how 3.2.7 works in your Mandriva. Thanks. Il 31/05/2011 16:39, geo cherchetout ha scritto: > Le 31/05/2011 16:04, *Eugen Dedu* a ?crit : > >>> Is libebook-1.2 really essential ? If not, what option could i give to >>> configure for it to ignore libebook-1.2 ? >> libebook is not essential, it is about integration with evolution. Add >> --disable-eds to configure and tell us if it works. > $ PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --disable-eds > > works. :-) Thank you for the help. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From geo.cherchetout at laposte.net Tue May 31 18:05:56 2011 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 31 May 2011 20:05:56 +0200 Subject: [Ekiga-list] Missing library in Mandriva In-Reply-To: <4DE51EF4.50807@yahoo.it> References: <4DE4AF54.1000607@laposte.net> <4DE4DA6F.8000807@laposte.net> <4DE4F56A.4020300@pu-pm.univ-fcomte.fr> <4DE4FD8F.9010204@laposte.net> <4DE51EF4.50807@yahoo.it> Message-ID: <4DE52E04.9070604@laposte.net> Le 31/05/2011 19:01, *Giorgio* wrote : > to geo cherchetout > > I'm using Mandriva 2010.2 64 bit, your is 32 or 64 bit ? Mine is 32 bits. > I've tried Ekiga 3.2.6 from repositories with no luck. Echo isn't working. I had also many problems like this one with 3.2.6 and was hopping 3.2.7 resolve them. > I'm interested in 3.2.7 because I hope it can solve my audio problems. > Please let me know how 3.2.7 works in your Mandriva. For me it's not better than 3.2.6 but I can't blame Ekiga because my Mandriva 2010.2 is very "customized" and also my router. I suspect also a bug in gconf-editor because some changes in ekiga configuration seems not always taken in account... From geo.cherchetout at laposte.net Tue May 31 20:34:46 2011 From: geo.cherchetout at laposte.net (geo cherchetout) Date: Tue, 31 May 2011 22:34:46 +0200 Subject: [Ekiga-list] Can't connect to robot sipomatic Message-ID: <4DE550E6.2070501@laposte.net> Hello, Ekiga 3.2.7 and sipomatic are running on the same machine with Mandriva 2010.2 32 bits distribution. Stun is disabled. Video is disabled. I am not registered to any registrar. Only sound codecs PCMA and PCMU are activated and not any video codec. Sound is working. When I call sip:robot at 127.0.0.1:5064 I only get this message after some time at the bottom of main ekiga window: "Impossible de se connecter au correspondant distant". The messages gotten in Terminal during an ekiga session with one such call are recorded in this file: http://www.cijoint.fr/cjlink.php?file=cj201105/cijjTlCgQC.txt Same problem with Ekiga 3.2.6 on another machine with the same distribution Mandriva. No problem on the two machines with Linphone and Twinkle to hear Simon's voice. What is wrong in my Ekiga configuration or my Mandriva ? From gandalfinium at yahoo.fr Tue May 31 20:53:41 2011 From: gandalfinium at yahoo.fr (Gandalfinium Le blanc) Date: Tue, 31 May 2011 21:53:41 +0100 (BST) Subject: [Ekiga-list] USB Hercules Muse LT3 Message-ID: <890951.12003.qm@web29102.mail.ird.yahoo.com> Hi, I'm using this marvellous software (Ekiga) with an external sound card : the USB Hercules Gamesurround Muse XL LT3. I've configured the audio driver of ekiga to use this card specifically.? Emission of sound with mic ou line if ok but reception of sound is inaudible. It makes a incomprehensible creepy voice. I'm on Debian squeeze, I tested with a good server in gigabyte LAN still the same. I tested with the internal sound card everything was OK. Unfortunately I have to use an external sound card, such as muse. Do you think it's a codec problem that could not be sync with rate sample of the card ? Is there a specific configuration to improve the reception of sound via USB sound card ? Thank for answer -------------- next part -------------- An HTML attachment was scrubbed... URL: From arena.g at videotron.ca Tue May 31 21:36:21 2011 From: arena.g at videotron.ca (Gaetano Arena) Date: Tue, 31 May 2011 17:36:21 -0400 Subject: [Ekiga-list] unsuscribe Message-ID: <1306877781.2405.0.camel@Lilli> -------------- next part -------------- An HTML attachment was scrubbed... URL: