From arsphl at Davidbowie.com Mon Oct 1 01:05:18 2007 From: arsphl at Davidbowie.com (Philippe Laliberte) Date: Mon, 01 Oct 2007 02:05:18 +0100 Subject: [Ekiga-list] Fullscreen In-Reply-To: <47002FC8.8000302@emich.edu> References: <47002FC8.8000302@emich.edu> Message-ID: <470047CE.2050406@Davidbowie.com> Hello, Well I do not get a distorted image with gspca . I tried it with both an old Logictec Express and a Pixart. That is with v4l not v4l2. The resolution is pretty bad with both, but I am trying to understand why. Might be simply that they are piece of junk. I found one in the trash, the other paid 12? for it. Cheers, Bus 001 Device 004: ID 046d:0928 Logitech, Inc. Quickcam Express Bus 003 Device 003: ID 093a:2468 Pixart Imaging, Inc. Easy Snap Snake Eye WebCam P.S. Chris, you can make your signature as an attachment, it is more convivial for those that do not have a GPG/PGP plugin. Alternatively you can get for free a formal Internet personal certificate. It is accepted by most email browsers, which is better because they can encrypt back easily any answer they might have. Christopher L Tubbs II wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > My webcam works in full screen mode: Logitech QuickCam Communicate STX > (using gspca driver, although it should be noted that until the gspca > driver is patched, or until Ekiga supports more resolutions, this camera > will crop the image instead of scale it). > > However, a separate issue I've noticed with fullscreen is that Ekiga > scales the video to match the dimensions of the screen. This is > problematic for widescreen displays because it stretches the picture, > distorting the image. My suggestion is that the scaling should happen to > the largest possible image size that maintains the same image ratio, and > should fill in the leftover with black space (this is how most video > programs nowadays handle widescreen displays). > > Chris > > RazaMetaL | Only The Good Die Young wrote: > >> Hi, >> >> What model of webcams are supporting the fullscreen view? >> >> I've one logitech quickcam pro 4000 that can not use the fullscreen >> view. I'm using the pwc module for this webcam. >> >> Regards, >> >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iD8DBQFHAC/IyQYCx13q+8oRAkIVAKCuXp27oo7/U+26oR5D5UkWcLEUOgCfZZHD > HL520BH6yHVX1lXKuV/zGSs= > =JvNW > -----END PGP SIGNATURE----- > _______________________________________________ > 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: -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 141 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 3323 bytes Desc: S/MIME Cryptographic Signature URL: From ctubbsii at emich.edu Mon Oct 1 02:32:21 2007 From: ctubbsii at emich.edu (Christopher L Tubbs II) Date: Sun, 30 Sep 2007 22:32:21 -0400 Subject: [Ekiga-list] Fullscreen In-Reply-To: <470047CE.2050406@Davidbowie.com> References: <47002FC8.8000302@emich.edu> <470047CE.2050406@Davidbowie.com> Message-ID: <47005C35.1090700@emich.edu> The distortion I'm talking about is when the image is stretched across the entire widescreen. I don't get this with other software that understands widescreen, but I do with Ekiga. It was my understanding that this was because Ekiga takes the image from the stream and just stretches it for fullscreen mode. Perhaps it works differently? If you're not getting a distorted (stretched image), I must ask what your fullscreen dimensions are? gspca drivers ONLY work with v4l, not v4l2, AFAIK. But this shouldn't make a difference, b/c Ekiga handles both, and from what I understand, the system calls are different, but the image quality should be the same with v4l or v4l2. As for the resolution issue you mentioned, Ekiga version 2 doesn't support high resolutions, even though your camera does, so that might have a lot to do with your fullscreen quality. I recently asked about different resolution support and was told that version 3 will include support for higher resolutions. Chris Philippe Laliberte wrote: > Hello, > > Well I do not get a distorted image with gspca . I tried it with both an > old Logictec Express and a Pixart. That is with v4l not v4l2. The > resolution is pretty bad with both, but I am trying to understand why. > Might be simply that they are piece of junk. I found one in the trash, > the other paid 12? for it. > > Cheers, > Bus 001 Device 004: ID 046d:0928 Logitech, Inc. Quickcam Express > Bus 003 Device 003: ID 093a:2468 Pixart Imaging, Inc. Easy Snap Snake > Eye WebCam > > P.S. Chris, you can make your signature as an attachment, it is more > convivial for those that do not have a GPG/PGP plugin. Alternatively you > can get for free a formal Internet personal certificate. It is accepted > by most email browsers, which is better because they can encrypt back > easily any answer they might have. > > > > Christopher L Tubbs II wrote: > My webcam works in full screen mode: Logitech QuickCam Communicate STX > (using gspca driver, although it should be noted that until the gspca > driver is patched, or until Ekiga supports more resolutions, this camera > will crop the image instead of scale it). > > However, a separate issue I've noticed with fullscreen is that Ekiga > scales the video to match the dimensions of the screen. This is > problematic for widescreen displays because it stretches the picture, > distorting the image. My suggestion is that the scaling should happen to > the largest possible image size that maintains the same image ratio, and > should fill in the leftover with black space (this is how most video > programs nowadays handle widescreen displays). > > Chris > > RazaMetaL | Only The Good Die Young wrote: > >>>> Hi, >>>> >>>> What model of webcams are supporting the fullscreen view? >>>> >>>> I've one logitech quickcam pro 4000 that can not use the fullscreen >>>> view. I'm using the pwc module for this webcam. >>>> >>>> Regards, >>>> >>>> _______________________________________________ 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 -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 251 bytes Desc: OpenPGP digital signature URL: From zach at zzelinski.com Mon Oct 1 03:23:28 2007 From: zach at zzelinski.com (Zachary Zelinski) Date: Sun, 30 Sep 2007 20:23:28 -0700 Subject: [Ekiga-list] Ekiga 2.0.11 finally released In-Reply-To: <1191059165.4146.8.camel@scorpion> References: <1190927012.4162.9.camel@scorpion> <18662247.281191059227961.OPEN-XCHANGE.WebMail.nobody@sam> <1191059165.4146.8.camel@scorpion> Message-ID: <86e56ee40709302023h5a4810aayc896270502f9c50c@mail.gmail.com> What is sid? People keep referencing it, but I have no idea where this is. Is this where i might find debian packages for ekiga? On 9/29/07, Damien Sandras wrote: > > > Le samedi 29 septembre 2007 ? 10:47 +0100, Michael Stockenhuber a > ?crit : > > Thank you for that. > > > > Do you plan to have a debian package as well? > > Cheers > > They are already in sid. Mirroring on ekiga.org is coming soon. > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > 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 ambrose at vrvl.net Mon Oct 1 03:37:04 2007 From: ambrose at vrvl.net (Ambrose Andrews) Date: Mon, 1 Oct 2007 13:37:04 +1000 Subject: [Ekiga-list] Ekiga 2.0.11 finally released In-Reply-To: <86e56ee40709302023h5a4810aayc896270502f9c50c@mail.gmail.com> References: <1190927012.4162.9.camel@scorpion> <18662247.281191059227961.OPEN-XCHANGE.WebMail.nobody@sam> <1191059165.4146.8.camel@scorpion> <86e56ee40709302023h5a4810aayc896270502f9c50c@mail.gmail.com> Message-ID: <20b1e36e0709302037o283e7ac2q18db1f462f4243ec@mail.gmail.com> 'sid' is debian unstable. debian is three distributions in one: stable, testing and unstable. packages are first introduced into unstable and if they survive a certain amount of time in 'unstable' without any serious bugs against them, they become eligible to enter the 'testing' repository. 'sid' is the nickname given to the (permanently) unstable repository. every once in a while 'testing' is frozen and much work devoted to stabilising and bugfixing it until it is considered rock-solid, at which point it becomes a 'stable' release. 'stable' is a more thoroughly tested and stabilised static set of packages released periodically from the primordial soup described earlier. as soon as a new stable is released, software bubbles up from unstable into testing again, and the cycle continues. -AA. On 01/10/2007, Zachary Zelinski wrote: > What is sid? People keep referencing it, but I have no idea where this is. > Is this where i might find debian packages for ekiga? -- Ambrose Andrews LPO box 8274 ANU Canberra ACT 2601 Australia http://www.vrvl.net/~ambrose/ mailto:ambrose at vrvl.net home:+61_262305976 work:+61_261256749 mobile:+61_415544621 irc:{undernet|freenode|oftc}:znalo xmpp:ambrose at jabber.fsfe.org sip:znalo at ekiga.net CE38 8B79 C0A7 DF4A 4F54 E352 2647 19A1 DB3B F823 556A 6D19 0904 827C 9DB8 3697 32D0 1E11 403F 2BE1 From philippel at aqiii.org Mon Oct 1 08:14:35 2007 From: philippel at aqiii.org (philippe Laliberte) Date: Mon, 01 Oct 2007 09:14:35 +0100 Subject: [Ekiga-list] Fullscreen In-Reply-To: <47005C35.1090700@emich.edu> References: <47002FC8.8000302@emich.edu> <470047CE.2050406@Davidbowie.com> <47005C35.1090700@emich.edu> Message-ID: <4700AC6B.5040709@aqiii.org> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: philippel.vcf Type: text/x-vcard Size: 139 bytes Desc: not available URL: From pratiksha.powar at onmobile.com Mon Oct 1 09:44:18 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Mon, 01 Oct 2007 15:14:18 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1190383204.4106.27.camel@scorpion> References: <1190365436.3362.27.camel@localhost.localdomain> <1190383204.4106.27.camel@scorpion> Message-ID: <1191231858.3359.26.camel@localhost.localdomain> Hi Damein, Does Ekiga 2.0.9 or above use Codec-96 for DTMF encoding? Please provide this information as early as possible. Thanks, Pratiksha On Fri, 2007-09-21 at 16:00 +0200, Damien Sandras wrote: > Le vendredi 21 septembre 2007 ? 14:33 +0530, Pratiksha Powar a ?crit : > > Hi Everybody, > > > > I'm using Ekiga for a corporate project. > > Using Ekiga I connect to a local server in my company which > > runs voice applications. I want to use Ekiga to test these > > applications. > > > > I use sip addresses like 123 at 172.16.18.69 etc. > > The server is unable to understand the DTMF PayLoad because the codec > > used by Ekiga is 101 and the one supported is 96. > > > > I receive the following error when i run : > > > > ekiga -d 2 -c 123 at 172.16.18.69 > > > > 2007/09/21 14:28:12.849 0:11.431 SIP Transport:a2de7c8 SDP > > Media attribute rtpmap found for unknown RTP type [pt=96] > > > > Following is the server's log: > > INVITE sip:123 at 172.16.18.69 SIP/2.0 > > Date: Thu, 20 Sep 2007 10:33:47 GMT > > CSeq: 1 INVITE > > Via: SIP/2.0/UDP > > 172.16.18.92:5063;branch=z9hG4bK34ff8fa3-d265-dc11-996c-0019b97d3b5d;rport > > User-Agent: Ekiga/2.0.2 > > From: "Pratiksha Powar" > > ;tag=2c218fa3-d265-dc11-996c-0019b97d3b5d > > Call-ID: 76188fa3-d265-dc11-996c-0019b97d3b5d at Pratiksha > > To: > > Contact: > > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > > Content-Type: application/sdp > > Content-Length: 368 > > Max-Forwards: 70 > > > > v=0 > > o=- 1190284427 1190284427 IN IP4 172.16.18.92 > > s=Opal SIP Session > > c=IN IP4 172.16.18.92 > > t=0 0 > > m=audio 5004 RTP/AVP 101 114 115 3 107 110 0 8 > > a=rtpmap:101 telephone-event/8000 > > a=fmtp:101 0-15 > > a=rtpmap:114 SPEEX/16000 > > a=rtpmap:115 iLBC/8000 > > a=rtpmap:3 GSM/8000 > > a=rtpmap:107 MS-GSM/8000 > > a=rtpmap:110 SPEEX/8000 > > a=rtpmap:0 PCMU/8000 > > a=rtpmap:8 PCMA/8000 > > > > I don't know much about codecs. > > Is there a version of Ekiga which can help me solve this problem? > > Currently I'm using Ekiga 2.0.2 on Gnome 2.16. > > Ekiga was a part of the CentOS 5.0 distribution. > > > > You should upgrade to at least Ekiga 2.0.9 and upload a full -d 4 output > somewhere. We will check it out. -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From dsandras at seconix.com Mon Oct 1 09:44:57 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 01 Oct 2007 11:44:57 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191231858.3359.26.camel@localhost.localdomain> References: <1190365436.3362.27.camel@localhost.localdomain> <1190383204.4106.27.camel@scorpion> <1191231858.3359.26.camel@localhost.localdomain> Message-ID: <1191231897.4147.18.camel@scorpion> Hello, Le lundi 01 octobre 2007 ? 15:14 +0530, Pratiksha Powar a ?crit : > Hi Damein, > > Does Ekiga 2.0.9 or above use Codec-96 for DTMF encoding? 96 is the payload type. The Payload type is dynamic for RFC2833. > Please provide this information as early as possible. > > Thanks, > Pratiksha > > On Fri, 2007-09-21 at 16:00 +0200, Damien Sandras wrote: > > Le vendredi 21 septembre 2007 ? 14:33 +0530, Pratiksha Powar a ?crit : > > > Hi Everybody, > > > > > > I'm using Ekiga for a corporate project. > > > Using Ekiga I connect to a local server in my company which > > > runs voice applications. I want to use Ekiga to test these > > > applications. > > > > > > I use sip addresses like 123 at 172.16.18.69 etc. > > > The server is unable to understand the DTMF PayLoad because the codec > > > used by Ekiga is 101 and the one supported is 96. > > > > > > I receive the following error when i run : > > > > > > ekiga -d 2 -c 123 at 172.16.18.69 > > > > > > 2007/09/21 14:28:12.849 0:11.431 SIP Transport:a2de7c8 SDP > > > Media attribute rtpmap found for unknown RTP type [pt=96] > > > > > > Following is the server's log: > > > INVITE sip:123 at 172.16.18.69 SIP/2.0 > > > Date: Thu, 20 Sep 2007 10:33:47 GMT > > > CSeq: 1 INVITE > > > Via: SIP/2.0/UDP > > > 172.16.18.92:5063;branch=z9hG4bK34ff8fa3-d265-dc11-996c-0019b97d3b5d;rport > > > User-Agent: Ekiga/2.0.2 > > > From: "Pratiksha Powar" > > > ;tag=2c218fa3-d265-dc11-996c-0019b97d3b5d > > > Call-ID: 76188fa3-d265-dc11-996c-0019b97d3b5d at Pratiksha > > > To: > > > Contact: > > > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > > > Content-Type: application/sdp > > > Content-Length: 368 > > > Max-Forwards: 70 > > > > > > v=0 > > > o=- 1190284427 1190284427 IN IP4 172.16.18.92 > > > s=Opal SIP Session > > > c=IN IP4 172.16.18.92 > > > t=0 0 > > > m=audio 5004 RTP/AVP 101 114 115 3 107 110 0 8 > > > a=rtpmap:101 telephone-event/8000 > > > a=fmtp:101 0-15 > > > a=rtpmap:114 SPEEX/16000 > > > a=rtpmap:115 iLBC/8000 > > > a=rtpmap:3 GSM/8000 > > > a=rtpmap:107 MS-GSM/8000 > > > a=rtpmap:110 SPEEX/8000 > > > a=rtpmap:0 PCMU/8000 > > > a=rtpmap:8 PCMA/8000 > > > > > > I don't know much about codecs. > > > Is there a version of Ekiga which can help me solve this problem? > > > Currently I'm using Ekiga 2.0.2 on Gnome 2.16. > > > Ekiga was a part of the CentOS 5.0 distribution. > > > > > > > You should upgrade to at least Ekiga 2.0.9 and upload a full -d 4 output > > somewhere. We will check it out. > > > ============================== > DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. > Thank you - OnMobile Global Limited. > ============================== -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From pratiksha.powar at onmobile.com Mon Oct 1 09:56:51 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Mon, 01 Oct 2007 15:26:51 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191231897.4147.18.camel@scorpion> References: <1190365436.3362.27.camel@localhost.localdomain> <1190383204.4106.27.camel@scorpion> <1191231858.3359.26.camel@localhost.localdomain> <1191231897.4147.18.camel@scorpion> Message-ID: <1191232612.3359.30.camel@localhost.localdomain> Thanks for quick response. What does the PayLoad Type depend on? Can it be 101 sometimes and 96 sometimes? Does Ekiga see what kind of PayLoad type is supported by recipient system and then choose the PayLoad type? On Mon, 2007-10-01 at 11:44 +0200, Damien Sandras wrote: > Hello, > > Le lundi 01 octobre 2007 ? 15:14 +0530, Pratiksha Powar a ?crit : > > Hi Damein, > > > > Does Ekiga 2.0.9 or above use Codec-96 for DTMF encoding? > > 96 is the payload type. The Payload type is dynamic for RFC2833. > > > > Please provide this information as early as possible. > > > > Thanks, > > Pratiksha > > > > On Fri, 2007-09-21 at 16:00 +0200, Damien Sandras wrote: > > > Le vendredi 21 septembre 2007 ? 14:33 +0530, Pratiksha Powar a ?crit : > > > > Hi Everybody, > > > > > > > > I'm using Ekiga for a corporate project. > > > > Using Ekiga I connect to a local server in my company which > > > > runs voice applications. I want to use Ekiga to test these > > > > applications. > > > > > > > > I use sip addresses like 123 at 172.16.18.69 etc. > > > > The server is unable to understand the DTMF PayLoad because the codec > > > > used by Ekiga is 101 and the one supported is 96. > > > > > > > > I receive the following error when i run : > > > > > > > > ekiga -d 2 -c 123 at 172.16.18.69 > > > > > > > > 2007/09/21 14:28:12.849 0:11.431 SIP Transport:a2de7c8 SDP > > > > Media attribute rtpmap found for unknown RTP type [pt=96] > > > > > > > > Following is the server's log: > > > > INVITE sip:123 at 172.16.18.69 SIP/2.0 > > > > Date: Thu, 20 Sep 2007 10:33:47 GMT > > > > CSeq: 1 INVITE > > > > Via: SIP/2.0/UDP > > > > 172.16.18.92:5063;branch=z9hG4bK34ff8fa3-d265-dc11-996c-0019b97d3b5d;rport > > > > User-Agent: Ekiga/2.0.2 > > > > From: "Pratiksha Powar" > > > > ;tag=2c218fa3-d265-dc11-996c-0019b97d3b5d > > > > Call-ID: 76188fa3-d265-dc11-996c-0019b97d3b5d at Pratiksha > > > > To: > > > > Contact: > > > > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > > > > Content-Type: application/sdp > > > > Content-Length: 368 > > > > Max-Forwards: 70 > > > > > > > > v=0 > > > > o=- 1190284427 1190284427 IN IP4 172.16.18.92 > > > > s=Opal SIP Session > > > > c=IN IP4 172.16.18.92 > > > > t=0 0 > > > > m=audio 5004 RTP/AVP 101 114 115 3 107 110 0 8 > > > > a=rtpmap:101 telephone-event/8000 > > > > a=fmtp:101 0-15 > > > > a=rtpmap:114 SPEEX/16000 > > > > a=rtpmap:115 iLBC/8000 > > > > a=rtpmap:3 GSM/8000 > > > > a=rtpmap:107 MS-GSM/8000 > > > > a=rtpmap:110 SPEEX/8000 > > > > a=rtpmap:0 PCMU/8000 > > > > a=rtpmap:8 PCMA/8000 > > > > > > > > I don't know much about codecs. > > > > Is there a version of Ekiga which can help me solve this problem? > > > > Currently I'm using Ekiga 2.0.2 on Gnome 2.16. > > > > Ekiga was a part of the CentOS 5.0 distribution. > > > > > > > > > > You should upgrade to at least Ekiga 2.0.9 and upload a full -d 4 output > > > somewhere. We will check it out. > > > > > > ============================== > > DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. > > Thank you - OnMobile Global Limited. > > ============================== -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From dsandras at seconix.com Mon Oct 1 10:21:48 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 01 Oct 2007 12:21:48 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191232612.3359.30.camel@localhost.localdomain> References: <1190365436.3362.27.camel@localhost.localdomain> <1190383204.4106.27.camel@scorpion> <1191231858.3359.26.camel@localhost.localdomain> <1191231897.4147.18.camel@scorpion> <1191232612.3359.30.camel@localhost.localdomain> Message-ID: <1191234108.4147.22.camel@scorpion> Le lundi 01 octobre 2007 ? 15:26 +0530, Pratiksha Powar a ?crit : > Thanks for quick response. > > What does the PayLoad Type depend on? Nothing special. > Can it be 101 sometimes and 96 sometimes? Yes > Does Ekiga see what kind of PayLoad type is supported by recipient > system and then choose the PayLoad type? It depends if you are calling or not. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From geno999 at yahoo.com Tue Oct 2 17:44:45 2007 From: geno999 at yahoo.com (J. Rehbock) Date: Tue, 2 Oct 2007 10:44:45 -0700 (PDT) Subject: [Ekiga-list] Sound Problem In-Reply-To: <2791549.311191083446101.OPEN-XCHANGE.WebMail.nobody@sam> Message-ID: <247042.44697.qm@web33813.mail.mud.yahoo.com> Activating the Analog/Digital Output jack in the mixer does stop my non-Ekiga speech from coming immediately out of the speakers. However,I still get no results in the Ekiga Druid audio test. Any further thoughts? Tnx geno -------------------------- Michael Stockenhuber wrote: Hi, I had a similar problem in debian with a cs46xx sound card. The adc was switched off in kmix, switching it on sorted it. Cheers Michael On Wed 26.09.2007 17:06, geno wrote: >I am running a full-duplex Audigy SB0090 sound card under Debian 4.0r1. >Without Ekiga 2.0.9 running, anything spoken into the microphone comes >immediately out of the speakers. When I run the audio test in the >Configuration Druid, nothing comes out. There are no error messages. >So far I have been unable to find in the Debian repositories the "rec" >tool mentioned in the Ekiga documentation. Thoughts? Thanks. > >Geno >_______________________________________________ >ekiga-list mailing list >ekiga-list at gnome.org >http://mail.gnome.org/mailman/listinfo/ekiga-list Powered by Open-Xchange.com _______________________________________________ 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 sevmek at free.fr Tue Oct 2 17:55:34 2007 From: sevmek at free.fr (yannick) Date: Tue, 02 Oct 2007 19:55:34 +0200 Subject: [Ekiga-list] Fullscreen In-Reply-To: <4700AC6B.5040709@aqiii.org> References: <47002FC8.8000302@emich.edu> <470047CE.2050406@Davidbowie.com> <47005C35.1090700@emich.edu> <4700AC6B.5040709@aqiii.org> Message-ID: <1191347735.6744.75.camel@achille> Hi, it will be fixed in the new implementation of 3.00 which has completely different fullscreen support (DirectX and XVideo). You can give it a try: http://snapshots.voxgratia.org/ (this is development version!) Regards, Yannick Le lundi 01 octobre 2007 ? 09:14 +0100, philippe Laliberte a ?crit : > Hello, > > I do have a wide-screen and I definitively do not have the proportions > strongly changed in fullscreen mode. Sadly I can not take a screenshot > of it. > > I am in 1280 x 768, on an ATI Radeon card. Maybe the stretch is less > marked because I have a smaller screen? > > What I get is something like this: > > ------------------------------------------ > | | | | > | | | | > | | | | > | ------------------------|-------| > | | | > ----------------------------------------- > Cheers, > > > Christopher L Tubbs II wrote: > > The distortion I'm talking about is when the image is stretched across > > the entire widescreen. I don't get this with other software that > > understands widescreen, but I do with Ekiga. It was my understanding > > that this was because Ekiga takes the image from the stream and just > > stretches it for fullscreen mode. Perhaps it works differently? > > > > If you're not getting a distorted (stretched image), I must ask what > > your fullscreen dimensions are? > > > > gspca drivers ONLY work with v4l, not v4l2, AFAIK. But this shouldn't > > make a difference, b/c Ekiga handles both, and from what I understand, > > the system calls are different, but the image quality should be the same > > with v4l or v4l2. > > > > As for the resolution issue you mentioned, Ekiga version 2 doesn't > > support high resolutions, even though your camera does, so that might > > have a lot to do with your fullscreen quality. I recently asked about > > different resolution support and was told that version 3 will include > > support for higher resolutions. > > > > Chris > > > > Philippe Laliberte wrote: > > > > > Hello, > > > > > > Well I do not get a distorted image with gspca . I tried it with both an > > > old Logictec Express and a Pixart. That is with v4l not v4l2. The > > > resolution is pretty bad with both, but I am trying to understand why. > > > Might be simply that they are piece of junk. I found one in the trash, > > > the other paid 12? for it. > > > > > > Cheers, > > > Bus 001 Device 004: ID 046d:0928 Logitech, Inc. Quickcam Express > > > Bus 003 Device 003: ID 093a:2468 Pixart Imaging, Inc. Easy Snap Snake > > > Eye WebCam > > > > > > P.S. Chris, you can make your signature as an attachment, it is more > > > convivial for those that do not have a GPG/PGP plugin. Alternatively you > > > can get for free a formal Internet personal certificate. It is accepted > > > by most email browsers, which is better because they can encrypt back > > > easily any answer they might have. > > > > > > > > > > > > Christopher L Tubbs II wrote: > > > My webcam works in full screen mode: Logitech QuickCam Communicate STX > > > (using gspca driver, although it should be noted that until the gspca > > > driver is patched, or until Ekiga supports more resolutions, this camera > > > will crop the image instead of scale it). > > > > > > However, a separate issue I've noticed with fullscreen is that Ekiga > > > scales the video to match the dimensions of the screen. This is > > > problematic for widescreen displays because it stretches the picture, > > > distorting the image. My suggestion is that the scaling should happen to > > > the largest possible image size that maintains the same image ratio, and > > > should fill in the leftover with black space (this is how most video > > > programs nowadays handle widescreen displays). > > > > > > Chris > > > > > > RazaMetaL | Only The Good Die Young wrote: > > > > > > > > > > > > Hi, > > > > > > > > > > > > What model of webcams are supporting the fullscreen view? > > > > > > > > > > > > I've one logitech quickcam pro 4000 that can not use the fullscreen > > > > > > view. I'm using the pwc module for this webcam. > > > > > > > > > > > > Regards, > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > 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 > > > > > > > > > > > ____________________________________________________________________ > > > > _______________________________________________ > > 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 -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From 1.41421 at gmail.com Wed Oct 3 00:47:03 2007 From: 1.41421 at gmail.com (JCA) Date: Tue, 2 Oct 2007 17:47:03 -0700 Subject: [Ekiga-list] Ekiga under Slackware 12 Message-ID: I am trying to use Ekiga 2.0.9 under Slackware 12. The Ekiga package is one delivered with Gnome Slacky 2.18.3, from www.slacky.eu. So far I have noticed the following: Most of the time, Ekiga crashes immediately after establishing a connection with sip:500 at ekiga.net. Sometimes the connection succeeds all right, and everything works flawlessly (sound and video) until attempting to close the connection, at which point Ekiga crashes - again, most of the time, although not always. Before I start sending bug traces, I wonder if somebody could let me know if this behavior has been noticed on platforms like mine. From 1.41421 at gmail.com Wed Oct 3 02:30:11 2007 From: 1.41421 at gmail.com (JCA) Date: Tue, 2 Oct 2007 19:30:11 -0700 Subject: [Ekiga-list] Ekiga under Slackware 12 In-Reply-To: References: Message-ID: Well, I changed my audio device from within Ekiga and it now seems to work fine - no crashes. I have an old Ensoniq AudioPCI which, for my very simple purposes, is more than good enough. When configuring my audio devices in the Ekiga druid (page 7) for the audio output device the choices are Default and Ensoniq AudioPCI, whereas for the audio input device I also have a USB device - the microphone built in my webcam. When audio input and output are set to Ensoniq AudioPCI I have the behavior described in my previous email. If I change them to Default, the crashes disappear - at least, I have yet to cause another crash. This is of course terrific, but I wonder what is the difference? The actual hardware is the same in both cases. Any ideas? On 10/2/07, JCA <1.41421 at gmail.com> wrote: > I am trying to use Ekiga 2.0.9 under Slackware 12. The Ekiga > package is one delivered with Gnome Slacky 2.18.3, from www.slacky.eu. > So far I have noticed the following: > > Most of the time, Ekiga crashes immediately after establishing a > connection with sip:500 at ekiga.net. Sometimes the connection succeeds > all right, and everything works flawlessly (sound and video) until > attempting to close the connection, at which point Ekiga crashes - > again, most of the time, although not always. > > Before I start sending bug traces, I wonder if somebody could let > me know if this behavior has been noticed on platforms like mine. > From afb at paradise.net.nz Wed Oct 3 10:36:41 2007 From: afb at paradise.net.nz (Adam Bogacki) Date: Wed, 03 Oct 2007 23:36:41 +1300 Subject: [Ekiga-list] 'Fixing' Ekiga disables Mutt & apt-update Message-ID: <470370B9.9020602@paradise.net.nz> Hi Damien, I installed Ekiga 2.0.11 from source but it would not open giving me notice of a gconf error. I consulted your faq at < http://www.ekiga.org/index.php?rub=3&pos=0&faqpage=x201.html#AEN264 >, killed the Gconf Daemon via '$ killall -9 gconfd-2' and carried out ' $ chmod -R 4755 /etc/gconf/gconf.xml.defaults/ into the bargain. Ekiga now works, but I now find downloaded msgs to Mutt won't flush > 2 messages for afb at pop.paradise.net.nz (5986 octets). reading > message afb at pop3.paradise.net.nz:1 of 2 (3023 octets)..procmail: Lock > failure on "/var/mail/adam.lock" procmail: Error while writing to > "/var/mail/adam" fetchmail: MDA returned nonzero status 73 not flushed > reading message afb at pop3.paradise.net.nz:2 of 2 (2963 > octets)..procmail: Lock failure on "/var/mail/adam.lock" procmail: > Error while writing to "/var/mail/adam" fetchmail: MDA returned > nonzero status 73 not flushed .. I cannot delete msgs in Mutt .. 'mailbox is read-only', and apt-upgrade (in a mixed Etch/unstable system) gives me > Tohunga:~# apt-get upgrade W: Not using locking for read only lock > file /var/lib/dpkg/lock E: Unable to write to /var/cache/apt/ E: The > package lists or status file could not be parsed or opened. It is hard to believe that the 's' permission (below) is the problem. > Tohunga:/etc/gconf# ls -la total 44 drwxr-xr-x 7 root root 4096 > 2007-08-20 19:33 . drwxrwxrwx 212 root root 20480 2007-10-03 17:31 .. > drwxr-xr-x 2 root root 4096 2007-08-20 19:33 1 drwxr-xr-x 2 root root > 4096 2007-09-23 20:32 2 drwsr-xr-x 2 root root 4096 2007-10-03 11:03 > gconf.xml.defaults drwxr-xr-x 2 root root 4096 2007-03-09 13:12 > gconf.xml.mandatory drwxr-xr-x 2 root root 4096 2007-10-03 11:03 schemas .. which I can't change. I'd appreciate any constructive advice. Adam Bogacki, afb at paradise.net.nz: From pratiksha.powar at onmobile.com Wed Oct 3 10:43:58 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Wed, 03 Oct 2007 16:13:58 +0530 Subject: [Ekiga-list] 'Fixing' Ekiga disables Mutt & apt-update In-Reply-To: <470370B9.9020602@paradise.net.nz> References: <470370B9.9020602@paradise.net.nz> Message-ID: <1191408238.3451.6.camel@localhost.localdomain> Hi Everybody, I have an Installation of Ekiga 2.0.2. I'm trying to install 2.0.11 from source. I get the following error: ********************************************************************** checking for EKIGA... configure: error: Package requirements (gtk+-2.0 >= 2.6.0 gthread-2.0 >= 2.4.0 esound >= 0.2.28 gconf-2.0 >= 2.2.0 libgnome-2.0 >= 2.2.0 libgnomeui-2.0 >= 2.2.0) were not met: No package 'gtk+-2.0' found No package 'gthread-2.0' found No package 'esound' found No package 'gconf-2.0' found No package 'libgnome-2.0' found No package 'libgnomeui-2.0' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables EKIGA_CFLAGS and EKIGA_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. ********************************************************************** I don't know what I should set in the PKG_CONFIG_PATH env variable. And what is this variable used for? Thanks, Pratiksha On Wed, 2007-10-03 at 23:36 +1300, Adam Bogacki wrote: > Hi Damien, > > I installed Ekiga 2.0.11 from source but it would not open giving me > notice of a gconf error. > I consulted your faq at < > http://www.ekiga.org/index.php?rub=3&pos=0&faqpage=x201.html#AEN264 >, > killed the Gconf Daemon via '$ killall -9 gconfd-2' and carried out ' > > $ chmod -R 4755 /etc/gconf/gconf.xml.defaults/ > > into the bargain. Ekiga now works, but I now find downloaded msgs to Mutt > won't flush > > 2 messages for afb at pop.paradise.net.nz (5986 octets). reading > > message afb at pop3.paradise.net.nz:1 of 2 (3023 octets)..procmail: Lock > > failure on "/var/mail/adam.lock" procmail: Error while writing to > > "/var/mail/adam" fetchmail: MDA returned nonzero status 73 not flushed > > reading message afb at pop3.paradise.net.nz:2 of 2 (2963 > > octets)..procmail: Lock failure on "/var/mail/adam.lock" procmail: > > Error while writing to "/var/mail/adam" fetchmail: MDA returned > > nonzero status 73 not flushed > .. I cannot delete msgs in Mutt .. 'mailbox is read-only', and > apt-upgrade (in a mixed Etch/unstable system) gives me > > Tohunga:~# apt-get upgrade W: Not using locking for read only lock > > file /var/lib/dpkg/lock E: Unable to write to /var/cache/apt/ E: The > > package lists or status file could not be parsed or opened. > It is hard to believe that the 's' permission (below) is the problem. > > Tohunga:/etc/gconf# ls -la total 44 drwxr-xr-x 7 root root 4096 > > 2007-08-20 19:33 . drwxrwxrwx 212 root root 20480 2007-10-03 17:31 .. > > drwxr-xr-x 2 root root 4096 2007-08-20 19:33 1 drwxr-xr-x 2 root root > > 4096 2007-09-23 20:32 2 drwsr-xr-x 2 root root 4096 2007-10-03 11:03 > > gconf.xml.defaults drwxr-xr-x 2 root root 4096 2007-03-09 13:12 > > gconf.xml.mandatory drwxr-xr-x 2 root root 4096 2007-10-03 11:03 schemas > .. which I can't change. I'd appreciate any constructive advice. > > Adam Bogacki, > afb at paradise.net.nz: > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From jpuydt at free.fr Wed Oct 3 11:40:05 2007 From: jpuydt at free.fr (Julien Puydt) Date: Wed, 03 Oct 2007 13:40:05 +0200 Subject: [Ekiga-list] 'Fixing' Ekiga disables Mutt & apt-update In-Reply-To: <1191408238.3451.6.camel@localhost.localdomain> References: <470370B9.9020602@paradise.net.nz> <1191408238.3451.6.camel@localhost.localdomain> Message-ID: <47037F95.3000202@free.fr> Pratiksha Powar a ?crit : > Hi Everybody, > > I have an Installation of Ekiga 2.0.2. I'm trying to install 2.0.11 from > source. I get the following error: > ********************************************************************** > checking for EKIGA... configure: error: Package requirements (gtk+-2.0 >> = 2.6.0 gthread-2.0 >= 2.4.0 esound >= 0.2.28 gconf-2.0 >= 2.2.0 > libgnome-2.0 >= 2.2.0 libgnomeui-2.0 >= 2.2.0) were not met: > > No package 'gtk+-2.0' found > No package 'gthread-2.0' found > No package 'esound' found > No package 'gconf-2.0' found > No package 'libgnome-2.0' found > No package 'libgnomeui-2.0' found > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > installed software in a non-standard prefix. > > Alternatively, you may set the environment variables EKIGA_CFLAGS > and EKIGA_LIBS to avoid the need to call pkg-config. > See the pkg-config man page for more details. > ********************************************************************** > I don't know what I should set in the PKG_CONFIG_PATH env variable. > And what is this variable used for? Don't compile if you have no idea what this message means : use packages. Snark From jpuydt at free.fr Wed Oct 3 11:41:20 2007 From: jpuydt at free.fr (Julien Puydt) Date: Wed, 03 Oct 2007 13:41:20 +0200 Subject: [Ekiga-list] 'Fixing' Ekiga disables Mutt & apt-update In-Reply-To: <470370B9.9020602@paradise.net.nz> References: <470370B9.9020602@paradise.net.nz> Message-ID: <47037FE0.1090402@free.fr> Adam Bogacki a ?crit : > Hi Damien, > > I installed Ekiga 2.0.11 from source but it would not open giving me > notice of a gconf error. > I consulted your faq at < > http://www.ekiga.org/index.php?rub=3&pos=0&faqpage=x201.html#AEN264 >, > killed the Gconf Daemon via '$ killall -9 gconfd-2' and carried out ' > > $ chmod -R 4755 /etc/gconf/gconf.xml.defaults/ > > into the bargain. Ekiga now works, but I now find downloaded msgs to Mutt > won't flush That looks crazy. Are you sure you don't have a full disk or something like this? The break doesn't look related to ekiga at all. Snark From pratiksha.powar at onmobile.com Wed Oct 3 11:52:50 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Wed, 03 Oct 2007 17:22:50 +0530 Subject: [Ekiga-list] Problems with Ekiga Install 2.0.11 from source In-Reply-To: <47037F95.3000202@free.fr> References: <470370B9.9020602@paradise.net.nz> <1191408238.3451.6.camel@localhost.localdomain> <47037F95.3000202@free.fr> Message-ID: <1191412370.3451.12.camel@localhost.localdomain> I searched a lot for rpm packages but didn't find any. I can't use yum, as it requires the repodata folder on the websites and I couldn't find any websites which have repodata. Could you help me get an rpm? On Wed, 2007-10-03 at 13:40 +0200, Julien Puydt wrote: > Pratiksha Powar a ?crit : > > Hi Everybody, > > > > I have an Installation of Ekiga 2.0.2. I'm trying to install 2.0.11 from > > source. I get the following error: > > ********************************************************************** > > checking for EKIGA... configure: error: Package requirements (gtk+-2.0 > >> = 2.6.0 gthread-2.0 >= 2.4.0 esound >= 0.2.28 gconf-2.0 >= 2.2.0 > > libgnome-2.0 >= 2.2.0 libgnomeui-2.0 >= 2.2.0) were not met: > > > > No package 'gtk+-2.0' found > > No package 'gthread-2.0' found > > No package 'esound' found > > No package 'gconf-2.0' found > > No package 'libgnome-2.0' found > > No package 'libgnomeui-2.0' found > > > > Consider adjusting the PKG_CONFIG_PATH environment variable if you > > installed software in a non-standard prefix. > > > > Alternatively, you may set the environment variables EKIGA_CFLAGS > > and EKIGA_LIBS to avoid the need to call pkg-config. > > See the pkg-config man page for more details. > > ********************************************************************** > > I don't know what I should set in the PKG_CONFIG_PATH env variable. > > And what is this variable used for? > > Don't compile if you have no idea what this message means : use packages. > > Snark -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From sevmek at free.fr Wed Oct 3 11:57:40 2007 From: sevmek at free.fr (yannick) Date: Wed, 03 Oct 2007 13:57:40 +0200 Subject: [Ekiga-list] Problems with Ekiga Install 2.0.11 from source In-Reply-To: <1191412370.3451.12.camel@localhost.localdomain> References: <470370B9.9020602@paradise.net.nz> <1191408238.3451.6.camel@localhost.localdomain> <47037F95.3000202@free.fr> <1191412370.3451.12.camel@localhost.localdomain> Message-ID: <1191412660.6744.82.camel@achille> Le mercredi 03 octobre 2007 ? 17:22 +0530, Pratiksha Powar a ?crit : > I searched a lot for rpm packages but didn't find any. > I can't use yum, as it requires the repodata folder on the websites > and > I couldn't find any websites which have repodata. > Could you help me get an rpm? http://wiki.ekiga.org/index.php/Linux_Users Regards, Yannick -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From dsandras at seconix.com Wed Oct 3 19:24:34 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 03 Oct 2007 21:24:34 +0200 Subject: [Ekiga-list] Ekiga under Slackware 12 In-Reply-To: References: Message-ID: <1191439474.4153.21.camel@scorpion> Le mardi 02 octobre 2007 ? 19:30 -0700, JCA a ?crit : > Well, I changed my audio device from within Ekiga and it now seems > to work fine - no crashes. > > I have an old Ensoniq AudioPCI which, for my very simple purposes, > is more than good enough. When configuring my audio devices in the > Ekiga druid (page 7) for the audio output device the choices are > Default and Ensoniq AudioPCI, whereas for the audio input device I > also have a USB device - the microphone built in my webcam. > > When audio input and output are set to Ensoniq AudioPCI I have the > behavior described in my previous email. If I change them to Default, > the crashes disappear - at least, I have yet to cause another crash. > This is of course terrific, but I wonder what is the difference? The > actual hardware is the same in both cases. Any ideas? You probably hit yet another ALSA bug. You can test this : $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 8000 -f S16_LE - $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 -c 1 -r 16000 -f S16_LE - You can also use default instead of plughw:0,0 and see what happens. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Oct 3 19:25:36 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 03 Oct 2007 21:25:36 +0200 Subject: [Ekiga-list] 'Fixing' Ekiga disables Mutt & apt-update In-Reply-To: <47037FE0.1090402@free.fr> References: <470370B9.9020602@paradise.net.nz> <47037FE0.1090402@free.fr> Message-ID: <1191439536.4153.23.camel@scorpion> Le mercredi 03 octobre 2007 ? 13:41 +0200, Julien Puydt a ?crit : > Adam Bogacki a ?crit : > > Hi Damien, > > > > I installed Ekiga 2.0.11 from source but it would not open giving me > > notice of a gconf error. > > I consulted your faq at < > > http://www.ekiga.org/index.php?rub=3&pos=0&faqpage=x201.html#AEN264 >, > > killed the Gconf Daemon via '$ killall -9 gconfd-2' and carried out ' > > > > $ chmod -R 4755 /etc/gconf/gconf.xml.defaults/ > > > > into the bargain. Ekiga now works, but I now find downloaded msgs to Mutt > > won't flush > > That looks crazy. Are you sure you don't have a full disk or something > like this? > > The break doesn't look related to ekiga at all. > Perhaps your disk will crash ? Mutt does not use /etc/gconf/ at all, so the behavior can not be related to the chmod command or to Ekiga... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From afb at paradise.net.nz Wed Oct 3 23:42:20 2007 From: afb at paradise.net.nz (Adam Bogacki) Date: Thu, 04 Oct 2007 12:42:20 +1300 Subject: [Ekiga-list] 'Fixing' Ekiga disables Mutt & apt-update Message-ID: <470428DC.4020802@paradise.net.nz> > > That looks crazy. Are you sure you don't have a full disk or something > like this? > > The break doesn't look related to ekiga at all. > > Snark You were right. It seems to have cleared up with Mutt and apt now working. Regards to Damien. Vive Les Bleus ! Adam Bogacki. From pratiksha.powar at onmobile.com Thu Oct 4 08:59:28 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Thu, 04 Oct 2007 14:29:28 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1190383204.4106.27.camel@scorpion> References: <1190365436.3362.27.camel@localhost.localdomain> <1190383204.4106.27.camel@scorpion> Message-ID: <1191488368.3405.10.camel@localhost.localdomain> Hi Damein, I upgraded to Ekiga 2.0.11 and now I'm unable to connect to my local Voice Applications server which I was able to do with 2.0.2 . Ekiga tries to call that application, sets up a connection and then hangs up. Following is the output of the command : ekiga -d 2 2007/10/04 14:22:01.368 59:58.931 GMURLHandler:08ee58d0 PCSS Outgoing call routed to sip:123 at 172.16.29.68 for Call[6]-EP[Default] 2007/10/04 14:22:01.369 59:58.932 GMURLHandler:08ee58d0 SIP SetUpConnection: 2007/10/04 14:22:01.370 59:58.933 GMURLHandler:08ee58d0 OpalUDP Started connect to 172.16.29.68:5060 2007/10/04 14:22:01.371 59:58.935 SIP Transport:b2f7cf38 SIP Read thread started. 2007/10/04 14:22:01.374 59:58.937 GMURLHandler:08ee58d0 RTP_UDP Session 1 created: 172.16.25.113:5020-5021 ssrc=1050612490 2007/10/04 14:22:01.374 59:58.937 GMURLHandler:08ee58d0 RTP Adding session RTP_UDP 2007/10/04 14:22:01.386 59:58.949 GMURLHandler:08ee58d0 RTP_UDP Session 2 created: 172.16.25.113:5022-5023 ssrc=1917150571 2007/10/04 14:22:01.387 59:58.950 GMURLHandler:08ee58d0 RTP Adding session RTP_UDP 2007/10/04 14:22:01.400 59:58.963 GMURLHandler:08ee58d0 SIP No authentication information present 2007/10/04 14:22:01.401 59:58.964 GMURLHandler:08ee58d0 SetUpCall succeeded 2007/10/04 14:22:01.421 59:58.984 SIP Handler:8ec6f80 SIP PDU handler thread started. 2007/10/04 14:22:01.422 59:58.985 OnRelease:8ec7a00 OpalCon Media stream threads closed. 2007/10/04 14:22:01.423 59:58.986 SIP Handler:8ec6f80 SIP PDU handler thread finished. 2007/10/04 14:22:01.423 59:58.986 SIP Transport:b2f7cf38 SIP Read thread finished. 2007/10/04 14:22:01.423 59:58.986 OnRelease:8ec7a00 OpalCon Media stream threads closed. 2007/10/04 14:22:01.434 59:58.997 OnRelease:b2f6b0e0 OpalCon Media stream threads closed. The Voice application server has not undergone any changes. Could you help me with this? Thanks, Pratiksha *********************************************************************** You should upgrade to at least Ekiga 2.0.9 and upload a full -d 4 output > somewhere. We will check it out. *********************************************************************** On Fri, 2007-09-21 at 16:00 +0200, Damien Sandras wrote: > Le vendredi 21 septembre 2007 ? 14:33 +0530, Pratiksha Powar a ?crit : > > Hi Everybody, > > > > I'm using Ekiga for a corporate project. > > Using Ekiga I connect to a local server in my company which > > runs voice applications. I want to use Ekiga to test these > > applications. > > > > I use sip addresses like 123 at 172.16.18.69 etc. > > The server is unable to understand the DTMF PayLoad because the codec > > used by Ekiga is 101 and the one supported is 96. > > > > I receive the following error when i run : > > > > ekiga -d 2 -c 123 at 172.16.18.69 > > > > 2007/09/21 14:28:12.849 0:11.431 SIP Transport:a2de7c8 SDP > > Media attribute rtpmap found for unknown RTP type [pt=96] > > > > Following is the server's log: > > INVITE sip:123 at 172.16.18.69 SIP/2.0 > > Date: Thu, 20 Sep 2007 10:33:47 GMT > > CSeq: 1 INVITE > > Via: SIP/2.0/UDP > > 172.16.18.92:5063;branch=z9hG4bK34ff8fa3-d265-dc11-996c-0019b97d3b5d;rport > > User-Agent: Ekiga/2.0.2 > > From: "Pratiksha Powar" > > ;tag=2c218fa3-d265-dc11-996c-0019b97d3b5d > > Call-ID: 76188fa3-d265-dc11-996c-0019b97d3b5d at Pratiksha > > To: > > Contact: > > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE > > Content-Type: application/sdp > > Content-Length: 368 > > Max-Forwards: 70 > > > > v=0 > > o=- 1190284427 1190284427 IN IP4 172.16.18.92 > > s=Opal SIP Session > > c=IN IP4 172.16.18.92 > > t=0 0 > > m=audio 5004 RTP/AVP 101 114 115 3 107 110 0 8 > > a=rtpmap:101 telephone-event/8000 > > a=fmtp:101 0-15 > > a=rtpmap:114 SPEEX/16000 > > a=rtpmap:115 iLBC/8000 > > a=rtpmap:3 GSM/8000 > > a=rtpmap:107 MS-GSM/8000 > > a=rtpmap:110 SPEEX/8000 > > a=rtpmap:0 PCMU/8000 > > a=rtpmap:8 PCMA/8000 > > > > I don't know much about codecs. > > Is there a version of Ekiga which can help me solve this problem? > > Currently I'm using Ekiga 2.0.2 on Gnome 2.16. > > Ekiga was a part of the CentOS 5.0 distribution. > > > -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From dsandras at seconix.com Thu Oct 4 14:39:47 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 04 Oct 2007 16:39:47 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191488368.3405.10.camel@localhost.localdomain> References: <1190365436.3362.27.camel@localhost.localdomain> <1190383204.4106.27.camel@scorpion> <1191488368.3405.10.camel@localhost.localdomain> Message-ID: <1191508787.5606.14.camel@scorpion> Hi, Le jeudi 04 octobre 2007 ? 14:29 +0530, Pratiksha Powar a ?crit : > Hi Damein, > > I upgraded to Ekiga 2.0.11 and now I'm unable to connect to my local > Voice Applications server which I was able to do with 2.0.2 . > Ekiga tries to call that application, sets up a connection and then > hangs up. > Can you send a -d 4 please ? Please do not CC me, the list is enough :) -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From 1.41421 at gmail.com Thu Oct 4 17:23:51 2007 From: 1.41421 at gmail.com (JCA) Date: Thu, 4 Oct 2007 10:23:51 -0700 Subject: [Ekiga-list] Ekiga under Slackware 12 Message-ID: > You probably hit yet another ALSA bug. > > You can test this : > $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 > -c 1 -r 8000 -f S16_LE - > > $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 > -c 1 -r 16000 -f S16_LE - They both seem to work fine. > You can also use default instead of plughw:0,0 and see what happens. I take it that you mean replace plughw:0,0 with default in the lines above, right? That also works fine, as far as I can tell. Another issue is that, all of a sudden, all my calls to sip:500 at ekiga.net are failing :-( From dsandras at seconix.com Thu Oct 4 18:31:35 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 04 Oct 2007 20:31:35 +0200 Subject: [Ekiga-list] Ekiga under Slackware 12 In-Reply-To: References: Message-ID: <1191522695.4089.3.camel@scorpion> Le jeudi 04 octobre 2007 ? 10:23 -0700, JCA a ?crit : > > You probably hit yet another ALSA bug. > > > > You can test this : > > $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 > > -c 1 -r 8000 -f S16_LE - > > > > $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 > > -c 1 -r 16000 -f S16_LE - > > They both seem to work fine. > > > You can also use default instead of plughw:0,0 and see what happens. > > I take it that you mean replace plughw:0,0 with default in the > lines above, right? That also works fine, as far as I can tell. Weird. > Another issue is that, all of a sudden, all my calls to > sip:500 at ekiga.net are failing :-( Asterisk had crashed on ekiga.net, I restarted it. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From lists at dcorking.com Thu Oct 4 19:52:35 2007 From: lists at dcorking.com (David Corking) Date: Thu, 4 Oct 2007 20:52:35 +0100 Subject: [Ekiga-list] ekiga 2.0.11 install In-Reply-To: <86e56ee40709291518p326f89ddo9002a834e3fee6c4@mail.gmail.com> References: <86e56ee40709281725i2a49ba52re4ba0656f3b5afe8@mail.gmail.com> <86e56ee40709291518p326f89ddo9002a834e3fee6c4@mail.gmail.com> Message-ID: On 9/29/07, Zachary Zelinski wrote: > Thanks for the information, but I do already have all three packages from > ekiga.org. The issue is not those packages, it is that during my ekiga > build, it says I cannot continue because the build requires the opal > headers. There is a version of the opal-dev package in synaptic, but that > version of the headers requires that I install an older version of opal, > effectively stopping my ekiga installation. Is there a place to get the opal > headers that match the 2.2.11 opal files? This is what I need to continue > building ekiga. > Zach - I am afraid I missed your question but you have confused me. 1. Please list exactly which three packages you downloaded. 2. What is your reason for building ekiga rather than downloading the binary? It is not normally necessary for Ubuntu on x86. David From me at saurocesaretti.com Thu Oct 4 22:04:41 2007 From: me at saurocesaretti.com (Sauro Cesaretti) Date: Fri, 5 Oct 2007 00:04:41 +0200 Subject: [Ekiga-list] text-based version Message-ID: <00d001c806d2$9072ca80$6401a8c0@sauro> Hello everyone, I'd like to know if there is a version of ekiga that I can use in text-mode under linux. If not, can you suggest me anotger software in text-mode that perform the same task? Thanks in advace best regards Sauro No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.5.488 / Virus Database: 269.14.0/1048 - Release Date: 03/10/2007 20.22 From lists at dcorking.com Thu Oct 4 22:44:21 2007 From: lists at dcorking.com (David Corking) Date: Thu, 4 Oct 2007 23:44:21 +0100 Subject: [Ekiga-list] ekiga 2.0.11 install In-Reply-To: <86e56ee40709291518p326f89ddo9002a834e3fee6c4@mail.gmail.com> References: <86e56ee40709281725i2a49ba52re4ba0656f3b5afe8@mail.gmail.com> <86e56ee40709291518p326f89ddo9002a834e3fee6c4@mail.gmail.com> Message-ID: On 9/29/07, Zachary Zelinski wrote: > Thanks for the information, but I do already have all three packages from > ekiga.org. The issue is not those packages, it is that during my ekiga > build, it says I cannot continue because the build requires the opal > headers. There is a version of the opal-dev package in synaptic, but that > version of the headers requires that I install an older version of opal, > effectively stopping my ekiga installation. Is there a place to get the opal > headers that match the 2.2.11 opal files? This is what I need to continue > building ekiga. > Zach - I missed your question but you have confused me. Please list exactly which three packages you downloaded. From zach at zzelinski.com Fri Oct 5 00:26:09 2007 From: zach at zzelinski.com (Zachary Zelinski) Date: Thu, 4 Oct 2007 17:26:09 -0700 Subject: [Ekiga-list] ekiga 2.0.11 install In-Reply-To: References: <86e56ee40709281725i2a49ba52re4ba0656f3b5afe8@mail.gmail.com> <86e56ee40709291518p326f89ddo9002a834e3fee6c4@mail.gmail.com> Message-ID: <86e56ee40710041726x6e6c841ex94b3e563becde819@mail.gmail.com> I just found out what to do....I searched online and found that the packages DO install the headers Ekiga wanted, but in a default folder, whereas I should be installing them with this added on the end: --prefix=/usr When I did that, everything went well...sorry for the confusion, it was because I was ignorant of the installation path (and because of my general linux ignorance). Thanks for trying to understand my nonsense! On 10/4/07, David Corking wrote: > > On 9/29/07, Zachary Zelinski wrote: > > Thanks for the information, but I do already have all three packages > from > > ekiga.org. The issue is not those packages, it is that during my ekiga > > build, it says I cannot continue because the build requires the opal > > headers. There is a version of the opal-dev package in synaptic, but > that > > version of the headers requires that I install an older version of opal, > > effectively stopping my ekiga installation. Is there a place to get the > opal > > headers that match the 2.2.11 opal files? This is what I need to > continue > > building ekiga. > > > > Zach - I am afraid I missed your question but you have confused me. > > 1. Please list exactly which three packages you downloaded. > > 2. What is your reason for building ekiga rather than downloading the > binary? It is not normally necessary for Ubuntu on x86. > > David > _______________________________________________ > 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 derek at indranet.co.nz Fri Oct 5 00:39:21 2007 From: derek at indranet.co.nz (Derek Smithies) Date: Fri, 5 Oct 2007 12:39:21 +1200 (NZST) Subject: [Ekiga-list] text-based version In-Reply-To: <00d001c806d2$9072ca80$6401a8c0@sauro> References: <00d001c806d2$9072ca80$6401a8c0@sauro> Message-ID: Hi, Use ohphone, which is in the contrib directory of the cvs for pwlib/opal. For details on grabbing the code, go to www.voxgratia.org, suck down the libs and ohphone and build away... ohphone will have many of the features of ekiga - it is a matter of hunting for the right parameter etc to make it work. Derek. On Fri, 5 Oct 2007, Sauro Cesaretti wrote: > Hello everyone, > > I'd like to know if there is a version of ekiga that I can use in text-mode > under linux. > If not, can you suggest me anotger software in text-mode that perform the > same task? > > Thanks in advace > best regards Sauro > > > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.5.488 / Virus Database: 269.14.0/1048 - Release Date: 03/10/2007 > 20.22 > > > -- Derek Smithies Ph.D. IndraNet Technologies Ltd. Email: derek at indranet.co.nz ph +64 3 365 6485 Web: http://www.indranet-technologies.com/ From pratiksha.powar at onmobile.com Fri Oct 5 04:55:06 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Fri, 05 Oct 2007 10:25:06 +0530 Subject: [Ekiga-list] Ekiga under Slackware 12 In-Reply-To: <1191522695.4089.3.camel@scorpion> References: <1191522695.4089.3.camel@scorpion> Message-ID: <1191560106.3388.1.camel@localhost.localdomain> Hi Damien, Attached is the -d 4 output for Ekiga. Another problem I faced after installing 2.0.11 is that I can't hear any dial tone or ringing tone. Thanks, Pratiksha On Thu, 2007-10-04 at 20:31 +0200, Damien Sandras wrote: > Le jeudi 04 octobre 2007 ? 10:23 -0700, JCA a ?crit : > > > You probably hit yet another ALSA bug. > > > > > > You can test this : > > > $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 > > > -c 1 -r 8000 -f S16_LE - > > > > > > $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 > > > -c 1 -r 16000 -f S16_LE - > > > > They both seem to work fine. > > > > > You can also use default instead of plughw:0,0 and see what happens. > > > > I take it that you mean replace plughw:0,0 with default in the > > lines above, right? That also works fine, as far as I can tell. > > Weird. > > > Another issue is that, all of a sudden, all my calls to > > sip:500 at ekiga.net are failing :-( > > Asterisk had crashed on ekiga.net, I restarted it. > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- created 2007/10/05 10:20:20.206 0:10.663 GMURLHandler:0a1c0ea0 Echo Canceler Handler created 2007/10/05 10:20:20.206 0:10.663 GMURLHandler:0a1c0ea0 PCSS Created PC sound system connection. 2007/10/05 10:20:20.206 0:10.663 GMURLHandler:0a1c0ea0 OpalMan On incoming connection Call[1]-EP[Default] 2007/10/05 10:20:20.207 0:10.664 GMURLHandler:0a1c0ea0 Call GetOtherPartyConnection Call[1]-EP[Default] 2007/10/05 10:20:20.208 0:10.665 GMURLHandler:0a1c0ea0 OpalMan Set up connection to "sip:722 at 172.16.29.68" 2007/10/05 10:20:20.209 0:10.666 GMURLHandler:0a1c0ea0 OpalCon Created connection Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.209 0:10.666 GMURLHandler:0a1c0ea0 RFC2833 Handler created 2007/10/05 10:20:20.214 0:10.671 GMURLHandler:0a1c0ea0 SIP Created connection. 2007/10/05 10:20:20.214 0:10.671 GMURLHandler:0a1c0ea0 PCSS Outgoing call routed to sip:722 at 172.16.29.68 for Call[1]-EP[Default] 2007/10/05 10:20:20.215 0:10.672 GMURLHandler:0a1c0ea0 Call OnSetUp Call[1]-EP[Default] 2007/10/05 10:20:20.216 0:10.673 GMURLHandler:0a1c0ea0 SIP SetUpConnection: 2007/10/05 10:20:20.217 0:10.674 GMURLHandler:0a1c0ea0 OpalUDP Binding to interface: 172.16.25.113:32777 2007/10/05 10:20:20.217 0:10.674 GMURLHandler:0a1c0ea0 SIP Created transport udp$0.0.0.0 2007/10/05 10:20:20.217 0:10.674 GMURLHandler:0a1c0ea0 OpalUDP Started connect to 172.16.29.68:5060 2007/10/05 10:20:20.218 0:10.675 GMURLHandler:0a1c0ea0 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 10:20:20.219 0:10.676 SIP Transport:b5028b80 SIP Read thread started. 2007/10/05 10:20:20.219 0:10.676 SIP Transport:b5028b80 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/05 10:20:20.221 0:10.678 GMURLHandler:0a1c0ea0 SIP Transaction 1 INVITE created. 2007/10/05 10:20:20.221 0:10.678 GMURLHandler:0a1c0ea0 Call CanDoMediaBypass Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] session 1 2007/10/05 10:20:20.221 0:10.678 GMURLHandler:0a1c0ea0 OpalMan IsMediaBypassPossible: session 1 2007/10/05 10:20:20.222 0:10.679 GMURLHandler:0a1c0ea0 SIP IsMediaBypassPossible: session 1 2007/10/05 10:20:20.222 0:10.679 GMURLHandler:0a1c0ea0 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/05 10:20:20.223 0:10.683 GMURLHandler:0a1c0ea0 RTP_UDP Session 1 created: 172.16.25.113:5000-5001 ssrc=332968017 2007/10/05 10:20:20.227 0:10.684 GMURLHandler:0a1c0ea0 RTP Adding session RTP_UDP 2007/10/05 10:20:20.234 0:10.691 GMURLHandler:0a1c0ea0 Call GetMediaFormats for Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] G.711-ALaw-64k G.711-uLaw-64k SpeexWide-20.6k iLBC-13k3 GSM-06.10 H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 SIP Using RTP payload [pt=101] for NTE 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 Call CanDoMediaBypass Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] session 2 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 OpalMan IsMediaBypassPossible: session 2 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 SIP IsMediaBypassPossible: session 2 2007/10/05 10:20:20.235 0:10.693 GMURLHandler:0a1c0ea0 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/05 10:20:20.236 0:10.693 GMURLHandler:0a1c0ea0 RTP_UDP Session 2 created: 172.16.25.113:5002-5003 ssrc=2091935353 2007/10/05 10:20:20.236 0:10.693 GMURLHandler:0a1c0ea0 RTP Adding session RTP_UDP 2007/10/05 10:20:20.242 0:10.699 GMURLHandler:0a1c0ea0 Call GetMediaFormats for Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] G.711-ALaw-64k G.711-uLaw-64k SpeexWide-20.6k iLBC-13k3 GSM-06.10 H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/05 10:20:20.244 0:10.701 GMURLHandler:0a1c0ea0 SIP No authentication information present 2007/10/05 10:20:20.244 0:10.701 GMURLHandler:0a1c0ea0 SIP Sending PDU on udp$172.16.29.68:5060 INVITE sip:722 at 172.16.29.68 SIP/2.0 Date: Fri, 05 Oct 2007 04:50:20 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5061;branch=z9hG4bK62d0ce24-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: "Pratiksha Powar" ;tag=9602cd24-6c71-dc11-9700-0019b97d3b5d Call-ID: 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 360 Max-Forwards: 70 v=0 o=- 1191559820 1191559820 IN IP4 172.16.25.113 s=Opal SIP Session c=IN IP4 172.16.25.113 t=0 0 m=audio 5000 RTP/AVP 8 0 114 115 3 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/05 10:20:20.245 0:10.702 GMURLHandler:0a1c0ea0 SetUpCall succeeded 2007/10/05 10:20:20.262 0:10.719 SIP Transport:b5028b80 SIP PDU Received on udp$172.16.29.68:5060 SIP/2.0 415 Unsupported Media Type CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5061;rport;branch=z9hG4bK62d0ce24-6c71-dc11-9700-0019b97d3b5d From: "Pratiksha Powar" ;tag=9602cd24-6c71-dc11-9700-0019b97d3b5d Call-ID: 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: ;tag=49a10700 Content-Length: 0 2007/10/05 10:20:20.263 0:10.721 SIP Transport:b5028b80 OpalUDP Ended connect, selecting 172.16.25.113:5061 2007/10/05 10:20:20.264 0:10.721 SIP Transport:b5028b80 SIP Queueing PDU: 1 INVITE <415> 2007/10/05 10:20:20.264 0:10.721 SIP Transport:b5028b80 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/05 10:20:20.265 0:10.722 SIP Handler:b502ca38 SIP PDU handler thread started. 2007/10/05 10:20:20.265 0:10.722 SIP Handler:b502ca38 SIP Awaiting next PDU. 2007/10/05 10:20:20.265 0:10.722 SIP Handler:b502ca38 SIP Handling PDU 1 INVITE <415> 2007/10/05 10:20:20.266 0:10.723 SIP Handler:b502ca38 SIP Transaction 1 INVITE completed. 2007/10/05 10:20:20.267 0:10.724 SIP Handler:b502ca38 SIP Sending PDU on udp$172.16.29.68:5060 ACK sip:722 at 172.16.29.68 SIP/2.0 CSeq: 1 ACK Via: SIP/2.0/UDP 172.16.25.113:5061;branch=z9hG4bK62d0ce24-6c71-dc11-9700-0019b97d3b5d;rport From: "Pratiksha Powar" ;tag=9602cd24-6c71-dc11-9700-0019b97d3b5d Call-ID: 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: ;tag=49a10700 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:20.267 0:10.725 SIP Handler:b502ca38 OpalCon Releasing Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.268 0:10.725 SIP Handler:b502ca38 OpalCon Call end reason for 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha set to EndedByCapabilityExchange 2007/10/05 10:20:20.268 0:10.725 SIP Handler:b502ca38 OpalCon SetPhase from UninitialisedPhase to ReleasingPhase 2007/10/05 10:20:20.269 0:10.726 SIP Handler:b502ca38 SIP Awaiting next PDU. 2007/10/05 10:20:20.269 0:10.726 OnRelease:a1c5f18 SIP OnReleased: Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha], phase = ReleasingPhase 2007/10/05 10:20:20.270 0:10.727 OnRelease:a1c5f18 OpalCon SetPhase from ReleasingPhase to ReleasingPhase 2007/10/05 10:20:20.271 0:10.728 OnRelease:a1c5f18 SIP Cancelling transaction 0 of 1 2007/10/05 10:20:20.271 0:10.728 OnRelease:a1c5f18 SIP Could not cancel transaction 0 2007/10/05 10:20:20.271 0:10.728 OnRelease:a1c5f18 OpalCon Media stream threads closed. 2007/10/05 10:20:20.275 0:10.732 OnRelease:a1c5f18 OpalCon SetPhase from ReleasingPhase to ReleasedPhase 2007/10/05 10:20:20.275 0:10.732 SIP Handler:b502ca38 SIP PDU handler thread finished. 2007/10/05 10:20:20.275 0:10.732 OnRelease:a1c5f18 Opal Transport clean up on termination 2007/10/05 10:20:20.276 0:10.733 OnRelease:a1c5f18 OpalUDP Close 2007/10/05 10:20:20.276 0:10.733 OnRelease:a1c5f18 Opal Transport Close 2007/10/05 10:20:20.276 0:10.733 SIP Transport:b5028b80 SIP Read thread finished. 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 OpalCon OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 OpalCon Media stream threads closed. 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 GMSIPEndpoint SIP connection released 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 OpalEP OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.286 0:10.743 OnRelease:a1c5f18 GMManager Will release the connection 2007/10/05 10:20:20.286 0:10.743 OnRelease:a1c5f18 OpalMan OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.287 0:10.744 OnRelease:a1c5f18 Call OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.287 0:10.744 OnRelease:a1c5f18 OpalCon Releasing Call[1]-EP[Default] 2007/10/05 10:20:20.288 0:10.745 OnRelease:a1c5f18 OpalCon Call end reason for Default set to EndedByCapabilityExchange 2007/10/05 10:20:20.288 0:10.746 OnRelease:a1c5f18 OpalCon SetPhase from SetUpPhase to ReleasingPhase 2007/10/05 10:20:20.289 0:10.746 OnRelease:a1c5f18 SIP Transaction 1 INVITE aborted. 2007/10/05 10:20:20.290 0:10.747 OnRelease:a1c5f18 SIP Transaction 1 INVITE destroyed. 2007/10/05 10:20:20.290 0:10.747 OnRelease:a1c5f18 OpalCon OnRelease thread completed for 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha 2007/10/05 10:20:20.291 0:10.748 OnRelease:a1c5e38 OpalCon OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.291 0:10.748 OnRelease:a1c5e38 OpalCon Media stream threads closed. 2007/10/05 10:20:20.473 0:10.930 OnRelease:a1c5e38 GMPCSSEndpoint PCSS connection released 2007/10/05 10:20:20.473 0:10.931 OnRelease:a1c5e38 OpalEP OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.474 0:10.931 OnRelease:a1c5e38 GMManager Will release the connection 2007/10/05 10:20:20.474 0:10.931 OnRelease:a1c5e38 OpalMan OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.474 0:10.931 OnRelease:a1c5e38 Call OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.495 0:10.952 OnRelease:a1c5e38 OpalCon OnRelease thread completed for Default 2007/10/05 10:20:20.609 0:11.066 OpalGarbage Opal Transport clean up on termination 2007/10/05 10:20:20.609 0:11.066 OpalGarbage OpalUDP Close 2007/10/05 10:20:20.609 0:11.066 OpalGarbage Opal Transport Close 2007/10/05 10:20:20.609 0:11.066 OpalGarbage SIP Deleted connection. 2007/10/05 10:20:20.609 0:11.066 OpalGarbage OpalCon Connection Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] destroyed. 2007/10/05 10:20:20.609 0:11.066 OpalGarbage RTP_UDP Session 1, Shutting down read. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage RTP_UDP Session 1, Shutting down write. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage RTP_UDP Session 2, Shutting down read. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage RTP_UDP Session 2, Shutting down write. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage PCSS Deleted PC sound system connection. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage OpalCon Connection Call[1]-EP[Default] destroyed. 2007/10/05 10:20:20.836 0:11.293 GMAccounts...t:0a0d67d0 OpalUDP Binding to interface: 172.16.25.113:32777 2007/10/05 10:20:20.836 0:11.293 GMAccounts...t:0a0d67d0 SIP Created transport udp$0.0.0.0 2007/10/05 10:20:20.837 0:11.294 GMAccounts...t:0a0d67d0 OpalUDP Started connect to 86.64.162.35:5060 2007/10/05 10:20:20.837 0:11.294 GMAccounts...t:0a0d67d0 OpalUDP STUN could not create socket! 2007/10/05 10:20:20.837 0:11.294 GMAccounts...t:0a0d67d0 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 10:20:20.838 0:11.295 GMAccounts...t:0a0d67d0 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/05 10:20:20.839 0:11.296 SIP Transport:b5032ad8 SIP Read thread started. 2007/10/05 10:20:20.839 0:11.296 SIP Transport:b5032ad8 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/05 10:20:20.840 0:11.297 GMAccounts...t:0a0d67d0 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:21.340 0:11.797 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1 2007/10/05 10:20:21.340 0:11.797 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:21.612 0:12.069 OpalGarbage Call Call[1] destroyed. 2007/10/05 10:20:22.341 0:12.798 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 2 2007/10/05 10:20:22.341 0:12.798 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:24.342 0:14.799 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 3 2007/10/05 10:20:24.342 0:14.799 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:25.842 0:16.299 GMAccounts...t:0a0d67d0 OpalUDP Binding to interface: 172.16.25.113:32778 2007/10/05 10:20:25.842 0:16.299 GMAccounts...t:0a0d67d0 SIP Created transport udp$0.0.0.0 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 OpalUDP Started connect to 86.64.162.35:5060 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 OpalUDP STUN could not create socket! 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/05 10:20:25.845 0:16.302 SIP Transport:9fa9cb8 SIP Read thread started. 2007/10/05 10:20:25.845 0:16.302 SIP Transport:9fa9cb8 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/05 10:20:25.846 0:16.303 GMAccounts...t:0a0d67d0 SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:26.345 0:16.802 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 1 2007/10/05 10:20:26.345 0:16.802 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:26.841 0:17.298 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2007/10/05 10:20:27.346 0:17.803 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 2 2007/10/05 10:20:27.346 0:17.803 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:29.346 0:19.803 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2007/10/05 10:20:29.346 0:19.803 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:31.642 0:22.099 ekiga Listen Stopping listening thread on tcp$172.16.25.113:1720 2007/10/05 10:20:31.642 0:22.099 ekiga H323 Deleted endpoint. 2007/10/05 10:20:31.642 0:22.099 ekiga OpalEP h323 endpoint destroyed. 2007/10/05 10:20:31.846 0:22.303 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE 2007/10/05 10:20:33.602 0:24.059 ekiga SIPInfo Will delete SIPInfo sip:pratiksha.powar at ekiga.net 2007/10/05 10:20:33.602 0:24.059 ekiga SIPInfo Will delete transport udp$86.64.162.35:5060 (deleting SIPInfo) 2007/10/05 10:20:33.602 0:24.059 ekiga Opal Transport clean up on termination 2007/10/05 10:20:33.602 0:24.059 ekiga OpalUDP Close 2007/10/05 10:20:33.602 0:24.059 SIP Transport:b5032ad8 OpalUDP Error on connection read select. 2007/10/05 10:20:33.602 0:24.059 SIP Transport:b5032ad8 SIP Read thread finished. 2007/10/05 10:20:33.612 0:24.069 ekiga Opal Transport clean up on termination 2007/10/05 10:20:33.612 0:24.069 ekiga OpalUDP Close 2007/10/05 10:20:33.612 0:24.070 ekiga SIP Transaction 1 REGISTER destroyed. 2007/10/05 10:20:35.599 0:26.056 ekiga Listen Stopping listening thread on udp$172.16.25.113:5060 2007/10/05 10:20:35.599 0:26.056 Opal Listener:a0d30e8 Listen UDP select error: Interrupted system call 2007/10/05 10:20:35.609 0:26.066 ekiga SIP Deleted endpoint. 2007/10/05 10:20:35.609 0:26.067 ekiga SIPInfo Will delete SIPInfo sip:pratiksha.powar at ekiga.net 2007/10/05 10:20:35.610 0:26.067 ekiga SIPInfo Will delete transport udp$86.64.162.35:5060 (deleting SIPInfo) 2007/10/05 10:20:35.610 0:26.067 ekiga Opal Transport clean up on termination 2007/10/05 10:20:35.610 0:26.067 ekiga OpalUDP Close 2007/10/05 10:20:35.610 0:26.067 SIP Transport:9fa9cb8 OpalUDP Error on connection read select. 2007/10/05 10:20:35.610 0:26.067 SIP Transport:9fa9cb8 SIP Read thread finished. 2007/10/05 10:20:35.621 0:26.079 ekiga Opal Transport clean up on termination 2007/10/05 10:20:35.622 0:26.079 ekiga OpalUDP Close 2007/10/05 10:20:35.622 0:26.079 ekiga SIP Transaction 2 SUBSCRIBE destroyed. 2007/10/05 10:20:35.622 0:26.079 ekiga OpalEP sip endpoint destroyed. 2007/10/05 10:20:35.622 0:26.079 ekiga PCSS Deleted PC sound system endpoint. 2007/10/05 10:20:35.622 0:26.079 ekiga OpalEP pc endpoint destroyed. 2007/10/05 10:20:35.622 0:26.079 ekiga OpalMan Deleted manager. -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From pratiksha.powar at onmobile.com Fri Oct 5 05:17:52 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Fri, 05 Oct 2007 10:47:52 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191560106.3388.1.camel@localhost.localdomain> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> Message-ID: <1191561472.3388.8.camel@localhost.localdomain> Hello Everybody, Please ignore the previous mail with subject "Re: [Ekiga-list] Ekiga under Slackware 12" Damien - Attached is the -d 4 output for Ekiga. Another problem I faced after installing 2.0.11 is that I can't hear any dial tone or ringing tone. Sorry for the inconvenience caused. ~Pratiksha On Fri, 2007-10-05 at 10:25 +0530, Pratiksha Powar wrote: > Hi Damien, > > Attached is the -d 4 output for Ekiga. > Another problem I faced after installing 2.0.11 > is that I can't hear any dial tone or ringing tone. > > Thanks, > Pratiksha > > On Thu, 2007-10-04 at 20:31 +0200, Damien Sandras wrote: > > Le jeudi 04 octobre 2007 ? 10:23 -0700, JCA a ?crit : > > > > You probably hit yet another ALSA bug. > > > > > > > > You can test this : > > > > $ arecord -D plughw:0,0 -c 1 -r 8000 -f S16_LE - | aplay -D plughw:0,0 > > > > -c 1 -r 8000 -f S16_LE - > > > > > > > > $ arecord -D plughw:0,0 -c 1 -r 16000 -f S16_LE - | aplay -D plughw:0,0 > > > > -c 1 -r 16000 -f S16_LE - > > > > > > They both seem to work fine. > > > > > > > You can also use default instead of plughw:0,0 and see what happens. > > > > > > I take it that you mean replace plughw:0,0 with default in the > > > lines above, right? That also works fine, as far as I can tell. > > > > Weird. > > > > > Another issue is that, all of a sudden, all my calls to > > > sip:500 at ekiga.net are failing :-( > > > > Asterisk had crashed on ekiga.net, I restarted it. > > -- > > _ Damien Sandras > > (o- > > //\ Ekiga Softphone : http://www.ekiga.org/ > > v_/_ NOVACOM : http://www.novacom.be/ > > FOSDEM : http://www.fosdem.org/ > > SIP Phone : sip:dsandras at ekiga.net > > > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > ============================== > DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. > Thank you - OnMobile Global Limited. > ============================== > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -------------- next part -------------- created 2007/10/05 10:20:20.206 0:10.663 GMURLHandler:0a1c0ea0 Echo Canceler Handler created 2007/10/05 10:20:20.206 0:10.663 GMURLHandler:0a1c0ea0 PCSS Created PC sound system connection. 2007/10/05 10:20:20.206 0:10.663 GMURLHandler:0a1c0ea0 OpalMan On incoming connection Call[1]-EP[Default] 2007/10/05 10:20:20.207 0:10.664 GMURLHandler:0a1c0ea0 Call GetOtherPartyConnection Call[1]-EP[Default] 2007/10/05 10:20:20.208 0:10.665 GMURLHandler:0a1c0ea0 OpalMan Set up connection to "sip:722 at 172.16.29.68" 2007/10/05 10:20:20.209 0:10.666 GMURLHandler:0a1c0ea0 OpalCon Created connection Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.209 0:10.666 GMURLHandler:0a1c0ea0 RFC2833 Handler created 2007/10/05 10:20:20.214 0:10.671 GMURLHandler:0a1c0ea0 SIP Created connection. 2007/10/05 10:20:20.214 0:10.671 GMURLHandler:0a1c0ea0 PCSS Outgoing call routed to sip:722 at 172.16.29.68 for Call[1]-EP[Default] 2007/10/05 10:20:20.215 0:10.672 GMURLHandler:0a1c0ea0 Call OnSetUp Call[1]-EP[Default] 2007/10/05 10:20:20.216 0:10.673 GMURLHandler:0a1c0ea0 SIP SetUpConnection: 2007/10/05 10:20:20.217 0:10.674 GMURLHandler:0a1c0ea0 OpalUDP Binding to interface: 172.16.25.113:32777 2007/10/05 10:20:20.217 0:10.674 GMURLHandler:0a1c0ea0 SIP Created transport udp$0.0.0.0 2007/10/05 10:20:20.217 0:10.674 GMURLHandler:0a1c0ea0 OpalUDP Started connect to 172.16.29.68:5060 2007/10/05 10:20:20.218 0:10.675 GMURLHandler:0a1c0ea0 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 10:20:20.219 0:10.676 SIP Transport:b5028b80 SIP Read thread started. 2007/10/05 10:20:20.219 0:10.676 SIP Transport:b5028b80 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/05 10:20:20.221 0:10.678 GMURLHandler:0a1c0ea0 SIP Transaction 1 INVITE created. 2007/10/05 10:20:20.221 0:10.678 GMURLHandler:0a1c0ea0 Call CanDoMediaBypass Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] session 1 2007/10/05 10:20:20.221 0:10.678 GMURLHandler:0a1c0ea0 OpalMan IsMediaBypassPossible: session 1 2007/10/05 10:20:20.222 0:10.679 GMURLHandler:0a1c0ea0 SIP IsMediaBypassPossible: session 1 2007/10/05 10:20:20.222 0:10.679 GMURLHandler:0a1c0ea0 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/05 10:20:20.223 0:10.683 GMURLHandler:0a1c0ea0 RTP_UDP Session 1 created: 172.16.25.113:5000-5001 ssrc=332968017 2007/10/05 10:20:20.227 0:10.684 GMURLHandler:0a1c0ea0 RTP Adding session RTP_UDP 2007/10/05 10:20:20.234 0:10.691 GMURLHandler:0a1c0ea0 Call GetMediaFormats for Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] G.711-ALaw-64k G.711-uLaw-64k SpeexWide-20.6k iLBC-13k3 GSM-06.10 H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 SIP Using RTP payload [pt=101] for NTE 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 Call CanDoMediaBypass Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] session 2 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 OpalMan IsMediaBypassPossible: session 2 2007/10/05 10:20:20.235 0:10.692 GMURLHandler:0a1c0ea0 SIP IsMediaBypassPossible: session 2 2007/10/05 10:20:20.235 0:10.693 GMURLHandler:0a1c0ea0 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/05 10:20:20.236 0:10.693 GMURLHandler:0a1c0ea0 RTP_UDP Session 2 created: 172.16.25.113:5002-5003 ssrc=2091935353 2007/10/05 10:20:20.236 0:10.693 GMURLHandler:0a1c0ea0 RTP Adding session RTP_UDP 2007/10/05 10:20:20.242 0:10.699 GMURLHandler:0a1c0ea0 Call GetMediaFormats for Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] G.711-ALaw-64k G.711-uLaw-64k SpeexWide-20.6k iLBC-13k3 GSM-06.10 H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/05 10:20:20.244 0:10.701 GMURLHandler:0a1c0ea0 SIP No authentication information present 2007/10/05 10:20:20.244 0:10.701 GMURLHandler:0a1c0ea0 SIP Sending PDU on udp$172.16.29.68:5060 INVITE sip:722 at 172.16.29.68 SIP/2.0 Date: Fri, 05 Oct 2007 04:50:20 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5061;branch=z9hG4bK62d0ce24-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: "Pratiksha Powar" ;tag=9602cd24-6c71-dc11-9700-0019b97d3b5d Call-ID: 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 360 Max-Forwards: 70 v=0 o=- 1191559820 1191559820 IN IP4 172.16.25.113 s=Opal SIP Session c=IN IP4 172.16.25.113 t=0 0 m=audio 5000 RTP/AVP 8 0 114 115 3 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/05 10:20:20.245 0:10.702 GMURLHandler:0a1c0ea0 SetUpCall succeeded 2007/10/05 10:20:20.262 0:10.719 SIP Transport:b5028b80 SIP PDU Received on udp$172.16.29.68:5060 SIP/2.0 415 Unsupported Media Type CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5061;rport;branch=z9hG4bK62d0ce24-6c71-dc11-9700-0019b97d3b5d From: "Pratiksha Powar" ;tag=9602cd24-6c71-dc11-9700-0019b97d3b5d Call-ID: 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: ;tag=49a10700 Content-Length: 0 2007/10/05 10:20:20.263 0:10.721 SIP Transport:b5028b80 OpalUDP Ended connect, selecting 172.16.25.113:5061 2007/10/05 10:20:20.264 0:10.721 SIP Transport:b5028b80 SIP Queueing PDU: 1 INVITE <415> 2007/10/05 10:20:20.264 0:10.721 SIP Transport:b5028b80 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/05 10:20:20.265 0:10.722 SIP Handler:b502ca38 SIP PDU handler thread started. 2007/10/05 10:20:20.265 0:10.722 SIP Handler:b502ca38 SIP Awaiting next PDU. 2007/10/05 10:20:20.265 0:10.722 SIP Handler:b502ca38 SIP Handling PDU 1 INVITE <415> 2007/10/05 10:20:20.266 0:10.723 SIP Handler:b502ca38 SIP Transaction 1 INVITE completed. 2007/10/05 10:20:20.267 0:10.724 SIP Handler:b502ca38 SIP Sending PDU on udp$172.16.29.68:5060 ACK sip:722 at 172.16.29.68 SIP/2.0 CSeq: 1 ACK Via: SIP/2.0/UDP 172.16.25.113:5061;branch=z9hG4bK62d0ce24-6c71-dc11-9700-0019b97d3b5d;rport From: "Pratiksha Powar" ;tag=9602cd24-6c71-dc11-9700-0019b97d3b5d Call-ID: 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: ;tag=49a10700 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:20.267 0:10.725 SIP Handler:b502ca38 OpalCon Releasing Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.268 0:10.725 SIP Handler:b502ca38 OpalCon Call end reason for 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha set to EndedByCapabilityExchange 2007/10/05 10:20:20.268 0:10.725 SIP Handler:b502ca38 OpalCon SetPhase from UninitialisedPhase to ReleasingPhase 2007/10/05 10:20:20.269 0:10.726 SIP Handler:b502ca38 SIP Awaiting next PDU. 2007/10/05 10:20:20.269 0:10.726 OnRelease:a1c5f18 SIP OnReleased: Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha], phase = ReleasingPhase 2007/10/05 10:20:20.270 0:10.727 OnRelease:a1c5f18 OpalCon SetPhase from ReleasingPhase to ReleasingPhase 2007/10/05 10:20:20.271 0:10.728 OnRelease:a1c5f18 SIP Cancelling transaction 0 of 1 2007/10/05 10:20:20.271 0:10.728 OnRelease:a1c5f18 SIP Could not cancel transaction 0 2007/10/05 10:20:20.271 0:10.728 OnRelease:a1c5f18 OpalCon Media stream threads closed. 2007/10/05 10:20:20.275 0:10.732 OnRelease:a1c5f18 OpalCon SetPhase from ReleasingPhase to ReleasedPhase 2007/10/05 10:20:20.275 0:10.732 SIP Handler:b502ca38 SIP PDU handler thread finished. 2007/10/05 10:20:20.275 0:10.732 OnRelease:a1c5f18 Opal Transport clean up on termination 2007/10/05 10:20:20.276 0:10.733 OnRelease:a1c5f18 OpalUDP Close 2007/10/05 10:20:20.276 0:10.733 OnRelease:a1c5f18 Opal Transport Close 2007/10/05 10:20:20.276 0:10.733 SIP Transport:b5028b80 SIP Read thread finished. 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 OpalCon OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 OpalCon Media stream threads closed. 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 GMSIPEndpoint SIP connection released 2007/10/05 10:20:20.277 0:10.734 OnRelease:a1c5f18 OpalEP OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.286 0:10.743 OnRelease:a1c5f18 GMManager Will release the connection 2007/10/05 10:20:20.286 0:10.743 OnRelease:a1c5f18 OpalMan OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.287 0:10.744 OnRelease:a1c5f18 Call OnReleased Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] 2007/10/05 10:20:20.287 0:10.744 OnRelease:a1c5f18 OpalCon Releasing Call[1]-EP[Default] 2007/10/05 10:20:20.288 0:10.745 OnRelease:a1c5f18 OpalCon Call end reason for Default set to EndedByCapabilityExchange 2007/10/05 10:20:20.288 0:10.746 OnRelease:a1c5f18 OpalCon SetPhase from SetUpPhase to ReleasingPhase 2007/10/05 10:20:20.289 0:10.746 OnRelease:a1c5f18 SIP Transaction 1 INVITE aborted. 2007/10/05 10:20:20.290 0:10.747 OnRelease:a1c5f18 SIP Transaction 1 INVITE destroyed. 2007/10/05 10:20:20.290 0:10.747 OnRelease:a1c5f18 OpalCon OnRelease thread completed for 3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha 2007/10/05 10:20:20.291 0:10.748 OnRelease:a1c5e38 OpalCon OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.291 0:10.748 OnRelease:a1c5e38 OpalCon Media stream threads closed. 2007/10/05 10:20:20.473 0:10.930 OnRelease:a1c5e38 GMPCSSEndpoint PCSS connection released 2007/10/05 10:20:20.473 0:10.931 OnRelease:a1c5e38 OpalEP OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.474 0:10.931 OnRelease:a1c5e38 GMManager Will release the connection 2007/10/05 10:20:20.474 0:10.931 OnRelease:a1c5e38 OpalMan OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.474 0:10.931 OnRelease:a1c5e38 Call OnReleased Call[1]-EP[Default] 2007/10/05 10:20:20.495 0:10.952 OnRelease:a1c5e38 OpalCon OnRelease thread completed for Default 2007/10/05 10:20:20.609 0:11.066 OpalGarbage Opal Transport clean up on termination 2007/10/05 10:20:20.609 0:11.066 OpalGarbage OpalUDP Close 2007/10/05 10:20:20.609 0:11.066 OpalGarbage Opal Transport Close 2007/10/05 10:20:20.609 0:11.066 OpalGarbage SIP Deleted connection. 2007/10/05 10:20:20.609 0:11.066 OpalGarbage OpalCon Connection Call[1]-EP[3cf8cc24-6c71-dc11-9700-0019b97d3b5d at Pratiksha] destroyed. 2007/10/05 10:20:20.609 0:11.066 OpalGarbage RTP_UDP Session 1, Shutting down read. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage RTP_UDP Session 1, Shutting down write. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage RTP_UDP Session 2, Shutting down read. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage RTP_UDP Session 2, Shutting down write. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage PCSS Deleted PC sound system connection. 2007/10/05 10:20:20.610 0:11.067 OpalGarbage OpalCon Connection Call[1]-EP[Default] destroyed. 2007/10/05 10:20:20.836 0:11.293 GMAccounts...t:0a0d67d0 OpalUDP Binding to interface: 172.16.25.113:32777 2007/10/05 10:20:20.836 0:11.293 GMAccounts...t:0a0d67d0 SIP Created transport udp$0.0.0.0 2007/10/05 10:20:20.837 0:11.294 GMAccounts...t:0a0d67d0 OpalUDP Started connect to 86.64.162.35:5060 2007/10/05 10:20:20.837 0:11.294 GMAccounts...t:0a0d67d0 OpalUDP STUN could not create socket! 2007/10/05 10:20:20.837 0:11.294 GMAccounts...t:0a0d67d0 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 10:20:20.838 0:11.295 GMAccounts...t:0a0d67d0 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/05 10:20:20.839 0:11.296 SIP Transport:b5032ad8 SIP Read thread started. 2007/10/05 10:20:20.839 0:11.296 SIP Transport:b5032ad8 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/05 10:20:20.840 0:11.297 GMAccounts...t:0a0d67d0 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:21.340 0:11.797 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1 2007/10/05 10:20:21.340 0:11.797 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:21.612 0:12.069 OpalGarbage Call Call[1] destroyed. 2007/10/05 10:20:22.341 0:12.798 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 2 2007/10/05 10:20:22.341 0:12.798 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:24.342 0:14.799 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 3 2007/10/05 10:20:24.342 0:14.799 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK9c192d25-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=880f2d25-6c71-dc11-9700-0019b97d3b5d Call-ID: 0ea32c25-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:25.842 0:16.299 GMAccounts...t:0a0d67d0 OpalUDP Binding to interface: 172.16.25.113:32778 2007/10/05 10:20:25.842 0:16.299 GMAccounts...t:0a0d67d0 SIP Created transport udp$0.0.0.0 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 OpalUDP Started connect to 86.64.162.35:5060 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 OpalUDP STUN could not create socket! 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 10:20:25.843 0:16.300 GMAccounts...t:0a0d67d0 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/05 10:20:25.845 0:16.302 SIP Transport:9fa9cb8 SIP Read thread started. 2007/10/05 10:20:25.845 0:16.302 SIP Transport:9fa9cb8 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/05 10:20:25.846 0:16.303 GMAccounts...t:0a0d67d0 SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:26.345 0:16.802 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 1 2007/10/05 10:20:26.345 0:16.802 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:26.841 0:17.298 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2007/10/05 10:20:27.346 0:17.803 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 2 2007/10/05 10:20:27.346 0:17.803 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:29.346 0:19.803 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2007/10/05 10:20:29.346 0:19.803 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKe2e82828-6c71-dc11-9700-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f2dd2828-6c71-dc11-9700-0019b97d3b5d Call-ID: a27e2828-6c71-dc11-9700-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 10:20:31.642 0:22.099 ekiga Listen Stopping listening thread on tcp$172.16.25.113:1720 2007/10/05 10:20:31.642 0:22.099 ekiga H323 Deleted endpoint. 2007/10/05 10:20:31.642 0:22.099 ekiga OpalEP h323 endpoint destroyed. 2007/10/05 10:20:31.846 0:22.303 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE 2007/10/05 10:20:33.602 0:24.059 ekiga SIPInfo Will delete SIPInfo sip:pratiksha.powar at ekiga.net 2007/10/05 10:20:33.602 0:24.059 ekiga SIPInfo Will delete transport udp$86.64.162.35:5060 (deleting SIPInfo) 2007/10/05 10:20:33.602 0:24.059 ekiga Opal Transport clean up on termination 2007/10/05 10:20:33.602 0:24.059 ekiga OpalUDP Close 2007/10/05 10:20:33.602 0:24.059 SIP Transport:b5032ad8 OpalUDP Error on connection read select. 2007/10/05 10:20:33.602 0:24.059 SIP Transport:b5032ad8 SIP Read thread finished. 2007/10/05 10:20:33.612 0:24.069 ekiga Opal Transport clean up on termination 2007/10/05 10:20:33.612 0:24.069 ekiga OpalUDP Close 2007/10/05 10:20:33.612 0:24.070 ekiga SIP Transaction 1 REGISTER destroyed. 2007/10/05 10:20:35.599 0:26.056 ekiga Listen Stopping listening thread on udp$172.16.25.113:5060 2007/10/05 10:20:35.599 0:26.056 Opal Listener:a0d30e8 Listen UDP select error: Interrupted system call 2007/10/05 10:20:35.609 0:26.066 ekiga SIP Deleted endpoint. 2007/10/05 10:20:35.609 0:26.067 ekiga SIPInfo Will delete SIPInfo sip:pratiksha.powar at ekiga.net 2007/10/05 10:20:35.610 0:26.067 ekiga SIPInfo Will delete transport udp$86.64.162.35:5060 (deleting SIPInfo) 2007/10/05 10:20:35.610 0:26.067 ekiga Opal Transport clean up on termination 2007/10/05 10:20:35.610 0:26.067 ekiga OpalUDP Close 2007/10/05 10:20:35.610 0:26.067 SIP Transport:9fa9cb8 OpalUDP Error on connection read select. 2007/10/05 10:20:35.610 0:26.067 SIP Transport:9fa9cb8 SIP Read thread finished. 2007/10/05 10:20:35.621 0:26.079 ekiga Opal Transport clean up on termination 2007/10/05 10:20:35.622 0:26.079 ekiga OpalUDP Close 2007/10/05 10:20:35.622 0:26.079 ekiga SIP Transaction 2 SUBSCRIBE destroyed. 2007/10/05 10:20:35.622 0:26.079 ekiga OpalEP sip endpoint destroyed. 2007/10/05 10:20:35.622 0:26.079 ekiga PCSS Deleted PC sound system endpoint. 2007/10/05 10:20:35.622 0:26.079 ekiga OpalEP pc endpoint destroyed. 2007/10/05 10:20:35.622 0:26.079 ekiga OpalMan Deleted manager. -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From dsandras at seconix.com Fri Oct 5 07:40:04 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 05 Oct 2007 09:40:04 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191561472.3388.8.camel@localhost.localdomain> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> Message-ID: <1191570004.4308.9.camel@scorpion> Hi, Le vendredi 05 octobre 2007 ? 10:47 +0530, Pratiksha Powar a ?crit : > Hello Everybody, > > Please ignore the previous mail with subject > "Re: [Ekiga-list] Ekiga under Slackware 12" > > Damien - Attached is the -d 4 output for Ekiga. > Another problem I faced after installing 2.0.11 > is that I can't hear any dial tone or ringing tone. > Your proxy seems to reject the call because it does not support codecs of Ekiga : SIP/2.0 415 Unsupported Media Type CSeq: 1 INVITE I would disable video and all codecs except PCMA and PCMU. Those ones should work... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Oct 5 08:24:44 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 05 Oct 2007 10:24:44 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191572657.3343.2.camel@localhost.localdomain> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191572657.3343.2.camel@localhost.localdomain> Message-ID: <1191572684.4308.23.camel@scorpion> Le vendredi 05 octobre 2007 ? 13:54 +0530, Pratiksha Powar a ?crit : > Thanks, it is working now. > > ~Pratiksha good :) > > > On Fri, 2007-10-05 at 09:40 +0200, Damien Sandras wrote: > > Hi, > > > > Le vendredi 05 octobre 2007 ? 10:47 +0530, Pratiksha Powar a ?crit : > > > Hello Everybody, > > > > > > Please ignore the previous mail with subject > > > "Re: [Ekiga-list] Ekiga under Slackware 12" > > > > > > Damien - Attached is the -d 4 output for Ekiga. > > > Another problem I faced after installing 2.0.11 > > > is that I can't hear any dial tone or ringing tone. > > > > > > > Your proxy seems to reject the call because it does not support codecs > > of Ekiga : > > SIP/2.0 415 Unsupported Media Type > > CSeq: 1 INVITE > > > > I would disable video and all codecs except PCMA and PCMU. Those ones > > should work... > > > ============================== > DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. > Thank you - OnMobile Global Limited. > ============================== -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From pratiksha.powar at onmobile.com Fri Oct 5 08:31:36 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Fri, 05 Oct 2007 14:01:36 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191570004.4308.9.camel@scorpion> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> Message-ID: <1191573096.3343.7.camel@localhost.localdomain> Hi Damien, I'm able to connect to the Voice Applications server, but once connected I'm unable to hear anything. I have kept only PCMU and PCMA on. Attached is the trace at level 4 Could you help me? Thanks, Pratiksha On Fri, 2007-10-05 at 09:40 +0200, Damien Sandras wrote: > Hi, > > Le vendredi 05 octobre 2007 ? 10:47 +0530, Pratiksha Powar a ?crit : > > Hello Everybody, > > > > Please ignore the previous mail with subject > > "Re: [Ekiga-list] Ekiga under Slackware 12" > > > > Damien - Attached is the -d 4 output for Ekiga. > > Another problem I faced after installing 2.0.11 > > is that I can't hear any dial tone or ringing tone. > > > > Your proxy seems to reject the call because it does not support codecs > of Ekiga : > SIP/2.0 415 Unsupported Media Type > CSeq: 1 INVITE > > I would disable video and all codecs except PCMA and PCMU. Those ones > should work... -------------- next part -------------- 2007/10/05 13:58:33.278 0:12.539 SIP Handler:90be948 OpalCon Media stream threads started. 2007/10/05 13:58:33.279 0:12.539 SIP Handler:90be948 OpalCon SetPhase from AlertingPhase to EstablishedPhase 2007/10/05 13:58:33.279 0:12.539 SIP Handler:90be948 GMSIPEndpoint SIP connection established 2007/10/05 13:58:33.287 0:12.547 SIP Handler:90be948 RTP Found existing session 1 2007/10/05 13:58:33.288 0:12.548 SIP Handler:90be948 GMManager Will establish the connection 2007/10/05 13:58:33.288 0:12.548 SIP Handler:90be948 OpalMan OnEstablished Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:33.288 0:12.548 SIP Handler:90be948 Call OnEstablished Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:33.292 0:12.552 SIP Handler:90be948 SIP Awaiting next PDU. 2007/10/05 13:58:33.312 0:12.572 Media Patch:8e2b038 RTP First sent data: ver=2 pt=PCMU psz=160 m=1 x=0 seq=6569 ts=0 src=2052757532 ccnt=0 2007/10/05 13:58:34.292 0:13.553 Housekeeper RTP Found existing session 1 2007/10/05 13:58:35.302 0:14.563 Housekeeper RTP Found existing session 1 2007/10/05 13:58:35.322 0:14.582 Media Patch:8e2b038 RTP Transmit statistics: packets=101 octets=16160 avgTime=20 maxTime=60 minTime=16 2007/10/05 13:58:36.312 0:15.572 Housekeeper RTP Found existing session 1 2007/10/05 13:58:37.060 0:16.320 GMAccounts...t:08fd7a50 OpalUDP Binding to interface: 172.16.25.113:32772 2007/10/05 13:58:37.060 0:16.320 GMAccounts...t:08fd7a50 SIP Created transport udp$0.0.0.0 2007/10/05 13:58:37.060 0:16.320 GMAccounts...t:08fd7a50 OpalUDP Started connect to 86.64.162.35:5060 2007/10/05 13:58:37.060 0:16.320 GMAccounts...t:08fd7a50 OpalUDP STUN could not create socket! 2007/10/05 13:58:37.060 0:16.321 GMAccounts...t:08fd7a50 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 13:58:37.061 0:16.321 GMAccounts...t:08fd7a50 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/05 13:58:37.063 0:16.323 GMAccounts...t:08fd7a50 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK4c2822a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=881e22a3-8a71-dc11-891b-0019b97d3b5d Call-ID: aebc21a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:37.063 0:16.323 SIP Transport:8fbbf40 SIP Read thread started. 2007/10/05 13:58:37.064 0:16.324 SIP Transport:8fbbf40 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/05 13:58:37.068 0:16.328 GMAccounts...t:08fd7a50 OpalUDP Binding to interface: 172.16.25.113:32772 2007/10/05 13:58:37.068 0:16.328 GMAccounts...t:08fd7a50 SIP Created transport udp$0.0.0.0 2007/10/05 13:58:37.068 0:16.328 GMAccounts...t:08fd7a50 OpalUDP Started connect to 86.64.162.35:5060 2007/10/05 13:58:37.069 0:16.329 GMAccounts...t:08fd7a50 OpalUDP STUN could not create socket! 2007/10/05 13:58:37.069 0:16.329 GMAccounts...t:08fd7a50 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/05 13:58:37.069 0:16.329 GMAccounts...t:08fd7a50 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/05 13:58:37.070 0:16.330 SIP Transport:91add40 SIP Read thread started. 2007/10/05 13:58:37.071 0:16.331 SIP Transport:91add40 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/05 13:58:37.071 0:16.331 GMAccounts...t:08fd7a50 SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKce6823a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=ca5d23a3-8a71-dc11-891b-0019b97d3b5d Call-ID: 340323a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:37.312 0:16.573 Housekeeper RTP Found existing session 1 2007/10/05 13:58:37.320 0:16.581 Media Patch:8e2b038 RTP Transmit statistics: packets=201 octets=32160 avgTime=19 maxTime=60 minTime=15 2007/10/05 13:58:37.582 0:16.842 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1 2007/10/05 13:58:37.583 0:16.843 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK4c2822a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=881e22a3-8a71-dc11-891b-0019b97d3b5d Call-ID: aebc21a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:37.583 0:16.843 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 1 2007/10/05 13:58:37.583 0:16.843 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKce6823a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=ca5d23a3-8a71-dc11-891b-0019b97d3b5d Call-ID: 340323a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:38.322 0:17.582 Housekeeper RTP Found existing session 1 2007/10/05 13:58:38.592 0:17.852 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 2 2007/10/05 13:58:38.593 0:17.853 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK4c2822a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=881e22a3-8a71-dc11-891b-0019b97d3b5d Call-ID: aebc21a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:38.593 0:17.853 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 2 2007/10/05 13:58:38.594 0:17.854 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKce6823a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=ca5d23a3-8a71-dc11-891b-0019b97d3b5d Call-ID: 340323a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:39.323 0:18.584 Media Patch:8e2b038 RTP Transmit statistics: packets=301 octets=48160 avgTime=20 maxTime=60 minTime=15 2007/10/05 13:58:39.342 0:18.602 Housekeeper RTP Found existing session 1 2007/10/05 13:58:40.340 0:19.600 Housekeeper RTP Found existing session 1 2007/10/05 13:58:40.621 0:19.881 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 3 2007/10/05 13:58:40.621 0:19.881 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK4c2822a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=881e22a3-8a71-dc11-891b-0019b97d3b5d Call-ID: aebc21a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:40.622 0:19.882 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2007/10/05 13:58:40.622 0:19.882 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKce6823a3-8a71-dc11-891b-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=ca5d23a3-8a71-dc11-891b-0019b97d3b5d Call-ID: 340323a3-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:41.332 0:20.592 Media Patch:8e2b038 RTP Transmit statistics: packets=401 octets=64160 avgTime=20 maxTime=61 minTime=15 2007/10/05 13:58:41.382 0:20.642 Housekeeper RTP Found existing session 1 2007/10/05 13:58:42.402 0:21.662 Housekeeper RTP Found existing session 1 2007/10/05 13:58:42.931 0:22.192 Media Patch:8e2b038 RTP SentSenderReport: ssrc=2052757532 ntp=3400561722.4001909238 rtp=76800 psent=481 osent=76960 2007/10/05 13:58:42.932 0:22.192 Media Patch:8e2b038 RTP Sending SDES: root at Pratiksha 2007/10/05 13:58:43.063 0:22.323 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2007/10/05 13:58:43.072 0:22.332 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE 2007/10/05 13:58:43.331 0:22.592 Media Patch:8e2b038 RTP Transmit statistics: packets=501 octets=80160 avgTime=19 maxTime=41 minTime=15 2007/10/05 13:58:43.414 0:22.674 Housekeeper RTP Found existing session 1 2007/10/05 13:58:44.425 0:23.685 Housekeeper RTP Found existing session 1 2007/10/05 13:58:44.807 0:24.067 ekiga Call Clearing Call[1] reason=EndedByLocalUser 2007/10/05 13:58:44.808 0:24.068 ekiga OpalCon Releasing Call[1]-EP[Default] 2007/10/05 13:58:44.808 0:24.068 ekiga OpalCon Call end reason for Default set to EndedByLocalUser 2007/10/05 13:58:44.808 0:24.068 ekiga OpalCon SetPhase from EstablishedPhase to ReleasingPhase 2007/10/05 13:58:44.809 0:24.069 ekiga OpalCon Releasing Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:44.809 0:24.069 ekiga OpalCon Call end reason for e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha set to EndedByLocalUser 2007/10/05 13:58:44.809 0:24.069 ekiga OpalCon SetPhase from EstablishedPhase to ReleasingPhase 2007/10/05 13:58:44.812 0:24.072 OnRelease:91aeac8 OpalCon OnReleased Call[1]-EP[Default] 2007/10/05 13:58:44.813 0:24.073 OnRelease:91aeac8 Media Closing raw media stream OpalAudioMediaStream-Source-PCM-16 2007/10/05 13:58:44.813 0:24.073 OnRelease:91aeac8 Media Closing stream OpalAudioMediaStream-Source-PCM-16 2007/10/05 13:58:44.813 0:24.073 OnRelease:91aeac8 Media Disconnecting OpalAudioMediaStream-Source-PCM-16 from patch thread Patch OpalAudioMediaStream-Source-PCM-16 -> OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/05 13:58:44.822 0:24.082 OnRelease:91aeac8 Patch Closing media patch Patch OpalAudioMediaStream-Source-PCM-16 -> OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/05 13:58:44.823 0:24.083 OnRelease:91aeac8 Media Closing raw media stream OpalAudioMediaStream-Source-PCM-16 2007/10/05 13:58:44.823 0:24.083 OnRelease:91aeac8 Patch Removing media stream sink OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/05 13:58:44.823 0:24.083 OnRelease:91aeac8 Patch Waiting for media patch thread to stop Patch OpalAudioMediaStream-Source-PCM-16 2007/10/05 13:58:44.824 0:24.084 OnRelease:90be708 SIP OnReleased: Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha], phase = ReleasingPhase 2007/10/05 13:58:44.824 0:24.084 OnRelease:90be708 OpalCon SetPhase from ReleasingPhase to ReleasingPhase 2007/10/05 13:58:44.826 0:24.086 OnRelease:90be708 SIP Transaction 3 BYE created. 2007/10/05 13:58:44.827 0:24.087 Media Patch:8e2b038 Patch Thread ended for Patch OpalAudioMediaStream-Source-PCM-16 2007/10/05 13:58:44.832 0:24.092 OnRelease:90be708 Media Closing RTP for OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/05 13:58:44.832 0:24.092 OnRelease:90be708 RTP_UDP Session 1, Shutting down write. 2007/10/05 13:58:44.832 0:24.092 OnRelease:90be708 Media Closing stream OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/05 13:58:44.837 0:24.097 OnRelease:90be708 Media Closing RTP for OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/05 13:58:44.837 0:24.097 OnRelease:90be708 RTP_UDP Session 1, Shutting down read. 2007/10/05 13:58:44.837 0:24.097 RTP Jitter:90c4498 RTP_UDP Session 1, Read shutdown. 2007/10/05 13:58:44.837 0:24.097 RTP Jitter:90c4498 RTP Jitter RTP receive thread ended 2007/10/05 13:58:44.837 0:24.097 OnRelease:90be708 Media Closing stream OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/05 13:58:44.837 0:24.097 OnRelease:90be708 Media Disconnecting OpalRTPMediaStream-Source-G.711-uLaw-64k from patch thread Patch OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/05 13:58:44.858 0:24.118 OnRelease:90be708 Patch Closing media patch Patch OpalRTPMediaStream-Source-G.711-uLaw-64k -> OpalAudioMediaStream-Sink-PCM-16 2007/10/05 13:58:44.863 0:24.123 OnRelease:90be708 Media Closing RTP for OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/05 13:58:44.863 0:24.123 OnRelease:90be708 RTP_UDP Session 1, Shutting down read. 2007/10/05 13:58:44.863 0:24.123 OnRelease:90be708 Patch Removing media stream sink OpalAudioMediaStream-Sink-PCM-16 2007/10/05 13:58:44.863 0:24.123 OnRelease:90be708 Patch Waiting for media patch thread to stop Patch OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/05 13:58:44.864 0:24.124 OnRelease:91aeac8 Patch Media patch thread Patch OpalAudioMediaStream-Source-PCM-16 destroyed. 2007/10/05 13:58:44.867 0:24.127 Media Patch:90c8668 Patch Thread ended for Patch OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/05 13:58:44.868 0:24.128 OnRelease:91aeac8 Media Closing raw media stream OpalAudioMediaStream-Sink-PCM-16 2007/10/05 13:58:44.869 0:24.129 OnRelease:91aeac8 Media Closing stream OpalAudioMediaStream-Sink-PCM-16 2007/10/05 13:58:44.872 0:24.132 OnRelease:91aeac8 OpalCon Media stream threads closed. 2007/10/05 13:58:44.874 0:24.134 OnRelease:90be708 Patch Media patch thread Patch OpalRTPMediaStream-Source-G.711-uLaw-64k destroyed. 2007/10/05 13:58:44.874 0:24.134 OnRelease:90be708 OpalCon Media stream threads closed. 2007/10/05 13:58:44.875 0:24.135 OnRelease:90be708 SIP No authentication information present 2007/10/05 13:58:44.875 0:24.135 OnRelease:90be708 SIP Sending PDU on udp$172.16.29.68:5060 BYE sip:722 at 172.16.29.68 SIP/2.0 CSeq: 3 BYE Via: SIP/2.0/UDP 172.16.25.113:5061;branch=z9hG4bKd6d0c2a7-8a71-dc11-891b-0019b97d3b5d;rport From: "Pratiksha Powar" ;tag=fcb1739f-8a71-dc11-891b-0019b97d3b5d Call-ID: e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: ;tag=7bc20500 Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Length: 0 Max-Forwards: 70 2007/10/05 13:58:44.888 0:24.148 SIP Transport:b5003fe8 SIP PDU Received on udp$172.16.29.68:5060 SIP/2.0 200 OK CSeq: 3 BYE Via: SIP/2.0/UDP 172.16.25.113:5061;rport;branch=z9hG4bKd6d0c2a7-8a71-dc11-891b-0019b97d3b5d From: "Pratiksha Powar" ;tag=fcb1739f-8a71-dc11-891b-0019b97d3b5d Call-ID: e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha To: ;tag=7bc20500 Content-Length: 0 2007/10/05 13:58:44.890 0:24.150 OnRelease:91aeac8 GMPCSSEndpoint PCSS connection released 2007/10/05 13:58:44.890 0:24.150 OnRelease:91aeac8 OpalEP OnReleased Call[1]-EP[Default] 2007/10/05 13:58:44.890 0:24.150 OnRelease:91aeac8 GMManager Will release the connection 2007/10/05 13:58:44.890 0:24.150 OnRelease:91aeac8 OpalMan OnReleased Call[1]-EP[Default] 2007/10/05 13:58:44.890 0:24.150 OnRelease:91aeac8 Call OnReleased Call[1]-EP[Default] 2007/10/05 13:58:44.891 0:24.151 SIP Transport:b5003fe8 SIP Queueing PDU: 3 BYE <200> 2007/10/05 13:58:44.891 0:24.151 OnRelease:91aeac8 OpalCon Already released Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:44.891 0:24.151 SIP Handler:90be948 SIP Handling PDU 3 BYE <200> 2007/10/05 13:58:44.892 0:24.152 SIP Handler:90be948 SIP Transaction 3 BYE completed. 2007/10/05 13:58:44.892 0:24.152 SIP Handler:90be948 SIP Received OK response for non INVITE 2007/10/05 13:58:44.892 0:24.152 OnRelease:90be708 SIP Transaction 3 BYE aborted. 2007/10/05 13:58:44.892 0:24.152 SIP Handler:90be948 SIP Awaiting next PDU. 2007/10/05 13:58:44.892 0:24.152 OnRelease:91aeac8 OpalCon OnRelease thread completed for Default 2007/10/05 13:58:44.892 0:24.152 OnRelease:90be708 SIP Transaction 3 BYE destroyed. 2007/10/05 13:58:44.892 0:24.152 SIP Transport:b5003fe8 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/05 13:58:44.893 0:24.153 OnRelease:90be708 OpalCon SetPhase from ReleasingPhase to ReleasedPhase 2007/10/05 13:58:44.893 0:24.153 SIP Handler:90be948 SIP PDU handler thread finished. 2007/10/05 13:58:44.904 0:24.164 OnRelease:90be708 Opal Transport clean up on termination 2007/10/05 13:58:44.905 0:24.165 OnRelease:90be708 OpalUDP Close 2007/10/05 13:58:44.905 0:24.165 OnRelease:90be708 Opal Transport Close 2007/10/05 13:58:44.905 0:24.165 SIP Transport:b5003fe8 SIP Read thread finished. 2007/10/05 13:58:44.906 0:24.166 OnRelease:90be708 OpalCon OnReleased Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:44.906 0:24.166 OnRelease:90be708 OpalCon Media stream threads closed. 2007/10/05 13:58:44.906 0:24.166 OnRelease:90be708 GMSIPEndpoint SIP connection released 2007/10/05 13:58:44.906 0:24.166 OnRelease:90be708 OpalEP OnReleased Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:44.916 0:24.176 OnRelease:90be708 GMManager Will release the connection 2007/10/05 13:58:44.916 0:24.176 OnRelease:90be708 OpalMan OnReleased Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:44.916 0:24.176 OnRelease:90be708 Call OnReleased Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] 2007/10/05 13:58:45.833 0:25.093 OpalGarbage PCSS Deleted PC sound system connection. 2007/10/05 13:58:45.834 0:25.094 OpalGarbage OpalCon Connection Call[1]-EP[Default] destroyed. 2007/10/05 13:58:48.178 0:27.438 OnRelease:90be708 SIP Transaction 1 INVITE destroyed. 2007/10/05 13:58:48.178 0:27.438 OnRelease:90be708 OpalCon OnRelease thread completed for e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha 2007/10/05 13:58:48.839 0:28.099 OpalGarbage Opal Transport clean up on termination 2007/10/05 13:58:48.839 0:28.099 OpalGarbage OpalUDP Close 2007/10/05 13:58:48.839 0:28.099 OpalGarbage Opal Transport Close 2007/10/05 13:58:48.840 0:28.100 OpalGarbage SIP Deleted connection. 2007/10/05 13:58:48.840 0:28.100 OpalGarbage OpalCon Connection Call[1]-EP[e8a7739f-8a71-dc11-891b-0019b97d3b5d at Pratiksha] destroyed. 2007/10/05 13:58:48.840 0:28.100 OpalGarbage RTP_UDP Session 1, Shutting down write. 2007/10/05 13:58:48.840 0:28.100 OpalGarbage RTP Final statistics: packetsSent = 576 octetsSent = 92160 averageSendTime = 19 maximumSendTime = 41 minimumSendTime = 15 packetsReceived = 0 octetsReceived = 0 packetsLost = 0 packetsTooLate = 0 packetsOutOfOrder = 0 averageReceiveTime= 0 maximumReceiveTime= 0 minimumReceiveTime= 0 averageJitter = 0 maximumJitter = 0 2007/10/05 13:58:48.840 0:28.100 OpalGarbage RTP Removing jitter buffer 0x90c4498 RTP Jitter:90c4498 2007/10/05 13:58:49.842 0:29.102 OpalGarbage Call Call[1] destroyed. 2007/10/05 13:58:53.860 0:33.120 ekiga Listen Stopping listening thread on tcp$172.16.25.113:1720 2007/10/05 13:58:53.871 0:33.131 ekiga H323 Deleted endpoint. 2007/10/05 13:58:53.871 0:33.131 ekiga OpalEP h323 endpoint destroyed. 2007/10/05 13:58:54.879 0:34.139 ekiga SIPInfo Will delete SIPInfo sip:pratiksha.powar at ekiga.net 2007/10/05 13:58:54.879 0:34.139 ekiga SIPInfo Will delete transport udp$86.64.162.35:5060 (deleting SIPInfo) 2007/10/05 13:58:54.880 0:34.140 ekiga Opal Transport clean up on termination 2007/10/05 13:58:54.880 0:34.140 ekiga OpalUDP Close 2007/10/05 13:58:54.880 0:34.140 SIP Transport:8fbbf40 OpalUDP Error on connection read select. 2007/10/05 13:58:54.880 0:34.140 SIP Transport:8fbbf40 SIP Read thread finished. 2007/10/05 13:58:54.890 0:34.150 ekiga Opal Transport clean up on termination 2007/10/05 13:58:54.890 0:34.150 ekiga OpalUDP Close 2007/10/05 13:58:54.890 0:34.150 ekiga SIP Transaction 1 REGISTER destroyed. 2007/10/05 13:58:56.880 0:36.140 ekiga Listen Stopping listening thread on udp$172.16.25.113:5060 2007/10/05 13:58:56.880 0:36.140 Opal Listener:8fd4358 Listen UDP select error: Interrupted system call 2007/10/05 13:58:56.881 0:36.141 ekiga SIP Deleted endpoint. 2007/10/05 13:58:56.881 0:36.141 ekiga SIPInfo Will delete SIPInfo sip:pratiksha.powar at ekiga.net 2007/10/05 13:58:56.881 0:36.141 ekiga SIPInfo Will delete transport udp$86.64.162.35:5060 (deleting SIPInfo) 2007/10/05 13:58:56.881 0:36.141 ekiga Opal Transport clean up on termination 2007/10/05 13:58:56.881 0:36.141 ekiga OpalUDP Close 2007/10/05 13:58:56.881 0:36.141 SIP Transport:91add40 OpalUDP Error on connection read select. 2007/10/05 13:58:56.882 0:36.142 SIP Transport:91add40 SIP Read thread finished. 2007/10/05 13:58:56.892 0:36.152 ekiga Opal Transport clean up on termination 2007/10/05 13:58:56.892 0:36.152 ekiga OpalUDP Close 2007/10/05 13:58:56.892 0:36.152 ekiga SIP Transaction 2 SUBSCRIBE destroyed. 2007/10/05 13:58:56.892 0:36.152 ekiga OpalEP sip endpoint destroyed. 2007/10/05 13:58:56.892 0:36.152 ekiga PCSS Deleted PC sound system endpoint. 2007/10/05 13:58:56.892 0:36.152 ekiga OpalEP pc endpoint destroyed. 2007/10/05 13:58:56.892 0:36.152 ekiga OpalMan Deleted manager. -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From christopher.fanning at gmail.com Fri Oct 5 08:34:47 2007 From: christopher.fanning at gmail.com (Chris Fanning) Date: Fri, 5 Oct 2007 10:34:47 +0200 Subject: [Ekiga-list] consult the videos at a later date Message-ID: <215ff4410710050134x57125794y325407c61920a731@mail.gmail.com> Hello, I've just signed up on the list. Above all, I'd like to thank and congradulate the Ekiga team for this excelent software. My question. We would like to set up multi-point videoconferencing on our national network. We have a Multipoint Control Unit. Ekiga seems a good option. But we also would like to save the conferences to files and add them to a repository so users can consult the videos at a later date. How would you suggest doing this? (I hope this isn't off-topic). Thanks again. Chris. From alanslists at gmail.com Fri Oct 5 10:12:07 2007 From: alanslists at gmail.com (Alan Lord) Date: Fri, 05 Oct 2007 11:12:07 +0100 Subject: [Ekiga-list] DTMF and Asterisk? Message-ID: <47060DF7.3080007@gmail.com> Hi all, I have started playing around with Asterisk recently. I got very confused when I couldn't get it to respond to DTMF tones from my Ekiga client. I tried loads of configuration settings on Asterisk and upgraded to their latest version 1-4.12. Same problem. I installed Twinkle and OpenWengo as alternatives to test, and they both worked first time! Asterisk correctly interprets the tones sent from my keyboard.... How can I help to identify and fix the problem here? My client end PC is Ubuntu 7.04 and the Ekiga version is from the standard Ubuntu Feisty repo: 2.0.3. The sound quality and echo cancellation of Ekiga is far better than Twinkle and somewhat better than OpenWengo so I'd really like to continue using Ekiga if possible. Thanks Alan -- The way out is open! http://www.theopensourcerer.com From njaal at itek.norut.no Fri Oct 5 11:55:24 2007 From: njaal at itek.norut.no (=?ISO-8859-1?Q?Nj=E5l?= Borch) Date: Fri, 05 Oct 2007 13:55:24 +0200 Subject: [Ekiga-list] CIF over h261 on Ekiga 2.0 Message-ID: <1191585324.10701.0.camel@seer2.itek.norut.no> Hi all, I've used GnomeMeeting 1.2.1 with some Logitech quickcam pro 4000 to provide video conferencing. Using that setup, we ran CIF resolution video using the h261 video codec. Now that we're trying a similar setup based on Ekiga 2.0.11, we only get QCIF. This is unaffected by network limitations, as we're running it with max allowed bandwidth (100KB/s) on a LAN. The strange thing is that if I call Ekiga from GnomeMeeting, the GM video will be CIF resolution (and looks very good), while the return video is still QCIF and looks very bad. I have configured video size to be CIF in gconf, and the camera preview shows me a nice and crispy CIF image. On connect though, it switches to QCIF. Is there any special reason that Ekiga has "lost" the ability to use CIF resolution? Specially since it apparently can handle it well if the remote client sends it? Is there an easy fix? Best regards, N From dsandras at seconix.com Fri Oct 5 13:04:27 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 05 Oct 2007 15:04:27 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191573096.3343.7.camel@localhost.localdomain> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191573096.3343.7.camel@localhost.localdomain> Message-ID: <1191589467.4308.32.camel@scorpion> Le vendredi 05 octobre 2007 ? 14:01 +0530, Pratiksha Powar a ?crit : > Hi Damien, > > I'm able to connect to the Voice Applications server, but once connected > I'm unable to hear anything. > I have kept only PCMU and PCMA on. > Attached is the trace at level 4 > The trace is incomplete... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From arsphl at davidbowie.com Fri Oct 5 14:12:40 2007 From: arsphl at davidbowie.com (Philippe Laliberte) Date: Fri, 05 Oct 2007 15:12:40 +0100 Subject: [Ekiga-list] SIP Proxy Message-ID: <47064658.3030109@davidbowie.com> Hello, I am lost a bit about the uses of a SIP Proxy. I see how it is useful for outgoing calls, but I don't see how it can handle multiple ekiga.net addresses on different workstation. Setup: I have a non port translating firewall, that simply routes incoming calls to given internal IP. I have a certain number of workstations. If I set-up the routes for a specific workstation the RTP works fine both for calls out and incoming. So I assume that technically I should be able to have an outgoing/incoming relay behind the firewall that would make the distribution. Do I need to set-up a public domain name and an internal registrar? What am I missing here? ... Cheers, Philippe -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 207 bytes Desc: not available URL: From alanslists at gmail.com Fri Oct 5 15:50:42 2007 From: alanslists at gmail.com (Alan Lord) Date: Fri, 05 Oct 2007 16:50:42 +0100 Subject: [Ekiga-list] DTMF and Asterisk? In-Reply-To: <47060DF7.3080007@gmail.com> References: <47060DF7.3080007@gmail.com> Message-ID: <47065D52.9040703@gmail.com> Alan Lord wrote: > Hi all, > > I have started playing around with Asterisk recently. I got very > confused when I couldn't get it to respond to DTMF tones from my Ekiga > client. I tried loads of configuration settings on Asterisk and upgraded > to their latest version 1-4.12. Same problem. Sorry about replying to my own post but I just installed the Ekiga snapshot (20071001) and tried both RFC2833 and INFO but I still have the same problem. Both the Twinkle and OpenWengo phones work fine. Any Ideas? Cheers Alan -- The way out is open! http://www.theopensourcerer.com From dsandras at seconix.com Fri Oct 5 16:00:49 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 05 Oct 2007 18:00:49 +0200 Subject: [Ekiga-list] DTMF and Asterisk? In-Reply-To: <47065D52.9040703@gmail.com> References: <47060DF7.3080007@gmail.com> <47065D52.9040703@gmail.com> Message-ID: <1191600049.7486.15.camel@scorpion> Le vendredi 05 octobre 2007 ? 16:50 +0100, Alan Lord a ?crit : > Alan Lord wrote: > > Hi all, > > > > I have started playing around with Asterisk recently. I got very > > confused when I couldn't get it to respond to DTMF tones from my Ekiga > > client. I tried loads of configuration settings on Asterisk and upgraded > > to their latest version 1-4.12. Same problem. > > > Sorry about replying to my own post but I just installed the Ekiga > snapshot (20071001) and tried both RFC2833 and INFO but I still have the > same problem. Both the Twinkle and OpenWengo phones work fine. There must be a problem on the Asterisk side in that case... Don't you have debug on Asterisk's side ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Oct 5 16:01:37 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 05 Oct 2007 18:01:37 +0200 Subject: [Ekiga-list] consult the videos at a later date In-Reply-To: <215ff4410710050134x57125794y325407c61920a731@mail.gmail.com> References: <215ff4410710050134x57125794y325407c61920a731@mail.gmail.com> Message-ID: <1191600097.7486.17.camel@scorpion> Hello; Le vendredi 05 octobre 2007 ? 10:34 +0200, Chris Fanning a ?crit : > Hello, > > I've just signed up on the list. > Above all, I'd like to thank and congradulate the Ekiga team for this > excelent software. > > My question. > We would like to set up multi-point videoconferencing on our national > network. We have a Multipoint Control Unit. Ekiga seems a good option. > > But we also would like to save the conferences to files and add them > to a repository so users can consult the videos at a later date. > > How would you suggest doing this? (I hope this isn't off-topic). > It is not possible using Ekiga. I think that feature should be part of the MCU. I honnestly have no idea how to achieve this outside of the MCU or Ekiga, but if none of them supports the feature, it won't work. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Oct 5 16:02:31 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 05 Oct 2007 18:02:31 +0200 Subject: [Ekiga-list] CIF over h261 on Ekiga 2.0 In-Reply-To: <1191585324.10701.0.camel@seer2.itek.norut.no> References: <1191585324.10701.0.camel@seer2.itek.norut.no> Message-ID: <1191600151.7486.19.camel@scorpion> Hello, Le vendredi 05 octobre 2007 ? 13:55 +0200, Nj?l Borch a ?crit : > Hi all, > > I've used GnomeMeeting 1.2.1 with some Logitech quickcam pro 4000 to > provide video conferencing. Using that setup, we ran CIF resolution > video using the h261 video codec. Now that we're trying a similar setup > based on Ekiga 2.0.11, we only get QCIF. This is unaffected by network > limitations, as we're running it with max allowed bandwidth (100KB/s) on > a LAN. > > The strange thing is that if I call Ekiga from GnomeMeeting, the GM > video will be CIF resolution (and looks very good), while the return > video is still QCIF and looks very bad. > > I have configured video size to be CIF in gconf, and the camera preview > shows me a nice and crispy CIF image. On connect though, it switches to > QCIF. > > Is there any special reason that Ekiga has "lost" the ability to use CIF > resolution? Specially since it apparently can handle it well if the > remote client sends it? Is there an easy fix? You can try the SVN snapshot : http://snapshots.seconix.com/ The feature is back. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From alanslists at gmail.com Fri Oct 5 16:28:31 2007 From: alanslists at gmail.com (Alan Lord) Date: Fri, 05 Oct 2007 17:28:31 +0100 Subject: [Ekiga-list] DTMF and Asterisk? In-Reply-To: <1191600049.7486.15.camel@scorpion> References: <47060DF7.3080007@gmail.com> <47065D52.9040703@gmail.com> <1191600049.7486.15.camel@scorpion> Message-ID: <4706662F.20907@gmail.com> Damien Sandras wrote: > Le vendredi 05 octobre 2007 ? 16:50 +0100, Alan Lord a ?crit : >> Alan Lord wrote: >>> Hi all, >>> >>> I have started playing around with Asterisk recently. I got very >>> confused when I couldn't get it to respond to DTMF tones from my Ekiga >>> client. I tried loads of configuration settings on Asterisk and upgraded >>> to their latest version 1-4.12. Same problem. >> >> >> Sorry about replying to my own post but I just installed the Ekiga >> snapshot (20071001) and tried both RFC2833 and INFO but I still have the >> same problem. Both the Twinkle and OpenWengo phones work fine. > > There must be a problem on the Asterisk side in that case... > > Don't you have debug on Asterisk's side ? debug on what? I can see the DTMF packets being sent from Ekiga to Asterisk but it doesn't seem to recognise them. After removing the "dtmfmode=xxxx" comment entirely, the asterisk server now reads the dtmf tones! Setting it to RFC2833 or info didn't work. However Ekiga still misses playing the first message sent from the asterisk server. The other two soft phones do not... Any ideas? Cheers Alan -- The way out is open! http://www.theopensourcerer.com From bbagger at gmail.com Fri Oct 5 19:09:12 2007 From: bbagger at gmail.com (Bent) Date: Fri, 5 Oct 2007 21:09:12 +0200 Subject: [Ekiga-list] SIP Proxy In-Reply-To: <47064658.3030109@davidbowie.com> References: <47064658.3030109@davidbowie.com> Message-ID: <2e19719f0710051209t266d7e4eme21bdb6992a054a3@mail.gmail.com> Hello Philippe 2007/10/5, Philippe Laliberte : > > What am I missing here? ... > Without being rude: probably more knowledge about the finer details of SIP. Try this one: http://pcpanic.us/files/sip_tutorial.pdf Cisco's excellent journal 'The Internet Protocol Journal' had an article on SIP in Vol 6, No. 1, March 2003 on page 20. The whole issue is available here: http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_6-1/ipj_6-1.pdf Kind regards, Bent From arsphl at davidbowie.com Fri Oct 5 19:17:27 2007 From: arsphl at davidbowie.com (Philippe Laliberte) Date: Fri, 05 Oct 2007 20:17:27 +0100 Subject: [Ekiga-list] SIP Proxy In-Reply-To: <2e19719f0710051209t266d7e4eme21bdb6992a054a3@mail.gmail.com> References: <47064658.3030109@davidbowie.com> <2e19719f0710051209t266d7e4eme21bdb6992a054a3@mail.gmail.com> Message-ID: <47068DC7.7060106@davidbowie.com> Hello Bent, Not only it is not rude but it is what I was expecting. We can not all be SIP cracks and I did not find on SER or other SIP central system functional details. The RFC was not available to me a few hours ago. Thanks. That way I'll sleep with a fuller mind tonight... well it's Friday, it might melt down a little, 08:00 PM is late enough for serious activities. Cheers, Philippe Bent wrote: > Hello Philippe > > 2007/10/5, Philippe Laliberte : > >> What am I missing here? ... >> >> > Without being rude: probably more knowledge about the finer details of SIP. > > Try this one: http://pcpanic.us/files/sip_tutorial.pdf > > Cisco's excellent journal 'The Internet Protocol Journal' had an > article on SIP in Vol 6, No. 1, March 2003 on page 20. The whole issue > is available here: > http://www.cisco.com/web/about/ac123/ac147/archived_issues/ipj_6-1/ipj_6-1.pdf > > Kind regards, > > Bent > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 171 bytes Desc: not available URL: From 1.41421 at gmail.com Fri Oct 5 23:57:28 2007 From: 1.41421 at gmail.com (JCA) Date: Fri, 5 Oct 2007 16:57:28 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: I am trying to dial a 1-800 number in the US using Ekiga and my Ekiga PC-to-Phone account. When I do so, I get a recording to the effect that such number is not free from my current location, and that international calling fees will be charged if I proceed. This is kind of galling, for I am calling from the US. Is it at all possible to call 1-800 numbers at no charge with Ekiga? From mshahwan2001 at yahoo.com Sat Oct 6 04:42:52 2007 From: mshahwan2001 at yahoo.com (Michael) Date: Fri, 5 Oct 2007 21:42:52 -0700 (PDT) Subject: [Ekiga-list] DTMF and Asterisk? Message-ID: <146430.95197.qm@web52403.mail.re2.yahoo.com> We use Asterisk 1-4.11 and noticed that sometimes the DTMF tones are delayed. Once they pass through the other party cannot hear. We have SIP peers shown to see the ms per phone, but they are all less then 200 when this happens. How can we trouble shoot this issue? ----- Original Message ---- From: Alan Lord To: Ekiga mailing list Sent: Friday, October 5, 2007 11:28:31 AM Subject: Re: [Ekiga-list] DTMF and Asterisk? Damien Sandras wrote: > Le vendredi 05 octobre 2007 ? 16:50 +0100, Alan Lord a ?crit : >> Alan Lord wrote: >>> Hi all, >>> >>> I have started playing around with Asterisk recently. I got very >>> confused when I couldn't get it to respond to DTMF tones from my Ekiga >>> client. I tried loads of configuration settings on Asterisk and upgraded >>> to their latest version 1-4.12. Same problem. >> >> >> Sorry about replying to my own post but I just installed the Ekiga >> snapshot (20071001) and tried both RFC2833 and INFO but I still have the >> same problem. Both the Twinkle and OpenWengo phones work fine. > > There must be a problem on the Asterisk side in that case... > > Don't you have debug on Asterisk's side ? debug on what? I can see the DTMF packets being sent from Ekiga to Asterisk but it doesn't seem to recognise them. After removing the "dtmfmode=xxxx" comment entirely, the asterisk server now reads the dtmf tones! Setting it to RFC2833 or info didn't work. However Ekiga still misses playing the first message sent from the asterisk server. The other two soft phones do not... Any ideas? Cheers Alan -- The way out is open! http://www.theopensourcerer.com _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433 -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevmek at free.fr Sat Oct 6 04:45:26 2007 From: sevmek at free.fr (yannick) Date: Sat, 06 Oct 2007 06:45:26 +0200 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: <1191645926.6744.89.camel@achille> Le vendredi 05 octobre 2007 ? 16:57 -0700, JCA a ?crit : > I am trying to dial a 1-800 number in the US using Ekiga and my > Ekiga PC-to-Phone account. When I do so, I get a recording to the > effect that such number is not free from my current location, and that > international calling fees will be charged if I proceed. This is kind > of galling, for I am calling from the US. > > Is it at all possible to call 1-800 numbers at no charge with Ekiga? Yes, it is. Just get a free account on http://ekiga.net and dial : *0131800xxxxxxx at ekiga.net Further infos here: http://wiki.ekiga.org/index.php/Fun_Numbers Regards, Yannick > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From dsandras at seconix.com Sat Oct 6 13:23:53 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 06 Oct 2007 15:23:53 +0200 Subject: [Ekiga-list] DTMF and Asterisk? In-Reply-To: <146430.95197.qm@web52403.mail.re2.yahoo.com> References: <146430.95197.qm@web52403.mail.re2.yahoo.com> Message-ID: <1191677033.4156.13.camel@scorpion> I have the feeling Asterisk 1.4.11 is buggy with DTMFs. The only way to debug this is to sniff the traffic with wireshark and check which one is wrong : ekiga or asterisk. Le vendredi 05 octobre 2007 ? 21:42 -0700, Michael a ?crit : > We use Asterisk 1-4.11 and noticed that sometimes the DTMF tones are > delayed. Once they pass through the other party cannot hear. We have > SIP peers shown to see the ms per phone, but they are all less then > 200 when this happens. How can we trouble shoot this issue? > > ----- Original Message ---- > From: Alan Lord > To: Ekiga mailing list > Sent: Friday, October 5, 2007 11:28:31 AM > Subject: Re: [Ekiga-list] DTMF and Asterisk? > > Damien Sandras wrote: > > Le vendredi 05 octobre 2007 ? 16:50 +0100, Alan Lord a ?crit : > >> Alan Lord wrote: > >>> Hi all, > >>> > >>> I have started playing around with Asterisk recently. I got very > >>> confused when I couldn't get it to respond to DTMF tones from my > Ekiga > >>> client. I tried loads of configuration settings on Asterisk and > upgraded > >>> to their latest version 1-4.12. Same problem. > >> > >> > >> Sorry about replying to my own post but I just installed the Ekiga > >> snapshot (20071001) and tried both RFC2833 and INFO but I still > have the > >> same problem. Both the Twinkle and OpenWengo phones work fine. > > > > There must be a problem on the Asterisk side in that case... > > > > Don't you have debug on Asterisk's side ? > > debug on what? > > I can see the DTMF packets being sent from Ekiga to Asterisk but it > doesn't seem to recognise them. > > After removing the "dtmfmode=xxxx" comment entirely, the asterisk > server > now reads the dtmf tones! Setting it to RFC2833 or info didn't work. > > However Ekiga still misses playing the first message sent from the > asterisk server. The other two soft phones do not... Any ideas? > > Cheers > > Alan > > > -- > The way out is open! > http://www.theopensourcerer.com > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > ______________________________________________________________________ > Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: > mail, news, photos & more. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From iangrace at free.fr Sat Oct 6 16:17:42 2007 From: iangrace at free.fr (Ian Grace) Date: Sat, 06 Oct 2007 18:17:42 +0200 Subject: [Ekiga-list] Beginner's problems! Message-ID: <4707B526.40301@free.fr> I'm using Ekiga 2.0.3-0ubuntu8 on Ubuntu 7.04 (Feisty Fawn) and I'm hoping you can answer the following (NB non-technical beginner's language would be much appreciated!): - I downloaded Ekiga simply via the "Add applications" facility. I'm perplexed why Ubuntu doesn't appear in the "Choose your distribution" list (along with Fedora, Opensuse, Sources & even Windows) on your Home Page. Can you please confirm that Ubuntu is still suitable for Ekiga softphone and that the above version I have loaded is in fact the latest. - On the download page you stipulate *"**You need to download and install the OPAL and PWLIB libraries before Ekiga"*. Does this also apply to Ubuntu (even though Ubuntu isn't listed on that page and these libraries don't appear to be available via my Synaptic Package Manager)? In the latter, the nearest I can find are: "*Opalmod package" *(latest version 0.1.14), a set of Perl modules for Exception handle emulation; Simplified file and command read functions & Simplified debugging support. *"Pxlib-1" *(Library to read and write Paradox DB files) Am I right in saying that these are irrelevant? - When I was setting up Ekiga and I did the echo test, I could hear the automated voice perfectly but my voice sent back after a 4 second delay sounded far too distant (as if I were on the moon!). On trying to call the echo test again (by calling sip:500 at ekiga.net ), nothing happens and I see the message "Security Check failed". Is that normal ie can you only listen to the echo test on setting up Ekiga? - I tried calling friends' Hotmail addresses when they were logged into Windows Messenger Live; Ekiga would ring the dial tone twice but then cut off (with a message "could not connect to the remote server). Can you confirm that there should be NO problem in speaking (& text chatting simultaneously) between my Ekiga (using Feisty Fawn) & their Windows Messenger (as stated in your product descriptions)? In the SIP to call box, I simply inserted the standard Hotmail address - are Hotmail email addresses registered with Windows Messenger Live automatically SIP addresses?! - I also tried several Ekiga "SIP" addresses (from your "white pages" where subscribers invited test calls, including dsandras at ekiga.net ); Ekiga rang the dial tone for much longer but my call was either "rejected" or the "caller was unreachable". As I personally don't know anybody with an Ekiga address, do you happen to have any suggestions of any Ekiga subscribers I could call? Mine is sip:iangrace at ekiga.net - Is my computer suitable for use with Ekiga (audio and video)? It has an AMD Duron 600Mhz, 416Mb Ram, (40Gb HDD) and am I correct in thinking that ESS Technology *ES1969* (Solo 1) AUDIODRIVE (as listed in my "device manager") is my Sound card? ( The graphics card is Voodoo3 AGP) Ref the sound card, I'm also confused, as my "Input & Output" devices (in the "Preferences section") are listed as ESS *ES1938* (Solo-1). The model numbers apparently don't match, so do I have to reconfigure something? Thanks very much Ian -------------- next part -------------- An HTML attachment was scrubbed... URL: From 1.41421 at gmail.com Sat Oct 6 16:36:33 2007 From: 1.41421 at gmail.com (JCA) Date: Sat, 6 Oct 2007 09:36:33 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: >> I am trying to dial a 1-800 number in the US using Ekiga and my >> Ekiga PC-to-Phone account. When I do so, I get a recording to the >> effect that such number is not free from my current location, and that >> international calling fees will be charged if I proceed. This is kind >> of galling, for I am calling from the US. >> >> Is it at all possible to call 1-800 numbers at no charge with Ekiga? > > Yes, it is. > > Just get a free account on http://ekiga.net > and dial : > *0131800xxxxxxx at ekiga.net It doesn't work for me. I do have an ekiga.net account, I do have a PC-to-phone account, I can use them both all right, but if I try the recipe above I get a fleeting message that says Security Check Failed. From jpuydt at free.fr Sat Oct 6 17:03:15 2007 From: jpuydt at free.fr (Julien Puydt) Date: Sat, 06 Oct 2007 19:03:15 +0200 Subject: [Ekiga-list] Beginner's problems! In-Reply-To: <4707B526.40301@free.fr> References: <4707B526.40301@free.fr> Message-ID: <4707BFD3.30106@free.fr> Ian Grace a ?crit : > I'm using Ekiga 2.0.3-0ubuntu8 on Ubuntu 7.04 (Feisty Fawn) 2.0.3 is obsolete. 2.0.11 is out, and we provide packages. Snark on #ekiga From law_ence.dev at ntlworld.com Sat Oct 6 17:58:58 2007 From: law_ence.dev at ntlworld.com (ael) Date: Sat, 06 Oct 2007 18:58:58 +0100 Subject: [Ekiga-list] Beginner's problems! In-Reply-To: <4707BFD3.30106@free.fr> References: <4707B526.40301@free.fr> <4707BFD3.30106@free.fr> Message-ID: <4707CCE2.8090502@ntlworld.com> Julien Puydt wrote: > Ian Grace a ?crit : >> I'm using Ekiga 2.0.3-0ubuntu8 on Ubuntu 7.04 (Feisty Fawn) > > 2.0.3 is obsolete. 2.0.11 is out, and we provide packages. Yes, but Ian asked about Ubuntu. Neither Ubuntu nor debian packages are yet at http://www.ekiga.org/?rub=5 since we moved to 2.0.11. It's a pity that the links to 2.0.10 were not left for these distributions until the new packages arrive. The snapshots at http://snapshots.seconix.com/debian/pool/main/e/ekiga/ didn't work for me on debian etch. So the answer to the question is probably 1) Try http://snapshots.seconix.com/ubuntu/, or 2) wait for 2.0.11 to appear on www.ekiga.org or 3) collect the source from www.ekiga.org and compile yourself either as a local installation or as a deb package. 3) is not straightforward in that many other development packages need to be installed and often updated in a typical system. ael From sevmek at free.fr Sat Oct 6 22:45:03 2007 From: sevmek at free.fr (yannick) Date: Sun, 07 Oct 2007 00:45:03 +0200 Subject: [Ekiga-list] Beginner's problems! In-Reply-To: <4707CCE2.8090502@ntlworld.com> References: <4707B526.40301@free.fr> <4707BFD3.30106@free.fr> <4707CCE2.8090502@ntlworld.com> Message-ID: <1191710703.6744.100.camel@achille> Hi, Le samedi 06 octobre 2007 ? 18:58 +0100, ael a ?crit : > Julien Puydt wrote: > > Ian Grace a ?crit : > >> I'm using Ekiga 2.0.3-0ubuntu8 on Ubuntu 7.04 (Feisty Fawn) > > > > 2.0.3 is obsolete. 2.0.11 is out, and we provide packages. > > Yes, but Ian asked about Ubuntu. Neither Ubuntu nor debian packages are > yet at http://www.ekiga.org/?rub=5 since we moved to 2.0.11. It's a pity > that the links to 2.0.10 were not left for these distributions until the > new packages arrive. > This is due to lack of man power... 2.0.11 packages for Ubuntu will come when they will be ready... But, as I maintain the Ubuntu wiki about Ekiga, you can still use 2.0.9 (2.0.10 and 2.0.11 are almost the same) here: https://help.ubuntu.com/community/Ekiga The download for 2.0.9 are here: https://help.ubuntu.com/community/Ekiga#head-57385c7cf79361cbb4d7195b9f43c1bb33c1e94c By the way, you can't use Ekiga to join friends using *Windows Live Messenger*, you can join them if they use *Windows Messenger* (yes I know, this is confusing, but please don't blame us, Microsoft pick up those names and I'm pretty sure they know what they are doing : they just dropped SIP support in Vista in favor of their own private and closed protocol :( ) How to use windows messenger with ekiga.net: http://wiki.ekiga.org/index.php/Connecting_Windows_Messenger_5.1_to_ekiga.net Regards, Yannick > The snapshots at http://snapshots.seconix.com/debian/pool/main/e/ekiga/ > didn't work for me on debian etch. > > So the answer to the question is probably > > 1) Try http://snapshots.seconix.com/ubuntu/, > or > 2) wait for 2.0.11 to appear on www.ekiga.org > or > 3) collect the source from www.ekiga.org and compile yourself either as > a local installation or as a deb package. > > 3) is not straightforward in that many other development packages need > to be installed and often updated in a typical system. > > ael > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From dsandras at seconix.com Sun Oct 7 08:30:11 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 07 Oct 2007 10:30:11 +0200 Subject: [Ekiga-list] Beginner's problems! In-Reply-To: <4707CCE2.8090502@ntlworld.com> References: <4707B526.40301@free.fr> <4707BFD3.30106@free.fr> <4707CCE2.8090502@ntlworld.com> Message-ID: <1191745811.4170.0.camel@scorpion> Le samedi 06 octobre 2007 ? 18:58 +0100, ael a ?crit : > Julien Puydt wrote: > > Ian Grace a ?crit : > >> I'm using Ekiga 2.0.3-0ubuntu8 on Ubuntu 7.04 (Feisty Fawn) > > > > 2.0.3 is obsolete. 2.0.11 is out, and we provide packages. > > Yes, but Ian asked about Ubuntu. Neither Ubuntu nor debian packages are > yet at http://www.ekiga.org/?rub=5 since we moved to 2.0.11. It's a pity > that the links to 2.0.10 were not left for these distributions until the > new packages arrive. > I just uploaded them thanks to Kilian. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From pratiksha.powar at onmobile.com Mon Oct 8 10:52:47 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Mon, 08 Oct 2007 16:22:47 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191589467.4308.32.camel@scorpion> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191573096.3343.7.camel@localhost.localdomain> <1191589467.4308.32.camel@scorpion> Message-ID: <1191840767.12577.1.camel@localhost.localdomain> Hi Damien, Here is the latest trace at debugLevel=4. I again not able to connect to the Voice Application. Audio codecs on are PCMU and PCMA only. Thanks, Pratiksha On Fri, 2007-10-05 at 15:04 +0200, Damien Sandras wrote: > Le vendredi 05 octobre 2007 ? 14:01 +0530, Pratiksha Powar a ?crit : > > Hi Damien, > > > > I'm able to connect to the Voice Applications server, but once connected > > I'm unable to hear anything. > > I have kept only PCMU and PCMA on. > > Attached is the trace at level 4 > > > > The trace is incomplete... -------------- next part -------------- ute "pc:.*=sip:" 2007/10/08 16:19:32.531 0:00.640 ekiga OpalEP Created endpoint: pc 2007/10/08 16:19:32.532 0:00.641 ekiga PCSS Created PC sound system endpoint. 2007/10/08 16:19:32.532 0:00.641 ekiga OpalMan Added route "h323:.*=pc:" 2007/10/08 16:19:32.532 0:00.641 ekiga OpalMan Added route "sip:.*=pc:" 2007/10/08 16:19:32.551 0:00.660 Opal Listener:95b2198 Listen Started listening thread on tcp$172.16.25.113:1720 2007/10/08 16:19:32.551 0:00.661 Opal Listener:95b2198 Listen Waiting on socket accept on tcp$172.16.25.113:1720 2007/10/08 16:19:32.552 0:00.661 Opal Listener:95b2bb8 Listen Started listening thread on udp$172.16.25.113:5060 2007/10/08 16:19:32.553 0:00.662 Opal Listener:95b2bb8 Listen Waiting on UDP packet on udp$172.16.25.113:5060 2007/10/08 16:19:32.556 0:00.665 ekiga AVAHI Adding service Pratiksha Powar 2007/10/08 16:19:36.398 0:04.507 GMURLHandler:0942f5f8 OpalMan Set up call from pc:* to sip:123 at 172.16.29.68 2007/10/08 16:19:36.399 0:04.508 GMURLHandler:0942f5f8 Call Created Call[1] 2007/10/08 16:19:36.399 0:04.508 GMURLHandler:0942f5f8 OpalMan Set up connection to "pc:*" 2007/10/08 16:19:36.402 0:04.511 GMURLHandler:0942f5f8 OpalCon Created connection Call[1]-EP[Default] 2007/10/08 16:19:36.402 0:04.512 GMURLHandler:0942f5f8 RFC2833 Handler created 2007/10/08 16:19:36.403 0:04.512 GMURLHandler:0942f5f8 Silence Handler created 2007/10/08 16:19:36.403 0:04.512 GMURLHandler:0942f5f8 Echo Canceler Handler created 2007/10/08 16:19:36.403 0:04.512 GMURLHandler:0942f5f8 PCSS Created PC sound system connection. 2007/10/08 16:19:36.403 0:04.512 GMURLHandler:0942f5f8 OpalMan On incoming connection Call[1]-EP[Default] 2007/10/08 16:19:36.403 0:04.512 GMURLHandler:0942f5f8 Call GetOtherPartyConnection Call[1]-EP[Default] 2007/10/08 16:19:36.403 0:04.512 GMURLHandler:0942f5f8 OpalMan Set up connection to "sip:123 at 172.16.29.68" 2007/10/08 16:19:36.404 0:04.513 GMURLHandler:0942f5f8 OpalCon Created connection Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] 2007/10/08 16:19:36.404 0:04.513 GMURLHandler:0942f5f8 RFC2833 Handler created 2007/10/08 16:19:36.405 0:04.515 GMURLHandler:0942f5f8 SIP Created connection. 2007/10/08 16:19:36.406 0:04.515 GMURLHandler:0942f5f8 PCSS Outgoing call routed to sip:123 at 172.16.29.68 for Call[1]-EP[Default] 2007/10/08 16:19:36.407 0:04.516 GMURLHandler:0942f5f8 Call OnSetUp Call[1]-EP[Default] 2007/10/08 16:19:36.408 0:04.517 GMURLHandler:0942f5f8 SIP SetUpConnection: 2007/10/08 16:19:36.409 0:04.518 GMURLHandler:0942f5f8 OpalUDP Binding to interface: 172.16.25.113:32859 2007/10/08 16:19:36.409 0:04.518 GMURLHandler:0942f5f8 SIP Created transport udp$0.0.0.0 2007/10/08 16:19:36.409 0:04.518 GMURLHandler:0942f5f8 OpalUDP Started connect to 172.16.29.68:5060 2007/10/08 16:19:36.410 0:04.519 GMURLHandler:0942f5f8 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/08 16:19:36.413 0:04.522 SIP Transport:94d49f0 SIP Read thread started. 2007/10/08 16:19:36.413 0:04.522 SIP Transport:94d49f0 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/08 16:19:36.414 0:04.523 GMURLHandler:0942f5f8 SIP Transaction 1 INVITE created. 2007/10/08 16:19:36.414 0:04.523 GMURLHandler:0942f5f8 Call CanDoMediaBypass Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] session 1 2007/10/08 16:19:36.415 0:04.524 GMURLHandler:0942f5f8 OpalMan IsMediaBypassPossible: session 1 2007/10/08 16:19:36.416 0:04.525 GMURLHandler:0942f5f8 SIP IsMediaBypassPossible: session 1 2007/10/08 16:19:36.416 0:04.525 GMURLHandler:0942f5f8 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/08 16:19:36.416 0:04.525 GMURLHandler:0942f5f8 RTP_UDP Session 1 created: 172.16.25.113:5000-5001 ssrc=1412891838 2007/10/08 16:19:36.416 0:04.525 GMURLHandler:0942f5f8 RTP Adding session RTP_UDP 2007/10/08 16:19:36.429 0:04.538 GMURLHandler:0942f5f8 Call GetMediaFormats for Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] G.711-ALaw-64k G.711-uLaw-64k H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/08 16:19:36.431 0:04.540 GMURLHandler:0942f5f8 SIP Using RTP payload [pt=101] for NTE 2007/10/08 16:19:36.432 0:04.542 GMURLHandler:0942f5f8 SIP No authentication information present 2007/10/08 16:19:36.434 0:04.543 GMURLHandler:0942f5f8 SIP Sending PDU on udp$172.16.29.68:5060 INVITE sip:123 at 172.16.29.68 SIP/2.0 Date: Mon, 08 Oct 2007 10:49:36 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK780a8ad4-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: "Pratiksha Powar" ;tag=a08e88d4-f973-dc11-9bc9-0019b97d3b5d Call-ID: d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 230 Max-Forwards: 70 v=0 o=- 1191840576 1191840576 IN IP4 172.16.25.113 s=Opal SIP Session c=IN IP4 172.16.25.113 t=0 0 m=audio 5000 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 2007/10/08 16:19:36.435 0:04.544 GMURLHandler:0942f5f8 SetUpCall succeeded 2007/10/08 16:19:36.933 0:05.042 Housekeeper SIP Transaction 1 INVITE timeout, making retry 1 2007/10/08 16:19:36.934 0:05.043 Housekeeper SIP Sending PDU on udp$172.16.29.68:5060 INVITE sip:123 at 172.16.29.68 SIP/2.0 Date: Mon, 08 Oct 2007 10:49:36 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK780a8ad4-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: "Pratiksha Powar" ;tag=a08e88d4-f973-dc11-9bc9-0019b97d3b5d Call-ID: d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 230 Max-Forwards: 70 v=0 o=- 1191840576 1191840576 IN IP4 172.16.25.113 s=Opal SIP Session c=IN IP4 172.16.25.113 t=0 0 m=audio 5000 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 2007/10/08 16:19:37.934 0:06.043 Housekeeper SIP Transaction 1 INVITE timeout, making retry 2 2007/10/08 16:19:37.935 0:06.044 Housekeeper SIP Sending PDU on udp$172.16.29.68:5060 INVITE sip:123 at 172.16.29.68 SIP/2.0 Date: Mon, 08 Oct 2007 10:49:36 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK780a8ad4-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: "Pratiksha Powar" ;tag=a08e88d4-f973-dc11-9bc9-0019b97d3b5d Call-ID: d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 230 Max-Forwards: 70 v=0 o=- 1191840576 1191840576 IN IP4 172.16.25.113 s=Opal SIP Session c=IN IP4 172.16.25.113 t=0 0 m=audio 5000 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 2007/10/08 16:19:38.135 0:06.244 GMStunClient:092e4d60 OPAL STUN server "stun.ekiga.net" replies Blocked, external IP 0.0.0.0 2007/10/08 16:19:38.144 0:06.253 GMAccounts...t:095b62e8 OpalUDP Binding to interface: 172.16.25.113:32859 2007/10/08 16:19:38.144 0:06.253 GMAccounts...t:095b62e8 SIP Created transport udp$0.0.0.0 2007/10/08 16:19:38.144 0:06.253 GMAccounts...t:095b62e8 OpalUDP Started connect to 86.64.162.35:5060 2007/10/08 16:19:38.144 0:06.253 GMAccounts...t:095b62e8 OpalUDP STUN could not create socket! 2007/10/08 16:19:38.145 0:06.254 GMAccounts...t:095b62e8 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/08 16:19:38.145 0:06.254 GMAccounts...t:095b62e8 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/08 16:19:38.147 0:06.256 GMAccounts...t:095b62e8 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKca5e92d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f25492d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: 1ef791d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:38.148 0:06.257 SIP Transport:b5066c60 SIP Read thread started. 2007/10/08 16:19:38.148 0:06.257 SIP Transport:b5066c60 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/08 16:19:38.149 0:06.258 GMAccounts...t:095b62e8 OpalUDP Binding to interface: 172.16.25.113:32859 2007/10/08 16:19:38.149 0:06.258 GMAccounts...t:095b62e8 SIP Created transport udp$0.0.0.0 2007/10/08 16:19:38.149 0:06.258 GMAccounts...t:095b62e8 OpalUDP Started connect to 86.64.162.35:5060 2007/10/08 16:19:38.150 0:06.259 GMAccounts...t:095b62e8 OpalUDP STUN could not create socket! 2007/10/08 16:19:38.150 0:06.259 GMAccounts...t:095b62e8 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/08 16:19:38.150 0:06.259 GMAccounts...t:095b62e8 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/08 16:19:38.152 0:06.261 SIP Transport:b5088f10 SIP Read thread started. 2007/10/08 16:19:38.152 0:06.261 SIP Transport:b5088f10 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/08 16:19:38.153 0:06.262 GMAccounts...t:095b62e8 SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKa23093d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=da2593d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: acc792d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:38.647 0:06.756 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1 2007/10/08 16:19:38.647 0:06.756 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKca5e92d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f25492d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: 1ef791d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:38.652 0:06.761 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 1 2007/10/08 16:19:38.652 0:06.761 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKa23093d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=da2593d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: acc792d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:39.647 0:07.756 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 2 2007/10/08 16:19:39.647 0:07.756 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKca5e92d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f25492d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: 1ef791d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:39.652 0:07.761 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 2 2007/10/08 16:19:39.652 0:07.761 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKa23093d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=da2593d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: acc792d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:39.935 0:08.044 Housekeeper SIP Transaction 1 INVITE timeout, making retry 3 2007/10/08 16:19:39.936 0:08.045 Housekeeper SIP Sending PDU on udp$172.16.29.68:5060 INVITE sip:123 at 172.16.29.68 SIP/2.0 Date: Mon, 08 Oct 2007 10:49:36 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK780a8ad4-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: "Pratiksha Powar" ;tag=a08e88d4-f973-dc11-9bc9-0019b97d3b5d Call-ID: d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Type: application/sdp Content-Length: 230 Max-Forwards: 70 v=0 o=- 1191840576 1191840576 IN IP4 172.16.25.113 s=Opal SIP Session c=IN IP4 172.16.25.113 t=0 0 m=audio 5000 RTP/AVP 8 0 101 a=rtpmap:8 PCMA/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 2007/10/08 16:19:41.647 0:09.756 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 3 2007/10/08 16:19:41.647 0:09.756 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bKca5e92d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=f25492d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: 1ef791d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:41.652 0:09.761 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2007/10/08 16:19:41.652 0:09.761 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKa23093d5-f973-dc11-9bc9-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=da2593d5-f973-dc11-9bc9-0019b97d3b5d Call-ID: acc792d5-f973-dc11-9bc9-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:19:42.434 0:10.543 Housekeeper SIP Set state Terminated_Timeout for transaction 1 INVITE 2007/10/08 16:19:42.434 0:10.543 Housekeeper OpalCon Releasing Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] 2007/10/08 16:19:42.434 0:10.543 Housekeeper OpalCon Call end reason for d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha set to EndedByConnectFail 2007/10/08 16:19:42.434 0:10.543 Housekeeper OpalCon SetPhase from UninitialisedPhase to ReleasingPhase 2007/10/08 16:19:42.434 0:10.543 OnRelease:b508a248 SIP OnReleased: Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha], phase = ReleasingPhase 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 OpalCon SetPhase from ReleasingPhase to ReleasingPhase 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 SIP Cancelling transaction 0 of 1 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 SIP Could not cancel transaction 0 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 OpalCon Media stream threads closed. 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 OpalCon SetPhase from ReleasingPhase to ReleasedPhase 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 Opal Transport clean up on termination 2007/10/08 16:19:42.435 0:10.544 OnRelease:b508a248 OpalUDP Close 2007/10/08 16:19:42.435 0:10.545 SIP Transport:94d49f0 OpalUDP Error on connection read select. 2007/10/08 16:19:42.436 0:10.545 SIP Transport:94d49f0 SIP Read thread finished. 2007/10/08 16:19:42.446 0:10.555 OnRelease:b508a248 OpalCon OnReleased Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] 2007/10/08 16:19:42.446 0:10.555 OnRelease:b508a248 OpalCon Media stream threads closed. 2007/10/08 16:19:42.446 0:10.555 OnRelease:b508a248 GMSIPEndpoint SIP connection released 2007/10/08 16:19:42.446 0:10.555 OnRelease:b508a248 OpalEP OnReleased Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 GMManager Will release the connection 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 OpalMan OnReleased Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 Call OnReleased Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 OpalCon Releasing Call[1]-EP[Default] 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 OpalCon Call end reason for Default set to EndedByConnectFail 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 OpalCon SetPhase from SetUpPhase to ReleasingPhase 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 RTP_UDP Session 1, Shutting down read. 2007/10/08 16:19:42.455 0:10.564 OnRelease:b508a248 RTP_UDP Session 1, Shutting down write. 2007/10/08 16:19:42.467 0:10.576 OnRelease:b508a248 SIP Transaction 1 INVITE destroyed. 2007/10/08 16:19:42.467 0:10.576 OnRelease:b508a248 OpalCon OnRelease thread completed for d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha 2007/10/08 16:19:42.467 0:10.576 OnRelease:967d020 OpalCon OnReleased Call[1]-EP[Default] 2007/10/08 16:19:42.467 0:10.576 OnRelease:967d020 OpalCon Media stream threads closed. 2007/10/08 16:19:42.646 0:10.755 OnRelease:967d020 GMPCSSEndpoint PCSS connection released 2007/10/08 16:19:42.646 0:10.755 OnRelease:967d020 OpalEP OnReleased Call[1]-EP[Default] 2007/10/08 16:19:42.646 0:10.755 OnRelease:967d020 GMManager Will release the connection 2007/10/08 16:19:42.646 0:10.755 OnRelease:967d020 OpalMan OnReleased Call[1]-EP[Default] 2007/10/08 16:19:42.646 0:10.755 OnRelease:967d020 Call OnReleased Call[1]-EP[Default] 2007/10/08 16:19:42.669 0:10.784 OnRelease:967d020 OpalCon OnRelease thread completed for Default 2007/10/08 16:19:42.957 0:11.066 OpalGarbage Opal Transport clean up on termination 2007/10/08 16:19:42.957 0:11.066 OpalGarbage OpalUDP Close 2007/10/08 16:19:42.957 0:11.066 OpalGarbage SIP Deleted connection. 2007/10/08 16:19:42.957 0:11.066 OpalGarbage OpalCon Connection Call[1]-EP[d68088d4-f973-dc11-9bc9-0019b97d3b5d at Pratiksha] destroyed. 2007/10/08 16:19:42.957 0:11.066 OpalGarbage PCSS Deleted PC sound system connection. 2007/10/08 16:19:42.957 0:11.067 OpalGarbage OpalCon Connection Call[1]-EP[Default] destroyed. 2007/10/08 16:19:43.960 0:12.069 OpalGarbage Call Call[1] destroyed. 2007/10/08 16:19:44.147 0:12.256 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2007/10/08 16:19:44.153 0:12.262 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE Killed -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From dsandras at seconix.com Mon Oct 8 11:02:01 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 08 Oct 2007 13:02:01 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191840767.12577.1.camel@localhost.localdomain> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191573096.3343.7.camel@localhost.localdomain> <1191589467.4308.32.camel@scorpion> <1191840767.12577.1.camel@localhost.localdomain> Message-ID: <1191841321.4925.45.camel@scorpion> Hi, Le lundi 08 octobre 2007 ? 16:22 +0530, Pratiksha Powar a ?crit : > Hi Damien, > > Here is the latest trace at debugLevel=4. > I again not able to connect to the Voice Application. > Audio codecs on are PCMU and PCMA only. > The SIP server does not answer : Transaction 1 INVITE timeout, making retry 3 Make sure Ekiga is listening on the correct interface and make sure it is not down. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From pratiksha.powar at onmobile.com Mon Oct 8 11:17:35 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Mon, 08 Oct 2007 16:47:35 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191841321.4925.45.camel@scorpion> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191573096.3343.7.camel@localhost.localdomain> <1191589467.4308.32.camel@scorpion> <1191840767.12577.1.camel@localhost.localdomain> <1191841321.4925.45.camel@scorpion> Message-ID: <1191842255.12577.4.camel@localhost.localdomain> Hi Damien, I restarted the process on the Voice App Server. I could connect using Ekiga. But I still hear anything. Here is the trace at d 4. Thanks, Pratiksha On Mon, 2007-10-08 at 13:02 +0200, Damien Sandras wrote: > Hi, > > Le lundi 08 octobre 2007 ? 16:22 +0530, Pratiksha Powar a ?crit : > > Hi Damien, > > > > Here is the latest trace at debugLevel=4. > > I again not able to connect to the Voice Application. > > Audio codecs on are PCMU and PCMA only. > > > > The SIP server does not answer : > Transaction 1 INVITE timeout, making retry 3 > > Make sure Ekiga is listening on the correct interface and make sure it > is not down. -------------- next part -------------- a=rtpmap:96 telephone-event/8000 a=ptime:20 2007/10/08 16:43:45.943 0:04.729 SIP Transport:98449a8 OpalUDP Ended connect, selecting 172.16.25.113:5062 2007/10/08 16:43:45.943 0:04.729 SIP Transport:98449a8 SIP Queueing PDU: 1 INVITE <180> 2007/10/08 16:43:45.943 0:04.729 SIP Transport:98449a8 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/08 16:43:45.944 0:04.730 SIP Handler:981e608 SIP PDU handler thread started. 2007/10/08 16:43:45.944 0:04.730 SIP Handler:981e608 SIP Awaiting next PDU. 2007/10/08 16:43:45.944 0:04.730 SIP Handler:981e608 SIP Handling PDU 1 INVITE <180> 2007/10/08 16:43:45.944 0:04.730 SIP Handler:981e608 SIP Transaction 1 INVITE proceeding. 2007/10/08 16:43:45.944 0:04.730 SIP Handler:981e608 SIP Received Ringing response 2007/10/08 16:43:45.945 0:04.731 SIP Handler:981e608 OpalCon SetPhase from UninitialisedPhase to AlertingPhase 2007/10/08 16:43:45.945 0:04.731 SIP Handler:981e608 OpalMan OnAlerting Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:45.945 0:04.731 SIP Handler:981e608 Call OnAlerting Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:45.945 0:04.731 SIP Handler:981e608 PCSS SetAlerting(123 at 172.16.29.68) 2007/10/08 16:43:45.945 0:04.731 SIP Handler:981e608 SIP Awaiting next PDU. 2007/10/08 16:43:45.962 0:04.748 SIP Transport:98449a8 SDP Origin has 7 elements 2007/10/08 16:43:45.962 0:04.748 SIP Transport:98449a8 SDP Media session port=9022 2007/10/08 16:43:45.962 0:04.748 SIP Transport:98449a8 SDP Adding media session with 2 formats 2007/10/08 16:43:45.962 0:04.748 SIP Transport:98449a8 SDP Media attribute rtpmap found for unknown RTP type [pt=96] 2007/10/08 16:43:45.963 0:04.749 SIP Transport:98449a8 SIP PDU Received on udp$172.16.29.68:5060 SIP/2.0 200 OK CSeq: 1 INVITE Via: SIP/2.0/UDP 172.16.25.113:5062;rport;branch=z9hG4bKb60e8034-fd73-dc11-864a-0019b97d3b5d From: "Pratiksha Powar" ;tag=4c847e34-fd73-dc11-864a-0019b97d3b5d Call-ID: 2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: ;tag=b39b0300 Content-Type: application/sdp Content-Length: 221 v=0 o=onmobilesipua 1191842025 1191842025 IN IP4 172.16.18.69 s=phone-call c=IN IP4 172.16.18.69 t=2208988800 2208988800 m=audio 9022 RTP/AVP 0 0 a=rtpmap:0 PCMU/8000 a=rtpmap:96 telephone-event/8000 a=ptime:20 2007/10/08 16:43:45.963 0:04.749 SIP Transport:98449a8 SIP Queueing PDU: 1 INVITE <200> 2007/10/08 16:43:45.963 0:04.749 SIP Transport:98449a8 SIP Waiting for PDU on udp$172.16.29.68:5060 2007/10/08 16:43:45.964 0:04.750 SIP Handler:981e608 SIP Handling PDU 1 INVITE <200> 2007/10/08 16:43:45.964 0:04.750 SIP Handler:981e608 SIP Transaction 1 INVITE completed. 2007/10/08 16:43:45.966 0:04.752 SIP Handler:981e608 SIP Sending PDU on udp$172.16.29.68:5060 ACK sip:123 at 172.16.29.68 SIP/2.0 CSeq: 1 ACK Via: SIP/2.0/UDP 172.16.25.113:5062;branch=z9hG4bK04258a34-fd73-dc11-864a-0019b97d3b5d;rport From: "Pratiksha Powar" ;tag=4c847e34-fd73-dc11-864a-0019b97d3b5d Call-ID: 2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: ;tag=b39b0300 Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:45.966 0:04.752 SIP Handler:981e608 SIP Received INVITE OK response 2007/10/08 16:43:45.966 0:04.752 SIP Handler:981e608 SIP RTP payload type PCMU matched to codec G.711-uLaw-64k 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 SIP RTP payload type PCMU matched to codec G.711-uLaw-64k 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 Call GetOtherPartyConnection Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 Call CanDoMediaBypass Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] session 1 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 OpalMan IsMediaBypassPossible: session 1 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 SIP IsMediaBypassPossible: session 1 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 RTP Found existing session 1 2007/10/08 16:43:45.967 0:04.753 SIP Handler:981e608 RTP_UDP SetRemoteSocketInfo: session=1 data channel, new=172.16.18.69:9022, local=172.16.25.113:5000-5001, remote=0.0.0.0:0-0 2007/10/08 16:43:45.968 0:04.754 SIP Handler:981e608 SIP RTP payload type PCMU matched to codec G.711-uLaw-64k 2007/10/08 16:43:45.968 0:04.754 SIP Handler:981e608 SIP RTP payload type PCMU matched to codec G.711-uLaw-64k 2007/10/08 16:43:45.968 0:04.754 SIP Handler:981e608 Call OpenSourceMediaStreams for session 1 with media G.711-uLaw-64k 2007/10/08 16:43:45.968 0:04.754 SIP Handler:981e608 OpalCon OpenSourceMediaStream for session 1 on Call[1]-EP[Default] 2007/10/08 16:43:45.970 0:04.756 SIP Handler:981e608 OpalCon Selected media stream PCM-16 -> G.711-uLaw-64k 2007/10/08 16:43:45.970 0:04.756 SIP Handler:981e608 Ekiga Creating Sound Channel 2007/10/08 16:43:47.494 0:06.280 Housekeeper SIP Set state Terminated_Success for transaction 1 INVITE 2007/10/08 16:43:47.543 0:06.329 GMStunClient:097e6000 OPAL STUN server "stun.ekiga.net" replies Blocked, external IP 0.0.0.0 2007/10/08 16:43:47.550 0:06.336 GMAccounts...t:09737848 OpalUDP Binding to interface: 172.16.25.113:32869 2007/10/08 16:43:47.550 0:06.336 GMAccounts...t:09737848 SIP Created transport udp$0.0.0.0 2007/10/08 16:43:47.551 0:06.337 GMAccounts...t:09737848 OpalUDP Started connect to 86.64.162.35:5060 2007/10/08 16:43:47.552 0:06.338 GMAccounts...t:09737848 OpalUDP STUN could not create socket! 2007/10/08 16:43:47.553 0:06.339 GMAccounts...t:09737848 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/08 16:43:47.554 0:06.340 GMAccounts...t:09737848 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/08 16:43:47.555 0:06.341 SIP Transport:9675418 SIP Read thread started. 2007/10/08 16:43:47.555 0:06.341 SIP Transport:9675418 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/08 16:43:47.557 0:06.343 GMAccounts...t:09737848 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bK74c17c35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=c4b77c35-fd73-dc11-864a-0019b97d3b5d Call-ID: 60c27b35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:47.559 0:06.345 GMAccounts...t:09737848 OpalUDP Binding to interface: 172.16.25.113:32869 2007/10/08 16:43:47.559 0:06.345 GMAccounts...t:09737848 SIP Created transport udp$0.0.0.0 2007/10/08 16:43:47.559 0:06.345 GMAccounts...t:09737848 OpalUDP Started connect to 86.64.162.35:5060 2007/10/08 16:43:47.559 0:06.345 GMAccounts...t:09737848 OpalUDP STUN could not create socket! 2007/10/08 16:43:47.560 0:06.346 GMAccounts...t:09737848 OpalUDP Connect on pre-bound interface: 172.16.25.113 2007/10/08 16:43:47.560 0:06.346 GMAccounts...t:09737848 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/08 16:43:47.562 0:06.348 SIP Transport:b500e888 SIP Read thread started. 2007/10/08 16:43:47.562 0:06.348 SIP Transport:b500e888 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/08 16:43:47.562 0:06.348 GMAccounts...t:09737848 SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKee8c7d35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=cc817d35-fd73-dc11-864a-0019b97d3b5d Call-ID: 28267d35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:47.809 0:06.595 SIP Handler:981e608 OpalMan OnOpenMediaStream Call[1]-EP[Default],OpalAudioMediaStream-Source-PCM-16 2007/10/08 16:43:47.810 0:06.596 SIP Handler:981e608 Call PatchMediaStreams Call[1]-EP[Default] 2007/10/08 16:43:47.810 0:06.596 SIP Handler:981e608 OpalCon OpenSinkMediaStream Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] session=1 2007/10/08 16:43:47.810 0:06.596 SIP Handler:981e608 OpalCon OpenSinkMediaStream, selected PCM-16 -> G.711-uLaw-64k 2007/10/08 16:43:47.810 0:06.596 SIP Handler:981e608 Call CanDoMediaBypass Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] session 1 2007/10/08 16:43:47.811 0:06.597 SIP Handler:981e608 OpalMan IsMediaBypassPossible: session 1 2007/10/08 16:43:47.811 0:06.597 SIP Handler:981e608 SIP IsMediaBypassPossible: session 1 2007/10/08 16:43:47.811 0:06.597 SIP Handler:981e608 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/08 16:43:47.811 0:06.597 SIP Handler:981e608 RTP Found existing session 1 2007/10/08 16:43:47.811 0:06.597 SIP Handler:981e608 RTP Found existing session 1 2007/10/08 16:43:47.811 0:06.597 SIP Handler:981e608 OpalMan OnOpenMediaStream Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha],OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/08 16:43:47.814 0:06.600 SIP Handler:981e608 Codec G711-uLaw-64k encoder created 2007/10/08 16:43:47.815 0:06.601 SIP Handler:981e608 Patch Added media stream sink OpalRTPMediaStream-Sink-G.711-uLaw-64k using transcoder PCM-16->G.711-uLaw-64k 2007/10/08 16:43:47.816 0:06.602 SIP Handler:981e608 Media Audio source data size set to 320 bytes and 20 buffers. 2007/10/08 16:43:47.816 0:06.602 SIP Handler:981e608 OpalCon New patch created 2007/10/08 16:43:47.817 0:06.603 SIP Handler:981e608 OpalCon New patch created 2007/10/08 16:43:47.821 0:06.607 SIP Handler:981e608 Call OpenSourceMediaStreams for session 1 adjusted media to G.711-uLaw-64k 2007/10/08 16:43:47.821 0:06.607 SIP Handler:981e608 Call GetOtherPartyConnection Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:47.822 0:06.608 SIP Handler:981e608 OpalCon OpenSourceMediaStream for session 1 on Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:47.822 0:06.608 SIP Handler:981e608 OpalCon Selected media stream G.711-uLaw-64k -> PCM-16 2007/10/08 16:43:47.822 0:06.608 SIP Handler:981e608 Call CanDoMediaBypass Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] session 1 2007/10/08 16:43:47.822 0:06.608 SIP Handler:981e608 OpalMan IsMediaBypassPossible: session 1 2007/10/08 16:43:47.822 0:06.608 SIP Handler:981e608 SIP IsMediaBypassPossible: session 1 2007/10/08 16:43:47.822 0:06.608 SIP Handler:981e608 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/08 16:43:47.822 0:06.609 SIP Handler:981e608 RTP Found existing session 1 2007/10/08 16:43:47.823 0:06.609 SIP Handler:981e608 RTP Found existing session 1 2007/10/08 16:43:47.823 0:06.609 SIP Handler:981e608 OpalMan OnOpenMediaStream Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha],OpalRTPMediaStream-Source-G.711-uLaw-64k 2007/10/08 16:43:47.823 0:06.609 SIP Handler:981e608 Call PatchMediaStreams Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:47.823 0:06.609 SIP Handler:981e608 OpalCon OpenSinkMediaStream Call[1]-EP[Default] session=1 2007/10/08 16:43:47.823 0:06.610 SIP Handler:981e608 OpalCon OpenSinkMediaStream, selected G.711-uLaw-64k -> PCM-16 2007/10/08 16:43:47.824 0:06.610 SIP Handler:981e608 Ekiga Creating Sound Channel 2007/10/08 16:43:48.056 0:06.842 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1 2007/10/08 16:43:48.056 0:06.842 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bK74c17c35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=c4b77c35-fd73-dc11-864a-0019b97d3b5d Call-ID: 60c27b35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:48.062 0:06.848 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 1 2007/10/08 16:43:48.062 0:06.848 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKee8c7d35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=cc817d35-fd73-dc11-864a-0019b97d3b5d Call-ID: 28267d35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:48.140 0:06.926 SIP Handler:981e608 OpalMan OnOpenMediaStream Call[1]-EP[Default],OpalAudioMediaStream-Sink-PCM-16 2007/10/08 16:43:48.142 0:06.928 SIP Handler:981e608 Codec G711-uLaw-64k decoder created 2007/10/08 16:43:48.142 0:06.928 SIP Handler:981e608 Media Audio sink data size set to 320 bytes and 20 buffers. 2007/10/08 16:43:48.143 0:06.929 SIP Handler:981e608 Patch Added media stream sink OpalAudioMediaStream-Sink-PCM-16 using transcoder G.711-uLaw-64k->PCM-16 2007/10/08 16:43:48.143 0:06.929 SIP Handler:981e608 OpalCon New patch created 2007/10/08 16:43:48.143 0:06.929 SIP Handler:981e608 OpalCon New patch created 2007/10/08 16:43:48.144 0:06.930 SIP Handler:981e608 OpalCon OpenSourceMediaStream (already opened) for session 1 on Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 SIP Could not find SDP media description for Video 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 OpalMan OnConnected Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 Call OnConnected Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 PCSS SetConnected() 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 GMPCSSEndpoint PCSS connection established 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 GMManager Will establish the connection 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 OpalMan OnEstablished Call[1]-EP[Default] 2007/10/08 16:43:48.145 0:06.931 SIP Handler:981e608 Call OnEstablished Call[1]-EP[Default] 2007/10/08 16:43:48.155 0:06.941 SIP Handler:981e608 Call GetMediaFormats for Call[1]-EP[Default] G.711-uLaw-64k 2007/10/08 16:43:48.155 0:06.941 SIP Handler:981e608 Call OpenSourceMediaStreams for session 1 with media G.711-uLaw-64k 2007/10/08 16:43:48.155 0:06.941 SIP Handler:981e608 OpalCon OpenSourceMediaStream (already opened) for session 1 on Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:48.155 0:06.941 SIP Handler:981e608 Call OpenSourceMediaStreams for session 2 with media G.711-uLaw-64k 2007/10/08 16:43:48.163 0:06.949 SIP Handler:981e608 Call GetMediaFormats for Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] G.711-uLaw-64k 2007/10/08 16:43:48.163 0:06.949 SIP Handler:981e608 Call OpenSourceMediaStreams for session 1 with media G.711-uLaw-64k 2007/10/08 16:43:48.163 0:06.949 SIP Handler:981e608 OpalCon OpenSourceMediaStream (already opened) for session 1 on Call[1]-EP[Default] 2007/10/08 16:43:48.163 0:06.949 SIP Handler:981e608 Call OpenSourceMediaStreams for session 1 adjusted media to G.711-uLaw-64k 2007/10/08 16:43:48.163 0:06.949 SIP Handler:981e608 Call OpenSourceMediaStreams for session 2 with media G.711-uLaw-64k 2007/10/08 16:43:48.164 0:06.950 Media Patch:97d9a38 Patch Thread started for Patch OpalAudioMediaStream-Source-PCM-16 -> OpalRTPMediaStream-Sink-G.711-uLaw-64k 2007/10/08 16:43:48.164 0:06.950 SIP Handler:981e608 Media Starting thread Media Patch:97d9a38 2007/10/08 16:43:48.164 0:06.950 Media Patch:b50144b0 Patch Thread started for Patch OpalRTPMediaStream-Source-G.711-uLaw-64k -> OpalAudioMediaStream-Sink-PCM-16 2007/10/08 16:43:48.165 0:06.951 Media Patch:b50144b0 RTP Jitter buffer created: size=101 delay=160-4000/160 (20ms) obj=0x9869948 2007/10/08 16:43:48.166 0:06.952 RTP Jitter:9869948 RTP Jitter RTP receive thread started: 0x9869948 2007/10/08 16:43:48.166 0:06.952 SIP Handler:981e608 Media Starting thread Media Patch:b50144b0 2007/10/08 16:43:48.166 0:06.952 SIP Handler:981e608 OpalCon Media stream threads started. 2007/10/08 16:43:48.166 0:06.952 SIP Handler:981e608 OpalCon Media stream threads started. 2007/10/08 16:43:48.166 0:06.952 SIP Handler:981e608 OpalCon SetPhase from AlertingPhase to EstablishedPhase 2007/10/08 16:43:48.166 0:06.952 SIP Handler:981e608 GMSIPEndpoint SIP connection established 2007/10/08 16:43:48.172 0:06.958 SIP Handler:981e608 RTP Found existing session 1 2007/10/08 16:43:48.172 0:06.958 SIP Handler:981e608 GMManager Will establish the connection 2007/10/08 16:43:48.172 0:06.958 SIP Handler:981e608 OpalMan OnEstablished Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:48.172 0:06.958 SIP Handler:981e608 Call OnEstablished Call[1]-EP[2a797e34-fd73-dc11-864a-0019b97d3b5d at Pratiksha] 2007/10/08 16:43:48.173 0:06.959 SIP Handler:981e608 SIP Awaiting next PDU. 2007/10/08 16:43:48.200 0:06.986 Media Patch:97d9a38 RTP First sent data: ver=2 pt=PCMU psz=160 m=1 x=0 seq=55865 ts=0 src=621051503 ccnt=0 2007/10/08 16:43:49.089 0:07.875 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 2 2007/10/08 16:43:49.090 0:07.876 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bK74c17c35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=c4b77c35-fd73-dc11-864a-0019b97d3b5d Call-ID: 60c27b35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:49.090 0:07.876 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 2 2007/10/08 16:43:49.090 0:07.876 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKee8c7d35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=cc817d35-fd73-dc11-864a-0019b97d3b5d Call-ID: 28267d35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:49.179 0:07.965 Housekeeper RTP Found existing session 1 2007/10/08 16:43:50.196 0:08.982 Housekeeper RTP Found existing session 1 2007/10/08 16:43:50.208 0:08.994 Media Patch:97d9a38 RTP Transmit statistics: packets=101 octets=16160 avgTime=20 maxTime=60 minTime=16 2007/10/08 16:43:51.101 0:09.887 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 3 2007/10/08 16:43:51.101 0:09.887 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 172.16.25.113:5063;branch=z9hG4bK74c17c35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=c4b77c35-fd73-dc11-864a-0019b97d3b5d Call-ID: 60c27b35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:51.102 0:09.888 Housekeeper SIP Transaction 2 SUBSCRIBE timeout, making retry 3 2007/10/08 16:43:51.102 0:09.888 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 SUBSCRIBE sip:pratiksha.powar at ekiga.net SIP/2.0 CSeq: 2 SUBSCRIBE Via: SIP/2.0/UDP 172.16.25.113:5064;branch=z9hG4bKee8c7d35-fd73-dc11-864a-0019b97d3b5d;rport User-Agent: Ekiga/2.0.11 From: ;tag=cc817d35-fd73-dc11-864a-0019b97d3b5d Call-ID: 28267d35-fd73-dc11-864a-0019b97d3b5d at Pratiksha To: Contact: Accept: application/simple-message-summary Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,NOTIFY,REFER,MESSAGE Expires: 3600 Event: message-summary Content-Length: 0 Max-Forwards: 70 2007/10/08 16:43:51.232 0:10.018 Housekeeper RTP Found existing session 1 2007/10/08 16:43:52.212 0:10.998 Housekeeper RTP Found existing session 1 2007/10/08 16:43:52.216 0:11.002 Media Patch:97d9a38 RTP Transmit statistics: packets=201 octets=32160 avgTime=20 maxTime=60 minTime=16 2007/10/08 16:43:53.212 0:11.998 Housekeeper RTP Found existing session 1 2007/10/08 16:43:53.567 0:12.353 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2007/10/08 16:43:53.568 0:12.354 Housekeeper SIP Set state Terminated_Timeout for transaction 2 SUBSCRIBE 2007/10/08 16:43:54.204 0:12.990 Media Patch:97d9a38 RTP Transmit statistics: packets=301 octets=48160 avgTime=19 maxTime=40 minTime=16 2007/10/08 16:43:54.221 0:13.007 Housekeeper RTP Found existing session 1 2007/10/08 16:43:55.231 0:14.017 Housekeeper RTP Found existing session 1 2007/10/08 16:43:56.216 0:15.002 Media Patch:97d9a38 RTP Transmit statistics: packets=401 octets=64160 avgTime=20 maxTime=69 minTime=16 2007/10/08 16:43:56.245 0:15.031 Housekeeper RTP Found existing session 1 2007/10/08 16:43:57.245 0:16.031 Housekeeper RTP Found existing session 1 Killed [root at Pratiksha ~]# -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From dsandras at seconix.com Mon Oct 8 12:44:10 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 08 Oct 2007 14:44:10 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191842255.12577.4.camel@localhost.localdomain> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191573096.3343.7.camel@localhost.localdomain> <1191589467.4308.32.camel@scorpion> <1191840767.12577.1.camel@localhost.localdomain> <1191841321.4925.45.camel@scorpion> <1191842255.12577.4.camel@localhost.localdomain> Message-ID: <1191847450.4925.49.camel@scorpion> Hi, Le lundi 08 octobre 2007 ? 16:47 +0530, Pratiksha Powar a ?crit : > Hi Damien, > > I restarted the process on the Voice App Server. > I could connect using Ekiga. But I still hear anything. > Here is the trace at d 4. > Everything seems to be correct on Ekiga's side. Are you sure your voice application server supports DTMFs as RFC2833 ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From eriksorenson at amtelecom.net Mon Oct 8 20:28:03 2007 From: eriksorenson at amtelecom.net (Erik Sorenson) Date: Mon, 8 Oct 2007 16:28:03 -0400 Subject: [Ekiga-list] Calling Cuba Message-ID: <200710081628.03820.eriksorenson@amtelecom.net> I have e-mailed Diamond on this, but their reply didn't solve my problem. I hope that someone on the list can. When I dial Cuba from Canada on my normal phone via LD, I dial: 011-537-123-4567 (for example). So I set Ekiga on Suse via Diamond (using their instruction with the account activation) to dial 00-537-123-4567. The result was connection to a French-speaking number, definitely not Spanish nor Cuba. I e-mailed Diamond and they said to drop the leading (two zeroes), which work fine for Spain BTW. That left 537-123-4567 as the dial string (plus the diamond appendage string). Didn't work either. Any suggestions as to the string needed? TIA. From dsandras at seconix.com Mon Oct 8 20:42:34 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 08 Oct 2007 22:42:34 +0200 Subject: [Ekiga-list] Calling Cuba In-Reply-To: <200710081628.03820.eriksorenson@amtelecom.net> References: <200710081628.03820.eriksorenson@amtelecom.net> Message-ID: <1191876154.4179.21.camel@scorpion> Le lundi 08 octobre 2007 ? 16:28 -0400, Erik Sorenson a ?crit : > I have e-mailed Diamond on this, but their reply didn't solve my problem. I > hope that someone on the list can. > > When I dial Cuba from Canada on my normal phone via LD, I dial: > 011-537-123-4567 (for example). > > So I set Ekiga on Suse via Diamond (using their instruction with the account > activation) to dial 00-537-123-4567. The result was connection to a > French-speaking number, definitely not Spanish nor Cuba. > > I e-mailed Diamond and they said to drop the leading (two zeroes), which work > fine for Spain BTW. That left 537-123-4567 as the dial string (plus the > diamond appendage string). Didn't work either. > > Any suggestions as to the string needed? TIA. Logically : coutrycodenumber at eugw.ast.diamondcard.us For Belgium : +32 (country code) AND 065 39 91 91 (number) will give -> 3265399191 at .... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From eriksorenson at amtelecom.net Mon Oct 8 21:18:48 2007 From: eriksorenson at amtelecom.net (Erik Sorenson) Date: Mon, 8 Oct 2007 17:18:48 -0400 Subject: [Ekiga-list] Importing Settings and Phone Numbers Message-ID: <200710081718.48289.eriksorenson@amtelecom.net> I have a working Ekiga install working on openSUSE 10.1. I' installing openSUSE 10.3 into a separate partition with a new install of Ekiga. Is there any way to import my prior settings (including subscription to ekiga.net (username, pw, phone numbers I dial, the diamond account info, etc) into the 10.3 install of Ekiga, perhaps even by copying one or more files across? If copying, where's the "config" files that stores this info? Or do I have to enter all the stuff again? TIA. From dsandras at seconix.com Mon Oct 8 21:31:32 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 08 Oct 2007 23:31:32 +0200 Subject: [Ekiga-list] Importing Settings and Phone Numbers In-Reply-To: <200710081718.48289.eriksorenson@amtelecom.net> References: <200710081718.48289.eriksorenson@amtelecom.net> Message-ID: <1191879092.25236.1.camel@scorpion> Le lundi 08 octobre 2007 ? 17:18 -0400, Erik Sorenson a ?crit : > I have a working Ekiga install working on openSUSE 10.1. I' installing > openSUSE 10.3 into a separate partition with a new install of Ekiga. > > Is there any way to import my prior settings (including subscription to > ekiga.net (username, pw, phone numbers I dial, the diamond account info, etc) > into the 10.3 install of Ekiga, perhaps even by copying one or more files > across? If copying, where's the "config" files that stores this info? > > Or do I have to enter all the stuff again? TIA. See if gconftool-2 can help you or not. All Ekiga settings are stored using GConf. gconftool-2 -R /apps/ekiga will get you all Ekiga settings. There is probably some way to reincorporate, but there is no automated tool. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From pratiksha.powar at onmobile.com Tue Oct 9 05:25:35 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Tue, 09 Oct 2007 10:55:35 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191847450.4925.49.camel@scorpion> References: <1191522695.4089.3.camel@scorpion> <1191560106.3388.1.camel@localhost.localdomain> <1191561472.3388.8.camel@localhost.localdomain> <1191570004.4308.9.camel@scorpion> <1191573096.3343.7.camel@localhost.localdomain> <1191589467.4308.32.camel@scorpion> <1191840767.12577.1.camel@localhost.localdomain> <1191841321.4925.45.camel@scorpion> <1191842255.12577.4.camel@localhost.localdomain> <1191847450.4925.49.camel@scorpion> Message-ID: <1191907535.3645.16.camel@localhost.localdomain> Hi Damien, Yes, our Voice Applications support DTMF RFC2833 quite well. But they expect the payload type to be 96 and not 101. I saw the following line in the trace: SIP Transport:98449a8 SDP Media attribute rtpmap found for unknown RTP type [pt=96] And later the SIP INVITE message included this "a=rtpmap:96 telephone-event/8000" instead of "a=rtpmap:101 telephone-event/8000" which it normally included. This is what I have been trying to achieve for so long. Now that I have achieved it, I'm not able to hear any sound once I call the Voice pp which I was able to with Ekiga 2.0.2 Thanks, Pratiksha On Mon, 2007-10-08 at 14:44 +0200, Damien Sandras wrote: > Hi, > > Le lundi 08 octobre 2007 ? 16:47 +0530, Pratiksha Powar a ?crit : > > Hi Damien, > > > > I restarted the process on the Voice App Server. > > I could connect using Ekiga. But I still hear anything. > > Here is the trace at d 4. > > > > Everything seems to be correct on Ekiga's side. > > Are you sure your voice application server supports DTMFs as RFC2833 ? -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From nogueira at emc.ufsc.br Tue Oct 9 11:39:54 2007 From: nogueira at emc.ufsc.br (Antonio Carlos Ribeiro Nogueira) Date: Tue, 09 Oct 2007 08:39:54 -0300 Subject: [Ekiga-list] How to disconect from the other end with console command. Message-ID: <470B688A.1050604@emc.ufsc.br> Hi, My Ekiga, despite to be 2.0.9 version, it is not disconnecting the other hand (at my home. I left it connected in automatic answer) when I disconnect myself here at my work at University. So I would like to know the command I should give in console mode to disconnect it (without to need to click on the plug icone in the graphical interface). I use the auto answer because my mother understand nothing of computer. She is 83 years old. And I would like to chat with her along the day. I beg your perdon for my poor english. Thanks in advance. Antonio Carlos From lurch at gmx.li Tue Oct 9 17:20:58 2007 From: lurch at gmx.li (Stefan Bruens) Date: Tue, 09 Oct 2007 19:20:58 +0200 Subject: [Ekiga-list] Importing Settings and Phone Numbers In-Reply-To: <1191879092.25236.1.camel@scorpion> References: <200710081718.48289.eriksorenson@amtelecom.net> <1191879092.25236.1.camel@scorpion> Message-ID: <200710091921.01576.lurch@gmx.li> Am Montag, 8. Oktober 2007 23:31:32 schrieb Damien Sandras: > gconftool-2 -R /apps/ekiga > will get you all Ekiga settings. There is probably some way to > reincorporate, but there is no automated tool. Try: gconftool-2 --dump /apps/ekiga > ekiga_settings.xml gconftool-2 --load ekiga_settings.xml Totally untested ... Bye, Lurchi -- Stefan Br?ns / Kastanienweg 6 - Zimmer 1206 / 52074 Aachen mailto:lurch at gmx.li http://www.kawo1.rwth-aachen.de/~lurchi/ phone: +49 241 169-4206 mobile: +49 160 3797725 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From lurch at gmx.li Tue Oct 9 17:24:39 2007 From: lurch at gmx.li (Stefan Bruens) Date: Tue, 09 Oct 2007 19:24:39 +0200 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1191907535.3645.16.camel@localhost.localdomain> References: <1191847450.4925.49.camel@scorpion> <1191907535.3645.16.camel@localhost.localdomain> Message-ID: <200710091924.39470.lurch@gmx.li> Am Dienstag, 9. Oktober 2007 07:25:35 schrieb Pratiksha Powar: > Hi Damien, > > Yes, our Voice Applications support DTMF RFC2833 quite well. > But they expect the payload type to be 96 and not 101. If the application expects DTMF to have a payload of 96, it is broken. DTMF uses dynamic payload types, so the application should use the rtpmap to get the payload type for DTMF Lurchi -- Stefan Br?ns / Kastanienweg 6 - Zimmer 1206 / 52074 Aachen mailto:lurch at gmx.li http://www.kawo1.rwth-aachen.de/~lurchi/ phone: +49 241 169-4206 mobile: +49 160 3797725 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From alex at schlossadler.net Wed Oct 10 13:32:10 2007 From: alex at schlossadler.net (alex) Date: Wed, 10 Oct 2007 23:32:10 +1000 Subject: [Ekiga-list] Calls die after a couple of minutes Message-ID: <470CD45A.9000109@schlossadler.net> Hi Guys, Not real sure what is going on with this issue I have, but I will attempt to describe it s best as I can. Me and another person both registered on ekiga.net. I am using Ekiga 2.0.9 Under OpenSolaris x86. The other person is using the current MS Windows (Under XP SP2) version (downloaded today). After talking for a couple of minutes, I hear a loud screeching sound, followed by a fast clicking noise and I can no longer hear them. When this happens the other party doesn't hear the screeching or clicking, it just appears I have gone 'silent' to them, and the only way for them to be able to hear me, and for me to be to be able to hear them again, is to hang up and start again. This seems to happen no matter which codec I am using. The other party using the windows version has advised me that when this happens, the program occasionally crashes "Program has encountered a problem and needs to close". I have had no crashes on my end. This issue has also occurred and the other party on Windows has had NO crash and I have been able to call them straight back. I don't know if the issue is on my side or theirs, I suspect theirs but I am guessing. I am unable to test with Ekiga 2.0.11 because pwlib refuses to build under Solaris (its author has not tested adequately or has only tested with an old version of solaris), ie: it does some really stupid things, like try to use the -xO3 instead of -O3 flag with GCC, when that flag only works with Sun's Compiler (which I am unable to get pwlib to build with either), I got around this by editing one of the makefiles, only to find that "gmake install" stuff's up too, and cant "stat" this file or "stat" that directory and some other nonsense. So I have hit a brick wall there. How do I contact the author of pwlib? Im, even willing to give them ssh access to a Solaris 11 machine for testing if need be. A bit of googling indicates others have reported similar issues, but I could never really find any answer on resolving it. I guess the first step is to find out who's side is having the issue, me or them? Any suggestions appreciated. Kind Regards Alex From dsandras at seconix.com Wed Oct 10 20:09:57 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 10 Oct 2007 22:09:57 +0200 Subject: [Ekiga-list] Calls die after a couple of minutes In-Reply-To: <470CD45A.9000109@schlossadler.net> References: <470CD45A.9000109@schlossadler.net> Message-ID: <1192046997.31851.5.camel@scorpion> Hello, Le mercredi 10 octobre 2007 ? 23:32 +1000, alex a ?crit : > Hi Guys, > > Not real sure what is going on with this issue I have, but I will > attempt to describe it s best as I can. Me and another person both > registered on ekiga.net. I am using Ekiga 2.0.9 Under OpenSolaris x86. > The other person is using the current MS Windows (Under XP SP2) version > (downloaded today). After talking for a couple of minutes, I hear a loud > screeching sound, followed by a fast clicking noise and I can no longer > hear them. When this happens the other party doesn't hear the screeching > or clicking, it just appears I have gone 'silent' to them, and the only > way for them to be able to hear me, and for me to be to be able to hear > them again, is to hang up and start again. This seems to happen no > matter which codec I am using. The other party using the windows version > has advised me that when this happens, the program occasionally crashes > "Program has encountered a problem and needs to close". I have had no > crashes on my end. This issue has also occurred and the other party on > Windows has had NO crash and I have been able to call them straight back. > Try disabling Echo cancellation on both sides. Does it work better ? It is a typical sign of the echo canceller going crazy. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Oct 10 20:11:09 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 10 Oct 2007 22:11:09 +0200 Subject: [Ekiga-list] How to disconect from the other end with console command. In-Reply-To: <470B688A.1050604@emc.ufsc.br> References: <470B688A.1050604@emc.ufsc.br> Message-ID: <1192047069.31851.7.camel@scorpion> Le mardi 09 octobre 2007 ? 08:39 -0300, Antonio Carlos Ribeiro Nogueira a ?crit : > Hi, My Ekiga, despite to be 2.0.9 version, it is not disconnecting the > other hand (at my home. I left it connected in automatic answer) when I > disconnect myself here at my work at University. So I would like to know > the command I should give in console mode to disconnect it (without to > need to click on the plug icone in the graphical interface). I use the > auto answer because my mother understand nothing of computer. She is 83 > years old. And I would like to chat with her along the day. I beg your > perdon for my poor english. Thanks in advance. There is a setting in Ekiga : "Disconnect the call if nothing is received during x seconds". Just enable that setting and the phone will disconnect if there is inactivity. That being said, it is weird that it does not react to your disconnection. Perhaps a network issue... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From alex at schlossadler.net Wed Oct 10 21:46:42 2007 From: alex at schlossadler.net (alex) Date: Thu, 11 Oct 2007 07:46:42 +1000 Subject: [Ekiga-list] Calls die after a couple of minutes In-Reply-To: <1192046997.31851.5.camel@scorpion> References: <470CD45A.9000109@schlossadler.net> <1192046997.31851.5.camel@scorpion> Message-ID: <470D4842.4040406@schlossadler.net> Damien Sandras wrote: > Hello, > > Le mercredi 10 octobre 2007 ? 23:32 +1000, alex a ?crit : > >> Hi Guys, >> >> Not real sure what is going on with this issue I have, but I will >> attempt to describe it s best as I can. Me and another person both >> registered on ekiga.net. I am using Ekiga 2.0.9 Under OpenSolaris x86. >> The other person is using the current MS Windows (Under XP SP2) version >> (downloaded today). After talking for a couple of minutes, I hear a loud >> screeching sound, followed by a fast clicking noise and I can no longer >> hear them. When this happens the other party doesn't hear the screeching >> or clicking, it just appears I have gone 'silent' to them, and the only >> way for them to be able to hear me, and for me to be to be able to hear >> them again, is to hang up and start again. This seems to happen no >> matter which codec I am using. The other party using the windows version >> has advised me that when this happens, the program occasionally crashes >> "Program has encountered a problem and needs to close". I have had no >> crashes on my end. This issue has also occurred and the other party on >> Windows has had NO crash and I have been able to call them straight back. >> >> > > Try disabling Echo cancellation on both sides. > > Does it work better ? > > It is a typical sign of the echo canceller going crazy. > Hi Damien, Thank you for your reply :) The echo canceller/silence detection options have never been enabled on either end. Would you have any other suggestions? Kind Regards, Alex From dsandras at seconix.com Wed Oct 10 21:59:03 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 10 Oct 2007 23:59:03 +0200 Subject: [Ekiga-list] Calls die after a couple of minutes In-Reply-To: <470D4842.4040406@schlossadler.net> References: <470CD45A.9000109@schlossadler.net> <1192046997.31851.5.camel@scorpion> <470D4842.4040406@schlossadler.net> Message-ID: <1192053543.31851.47.camel@scorpion> Le jeudi 11 octobre 2007 ? 07:46 +1000, alex a ?crit : > Damien Sandras wrote: > > Hello, > > > > Le mercredi 10 octobre 2007 ? 23:32 +1000, alex a ?crit : > > > >> Hi Guys, > >> > >> Not real sure what is going on with this issue I have, but I will > >> attempt to describe it s best as I can. Me and another person both > >> registered on ekiga.net. I am using Ekiga 2.0.9 Under OpenSolaris x86. > >> The other person is using the current MS Windows (Under XP SP2) version > >> (downloaded today). After talking for a couple of minutes, I hear a loud > >> screeching sound, followed by a fast clicking noise and I can no longer > >> hear them. When this happens the other party doesn't hear the screeching > >> or clicking, it just appears I have gone 'silent' to them, and the only > >> way for them to be able to hear me, and for me to be to be able to hear > >> them again, is to hang up and start again. This seems to happen no > >> matter which codec I am using. The other party using the windows version > >> has advised me that when this happens, the program occasionally crashes > >> "Program has encountered a problem and needs to close". I have had no > >> crashes on my end. This issue has also occurred and the other party on > >> Windows has had NO crash and I have been able to call them straight back. > >> > >> > > > > Try disabling Echo cancellation on both sides. > > > > Does it work better ? > > > > It is a typical sign of the echo canceller going crazy. > > > Hi Damien, > > Thank you for your reply :) The echo canceller/silence detection options > have never been enabled on either end. Would you have any other suggestions? Use another codec... That is the only option left. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From threerocks at kos.net Thu Oct 11 00:25:54 2007 From: threerocks at kos.net (Ron H) Date: Thu, 11 Oct 2007 00:25:54 +0000 Subject: [Ekiga-list] Registration Failed Message-ID: <1192062355.22692.23.camel@localhost> Hi, I am looking for help....so far no luck. I want to use Ekiga. I have set it up and have gone through the configuration druid. I cannot make a call. I cannot make a test call. On the dialpad display it shows 'Registered Accounts 0'.....So I go to 'Edit' / 'Accounts' ...take a look and all my registration attempts have failed. ???? 1. ekiga.net SIP Service - registration failed 2. Ekiga PC-To-Phone - registration failed 3. ron2100 - registration failed Any Idea what I'm doing wrong???? please help Thanks, Ron From threerocks at kos.net Thu Oct 11 00:50:41 2007 From: threerocks at kos.net (Ron H) Date: Thu, 11 Oct 2007 00:50:41 +0000 Subject: [Ekiga-list] test Message-ID: <1192063841.15970.0.camel@localhost> test From alex at schlossadler.net Thu Oct 11 01:39:54 2007 From: alex at schlossadler.net (alex) Date: Thu, 11 Oct 2007 11:39:54 +1000 Subject: [Ekiga-list] Registration Failed In-Reply-To: <1192062355.22692.23.camel@localhost> References: <1192062355.22692.23.camel@localhost> Message-ID: <470D7EEA.2000106@schlossadler.net> Ron H wrote: > Hi, > > I am looking for help....so far no luck. > > I want to use Ekiga. I have set it up and have gone through the > configuration druid. I cannot make a call. I cannot make a test call. On > the dialpad display it shows 'Registered Accounts 0'.....So I go to > 'Edit' / 'Accounts' ...take a look and all my registration attempts have > failed. ???? > 1. ekiga.net SIP Service - registration failed > 2. Ekiga PC-To-Phone - registration failed > 3. ron2100 - registration failed > > > Any Idea what I'm doing wrong???? > > please help > > Thanks, > > Ron > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > Have you forwarded the correct UDP ports on your router/gateway? From mshahwan2001 at yahoo.com Thu Oct 11 02:09:04 2007 From: mshahwan2001 at yahoo.com (Michael) Date: Wed, 10 Oct 2007 19:09:04 -0700 (PDT) Subject: [Ekiga-list] DTMF and Asterisk? Message-ID: <352298.40674.qm@web52405.mail.re2.yahoo.com> Damien: Just received additional information on this problem. If any user uses Ekiga and they press a digit the digit will sound as if it is continually pressed (never left go of it). For example if I called you and accidentally pressed ZERO you would hear the number ZERO beep to infinity. This must be the problem with DTMF tones. Instead of being a short beep it is as if the number is stuck and continually gives a prolonged beeeeeee....(never ending) ....p. Any ideas? ----- Original Message ---- From: Damien Sandras To: Ekiga mailing list Sent: Saturday, October 6, 2007 8:23:53 AM Subject: Re: [Ekiga-list] DTMF and Asterisk? I have the feeling Asterisk 1.4.11 is buggy with DTMFs. The only way to debug this is to sniff the traffic with wireshark and check which one is wrong : ekiga or asterisk. Le vendredi 05 octobre 2007 ? 21:42 -0700, Michael a ?crit : > We use Asterisk 1-4.11 and noticed that sometimes the DTMF tones are > delayed. Once they pass through the other party cannot hear. We have > SIP peers shown to see the ms per phone, but they are all less then > 200 when this happens. How can we trouble shoot this issue? > > ----- Original Message ---- > From: Alan Lord > To: Ekiga mailing list > Sent: Friday, October 5, 2007 11:28:31 AM > Subject: Re: [Ekiga-list] DTMF and Asterisk? > > Damien Sandras wrote: > > Le vendredi 05 octobre 2007 ? 16:50 +0100, Alan Lord a ?crit : > >> Alan Lord wrote: > >>> Hi all, > >>> > >>> I have started playing around with Asterisk recently. I got very > >>> confused when I couldn't get it to respond to DTMF tones from my > Ekiga > >>> client. I tried loads of configuration settings on Asterisk and > upgraded > >>> to their latest version 1-4.12. Same problem. > >> > >> > >> Sorry about replying to my own post but I just installed the Ekiga > >> snapshot (20071001) and tried both RFC2833 and INFO but I still > have the > >> same problem. Both the Twinkle and OpenWengo phones work fine. > > > > There must be a problem on the Asterisk side in that case... > > > > Don't you have debug on Asterisk's side ? > > debug on what? > > I can see the DTMF packets being sent from Ekiga to Asterisk but it > doesn't seem to recognise them. > > After removing the "dtmfmode=xxxx" comment entirely, the asterisk > server > now reads the dtmf tones! Setting it to RFC2833 or info didn't work. > > However Ekiga still misses playing the first message sent from the > asterisk server. The other two soft phones do not... Any ideas? > > Cheers > > Alan > > > -- > The way out is open! > http://www.theopensourcerer.com > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > ______________________________________________________________________ > Take the Internet to Go: Yahoo!Go puts the Internet in your pocket: > mail, news, photos & more. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ____________________________________________________________________________________ Shape Yahoo! in your own image. Join our Network Research Panel today! http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7 -------------- next part -------------- An HTML attachment was scrubbed... URL: From mshahwan2001 at yahoo.com Thu Oct 11 02:12:06 2007 From: mshahwan2001 at yahoo.com (Michael) Date: Wed, 10 Oct 2007 19:12:06 -0700 (PDT) Subject: [Ekiga-list] call termination is unnoticed Message-ID: <373941.23888.qm@web52408.mail.re2.yahoo.com> Does anyone notice that Ekiga does not understand a call has terminated. For example if Ekiga user calls or receives a call and the other party hangs up Ekiga does not disconnect. It simply will keep the line active and not allow new calls to come in. Any work around besides remembering to hang up after each call is terminated? ____________________________________________________________________________________ Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV. http://tv.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From alex at schlossadler.net Thu Oct 11 03:29:22 2007 From: alex at schlossadler.net (alex) Date: Thu, 11 Oct 2007 13:29:22 +1000 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? Message-ID: <470D9892.8020008@schlossadler.net> This is probably a very common question/issue, but as far as I know, I have done everything to help the configure script find the library, I have this output: Invoked: ./configure --prefix=/usr/local --with-pwlib-dir=/usr/local --with-opal-dir=/usr/local Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for pkg-config... (cached) /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for EKIGA... yes checking for EDS... yes checking for scrollkeeper-config... /usr/bin/scrollkeeper-config checking whether OS type is supported... yes checking for PWLib includes in /usr/local/include/... checking for /usr/local/include/ptlib/pprocess.h... yes checking for read in -lpt... no configure: error: You need the PWLib library to compile Ekiga bash-3.00$ ls -l /usr/local/lib |grep libpt lrwxrwxrwx 1 root root 22 Oct 11 12:33 libpt.so -> libpt_solaris_x86_r.so lrwxrwxrwx 1 root root 30 Oct 11 12:33 libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 lrwxrwxrwx 1 root root 30 Oct 11 12:33 libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 lrwxrwxrwx 1 root root 30 Oct 11 12:33 libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 -r--r--r-- 1 root root 5507268 Oct 11 12:33 libpt_solaris_x86_r.so.1.10.10 Operating system is Solaris (OpenSolaris - Solaris 11). Out of desperation, I tried this (not normally needed as other software doesn't have trouble finding things): bash-3.00$ export LDFLAGS="-L/usr/local/lib:/usr/lib -R/usr/local/lib:/usr/lib" and tried again.. same error. Opal didnt have any problems finding my libraries in /usr/local, why is ekiga having the issue? Any ideas what the problem is? From alex at schlossadler.net Thu Oct 11 04:11:35 2007 From: alex at schlossadler.net (alex) Date: Thu, 11 Oct 2007 14:11:35 +1000 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <470D9892.8020008@schlossadler.net> References: <470D9892.8020008@schlossadler.net> Message-ID: <470DA277.4030809@schlossadler.net> alex wrote: > This is probably a very common question/issue, but as far as I know, I > have done everything to help the configure script find the library, I > have this output: > > Invoked: ./configure --prefix=/usr/local --with-pwlib-dir=/usr/local > --with-opal-dir=/usr/local > > Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema > installation > Using $(sysconfdir)/gconf/schemas as install directory for schema files > checking for pkg-config... (cached) /usr/bin/pkg-config > checking pkg-config is at least version 0.9.0... yes > checking for EKIGA... yes > checking for EDS... yes > checking for scrollkeeper-config... /usr/bin/scrollkeeper-config > checking whether OS type is supported... yes > checking for PWLib includes in /usr/local/include/... > checking for /usr/local/include/ptlib/pprocess.h... yes > checking for read in -lpt... no > configure: error: You need the PWLib library to compile Ekiga > > bash-3.00$ ls -l /usr/local/lib |grep libpt > lrwxrwxrwx 1 root root 22 Oct 11 12:33 libpt.so -> > libpt_solaris_x86_r.so > lrwxrwxrwx 1 root root 30 Oct 11 12:33 > libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 > lrwxrwxrwx 1 root root 30 Oct 11 12:33 > libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 > lrwxrwxrwx 1 root root 30 Oct 11 12:33 > libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 > -r--r--r-- 1 root root 5507268 Oct 11 12:33 > libpt_solaris_x86_r.so.1.10.10 > > Operating system is Solaris (OpenSolaris - Solaris 11). > > Out of desperation, I tried this (not normally needed as other software > doesn't have trouble finding things): > > bash-3.00$ export LDFLAGS="-L/usr/local/lib:/usr/lib > -R/usr/local/lib:/usr/lib" > > and tried again.. same error. Opal didnt have any problems finding my > libraries in /usr/local, why is ekiga having the issue? > > Any ideas what the problem is? > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > Some more info on this, I looked at config.log and found this: configure:22375: checking for read in -lpt configure:22410: g++ -o conftest -O4 -L/usr/local/lib:/usr/lib -R/usr/local/lib:/usr/lib -L/usr/local/lib/ conftest.cpp -lpt >&5 Undefined first referenced symbol in file PVideoDevice::SetColourFormatConverter(PString const&) /usr/local/lib//libpt.so PVideoDevice::GetVideoFormat() const /usr/local/lib//libpt.so PVideoDevice::GetHue() /usr/local/lib//libpt.so PVideoDevice::SetHue(unsigned int) /usr/local/lib//libpt.so typeinfo for PVideoOutputDevice /usr/local/lib//libpt.so vtable for PVideoOutputDevice /usr/local/lib//libpt.so PVideoOutputDevice::Start() /usr/local/lib//libpt.so PVideoDevice::SetVideoChannelFormat(int, PVideoDevice::VideoFormat)/usr/local/lib//libpt.so PVideoDevice::~PVideoDevice() /usr/local/lib//libpt.so PVideoOutputDevice::PVideoOutputDevice()/usr/local/lib//libpt.so PVideoDevice::SetWhiteness(unsigned int)/usr/local/lib//libpt.so PVideoDevice::GetWhiteness() /usr/local/lib//libpt.so PVideoDevice::SetFrameRate(unsigned int)/usr/local/lib//libpt.so PVideoOutputDevice::Stop() /usr/local/lib//libpt.so PVideoDevice::GetMaxFrameBytesConverted(int) const/usr/local/lib//libpt.so PVideoDevice::SetChannel(int) /usr/local/lib//libpt.so PVideoDevice::OpenFull(PVideoDevice::OpenArgs const&, int)/usr/local/lib//libpt.so PVideoDevice::SetFrameSize(unsigned int, unsigned int)/usr/local/lib//libpt.so PVideoDevice::GetFrameSizeLimits(unsigned int&, unsigned int&, unsigned int&, unsigned int&)/usr/local/lib//libpt.so PVideoDevice::SetColour(unsigned int)/usr/local/lib//libpt.so PVideoDevice::GetContrast() /usr/local/lib//libpt.so PVideoDevice::GetColour() /usr/local/lib//libpt.so What is this all about? From dsandras at seconix.com Thu Oct 11 07:56:55 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Oct 2007 09:56:55 +0200 Subject: [Ekiga-list] DTMF and Asterisk? In-Reply-To: <352298.40674.qm@web52405.mail.re2.yahoo.com> References: <352298.40674.qm@web52405.mail.re2.yahoo.com> Message-ID: <1192089415.4213.16.camel@scorpion> Le mercredi 10 octobre 2007 ? 19:09 -0700, Michael a ?crit : > Damien: > > Just received additional information on this problem. If any user uses > Ekiga and they press a digit the digit will sound as if it is > continually pressed (never left go of it). For example if I called you > and accidentally pressed ZERO you would hear the number ZERO beep to > infinity. This must be the problem with DTMF tones. Instead of being a > short beep it is as if the number is stuck and continually gives a > prolonged beeeeeee....(never ending) ....p. > > Any ideas? They must have a problem with their RFC2833 implementation. Try using SIP Info instead. I do not think the bug is in Ekiga or OPAL... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Thu Oct 11 07:57:30 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Oct 2007 09:57:30 +0200 Subject: [Ekiga-list] call termination is unnoticed In-Reply-To: <373941.23888.qm@web52408.mail.re2.yahoo.com> References: <373941.23888.qm@web52408.mail.re2.yahoo.com> Message-ID: <1192089450.4213.18.camel@scorpion> Le mercredi 10 octobre 2007 ? 19:12 -0700, Michael a ?crit : > Does anyone notice that Ekiga does not understand a call has > terminated. > > For example if Ekiga user calls or receives a call and the other party > hangs up Ekiga does not disconnect. It simply will keep the line > active and not allow new calls to come in. > > Any work around besides remembering to hang up after each call is > terminated? > > > > ______________________________________________________________________ Can you post a -d 4 output of the side that receives the disconnection request and does not hangup ? Thanks, -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Thu Oct 11 07:58:05 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Oct 2007 09:58:05 +0200 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <470DA277.4030809@schlossadler.net> References: <470D9892.8020008@schlossadler.net> <470DA277.4030809@schlossadler.net> Message-ID: <1192089485.4213.20.camel@scorpion> Le jeudi 11 octobre 2007 ? 14:11 +1000, alex a ?crit : > alex wrote: > > This is probably a very common question/issue, but as far as I know, I > > have done everything to help the configure script find the library, I > > have this output: > > > > Invoked: ./configure --prefix=/usr/local --with-pwlib-dir=/usr/local > > --with-opal-dir=/usr/local > > > > Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema > > installation > > Using $(sysconfdir)/gconf/schemas as install directory for schema files > > checking for pkg-config... (cached) /usr/bin/pkg-config > > checking pkg-config is at least version 0.9.0... yes > > checking for EKIGA... yes > > checking for EDS... yes > > checking for scrollkeeper-config... /usr/bin/scrollkeeper-config > > checking whether OS type is supported... yes > > checking for PWLib includes in /usr/local/include/... > > checking for /usr/local/include/ptlib/pprocess.h... yes > > checking for read in -lpt... no > > configure: error: You need the PWLib library to compile Ekiga > > > > bash-3.00$ ls -l /usr/local/lib |grep libpt > > lrwxrwxrwx 1 root root 22 Oct 11 12:33 libpt.so -> > > libpt_solaris_x86_r.so > > lrwxrwxrwx 1 root root 30 Oct 11 12:33 > > libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 > > lrwxrwxrwx 1 root root 30 Oct 11 12:33 > > libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 > > lrwxrwxrwx 1 root root 30 Oct 11 12:33 > > libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 > > -r--r--r-- 1 root root 5507268 Oct 11 12:33 > > libpt_solaris_x86_r.so.1.10.10 > > > > Operating system is Solaris (OpenSolaris - Solaris 11). > > > > Out of desperation, I tried this (not normally needed as other software > > doesn't have trouble finding things): > > > > bash-3.00$ export LDFLAGS="-L/usr/local/lib:/usr/lib > > -R/usr/local/lib:/usr/lib" > > > > and tried again.. same error. Opal didnt have any problems finding my > > libraries in /usr/local, why is ekiga having the issue? > > > > Any ideas what the problem is? > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > Some more info on this, I looked at config.log and found this: > > configure:22375: checking for read in -lpt > configure:22410: g++ -o conftest -O4 -L/usr/local/lib:/usr/lib > -R/usr/local/lib:/usr/lib -L/usr/local/lib/ conftest.cpp -lpt > >&5 > Undefined first referenced > symbol in file > PVideoDevice::SetColourFormatConverter(PString const&) > /usr/local/lib//libpt.so > PVideoDevice::GetVideoFormat() const /usr/local/lib//libpt.so > PVideoDevice::GetHue() /usr/local/lib//libpt.so > PVideoDevice::SetHue(unsigned int) /usr/local/lib//libpt.so > typeinfo for PVideoOutputDevice /usr/local/lib//libpt.so > vtable for PVideoOutputDevice /usr/local/lib//libpt.so > PVideoOutputDevice::Start() /usr/local/lib//libpt.so > PVideoDevice::SetVideoChannelFormat(int, > PVideoDevice::VideoFormat)/usr/local/lib//libpt.so > PVideoDevice::~PVideoDevice() /usr/local/lib//libpt.so > PVideoOutputDevice::PVideoOutputDevice()/usr/local/lib//libpt.so > PVideoDevice::SetWhiteness(unsigned int)/usr/local/lib//libpt.so > PVideoDevice::GetWhiteness() /usr/local/lib//libpt.so > PVideoDevice::SetFrameRate(unsigned int)/usr/local/lib//libpt.so > PVideoOutputDevice::Stop() /usr/local/lib//libpt.so > PVideoDevice::GetMaxFrameBytesConverted(int) const/usr/local/lib//libpt.so > PVideoDevice::SetChannel(int) /usr/local/lib//libpt.so > PVideoDevice::OpenFull(PVideoDevice::OpenArgs const&, > int)/usr/local/lib//libpt.so > PVideoDevice::SetFrameSize(unsigned int, unsigned > int)/usr/local/lib//libpt.so > PVideoDevice::GetFrameSizeLimits(unsigned int&, unsigned int&, unsigned > int&, unsigned int&)/usr/local/lib//libpt.so > PVideoDevice::SetColour(unsigned int)/usr/local/lib//libpt.so > PVideoDevice::GetContrast() /usr/local/lib//libpt.so > PVideoDevice::GetColour() /usr/local/lib//libpt.so > > What is this all about? You probably have conflicting libraries / headers on your system. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From alex at schlossadler.net Thu Oct 11 07:59:52 2007 From: alex at schlossadler.net (alex) Date: Thu, 11 Oct 2007 17:59:52 +1000 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <1192089485.4213.20.camel@scorpion> References: <470D9892.8020008@schlossadler.net> <470DA277.4030809@schlossadler.net> <1192089485.4213.20.camel@scorpion> Message-ID: <470DD7F8.9000501@schlossadler.net> Damien Sandras wrote: > Le jeudi 11 octobre 2007 ? 14:11 +1000, alex a ?crit : > >> alex wrote: >> >>> This is probably a very common question/issue, but as far as I know, I >>> have done everything to help the configure script find the library, I >>> have this output: >>> >>> Invoked: ./configure --prefix=/usr/local --with-pwlib-dir=/usr/local >>> --with-opal-dir=/usr/local >>> >>> Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema >>> installation >>> Using $(sysconfdir)/gconf/schemas as install directory for schema files >>> checking for pkg-config... (cached) /usr/bin/pkg-config >>> checking pkg-config is at least version 0.9.0... yes >>> checking for EKIGA... yes >>> checking for EDS... yes >>> checking for scrollkeeper-config... /usr/bin/scrollkeeper-config >>> checking whether OS type is supported... yes >>> checking for PWLib includes in /usr/local/include/... >>> checking for /usr/local/include/ptlib/pprocess.h... yes >>> checking for read in -lpt... no >>> configure: error: You need the PWLib library to compile Ekiga >>> >>> bash-3.00$ ls -l /usr/local/lib |grep libpt >>> lrwxrwxrwx 1 root root 22 Oct 11 12:33 libpt.so -> >>> libpt_solaris_x86_r.so >>> lrwxrwxrwx 1 root root 30 Oct 11 12:33 >>> libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 >>> lrwxrwxrwx 1 root root 30 Oct 11 12:33 >>> libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 >>> lrwxrwxrwx 1 root root 30 Oct 11 12:33 >>> libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 >>> -r--r--r-- 1 root root 5507268 Oct 11 12:33 >>> libpt_solaris_x86_r.so.1.10.10 >>> >>> Operating system is Solaris (OpenSolaris - Solaris 11). >>> >>> Out of desperation, I tried this (not normally needed as other software >>> doesn't have trouble finding things): >>> >>> bash-3.00$ export LDFLAGS="-L/usr/local/lib:/usr/lib >>> -R/usr/local/lib:/usr/lib" >>> >>> and tried again.. same error. Opal didnt have any problems finding my >>> libraries in /usr/local, why is ekiga having the issue? >>> >>> Any ideas what the problem is? >>> >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >>> >>> >> Some more info on this, I looked at config.log and found this: >> >> configure:22375: checking for read in -lpt >> configure:22410: g++ -o conftest -O4 -L/usr/local/lib:/usr/lib >> -R/usr/local/lib:/usr/lib -L/usr/local/lib/ conftest.cpp -lpt >> >&5 >> Undefined first referenced >> symbol in file >> PVideoDevice::SetColourFormatConverter(PString const&) >> /usr/local/lib//libpt.so >> PVideoDevice::GetVideoFormat() const /usr/local/lib//libpt.so >> PVideoDevice::GetHue() /usr/local/lib//libpt.so >> PVideoDevice::SetHue(unsigned int) /usr/local/lib//libpt.so >> typeinfo for PVideoOutputDevice /usr/local/lib//libpt.so >> vtable for PVideoOutputDevice /usr/local/lib//libpt.so >> PVideoOutputDevice::Start() /usr/local/lib//libpt.so >> PVideoDevice::SetVideoChannelFormat(int, >> PVideoDevice::VideoFormat)/usr/local/lib//libpt.so >> PVideoDevice::~PVideoDevice() /usr/local/lib//libpt.so >> PVideoOutputDevice::PVideoOutputDevice()/usr/local/lib//libpt.so >> PVideoDevice::SetWhiteness(unsigned int)/usr/local/lib//libpt.so >> PVideoDevice::GetWhiteness() /usr/local/lib//libpt.so >> PVideoDevice::SetFrameRate(unsigned int)/usr/local/lib//libpt.so >> PVideoOutputDevice::Stop() /usr/local/lib//libpt.so >> PVideoDevice::GetMaxFrameBytesConverted(int) const/usr/local/lib//libpt.so >> PVideoDevice::SetChannel(int) /usr/local/lib//libpt.so >> PVideoDevice::OpenFull(PVideoDevice::OpenArgs const&, >> int)/usr/local/lib//libpt.so >> PVideoDevice::SetFrameSize(unsigned int, unsigned >> int)/usr/local/lib//libpt.so >> PVideoDevice::GetFrameSizeLimits(unsigned int&, unsigned int&, unsigned >> int&, unsigned int&)/usr/local/lib//libpt.so >> PVideoDevice::SetColour(unsigned int)/usr/local/lib//libpt.so >> PVideoDevice::GetContrast() /usr/local/lib//libpt.so >> PVideoDevice::GetColour() /usr/local/lib//libpt.so >> >> What is this all about? >> > > You probably have conflicting libraries / headers on your system. > Any ideas where to start looking? From death.jockey85 at gmail.com Thu Oct 11 08:49:37 2007 From: death.jockey85 at gmail.com (=?ISO-8859-1?Q?Victor_Nu=F1ez?=) Date: Thu, 11 Oct 2007 10:49:37 +0200 Subject: [Ekiga-list] Hi from Spain! Message-ID: Good morning from Spain, I need to make a small modification on Ekiga code and I'm lost. I'm engineer of telecommunications and i need to make some tests for my project (a kind of bluetooth protocol), I'm not very good programming by that reason I write to you to see if some knows it or has made something similar. It would need to indicate a variable to him through GUI (Linux) a whole number between 0 - 9 this I number would modify FPS(Frame Rate), % of bandwidth selected by of user, and information of colour YES/NO, only from video information, i don't need to make any modification in the AUDIO. I'm searching in Ekiga code and I find the dir \src\devices\videoinput.cpp where is defined the colour, brightness and more, but i can't find where is the variable of the bandwidth selected by the user. Thanks for all and sorry for my English! From nogueira at emc.ufsc.br Thu Oct 11 11:54:42 2007 From: nogueira at emc.ufsc.br (Antonio Carlos Ribeiro Nogueira) Date: Thu, 11 Oct 2007 08:54:42 -0300 Subject: [Ekiga-list] call termination is unnoticed In-Reply-To: <373941.23888.qm@web52408.mail.re2.yahoo.com> References: <373941.23888.qm@web52408.mail.re2.yahoo.com> Message-ID: <470E0F02.4050306@emc.ufsc.br> Yes, I am having this problem also. Antonio Carlos Michael escreveu: > Does anyone notice that Ekiga does not understand a call has terminated. > > For example if Ekiga user calls or receives a call and the other party > hangs up Ekiga does not disconnect. It simply will keep the line > active and not allow new calls to come in. > > Any work around besides remembering to hang up after each call is > terminated? > > ------------------------------------------------------------------------ > Tonight's top picks. What will you watch tonight? Preview the hottest > shows > > on Yahoo! TV. > ------------------------------------------------------------------------ > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From nogueira at emc.ufsc.br Thu Oct 11 12:05:51 2007 From: nogueira at emc.ufsc.br (Antonio Carlos Ribeiro Nogueira) Date: Thu, 11 Oct 2007 09:05:51 -0300 Subject: [Ekiga-list] How to disconect from the other end with console command. In-Reply-To: <1192047069.31851.7.camel@scorpion> References: <470B688A.1050604@emc.ufsc.br> <1192047069.31851.7.camel@scorpion> Message-ID: <470E119F.9080603@emc.ufsc.br> Well, it is a problem like another user reported us in the list... It doesn't hung up if the other side disconnect. So I would like to know how is the command I should send throuhg the console. Damien Sandras escreveu: > Le mardi 09 octobre 2007 ? 08:39 -0300, Antonio Carlos Ribeiro Nogueira > a ?crit : > >> Hi, My Ekiga, despite to be 2.0.9 version, it is not disconnecting the >> other hand (at my home. I left it connected in automatic answer) when I >> disconnect myself here at my work at University. So I would like to know >> the command I should give in console mode to disconnect it (without to >> need to click on the plug icone in the graphical interface). I use the >> auto answer because my mother understand nothing of computer. She is 83 >> years old. And I would like to chat with her along the day. I beg your >> perdon for my poor english. Thanks in advance. >> > > There is a setting in Ekiga : "Disconnect the call if nothing is > received during x seconds". > > Just enable that setting and the phone will disconnect if there is > inactivity. > > That being said, it is weird that it does not react to your > disconnection. Perhaps a network issue... > From dsandras at seconix.com Thu Oct 11 14:30:15 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Oct 2007 16:30:15 +0200 Subject: [Ekiga-list] How to disconect from the other end with console command. In-Reply-To: <470E119F.9080603@emc.ufsc.br> References: <470B688A.1050604@emc.ufsc.br> <1192047069.31851.7.camel@scorpion> <470E119F.9080603@emc.ufsc.br> Message-ID: <1192113015.23414.0.camel@scorpion> Le jeudi 11 octobre 2007 ? 09:05 -0300, Antonio Carlos Ribeiro Nogueira a ?crit : > Well, it is a problem like another user reported us in the list... It > doesn't hung up if the other side disconnect. So I would like to know > how is the command I should send throuhg the console. > There is no such command. and until nobody sends a -d 4 output of the side that does not disconnect, it will be hard to fix as I can not reproduce it. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From hunteke at earlham.edu Thu Oct 11 16:16:58 2007 From: hunteke at earlham.edu (Kevin Hunter) Date: Thu, 11 Oct 2007 12:16:58 -0400 Subject: [Ekiga-list] suggestion Message-ID: <470E4C7A.8030306@earlham.edu> Hi Damien, Suggestion: I note that the tooltip that pops up when I'm over the audio transmission button says "Audio transmission status. During a call, click here to suspend or resume the audio transmission." Seems to me that might be better served as "Mute" and "Unmute". My 2 cents, Kevin Ekiga 2.0.11 From alex at schlossadler.net Thu Oct 11 18:45:27 2007 From: alex at schlossadler.net (alex) Date: Fri, 12 Oct 2007 04:45:27 +1000 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <1192089485.4213.20.camel@scorpion> References: <470D9892.8020008@schlossadler.net> <470DA277.4030809@schlossadler.net> <1192089485.4213.20.camel@scorpion> Message-ID: <470E6F47.1010702@schlossadler.net> Damien Sandras wrote: > Le jeudi 11 octobre 2007 ? 14:11 +1000, alex a ?crit : > >> alex wrote: >> >>> This is probably a very common question/issue, but as far as I know, I >>> have done everything to help the configure script find the library, I >>> have this output: >>> >>> Invoked: ./configure --prefix=/usr/local --with-pwlib-dir=/usr/local >>> --with-opal-dir=/usr/local >>> >>> Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema >>> installation >>> Using $(sysconfdir)/gconf/schemas as install directory for schema files >>> checking for pkg-config... (cached) /usr/bin/pkg-config >>> checking pkg-config is at least version 0.9.0... yes >>> checking for EKIGA... yes >>> checking for EDS... yes >>> checking for scrollkeeper-config... /usr/bin/scrollkeeper-config >>> checking whether OS type is supported... yes >>> checking for PWLib includes in /usr/local/include/... >>> checking for /usr/local/include/ptlib/pprocess.h... yes >>> checking for read in -lpt... no >>> configure: error: You need the PWLib library to compile Ekiga >>> >>> bash-3.00$ ls -l /usr/local/lib |grep libpt >>> lrwxrwxrwx 1 root root 22 Oct 11 12:33 libpt.so -> >>> libpt_solaris_x86_r.so >>> lrwxrwxrwx 1 root root 30 Oct 11 12:33 >>> libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 >>> lrwxrwxrwx 1 root root 30 Oct 11 12:33 >>> libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 >>> lrwxrwxrwx 1 root root 30 Oct 11 12:33 >>> libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 >>> -r--r--r-- 1 root root 5507268 Oct 11 12:33 >>> libpt_solaris_x86_r.so.1.10.10 >>> >>> Operating system is Solaris (OpenSolaris - Solaris 11). >>> >>> Out of desperation, I tried this (not normally needed as other software >>> doesn't have trouble finding things): >>> >>> bash-3.00$ export LDFLAGS="-L/usr/local/lib:/usr/lib >>> -R/usr/local/lib:/usr/lib" >>> >>> and tried again.. same error. Opal didnt have any problems finding my >>> libraries in /usr/local, why is ekiga having the issue? >>> >>> Any ideas what the problem is? >>> >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >>> >>> >> Some more info on this, I looked at config.log and found this: >> >> configure:22375: checking for read in -lpt >> configure:22410: g++ -o conftest -O4 -L/usr/local/lib:/usr/lib >> -R/usr/local/lib:/usr/lib -L/usr/local/lib/ conftest.cpp -lpt >> >&5 >> Undefined first referenced >> symbol in file >> PVideoDevice::SetColourFormatConverter(PString const&) >> /usr/local/lib//libpt.so >> PVideoDevice::GetVideoFormat() const /usr/local/lib//libpt.so >> PVideoDevice::GetHue() /usr/local/lib//libpt.so >> PVideoDevice::SetHue(unsigned int) /usr/local/lib//libpt.so >> typeinfo for PVideoOutputDevice /usr/local/lib//libpt.so >> vtable for PVideoOutputDevice /usr/local/lib//libpt.so >> PVideoOutputDevice::Start() /usr/local/lib//libpt.so >> PVideoDevice::SetVideoChannelFormat(int, >> PVideoDevice::VideoFormat)/usr/local/lib//libpt.so >> PVideoDevice::~PVideoDevice() /usr/local/lib//libpt.so >> PVideoOutputDevice::PVideoOutputDevice()/usr/local/lib//libpt.so >> PVideoDevice::SetWhiteness(unsigned int)/usr/local/lib//libpt.so >> PVideoDevice::GetWhiteness() /usr/local/lib//libpt.so >> PVideoDevice::SetFrameRate(unsigned int)/usr/local/lib//libpt.so >> PVideoOutputDevice::Stop() /usr/local/lib//libpt.so >> PVideoDevice::GetMaxFrameBytesConverted(int) const/usr/local/lib//libpt.so >> PVideoDevice::SetChannel(int) /usr/local/lib//libpt.so >> PVideoDevice::OpenFull(PVideoDevice::OpenArgs const&, >> int)/usr/local/lib//libpt.so >> PVideoDevice::SetFrameSize(unsigned int, unsigned >> int)/usr/local/lib//libpt.so >> PVideoDevice::GetFrameSizeLimits(unsigned int&, unsigned int&, unsigned >> int&, unsigned int&)/usr/local/lib//libpt.so >> PVideoDevice::SetColour(unsigned int)/usr/local/lib//libpt.so >> PVideoDevice::GetContrast() /usr/local/lib//libpt.so >> PVideoDevice::GetColour() /usr/local/lib//libpt.so >> >> What is this all about? >> > > You probably have conflicting libraries / headers on your system. > Damien, I'm not convinced this is the issue after finding this: http://mail.gnome.org/archives/ekiga-list/2007-February/msg00125.html Could it be perhaps that these PVideo functions are only available under linux? I am not using linux, I'm not interested in video, I just want to use VOIP. The --disable-video flag in pwlib's configure script doesn't help. Its ekiga that is expecting these functions to be available? How do we go disabling ekiga's dependency on these functions, so that people who arn't using linux can build the program without having to resort to open heart surgery on the code? Perhaps you could integrate this into the configure script. Not meaning to be rude, it would be nice if your program was a bit more BSD and Solaris friendly. BTW: The pwlib up on your page (1.10.10) wont even build under solaris without hacking up the makefiles. However http://www.voxgratia.org/releases/pwlib-v1_11_1-src.tar.gz builds and installs straight out of the box with no problems. Hopefully anyone else attempting to get ekiga 2.0.11 working on bsd/solaris will see this post of mine and it will spare them many hours of grief. Alex. From dsandras at seconix.com Thu Oct 11 20:58:51 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Oct 2007 22:58:51 +0200 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <470E6F47.1010702@schlossadler.net> References: <470D9892.8020008@schlossadler.net> <470DA277.4030809@schlossadler.net> <1192089485.4213.20.camel@scorpion> <470E6F47.1010702@schlossadler.net> Message-ID: <1192136331.4076.21.camel@scorpion> Hi, Le vendredi 12 octobre 2007 ? 04:45 +1000, alex a ?crit : > Damien, > > I'm not convinced this is the issue after finding this: > > http://mail.gnome.org/archives/ekiga-list/2007-February/msg00125.html > > Could it be perhaps that these PVideo functions are only available under > linux? I am not using linux, I'm not interested in video, I just want to > use VOIP. They are supposed to work everywhere. Specific implementation is done in plugins, but those functions are generic. > > The --disable-video flag in pwlib's configure script doesn't help. Its > ekiga that is expecting these functions to be available? No, Ekiga is not expecting them, and if I'm not wrong, the configure script fails before trying to compile ekiga, just when trying to compile a sample program (which does not implement video). So your libraries are not correctly compiled/installed. > How do we go disabling ekiga's dependency on these functions, so that > people who arn't using linux can build the program without having to resort > to open heart surgery on the code? Perhaps you could integrate this into > the configure script. Sure I could. But Ekiga builds on other platforms. > Not meaning to be rude, it would be nice if your program was a bit more > BSD and Solaris friendly. BTW: The pwlib up on your page (1.10.10) wont Sun is providing an OpenSolaris build for each release. Nobody is maintaining the BSD version anymore. I don't want to be rude either, but Ekiga is Open Source and I am its maintainer. That means everybody can help maintaining a version for each OS. That does not mean I am forced doing it. I simply do not have enough spare time for that... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Thu Oct 11 20:59:13 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 11 Oct 2007 22:59:13 +0200 Subject: [Ekiga-list] suggestion In-Reply-To: <470E4C7A.8030306@earlham.edu> References: <470E4C7A.8030306@earlham.edu> Message-ID: <1192136353.4076.23.camel@scorpion> Hi, Le jeudi 11 octobre 2007 ? 12:16 -0400, Kevin Hunter a ?crit : > Hi Damien, > > Suggestion: I note that the tooltip that pops up when I'm over the audio > transmission button says "Audio transmission status. During a call, > click here to suspend or resume the audio transmission." Seems to me > that might be better served as "Mute" and "Unmute". > Good suggestion, I am forwarding it to somebody who can commit it. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From jan.schampera at web.de Thu Oct 11 21:07:52 2007 From: jan.schampera at web.de (Jan Schampera) Date: Thu, 11 Oct 2007 23:07:52 +0200 Subject: [Ekiga-list] suggestion In-Reply-To: <470E4C7A.8030306@earlham.edu> References: <470E4C7A.8030306@earlham.edu> Message-ID: <470E90A8.1090701@web.de> Kevin Hunter wrote: > Suggestion: I note that the tooltip that pops up when I'm over the audio > transmission button says "Audio transmission status. During a call, > click here to suspend or resume the audio transmission." Seems to me > that might be better served as "Mute" and "Unmute". Kevin, This button doesn't mute the microphone, it really stops the transmission of audio data. The MIC still is active. The result might be similar but it's definitely not the same. I agree that the tooltip is long and maybe confusing. Is there another word or short expression that matches the real functionality? J. From alex at schlossadler.net Thu Oct 11 21:15:01 2007 From: alex at schlossadler.net (alex) Date: Fri, 12 Oct 2007 07:15:01 +1000 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <1192136331.4076.21.camel@scorpion> References: <470D9892.8020008@schlossadler.net> <470DA277.4030809@schlossadler.net> <1192089485.4213.20.camel@scorpion> <470E6F47.1010702@schlossadler.net> <1192136331.4076.21.camel@scorpion> Message-ID: <470E9255.7020801@schlossadler.net> Hi Damien, I have made some further progress on getting it to build, with a lot of hackwork though. I borrowed /usr/ports/multimedia/v4l_compat/files/videodev.h from a FreeBSD machine and copied it over to /usr/include/linux, and rebuilt pwlib. I no longer get the message that the library is missing, however, that my version of pwlib 1.11.1 doesnt meet the recommended requirements, my solution to this is very bad and dirty, but I had no choice, pwlib 1.10.10 refuses to build (who can I speak to regarding this problem with that version of pwlib?), I had to edit ptbuildopts.h and fake the version number to allow the configure script to proceed (and also having to symlink libpt_solaris_x86_r.so.1.10.10 to libpt_solaris_x86_r.so.1.11.1 to avoid linking issues). I disabled avahi support - is this a bad idea? What will be missing from the program if I do this? I have one final error that occurs in the build, perhaps you can suggest a possible cause: g++ -O4 -o ekiga accounts.o addressbook.o callbacks.o callshistory.o chat.o config.o druid.o history.o main.o misc.o preferences.o tools.o statusicon.o audio.o fakevideoinput.o videoinput.o videooutput.o accountshandler.o ekiga.o manager.o h323.o pcss.o sip.o urlhandler.o stun.o bonobo.o ../lib/.libs/libekiga.a /usr/sfw/lib/libstdc++.so -L/usr/sfw/lib -lgcc_s -L/usr/local/lib -lesd -laudiofile -lgnomeui-2 -lSM -lICE -lbonoboui-2 -lgnomevfs-2 -lgnome-keyring -lgnomecanvas-2 -lart_lgpl_2 -lpangoft2-1.0 -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lmlib -lpangocairo-1.0 -lpango-1.0 -lcairo -lebook-1.2 -lgnome-2 -lpopt -ledataserver-1.2 -lxml2 -lz -lm -lsocket -lnsl -lgconf-2 -lbonobo-2 -lbonobo-activation -lgmodule-2.0 -lORBit-2 -lgthread-2.0 -lthread -lgobject-2.0 -lglib-2.0 -L/usr/lib -lSDL -lposix4 -lpt -lopal -ldl -lpthread -Wl,-R -Wl,/usr/sfw/lib -Wl,-R -Wl,/usr/sfw/lib -Wl,-R -Wl,/usr/lib ld: warning: file /usr/sfw/lib/libstdc++.so: attempted multiple inclusion of file Undefined first referenced symbol in file XFree ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XSync ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XSendEvent misc.o (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XGetWindowProperty ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XFlush ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) PSafeObject::PSafeObject(PSafeObject*)/usr/local/lib/libopal.so XGrabServer ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XUngrabServer ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XGetSelectionOwner ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XInternAtom ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) XSelectInput ../lib/.libs/libekiga.a(eggtrayicon.o) (symbol belongs to implicit dependency /usr/lib/libX11.so.4) ld: fatal: Symbol referencing errors. No output written to ekiga collect2: ld returned 1 exit status gmake[3]: *** [ekiga] Error 1 gmake[3]: Leaving directory `/export/home/alex/download/ekiga-2.0.11/src' Error: ld: warning: file /usr/sfw/lib/libstdc++.so: attempted multiple inclusion of file What does this mean? Damien Sandras wrote: > Hi, > > Le vendredi 12 octobre 2007 ? 04:45 +1000, alex a ?crit : > >> Damien, >> >> I'm not convinced this is the issue after finding this: >> >> http://mail.gnome.org/archives/ekiga-list/2007-February/msg00125.html >> >> Could it be perhaps that these PVideo functions are only available under >> linux? I am not using linux, I'm not interested in video, I just want to >> use VOIP. >> > > They are supposed to work everywhere. Specific implementation is done in > plugins, but those functions are generic. > >> The --disable-video flag in pwlib's configure script doesn't help. Its >> ekiga that is expecting these functions to be available? >> > > No, Ekiga is not expecting them, and if I'm not wrong, the configure > script fails before trying to compile ekiga, just when trying to compile > a sample program (which does not implement video). > > So your libraries are not correctly compiled/installed. > > >> How do we go disabling ekiga's dependency on these functions, so that >> people who arn't using linux can build the program without having to resort >> to open heart surgery on the code? Perhaps you could integrate this into >> the configure script. >> > > Sure I could. But Ekiga builds on other platforms. > > >> Not meaning to be rude, it would be nice if your program was a bit more >> BSD and Solaris friendly. BTW: The pwlib up on your page (1.10.10) wont >> > > Sun is providing an OpenSolaris build for each release. > Nobody is maintaining the BSD version anymore. > > I don't want to be rude either, but Ekiga is Open Source and I am its > maintainer. That means everybody can help maintaining a version for each > OS. That does not mean I am forced doing it. I simply do not have enough > spare time for that... > From hunteke at earlham.edu Thu Oct 11 21:28:29 2007 From: hunteke at earlham.edu (Kevin Hunter) Date: Thu, 11 Oct 2007 17:28:29 -0400 Subject: [Ekiga-list] suggestion In-Reply-To: <470E90A8.1090701@web.de> References: <470E4C7A.8030306@earlham.edu> <470E90A8.1090701@web.de> Message-ID: <470E957D.3000702@earlham.edu> At 5:07p -0400 on 11 Oct 2007, Jan Schampera wrote: > This button doesn't mute the microphone, it really stops the > transmission of audio data. The MIC still is active. The result might be > similar but it's definitely not the same. I like the way you think! (Developer ? developer) Okay, it doesn't mute the microphone, yet no audio is sent. What qualitative difference to the user does that make? > I agree that the tooltip is long and maybe confusing. Is there another > word or short expression that matches the real functionality? Pending response to above question . . . (i.e. I dunno yet.) Kevin From 1.41421 at gmail.com Thu Oct 11 21:41:05 2007 From: 1.41421 at gmail.com (JCA) Date: Thu, 11 Oct 2007 14:41:05 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: >>> I am trying to dial a 1-800 number in the US using Ekiga and my >>> Ekiga PC-to-Phone account. When I do so, I get a recording to the >>> effect that such number is not free from my current location, and that >>> international calling fees will be charged if I proceed. This is kind >>> of galling, for I am calling from the US. >>> >>> Is it at all possible to call 1-800 numbers at no charge with Ekiga? >> >> Yes, it is. >> >> Just get a free account on http://ekiga.net >> and dial : >> *0131800xxxxxxx at ekiga.net > > It doesn't work for me. I do have an ekiga.net account, I do have a > PC-to-phone account, I can use them both all right, but if I try the > recipe above I get a fleeting message that says Security Check Failed. I notice that nobody has addressed this. Could somebody please confirm that these numbers can be reached as indicated in the reply above? Like I said, it does not work for me; in fact, all the recipes for 1800 numbers in the US listed in http://wiki.ekiga.org/index.php/Fun_Numbers fail in the way I described. Since I have an account at ekiga.net and I can make calls to ordinary phones, I must be missing something that prevents me from using the 1800 recipes. Feedback on what might be missing would be most welcome. From iris.gates at gmail.com Thu Oct 11 21:47:24 2007 From: iris.gates at gmail.com (E Johnson) Date: Thu, 11 Oct 2007 17:47:24 -0400 Subject: [Ekiga-list] suggestion Message-ID: <70541d1e0710111447n732f0e1cg5faf250567fac318@mail.gmail.com> J: > This button doesn't mute the microphone, it really stops the transmission of audio data. The MIC still is active. The result might be similar but it's definitely not the same. > I agree that the tooltip is long and maybe confusing. Is there another word or short expression that matches the real functionality? Call it 'Hold' and 'Resume.' That's what other VoIP progs use, as well as what regular landline phone communications have used for decades. And it makes sense, as you say the mic is still on, but the xmit is off for that particular call. Liz J From jan.schampera at web.de Thu Oct 11 22:36:04 2007 From: jan.schampera at web.de (Jan Schampera) Date: Fri, 12 Oct 2007 00:36:04 +0200 Subject: [Ekiga-list] suggestion In-Reply-To: <70541d1e0710111447n732f0e1cg5faf250567fac318@mail.gmail.com> References: <70541d1e0710111447n732f0e1cg5faf250567fac318@mail.gmail.com> Message-ID: <470EA554.3030201@web.de> E Johnson wrote: > Call it 'Hold' and 'Resume.' That's what other VoIP progs use, as well > as what regular landline phone communications have used for decades. > And it makes sense, as you say the mic is still on, but the xmit is > off for that particular call. Mh, to not confuse it with call hold, it would be something like "Hold audio.", "Resume audio." then. J. From alex at schlossadler.net Fri Oct 12 00:57:29 2007 From: alex at schlossadler.net (alex) Date: Fri, 12 Oct 2007 10:57:29 +1000 Subject: [Ekiga-list] ekiga 2.0.11 wont start Message-ID: <470EC679.8070308@schlossadler.net> Hi Guys, I managed to get the proper pwlib and opal given on the ekiga.net site, built and installed. But when I run it, I get errors and it wont start: bash-3.00$ /usr/local/bin/ekiga ld.so.1: ekiga: fatal: libopal_solaris_x86_r.so.2.2: open failed: No such file or directory Killed bash-3.00$ ls -l /usr/local/lib total 49396 drwxr-xr-x 3 root root 512 Oct 12 10:50 bonobo lrwxrwxrwx 1 root root 31 Oct 12 10:38 libopal.so -> libopal_solaris_x86_r.so.2.2.11 lrwxrwxrwx 1 root root 31 Oct 12 10:38 libopal_solaris_x86_r.so -> libopal_solaris_x86_r.so.2.2.11 lrwxrwxrwx 1 root root 31 Oct 12 10:38 libopal_solaris_x86_r.so.2 -> libopal_solaris_x86_r.so.2.2.11 lrwxrwxrwx 1 root root 31 Oct 12 10:38 libopal_solaris_x86_r.so.2.2 -> libopal_solaris_x86_r.so.2.2.11 -rwxr-xr-x 1 root root 19260752 Oct 12 10:38 libopal_solaris_x86_r.so.2.2.11 lrwxrwxrwx 1 root root 22 Oct 12 10:26 libpt.so -> libpt_solaris_x86_r.so lrwxrwxrwx 1 root root 30 Oct 12 10:26 libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 lrwxrwxrwx 1 root root 30 Oct 12 10:26 libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 lrwxrwxrwx 1 root root 30 Oct 12 10:26 libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 -r--r--r-- 1 root root 5975888 Oct 12 10:26 libpt_solaris_x86_r.so.1.10.10 drwxr-xr-x 3 root root 512 Oct 12 10:26 pwlib What could be the problem? From alex at schlossadler.net Fri Oct 12 01:10:26 2007 From: alex at schlossadler.net (alex) Date: Fri, 12 Oct 2007 11:10:26 +1000 Subject: [Ekiga-list] ekiga 2.0.11 wont start In-Reply-To: <470EC679.8070308@schlossadler.net> References: <470EC679.8070308@schlossadler.net> Message-ID: <470EC982.3020004@schlossadler.net> alex wrote: > Hi Guys, > > I managed to get the proper pwlib and opal given on the ekiga.net site, > built and installed. > > But when I run it, I get errors and it wont start: > > bash-3.00$ /usr/local/bin/ekiga > ld.so.1: ekiga: fatal: libopal_solaris_x86_r.so.2.2: open failed: No > such file or directory > Killed > > bash-3.00$ ls -l /usr/local/lib > total 49396 > drwxr-xr-x 3 root root 512 Oct 12 10:50 bonobo > lrwxrwxrwx 1 root root 31 Oct 12 10:38 libopal.so -> > libopal_solaris_x86_r.so.2.2.11 > lrwxrwxrwx 1 root root 31 Oct 12 10:38 > libopal_solaris_x86_r.so -> libopal_solaris_x86_r.so.2.2.11 > lrwxrwxrwx 1 root root 31 Oct 12 10:38 > libopal_solaris_x86_r.so.2 -> libopal_solaris_x86_r.so.2.2.11 > lrwxrwxrwx 1 root root 31 Oct 12 10:38 > libopal_solaris_x86_r.so.2.2 -> libopal_solaris_x86_r.so.2.2.11 > -rwxr-xr-x 1 root root 19260752 Oct 12 10:38 > libopal_solaris_x86_r.so.2.2.11 > lrwxrwxrwx 1 root root 22 Oct 12 10:26 libpt.so -> > libpt_solaris_x86_r.so > lrwxrwxrwx 1 root root 30 Oct 12 10:26 > libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 > lrwxrwxrwx 1 root root 30 Oct 12 10:26 > libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 > lrwxrwxrwx 1 root root 30 Oct 12 10:26 > libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 > -r--r--r-- 1 root root 5975888 Oct 12 10:26 > libpt_solaris_x86_r.so.1.10.10 > drwxr-xr-x 3 root root 512 Oct 12 10:26 pwlib > > What could be the problem? > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > Ok, I fixed this, but I dont understand why I had to do, what I did. When I built pwlib, opal and ekiga, I used --prefix=/usr/local on each. For some reason ekiga was looking in /usr/lib instead of /usr/local/lib, I re-ran the install for each of the libraries, but this time installed them in /usr, ekiga now starts, but I get an error message about no suitable audio plugins being found. I have ekiga 2.0.9 installed on the same system and it works.. bash-3.00$ /usr/local/bin/ekiga -d 4 2007/10/12 11:05:00.981 0:00.382 ekiga Detected audio plugins: 2007/10/12 11:05:00.981 0:00.382 ekiga Detected video plugins: Picture,V4L 2007/10/12 11:05:00.982 0:00.383 ekiga Detected audio plugins: 2007/10/12 11:05:00.982 0:00.383 ekiga Detected video plugins: Picture,V4L 2007/10/12 11:05:51.168 0:50.569 ekiga OpalMan Deleted manager. Any ideas? From mshahwan2001 at yahoo.com Fri Oct 12 03:15:30 2007 From: mshahwan2001 at yahoo.com (Michael) Date: Thu, 11 Oct 2007 20:15:30 -0700 (PDT) Subject: [Ekiga-list] call termination is unnoticed Message-ID: <779355.8682.qm@web52405.mail.re2.yahoo.com> Damien: Forgive me for not be so tech savvy, but if you or anyone in the community can give me step by step instructions in Xubuntu I would be more then happy to post a -d 4 output . ----- Original Message ---- From: Damien Sandras To: Ekiga mailing list Sent: Thursday, October 11, 2007 2:57:30 AM Subject: Re: [Ekiga-list] call termination is unnoticed Le mercredi 10 octobre 2007 ? 19:12 -0700, Michael a ?crit : > Does anyone notice that Ekiga does not understand a call has > terminated. > > For example if Ekiga user calls or receives a call and the other party > hangs up Ekiga does not disconnect. It simply will keep the line > active and not allow new calls to come in. > > Any work around besides remembering to hang up after each call is > terminated? > > > > ______________________________________________________________________ Can you post a -d 4 output of the side that receives the disconnection request and does not hangup ? Thanks, -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list ____________________________________________________________________________________ Looking for a deal? Find great prices on flights and hotels with Yahoo! FareChase. http://farechase.yahoo.com/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From lists at dcorking.com Fri Oct 12 07:06:16 2007 From: lists at dcorking.com (David Corking) Date: Fri, 12 Oct 2007 08:06:16 +0100 Subject: [Ekiga-list] call termination is unnoticed In-Reply-To: <779355.8682.qm@web52405.mail.re2.yahoo.com> References: <779355.8682.qm@web52405.mail.re2.yahoo.com> Message-ID: On 10/12/07, Michael wrote: > Forgive me for not be so tech savvy, but if you or anyone in the community > can give me step by step instructions in Xubuntu I would be more then happy > to post a -d 4 output . http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output_from_Ekiga From dsandras at seconix.com Fri Oct 12 08:11:44 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 12 Oct 2007 10:11:44 +0200 Subject: [Ekiga-list] suggestion In-Reply-To: <470EA554.3030201@web.de> References: <70541d1e0710111447n732f0e1cg5faf250567fac318@mail.gmail.com> <470EA554.3030201@web.de> Message-ID: <1192176704.4417.4.camel@scorpion> Le vendredi 12 octobre 2007 ? 00:36 +0200, Jan Schampera a ?crit : > E Johnson wrote: > > > Call it 'Hold' and 'Resume.' That's what other VoIP progs use, as well > > as what regular landline phone communications have used for decades. > > And it makes sense, as you say the mic is still on, but the xmit is > > off for that particular call. > > Mh, to not confuse it with call hold, it would be something like > "Hold audio.", "Resume audio." then. Very good idea! -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Oct 12 08:14:14 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 12 Oct 2007 10:14:14 +0200 Subject: [Ekiga-list] ekiga 2.0.11 wont start In-Reply-To: <470EC982.3020004@schlossadler.net> References: <470EC679.8070308@schlossadler.net> <470EC982.3020004@schlossadler.net> Message-ID: <1192176854.4417.7.camel@scorpion> Le vendredi 12 octobre 2007 ? 11:10 +1000, alex a ?crit : > alex wrote: > > Hi Guys, > > > > I managed to get the proper pwlib and opal given on the ekiga.net site, > > built and installed. > > > > But when I run it, I get errors and it wont start: > > > > bash-3.00$ /usr/local/bin/ekiga > > ld.so.1: ekiga: fatal: libopal_solaris_x86_r.so.2.2: open failed: No > > such file or directory > > Killed > > > > bash-3.00$ ls -l /usr/local/lib > > total 49396 > > drwxr-xr-x 3 root root 512 Oct 12 10:50 bonobo > > lrwxrwxrwx 1 root root 31 Oct 12 10:38 libopal.so -> > > libopal_solaris_x86_r.so.2.2.11 > > lrwxrwxrwx 1 root root 31 Oct 12 10:38 > > libopal_solaris_x86_r.so -> libopal_solaris_x86_r.so.2.2.11 > > lrwxrwxrwx 1 root root 31 Oct 12 10:38 > > libopal_solaris_x86_r.so.2 -> libopal_solaris_x86_r.so.2.2.11 > > lrwxrwxrwx 1 root root 31 Oct 12 10:38 > > libopal_solaris_x86_r.so.2.2 -> libopal_solaris_x86_r.so.2.2.11 > > -rwxr-xr-x 1 root root 19260752 Oct 12 10:38 > > libopal_solaris_x86_r.so.2.2.11 > > lrwxrwxrwx 1 root root 22 Oct 12 10:26 libpt.so -> > > libpt_solaris_x86_r.so > > lrwxrwxrwx 1 root root 30 Oct 12 10:26 > > libpt_solaris_x86_r.so -> libpt_solaris_x86_r.so.1.10.10 > > lrwxrwxrwx 1 root root 30 Oct 12 10:26 > > libpt_solaris_x86_r.so.1 -> libpt_solaris_x86_r.so.1.10.10 > > lrwxrwxrwx 1 root root 30 Oct 12 10:26 > > libpt_solaris_x86_r.so.1.10 -> libpt_solaris_x86_r.so.1.10.10 > > -r--r--r-- 1 root root 5975888 Oct 12 10:26 > > libpt_solaris_x86_r.so.1.10.10 > > drwxr-xr-x 3 root root 512 Oct 12 10:26 pwlib > > > > What could be the problem? > > > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > Ok, I fixed this, but I dont understand why I had to do, what I did. > When I built pwlib, opal and ekiga, I used --prefix=/usr/local on each. > For some reason ekiga was looking in /usr/lib instead of /usr/local/lib, > I re-ran the install for each of the libraries, but this time installed > them in That is the way unix systems work : each program loads its libraries from the LIBRARY PATH. You can modify it by setting the appropriate LD_LIBRARY_PATH variable. > /usr, ekiga now starts, but I get an error message about no suitable > audio plugins being found. I have ekiga 2.0.9 installed on the same system > and it works.. > > bash-3.00$ /usr/local/bin/ekiga -d 4 > 2007/10/12 11:05:00.981 0:00.382 ekiga Detected > audio plugins: > 2007/10/12 11:05:00.981 0:00.382 ekiga Detected > video plugins: Picture,V4L > 2007/10/12 11:05:00.982 0:00.383 ekiga Detected > audio plugins: > 2007/10/12 11:05:00.982 0:00.383 ekiga Detected > video plugins: Picture,V4L > 2007/10/12 11:05:51.168 0:50.569 ekiga OpalMan > Deleted manager. > The Video4Linux plugin is correctly installed, but you have no plugin for audio. Make sure the correct plugin for audio has been compiled. On FreeBSD, it should be OSS. On OpenSolaris, it should be sunaudio. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From lists at dcorking.com Fri Oct 12 09:01:23 2007 From: lists at dcorking.com (David Corking) Date: Fri, 12 Oct 2007 10:01:23 +0100 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: On 10/11/07, JCA <1.41421 at gmail.com> wrote: > >>> I am trying to dial a 1-800 number in the US using Ekiga and my > >>> Ekiga PC-to-Phone account. When I do so, I get a recording to the > >>> effect that such number is not free from my current location, and that > >>> international calling fees will be charged if I proceed. This is kind > >>> of galling, for I am calling from the US. > >>> > >>> Is it at all possible to call 1-800 numbers at no charge with Ekiga? > >> > >> Yes, it is. > >> > >> Just get a free account on http://ekiga.net > >> and dial : > >> *0131800xxxxxxx at ekiga.net > > > > It doesn't work for me. I do have an ekiga.net account, I do have a > > PC-to-phone account, I can use them both all right, but if I try the > > recipe above I get a fleeting message that says Security Check Failed. > > I notice that nobody has addressed this. Could somebody please > confirm that these numbers can be reached as indicated in the reply > above? Like I said, it does not work for me; in fact, all the recipes > for 1800 numbers in the US listed in > http://wiki.ekiga.org/index.php/Fun_Numbers fail in the way I > described. Since I have an account at ekiga.net and I can make calls > to ordinary phones, I must be missing something that prevents me from > using the 1800 recipes. Feedback on what might be missing would be > most welcome. Do the other Fun Numbers work for you? From lists at dcorking.com Fri Oct 12 14:43:38 2007 From: lists at dcorking.com (David Corking) Date: Fri, 12 Oct 2007 15:43:38 +0100 Subject: [Ekiga-list] ekiga 2.0.11 Cant find pwlib? In-Reply-To: <470E9255.7020801@schlossadler.net> References: <470D9892.8020008@schlossadler.net> <470DA277.4030809@schlossadler.net> <1192089485.4213.20.camel@scorpion> <470E6F47.1010702@schlossadler.net> <1192136331.4076.21.camel@scorpion> <470E9255.7020801@schlossadler.net> Message-ID: On 10/11/07, alex wrote: > I disabled avahi support - is this a bad idea? I have compiled it in the past with avahi disabled - no problem. > What will be missing from > the program if I do this? Only the ability for agents to discover each other on the LAN using zeroconf aka Apple Bonjour. Someone else will have to answer regarding your linker error, however. I know little enough about the Linux linker, and the Solaris linker is completely out of my ken. From sevmek at free.fr Fri Oct 12 15:29:35 2007 From: sevmek at free.fr (yannick) Date: Fri, 12 Oct 2007 17:29:35 +0200 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: <1192202976.6744.125.camel@achille> Le jeudi 11 octobre 2007 ? 14:41 -0700, JCA a ?crit : > >>> I am trying to dial a 1-800 number in the US using Ekiga and my > >>> Ekiga PC-to-Phone account. When I do so, I get a recording to the > >>> effect that such number is not free from my current location, and that > >>> international calling fees will be charged if I proceed. This is kind > >>> of galling, for I am calling from the US. > >>> > >>> Is it at all possible to call 1-800 numbers at no charge with Ekiga? > >> > >> Yes, it is. > >> > >> Just get a free account on http://ekiga.net > >> and dial : > >> *0131800xxxxxxx at ekiga.net > > > > It doesn't work for me. I do have an ekiga.net account, I do have a > > PC-to-phone account, I can use them both all right, but if I try the > > recipe above I get a fleeting message that says Security Check Failed. > > I notice that nobody has addressed this. Could somebody please > confirm that these numbers can be reached as indicated in the reply > above? Like I said, it does not work for me; in fact, all the recipes > for 1800 numbers in the US listed in > http://wiki.ekiga.org/index.php/Fun_Numbers fail in the way I > described. Since I have an account at ekiga.net and I can make calls > to ordinary phones, I must be missing something that prevents me from > using the 1800 recipes. Feedback on what might be missing would be > most welcome. I just tested those numbers: sip:*01318006790847 at ekiga.net (codec GSM, Pizza Hut Telemarketing) sip:*01318008267789 at ekiga.net Colonial Bank sip:*01318005277372 at ekiga.net Society Of Former Special Agents Of Fbi They work here. Not all numbers I tried do work, depending if they are connected to the network, or if I'm in the right area. But I get an error message (a vocal message) most of the time. Regards, Yannick > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From 1.41421 at gmail.com Fri Oct 12 17:25:16 2007 From: 1.41421 at gmail.com (JCA) Date: Fri, 12 Oct 2007 10:25:16 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: > I just tested those numbers: > sip:*01318006790847 at ekiga.net (codec GSM, Pizza Hut Telemarketing) > sip:*01318008267789 at ekiga.net Colonial Bank > sip:*01318005277372 at ekiga.net Society Of Former Special Agents Of Fbi > > They work here. They do work all right for me as well. > Not all numbers I tried do work, depending if they are connected to the > network, or if I'm in the right area. But I get an error message (a > vocal message) most of the time. It would seem that not all 1800 numbers in the US are equal. Other 1800 numbers I have tested (in particular, those I am interested in) all fail with the same "Security check failed" message printed out at the lower end of Ekiga's window. These are ordinary 1800 numbers that work as expected when using ordinary phones. You might like to test e.g. 1 800 4321359 (for Frontier Airlines.) From jan.schampera at web.de Fri Oct 12 17:47:47 2007 From: jan.schampera at web.de (Jan Schampera) Date: Fri, 12 Oct 2007 19:47:47 +0200 Subject: [Ekiga-list] suggestion In-Reply-To: <1192176704.4417.4.camel@scorpion> References: <70541d1e0710111447n732f0e1cg5faf250567fac318@mail.gmail.com> <470EA554.3030201@web.de> <1192176704.4417.4.camel@scorpion> Message-ID: <470FB343.3040809@web.de> Damien Sandras wrote: >>> Call it 'Hold' and 'Resume.' That's what other VoIP progs use, as well >>> as what regular landline phone communications have used for decades. >>> And it makes sense, as you say the mic is still on, but the xmit is >>> off for that particular call. >> Mh, to not confuse it with call hold, it would be something like >> "Hold audio.", "Resume audio." then. > > Very good idea! I'll open an ENH at the bugtracker, unless somebody has more time or a sytem where Ekiga actually compiles ;-) (only 2 strings!) J. From sevmek at free.fr Fri Oct 12 18:43:44 2007 From: sevmek at free.fr (yannick) Date: Fri, 12 Oct 2007 20:43:44 +0200 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: <1192214625.6744.135.camel@achille> Le vendredi 12 octobre 2007 ? 10:25 -0700, JCA a ?crit : > test e.g. 1 800 4321359 (for Frontier Airlines.) It seems this number answer a SIP 407: "407 Proxy Authentication Required This code is similar to 401 (Unauthorized), but indicates that the client MUST first authenticate itself with the proxy. SIP access authentication is explained in Sections 26 and 22.3. This status code can be used for applications where access to the communication channel (for example, a telephony gateway) rather than the callee requires authentication." I'm not sure what this exactly means in this situation... Regards, Yannick -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From dsandras at seconix.com Sat Oct 13 12:58:26 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 13 Oct 2007 14:58:26 +0200 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: <1192214625.6744.135.camel@achille> References: <1192214625.6744.135.camel@achille> Message-ID: <1192280306.4111.22.camel@scorpion> Le vendredi 12 octobre 2007 ? 20:43 +0200, yannick a ?crit : > Le vendredi 12 octobre 2007 ? 10:25 -0700, JCA a ?crit : > > test e.g. 1 800 4321359 (for Frontier Airlines.) > > It seems this number answer a SIP 407: > "407 Proxy Authentication Required > > This code is similar to 401 (Unauthorized), but indicates that the > client MUST first authenticate itself with the proxy. SIP access > authentication is explained in Sections 26 and 22.3. > > This status code can be used for applications where access to the > communication channel (for example, a telephony gateway) rather than > the callee requires authentication." > > I'm not sure what this exactly means in this situation... That the user should directly register with the SIP registrar providing access to that number. Imagine XY provides access for free to those numbers, Ekiga.net will route the SIP requests to XY, which should relay the call. In some cases (I suppose it is the case here), XY will require the user to have an XY account to relay the call. We are doing this for 500 at ekiga.net, it is restricted to Ekiga.net users. However, Ekiga.net users can be called by anyone without needing the remote peer to have an ekiga.net sip address. It is a question of policy. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From pratiksha.powar at onmobile.com Tue Oct 16 05:44:41 2007 From: pratiksha.powar at onmobile.com (Pratiksha Powar) Date: Tue, 16 Oct 2007 11:14:41 +0530 Subject: [Ekiga-list] DTMF codecs supported by Ekiga In-Reply-To: <1192513337.3299.8.camel@localhost.localdomain> References: <1191847450.4925.49.camel@scorpion> <1191907535.3645.16.camel@localhost.localdomain> <200710091924.39470.lurch@gmx.li> <1192513337.3299.8.camel@localhost.localdomain> Message-ID: <1192513481.3299.10.camel@localhost.localdomain> Also the line disturbing me is the following : 2007/10/16 11:06:05.784 0:15.021 SIP Transport:b5003270 SDP Media attribute rtpmap found for unknown RTP type [pt=96] What does it mean? On Tue, 2007-10-16 at 11:12 +0530, Pratiksha Powar wrote: > Hi Lurchi and Damien, > > > I'm attaching a fresh debug log from Ekiga. When I connect to the Voice > App, I'm keying in dtmf-1. > It looks like the payload is going through as expected but then the > Voice Application doesn't receive any dtmf input. > Please go through the log and let me know if something is strange > with either Ekiga or with the Voice App I'm connecting to. > I'll try and get some info from those guys who developed the voice app > too. > > Thanks, > Pratiksha > > > > On Tue, 2007-10-09 at 19:24 +0200, Stefan Bruens wrote: > > Am Dienstag, 9. Oktober 2007 07:25:35 schrieb Pratiksha Powar: > > > Hi Damien, > > > > > > Yes, our Voice Applications support DTMF RFC2833 quite well. > > > But they expect the payload type to be 96 and not 101. > > > > If the application expects DTMF to have a payload of 96, it is broken. DTMF > > uses dynamic payload types, so the application should use the rtpmap to get > > the payload type for DTMF > > > > Lurchi -------------- next part -------------- ============================== DISCLAIMER: The information in this message is confidential and may be legally privileged. It is intended solely for the addressee. Access to this message by anyone else is unauthorized. If you are not the intended recipient, any disclosure, copying, or distribution of the message, or any action or omission taken by you in reliance on it, is prohibited and may be unlawful. Please immediately contact the sender if you have received this message in error. Further, this e-mail may contain viruses and all reasonable precaution to minimize the risk arising there from is taken by OnMobile. OnMobile is not liable for any damage sustained by you as a result of any virus in this e-mail. All applicable virus checks should be carried out by you before opening this e-mail or any attachment thereto. Thank you - OnMobile Global Limited. ============================== From kas at fi.muni.cz Tue Oct 16 11:42:28 2007 From: kas at fi.muni.cz (Jan Kasprzak) Date: Tue, 16 Oct 2007 13:42:28 +0200 Subject: [Ekiga-list] Running a command on the incoming call event Message-ID: <20071016114228.GI23014@fi.muni.cz> Hello, I still have problems with locking the sound device between Ekiga and PulseAudio (apparently an ALSA bug, but still not fixed). I would like to suspend the PulseAudio server when the incoming call occurs (and possibly even during the outgoing calls). Is there any way of being notified before the call is established, and after the call is disconnected? Something like running an external command (or maybe a D-Bus notification). Thanks, -Yenya -- | Jan "Yenya" Kasprzak | | GPG: ID 1024/D3498839 Fingerprint 0D99A7FB206605D7 8B35FCDE05B18A5E | | http://www.fi.muni.cz/~kas/ Journal: http://www.fi.muni.cz/~kas/blog/ | > So at least in some cases, I think we should "default to stupid, < > but give users rope". --Linus Torvalds < From jpuydt at free.fr Tue Oct 16 18:08:02 2007 From: jpuydt at free.fr (Julien Puydt) Date: Tue, 16 Oct 2007 20:08:02 +0200 Subject: [Ekiga-list] Running a command on the incoming call event In-Reply-To: <20071016114228.GI23014@fi.muni.cz> References: <20071016114228.GI23014@fi.muni.cz> Message-ID: <4714FE02.5070205@free.fr> Jan Kasprzak a ?crit : > Hello, > > I still have problems with locking the sound device between Ekiga > and PulseAudio (apparently an ALSA bug, but still not fixed). I would > like to suspend the PulseAudio server when the incoming call occurs > (and possibly even during the outgoing calls). Is there any way > of being notified before the call is established, and after the > call is disconnected? Something like running an external command > (or maybe a D-Bus notification). http://svn.gnome.org/viewvc/ekiga/trunk/doc/using_dbus.html?view=markup Snark on #ekiga From mariofutire at googlemail.com Wed Oct 17 19:52:01 2007 From: mariofutire at googlemail.com (Mario Rossi) Date: Wed, 17 Oct 2007 20:52:01 +0100 Subject: [Ekiga-list] gdk & glib warnings Message-ID: <471667E1.6090302@googlemail.com> Hi, I've used for the first time ekiga 2.0.11 and I got those warnings printed on the console. I though to report them Unfortunately I don't remember what I was doing and when I tried again I was not able to reproduce them. Maybe you can use them anyway [andrea at thinkpad ~]$ ekiga It appears that you do not have ekiga.server installed in a valid location. Factory mode disabled. (ekiga:4482): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (ekiga:4482): GdkPixbuf-CRITICAL **: gdk_pixbuf_scale_simple: assertion `dest_width > 0' failed (ekiga:4482): GLib-GObject-WARNING **: gsignal.c:1695: instance `0x844f0a8' has no handler with id `3024' (ekiga:4482): GLib-GObject-WARNING **: gsignal.c:1718: instance `0x844f0a8' has no handler with id `3024' Just for reference this is the beginning of -d 4 2007/10/17 20:49:56.561 0:01.353 ekiga Detected audio plugins: ALSA 2007/10/17 20:49:56.562 0:01.354 ekiga Detected video plugins: Picture,V4L2,V4L 2007/10/17 20:49:56.562 0:01.354 ekiga Detected audio plugins: ALSA 2007/10/17 20:49:56.562 0:01.354 ekiga Detected video plugins: Picture,V4L2,V4L 2007/10/17 20:49:57.012 0:01.804 ekiga Detected the following audio input devices: Default,Intel 82801DB-ICH4,Intel 82801DB-ICH4 Modem,USB Device 0x46d:0x8b2 with plugin ALSA 2007/10/17 20:49:57.013 0:01.805 ekiga Detected the following audio output devices: Default,Intel 82801DB-ICH4,Intel 82801DB-ICH4 Modem with plugin ALSA 2007/10/17 20:49:57.014 0:01.806 ekiga Detected the following video input devices: Logitech QuickCam Pro 4000 with plugin V4L 2007/10/17 20:49:57.014 0:01.806 ekiga Detected the following audio input devices: Default,Intel 82801DB-ICH4,Intel 82801DB-ICH4 Modem,USB Device 0x46d:0x8b2 with plugin ALSA 2007/10/17 20:49:57.015 0:01.807 ekiga Detected the following audio output devices: Default,Intel 82801DB-ICH4,Intel 82801DB-ICH4 Modem with plugin ALSA 2007/10/17 20:49:57.015 0:01.807 ekiga Detected the following video input devices: Logitech QuickCam Pro 4000 with plugin V4L 2007/10/17 20:49:57.739 0:02.532 ekiga Ekiga version 2.0.11 2007/10/17 20:49:57.740 0:02.532 ekiga OPAL version 2.2.11 2007/10/17 20:49:57.740 0:02.532 ekiga PWLIB version 1.10.10 2007/10/17 20:49:57.741 0:02.541 ekiga GNOME support enabled 2007/10/17 20:49:57.749 0:02.541 ekiga Fullscreen support enabled 2007/10/17 20:49:57.749 0:02.541 ekiga DBUS support disabled 2007/10/17 20:49:57.753 0:02.545 ekiga Set TCP port range to 30000:30010 2007/10/17 20:49:57.754 0:02.546 ekiga Set RTP port range to 5000:5059 2007/10/17 20:49:57.754 0:02.546 ekiga Set UDP port range to 5060:5100 2007/10/17 20:49:57.755 0:02.547 ekiga OpalEP Created endpoint: h323 2007/10/17 20:49:57.755 0:02.547 ekiga H323 Created endpoint. 2007/10/17 20:49:57.756 0:02.548 ekiga OpalMan Added route "pc:.*=h323:" 2007/10/17 20:49:57.756 0:02.548 ekiga OpalEP Created endpoint: sip 2007/10/17 20:49:57.757 0:02.554 ekiga SIP Created endpoint. 2007/10/17 20:49:57.763 0:02.555 ekiga OpalMan Added route "pc:.*=sip:" 2007/10/17 20:49:57.763 0:02.555 ekiga OpalEP Created endpoint: pc 2007/10/17 20:49:57.765 0:02.557 ekiga PCSS Created PC sound system endpoint. 2007/10/17 20:49:57.765 0:02.557 ekiga OpalMan Added route "h323:.*=pc:" 2007/10/17 20:49:57.765 0:02.557 ekiga OpalMan Added route "sip:.*=pc:" 2007/10/17 20:49:58.661 0:03.453 Opal Listener:8488ce8 Listen Started listening thread on tcp$192.168.3.11:1720 2007/10/17 20:49:58.662 0:03.454 Opal Listener:8488ce8 Listen Waiting on socket accept on tcp$192.168.3.11:1720 2007/10/17 20:49:58.663 0:03.455 Opal Listener:848eda8 Listen Started listening thread on udp$192.168.3.11:5060 2007/10/17 20:49:58.663 0:03.455 Opal Listener:848eda8 Listen Waiting on UDP packet on udp$192.168.3.11:5060 From magaio at gmail.com Wed Oct 17 21:03:52 2007 From: magaio at gmail.com (David Farler) Date: Wed, 17 Oct 2007 17:03:52 -0400 Subject: [Ekiga-list] Service with Inbound PSTN Calls? Message-ID: <471678B8.8070304@gmail.com> Hi all, Can someone recommend an ekiga-compatible service that gives me PC-PSTN and PSTN-PC inbound calls with a phone number? I can't find much. I'm in the 'States. Thanks, Dave From razametal at gmail.com Wed Oct 17 21:15:17 2007 From: razametal at gmail.com (RazaMetaL | Only The Good Die Young) Date: Wed, 17 Oct 2007 16:15:17 -0500 Subject: [Ekiga-list] Service with Inbound PSTN Calls? In-Reply-To: <471678B8.8070304@gmail.com> References: <471678B8.8070304@gmail.com> Message-ID: On 10/17/07, David Farler wrote: > Hi all, > > Can someone recommend an ekiga-compatible service that gives me PC-PSTN > and PSTN-PC inbound calls with a phone number? I can't find much. I'm in > the 'States. > You can get one free phone number at www.ipkall.com and redirect it to your www.ekiga.net account. I'm doing the same but with my asterisk server, I'm redirecting the ipkall DID to my extension on my asterisk box. Regards, > Thanks, > > Dave > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Linux User: 255902 Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html From schan at cs.ucr.edu Thu Oct 18 01:02:49 2007 From: schan at cs.ucr.edu (sam chan) Date: Wed, 17 Oct 2007 18:02:49 -0700 (PDT) Subject: [Ekiga-list] land line users barely hear me Message-ID: hello all, using 500 at ekiga.net and Configuration Assistant, the audio tests work fine. but people at the end of land lines hear me at VERY low volume. and my voice often breaks up frequently. it's practically useless. i hear them just fine, however. my network bandwidth is fast enough(10mb down/1.5mb up). i don't know how well ekiga<->ekiga works since i don't know anyone who has it. this is version 2.0.11 on Fedora 7. i have debug output at ftp://shell.sgi.com/collect/ekiga. NOTE: you'll have to right-click and save the file. thanks, sam From michel.memeteau at gmail.com Thu Oct 18 06:45:25 2007 From: michel.memeteau at gmail.com (michel memeteau) Date: Thu, 18 Oct 2007 08:45:25 +0200 Subject: [Ekiga-list] Service with Inbound PSTN Calls? In-Reply-To: References: <471678B8.8070304@gmail.com> Message-ID: I Guess Sipphone pricing is interesting for united states ? We use Wengo and phonesystems in France 2007/10/17, RazaMetaL | Only The Good Die Young : > > On 10/17/07, David Farler wrote: > > Hi all, > > > > Can someone recommend an ekiga-compatible service that gives me PC-PSTN > > and PSTN-PC inbound calls with a phone number? I can't find much. I'm in > > the 'States. > > > > > You can get one free phone number at www.ipkall.com and redirect it to > your www.ekiga.net account. I'm doing the same but with my asterisk > server, I'm redirecting the ipkall DID to my extension on my asterisk > box. > > > Regards, > > > > Thanks, > > > > Dave > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > -- > Linux User: 255902 > > Please avoid sending me Word or PowerPoint attachments. > See http://www.fsf.org/philosophy/no-word-attachments.html > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- %<------------------------------------------------------->% Michel memeteau http://memeteau.free.fr Fixe : NOUVEAU NUMERO !! 0874763294 VOIP | Visio: sip:freechelmi at gizmoproject.com Mobile : 0624808051 jabber/GoogleTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.memeteau at gmail.com Thu Oct 18 08:03:03 2007 From: michel.memeteau at gmail.com (michel memeteau) Date: Thu, 18 Oct 2007 10:03:03 +0200 Subject: [Ekiga-list] land line users barely hear me In-Reply-To: References: Message-ID: Hi, Which SIP/H323 provider are you using ? diamoncard ? 2007/10/18, sam chan : > > > > hello all, > > using 500 at ekiga.net and Configuration Assistant, the > audio tests work fine. but people at the end of land > lines hear me at VERY low volume. and my voice often > breaks up frequently. it's practically useless. i > hear them just fine, however. > > my network bandwidth is fast enough(10mb down/1.5mb up). > > i don't know how well ekiga<->ekiga works since i don't > know anyone who has it. > > this is version 2.0.11 on Fedora 7. > > i have debug output at ftp://shell.sgi.com/collect/ekiga. > NOTE: you'll have to right-click and save the file. > > > thanks, > sam > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- %<------------------------------------------------------->% Michel memeteau http://memeteau.free.fr Fixe : NOUVEAU NUMERO !! 0874763294 VOIP | Visio: sip:freechelmi at gizmoproject.com Mobile : 0624808051 jabber/GoogleTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From schan at cs.ucr.edu Thu Oct 18 14:55:42 2007 From: schan at cs.ucr.edu (sam chan) Date: Thu, 18 Oct 2007 07:55:42 -0700 (PDT) Subject: [Ekiga-list] land line users barely hear me In-Reply-To: References: Message-ID: Michel, i'm not using a provider currently. i'm calling just toll-free numbers. eg, tele-conferencing numbers. thanks, sam On Thu, 18 Oct 2007, michel memeteau wrote: > Hi, Which SIP/H323 provider are you using ? diamoncard ? > > 2007/10/18, sam chan : >> >> >> >> hello all, >> >> using 500 at ekiga.net and Configuration Assistant, the >> audio tests work fine. but people at the end of land >> lines hear me at VERY low volume. and my voice often >> breaks up frequently. it's practically useless. i >> hear them just fine, however. >> >> my network bandwidth is fast enough(10mb down/1.5mb up). >> >> i don't know how well ekiga<->ekiga works since i don't >> know anyone who has it. >> >> this is version 2.0.11 on Fedora 7. >> >> i have debug output at ftp://shell.sgi.com/collect/ekiga. >> NOTE: you'll have to right-click and save the file. >> >> >> thanks, >> sam >> >> >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> > > > > From blasco.bonito at gmail.com Thu Oct 18 16:52:35 2007 From: blasco.bonito at gmail.com (Antonio-Blasco Bonito) Date: Thu, 18 Oct 2007 18:52:35 +0200 Subject: [Ekiga-list] registration failed using wireless lan Message-ID: Ekiga 2.0.11 on Ubuntu 7.10 Gutsy on MacBook I'm experiencing the following: when I use wired ethernet ekiga registers instantly, but when I use wireless connection it always says registration failed. I run the wizard for both types of network connection and it always gives no nat. The wireless connection works perfectly for any other application I use. Please help -- Antonio-Blasco Bonito Via Vico Fiaschi 35 54033 Carrara Avenza MS -------------- next part -------------- An HTML attachment was scrubbed... URL: From hunteke at earlham.edu Fri Oct 19 14:07:04 2007 From: hunteke at earlham.edu (Kevin Hunter) Date: Fri, 19 Oct 2007 10:07:04 -0400 Subject: [Ekiga-list] registration failed using wireless lan In-Reply-To: References: Message-ID: <4718BA08.9080807@earlham.edu> Antonio-Blasco Bonito wrote, On 10/18/2007 12:52 PM: > Ekiga 2.0.11 on Ubuntu 7.10 Gutsy on MacBook > > I'm experiencing the following: when I use wired ethernet ekiga registers > instantly, but when I use wireless connection it always says registration > failed. > I run the wizard for both types of network connection and it always gives no > nat. > The wireless connection works perfectly for any other application I use. I ran into something similar recently, I think. You may need to select which interface you want Ekiga to use: Edit->Preferences->Network Settings->Listen on (Dropdown combo box) Kevin From xlyz at fastwebnet.it Sun Oct 21 09:36:42 2007 From: xlyz at fastwebnet.it (xlyz) Date: Sun, 21 Oct 2007 11:36:42 +0200 Subject: [Ekiga-list] ekiga slow to connect Message-ID: <1192959402.6580.8.camel@xmachine> every time that i call with ekiga, it needs several seconds (at least 20-30) before establishing a connection. it just stay frozen. other software (e.g. linphone) on the same pc do not have problems. here you can find a log @ -d 4 http://paste.ubuntu-nl.org/41487/ I launched ekiga, wait for it to connect to ekiga.net, dialed to 500 at ekiga.net (at 11:28:30), once I got the line (I just heard the last bit of the registered message) said one word or two, hanged up, exit ekiga. ekiga is 2.0.11 in ubuntu 7.10 (but had the same problem with 7.04) xlyz From xlyz at fastwebnet.it Sun Oct 21 10:45:08 2007 From: xlyz at fastwebnet.it (xlyz) Date: Sun, 21 Oct 2007 12:45:08 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1192959402.6580.8.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> Message-ID: <1192963508.6580.11.camel@xmachine> new log: http://paste.ubuntu-nl.org/41498/ xlyz Il giorno dom, 21/10/2007 alle 11.36 +0200, xlyz ha scritto: > every time that i call with ekiga, it needs several seconds (at least 20-30) > before establishing a connection. it just stay frozen. other software > (e.g. linphone) on the same pc do not have problems. > > here you can find a log @ -d 4 > > http://paste.ubuntu-nl.org/41487/ > > I launched ekiga, wait for it to connect to ekiga.net, dialed to 500 at ekiga.net (at 11:28:30), once I got the line (I just heard the last bit of the registered message) said one word or two, hanged up, exit ekiga. > > ekiga is 2.0.11 in ubuntu 7.10 (but had the same problem with 7.04) > > xlyz > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From dsandras at seconix.com Sun Oct 21 14:36:16 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Oct 2007 16:36:16 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1192963508.6580.11.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> Message-ID: <1192977376.7807.3.camel@scorpion> Hi, Le dimanche 21 octobre 2007 ? 12:45 +0200, xlyz a ?crit : > new log: > > http://paste.ubuntu-nl.org/41498/ > The problem is the 20 seconds gap between lines 169 and 170. No way to know why it happens without executing ekiga step by step inside gdb unfortunately :( -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From xlyz at fastwebnet.it Sun Oct 21 14:56:46 2007 From: xlyz at fastwebnet.it (xlyz) Date: Sun, 21 Oct 2007 16:56:46 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1192977376.7807.3.camel@scorpion> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> Message-ID: <1192978606.6580.15.camel@xmachine> Il giorno dom, 21/10/2007 alle 16.36 +0200, Damien Sandras ha scritto: > The problem is the 20 seconds gap between lines 169 and 170. > > No way to know why it happens without executing ekiga step by step > inside gdb unfortunately :( if you can give me direction I'll be happy to do it. xlyz From dsandras at seconix.com Sun Oct 21 15:10:25 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Oct 2007 17:10:25 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1192978606.6580.15.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> Message-ID: <1192979425.7807.8.camel@scorpion> Le dimanche 21 octobre 2007 ? 16:56 +0200, xlyz a ?crit : > Il giorno dom, 21/10/2007 alle 16.36 +0200, Damien Sandras ha scritto: > > > The problem is the 20 seconds gap between lines 169 and 170. > > > > No way to know why it happens without executing ekiga step by step > > inside gdb unfortunately :( > > if you can give me direction I'll be happy to do it. > If you edit src/sip/sipcon.cxx, BOOL SIPConnection::SetUpConnection(), you will see the following : PTRACE(2, "SIP\tSetUpConnection: " << remotePartyAddress); After that, it takes 20 seconds until the next step. Perhaps it is the DNS SRV lookup that takes so long ? You can monitor that, the easiest if you are not used doing that, is probably to add something like this at various places: std::cout << "Hey 1" << std::endl << std::flush; You will be able to see what takes time, -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From arsphl at davidbowie.com Sun Oct 21 18:20:10 2007 From: arsphl at davidbowie.com (Philippe Laliberte) Date: Sun, 21 Oct 2007 19:20:10 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471667E1.6090302@googlemail.com> References: <471667E1.6090302@googlemail.com> Message-ID: <471B985A.90306@davidbowie.com> Hello, I am running into a little problem. I did dig into the wiki but to no avail. Set-up: Fedora 7. kernel-2.6.22.9 Firewall disabled. selinux disabled Ekiga 2.0.11 Router Modem ADSL SpeedTouch 780 Firewall disabled (once I get Ekiga working I'll test what I can close) VoIp turned off Modem routing Configuration Protocol Port Range Translate To ... Trigger Protocol Trigger Port Any 5000 - 5100 5000 - 5100 - - UDP 3479 - 3479 3479 - 3479 UDP 3479 UDP 3478 - 3479 3478 - 3479 UDP 3478 Nat detection always Symetric. Symptoms: Test in STUN: Calls to 500 at ekiga.net No audio in. Calls to my public phone number at diamoncard, from a normal phone, if routed through sip/arsphl at ekiga.net reach me, No Audio in Ekiga. Calls to public number at diamoncard, from a normal phone, route to IP Phone do not reach me at all. Test in None Calls to 500 at ekiga.net OK Calls to my public phone number at diamoncard, from a normal phone, if routed through sip/arsphl at ekiga.net reach me, but are in Abnormal termination as soon as I accept them. Calls to public number at diamoncard, from a normal phone, routed to IP Phone do not reach me at all. Other factors: I wondered if it could be linked to the timeout, but files given in the Wiki do not exists. find /proc/sys/net/ipv4/ -name "*timeout*" /proc/sys/net/ipv4/tcp_fin_timeout /proc/sys/net/ipv4/route/gc_timeout So I changed the timeout of the accounts to 179. It works, on start-up of Ekiga. I let it dry a little (15 mins) then it all falls apart again. So it seems that it is related to time outs, but without the ipv4 files I am a bit lost as to where to look for a kernel level solution. Should I setup ip.conntrack.udp.timeout=3600 and ip.conntrack.udp.timeout.stream=3600 in sysctl.conf? Cheers, Philippe -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 171 bytes Desc: not available URL: From dsandras at seconix.com Sun Oct 21 18:56:12 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Oct 2007 20:56:12 +0200 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471B985A.90306@davidbowie.com> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> Message-ID: <1192992972.4179.1.camel@scorpion> Hi, Le dimanche 21 octobre 2007 ? 19:20 +0100, Philippe Laliberte a ?crit : > Hello, > > I am running into a little problem. I did dig into the wiki but to no avail. > > Set-up: > > Fedora 7. > kernel-2.6.22.9 > Firewall disabled. selinux disabled > Ekiga 2.0.11 > > Router Modem ADSL SpeedTouch 780 > Firewall disabled (once I get Ekiga working I'll test what I can close) > VoIp turned off > > Modem routing Configuration > > Protocol Port Range Translate To ... Trigger Protocol > Trigger Port > Any 5000 - 5100 5000 - 5100 - > - > UDP 3479 - 3479 3479 - 3479 UDP > 3479 > UDP 3478 - 3479 3478 - 3479 UDP > 3478 > > Nat detection always Symetric. > That's the cause of your problem. Are you sure port are correctly forwarded ? Are you sure your router does not have SIP conntracking (in which case you could disable STUN and port forwarding alltogether). -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From law_ence.dev at ntlworld.com Sun Oct 21 19:09:11 2007 From: law_ence.dev at ntlworld.com (ael) Date: Sun, 21 Oct 2007 20:09:11 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471B985A.90306@davidbowie.com> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> Message-ID: <471BA3D7.7060805@ntlworld.com> Philippe Laliberte wrote: > Hello, > > I am running into a little problem. I did dig into the wiki but to no > avail. > > Set-up: > > Fedora 7. > kernel-2.6.22.9 > Firewall disabled. selinux disabled > Ekiga 2.0.11 > > Router Modem ADSL SpeedTouch 780 > Firewall disabled (once I get Ekiga working I'll test what I can close) > VoIp turned off > > Modem routing Configuration > > Protocol Port Range Translate To ... Trigger Protocol > Trigger Port Any 5000 - 5100 5000 - 5100 > - - > UDP 3479 - 3479 3479 - 3479 UDP > 3479 > UDP 3478 - 3479 3478 - 3479 UDP > 3478 I can't quite decode the above. If you trigger on 3478 (UDP) and then open 5000 -5100 (UDP) then it should be ok. I am not sure that is what you have above is it? I can't make out the first line ending in 5000-5100: how does that relate to the two following lines? ael From arsphl at davidbowie.com Sun Oct 21 19:17:35 2007 From: arsphl at davidbowie.com (Philippe Laliberte) Date: Sun, 21 Oct 2007 20:17:35 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <1192992972.4179.1.camel@scorpion> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <1192992972.4179.1.camel@scorpion> Message-ID: <471BA5CF.7020000@davidbowie.com> An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: spacer.gif Type: image/gif Size: 43 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ll04__md.gif Type: image/gif Size: 261 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: ll07__md.gif Type: image/gif Size: 256 bytes Desc: not available URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 179 bytes Desc: not available URL: From louis.ramel at wanadoo.fr Sun Oct 21 19:49:37 2007 From: louis.ramel at wanadoo.fr (Louis RAMEL) Date: Sun, 21 Oct 2007 21:49:37 +0200 Subject: [Ekiga-list] french list Message-ID: <200710212149.37562.louis.ramel@wanadoo.fr> hello due to my poor english where can y find help for ekiga in french. Thanks -- -- Louis RAMEL From svesmeralda at gmail.com Sun Oct 21 20:35:30 2007 From: svesmeralda at gmail.com (jim barber) Date: Sun, 21 Oct 2007 14:35:30 -0600 Subject: [Ekiga-list] Will not connect to test call Message-ID: <1192998930.7854.8.camel@sv-esmeralda> I reregistered to Ekiga and did it properly this time. The test call during the set up went well. I tried the test call after the setup was complete and it failed to connect to it and there is not record of the call in the call history. In the URL box I had entered: sip:500 at ekiga.net I also just upgraded the computer to Ubuntu 7.10 before reregistering with Ekiga. Any ideas on the problem will be greatly appreciated. Thanks, Jim aboard Esmeralda Mexico From marcel.dess at gmail.com Sun Oct 21 20:50:49 2007 From: marcel.dess at gmail.com (marcel.dess) Date: Sun, 21 Oct 2007 16:50:49 -0400 Subject: [Ekiga-list] french list In-Reply-To: <200710212149.37562.louis.ramel@wanadoo.fr> References: <200710212149.37562.louis.ramel@wanadoo.fr> Message-ID: <471BBBA9.7030309@gmail.com> Louis RAMEL a ?crit : > hello > due to my poor english where can y find help for ekiga in french. > Thanks > Bonjour Sur Ubuntu-Fr (gracieuset? de Yannick) http://doc.ubuntu-fr.org/ekiga From xlyz at fastwebnet.it Sun Oct 21 21:17:29 2007 From: xlyz at fastwebnet.it (xlyz) Date: Sun, 21 Oct 2007 23:17:29 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1192979425.7807.8.camel@scorpion> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> Message-ID: <1193001449.20115.3.camel@xmachine> > If you edit src/sip/sipcon.cxx, BOOL SIPConnection::SetUpConnection(), > you will see the following : > PTRACE(2, "SIP\tSetUpConnection: " << remotePartyAddress); > After that, it takes 20 seconds until the next step. > > Perhaps it is the DNS SRV lookup that takes so long ? > > You can monitor that, the easiest if you are not used doing that, is > probably to add something like this at various places: > std::cout << "Hey 1" << std::endl << std::flush; > > You will be able to see what takes time, I hoped was something simpler do you think that if I capture network traffic instead you can understand where is the problem? From dsandras at seconix.com Sun Oct 21 21:22:51 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Oct 2007 23:22:51 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193001449.20115.3.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> Message-ID: <1193001771.27017.0.camel@scorpion> Le dimanche 21 octobre 2007 ? 23:17 +0200, xlyz a ?crit : > > If you edit src/sip/sipcon.cxx, BOOL SIPConnection::SetUpConnection(), > > you will see the following : > > PTRACE(2, "SIP\tSetUpConnection: " << remotePartyAddress); > > After that, it takes 20 seconds until the next step. > > > > Perhaps it is the DNS SRV lookup that takes so long ? > > > > You can monitor that, the easiest if you are not used doing that, is > > probably to add something like this at various places: > > std::cout << "Hey 1" << std::endl << std::flush; > > > > You will be able to see what takes time, > > I hoped was something simpler > > do you think that if I capture network traffic instead you can > understand where is the problem? I don't think so... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sun Oct 21 21:23:31 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 21 Oct 2007 23:23:31 +0200 Subject: [Ekiga-list] Will not connect to test call In-Reply-To: <1192998930.7854.8.camel@sv-esmeralda> References: <1192998930.7854.8.camel@sv-esmeralda> Message-ID: <1193001811.27017.2.camel@scorpion> Le dimanche 21 octobre 2007 ? 14:35 -0600, jim barber a ?crit : > I reregistered to Ekiga and did it properly this time. The test call > during the set up went well. I tried the test call after the setup was > complete and it failed to connect to it and there is not record of the > call in the call history. In the URL box I had entered: > sip:500 at ekiga.net > > I also just upgraded the computer to Ubuntu 7.10 before reregistering > with Ekiga. > > Any ideas on the problem will be greatly appreciated. Please post a full -d 4 output somewhere. Thanks. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From xlyz at fastwebnet.it Sun Oct 21 21:37:59 2007 From: xlyz at fastwebnet.it (xlyz) Date: Sun, 21 Oct 2007 23:37:59 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193001771.27017.0.camel@scorpion> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> <1193001771.27017.0.camel@scorpion> Message-ID: <1193002679.20115.15.camel@xmachine> btw, installing ekiga in a different OS in a virtualbox in ubuntu on the same pc (the beta 2.0.11 exe on ekiga.org) works with no delay at all, in spite of being natted twice (once by the router and once by the virtual network of virtualbox) I'll try to follow your rqst. Just to be sure: something like this is correct: ============================================ BOOL SIPConnection::SetUpConnection() { SIPURL transportAddress = targetAddress; PTRACE(2, "SIP\tSetUpConnection: " << remotePartyAddress); // Do a DNS SRV lookup #if P_DNS PIPSocketAddressAndPortVector addrs; std::cout << "Hey 1" << std::endl << std::flush; if (PDNS::LookupSRV(targetAddress.GetHostName(), "_sip._udp", targetAddress.GetPort(), addrs)) { transportAddress.SetHostName(addrs[0].address.AsString()); std::cout << "Hey 2" << std::endl << std::flush; transportAddress.SetPort(addrs [0].port); } #endif PStringList routeSet = GetRouteSet(); std::cout << "Hey 3" << std::endl << std::flush; ======================================================= xlyz Il giorno dom, 21/10/2007 alle 23.22 +0200, Damien Sandras ha scritto: > Le dimanche 21 octobre 2007 ? 23:17 +0200, xlyz a ?crit : > > > If you edit src/sip/sipcon.cxx, BOOL SIPConnection::SetUpConnection(), > > > you will see the following : > > > PTRACE(2, "SIP\tSetUpConnection: " << remotePartyAddress); > > > After that, it takes 20 seconds until the next step. > > > > > > Perhaps it is the DNS SRV lookup that takes so long ? > > > > > > You can monitor that, the easiest if you are not used doing that, is > > > probably to add something like this at various places: > > > std::cout << "Hey 1" << std::endl << std::flush; > > > > > > You will be able to see what takes time, > > > > I hoped was something simpler > > > > do you think that if I capture network traffic instead you can > > understand where is the problem? > > I don't think so... > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From geno999 at yahoo.com Mon Oct 22 00:32:02 2007 From: geno999 at yahoo.com (J. Rehbock) Date: Sun, 21 Oct 2007 17:32:02 -0700 (PDT) Subject: [Ekiga-list] Quickcam Orbit AF Message-ID: <404392.24860.qm@web33801.mail.mud.yahoo.com> This camera looks attractive because it has both autofocus capability and a Carl Zeiss lens. I'm assuming it uses the Linux UVC driver since a predecessor Orbit camera does. What experiences (especially problems) have people had with THIS SPECIFIC CAMERA while running Ekiga under Linux. Tnx. Geno -------------- next part -------------- An HTML attachment was scrubbed... URL: From geno999 at yahoo.com Mon Oct 22 02:55:29 2007 From: geno999 at yahoo.com (J. Rehbock) Date: Sun, 21 Oct 2007 19:55:29 -0700 (PDT) Subject: [Ekiga-list] Quickcam Pro 9000 Message-ID: <928331.64436.qm@web33810.mail.mud.yahoo.com> Of the three webcams I've looked into recently, this one seems to have the best prospects for working decently with the Linux UVC driver. Does anyone have any practical experience with it using Ekiga under Linux? Does the autofocus work under Linux? Tnx. Geno -------------- next part -------------- An HTML attachment was scrubbed... URL: From dsandras at seconix.com Mon Oct 22 07:22:49 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Oct 2007 09:22:49 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193002679.20115.15.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> <1193001771.27017.0.camel@scorpion> <1193002679.20115.15.camel@xmachine> Message-ID: <1193037769.4186.0.camel@scorpion> Le dimanche 21 octobre 2007 ? 23:37 +0200, xlyz a ?crit : > btw, installing ekiga in a different OS in a virtualbox in ubuntu on the > same pc (the beta 2.0.11 exe on ekiga.org) works with no delay at all, > in spite of being natted twice (once by the router and once by the > virtual network of virtualbox) Something wrong on the native machine in that case. > I'll try to follow your rqst. > > Just to be sure: something like this is correct: > Yes I confirm... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From xlyz at fastwebnet.it Mon Oct 22 09:19:20 2007 From: xlyz at fastwebnet.it (xlyz) Date: Mon, 22 Oct 2007 11:19:20 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193037769.4186.0.camel@scorpion> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> <1193001771.27017.0.camel@scorpion> <1193002679.20115.15.camel@xmachine> <1193037769.4186.0.camel@scorpion> Message-ID: <1193044761.12410.3.camel@xmachine> here is the source modified: http://paste.ubuntu-nl.org/41663/ here the new log: http://paste.ubuntu-nl.org/41665/ added comments does not have timestamp, but most of the delay was beetween "hey 2" and "hey 6" xlyz Il giorno lun, 22/10/2007 alle 09.22 +0200, Damien Sandras ha scritto: > Le dimanche 21 octobre 2007 ? 23:37 +0200, xlyz a ?crit : > > btw, installing ekiga in a different OS in a virtualbox in ubuntu on the > > same pc (the beta 2.0.11 exe on ekiga.org) works with no delay at all, > > in spite of being natted twice (once by the router and once by the > > virtual network of virtualbox) > > > Something wrong on the native machine in that case. > > > I'll try to follow your rqst. > > > > Just to be sure: something like this is correct: > > > > Yes I confirm... > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From dsandras at seconix.com Mon Oct 22 09:31:34 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Oct 2007 11:31:34 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193044761.12410.3.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> <1193001771.27017.0.camel@scorpion> <1193002679.20115.15.camel@xmachine> <1193037769.4186.0.camel@scorpion> <1193044761.12410.3.camel@xmachine> Message-ID: <1193045494.4186.9.camel@scorpion> Le lundi 22 octobre 2007 ? 11:19 +0200, xlyz a ?crit : > here is the source modified: > > http://paste.ubuntu-nl.org/41663/ > > here the new log: > > http://paste.ubuntu-nl.org/41665/ > > added comments does not have timestamp, but most of the delay was > beetween "hey 2" and "hey 6" > Using PTRACE would have given comments, but your conclusion confirms what I was thinking. When doing a call over SIP, you have two ways to determine the IP address of the remote peer : - normal A Record Lookup - SRV Record Lookup The portion of code you have commented is doing a SRV Record. There is a limitation in Ekiga 2.xx: SRV lookups are done when it is not needed. This is what happens here. However, it is not normal to spend so much time on that lookup. It indicates a problem on your DNS server. Can you double-check /etc/resolv.conf on the machine on which you have a delay and on the machine that works correctly ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From law_ence.dev at ntlworld.com Mon Oct 22 10:43:13 2007 From: law_ence.dev at ntlworld.com (ael) Date: Mon, 22 Oct 2007 11:43:13 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471BA6CB.8020400@aqiii.org> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <471BA3D7.7060805@ntlworld.com> <471BA6CB.8020400@aqiii.org> Message-ID: <471C7EC1.1070102@ntlworld.com> P laliberte wrote: > ael wrote: >> Philippe Laliberte wrote: >> >>> Hello, >>> >>> I am running into a little problem. I did dig into the wiki but to no >>> avail. >>> >>> Set-up: >>> >>> Fedora 7. >>> kernel-2.6.22.9 >>> Firewall disabled. selinux disabled >>> Ekiga 2.0.11 >>> >>> Router Modem ADSL SpeedTouch 780 >>> Firewall disabled (once I get Ekiga working I'll test what I can close) >>> VoIp turned off >>> >>> Modem routing Configuration >>> >>> Protocol Port Range Translate To ... Trigger Protocol >>> Trigger Port Any 5000 - 5100 5000 - 5100 >>> - - >>> UDP 3479 - 3479 3479 - 3479 >>> UDP 3479 >>> UDP 3478 - 3479 3478 - 3479 >>> UDP 3478 >>> >> >> I can't quite decode the above. If you trigger on 3478 (UDP) and then >> open 5000 -5100 (UDP) then it should be ok. I am not sure that is what >> you have above is it? I can't make out the first line ending in >> 5000-5100: how does that relate to the two following lines? >> >> ael >> _______________________________________________ >> ekiga-list mailing list >> ekiga-list at gnome.org >> http://mail.gnome.org/mailman/listinfo/ekiga-list >> > > Just missing a cariage return > > Protocol Port Range Translate To ... Trigger Protocol Trigger > Port Any 5000 - 5100 5000 - 5100 - - > UDP 3479 - 3479 3479 - 3479 UDP 3479 > UDP 3478 - 3479 3478 - 3479 UDP 3478 > > > What you mean is that I should just do : > > UDP 5000 - 5100 3479 - 3479 UDP 3479 > UDP 5100 - 5100 3478 - 3479 UDP 3478 Looking at that again, why are you translating 3479 into 5000-5100? Or am I misunderstanding the web interface (I assume)? Once you see a packet on 3478, then open 5000-5100. Do not translate 3478 into 5000... if that is what the above means. 3478 and 3479 should be (con) tracked properly by the router. It is just that it will block 5000-5100 unless it is told otherwise. I have not encountered a SpeedTouch router so I may be misunderstanding its configuration. ael From arsphl at davidbowie.com Mon Oct 22 10:52:59 2007 From: arsphl at davidbowie.com (Philippe Laliberte) Date: Mon, 22 Oct 2007 11:52:59 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471C7EC1.1070102@ntlworld.com> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <471BA3D7.7060805@ntlworld.com> <471BA6CB.8020400@aqiii.org> <471C7EC1.1070102@ntlworld.com> Message-ID: <471C810B.8060304@davidbowie.com> ael wrote: > P laliberte wrote: > >> ael wrote: >> >>> Philippe Laliberte wrote: >>> >>> >>>> Hello, >>>> >>>> I am running into a little problem. I did dig into the wiki but to no >>>> avail. >>>> >>>> Set-up: >>>> >>>> Fedora 7. >>>> kernel-2.6.22.9 >>>> Firewall disabled. selinux disabled >>>> Ekiga 2.0.11 >>>> >>>> Router Modem ADSL SpeedTouch 780 >>>> Firewall disabled (once I get Ekiga working I'll test what I can close) >>>> VoIp turned off >>>> >>>> Modem routing Configuration >>>> >>>> Protocol Port Range Translate To ... Trigger Protocol >>>> Trigger Port Any 5000 - 5100 5000 - 5100 >>>> - - >>>> UDP 3479 - 3479 3479 - 3479 >>>> UDP 3479 >>>> UDP 3478 - 3479 3478 - 3479 >>>> UDP 3478 >>>> >>>> >>> I can't quite decode the above. If you trigger on 3478 (UDP) and then >>> open 5000 -5100 (UDP) then it should be ok. I am not sure that is what >>> you have above is it? I can't make out the first line ending in >>> 5000-5100: how does that relate to the two following lines? >>> >>> ael >>> _______________________________________________ >>> ekiga-list mailing list >>> ekiga-list at gnome.org >>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>> >>> >> Just missing a cariage return >> >> Protocol Port Range Translate To ... Trigger Protocol Trigger >> Port Any 5000 - 5100 5000 - 5100 - - >> UDP 3479 - 3479 3479 - 3479 UDP 3479 >> UDP 3478 - 3479 3478 - 3479 UDP 3478 >> >> >> What you mean is that I should just do : >> >> UDP 5000 - 5100 3479 - 3479 UDP 3479 >> UDP 5100 - 5100 3478 - 3479 UDP 3478 >> > > Looking at that again, why are you translating 3479 into 5000-5100? Or > am I misunderstanding the web interface (I assume)? > > Once you see a packet on 3478, then open 5000-5100. Do not translate > 3478 into 5000... if that is what the above means. 3478 and 3479 should > be (con) tracked properly by the router. It is just that it will block > 5000-5100 unless it is told otherwise. > > I have not encountered a SpeedTouch router so I may be misunderstanding > its configuration. > > ael > The error is mine, late doing too many thing at the same time. You did understand it correctly the first time. UDP 5000 - 5100 5000 - 5100 UDP 3479 UDP 5100 - 5100 5000 - 5100 UDP 3478 I'll test it later this afternoon thanks. Cheers, Philippe -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 207 bytes Desc: not available URL: From dsandras at seconix.com Mon Oct 22 10:55:41 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Oct 2007 12:55:41 +0200 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471C810B.8060304@davidbowie.com> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <471BA3D7.7060805@ntlworld.com> <471BA6CB.8020400@aqiii.org> <471C7EC1.1070102@ntlworld.com> <471C810B.8060304@davidbowie.com> Message-ID: <1193050541.1674.7.camel@scorpion> Le lundi 22 octobre 2007 ? 11:52 +0100, Philippe Laliberte a ?crit : > ael wrote: > > P laliberte wrote: > > > > > ael wrote: > > > > > > > Philippe Laliberte wrote: > > > > > > > > > > > > > Hello, > > > > > > > > > > I am running into a little problem. I did dig into the wiki but to no > > > > > avail. > > > > > > > > > > Set-up: > > > > > > > > > > Fedora 7. > > > > > kernel-2.6.22.9 > > > > > Firewall disabled. selinux disabled > > > > > Ekiga 2.0.11 > > > > > > > > > > Router Modem ADSL SpeedTouch 780 > > > > > Firewall disabled (once I get Ekiga working I'll test what I can close) > > > > > VoIp turned off > > > > > > > > > > Modem routing Configuration > > > > > > > > > > Protocol Port Range Translate To ... Trigger Protocol > > > > > Trigger Port Any 5000 - 5100 5000 - 5100 > > > > > - - > > > > > UDP 3479 - 3479 3479 - 3479 > > > > > UDP 3479 > > > > > UDP 3478 - 3479 3478 - 3479 > > > > > UDP 3478 > > > > > > > > > > > > > > I can't quite decode the above. If you trigger on 3478 (UDP) and then > > > > open 5000 -5100 (UDP) then it should be ok. I am not sure that is what > > > > you have above is it? I can't make out the first line ending in > > > > 5000-5100: how does that relate to the two following lines? > > > > > > > > ael > > > > _______________________________________________ > > > > ekiga-list mailing list > > > > ekiga-list at gnome.org > > > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > > > > > > > > > Just missing a cariage return > > > > > > Protocol Port Range Translate To ... Trigger Protocol Trigger > > > Port Any 5000 - 5100 5000 - 5100 - - > > > UDP 3479 - 3479 3479 - 3479 UDP 3479 > > > UDP 3478 - 3479 3478 - 3479 UDP 3478 > > > > > > > > > What you mean is that I should just do : > > > > > > UDP 5000 - 5100 3479 - 3479 UDP 3479 > > > UDP 5100 - 5100 3478 - 3479 UDP 3478 > > > > > > > Looking at that again, why are you translating 3479 into 5000-5100? Or > > am I misunderstanding the web interface (I assume)? > > > > Once you see a packet on 3478, then open 5000-5100. Do not translate > > 3478 into 5000... if that is what the above means. 3478 and 3479 should > > be (con) tracked properly by the router. It is just that it will block > > 5000-5100 unless it is told otherwise. > > > > I have not encountered a SpeedTouch router so I may be misunderstanding > > its configuration. > > > > ael > > > The error is mine, late doing too many thing at the same time. You did > understand it correctly the first time. > > UDP 5000 - 5100 5000 - 5100 UDP 3479 > UDP 5100 - 5100 5000 - 5100 UDP 3478 > I'll test it later this afternoon thanks. > Why 5100 - 5100 ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From arsphl at davidbowie.com Mon Oct 22 13:19:05 2007 From: arsphl at davidbowie.com (Philippe Laliberte) Date: Mon, 22 Oct 2007 14:19:05 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <1193050541.1674.7.camel@scorpion> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <471BA3D7.7060805@ntlworld.com> <471BA6CB.8020400@aqiii.org> <471C7EC1.1070102@ntlworld.com> <471C810B.8060304@davidbowie.com> <1193050541.1674.7.camel@scorpion> Message-ID: <471CA349.4040209@davidbowie.com> Damien Sandras wrote: > Le lundi 22 octobre 2007 ? 11:52 +0100, Philippe Laliberte a ?crit : > >> ael wrote: >> >>> P laliberte wrote: >>> >>> >>>> ael wrote: >>>> >>>> >>>>> Philippe Laliberte wrote: >>>>> >>>>> >>>>> >>>>>> Hello, >>>>>> >>>>>> I am running into a little problem. I did dig into the wiki but to no >>>>>> avail. >>>>>> >>>>>> Set-up: >>>>>> >>>>>> Fedora 7. >>>>>> kernel-2.6.22.9 >>>>>> Firewall disabled. selinux disabled >>>>>> Ekiga 2.0.11 >>>>>> >>>>>> Router Modem ADSL SpeedTouch 780 >>>>>> Firewall disabled (once I get Ekiga working I'll test what I can close) >>>>>> VoIp turned off >>>>>> >>>>>> Modem routing Configuration >>>>>> >>>>>> Protocol Port Range Translate To ... Trigger Protocol >>>>>> Trigger Port Any 5000 - 5100 5000 - 5100 >>>>>> - - >>>>>> UDP 3479 - 3479 3479 - 3479 >>>>>> UDP 3479 >>>>>> UDP 3478 - 3479 3478 - 3479 >>>>>> UDP 3478 >>>>>> >>>>>> >>>>>> >>>>> I can't quite decode the above. If you trigger on 3478 (UDP) and then >>>>> open 5000 -5100 (UDP) then it should be ok. I am not sure that is what >>>>> you have above is it? I can't make out the first line ending in >>>>> 5000-5100: how does that relate to the two following lines? >>>>> >>>>> ael >>>>> _______________________________________________ >>>>> ekiga-list mailing list >>>>> ekiga-list at gnome.org >>>>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>>>> >>>>> >>>>> >>>> Just missing a cariage return >>>> >>>> Protocol Port Range Translate To ... Trigger Protocol Trigger >>>> Port Any 5000 - 5100 5000 - 5100 - - >>>> UDP 3479 - 3479 3479 - 3479 UDP 3479 >>>> UDP 3478 - 3479 3478 - 3479 UDP 3478 >>>> >>>> >>>> What you mean is that I should just do : >>>> >>>> UDP 5000 - 5100 3479 - 3479 UDP 3479 >>>> UDP 5100 - 5100 3478 - 3479 UDP 3478 >>>> >>>> >>> Looking at that again, why are you translating 3479 into 5000-5100? Or >>> am I misunderstanding the web interface (I assume)? >>> >>> Once you see a packet on 3478, then open 5000-5100. Do not translate >>> 3478 into 5000... if that is what the above means. 3478 and 3479 should >>> be (con) tracked properly by the router. It is just that it will block >>> 5000-5100 unless it is told otherwise. >>> >>> I have not encountered a SpeedTouch router so I may be misunderstanding >>> its configuration. >>> >>> ael >>> >>> >> The error is mine, late doing too many thing at the same time. You did >> understand it correctly the first time. >> >> UDP 5000 - 5100 5000 - 5100 UDP 3479 >> UDP 5100 - 5100 5000 - 5100 UDP 3478 >> I'll test it later this afternoon thanks. >> >> > > Why 5100 - 5100 ? > > Well unconclusive: UDP 5000 - 5100 5000 - 5100 UDP 3479 UDP 5000 - 5100 5000 - 5100 UDP 3478 Wizard, still in symetric NAT Manual STUN: No sound on 500 at ekiga.net, no calls in from Diamoncard even after a fresh restart None: 500 at ekiga.net ok, no calls in from Diamoncard even after a fresh restart. Back to no trigger definition, same as above. Back to TCP/UDP Any 5000 - 5100 5000 - 5100 Any 3478 Any 5000 - 5100 5000 - 5100 Any 3479 Wizard, still in symetric NAT STUN: No sound on 500 at ekiga.net, Calls in from Diamoncard OK even after a while, after manual changes back and forth it does not work anymore None: 500 at ekiga.net ok, no calls in from Diamoncard even after a fresh restart. Back to no trigger definition, same as above. Wireshark shows SIP activity for the 500 at ekiga call but nothing coming in from Diamoncard. Can all this working not working be related to a slowness from diamoncard or the router to react to changes? I am connected to eugw.ast.diamondcard.us. If I try to setup my VoIp on the modem, it never seems to register. I'll go back to STUN (with trigger of the router) and shutdown Ekiga for an hour or so to see if when I come back It will work. Cheers, Philippe -------------- next part -------------- A non-text attachment was scrubbed... Name: arsphl.vcf Type: text/x-vcard Size: 179 bytes Desc: not available URL: From dsandras at seconix.com Mon Oct 22 13:36:10 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Oct 2007 15:36:10 +0200 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471CA349.4040209@davidbowie.com> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <471BA3D7.7060805@ntlworld.com> <471BA6CB.8020400@aqiii.org> <471C7EC1.1070102@ntlworld.com> <471C810B.8060304@davidbowie.com> <1193050541.1674.7.camel@scorpion> <471CA349.4040209@davidbowie.com> Message-ID: <1193060170.1674.24.camel@scorpion> Le lundi 22 octobre 2007 ? 14:19 +0100, Philippe Laliberte a ?crit : > Damien Sandras wrote: > > Le lundi 22 octobre 2007 ? 11:52 +0100, Philippe Laliberte a ?crit : > > > >> ael wrote: > >> > >>> P laliberte wrote: > >>> > >>> > >>>> ael wrote: > >>>> > >>>> > >>>>> Philippe Laliberte wrote: > >>>>> > >>>>> > >>>>> > >>>>>> Hello, > >>>>>> > >>>>>> I am running into a little problem. I did dig into the wiki but to no > >>>>>> avail. > >>>>>> > >>>>>> Set-up: > >>>>>> > >>>>>> Fedora 7. > >>>>>> kernel-2.6.22.9 > >>>>>> Firewall disabled. selinux disabled > >>>>>> Ekiga 2.0.11 > >>>>>> > >>>>>> Router Modem ADSL SpeedTouch 780 > >>>>>> Firewall disabled (once I get Ekiga working I'll test what I can close) > >>>>>> VoIp turned off > >>>>>> > >>>>>> Modem routing Configuration > >>>>>> > >>>>>> Protocol Port Range Translate To ... Trigger Protocol > >>>>>> Trigger Port Any 5000 - 5100 5000 - 5100 > >>>>>> - - > >>>>>> UDP 3479 - 3479 3479 - 3479 > >>>>>> UDP 3479 > >>>>>> UDP 3478 - 3479 3478 - 3479 > >>>>>> UDP 3478 > >>>>>> > >>>>>> > >>>>>> > >>>>> I can't quite decode the above. If you trigger on 3478 (UDP) and then > >>>>> open 5000 -5100 (UDP) then it should be ok. I am not sure that is what > >>>>> you have above is it? I can't make out the first line ending in > >>>>> 5000-5100: how does that relate to the two following lines? > >>>>> > >>>>> ael > >>>>> _______________________________________________ > >>>>> ekiga-list mailing list > >>>>> ekiga-list at gnome.org > >>>>> http://mail.gnome.org/mailman/listinfo/ekiga-list > >>>>> > >>>>> > >>>>> > >>>> Just missing a cariage return > >>>> > >>>> Protocol Port Range Translate To ... Trigger Protocol Trigger > >>>> Port Any 5000 - 5100 5000 - 5100 - - > >>>> UDP 3479 - 3479 3479 - 3479 UDP 3479 > >>>> UDP 3478 - 3479 3478 - 3479 UDP 3478 > >>>> > >>>> > >>>> What you mean is that I should just do : > >>>> > >>>> UDP 5000 - 5100 3479 - 3479 UDP 3479 > >>>> UDP 5100 - 5100 3478 - 3479 UDP 3478 > >>>> > >>>> > >>> Looking at that again, why are you translating 3479 into 5000-5100? Or > >>> am I misunderstanding the web interface (I assume)? > >>> > >>> Once you see a packet on 3478, then open 5000-5100. Do not translate > >>> 3478 into 5000... if that is what the above means. 3478 and 3479 should > >>> be (con) tracked properly by the router. It is just that it will block > >>> 5000-5100 unless it is told otherwise. > >>> > >>> I have not encountered a SpeedTouch router so I may be misunderstanding > >>> its configuration. > >>> > >>> ael > >>> > >>> > >> The error is mine, late doing too many thing at the same time. You did > >> understand it correctly the first time. > >> > >> UDP 5000 - 5100 5000 - 5100 UDP 3479 > >> UDP 5100 - 5100 5000 - 5100 UDP 3478 > >> I'll test it later this afternoon thanks. > >> > >> > > > > Why 5100 - 5100 ? > > > > > > Well unconclusive: > > UDP 5000 - 5100 5000 - 5100 UDP 3479 > UDP 5000 - 5100 5000 - 5100 UDP 3478 > > > Wizard, still in symetric NAT > > Manual STUN: No sound on 500 at ekiga.net, no calls in from Diamoncard even > after a fresh restart > None: 500 at ekiga.net ok, no calls in from Diamoncard even after a fresh > restart. > > > Back to no trigger definition, same as above. > > Back to TCP/UDP > > Any 5000 - 5100 5000 - 5100 Any 3478 > Any 5000 - 5100 5000 - 5100 Any 3479 > > Wizard, still in symetric NAT > > STUN: No sound on 500 at ekiga.net, Calls in from Diamoncard OK even after > a while, after manual changes back and forth it does not work anymore > > None: 500 at ekiga.net ok, no calls in from Diamoncard even after a fresh > restart. > > Back to no trigger definition, same as above. > > Wireshark shows SIP activity for the 500 at ekiga call but nothing coming > in from Diamoncard. > > Can all this working not working be related to a slowness from > diamoncard or the router to react to changes? I am connected to > eugw.ast.diamondcard.us. If I try to setup my VoIp on the modem, it > never seems to register. > > I'll go back to STUN (with trigger of the router) and shutdown Ekiga for > an hour or so to see if when I come back It will work. > In my opinion, the problem lies in the configuration of your router. There is relatively few that we can do. If it detects symmetric NAT, that is probably because the port forwarding does not work appropriately. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From svesmeralda at gmail.com Mon Oct 22 17:56:57 2007 From: svesmeralda at gmail.com (jim barber) Date: Mon, 22 Oct 2007 11:56:57 -0600 Subject: [Ekiga-list] Will not connect to test call In-Reply-To: <1193001811.27017.2.camel@scorpion> References: <1192998930.7854.8.camel@sv-esmeralda> <1193001811.27017.2.camel@scorpion> Message-ID: <1193075817.5372.1.camel@sv-esmeralda> Damien, Thank you for the reply. Unfortunately I am not very knowledgeable about computers yet. I do not know what a -d 4 output is and where I would post it. Can you help on this? Jim Barber From law_ence.dev at ntlworld.com Mon Oct 22 19:57:48 2007 From: law_ence.dev at ntlworld.com (ael) Date: Mon, 22 Oct 2007 20:57:48 +0100 Subject: [Ekiga-list] Timeout? Call out OK call in from Diamon unseen or broken In-Reply-To: <471CA349.4040209@davidbowie.com> References: <471667E1.6090302@googlemail.com> <471B985A.90306@davidbowie.com> <471BA3D7.7060805@ntlworld.com> <471BA6CB.8020400@aqiii.org> <471C7EC1.1070102@ntlworld.com> <471C810B.8060304@davidbowie.com> <1193050541.1674.7.camel@scorpion> <471CA349.4040209@davidbowie.com> Message-ID: <471D00BC.1070801@ntlworld.com> Philippe Laliberte wrote: > Damien Sandras wrote: >> Le lundi 22 octobre 2007 ? 11:52 +0100, Philippe Laliberte a ?crit : >> >>> ael wrote: >>>> P laliberte wrote: >>>> >>>>> ael wrote: >>>>> >>>>>> Philippe Laliberte wrote: >>>>>> >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> I am running into a little problem. I did dig into the wiki but >>>>>>> to no >>>>>>> avail. >>>>>>> >>>>>>> Set-up: >>>>>>> >>>>>>> Fedora 7. >>>>>>> kernel-2.6.22.9 >>>>>>> Firewall disabled. selinux disabled >>>>>>> Ekiga 2.0.11 >>>>>>> >>>>>>> Router Modem ADSL SpeedTouch 780 >>>>>>> Firewall disabled (once I get Ekiga working I'll test what I can >>>>>>> close) >>>>>>> VoIp turned off >>>>>>> >>>>>>> Modem routing Configuration >>>>>>> >>>>>>> Protocol Port Range Translate To ... Trigger Protocol >>>>>>> Trigger Port Any 5000 - 5100 5000 - 5100 >>>>>>> - - >>>>>>> UDP 3479 - 3479 3479 - 3479 >>>>>>> UDP 3479 >>>>>>> UDP 3478 - 3479 3478 - 3479 >>>>>>> UDP 3478 >>>>>>> >>>>>> I can't quite decode the above. If you trigger on 3478 (UDP) and then >>>>>> open 5000 -5100 (UDP) then it should be ok. I am not sure that is >>>>>> what >>>>>> you have above is it? I can't make out the first line ending in >>>>>> 5000-5100: how does that relate to the two following lines? >>>>>> >>>>>> ael >>>>>> _______________________________________________ >>>>>> ekiga-list mailing list >>>>>> ekiga-list at gnome.org >>>>>> http://mail.gnome.org/mailman/listinfo/ekiga-list >>>>>> >>>>> Just missing a cariage return >>>>> >>>>> Protocol Port Range Translate To ... Trigger Protocol >>>>> Trigger >>>>> Port Any 5000 - 5100 5000 - 5100 - - >>>>> UDP 3479 - 3479 3479 - 3479 UDP 3479 >>>>> UDP 3478 - 3479 3478 - 3479 UDP 3478 >>>>> >>>>> >>>>> What you mean is that I should just do : >>>>> >>>>> UDP 5000 - 5100 3479 - 3479 UDP 3479 >>>>> UDP 5100 - 5100 3478 - 3479 UDP 3478 >>>>> >>>> Looking at that again, why are you translating 3479 into 5000-5100? Or >>>> am I misunderstanding the web interface (I assume)? >>>> >>>> Once you see a packet on 3478, then open 5000-5100. Do not translate >>>> 3478 into 5000... if that is what the above means. 3478 and 3479 should >>>> be (con) tracked properly by the router. It is just that it will block >>>> 5000-5100 unless it is told otherwise. >>>> >>>> I have not encountered a SpeedTouch router so I may be misunderstanding >>>> its configuration. >>>> >>>> ael >>>> >>> The error is mine, late doing too many thing at the same time. You did >>> understand it correctly the first time. >>> UDP 5000 - 5100 5000 - 5100 UDP 3479 >>> UDP 5100 - 5100 5000 - 5100 UDP 3478 >>> I'll test it later this afternoon thanks. >>> >>> >> >> Why 5100 - 5100 ? >> >> > > Well unconclusive: > > UDP 5000 - 5100 5000 - 5100 UDP 3479 > UDP 5000 - 5100 5000 - 5100 UDP 3478 > > > Wizard, still in symetric NAT > > Manual STUN: No sound on 500 at ekiga.net, no calls in from Diamoncard even > after a fresh restart > None: 500 at ekiga.net ok, no calls in from Diamoncard even after a fresh > restart. > > > Back to no trigger definition, same as above. > > Back to TCP/UDP > > Any 5000 - 5100 5000 - 5100 Any 3478 > Any 5000 - 5100 5000 - 5100 Any 3479 > > Wizard, still in symetric NAT > > STUN: No sound on 500 at ekiga.net, Calls in from Diamoncard OK even after > a while, after manual changes back and forth it does not work anymore > > None: 500 at ekiga.net ok, no calls in from Diamoncard even after a fresh > restart. > > Back to no trigger definition, same as above. > > Wireshark shows SIP activity for the 500 at ekiga call but nothing coming > in from Diamoncard. > > Can all this working not working be related to a slowness from > diamoncard or the router to react to changes? I am connected to > eugw.ast.diamondcard.us. If I try to setup my VoIp on the modem, it > never seems to register. > > I'll go back to STUN (with trigger of the router) and shutdown Ekiga for > an hour or so to see if when I come back It will work. You have looked at http://wiki.ekiga.org/index.php/Ekiga_behind_a_NAT_router , I assume? ael From david at davidcrose.org Mon Oct 22 20:23:31 2007 From: david at davidcrose.org (David Rose) Date: Mon, 22 Oct 2007 16:23:31 -0400 Subject: [Ekiga-list] Using Intel PC Camera Pro Message-ID: Hi, I was using Ekiga in Feisty Fawn quite happily. I have upgraded Ubuntu to Gutsy and now I have an error message when I try to run Ekiga 2.0.11: "Your driver doesn't seem to support any of the color formats supported by Ekiga. Please check your kernel driver documentation in order to determine which Palette is supported." Well, it was working before - so how do I check this, or what and where do I tweak in Ekiga to get it to use this camera. Thnaks, David From sevmek at free.fr Mon Oct 22 20:50:18 2007 From: sevmek at free.fr (yannick) Date: Mon, 22 Oct 2007 22:50:18 +0200 Subject: [Ekiga-list] Will not connect to test call In-Reply-To: <1193075817.5372.1.camel@sv-esmeralda> References: <1192998930.7854.8.camel@sv-esmeralda> <1193001811.27017.2.camel@scorpion> <1193075817.5372.1.camel@sv-esmeralda> Message-ID: <1193086218.18565.5.camel@achille> Le lundi 22 octobre 2007 ? 11:56 -0600, jim barber a ?crit : > Damien, > > Thank you for the reply. Unfortunately I am not very knowledgeable > about computers yet. I do not know what a -d 4 output is and where I > would post it. Can you help on this? Follow those instructions http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output_from_Ekiga Post the resulting file on internet, like here http://pastebin.com/ And send us the URL here. Regards, Yannick > > Jim Barber > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From dsandras at seconix.com Mon Oct 22 21:06:34 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Oct 2007 23:06:34 +0200 Subject: [Ekiga-list] Using Intel PC Camera Pro In-Reply-To: References: Message-ID: <1193087194.4188.28.camel@scorpion> Le lundi 22 octobre 2007 ? 16:23 -0400, David Rose a ?crit : > Hi, > > I was using Ekiga in Feisty Fawn quite happily. > > I have upgraded Ubuntu to Gutsy and now I have an error message when I > try to run Ekiga 2.0.11: > > "Your driver doesn't seem to support any of the color formats > supported by Ekiga. > Please check your kernel driver documentation in order to determine > which Palette is supported." > > Well, it was working before - so how do I check this, or what and > where do I tweak in Ekiga to get it to use this camera. > The problem is most probably due to a change in the driver. Try emailing its author... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From mstokle at gmail.com Mon Oct 22 21:18:57 2007 From: mstokle at gmail.com (Mariano Stokle) Date: Mon, 22 Oct 2007 18:18:57 -0300 Subject: [Ekiga-list] Want to collaborate Message-ID: Hi all, I am new to the list and want to collaborate with the project. I am proficient in SIP technologies and work for a multinational telecommunication vendor (although I am not in the technical staff and could have access to test Ekiga again different versions of Communication Servers). I am also can collaborate with translations to Spanish and other stuff. Regards, -- Mariano Stokle -------------- next part -------------- An HTML attachment was scrubbed... URL: From xlyz at fastwebnet.it Mon Oct 22 21:25:25 2007 From: xlyz at fastwebnet.it (xlyz) Date: Mon, 22 Oct 2007 23:25:25 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193045494.4186.9.camel@scorpion> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> <1193001771.27017.0.camel@scorpion> <1193002679.20115.15.camel@xmachine> <1193037769.4186.0.camel@scorpion> <1193044761.12410.3.camel@xmachine> <1193045494.4186.9.camel@scorpion> Message-ID: <1193088325.6384.4.camel@xmachine> > However, it is not normal to spend so much time on that lookup. It > indicates a problem on your DNS server. > the culprit seems to be the dns relay of my router. I've disabled it and now ekiga works fine > Can you double-check /etc/resolv.conf on the machine on which you have a > delay and on the machine that works correctly ? > -- both were the same machine, the second being a virtualized windows installation. I still do not understand why it worked fine: maybe the windows versione does not do the SRV lookup? btw many thanks for the assistance. xlyz From dsandras at seconix.com Mon Oct 22 21:29:18 2007 From: dsandras at seconix.com (Damien Sandras) Date: Mon, 22 Oct 2007 23:29:18 +0200 Subject: [Ekiga-list] ekiga slow to connect In-Reply-To: <1193088325.6384.4.camel@xmachine> References: <1192959402.6580.8.camel@xmachine> <1192963508.6580.11.camel@xmachine> <1192977376.7807.3.camel@scorpion> <1192978606.6580.15.camel@xmachine> <1192979425.7807.8.camel@scorpion> <1193001449.20115.3.camel@xmachine> <1193001771.27017.0.camel@scorpion> <1193002679.20115.15.camel@xmachine> <1193037769.4186.0.camel@scorpion> <1193044761.12410.3.camel@xmachine> <1193045494.4186.9.camel@scorpion> <1193088325.6384.4.camel@xmachine> Message-ID: <1193088558.4188.37.camel@scorpion> Le lundi 22 octobre 2007 ? 23:25 +0200, xlyz a ?crit : > > However, it is not normal to spend so much time on that lookup. It > > indicates a problem on your DNS server. > > > > the culprit seems to be the dns relay of my router. I've disabled it and > now ekiga works fine > > > Can you double-check /etc/resolv.conf on the machine on which you have a > > delay and on the machine that works correctly ? > > -- > > both were the same machine, the second being a virtualized windows > installation. I still do not understand why it worked fine: maybe the > windows versione does not do the SRV lookup? Yes, it does not do the SRV lookup, there is a bug in our package ;-) The future 3.00 release only does the SRV lookup when needed (in this specific case, it is not needed). But I am happy it finally works without delay :) > btw many thanks for the assistance. I'm happy it finally works! -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From ianyoli at gmail.com Mon Oct 22 22:06:26 2007 From: ianyoli at gmail.com (Ian Murdoch) Date: Mon, 22 Oct 2007 17:06:26 -0500 Subject: [Ekiga-list] Ekiga quits, (crashes?), when I click on the Webcam icon, or on the "Test Video Device" button in the Druid. Message-ID: <60d2a91a0710221506x716002b7i940e106a8bf17fdd@mail.gmail.com> Hi All, I am a registered user of Ekiga and have Version 2.0.9 installed. I searched in your ekiga-list archives and found that you were already aware of this problem, so did not file a bug report. I also read your note that this bug had been fixed in the next version of Ekiga to be issued. My O.S. is Ubuntu/Linux 6.06 LTS, Dapper. So I have been waiting for you to post a Download of Version 2.0.11 for this O.S. that I can install. So far you have only posted download files for Feisty. So my questions are: 1 - Do you propose to post a download file for Dapper? If not, then: 2 - Can I safely install any of the download files for Feisty, or Debian? If not, then: 3 - How can I obtain and install Ekiga Version 2.0.11 in my O.S.? I am a newcomer to Linux and do not know all the tricks and shortcuts, so I will appreciate your help. For your information, I am trying to set up my Webcam, which is a MSI Starcam 370i. My system detects it and it appears as a Sangha 350k in the video devices page of the Druid. Also, from the command line info, it uses jpeg compression. I have searched on the web to discover the correct driver and have found that this webcam is supported by the spca5xx driver. I have downloaded the package spca5xx-source from the Linux repositories, using Synaptic P.M. and I have compiled it and installed it. Also, already installed on my system are: libopal-2.2.0 (2.2.8-0dapper0) libopal-doc 2.2.1-1ubuntu1 libpt-1.10.0 (1.10.7-0dapper0) libpt-plugins-alsa ( idem ) libpt-plugins-v4l ( idem ) libpt-plugins- v4l2( idem ) >From what I have read in your archives, I may need to change all these files! So your comments on this point would be helpful. I am anxious to test my webcam with this driver, with the hope that I can get this hardware working. At the moment I am using Ekiga, with much satisfaction, mostly for VoIP international calls to fixed phones through Diamondcard, with whom I have an account. I also make a few calls to mobile phones the same way. Speed of connection, sound quality and clarity are all top class. So I congratulate you digital wizards for creating an excelent software programme and I thank you all for your dedication to making and maintaining this very good software within the open source movement. I hope you will be able to help me overcome this last obstacle. Thanks, Yoliano. -------------- next part -------------- An HTML attachment was scrubbed... URL: From mshahwan2001 at yahoo.com Tue Oct 23 04:31:49 2007 From: mshahwan2001 at yahoo.com (Michael) Date: Mon, 22 Oct 2007 21:31:49 -0700 (PDT) Subject: [Ekiga-list] DTMF and Asterisk? Message-ID: <729280.63917.qm@web52407.mail.re2.yahoo.com> Damien: Your suggestion of using INFO worked well. However, when we set INFO on Asterisks all incoming PSTN DTMF tones fail. So it is either we have DTMF tones for out bound, but lose inbound. What do we do? ----- Original Message ---- From: Damien Sandras To: Ekiga mailing list Sent: Thursday, October 11, 2007 2:56:55 AM Subject: Re: [Ekiga-list] DTMF and Asterisk? Le mercredi 10 octobre 2007 ? 19:09 -0700, Michael a ?crit : > Damien: > > Just received additional information on this problem. If any user uses > Ekiga and they press a digit the digit will sound as if it is > continually pressed (never left go of it). For example if I called you > and accidentally pressed ZERO you would hear the number ZERO beep to > infinity. This must be the problem with DTMF tones. Instead of being a > short beep it is as if the number is stuck and continually gives a > prolonged beeeeeee....(never ending) ....p. > > Any ideas? They must have a problem with their RFC2833 implementation. Try using SIP Info instead. I do not think the bug is in Ekiga or OPAL... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From DAVE.HIGTON at nice.com Tue Oct 23 15:12:17 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Tue, 23 Oct 2007 16:12:17 +0100 Subject: [Ekiga-list] Bad sound from mic in Windows Ekiga Message-ID: I've just deleted my Ekiga installation (which came from ekiga-setup-2.0.9-BETA.exe, and on which I never got more than a buzz from the microphone) and replaced it from ekiga-setup-2.0.11-BETA.exe. This is an improvement, i.e. it's not quite as disastrous; I can hear my voice, though with a bad buzz added, and probably even modulated by the buzz. I'm referring to what I hear when I run the audio test in the installation process. I can hear other sounds in the headphones OK, so I know that audio out is working OK. I have the impression that there's a mismatch in the sampling rates. I opted to install with a sample rate of 8000, which wasn't offered in the list, it had to be a custom sample rate. I need 8000 as I need to be compatible with common telecom sample rates. I think my next step will have to be to feed in a signal from a signal generator and look at the output with an oscilloscope while running the test. OS is Windows XP with a full set of updates. The sound system is Realtek AC97 Audio for microphone and playback. Can anyone suggest what might be done to fix the problem? Have others experienced the same? Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From dsandras at seconix.com Tue Oct 23 16:03:33 2007 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Oct 2007 18:03:33 +0200 Subject: [Ekiga-list] Ekiga quits, (crashes?), when I click on the Webcam icon, or on the "Test Video Device" button in the Druid. In-Reply-To: <60d2a91a0710221506x716002b7i940e106a8bf17fdd@mail.gmail.com> References: <60d2a91a0710221506x716002b7i940e106a8bf17fdd@mail.gmail.com> Message-ID: <1193155413.15621.30.camel@scorpion> Hi, Le lundi 22 octobre 2007 ? 17:06 -0500, Ian Murdoch a ?crit : > Hi All, > I am a registered user of Ekiga and have Version 2.0.9 installed. I > searched in your ekiga-list archives and found that you were already > aware of this problem, so did not file a bug report. I also read your > note that this bug had been fixed in the next version of Ekiga to be > issued. My O.S. is Ubuntu/Linux 6.06 LTS, Dapper. So I have been > waiting for you to post a Download of Version 2.0.11 for this O.S. > that I can install. So far you have only posted download files for > Feisty. So my questions are: > 1 - Do you propose to post a download file for Dapper? If not, then: I do not think so. But perhaps somebody will do a backport. > 2 - Can I safely install any of the download files for Feisty, or > Debian? If not, then: No, it is not safe. > 3 - How can I obtain and install Ekiga Version 2.0.11 in my O.S.? You will have to compile it. If you are new to this, I would recommend against trying it as it might be complex and potentially break your system. Perhaps you could simply upgrade your distribution to something newer. > I am a newcomer to Linux and do not know all the tricks and shortcuts, > so I will appreciate your help. > For your information, I am trying to set up my Webcam, which is a MSI > Starcam 370i. My system detects it and it appears as a Sangha 350k in > the video devices page of the Druid. Also, from the command line info, > it uses jpeg compression. I have searched on the web to discover the > correct driver and have found that this webcam is supported by the > spca5xx driver. I have downloaded the package spca5xx-source from the > Linux repositories, using Synaptic P.M. and I have compiled it and > installed it. Also, already installed on my system are: > libopal-2.2.0 (2.2.8-0dapper0) > libopal-doc 2.2.1-1ubuntu1 > libpt-1.10.0 (1.10.7-0dapper0) > libpt-plugins-alsa ( idem ) > libpt-plugins-v4l ( idem ) > libpt-plugins- v4l2( idem ) > From what I have read in your archives, I may need to change all these > files! So your comments on this point would be helpful. I am anxious > to test my webcam with this driver, with the hope that I can get this > hardware working. At the moment I am using Ekiga, with much > satisfaction, mostly for VoIP international calls to fixed phones > through Diamondcard, with whom I have an account. I also make a few > calls to mobile phones the same way. Speed of connection, sound > quality and clarity are all top class. So I congratulate you digital > wizards for creating an excelent software programme and I thank you > all for your dedication to making and maintaining this very good > software within the open source movement. I hope you will be able to > help me overcome this last obstacle. Thanks, Yoliano. Thank you for your compliment ;-) I have CC'ed Kilian and Luc to know if they were aware of a Dapper backport of Ekiga 2.0.11. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Oct 23 16:05:38 2007 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Oct 2007 18:05:38 +0200 Subject: [Ekiga-list] DTMF and Asterisk? In-Reply-To: <729280.63917.qm@web52407.mail.re2.yahoo.com> References: <729280.63917.qm@web52407.mail.re2.yahoo.com> Message-ID: <1193155538.15621.34.camel@scorpion> Hello, Le lundi 22 octobre 2007 ? 21:31 -0700, Michael a ?crit : > Damien: > > Your suggestion of using INFO worked well. However, when we set INFO > on Asterisks all incoming PSTN DTMF tones fail. So it is either we > have DTMF tones for out bound, but lose inbound. What do we do? That is something I do not understand. Your PSTN DTMF tones do not depend from the SIP DTMF tones. Also, for each SIP peer (ie Ekiga, a SIP ITSP, another IP Phone), you can select the type of DTMF you want to use and Asterisk is able to deal with different sources using different mechanisms. Notice we are using Ekiga with RFC2833 tones in several production environments without having any problem. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Oct 23 16:07:28 2007 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Oct 2007 18:07:28 +0200 Subject: [Ekiga-list] Bad sound from mic in Windows Ekiga In-Reply-To: References: Message-ID: <1193155648.15621.37.camel@scorpion> Hello, Le mardi 23 octobre 2007 ? 16:12 +0100, Dave Higton a ?crit : > I've just deleted my Ekiga installation (which came from > ekiga-setup-2.0.9-BETA.exe, and on which I never got more than a buzz > from the microphone) and replaced it from ekiga-setup-2.0.11-BETA.exe. > This is an improvement, i.e. it's not quite as disastrous; I can hear my > voice, though with a bad buzz added, and probably even modulated by the > buzz. I'm referring to what I hear when I run the audio test in the > installation process. > > I can hear other sounds in the headphones OK, so I know that audio out > is working OK. > > I have the impression that there's a mismatch in the sampling rates. I > opted to install with a sample rate of 8000, which wasn't offered in the > list, it had to be a custom sample rate. I need 8000 as I need to be > compatible with common telecom sample rates. > > I think my next step will have to be to feed in a signal from a signal > generator and look at the output with an oscilloscope while running the > test. > > OS is Windows XP with a full set of updates. The sound system is > Realtek AC97 Audio for microphone and playback. > > Can anyone suggest what might be done to fix the problem? Have others > experienced the same? The sound audio test runs at 16 kHz. But when making calls, it will use 8 kHz or 16 kHz depending on the codec being used. I can not really help for your audio problem though, it seems to be some kind of hardware driver problem. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Tue Oct 23 16:08:39 2007 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 23 Oct 2007 18:08:39 +0200 Subject: [Ekiga-list] Want to collaborate In-Reply-To: References: Message-ID: <1193155719.15621.40.camel@scorpion> Hello, Le lundi 22 octobre 2007 ? 18:18 -0300, Mariano Stokle a ?crit : > Hi all, > I am new to the list and want to collaborate with the > project. Welcome on board ! > I am proficient in SIP technologies and work for a multinational > telecommunication vendor (although I am not in the technical staff and > could have access to test Ekiga again different versions of > Communication Servers). I am also can collaborate with translations to > Spanish and other stuff. If you are ready to code in C/C++ at the protocol level, or want to do GUI development, feel free to have a look at our roadmap on http://wiki.ekiga.org and step in for any feature that you want to see being added. That would be very much appreciated ! -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From kk at verfaction.de Tue Oct 23 16:19:06 2007 From: kk at verfaction.de (Kilian Krause) Date: Tue, 23 Oct 2007 18:19:06 +0200 Subject: [Ekiga-list] Ekiga quits, (crashes?), when I click on the Webcam icon, or on the "Test Video Device" button in the Druid. In-Reply-To: <1193155413.15621.30.camel@scorpion> References: <60d2a91a0710221506x716002b7i940e106a8bf17fdd@mail.gmail.com> <1193155413.15621.30.camel@scorpion> Message-ID: <20071023161905.GN17604@mx.verfaction.de> Ian, On Tue, Oct 23, 2007 at 06:03:33PM +0200, Damien Sandras wrote: > Le lundi 22 octobre 2007 ? 17:06 -0500, Ian Murdoch a ?crit : > > Hi All, > > I am a registered user of Ekiga and have Version 2.0.9 installed. I > > searched in your ekiga-list archives and found that you were already > > aware of this problem, so did not file a bug report. I also read your > > note that this bug had been fixed in the next version of Ekiga to be > > issued. My O.S. is Ubuntu/Linux 6.06 LTS, Dapper. So I have been > > waiting for you to post a Download of Version 2.0.11 for this O.S. > > that I can install. So far you have only posted download files for > > Feisty. So my questions are: > > 1 - Do you propose to post a download file for Dapper? If not, then: > > I do not think so. But perhaps somebody will do a backport. that would include backporting half of GNOME to make this work. For now it's quite unlikely this will happen. I know Dapper as the LTS is a very nice basis, but we've so far voted against automated backports due to the sheer amount of build-depends to satisfy manually. LTS is in that way a very good choice for a server, but not for the desktop. > > 2 - Can I safely install any of the download files for Feisty, or > > Debian? If not, then: > > No, it is not safe. Fully agreed. ;) > > 3 - How can I obtain and install Ekiga Version 2.0.11 in my O.S.? > > You will have to compile it. If you are new to this, I would recommend > against trying it as it might be complex and potentially break your > system. > > Perhaps you could simply upgrade your distribution to something newer. This is indeed the only true alternative. Everything else will render you almost there anyway. > > I am a newcomer to Linux and do not know all the tricks and shortcuts, > > so I will appreciate your help. > > For your information, I am trying to set up my Webcam, which is a MSI > > Starcam 370i. My system detects it and it appears as a Sangha 350k in > > the video devices page of the Druid. Also, from the command line info, > > it uses jpeg compression. I have searched on the web to discover the > > correct driver and have found that this webcam is supported by the > > spca5xx driver. I have downloaded the package spca5xx-source from the > > Linux repositories, using Synaptic P.M. and I have compiled it and > > installed it. Also, already installed on my system are: > > libopal-2.2.0 (2.2.8-0dapper0) > > libopal-doc 2.2.1-1ubuntu1 > > libpt-1.10.0 (1.10.7-0dapper0) > > libpt-plugins-alsa ( idem ) > > libpt-plugins-v4l ( idem ) > > libpt-plugins- v4l2( idem ) > > From what I have read in your archives, I may need to change all these > > files! Yes, you would. And quite a bit more even. > > So your comments on this point would be helpful. I am anxious > > to test my webcam with this driver, with the hope that I can get this > > hardware working. At the moment I am using Ekiga, with much > > satisfaction, mostly for VoIP international calls to fixed phones > > through Diamondcard, with whom I have an account. I also make a few > > calls to mobile phones the same way. Speed of connection, sound > > quality and clarity are all top class. So I congratulate you digital > > wizards for creating an excelent software programme and I thank you > > all for your dedication to making and maintaining this very good > > software within the open source movement. I hope you will be able to > > help me overcome this last obstacle. Thanks, Yoliano. > > Thank you for your compliment ;-) > > I have CC'ed Kilian and Luc to know if they were aware of a Dapper > backport of Ekiga 2.0.11. There's none that I'm aware of covering GNOME 2.20. Honestly, I'm not too much into Ubuntu to give an authoritive answer on this. But I can say as much, I don't do any. =) Thanks for the compilments though and much luck upgrading your desktop to Feisty. -- Best regards, Kilian -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: From mstokle at gmail.com Tue Oct 23 16:30:48 2007 From: mstokle at gmail.com (Mariano Stokle) Date: Tue, 23 Oct 2007 13:30:48 -0300 Subject: [Ekiga-list] Want to collaborate In-Reply-To: <1193155719.15621.40.camel@scorpion> References: <1193155719.15621.40.camel@scorpion> Message-ID: Thanks for the Welcome! I will read the wiki and see the area that I can contribute the most. Regards, Mariano On 10/23/07, Damien Sandras wrote: > > Hello, > > Le lundi 22 octobre 2007 ? 18:18 -0300, Mariano Stokle a ?crit : > > Hi all, > > I am new to the list and want to collaborate with the > > project. > > Welcome on board ! > > > I am proficient in SIP technologies and work for a multinational > > telecommunication vendor (although I am not in the technical staff and > > could have access to test Ekiga again different versions of > > Communication Servers). I am also can collaborate with translations to > > Spanish and other stuff. > > If you are ready to code in C/C++ at the protocol level, or want to do > GUI development, feel free to have a look at our roadmap on > http://wiki.ekiga.org and step in for any feature that you want to see > being added. > > That would be very much appreciated ! > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Mariano Stokle -------------- next part -------------- An HTML attachment was scrubbed... URL: From svesmeralda at gmail.com Wed Oct 24 02:40:32 2007 From: svesmeralda at gmail.com (jim barber) Date: Tue, 23 Oct 2007 20:40:32 -0600 Subject: [Ekiga-list] Will not connect to test call In-Reply-To: <1193086218.18565.5.camel@achille> References: <1192998930.7854.8.camel@sv-esmeralda> <1193001811.27017.2.camel@scorpion> <1193075817.5372.1.camel@sv-esmeralda> <1193086218.18565.5.camel@achille> Message-ID: <1193193632.5772.12.camel@sv-esmeralda> Yannick, The problem of not connecting the call still persists. I followed the instructions you gave me at: http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output_from_Ekiga I tried to post the output.test at: http://pastebin.com/ It was too large for the site and gave this error message: Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 145 bytes) in /home/pastebin/lib/geshi/geshi.php on line 1979 I can send to you the complete list of the output.txt file if you like. I noticed that there is place to report a problem in the Ekiga help menu. Should I pursue this avenue as well? Jim Barber Aboard Esmeralda Mazatlan, Mexico From damailings at mcbf.net Wed Oct 24 04:55:40 2007 From: damailings at mcbf.net (David Mohr) Date: Tue, 23 Oct 2007 22:55:40 -0600 Subject: [Ekiga-list] Will not connect to test call In-Reply-To: <1193193632.5772.12.camel@sv-esmeralda> References: <1192998930.7854.8.camel@sv-esmeralda> <1193001811.27017.2.camel@scorpion> <1193075817.5372.1.camel@sv-esmeralda> <1193086218.18565.5.camel@achille> <1193193632.5772.12.camel@sv-esmeralda> Message-ID: <472d4b250710232155oe55f00eu77f57466ae02654f@mail.gmail.com> On 10/23/07, jim barber wrote: > Yannick, > > The problem of not connecting the call still persists. I followed the > instructions you gave me at: > > http://wiki.ekiga.org/index.php/Debugging_Ekiga#How_to_get_a_debug_output_from_Ekiga > > I tried to post the output.test at: > > http://pastebin.com/ > > It was too large for the site and gave this error message: > > Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to > allocate 145 bytes) in /home/pastebin/lib/geshi/geshi.php on line 1979 Are you sure you selected "Syntax highlighting: none" at pastebin.com? Because the error you are seeing is from the syntax highlighting script. Or alternatively you could try to use any other pastebin that google can come up with. ~David > I can send to you the complete list of the output.txt file if you like. > > I noticed that there is place to report a problem in the Ekiga help > menu. Should I pursue this avenue as well? > > Jim Barber > Aboard Esmeralda > Mazatlan, Mexico > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From DAVE.HIGTON at nice.com Wed Oct 24 07:20:25 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Wed, 24 Oct 2007 08:20:25 +0100 Subject: [Ekiga-list] Bad sound from mic in Windows Ekiga In-Reply-To: <1193155648.15621.37.camel@scorpion> References: <1193155648.15621.37.camel@scorpion> Message-ID: > -----Original Message----- > From: ekiga-list-bounces at gnome.org > [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras > Sent: 2007 October 23 17:07 > To: Ekiga mailing list > Subject: Re: [Ekiga-list] Bad sound from mic in Windows Ekiga > > Hello, > > Le mardi 23 octobre 2007 ? 16:12 +0100, Dave Higton a ?crit : > > I've just deleted my Ekiga installation (which came from > > ekiga-setup-2.0.9-BETA.exe, and on which I never got more > than a buzz > > from the microphone) and replaced it from > ekiga-setup-2.0.11-BETA.exe. > > This is an improvement, i.e. it's not quite as disastrous; > I can hear my > > voice, though with a bad buzz added, and probably even > modulated by the > > buzz. I'm referring to what I hear when I run the audio test in the > > installation process. > > > > I can hear other sounds in the headphones OK, so I know > that audio out > > is working OK. > > > > I have the impression that there's a mismatch in the > sampling rates. I > > opted to install with a sample rate of 8000, which wasn't > offered in the > > list, it had to be a custom sample rate. I need 8000 as I > need to be > > compatible with common telecom sample rates. > > > > I think my next step will have to be to feed in a signal > from a signal > > generator and look at the output with an oscilloscope while > running the > > test. > > > > OS is Windows XP with a full set of updates. The sound system is > > Realtek AC97 Audio for microphone and playback. > > > > Can anyone suggest what might be done to fix the problem? > Have others > > experienced the same? > > The sound audio test runs at 16 kHz. But when making calls, > it will use > 8 kHz or 16 kHz depending on the codec being used. > > I can not really help for your audio problem though, it seems > to be some > kind of hardware driver problem. I don't think so. I just used Cool Edit 96 to record a few seconds of my voice and play it back. This uses the same drivers as does Ekiga - but Cool Edit records and replays fine. I set Cool Edit to record in 8 bit mono at 8000 Hz. It has to be something about the way Ekiga uses the drivers, doesn't it? Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From dsandras at seconix.com Wed Oct 24 07:39:45 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Oct 2007 09:39:45 +0200 Subject: [Ekiga-list] Bad sound from mic in Windows Ekiga In-Reply-To: References: <1193155648.15621.37.camel@scorpion> Message-ID: <1193211585.4243.3.camel@scorpion> Le mercredi 24 octobre 2007 ? 08:20 +0100, Dave Higton a ?crit : > > -----Original Message----- > > From: ekiga-list-bounces at gnome.org > > [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras > > Sent: 2007 October 23 17:07 > > To: Ekiga mailing list > > Subject: Re: [Ekiga-list] Bad sound from mic in Windows Ekiga > > > > Hello, > > > > Le mardi 23 octobre 2007 ? 16:12 +0100, Dave Higton a ?crit : > > > I've just deleted my Ekiga installation (which came from > > > ekiga-setup-2.0.9-BETA.exe, and on which I never got more > > than a buzz > > > from the microphone) and replaced it from > > ekiga-setup-2.0.11-BETA.exe. > > > This is an improvement, i.e. it's not quite as disastrous; > > I can hear my > > > voice, though with a bad buzz added, and probably even > > modulated by the > > > buzz. I'm referring to what I hear when I run the audio test in the > > > installation process. > > > > > > I can hear other sounds in the headphones OK, so I know > > that audio out > > > is working OK. > > > > > > I have the impression that there's a mismatch in the > > sampling rates. I > > > opted to install with a sample rate of 8000, which wasn't > > offered in the > > > list, it had to be a custom sample rate. I need 8000 as I > > need to be > > > compatible with common telecom sample rates. > > > > > > I think my next step will have to be to feed in a signal > > from a signal > > > generator and look at the output with an oscilloscope while > > running the > > > test. > > > > > > OS is Windows XP with a full set of updates. The sound system is > > > Realtek AC97 Audio for microphone and playback. > > > > > > Can anyone suggest what might be done to fix the problem? > > Have others > > > experienced the same? > > > > The sound audio test runs at 16 kHz. But when making calls, > > it will use > > 8 kHz or 16 kHz depending on the codec being used. > > > > I can not really help for your audio problem though, it seems > > to be some > > kind of hardware driver problem. > > I don't think so. I just used Cool Edit 96 to record a few > seconds of my voice and play it back. This uses the same > drivers as does Ekiga - but Cool Edit records and replays > fine. I set Cool Edit to record in 8 bit mono at 8000 Hz. > > It has to be something about the way Ekiga uses the drivers, > doesn't it? > That could be. We have preliminary support for DirectSound, but it is not fully tested yet.... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From DAVE.HIGTON at nice.com Wed Oct 24 09:43:42 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Wed, 24 Oct 2007 10:43:42 +0100 Subject: [Ekiga-list] Ekiga rpm for Fedora Core 5? Message-ID: Does an rpm exist for any recent version of Ekiga on Fedora Core 5? If so, where can I find it? I can't upgrade from FC5 because the product I'm working on uses FC5 and therefore all our dev tools and boxes also have to remain at FC5. We do plan to upgrade, but we haven't got firm dates to do so yet. Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From DAVE.HIGTON at nice.com Wed Oct 24 09:48:46 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Wed, 24 Oct 2007 10:48:46 +0100 Subject: [Ekiga-list] RTP/RTCP port ranges Message-ID: Is it possible to configure the range of ports that Ekiga uses for RTP and RTCP? Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From dsandras at seconix.com Wed Oct 24 14:21:24 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Oct 2007 16:21:24 +0200 Subject: [Ekiga-list] RTP/RTCP port ranges In-Reply-To: References: Message-ID: <1193235684.20167.42.camel@scorpion> Le mercredi 24 octobre 2007 ? 10:48 +0100, Dave Higton a ?crit : > Is it possible to configure the range of ports that Ekiga uses for RTP > and RTCP? > http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From DAVE.HIGTON at nice.com Wed Oct 24 14:29:28 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Wed, 24 Oct 2007 15:29:28 +0100 Subject: [Ekiga-list] RTP/RTCP port ranges In-Reply-To: <1193235684.20167.42.camel@scorpion> References: <1193235684.20167.42.camel@scorpion> Message-ID: > -----Original Message----- > From: ekiga-list-bounces at gnome.org > [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras > Sent: 2007 October 24 15:21 > To: Ekiga mailing list > Subject: Re: [Ekiga-list] RTP/RTCP port ranges > > > Le mercredi 24 octobre 2007 ? 10:48 +0100, Dave Higton a ?crit : > > Is it possible to configure the range of ports that Ekiga > uses for RTP > > and RTCP? > > > http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga Ah. I take it this facility isn't available in the Windows version, then? Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From dsandras at seconix.com Wed Oct 24 14:43:56 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Oct 2007 16:43:56 +0200 Subject: [Ekiga-list] RTP/RTCP port ranges In-Reply-To: References: <1193235684.20167.42.camel@scorpion> Message-ID: <1193237036.20167.48.camel@scorpion> Le mercredi 24 octobre 2007 ? 15:29 +0100, Dave Higton a ?crit : > > -----Original Message----- > > From: ekiga-list-bounces at gnome.org > > [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras > > Sent: 2007 October 24 15:21 > > To: Ekiga mailing list > > Subject: Re: [Ekiga-list] RTP/RTCP port ranges > > > > > > Le mercredi 24 octobre 2007 ? 10:48 +0100, Dave Higton a ?crit : > > > Is it possible to configure the range of ports that Ekiga > > uses for RTP > > > and RTCP? > > > > > http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga > > Ah. I take it this facility isn't available in the Windows > version, then? > You can edit the configuration file by hand. You will have to discover by yourself where it is being put, because I ignore it. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From DAVE.HIGTON at nice.com Wed Oct 24 14:53:47 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Wed, 24 Oct 2007 15:53:47 +0100 Subject: [Ekiga-list] RTP/RTCP port ranges In-Reply-To: <1193237036.20167.48.camel@scorpion> References: <1193235684.20167.42.camel@scorpion> <1193237036.20167.48.camel@scorpion> Message-ID: > -----Original Message----- > From: ekiga-list-bounces at gnome.org > [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras > Sent: 2007 October 24 15:44 > To: Ekiga mailing list > Subject: Re: [Ekiga-list] RTP/RTCP port ranges > > > Le mercredi 24 octobre 2007 ? 15:29 +0100, Dave Higton a ?crit : > > > -----Original Message----- > > > From: ekiga-list-bounces at gnome.org > > > [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras > > > Sent: 2007 October 24 15:21 > > > To: Ekiga mailing list > > > Subject: Re: [Ekiga-list] RTP/RTCP port ranges > > > > > > > > > Le mercredi 24 octobre 2007 ? 10:48 +0100, Dave Higton a ?crit : > > > > Is it possible to configure the range of ports that Ekiga > > > uses for RTP > > > > and RTCP? > > > > > > > http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga > > > > Ah. I take it this facility isn't available in the Windows > > version, then? > > > > You can edit the configuration file by hand. You will have to discover > by yourself where it is being put, because I ignore it. OK, got it. Thanks. Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From dsandras at seconix.com Wed Oct 24 14:48:08 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 24 Oct 2007 16:48:08 +0200 Subject: [Ekiga-list] Ekiga rpm for Fedora Core 5? In-Reply-To: References: Message-ID: <1193237288.20167.50.camel@scorpion> Le mercredi 24 octobre 2007 ? 10:43 +0100, Dave Higton a ?crit : > Does an rpm exist for any recent version of Ekiga on Fedora Core 5? If > so, where can I find it? On the website : http://www.ekiga.org/index.php?rub=5&path=fedora/FC5 > I can't upgrade from FC5 because the product I'm working on uses FC5 and > therefore all our dev tools and boxes also have to remain at FC5. We do > plan to upgrade, but we haven't got firm dates to do so yet. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From oisin.feeley at gmail.com Wed Oct 24 15:23:23 2007 From: oisin.feeley at gmail.com (Oisin Feeley) Date: Wed, 24 Oct 2007 11:23:23 -0400 Subject: [Ekiga-list] Ekiga rpm for Fedora Core 5? In-Reply-To: References: Message-ID: On 10/24/07, Dave Higton wrote: > Does an rpm exist for any recent version of Ekiga on Fedora Core 5? If > so, where can I find it? > > I can't upgrade from FC5 because the product I'm working on uses FC5 and > therefore all our dev tools and boxes also have to remain at FC5. We do > plan to upgrade, but we haven't got firm dates to do so yet. Hi Dave, You have two options: 1) build your own RPM from the source; 2) use one of the FedoraLegacy mirrors[1]. This one Australia has been active and useful to me: http://public.planetmirror.com/pub/fedoralegacy/fedora/5/updates/i386/repodata/?fl= but there's a whole list of them here: http://fedoralegacy.org/download/fedoralegacy-mirrors.php As you suggest it's probably worth transitioning to a newer version as soon as you can. Have you considered using RHEL instead because of the longer support cycle? Best wishes, Oisin Feeley 1. FedoraLegacy may not be around much longer! They have problems with getting enough community support/funding. Most people that want a platform with longer maintenance times use RHEL (or if they can't afford the licensing CentOS). Probably you know that. Good luck. From svesmeralda at gmail.com Wed Oct 24 17:46:23 2007 From: svesmeralda at gmail.com (jim barber) Date: Wed, 24 Oct 2007 11:46:23 -0600 Subject: [Ekiga-list] Will not connect to test call In-Reply-To: <472d4b250710232155oe55f00eu77f57466ae02654f@mail.gmail.com> References: <1192998930.7854.8.camel@sv-esmeralda> <1193001811.27017.2.camel@scorpion> <1193075817.5372.1.camel@sv-esmeralda> <1193086218.18565.5.camel@achille> <1193193632.5772.12.camel@sv-esmeralda> <472d4b250710232155oe55f00eu77f57466ae02654f@mail.gmail.com> Message-ID: <1193247983.5719.5.camel@sv-esmeralda> I checked the high lighting and it was set to none, retried, got the error message. I went to open paste bin and it said it was too big and to break it up into sections of 2000 lines or less. It has 8572 lines in the list. Shall I post it in open paste bin in 5 sections or post the problem through the Ekiga help menu? Jim Barber From destebani at gmail.com Thu Oct 25 01:18:13 2007 From: destebani at gmail.com (David Esteban) Date: Thu, 25 Oct 2007 10:18:13 +0900 Subject: [Ekiga-list] Instances of class Message-ID: Dear All, I modified the definition of the class in by adding son integer parameters that i will use later. Problem is that i need these parameters to be visible in "manager.cpp". library < videoinput.h> is already inlcuded in "manager.cpp" but i dont know the suitable call to that object from "manager.cpp". Can any of you give me any clue?? Thanks in advance, -------------- next part -------------- An HTML attachment was scrubbed... URL: From michel.memeteau at gmail.com Thu Oct 25 07:15:23 2007 From: michel.memeteau at gmail.com (michel memeteau) Date: Thu, 25 Oct 2007 09:15:23 +0200 Subject: [Ekiga-list] =?iso-8859-1?q?=5BOfftopic=5D_New_version_of_WinGizm?= =?iso-8859-1?q?o_with_vid=E9o?= Message-ID: Hi , I just came accross a beta version of Gizmo ( sipphone) that support vid?o, it's only on Gizmo right now and I haven't tested it. http://download.gizmoproject.com/jasmine/ there are a lot of things I don't like in Gizmo ( like the fact that they Push the Gizmo nickname idea confusing people like Wengo ) and it's closed software , But it's easy to setup for non geek and it result in a good standard Sip phone. as we can see right now : http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F#Windows they are not too many good sip windows client with vid?o right now for non geeks : Wengo has to be patched for video interop; Ekiga for windows is even the best opensource solution right now ! So If you have a windows machine to give it a try ( I don't ) ... i'm open to test Ekiga & Xmeeting interop. -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0874763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at gizmoproject.com jabber/GoogleTalk : xmpp:freechelmi at jabber.fr From nogueira at emc.ufsc.br Thu Oct 25 11:56:34 2007 From: nogueira at emc.ufsc.br (Antonio Carlos Ribeiro Nogueira) Date: Thu, 25 Oct 2007 08:56:34 -0300 Subject: [Ekiga-list] RTP/RTCP port ranges In-Reply-To: References: <1193235684.20167.42.camel@scorpion> <1193237036.20167.48.camel@scorpion> Message-ID: <47208472.4060602@emc.ufsc.br> Dave Higton escreveu: >> -----Original Message----- >> From: ekiga-list-bounces at gnome.org >> [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras >> Sent: 2007 October 24 15:44 >> To: Ekiga mailing list >> Subject: Re: [Ekiga-list] RTP/RTCP port ranges >> >> >> Le mercredi 24 octobre 2007 ? 15:29 +0100, Dave Higton a ?crit : >> >>>> -----Original Message----- >>>> From: ekiga-list-bounces at gnome.org >>>> [mailto:ekiga-list-bounces at gnome.org] On Behalf Of Damien Sandras >>>> Sent: 2007 October 24 15:21 >>>> To: Ekiga mailing list >>>> Subject: Re: [Ekiga-list] RTP/RTCP port ranges >>>> >>>> >>>> Le mercredi 24 octobre 2007 ? 10:48 +0100, Dave Higton a ?crit : >>>> >>>>> Is it possible to configure the range of ports that Ekiga >>>>> >>>> uses for RTP >>>> >>>>> and RTCP? >>>>> >>>>> >>>> http://wiki.ekiga.org/index.php/Internet_ports_used_by_Ekiga >>>> >>> Ah. I take it this facility isn't available in the Windows >>> version, then? >>> >>> >> You can edit the configuration file by hand. You will have to discover >> by yourself where it is being put, because I ignore it. >> > > OK, got it. Thanks. > > Dave > > > ************************************************************************************************************************************************************************************************************************************************* > > NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. > > Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. > > Monitoring: NICE may monitor incoming and outgoing e-mails. > > Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. > > **************************************************************************************************************************************************************************************************************************************************** > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > Dave, can you send to me the ports windows use? Thanks in advance. Antonio Carlos From schan at cs.ucr.edu Thu Oct 25 17:26:09 2007 From: schan at cs.ucr.edu (sam chan) Date: Thu, 25 Oct 2007 10:26:09 -0700 (PDT) Subject: [Ekiga-list] only 2 working audio codecs In-Reply-To: References: Message-ID: Fedora 7 ekiga 2.0.11 i'm having a problem using audio codecs other than PCMAU and iLBC. if select just one codec at a time to test, it's just these two that work. not even speex works. when it doesn't work, a call simply hangs up after a second or two without anything happening. any ideas? thanks. From dsandras at seconix.com Thu Oct 25 19:20:00 2007 From: dsandras at seconix.com (Damien Sandras) Date: Thu, 25 Oct 2007 21:20:00 +0200 Subject: [Ekiga-list] only 2 working audio codecs In-Reply-To: References: Message-ID: <1193340000.4169.0.camel@scorpion> Le jeudi 25 octobre 2007 ? 10:26 -0700, sam chan a ?crit : > > Fedora 7 > ekiga 2.0.11 > > > i'm having a problem using audio codecs other than PCMAU and > iLBC. if select just one codec at a time to test, it's just > these two that work. not even speex works. > > when it doesn't work, a call simply hangs up after a second or > two without anything happening. > > any ideas? thanks. Does the remote peer support other codecs than PCMU/A and iLBC ? -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From schan at cs.ucr.edu Thu Oct 25 19:51:08 2007 From: schan at cs.ucr.edu (sam chan) Date: Thu, 25 Oct 2007 12:51:08 -0700 (PDT) Subject: [Ekiga-list] only 2 working audio codecs In-Reply-To: <1193340000.4169.0.camel@scorpion> References: <1193340000.4169.0.camel@scorpion> Message-ID: Damien, when i tested this, i just used the echo test(500 at ekiga.net). i don't believe it's related to what's at the other end. i do have speex installed. might i be needing another package? -sam ps (i actually haven't used ekiga wither another voip peer since i don't know any who uses this; besides skype) On Thu, 25 Oct 2007, Damien Sandras wrote: >=20 Le jeudi 25 octobre 2007 =C3=A0 10:26 -0700, sam chan a =C3=A9crit : >=20 > Fedora 7 > ekiga 2.0.11 >=20 >=20 > i'm having a problem using audio codecs other than PCMAU and > iLBC. if select just one codec at a time to test, it's just > these two that work. not even speex works. >=20 > when it doesn't work, a call simply hangs up after a second or > two without anything happening. >=20 > any ideas? thanks. Does the remote peer support other codecs than PCMU/A and iLBC ? --=20 _ Damien Sandras (o- =20 //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net =20 _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list From ianyoli at gmail.com Thu Oct 25 22:53:27 2007 From: ianyoli at gmail.com (Ian Murdoch) Date: Thu, 25 Oct 2007 17:53:27 -0500 Subject: [Ekiga-list] Ekiga quits, (crashes?), when I click on the Webcam icon, or on the "Test Video Device" button in the Druid. Message-ID: <60d2a91a0710251553p6b476dd8sfed64bacc340c905@mail.gmail.com> Hi Damien and Kilian, Thanks for your instant and most helpful replies. I have just been to the Ubuntu website to check out my options for upgrading and have found that the situation is not so simple. Feisty, Version 7.04 is now obsolete and is no longer available for downloading, having been superceded by a new release, Version 7.10, called Gutsy, (would you believe?). I cannot upgrade to it because it is one release removed from my Dapper, (it is only possible to upgrade from one release to the next). So I would have to install it, which would wipe out my Dapper. I am not willing to do that because my Dapper is highly configured now for my particular usage needs. I have spent many hours over this past year configuring it, adding a number of new applications and fighting with obstacles that were presented at every step. So I am not willing, or able to repeat that dedication of effort. But I have another option. I have two hard disks in my CPU and one is vacant. So I could install Gutsy on the vacant HD and run Dapper and Gutsy side by side, putting the latest version of Ekiga in Gutsy and continue with my efforts to activate my webcam there. But this plan depends on whether you are going to provide an Ekiga download file for Gutsy. I am therefore in your hands and will appreciate your comments on this point. Thanks again for your friendly help. Ian Murdoch. -------------- next part -------------- An HTML attachment was scrubbed... URL: From sevmek at free.fr Fri Oct 26 00:27:54 2007 From: sevmek at free.fr (yannick) Date: Fri, 26 Oct 2007 02:27:54 +0200 Subject: [Ekiga-list] Ekiga quits, (crashes?), when I click on the Webcam icon, or on the "Test Video Device" button in the Druid. In-Reply-To: <60d2a91a0710251553p6b476dd8sfed64bacc340c905@mail.gmail.com> References: <60d2a91a0710251553p6b476dd8sfed64bacc340c905@mail.gmail.com> Message-ID: <1193358475.19230.7.camel@achille> Hi, A third option is to install in chroot in your dapper, like i did here for the SVN version: http://wiki.ekiga.org/index.php/Talk:Additional_Information Regards, Yannick Le jeudi 25 octobre 2007 ? 17:53 -0500, Ian Murdoch a ?crit : > Hi Damien and Kilian, > Thanks for your instant and most helpful replies. I have just been to > the Ubuntu website to check out my options for upgrading and have > found that the situation is not so simple. Feisty, Version 7.04 is now > obsolete and is no longer available for downloading, having been > superceded by a new release, Version 7.10, called Gutsy, (would you > believe?). I cannot upgrade to it because it is one release removed > from my Dapper, (it is only possible to upgrade from one release to > the next). So I would have to install it, which would wipe out my > Dapper. I am not willing to do that because my Dapper is highly > configured now for my particular usage needs. I have spent many hours > over this past year configuring it, adding a number of new > applications and fighting with obstacles that were presented at every > step. So I am not willing, or able to repeat that dedication of > effort. > But I have another option. I have two hard disks in my CPU and one is > vacant. So I could install Gutsy on the vacant HD and run Dapper and > Gutsy side by side, putting the latest version of Ekiga in Gutsy and > continue with my efforts to activate my webcam there. But this plan > depends on whether you are going to provide an Ekiga download file for > Gutsy. I am therefore in your hands and will appreciate your comments > on this point. Thanks again for your friendly help. Ian Murdoch. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From sevmek at free.fr Fri Oct 26 00:32:11 2007 From: sevmek at free.fr (yannick) Date: Fri, 26 Oct 2007 02:32:11 +0200 Subject: [Ekiga-list] only 2 working audio codecs In-Reply-To: References: <1193340000.4169.0.camel@scorpion> Message-ID: <1193358731.19230.10.camel@achille> Le jeudi 25 octobre 2007 ? 12:51 -0700, sam chan a ?crit : > > Damien, > > when i tested this, i just used the echo test(500 at ekiga.net). > i don't believe it's related to what's at the other end. > The echo test *only* support PCM and iLBC, thus any other audio codec wont work. Regards, Yannick > i do have speex installed. might i be needing another package? > > > -sam > > > ps > > (i actually haven't used ekiga wither another voip peer > since i don't know any who uses this; besides skype) > > > > On Thu, 25 Oct 2007, Damien Sandras wrote: > > >=20 > Le jeudi 25 octobre 2007 =C3=A0 10:26 -0700, sam chan a =C3=A9crit : > >=20 > > Fedora 7 > > ekiga 2.0.11 > >=20 > >=20 > > i'm having a problem using audio codecs other than PCMAU and > > iLBC. if select just one codec at a time to test, it's just > > these two that work. not even speex works. > >=20 > > when it doesn't work, a call simply hangs up after a second or > > two without anything happening. > >=20 > > any ideas? thanks. > > Does the remote peer support other codecs than PCMU/A and iLBC ? > --=20 > _ Damien Sandras > (o- =20 > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > =20 > > _______________________________________________ > 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 > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From ompaul at eircom.net Fri Oct 26 06:53:08 2007 From: ompaul at eircom.net (Paul O'Malley) Date: Fri, 26 Oct 2007 07:53:08 +0100 Subject: [Ekiga-list] Ekiga quits, (crashes?), when I click on the Webcam icon, or on the "Test Video Device" button in the Druid. In-Reply-To: <60d2a91a0710251553p6b476dd8sfed64bacc340c905@mail.gmail.com> References: <60d2a91a0710251553p6b476dd8sfed64bacc340c905@mail.gmail.com> Message-ID: <47218ED4.9050801@eircom.net> Ian Murdoch wrote: > Hi Damien and Kilian, > Thanks for your instant and most helpful replies. I have just been to the > Ubuntu website to check out my options for upgrading and have found that the > situation is not so simple. Feisty, Version 7.04 is now obsolete and is no > longer available for downloading, having been superceded by a new release, > Version 7.10, called Gutsy, (would you believe?). I cannot upgrade to it > because it is one release removed from my Dapper, (it is only possible to > upgrade from one release to the next). So I would have to install it, which > would wipe out my Dapper. I am not willing to do that because my Dapper is > highly configured now for my particular usage needs. I have spent many hours > over this past year configuring it, adding a number of new applications and > fighting with obstacles that were presented at every step. So I am not > willing, or able to repeat that dedication of effort. > But I have another option. I have two hard disks in my CPU and one is > vacant. So I could install Gutsy on the vacant HD and run Dapper and Gutsy > side by side, putting the latest version of Ekiga in Gutsy and continue > with my efforts to activate my webcam there. But this plan depends on > whether you are going to provide an Ekiga download file for Gutsy. I am > therefore in your hands and will appreciate your comments on this point. > Thanks again for your friendly help. Ian Murdoch. Hi Ian, You can obtain edgy and feisty from http://ie.releases.ubuntu.com/ However as with Debian if you jump versions you may not have the most pleasant of experiences. Personally if I was moving from dapper given the internal structures changes to Ubuntu I would jump on the fresh install route, and choose whichever version you want. Regards, Paul O'Malley From schan at cs.ucr.edu Fri Oct 26 07:30:42 2007 From: schan at cs.ucr.edu (sam chan) Date: Fri, 26 Oct 2007 00:30:42 -0700 (PDT) Subject: [Ekiga-list] only 2 working audio codecs In-Reply-To: <1193358731.19230.10.camel@achille> References: <1193340000.4169.0.camel@scorpion> <1193358731.19230.10.camel@achille> Message-ID: ok. that explains it. thanks. -sam On Fri, 26 Oct 2007, yannick wrote: > Le jeudi 25 octobre 2007 ?? 12:51 -0700, sam chan a ??crit : > > Damien, > > when i tested this, i just used the echo test(500 at ekiga.net). > i don't believe it's related to what's at the other end. > The echo test *only* support PCM and iLBC, thus any other audio codec wont work. Regards, Yannick From jklawiter at gmail.com Fri Oct 26 10:13:54 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Fri, 26 Oct 2007 12:13:54 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How Message-ID: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> Hello all! After months (years? ;-) of waiting we have now working bluetooth audio service in Linux without any magic it just works (ok, sometimes not, but till now it can be only better :-). The problem is i don't know how to tel Ekiga that i want to use bluetooth audio device instead of Intel sound card built into my laptop. Is it possible? If not, maybe it will be possible soon (before ekiga3)? -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From njaal at itek.norut.no Fri Oct 26 12:48:21 2007 From: njaal at itek.norut.no (=?ISO-8859-1?Q?Nj=E5l?= Borch) Date: Fri, 26 Oct 2007 14:48:21 +0200 Subject: [Ekiga-list] CIF over h261 on Ekiga 2.0 In-Reply-To: <1191600151.7486.19.camel@scorpion> References: <1191585324.10701.0.camel@seer2.itek.norut.no> <1191600151.7486.19.camel@scorpion> Message-ID: <1193402901.14789.0.camel@seer2.itek.norut.no> Hi, and thanks for the quick reply! On Fri, 2007-10-05 at 18:02 +0200, Damien Sandras wrote: > Hello, > > Le vendredi 05 octobre 2007 ? 13:55 +0200, Nj?l Borch a ?crit : > > Is there any special reason that Ekiga has "lost" the ability to use CIF > > resolution? Specially since it apparently can handle it well if the > > remote client sends it? Is there an easy fix? > > You can try the SVN snapshot : > http://snapshots.seconix.com/ > > The feature is back. We tried the snapshot, but it is quite different and not very stable. I was more wondering about whether there is an "easy fix" to enable CIF again. As I could see from the Ekiga source (2.0.11), both QCIF and CIF seems to be supported. Is it from the underlying libraries? I am quite able to code myself, but without any pointers I'll spend too much time reading code. :-) If I fix it, I will of course provide a patch for the community to re-enable CIF for Ekiga 2.0.11 (or whatever library requires changes). Best regards, Nj?l From dsandras at seconix.com Fri Oct 26 15:50:29 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Oct 2007 17:50:29 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> Message-ID: <1193413829.14114.15.camel@scorpion> Le vendredi 26 octobre 2007 ? 12:13 +0200, Jakub Klawiter a ?crit : > Hello all! > > After months (years? ;-) of waiting we have now working bluetooth > audio service in Linux without any magic it just works (ok, sometimes > not, but till now it can be only better :-). > > The problem is i don't know how to tel Ekiga that i want to use > bluetooth audio device instead of Intel sound card built into my > laptop. Is it possible? If not, maybe it will be possible soon (before > ekiga3)? > Can you use the Bluetooth headset using ALSA ? (aplay and arecord) -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Fri Oct 26 15:51:44 2007 From: dsandras at seconix.com (Damien Sandras) Date: Fri, 26 Oct 2007 17:51:44 +0200 Subject: [Ekiga-list] CIF over h261 on Ekiga 2.0 In-Reply-To: <1193402901.14789.0.camel@seer2.itek.norut.no> References: <1191585324.10701.0.camel@seer2.itek.norut.no> <1191600151.7486.19.camel@scorpion> <1193402901.14789.0.camel@seer2.itek.norut.no> Message-ID: <1193413904.14114.18.camel@scorpion> Le vendredi 26 octobre 2007 ? 14:48 +0200, Nj?l Borch a ?crit : > Hi, and thanks for the quick reply! > > On Fri, 2007-10-05 at 18:02 +0200, Damien Sandras wrote: > > Hello, > > > > Le vendredi 05 octobre 2007 ? 13:55 +0200, Nj?l Borch a ?crit : > > > Is there any special reason that Ekiga has "lost" the ability to use CIF > > > resolution? Specially since it apparently can handle it well if the > > > remote client sends it? Is there an easy fix? > > > > You can try the SVN snapshot : > > http://snapshots.seconix.com/ > > > > The feature is back. > > We tried the snapshot, but it is quite different and not very stable. I It should not be that unstable... > was more wondering about whether there is an "easy fix" to enable CIF > again. As I could see from the Ekiga source (2.0.11), both QCIF and CIF > seems to be supported. Is it from the underlying libraries? > > I am quite able to code myself, but without any pointers I'll spend too > much time reading code. :-) > > If I fix it, I will of course provide a patch for the community to > re-enable CIF for Ekiga 2.0.11 (or whatever library requires changes). There is no easy fix. However, I think I remember there was a GConf key in the Ekiga arborescence to force video to large. The key is video_size, and if I remember correctly, it should be set to "1". -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From rankincj at yahoo.com Fri Oct 26 16:10:05 2007 From: rankincj at yahoo.com (Chris Rankin) Date: Fri, 26 Oct 2007 17:10:05 +0100 (BST) Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <1193413829.14114.15.camel@scorpion> Message-ID: <344497.69612.qm@web52909.mail.re2.yahoo.com> --- Damien Sandras wrote: > Can you use the Bluetooth headset using ALSA ? (aplay and arecord) There's a Bluetooth Wiki that describes how to do this: http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset The problem is that headsets are now PCM plugin devices rather than hardware devices. So you need to be able to tell ekiga to use an ALSA device that you have defined yourself in your .asoundrc file. Failing that, perhaps you could temporarily make your headset the "default" device? Cheers, Chris ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ From jklawiter at gmail.com Fri Oct 26 18:32:39 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Fri, 26 Oct 2007 20:32:39 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <1193413829.14114.15.camel@scorpion> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> <1193413829.14114.15.camel@scorpion> Message-ID: <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> Hello! On 10/26/07, Damien Sandras wrote: > > The problem is i don't know how to tel Ekiga that i want to use > > bluetooth audio device instead of Intel sound card built into my > > laptop. Is it possible? If not, maybe it will be possible soon (before > > ekiga3)? > Can you use the Bluetooth headset using ALSA ? (aplay and arecord) Yes I can. As described here: http://wiki.bluez.org/wiki/HOWTO/AudioDevices I can test the device: $ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE or $ gst-launch-0.10 -v alsasrc device=bluetooth ! audioconvert ! audioresample ! alsasink device=bluetooth sync=false same time I can listen music via built in sound card, so it is working I just don't know how to "tell ekiga" that it should use pcm_bluetooth (?) device. -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From jklawiter at gmail.com Fri Oct 26 18:35:46 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Fri, 26 Oct 2007 20:35:46 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - Ho In-Reply-To: <344497.69612.qm@web52909.mail.re2.yahoo.com> References: <1193413829.14114.15.camel@scorpion> <344497.69612.qm@web52909.mail.re2.yahoo.com> Message-ID: <5dee460a0710261135w977aabw2d54c0ad9d74181f@mail.gmail.com> Hello! On 10/26/07, Chris Rankin wrote: > > Can you use the Bluetooth headset using ALSA ? (aplay and arecord) > There's a Bluetooth Wiki that describes how to do this: > http://gentoo-wiki.com/HOWTO_use_a_bluetooth_headset > > The problem is that headsets are now PCM plugin devices rather than hardware devices. So you need > to be able to tell ekiga to use an ALSA device that you have defined yourself in your .asoundrc > file. Failing that, perhaps you could temporarily make your headset the "default" device? This HowTo is obsolete, it is about old bluez, now it is much easier to start it to work. See: http://wiki.bluez.org/wiki/HOWTO/AudioDevices which is also linked to howto on gentoo wiki. -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From dsandras at seconix.com Sat Oct 27 10:06:01 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Oct 2007 12:06:01 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> <1193413829.14114.15.camel@scorpion> <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> Message-ID: <1193479561.4159.21.camel@scorpion> Le vendredi 26 octobre 2007 ? 20:32 +0200, Jakub Klawiter a ?crit : > Hello! > > On 10/26/07, Damien Sandras wrote: > > > > The problem is i don't know how to tel Ekiga that i want to use > > > bluetooth audio device instead of Intel sound card built into my > > > laptop. Is it possible? If not, maybe it will be possible soon (before > > > ekiga3)? > > Can you use the Bluetooth headset using ALSA ? (aplay and arecord) > Yes I can. As described here: http://wiki.bluez.org/wiki/HOWTO/AudioDevices > > I can test the device: > > $ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE > or > $ gst-launch-0.10 -v alsasrc device=bluetooth ! audioconvert ! > audioresample ! alsasink device=bluetooth sync=false > > same time I can listen music via built in sound card, so it is working > I just don't know how to "tell ekiga" that it should use pcm_bluetooth > (?) device. It is not possible to do it... Somebody would have to write a patch for the ALSA plugin... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From rankincj at yahoo.com Sat Oct 27 11:08:34 2007 From: rankincj at yahoo.com (Chris Rankin) Date: Sat, 27 Oct 2007 12:08:34 +0100 (BST) Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - Ho In-Reply-To: <5dee460a0710261135w977aabw2d54c0ad9d74181f@mail.gmail.com> Message-ID: <188874.51126.qm@web52912.mail.re2.yahoo.com> --- Jakub Klawiter wrote: > This HowTo is obsolete, it is about old bluez, now it is much easier > to start it to work. See: > http://wiki.bluez.org/wiki/HOWTO/AudioDevices which is also linked to > howto on gentoo wiki. Actually, I never managed to get my headset working using this HOWTO, as both aplay and arecord kept complaining about being unable to connect (to something). It wasn't until I switched to using plugz and the headsetd that I started getting sound out. Cheers, Chris ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ From paulino90 at tenbit.pl Sat Oct 27 12:32:05 2007 From: paulino90 at tenbit.pl (Pawel) Date: Sat, 27 Oct 2007 14:32:05 +0200 Subject: [Ekiga-list] G729 codec Message-ID: <18211.12229.383074.45065@localhost.localdomain> Hallo group members. I am trying to use ekiga with g729 codec according to post: http://www.mail-archive.com/ekiga-list at gnome.org/msg01886.html Unfortunatelly I failed, that is, after adding plugin to pwlib, I do not see g729 on audio codecs list in ekiga. Sould it be visible there at all? Maybe I am doing something wrong. The following is what I did: I am running fedora core 6. I put the plugin to: /usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so it is visible by ekiga: prompt$ strace ekiga .... lstat64("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so", {st_mode=S_IFREG|0755, st_size=256596, ...}) = 0 open("/usr/lib/pwlib/codecs/audio/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 24 fstat64(24, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 fcntl64(24, F_SETFD, FD_CLOEXEC) = 0 gettimeofday({1193475641, 415767}, NULL) = 0 gettimeofday({1193475641, 415906}, NULL) = 0 gettimeofday({1193475641, 415997}, NULL) = 0 getdents(24, /* 3 entries */, 4096) = 68 lstat64("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so", {st_mode=S_IFREG|0755, st_size=256596, ...}) = 0 open("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOTDIR (Not a directory) open("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so", O_RDONLY) = 25 read(25, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\200`\0"..., 512) = 512 fstat64(25, {st_mode=S_IFREG|0755, st_size=256596, ...}) = 0 mmap2(NULL, 232436, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 25, 0) = 0xb7c4d000 mmap2(0xb7c84000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 25, 0x36) = 0xb7c84000 mprotect(0xbbe000, 3792, PROT_READ|PROT_WRITE) = 0 mprotect(0xbbe000, 3792, PROT_READ) = 0 mprotect(0xbfafd000, 4096, PROT_READ|PROT_WRITE|PROT_EXEC|PROT_GROWSDOWN) = 0 close(25) = 0 mprotect(0xb7c4d000, 225280, PROT_READ|PROT_WRITE) = 0 mprotect(0xb7c4d000, 225280, PROT_READ|PROT_EXEC) = 0 brk(0x81cc000) = 0x81cc000 .... but I do not have additional option to choose in audio codecs for g729 codec in ekiga. I am running: pwlib-1.10.4-1.fc6 ekiga-2.0.5-3.fc6 opal-2.2.5-1.fc6 Have You got any ideas? Regards, Pawel From jklawiter at gmail.com Sat Oct 27 12:23:47 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Sat, 27 Oct 2007 14:23:47 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <1193479561.4159.21.camel@scorpion> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> <1193413829.14114.15.camel@scorpion> <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> <1193479561.4159.21.camel@scorpion> Message-ID: <5dee460a0710270523h5e78ed13u194e203e0a425eac@mail.gmail.com> Hello! On 10/27/07, Damien Sandras wrote: > > $ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE > > or > > $ gst-launch-0.10 -v alsasrc device=bluetooth ! audioconvert ! > > audioresample ! alsasink device=bluetooth sync=false > > > > same time I can listen music via built in sound card, so it is working > > I just don't know how to "tell ekiga" that it should use pcm_bluetooth > > (?) device. > > It is not possible to do it... Somebody would have to write a patch for > the ALSA plugin... :( It is not possible and will not be possible? BT headset can be very useful for ekiga while it is not using soundcard, so You can still listen music while talking via ekiga. And of course BT headset means no cables ;-) -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From jpuydt at free.fr Sat Oct 27 12:24:40 2007 From: jpuydt at free.fr (Julien Puydt) Date: Sat, 27 Oct 2007 14:24:40 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <18211.12229.383074.45065@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> Message-ID: <47232E08.6020003@free.fr> Pawel a ?crit : > Unfortunatelly I failed, that is, after adding plugin to pwlib, I do not see g729 on audio codecs list in ekiga. Sould it be visible there at all? Maybe I am doing something wrong. > it is visible by ekiga: > prompt$ strace ekiga > > Have You got any ideas? Does "ekiga -d 4" complain? Snark on #ekiga From dsandras at seconix.com Sat Oct 27 12:30:38 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Oct 2007 14:30:38 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <5dee460a0710270523h5e78ed13u194e203e0a425eac@mail.gmail.com> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> <1193413829.14114.15.camel@scorpion> <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> <1193479561.4159.21.camel@scorpion> <5dee460a0710270523h5e78ed13u194e203e0a425eac@mail.gmail.com> Message-ID: <1193488238.4164.5.camel@scorpion> Le samedi 27 octobre 2007 ? 14:23 +0200, Jakub Klawiter a ?crit : > Hello! > > On 10/27/07, Damien Sandras wrote: > > > $ arecord -D bluetooth -f S16_LE | aplay -D bluetooth -f S16_LE > > > or > > > $ gst-launch-0.10 -v alsasrc device=bluetooth ! audioconvert ! > > > audioresample ! alsasink device=bluetooth sync=false > > > > > > same time I can listen music via built in sound card, so it is working > > > I just don't know how to "tell ekiga" that it should use pcm_bluetooth > > > (?) device. > > > > It is not possible to do it... Somebody would have to write a patch for > > the ALSA plugin... > :( It is not possible and will not be possible? BT headset can be very > useful for ekiga while it is not using soundcard, so You can still > listen music while talking via ekiga. And of course BT headset means > no cables ;-) It is possible, but not currently. Somebody has to implement it... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From paulino90 at tenbit.pl Sat Oct 27 12:48:38 2007 From: paulino90 at tenbit.pl (Pawel) Date: Sat, 27 Oct 2007 14:48:38 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <47232E08.6020003@free.fr> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> Message-ID: <18211.13222.682696.228691@localhost.localdomain> Hallo Julien Julien Puydt writes: > Pawel a ?crit : > > Unfortunatelly I failed, that is, after adding plugin to pwlib, I do not see g729 on audio codecs list in ekiga. Sould it be visible there at all? Maybe I am doing something wrong. > > > it is visible by ekiga: > > prompt$ strace ekiga > > > > > Have You got any ideas? > > Does "ekiga -d 4" complain? > > Snark on #ekiga > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list No, it does not, but I do not see any strings that would confirm that ekiga noticed plugin. The following is the beginning of trace: 2007/10/27 14:38:58.266 0:00.424 ekiga Detected audio plugins: ALSA 2007/10/27 14:38:58.282 0:00.425 ekiga Detected video plugins: Picture,V4L,V4L2,1394AVC 2007/10/27 14:38:58.282 0:00.425 ekiga Detected audio plugins: ALSA 2007/10/27 14:38:58.282 0:00.425 ekiga Detected video plugins: Picture,V4L,V4L2,1394AVC 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following audio input devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following audio output devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following video input devices: No device found with plugin V4L 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following audio input devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 14:38:58.307 0:00.450 ekiga Detected the following audio output devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 14:38:58.307 0:00.450 ekiga Detected the following video input devices: No device found with plugin V4L 2007/10/27 14:38:59.190 0:01.333 ekiga Ekiga version 2.0.5 I noticed that ekiga found alsa plugin, so I put g729 to the same directory as alsa plugin, but I got the same result. Regards From rankincj at yahoo.com Sat Oct 27 12:51:17 2007 From: rankincj at yahoo.com (Chris Rankin) Date: Sat, 27 Oct 2007 13:51:17 +0100 (BST) Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <1193488238.4164.5.camel@scorpion> Message-ID: <123125.25631.qm@web52901.mail.re2.yahoo.com> --- Damien Sandras wrote: > It is possible, but not currently. Somebody has to implement it... http://bluetooth-alsa.sourceforge.net/build.html Interestingly enough, this link mentions patches for pwlib under the "Configure ekiga" section. Cheers, Chris ___________________________________________________________ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html From fonz at siol.net Sat Oct 27 12:58:28 2007 From: fonz at siol.net (Jure Petrovic) Date: Sat, 27 Oct 2007 14:58:28 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <18211.13222.682696.228691@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> Message-ID: <1193489908.24740.4.camel@localhost.localdomain> Hello, yes the G729 option should be visible. Do you have intel IPP library installed? The g729_audio_plugin.so binary is linked against it. You can try with ipp 5.1, and if it won't work you'll have to recompile the plugin using the included build script. Regards, Jure On Sat, 2007-10-27 at 14:48 +0200, Pawel wrote: > Hallo Julien > Julien Puydt writes: > > Pawel a ?crit : > > > Unfortunatelly I failed, that is, after adding plugin to pwlib, I do not see g729 on audio codecs list in ekiga. Sould it be visible there at all? Maybe I am doing something wrong. > > > > > it is visible by ekiga: > > > prompt$ strace ekiga > > > > > > > > Have You got any ideas? > > > > Does "ekiga -d 4" complain? > > > > Snark on #ekiga > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > > > No, it does not, but I do not see any strings that would confirm that ekiga noticed plugin. The following is the beginning of trace: > > 2007/10/27 14:38:58.266 0:00.424 ekiga Detected audio plugins: ALSA > 2007/10/27 14:38:58.282 0:00.425 ekiga Detected video plugins: Picture,V4L,V4L2,1394AVC > 2007/10/27 14:38:58.282 0:00.425 ekiga Detected audio plugins: ALSA > 2007/10/27 14:38:58.282 0:00.425 ekiga Detected video plugins: Picture,V4L,V4L2,1394AVC > 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following audio input devices: Default,Intel 82801BA-ICH2 with plugin ALSA > 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following audio output devices: Default,Intel 82801BA-ICH2 with plugin ALSA > 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following video input devices: No device found with plugin V4L > 2007/10/27 14:38:58.306 0:00.449 ekiga Detected the following audio input devices: Default,Intel 82801BA-ICH2 with plugin ALSA > 2007/10/27 14:38:58.307 0:00.450 ekiga Detected the following audio output devices: Default,Intel 82801BA-ICH2 with plugin ALSA > 2007/10/27 14:38:58.307 0:00.450 ekiga Detected the following video input devices: No device found with plugin V4L > 2007/10/27 14:38:59.190 0:01.333 ekiga Ekiga version 2.0.5 > > > I noticed that ekiga found alsa plugin, so I put g729 to the same directory as alsa plugin, but I got the same result. > > Regards > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list From jklawiter at gmail.com Sat Oct 27 13:06:13 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Sat, 27 Oct 2007 15:06:13 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <1193488238.4164.5.camel@scorpion> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> <1193413829.14114.15.camel@scorpion> <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> <1193479561.4159.21.camel@scorpion> <5dee460a0710270523h5e78ed13u194e203e0a425eac@mail.gmail.com> <1193488238.4164.5.camel@scorpion> Message-ID: <5dee460a0710270606v4d7a9a66lce73818306c8c3a6@mail.gmail.com> Hello! On 10/27/07, Damien Sandras wrote: > > :( It is not possible and will not be possible? BT headset can be very > > useful for ekiga while it is not using soundcard, so You can still > > listen music while talking via ekiga. And of course BT headset means > > no cables ;-) > It is possible, but not currently. Somebody has to implement it... I understand this, my question is, what do you think somebody will ... I don't know before Ekiga3? I understand that it will not be possible in near future (if somebody havr to do this), but is is possible that there is somebody in the Ekga team, who know how, and probably will do this, because it is usefull, and it is also possible that nobody will work on this task, because there is nobody (in the team) interested in this feature. I know the question is crazy but ...maybe it is possoble to answer. ;-) -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From dsandras at seconix.com Sat Oct 27 13:07:44 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Oct 2007 15:07:44 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <123125.25631.qm@web52901.mail.re2.yahoo.com> References: <123125.25631.qm@web52901.mail.re2.yahoo.com> Message-ID: <1193490464.4164.19.camel@scorpion> Le samedi 27 octobre 2007 ? 13:51 +0100, Chris Rankin a ?crit : > --- Damien Sandras wrote: > > It is possible, but not currently. Somebody has to implement it... > > http://bluetooth-alsa.sourceforge.net/build.html > > Interestingly enough, this link mentions patches for pwlib under the "Configure ekiga" section. > If it works, I'm ready to improve it and include it. They always list the Bluetooth headset. I can certainly find a way to discover if a headset is being plugged or not. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Sat Oct 27 13:08:26 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sat, 27 Oct 2007 15:08:26 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <5dee460a0710270606v4d7a9a66lce73818306c8c3a6@mail.gmail.com> References: <5dee460a0710260313q763f7cfan7fc66716b341012d@mail.gmail.com> <1193413829.14114.15.camel@scorpion> <5dee460a0710261132r78c03730je61e64418ea7009c@mail.gmail.com> <1193479561.4159.21.camel@scorpion> <5dee460a0710270523h5e78ed13u194e203e0a425eac@mail.gmail.com> <1193488238.4164.5.camel@scorpion> <5dee460a0710270606v4d7a9a66lce73818306c8c3a6@mail.gmail.com> Message-ID: <1193490506.4164.21.camel@scorpion> Le samedi 27 octobre 2007 ? 15:06 +0200, Jakub Klawiter a ?crit : > Hello! > > On 10/27/07, Damien Sandras wrote: > > > > :( It is not possible and will not be possible? BT headset can be very > > > useful for ekiga while it is not using soundcard, so You can still > > > listen music while talking via ekiga. And of course BT headset means > > > no cables ;-) > > It is possible, but not currently. Somebody has to implement it... > I understand this, my question is, what do you think somebody will ... > I don't know before Ekiga3? I understand that it will not be possible > in near future (if somebody havr to do this), but is is possible that > there is somebody in the Ekga team, who know how, and probably will do > this, because it is usefull, and it is also possible that nobody will > work on this task, because there is nobody (in the team) interested in > this feature. > I know the question is crazy but ...maybe it is possoble to answer. ;-) I certainly would like that somebody does this. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From jklawiter at gmail.com Sat Oct 27 13:18:13 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Sat, 27 Oct 2007 15:18:13 +0200 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - H In-Reply-To: <188874.51126.qm@web52912.mail.re2.yahoo.com> References: <5dee460a0710261135w977aabw2d54c0ad9d74181f@mail.gmail.com> <188874.51126.qm@web52912.mail.re2.yahoo.com> Message-ID: <5dee460a0710270618h3b36ed4aqecb6d3e1d01928ff@mail.gmail.com> Hello! On 10/27/07, Chris Rankin wrote: > > This HowTo is obsolete, it is about old bluez, now it is much easier > > to start it to work. See: > > http://wiki.bluez.org/wiki/HOWTO/AudioDevices which is also linked to > > howto on gentoo wiki. > > Actually, I never managed to get my headset working using this HOWTO, as both aplay and arecord > kept complaining about being unable to connect (to something). It wasn't until I switched to using > plugz and the headsetd that I started getting sound out. Under gentoo? I'm asking about distro because you have sent the link to gentoo wiki before. Here it just works, thinks what I did: 1. unmask ~x86 keyword for bluez-utils-3.22, bluez-libs-3.22, bluez-gnome-0.14 2. add modules to kernel (hope i'm copying all) # Network testing CONFIG_BT=m CONFIG_BT_L2CAP=m CONFIG_BT_SCO=m CONFIG_BT_RFCOMM=m CONFIG_BT_RFCOMM_TTY=y CONFIG_BT_HIDP=m # Bluetooth device drivers CONFIG_BT_HCIUSB=m CONFIG_BT_HCIUSB_SCO=y 3. emerge -avD bluez-gnome 3a. you can also emerge gnome-extra/gnome-vfs-obexftp if you want to browse e.g. mobile phone files ebuild is available in ecatmur overlay 4. plug in the BT dongle ;-) 5. authorize the headset via bluez-gnome 6. in services tab activate audio service and it's as I remember all -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From paulino90 at tenbit.pl Sat Oct 27 15:33:56 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sat, 27 Oct 2007 17:33:56 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <1193489908.24740.4.camel@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> Message-ID: <18211.23140.416476.656135@localhost.localdomain> Hello Jure Jure Petrovic writes: > Hello, > > yes the G729 option should be visible. > > Do you have intel IPP library installed? The g729_audio_plugin.so binary > is linked against it. > > You can try with ipp 5.1, and if it won't work you'll have to recompile > the plugin using the included build script. > > Regards, > Jure > my compilation fails on: prompt$ ./build.sh Cleaning up... Starting g729 build process... Compiling util_d.c... Compiling util_e.c... Compiling encg729.c... Compiling owng729fp.c... Compiling usc729fp.c... Compiling vm_thread_linux_32.c... Compiling decg729fp.c... Compiling myg729.c... Compiling main.c... Compiling g729codec.c... src/g729codec.c:22:30: error: codec/opalplugin.h: No such file or directory src/g729codec.c:27: error: expected declaration specifiers or ?...? before string constant In file included from /usr/include/stdio.h:34, from src/g729codec.c:29: /usr/lib/gcc/i386-redhat-linux/4.1.1/include/stddef.h: In function ?PLUGIN_CODEC_IMPLEMENT?: /usr/lib/gcc/i386-redhat-linux/4.1.1/include/stddef.h:214: error: storage class specified for parameter ?size_t? In file included from /usr/include/stdio.h:36, from src/g729codec.c:29: /usr/include/bits/types.h:34: error: storage class specified for parameter ?__u_char? /usr/include/bits/types.h:35: error: storage class specified for parameter ?__u_short? /usr/include/bits/types.h:36: error: storage class specified for parameter ?__u_int? I found out that opalplugin.h is included in openh323, but it is not in "codec" directory there. Where should I get it from. Regards, Pawel From paulino90 at tenbit.pl Sat Oct 27 15:36:14 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sat, 27 Oct 2007 17:36:14 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <1193489908.24740.4.camel@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> Message-ID: <18211.23278.865329.310635@localhost.localdomain> Jure Petrovic writes: > Hello, > > yes the G729 option should be visible. > > Do you have intel IPP library installed? The g729_audio_plugin.so binary > is linked against it. > > You can try with ipp 5.1, and if it won't work you'll have to recompile > the plugin using the included build script. > > Regards, > Jure > > I orgot to mention that I am compiling it against ipp/5.2. From fonz at siol.net Sat Oct 27 15:40:39 2007 From: fonz at siol.net (Jure Petrovic) Date: Sat, 27 Oct 2007 17:40:39 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <18211.23278.865329.310635@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> Message-ID: <1193499639.25244.4.camel@localhost.localdomain> opalplugin.h header file comes with opal package. I used opal from svn. You can edit build.sh script accordingly so that the paths inside will suit your needs. It's very basic script actually. Jure On Sat, 2007-10-27 at 17:36 +0200, PawelCarqowski wrote: > Jure Petrovic writes: > I orgot to mention that I am compiling it against ipp/5.2. From razametal at gmail.com Sat Oct 27 16:25:21 2007 From: razametal at gmail.com (RazaMetaL | Only The Good Die Young) Date: Sat, 27 Oct 2007 11:25:21 -0500 Subject: [Ekiga-list] G729 codec In-Reply-To: <1193499639.25244.4.camel@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> Message-ID: On 10/27/07, Jure Petrovic wrote: > > opalplugin.h header file comes with opal package. I used opal from svn. > > You can edit build.sh script accordingly so that the paths inside will > suit your needs. It's very basic script actually. > > Jure There is any binary g729 module? I can not install ipp from intel. Sorry, -- Linux User: 255902 Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html From paulino90 at tenbit.pl Sat Oct 27 16:43:29 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sat, 27 Oct 2007 18:43:29 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <1193499639.25244.4.camel@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> Message-ID: <18211.27313.814803.447934@localhost.localdomain> Jure Petrovic writes: > > opalplugin.h header file comes with opal package. I used opal from svn. > > You can edit build.sh script accordingly so that the paths inside will > suit your needs. It's very basic script actually. > > Jure > > > On Sat, 2007-10-27 at 17:36 +0200, PawelCarqowski wrote: > > Jure Petrovic writes: > > > I orgot to mention that I am compiling it against ipp/5.2. > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Jure, I compiled plugin with ipp 5.2 and installed it to ekiga, but unfortunatelly ekiga does not see the plugin: prompt$ ekiga -d 4 2007/10/27 18:34:41.867 0:00.429 ekiga Detected audio plugins: ALSA 2007/10/27 18:34:41.868 0:00.429 ekiga Detected video plugins: Picture,V4L,V4L2,1394AVC 2007/10/27 18:34:41.868 0:00.429 ekiga Detected audio plugins: ALSA 2007/10/27 18:34:41.868 0:00.429 ekiga Detected video plugins: Picture,V4L,V4L2,1394AVC 2007/10/27 18:34:41.891 0:00.452 ekiga Detected the following audio input devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 18:34:41.891 0:00.452 ekiga Detected the following audio output devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 18:34:41.891 0:00.452 ekiga Detected the following video input devices: No device found with plugin V4L 2007/10/27 18:34:41.891 0:00.452 ekiga Detected the following audio input devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 18:34:41.892 0:00.453 ekiga Detected the following audio output devices: Default,Intel 82801BA-ICH2 with plugin ALSA 2007/10/27 18:34:41.892 0:00.453 ekiga Detected the following video input devices: No device found with plugin V4L prompt$ ldd /usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so linux-gate.so.1 => (0xb7f49000) libguide.so => /opt/intel/ipp/5.2/ia32/sharedlib/libguide.so (0xb7edf000) libippsc.so.5.2 => /opt/intel/ipp/5.2/ia32/sharedlib/libippsc.so.5.2 (0xb7ed2000) libippsr.so.5.2 => /opt/intel/ipp/5.2/ia32/sharedlib/libippsr.so.5.2 (0xb7ebc000) libipps.so.5.2 => /opt/intel/ipp/5.2/ia32/sharedlib/libipps.so.5.2 (0xb7e84000) libippcore.so.5.2 => /opt/intel/ipp/5.2/ia32/sharedlib/libippcore.so.5.2 (0xb7e7d000) libpthread.so.0 => /lib/libpthread.so.0 (0xb7e65000) libm.so.6 => /lib/libm.so.6 (0xb7e3e000) libc.so.6 => /lib/libc.so.6 (0xb7d01000) libdl.so.2 => /lib/libdl.so.2 (0xb7cfd000) /lib/ld-linux.so.2 (0x80000000) prompt $ strace ekiga lstat64("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so", {st_mode=S_IFREG|0775, st_size=100459, ...}) = 0 open("/usr/lib/pwlib/codecs/audio/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 24 fstat64(24, {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0 fcntl64(24, F_SETFD, FD_CLOEXEC) = 0 gettimeofday({1193502947, 203367}, NULL) = 0 gettimeofday({1193502947, 203432}, NULL) = 0 gettimeofday({1193502947, 203496}, NULL) = 0 getdents(24, /* 3 entries */, 4096) = 68 lstat64("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so", {st_mode=S_IFREG|0775, st_size=100459, ...}) = 0 open("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so/", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = -1 ENOTDIR (Not a directory) open("/usr/lib/pwlib/codecs/audio/g729_audio_pwplugin.so", O_RDONLY) = 25 read(25, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0 @\0\000"..., 512) = 512 fstat64(25, {st_mode=S_IFREG|0775, st_size=100459, ...}) = 0 mmap2(NULL, 93684, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 25, 0) = 0xb7c4b000 mmap2(0xb7c61000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 25, 0x15) = 0xb7c61000 close(25) = 0 prompt$ cat build.sh echo "Cleaning up..." rm -rf ./bin/* echo "Starting g729 build process..." IPP_DIR=/opt/intel/ipp/5.2/ia32 ##${IPP_PX_H}="-include ${IPP_DIR}/tools/staticlib/ipp_px.h" IPP_PX_H="" echo "Compiling util_d.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/util_d.o api/util_d.c echo "Compiling util_e.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/util_e.o api/util_e.c echo "Compiling encg729.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/encg729fp.o api/encg729fp.c echo "Compiling owng729fp.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/owng729fp.o api/owng729fp.c echo "Compiling usc729fp.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/usc729fp.o api/usc729fp.c echo "Compiling vm_thread_linux_32.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/vm_thread_linux32.o vm/src/vm_thread_linux32.c echo "Compiling decg729fp.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/decg729fp.o api/decg729fp.c echo "Compiling myg729.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -o bin/myg729.o src/myg729.c echo "Compiling main.c..." gcc -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -fPIC -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O2 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -o bin/main.o src/main.c echo "Compiling g729codec.c..." gcc -I /usr/local/include/opal -I./include -I./vm/include -I${IPP_DIR}/include ${IPP_PX_H} -include /usr/src/openh323_v1_19_0_1/include/opalplugin.h -fPIC -D__unix__ -Dlinux -Dlinux32 -DNDEBUG -DLINUX32 -DNO_SCRATCH_MEMORY_USED -c -O6 -march=pentium2 -ffast-math -fomit-frame-pointer -DIPPCORE_NO_SSE -obin/g729codec.o src/g729codec.c echo "Linking main..." gcc -o bin/main bin/main.o bin/util_e.o bin/util_d.o bin/myg729.o bin/decg729fp.o bin/encg729fp.o bin/owng729fp.o bin/usc729fp.o bin/vm_thread_linux32.o -L${IPP_DIR}/sharedlib -lguide -lippsc -lippsr -lipps -lippcore -lpthread -lm echo "Linking g729 audio plugin in shared library..." gcc -shared -Wl,-soname,g729 -o bin/g729_audio_pwplugin.so bin/g729codec.o bin/myg729.o bin/util_e.o bin/util_d.o bin/decg729fp.o bin/encg729fp.o bin/owng729fp.o bin/usc729fp.o bin/vm_thread_linux32.o -L${IPP_DIR}/sharedlib -lguide -lippsc -lippsr -lipps -lippcore -lpthread -lm echo "Done." Have You got any ideas, what might be the reason? Regards, Pawel From fonz at siol.net Sat Oct 27 16:35:57 2007 From: fonz at siol.net (Jure Petrovic) Date: Sat, 27 Oct 2007 18:35:57 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> Message-ID: <1193502957.25606.2.camel@localhost.localdomain> Sorry, but for the moment g729 ekiga codec is dinamically linked against intel ipp. Jure On Sat, 2007-10-27 at 11:25 -0500, RazaMetaL | Only The Good Die Young wrote: > There is any binary g729 module? I can not install ipp from intel. From fonz at siol.net Sat Oct 27 16:48:37 2007 From: fonz at siol.net (Jure Petrovic) Date: Sat, 27 Oct 2007 18:48:37 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <18211.27313.814803.447934@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> <18211.27313.814803.447934@localhost.localdomain> Message-ID: <1193503717.25606.9.camel@localhost.localdomain> Please note the software versions, mentioned in my original mail: ekiga 2.1.0 opal 2.3.2 pwlib 1.11.5 All those packages were from svn at that time. I had to compile all of them myself because opal did not support dynamic module loading before 2.3.* Are you using original opal that comes with fc6? In opal 2.2.5 all codecs are linked within libopal... Jure On Sat, 2007-10-27 at 18:43 +0200, PawelCarqowski wrote: > > Have You got any ideas, what might be the reason? > From paulino90 at tenbit.pl Sat Oct 27 17:07:33 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sat, 27 Oct 2007 19:07:33 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <1193503717.25606.9.camel@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> <18211.27313.814803.447934@localhost.localdomain> <1193503717.25606.9.camel@localhost.localdomain> Message-ID: <18211.28757.284045.162540@localhost.localdomain> Jure Petrovic writes: > > > Please note the software versions, mentioned in my original mail: > > ekiga 2.1.0 > opal 2.3.2 > pwlib 1.11.5 > > All those packages were from svn at that time. I had to compile all of > them myself because opal did not support dynamic module loading before > 2.3.* > > Are you using original opal that comes with fc6? Yes I do. Build host: ls20-bc1-14.build.redhat.com. prompt$ rpm -qi opal Name : opal Relocations: (not relocatable) Version : 2.2.5 Vendor: Red Hat, Inc. Release : 1.fc6 Build Date: Wed 14 Feb 2007 04:24:43 PM CET Install Date: Thu 22 Mar 2007 08:48:27 PM CET Build Host: ls20-bc1-14.build.redhat.com Group : System Environment/Libraries Source RPM: opal-2.2.5-1.fc6.src.rpm Size : 11012907 License: MPL Signature : DSA/SHA1, Wed 21 Feb 2007 07:33:45 PM CET, Key ID b44269d04f2a6fd2 Packager : Red Hat, Inc. URL : http://www.openh323.org/ Summary : Open Phone Abstraction Library Description : Open Phone Abstraction Library, implementation of the ITU H.323 teleconferencing protocol, and successor of the openh323 library. > > In opal 2.2.5 all codecs are linked within libopal... ... so can I succeed with opal version 2.2.5? > > > Jure Pawel From fonz at siol.net Sat Oct 27 17:52:33 2007 From: fonz at siol.net (Jure Petrovic) Date: Sat, 27 Oct 2007 19:52:33 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <18211.28757.284045.162540@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> <18211.27313.814803.447934@localhost.localdomain> <1193503717.25606.9.camel@localhost.localdomain> <18211.28757.284045.162540@localhost.localdomain> Message-ID: <1193507553.26011.1.camel@localhost.localdomain> No, you will need opal version > 2.3.* to support dynamic plugin loading (*plugin.so files) On Sat, 2007-10-27 at 19:07 +0200, PawelCarqowski wrote: > > In opal 2.2.5 all codecs are linked within libopal... > ... so can I succeed with opal version 2.2.5? > From paulino90 at tenbit.pl Sat Oct 27 20:25:24 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sat, 27 Oct 2007 22:25:24 +0200 Subject: [Ekiga-list] G729 codec In-Reply-To: <1193507553.26011.1.camel@localhost.localdomain> References: <18211.12229.383074.45065@localhost.localdomain> <47232E08.6020003@free.fr> <18211.13222.682696.228691@localhost.localdomain> <1193489908.24740.4.camel@localhost.localdomain> <18211.23278.865329.310635@localhost.localdomain> <1193499639.25244.4.camel@localhost.localdomain> <18211.27313.814803.447934@localhost.localdomain> <1193503717.25606.9.camel@localhost.localdomain> <18211.28757.284045.162540@localhost.localdomain> <1193507553.26011.1.camel@localhost.localdomain> Message-ID: <18211.40628.862677.333594@localhost.localdomain> Jure Petrovic writes: > No, you will need opal version > 2.3.* to support dynamic plugin loading > (*plugin.so files) I just found out that ekiga page contains some up to date software, I will try with these. > > > On Sat, 2007-10-27 at 19:07 +0200, PawelCarqowski wrote: > > > In opal 2.2.5 all codecs are linked within libopal... > > ... so can I succeed with opal version 2.2.5? > > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Regards, Pawel From paulino90 at tenbit.pl Sun Oct 28 11:24:03 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sun, 28 Oct 2007 12:24:03 +0100 Subject: [Ekiga-list] fc6: ekiga compilation error Message-ID: <18212.29011.380113.412754@localhost.localdomain> hallo group members I have the following error during compiling ekiga (taken from svn). Have You got idea what might be the reason? ./autogen.sh checking for autoconf >= 2.53... testing autoconf2.50... not found. testing autoconf... found 2.59 checking for automake >= 1.8... testing automake-1.8... not found. testing automake-1.9... found 1.9.6 checking for libtool >= 1.4.3... testing libtoolize... found 1.5.22 checking for glib-gettext >= 2.2.0... testing glib-gettextize... found 2.12.9 checking for intltool >= 0.25... testing intltoolize... found 0.35.0 checking for pkg-config >= 0.14.0... testing pkg-config... found 0.21 checking for gnome-doc-utils >= 0.3.2... testing gnome-doc-prepare... found 0.8.0 Checking for required M4 macros... Checking for forbidden M4 macros... **Warning**: I am going to run `configure' with no arguments. If you wish to pass any to it, please specify them on the `./autogen.sh' command line. Processing ./configure.ac Running libtoolize... You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. Running glib-gettextize... Ignore non-fatal messages. Copying file mkinstalldirs Copying file po/Makefile.in.in Please add the files codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 progtest.m4 from the /usr/share/aclocal directory to your autoconf macro directory or directly to your aclocal.m4 file. You will also need config.guess and config.sub, which you can get from ftp://ftp.gnu.org/pub/gnu/config/. Running intltoolize... Running gnome-doc-prepare... You should add the contents of '/usr/share/aclocal/gnome-doc-utils.m4' to 'aclocal.m4'. Running aclocal-1.9... aclocal:configure.ac:199: warning: macro `AM_GCONF_SOURCE_2' not found in library Running autoconf... configure.ac:199: error: possibly undefined macro: AM_GCONF_SOURCE_2 If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. Regards, Pawel From dsandras at seconix.com Sun Oct 28 12:02:14 2007 From: dsandras at seconix.com (Damien Sandras) Date: Sun, 28 Oct 2007 13:02:14 +0100 Subject: [Ekiga-list] fc6: ekiga compilation error In-Reply-To: <18212.29011.380113.412754@localhost.localdomain> References: <18212.29011.380113.412754@localhost.localdomain> Message-ID: <1193572934.4173.2.camel@scorpion> Le dimanche 28 octobre 2007 ? 12:24 +0100, PawelCarqowski a ?crit : > hallo group members > I have the following error during compiling ekiga (taken from svn). > Have You got idea what might be the reason? > > ./autogen.sh > checking for autoconf >= 2.53... > testing autoconf2.50... not found. > testing autoconf... found 2.59 > checking for automake >= 1.8... > testing automake-1.8... not found. > testing automake-1.9... found 1.9.6 > checking for libtool >= 1.4.3... > testing libtoolize... found 1.5.22 > checking for glib-gettext >= 2.2.0... > testing glib-gettextize... found 2.12.9 > checking for intltool >= 0.25... > testing intltoolize... found 0.35.0 > checking for pkg-config >= 0.14.0... > testing pkg-config... found 0.21 > checking for gnome-doc-utils >= 0.3.2... > testing gnome-doc-prepare... found 0.8.0 > Checking for required M4 macros... > Checking for forbidden M4 macros... > **Warning**: I am going to run `configure' with no arguments. > If you wish to pass any to it, please specify them on the > `./autogen.sh' command line. > > Processing ./configure.ac > Running libtoolize... > You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. > Running glib-gettextize... Ignore non-fatal messages. > Copying file mkinstalldirs > Copying file po/Makefile.in.in > > Please add the files > codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 > progtest.m4 > from the /usr/share/aclocal directory to your autoconf macro directory > or directly to your aclocal.m4 file. > You will also need config.guess and config.sub, which you can get from > ftp://ftp.gnu.org/pub/gnu/config/. > > Running intltoolize... > Running gnome-doc-prepare... > You should add the contents of '/usr/share/aclocal/gnome-doc-utils.m4' to 'aclocal.m4'. > Running aclocal-1.9... > aclocal:configure.ac:199: warning: macro `AM_GCONF_SOURCE_2' not found in library > Running autoconf... > configure.ac:199: error: possibly undefined macro: AM_GCONF_SOURCE_2 > If this token and others are legitimate, please use m4_pattern_allow. > See the Autoconf documentation. You need to install gconf devel. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From paulino90 at tenbit.pl Sun Oct 28 14:01:17 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Sun, 28 Oct 2007 15:01:17 +0100 Subject: [Ekiga-list] fc6: ekiga compilation error In-Reply-To: <1193572934.4173.2.camel@scorpion> References: <18212.29011.380113.412754@localhost.localdomain> <1193572934.4173.2.camel@scorpion> Message-ID: <18212.38445.765697.92750@localhost.localdomain> Damien Sandras writes: > > Le dimanche 28 octobre 2007 ? 12:24 +0100, PawelCarqowski a ?crit : > > hallo group members > > I have the following error during compiling ekiga (taken from svn). > > Have You got idea what might be the reason? > > > > ./autogen.sh > > checking for autoconf >= 2.53... > > testing autoconf2.50... not found. > > testing autoconf... found 2.59 > > checking for automake >= 1.8... > > testing automake-1.8... not found. > > testing automake-1.9... found 1.9.6 > > checking for libtool >= 1.4.3... > > testing libtoolize... found 1.5.22 > > checking for glib-gettext >= 2.2.0... > > testing glib-gettextize... found 2.12.9 > > checking for intltool >= 0.25... > > testing intltoolize... found 0.35.0 > > checking for pkg-config >= 0.14.0... > > testing pkg-config... found 0.21 > > checking for gnome-doc-utils >= 0.3.2... > > testing gnome-doc-prepare... found 0.8.0 > > Checking for required M4 macros... > > Checking for forbidden M4 macros... > > **Warning**: I am going to run `configure' with no arguments. > > If you wish to pass any to it, please specify them on the > > `./autogen.sh' command line. > > > > Processing ./configure.ac > > Running libtoolize... > > You should add the contents of `/usr/share/aclocal/libtool.m4' to `aclocal.m4'. > > Running glib-gettextize... Ignore non-fatal messages. > > Copying file mkinstalldirs > > Copying file po/Makefile.in.in > > > > Please add the files > > codeset.m4 gettext.m4 glibc21.m4 iconv.m4 isc-posix.m4 lcmessage.m4 > > progtest.m4 > > from the /usr/share/aclocal directory to your autoconf macro directory > > or directly to your aclocal.m4 file. > > You will also need config.guess and config.sub, which you can get from > > ftp://ftp.gnu.org/pub/gnu/config/. > > > > Running intltoolize... > > Running gnome-doc-prepare... > > You should add the contents of '/usr/share/aclocal/gnome-doc-utils.m4' to 'aclocal.m4'. > > Running aclocal-1.9... > > aclocal:configure.ac:199: warning: macro `AM_GCONF_SOURCE_2' not found in library > > Running autoconf... > > configure.ac:199: error: possibly undefined macro: AM_GCONF_SOURCE_2 > > If this token and others are legitimate, please use m4_pattern_allow. > > See the Autoconf documentation. > > You need to install gconf devel. that's it! Thanks Pawel From jklawiter at gmail.com Mon Oct 29 14:32:18 2007 From: jklawiter at gmail.com (Jakub Klawiter) Date: Mon, 29 Oct 2007 15:32:18 +0100 Subject: [Ekiga-list] Bluez-3.20, Bluetooth Headset & ekiga - How In-Reply-To: <1193490464.4164.19.camel@scorpion> References: <123125.25631.qm@web52901.mail.re2.yahoo.com> <1193490464.4164.19.camel@scorpion> Message-ID: <5dee460a0710290732r4543202eq8d5c13f4b3b9070@mail.gmail.com> Hello! On 10/27/07, Damien Sandras wrote: > > http://bluetooth-alsa.sourceforge.net/build.html > > Interestingly enough, this link mentions patches for pwlib under the "Configure ekiga" section. > If it works, I'm ready to improve it and include it. > They always list the Bluetooth headset. I can certainly find a way to > discover if a headset is being plugged or not. I've tried to install it, but without success :D So only what can I do now is to wait and follow the bluetooth for linux changes next months ... -- Pozdrawiam, Jakub. Milion os?b dziennie pobiera Firefoksa... pobierz i Ty! www.firefox.pl From david.bercot at wanadoo.fr Mon Oct 29 14:46:58 2007 From: david.bercot at wanadoo.fr (David BERCOT) Date: Mon, 29 Oct 2007 15:46:58 +0100 Subject: [Ekiga-list] STUN - NAT : impossible to connect... Message-ID: <20071029154658.6be6084e@wanadoo.fr> Hi, At work, I've just tried to connect with Ekiga (Ekiga-snapshot on Debian/Sid). I've launched the STUN detection and the result is : "blocked" !!! (in French "R?sultat du test STUN : bloqu?"). Now, I have a tunnel between my computer and my home which I use for many things : mail, MSN, so on... Do you know how can I use this tunnel for Ekiga ? Which ports and which servers ? Thank you very much. David. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From michel.memeteau at gmail.com Mon Oct 29 14:58:00 2007 From: michel.memeteau at gmail.com (michel memeteau) Date: Mon, 29 Oct 2007 15:58:00 +0100 Subject: [Ekiga-list] STUN - NAT : impossible to connect... In-Reply-To: <20071029154658.6be6084e@wanadoo.fr> References: <20071029154658.6be6084e@wanadoo.fr> Message-ID: Hi what kind of tunnel ? Over http(s) ? How do you connect to the web ? via a http proxy ? On 10/29/07, David BERCOT wrote: > > Hi, > > At work, I've just tried to connect with Ekiga (Ekiga-snapshot on > Debian/Sid). > I've launched the STUN detection and the result is : "blocked" !!! > (in French "R?sultat du test STUN : bloqu?"). > > Now, I have a tunnel between my computer and my home which I use for > many things : mail, MSN, so on... > > Do you know how can I use this tunnel for Ekiga ? Which ports and which > servers ? > > Thank you very much. > > David. > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > > -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0874763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at gizmoproject.com jabber/GoogleTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From david.bercot at wanadoo.fr Mon Oct 29 15:10:35 2007 From: david.bercot at wanadoo.fr (David BERCOT) Date: Mon, 29 Oct 2007 16:10:35 +0100 Subject: [Ekiga-list] STUN - NAT : impossible to connect... In-Reply-To: References: <20071029154658.6be6084e@wanadoo.fr> Message-ID: <20071029161035.0fda6909@wanadoo.fr> Hi again, Le Mon, 29 Oct 2007 15:58:00 +0100, "michel memeteau" a ?crit : > Hi what kind of tunnel ? Over http(s) ? No, a direct tunnel !!! For example : ssh -N -f monserveyr -L9110:pop.wanadoo.fr:110 > How do you connect to the web ? via a http proxy ? At work, yes. But through my tunnel, I can do what I want ;-) David. > On 10/29/07, David BERCOT wrote: > > > > Hi, > > > > At work, I've just tried to connect with Ekiga (Ekiga-snapshot on > > Debian/Sid). > > I've launched the STUN detection and the result is : "blocked" !!! > > (in French "R?sultat du test STUN : bloqu?"). > > > > Now, I have a tunnel between my computer and my home which I use for > > many things : mail, MSN, so on... > > > > Do you know how can I use this tunnel for Ekiga ? Which ports and > > which servers ? > > > > Thank you very much. > > > > David. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From hazel_russman at yahoo.co.uk Mon Oct 29 16:53:06 2007 From: hazel_russman at yahoo.co.uk (Hazel Russman) Date: Mon, 29 Oct 2007 16:53:06 +0000 (GMT) Subject: [Ekiga-list] Could not connect to remote host Message-ID: <264823.97234.qm@web25012.mail.ukl.yahoo.com> I am having difficulty in getting ekiga working. I have an account at ekiga.net and it appears to be valid as I can log in there. But when I try the echo test, I get first "Registration failed - timeout" and then "Could not connect to remote host". My setup: I am using Linux pppoe behind a SMC Barricade adsl router/modem. This has a built-in firewall (configurable via the web browser) but I have not changed its default settings. As far as I can see, it is not doing any packet filtering or nat, although there are timing checks to prevent DoS attacks. The ekiga configuration druid's nat test reported "open nat". I normally have a simple iptables-based firewall on the computer itself but I flushed it away before testing ekiga. I have looked at the ekiga manual but have not found anything that looks relevant (apparently this error message is sometimes caused by a nat problem but not with open nat). I attach the transcript of a level-4 debug run (slightly edited for privacy) which I hope will be useful for pinpointing what is going wrong. Thanks in advance Hazel ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: ekiga_level4.txt URL: From sevmek at free.fr Mon Oct 29 17:31:57 2007 From: sevmek at free.fr (yannick) Date: Mon, 29 Oct 2007 18:31:57 +0100 Subject: [Ekiga-list] Could not connect to remote host In-Reply-To: <264823.97234.qm@web25012.mail.ukl.yahoo.com> References: <264823.97234.qm@web25012.mail.ukl.yahoo.com> Message-ID: <1193679117.7000.7.camel@achille> Hi, Maybe this wont solve your issue, you're using a *very* old version of ekiga (2.0.1), we now are up to 2.0.11 Consider upgrading it. Regards, Yannick Le lundi 29 octobre 2007 ? 16:53 +0000, Hazel Russman a ?crit : > I am having difficulty in getting ekiga working. I > have an account at ekiga.net and it appears to be > valid as I can log in there. But when I try the echo > test, I get first "Registration failed - timeout" and > then "Could not connect to remote host". > > My setup: I am using Linux pppoe behind a SMC > Barricade adsl router/modem. This has a built-in > firewall (configurable via the web browser) but I have > not changed its default settings. As far as I can see, > it is not doing any packet filtering or nat, although > there are timing checks to prevent DoS attacks. The > ekiga configuration druid's nat test reported "open > nat". I normally have a simple iptables-based firewall > on the computer itself but I flushed it away before > testing ekiga. > > I have looked at the ekiga manual but have not found > anything that looks relevant (apparently this error > message is sometimes caused by a nat problem but not > with open nat). > > I attach the transcript of a level-4 debug run > (slightly edited for privacy) which I hope will be > useful for pinpointing what is going wrong. > > Thanks in advance > Hazel > > > ___________________________________________________________ > Yahoo! Answers - Got a question? Someone out there knows the answer. Try it > now. > http://uk.answers.yahoo.com/ > pi?ce jointe document plein texte (ekiga_level4.txt), > "2189693495-ekiga_level4.txt" > Script started on Mon 29 Oct 2007 12:11:53 GMT hazel at scenic:~$ ekiga -d 4 2007/10/29 12:12:02.051 0:00.722 ekiga Detected audio plugins: ALSA 2007/10/29 12:12:02.055 0:00.724 ekiga Detected video plugins: Picture,V4L2,V4L 2007/10/29 12:12:02.055 0:00.724 ekiga Detected audio plugins: ALSA 2007/10/29 12:12:02.055 0:00.724 ekiga Detected video plugins: Picture,V4L2,V4L 2007/10/29 12:12:02.154 0:00.824 ekiga Detected the following audio input devices: Intel 82801AA-ICH,Default with plugin ALSA 2007/10/29 12:12:02.155 0:00.824 ekiga Detected the following audio output devices: Intel 82801AA-ICH,Default with plugin ALSA 2007/10/29 12:12:02.155 0:00.824 ekiga Detected the following video input devices: No device found with plugin V4L 2007/10/29 12:12:02.155 0:00.824 ekiga Detected the following audio input devices: Intel 82801AA-ICH,Default with plugin ALSA 2007/10/29 12:12:02.155 0:00.824 ekiga Detected the following audio output devices: Intel 82801AA-ICH,Default with plugin ALSA 2007/10/29 12:12:02.155 0:00.824 ekiga Detected the following video input devices: No device found with plugin V4L 2007/10/29 12:12:02.456 0:01.125 ekiga AVAHI Failed to create client: Daemon not running 2007/10/29 12:12:04.933 0:03.602 ekiga GnomeMeeting version 2.0.1 2007/10/29 12:12:04.936 0:03.606 ekiga OPAL version unknown 2007/10/29 12:12:04.939 0:03.608 ekiga PWLIB version 1.10.0 2007/10/29 12:12:04.941 0:03.610 ekiga GNOME support enabled 2007/10/29 12:12:04.944 0:03.614 ekiga Fullscreen support enabled 2007/10/29 12:12:04.946 0:03.616 ekiga DBUS support disabled 2007/10/29 12:12:05.097 0:03.767 ekiga Set TCP port range to 3000030010 2007/10/29 12:12:05.100 0:03.769 ekiga Set RTP port range to 50005059 2007/10/29 12:12:05.102 0:03.771 ekiga Set UDP port range to 50605100 2007/10/29 12:12:05.105 0:03.775 ekiga OpalEP Created endpoint: h323 2007/10/29 12:12:05.110 0:03.780 ekiga H323 Created endpoint. 2007/10/29 12:12:05.118 0:03.993 ekiga OpalMan Added route "pc:.*=h323:" 2007/10/29 12:12:05.327 0:03.996 ekiga OpalEP Created endpoint: sip 2007/10/29 12:12:05.330 0:03.999 ekiga SIP Created endpoint. 2007/10/29 12:12:05.335 0:04.006 ekiga OpalMan Added route "pc:.*=sip:" 2007/10/29 12:12:05.339 0:04.009 ekiga OpalEP Created endpoint: pc 2007/10/29 12:12:05.345 0:04.220 ekiga PCSS Created PC sound system endpoint. 2007/10/29 12:12:05.553 0:04.223 ekiga OpalMan Added route "h323:.*=pc:" 2007/10/29 12:12:05.556 0:04.226 ekiga OpalMan Added route "sip:.*=pc:" 2007/10/29 12:12:05.863 0:04.533 ekiga AVAHI Error initializing Avahi: %sDaemon not running 2007/10/29 12:12:05.871 0:04.540 Opal Listener:851f720 Listen Started listening thread on tcp$192.168.2.100:1720 2007/10/29 12:12:05.873 0:04.545 Opal Listener:851f720 Listen Waiting on socket accept on tcp$192.168.2.100:1720 2007/10/29 12:12:05.878 0:04.548 Opal Listener:851ff78 Listen Started listening thread on udp$192.168.2.100:5060 2007/10/29 12:12:05.880 0:04.550 Opal Listener:851ff78 Listen Waiting on UDP packet on udp$192.168.2.100:5060 2007/10/29 12:12:06.659 0:05.328 GMAccounts...t:08521978 OpalUDP Binding to interface: 192.168.2.100:1061 2007/10/29 12:12:06.659 0:05.329 GMAccounts...t:08521978 SIP Created transport udp$0.0.0.0 2007/10/29 12:12:06.686 0:05.356 GMAccounts...t:08521978 OpalUDP Started connect to 86.64.162.35:5060 2007/10/29 12:12:06.689 0:05.358 GMAccounts...t:08521978 OpalUDP Connect on pre-bound interface: 192.168.2.100 2007/10/29 12:12:06.691 0:05.361 GMAccounts...t:08521978 SIP Created Transport for Registrar udp$86.64.162.35:5060 2007/10/29 12:12:06.718 0:05.387 GMAccounts...t:08521978 SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 192.168.2.100:5061;branch=z9hG4bK1258d2d5-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: ;tag=16abd0d5-8584-dc11-98dd-003084733f80 Call-ID: 4cd6c9d5-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/29 12:12:06.921 0:05.591 SIP Transport:85c8a80 SIP Read thread started. 2007/10/29 12:12:06.926 0:05.596 SIP Transport:85c8a80 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/29 12:12:06.939 0:05.608 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 1 2007/10/29 12:12:06.940 0:05.609 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 192.168.2.100:5061;branch=z9hG4bK1258d2d5-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: ;tag=16abd0d5-8584-dc11-98dd-003084733f80 Call-ID: 4cd6c9d5-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/29 12:12:07.443 0:06.112 Housekeeper SIP Transaction 1 REGISTER timeout, making retry 2 2007/10/29 12:12:07.444 0:06.113 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 REGISTER sip:ekiga.net SIP/2.0 CSeq: 1 REGISTER Via: SIP/2.0/UDP 192.168.2.100:5061;branch=z9hG4bK1258d2d5-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: ;tag=16abd0d5-8584-dc11-98dd-003084733f80 Call-ID: 4cd6c9d5-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Expires: 3600 Content-Length: 0 Max-Forwards: 70 2007/10/29 12:12:07.961 0:06.631 Housekeeper SIP Set state Terminated_Timeout for transaction 1 REGISTER 2007/10/29 12:12:23.684 0:22.353 GMURLHandler:0862b268 OpalMan Set up call from pc:* to sip:500 at ekiga.net 2007/10/29 12:12:23.685 0:22.354 GMURLHandler:0862b268 Call Created Call[1] 2007/10/29 12:12:23.685 0:22.354 GMURLHandler:0862b268 OpalMan Set up connection to "pc:*" 2007/10/29 12:12:23.690 0:22.360 GMURLHandler:0862b268 OpalCon Created connection Call[1]-EP[Default] 2007/10/29 12:12:23.691 0:22.361 GMURLHandler:0862b268 RFC2833 Handler created 2007/10/29 12:12:23.692 0:22.361 GMURLHandler:0862b268 Silence Handler created 2007/10/29 12:12:23.693 0:22.362 GMURLHandler:0862b268 Echo Canceler Handler created 2007/10/29 12:12:23.693 0:22.362 GMURLHandler:0862b268 PCSS Created PC sound system connection. 2007/10/29 12:12:23.693 0:22.363 GMURLHandler:0862b268 OpalMan On incoming connection Call[1]-EP[Default] 2007/10/29 12:12:23.694 0:22.363 GMURLHandler:0862b268 Call GetOtherPartyConnection Call[1]-EP[Default] 2007/10/29 12:12:23.695 0:22.364 GMURLHandler:0862b268 OpalMan Set up connection to "sip:500 at ekiga.net" 2007/10/29 12:12:23.696 0:22.365 GMURLHandler:0862b268 OpalCon Created connection Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] 2007/10/29 12:12:23.696 0:22.366 GMURLHandler:0862b268 RFC2833 Handler created 2007/10/29 12:12:23.698 0:22.367 GMURLHandler:0862b268 SIP Created connection. 2007/10/29 12:12:23.698 0:22.367 GMURLHandler:0862b268 PCSS Outgoing call routed to sip:500 at ekiga.net for Call[1]-EP[Default] 2007/10/29 12:12:23.698 0:22.368 GMURLHandler:0862b268 Call OnSetUp Call[1]-EP[Default] 2007/10/29 12:12:23.699 0:22.368 GMURLHandler:0862b268 SIP SetUpConnection: 2007/10/29 12:12:23.700 0:22.369 GMURLHandler:0862b268 OpalUDP Binding to interface: 192.168.2.100:1063 2007/10/29 12:12:23.701 0:22.370 GMURLHandler:0862b268 SIP Created transport udp$0.0.0.0 2007/10/29 12:12:23.702 0:22.372 GMURLHandler:0862b268 OpalUDP Started connect to 86.64.162.35:5060 2007/10/29 12:12:23.710 0:22.380 GMURLHandler:0862b268 OpalUDP Connect on pre-bound interface: 192.168.2.100 2007/10/29 12:12:23.731 0:22.400 GMURLHandler:0862b268 SIP Transaction 1 INVITE created. 2007/10/29 12:12:23.734 0:22.403 GMURLHandler:0862b268 Call CanDoMediaBypass Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] session 1 2007/10/29 12:12:24.070 0:22.739 GMURLHandler:0862b268 OpalMan IsMediaBypassPossible: session 1 2007/10/29 12:12:24.072 0:22.741 GMURLHandler:0862b268 SIP IsMediaBypassPossible: session 1 2007/10/29 12:12:24.074 0:22.743 GMURLHandler:0862b268 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/29 12:12:24.082 0:22.754 GMURLHandler:0862b268 RTP_UDP Session 1 created: 192.168.2.100:5000-5001 ssrc=284857385 2007/10/29 12:12:24.091 0:22.761 GMURLHandler:0862b268 RTP Adding session RTP_UDP 2007/10/29 12:12:24.322 0:22.992 GMURLHandler:0862b268 SIP Using RTP payload [pt=101] for NTE 2007/10/29 12:12:24.347 0:23.136 GMURLHandler:0862b268 Call GetMediaFormats for Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] SpeexWide-20.6k iLBC-13k3 GSM-06.10 MS-GSM SpeexNarrow-8k G.711-uLaw-64k G.711-ALaw-64k H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/29 12:12:24.494 0:23.261 SIP Transport:862a8d0 SIP Read thread started. 2007/10/29 12:12:24.595 0:23.265 SIP Transport:862a8d0 SIP Waiting for PDU on udp$86.64.162.35:5060 2007/10/29 12:12:24.599 0:23.269 GMURLHandler:0862b268 Call CanDoMediaBypass Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] session 2 2007/10/29 12:12:24.605 0:23.274 GMURLHandler:0862b268 OpalMan IsMediaBypassPossible: session 2 2007/10/29 12:12:24.607 0:23.276 GMURLHandler:0862b268 SIP IsMediaBypassPossible: session 2 2007/10/29 12:12:24.609 0:23.278 GMURLHandler:0862b268 OpalCon IsMediaBypassPossible: default returns FALSE 2007/10/29 12:12:24.613 0:23.382 GMURLHandler:0862b268 RTP_UDP Session 2 created: 192.168.2.100:5002-5003 ssrc=1662607250 2007/10/29 12:12:24.716 0:23.386 GMURLHandler:0862b268 RTP Adding session RTP_UDP 2007/10/29 12:12:24.737 0:23.516 GMURLHandler:0862b268 Call GetMediaFormats for Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] SpeexWide-20.6k iLBC-13k3 GSM-06.10 MS-GSM SpeexNarrow-8k G.711-uLaw-64k G.711-ALaw-64k H.261(QCIF) H.261(CIF) YUV420P RGB32 RGB24 2007/10/29 12:12:24.857 0:23.528 GMURLHandler:0862b268 SIP No authentication information present 2007/10/29 12:12:25.016 0:23.685 GMURLHandler:0862b268 SIP Adjusting transport to address udp$ekiga.net:5060 2007/10/29 12:12:25.019 0:23.688 GMURLHandler:0862b268 SIP Sending PDU on udp$86.64.162.35:5060 INVITE sip:500 at ekiga.net SIP/2.0 Date: Mon, 29 Oct 2007 12:12:23 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.2.100:5062;branch=z9hG4bK5e1ef7df-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: "Hazel Russman" ;tag=6cf2f1df-8584-dc11-98dd-003084733f80 Call-ID: 16d5f1df-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Content-Type: application/sdp Content-Length: 419 Max-Forwards: 70 v=0 o=- 1193659944 1193659944 IN IP4 192.168.2.100 s=Opal SIP Session c=IN IP4 192.168.2.100 t=0 0 m=audio 5000 RTP/AVP 101 114 115 3 107 110 0 8 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:107 MS-GSM/8000 a=rtpmap:110 SPEEX/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/29 12:12:25.020 0:23.690 GMURLHandler:0862b268 SetUpCall succeeded 2007/10/29 12:12:25.023 0:23.692 Housekeeper SIP Transaction 1 INVITE timeout, making retry 1 2007/10/29 12:12:25.026 0:23.695 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 INVITE sip:500 at ekiga.net SIP/2.0 Date: Mon, 29 Oct 2007 12:12:23 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.2.100:5062;branch=z9hG4bK5e1ef7df-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: "Hazel Russman" ;tag=6cf2f1df-8584-dc11-98dd-003084733f80 Call-ID: 16d5f1df-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Content-Type: application/sdp Content-Length: 419 Max-Forwards: 70 v=0 o=- 1193659944 1193659944 IN IP4 192.168.2.100 s=Opal SIP Session c=IN IP4 192.168.2.100 t=0 0 m=audio 5000 RTP/AVP 101 114 115 3 107 110 0 8 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:107 MS-GSM/8000 a=rtpmap:110 SPEEX/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/29 12:12:25.527 0:24.197 Housekeeper SIP Transaction 1 INVITE timeout, making retry 2 2007/10/29 12:12:25.530 0:24.199 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 INVITE sip:500 at ekiga.net SIP/2.0 Date: Mon, 29 Oct 2007 12:12:23 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.2.100:5062;branch=z9hG4bK5e1ef7df-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: "Hazel Russman" ;tag=6cf2f1df-8584-dc11-98dd-003084733f80 Call-ID: 16d5f1df-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Content-Type: application/sdp Content-Length: 419 Max-Forwards: 70 v=0 o=- 1193659944 1193659944 IN IP4 192.168.2.100 s=Opal SIP Session c=IN IP4 192.168.2.100 t=0 0 m=audio 5000 RTP/AVP 101 114 115 3 107 110 0 8 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:107 MS-GSM/8000 a=rtpmap:110 SPEEX/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/29 12:12:26.531 0:25.201 Housekeeper SIP Transaction 1 INVITE timeout, making retry 3 2007/10/29 12:12:26.534 0:25.203 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 INVITE sip:500 at ekiga.net SIP/2.0 Date: Mon, 29 Oct 2007 12:12:23 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.2.100:5062;branch=z9hG4bK5e1ef7df-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: "Hazel Russman" ;tag=6cf2f1df-8584-dc11-98dd-003084733f80 Call-ID: 16d5f1df-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Content-Type: application/sdp Content-Length: 419 Max-Forwards: 70 v=0 o=- 1193659944 1193659944 IN IP4 192.168.2.100 s=Opal SIP Session c=IN IP4 192.168.2.100 t=0 0 m=audio 5000 RTP/AVP 101 114 115 3 107 110 0 8 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:107 MS-GSM/8000 a=rtpmap:110 SPEEX/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/29 12:12:29.404 0:28.074 Housekeeper SIP Transaction 1 INVITE timeout, making retry 4 2007/10/29 12:12:29.407 0:28.076 Housekeeper SIP Sending PDU on udp$86.64.162.35:5060 INVITE sip:500 at ekiga.net SIP/2.0 Date: Mon, 29 Oct 2007 12:12:23 GMT CSeq: 1 INVITE Via: SIP/2.0/UDP 192.168.2.100:5062;branch=z9hG4bK5e1ef7df-8584-dc11-98dd-003084733f80;rport User-Agent: Ekiga/2.0.1 From: "Hazel Russman" ;tag=6cf2f1df-8584-dc11-98dd-003084733f80 Call-ID: 16d5f1df-8584-dc11-98dd-003084733f80 at scenic To: Contact: Allow: INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, SUBSCRIBE, NOTIFY, REFER, MESSAGE Content-Type: application/sdp Content-Length: 419 Max-Forwards: 70 v=0 o=- 1193659944 1193659944 IN IP4 192.168.2.100 s=Opal SIP Session c=IN IP4 192.168.2.100 t=0 0 m=audio 5000 RTP/AVP 101 114 115 3 107 110 0 8 a=rtpmap:101 telephone-event/8000 a=fmtp:101 0-15 a=rtpmap:114 SPEEX/16000 a=rtpmap:115 iLBC/8000 a=rtpmap:3 GSM/8000 a=rtpmap:107 MS-GSM/8000 a=rtpmap:110 SPEEX/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 m=video 5002 RTP/AVP 31 a=rtpmap:31 H261/90000 2007/10/29 12:12:29.716 0:28.385 Housekeeper SIP Set state Terminated_Timeout for transaction 1 INVITE 2007/10/29 12:12:29.717 0:28.386 Housekeeper OpalCon Releasing Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] 2007/10/29 12:12:29.717 0:28.386 Housekeeper OpalCon Call end reason for 16d5f1df-8584-dc11-98dd-003084733f80 at scenic set to EndedByConnectFail 2007/10/29 12:12:29.717 0:28.387 Housekeeper OpalCon SetPhase from UninitialisedPhase to ReleasingPhase 2007/10/29 12:12:29.720 0:28.390 OnRelease:8673d80 SIP OnReleased: Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic], phase = ReleasingPhase 2007/10/29 12:12:29.724 0:28.393 OnRelease:8673d80 OpalCon SetPhase from ReleasingPhase to ReleasingPhase 2007/10/29 12:12:29.725 0:28.394 OnRelease:8673d80 OpalCon Media stream threads closed. 2007/10/29 12:12:29.725 0:28.394 OnRelease:8673d80 OpalCon SetPhase from ReleasingPhase to ReleasedPhase 2007/10/29 12:12:29.726 0:28.395 OnRelease:8673d80 Opal Transport clean up on termination 2007/10/29 12:12:29.726 0:28.395 OnRelease:8673d80 OpalUDP Close 2007/10/29 12:12:29.727 0:28.396 SIP Transport:862a8d0 OpalUDP Error on connection read select. 2007/10/29 12:12:29.729 0:28.402 SIP Transport:862a8d0 SIP Read thread finished. 2007/10/29 12:12:29.735 0:28.405 OnRelease:8673d80 OpalCon OnReleased Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] 2007/10/29 12:12:29.739 0:28.409 OnRelease:8673d80 OpalCon Media stream threads closed. 2007/10/29 12:12:29.740 0:28.409 OnRelease:8673d80 OpalEP OnReleased Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] 2007/10/29 12:12:30.073 0:28.743 OnRelease:8673d80 GMManager Will release the connection 2007/10/29 12:12:30.075 0:28.745 OnRelease:8673d80 OpalMan OnReleased Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] 2007/10/29 12:12:30.076 0:28.745 OnRelease:8673d80 Call OnReleased Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] 2007/10/29 12:12:30.077 0:28.746 OnRelease:8673d80 OpalCon Releasing Call[1]-EP[Default] 2007/10/29 12:12:30.077 0:28.746 OnRelease:8673d80 OpalCon Call end reason for Default set to EndedByConnectFail 2007/10/29 12:12:30.077 0:28.746 OnRelease:8673d80 OpalCon SetPhase from SetUpPhase to ReleasingPhase 2007/10/29 12:12:30.078 0:28.747 OnRelease:8673d80 RTP_UDP Session 1, Shutting down read. 2007/10/29 12:12:30.078 0:28.748 OnRelease:8673d80 RTP_UDP Session 1, Shutting down write. 2007/10/29 12:12:30.079 0:28.748 OnRelease:8673d80 RTP_UDP Session 2, Shutting down read. 2007/10/29 12:12:30.079 0:28.748 OnRelease:8673d80 RTP_UDP Session 2, Shutting down write. 2007/10/29 12:12:30.080 0:28.749 OnRelease:8673d80 SIP Transaction 1 INVITE destroyed. 2007/10/29 12:12:30.081 0:28.750 OnRelease:8673d80 OpalCon OnRelease thread completed for 16d5f1df-8584-dc11-98dd-003084733f80 at scenic 2007/10/29 12:12:30.236 0:28.961 OpalGarbage Opal Transport clean up on termination 2007/10/29 12:12:30.293 0:28.963 OpalGarbage OpalUDP Close 2007/10/29 12:12:30.296 0:28.965 OpalGarbage SIP Deleted connection. 2007/10/29 12:12:30.298 0:28.967 OpalGarbage OpalCon Connection Call[1]-EP[16d5f1df-8584-dc11-98dd-003084733f80 at scenic] destroyed. 2007/10/29 12:12:30.529 0:29.199 OnRelease:861ed80 OpalCon OnReleased Call[1]-EP[Default] 2007/10/29 12:12:30.533 0:29.202 OnRelease:861ed80 OpalCon Media stream threads closed. 2007/10/29 12:12:30.539 0:29.210 OnRelease:861ed80 GMPCSSEndpoint PCSS connection released 2007/10/29 12:12:30.542 0:29.212 OnRelease:861ed80 OpalEP OnReleased Call[1]-EP[Default] 2007/10/29 12:12:30.546 0:29.215 OnRelease:861ed80 GMManager Will release the connection 2007/10/29 12:12:30.548 0:29.217 OnRelease:861ed80 OpalMan OnReleased Call[1]-EP[Default] 2007/10/29 12:12:30.763 0:29.432 OnRelease:861ed80 Call OnReleased Call[1]-EP[Default] 2007/10/29 12:12:34.167 0:32.837 OnRelease:861ed80 OpalCon OnRelease thread completed for Default 2007/10/29 12:12:34.316 0:32.986 OpalGarbage PCSS Deleted PC sound system connection. 2007/10/29 12:12:34.318 0:32.988 OpalGarbage OpalCon Connection Call[1]-EP[Default] destroyed. 2007/10/29 12:12:35.324 0:33.994 OpalGarbage Call Call[1] destroyed. 2007/10/29 12:12:50.426 0:49.095 ekiga Listen Stopping listening thread on tcp$192.168.2.100:1720 2007/10/29 12:12:50.428 0:49.097 ekiga H323 Deleted endpoint. 2007/10/29 12:12:50.428 0:49.098 ekiga OpalEP h323 endpoint destroyed. 2007/10/29 12:12:50.429 0:49.099 ekiga Listen Stopping listening thread on udp$192.168.2.100:5060 2007/10/29 12:12:50.431 0:49.101 Opal Listener:851ff78 Listen UDP select error: Interrupted system call 2007/10/29 12:12:50.433 0:49.102 ekiga SIP Transaction 1 REGISTER destroyed. 2007/10/29 12:12:50.434 0:49.103 ekiga Opal Transport clean up on termination 2007/10/29 12:12:50.434 0:49.103 ekiga OpalUDP Close 2007/10/29 12:12:50.435 0:49.104 SIP Transport:85c8a80 OpalUDP Error on connection read select. 2007/10/29 12:12:50.436 0:49.105 SIP Transport:85c8a80 SIP Read thread finished. 2007/10/29 12:12:50.438 0:49.110 ekiga SIP Deleted endpoint. 2007/10/29 12:12:50.442 0:49.111 ekiga OpalEP sip endpoint destroyed. 2007/10/29 12:12:50.442 0:49.111 ekiga PCSS Deleted PC sound system endpoint. 2007/10/29 12:12:50.442 0:49.111 ekiga OpalEP pc endpoint destroyed. 2007/10/29 12:12:50.443 0:49.112 ekiga OpalMan Deleted manager. hazel at scenic:~$ exit Script done on Mon 29 Oct 2007 12:12:53 GMT > _______________________________________________ ekiga-list mailing list ekiga-list at gnome.org http://mail.gnome.org/mailman/listinfo/ekiga-list -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From DAVE.HIGTON at nice.com Mon Oct 29 17:33:25 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Mon, 29 Oct 2007 17:33:25 -0000 Subject: [Ekiga-list] RTP/RTCP port ranges In-Reply-To: <47208472.4060602@emc.ufsc.br> References: <1193235684.20167.42.camel@scorpion><1193237036.20167.48.camel@scorpion> <47208472.4060602@emc.ufsc.br> Message-ID: > Dave, can you send to me the ports windows use? Thanks in advance. This is the relevant excerpt from my ekiga.conf file: /apps/ekiga/protocols/ports/udp_port_range string 5060:5100 /apps/ekiga/protocols/ports/rtp_port_range string 5000:5059 /apps/ekiga/protocols/ports/tcp_port_range string 30000:30010 /apps/ekiga/protocols/h323/listen_port int 1720 Dave From 1.41421 at gmail.com Mon Oct 29 19:34:48 2007 From: 1.41421 at gmail.com (JCA) Date: Mon, 29 Oct 2007 12:34:48 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: > Le vendredi 12 octobre 2007 ? 20:43 +0200, yannick a ?crit : >> Le vendredi 12 octobre 2007 ? 10:25 -0700, JCA a ?crit : >> > test e.g. 1 800 4321359 (for Frontier Airlines.) >> >> It seems this number answer a SIP 407: >> "407 Proxy Authentication Required >> >> This code is similar to 401 (Unauthorized), but indicates that the >> client MUST first authenticate itself with the proxy. SIP access >> authentication is explained in Sections 26 and 22.3. >> >> This status code can be used for applications where access to the >> communication channel (for example, a telephony gateway) rather than >> the callee requires authentication." >> >> I'm not sure what this exactly means in this situation... > > That the user should directly register with the SIP registrar providing > access to that number. > > Imagine XY provides access for free to those numbers, Ekiga.net will > route the SIP requests to XY, which should relay the call. > > In some cases (I suppose it is the case here), XY will require the user > to have an XY account to relay the call. > > We are doing this for 500 at ekiga.net, it is restricted to Ekiga.net > users. However, Ekiga.net users can be called by anyone without needing > the remote peer to have an ekiga.net sip address. > > It is a question of policy. I hate to bring up the "S" word (it royally pisses me off when Skype can do something that Ekiga can't) but the fact is that I have yet to come across a single 1800 number in the US that Skype can't reach at no charge. This without registering to anything other than Skype. How come that Skype can do it whereas Ekiga can't? From lists at dcorking.com Mon Oct 29 19:41:21 2007 From: lists at dcorking.com (David Corking) Date: Mon, 29 Oct 2007 19:41:21 +0000 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: On 10/29/07, JCA wrote: > I hate to bring up the "S" word (it royally pisses me off when > Skype can do something that Ekiga can't) but the fact is that I have > yet to come across a single 1800 number in the US that Skype can't > reach at no charge. This without registering to anything other than > Skype. > > How come that Skype can do it whereas Ekiga can't? Skype has paid contracts with long-distance providers, ekiga.net relies on those available free-of-charge through the likes of freeworlddialup. I am expect Skype has leverage with one of its providers to properly terminate all 1-800 calls without charging you. If you register your copy of Ekiga with a SIP provider that has POTS relationships, then you will probably get better 1-800 service. From damailings at mcbf.net Mon Oct 29 19:44:25 2007 From: damailings at mcbf.net (David Mohr) Date: Mon, 29 Oct 2007 13:44:25 -0600 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: <472d4b250710291244r5588a2fch4231f7526536393b@mail.gmail.com> On 10/29/07, JCA <1.41421 at gmail.com> wrote: > > Le vendredi 12 octobre 2007 ? 20:43 +0200, yannick a ?crit : > >> Le vendredi 12 octobre 2007 ? 10:25 -0700, JCA a ?crit : > >> > test e.g. 1 800 4321359 (for Frontier Airlines.) > >> > >> It seems this number answer a SIP 407: > >> "407 Proxy Authentication Required > >> > >> This code is similar to 401 (Unauthorized), but indicates that the > >> client MUST first authenticate itself with the proxy. SIP access > >> authentication is explained in Sections 26 and 22.3. > >> > >> This status code can be used for applications where access to the > >> communication channel (for example, a telephony gateway) rather than > >> the callee requires authentication." > >> > >> I'm not sure what this exactly means in this situation... > > > > That the user should directly register with the SIP registrar providing > > access to that number. > > > > Imagine XY provides access for free to those numbers, Ekiga.net will > > route the SIP requests to XY, which should relay the call. > > > > In some cases (I suppose it is the case here), XY will require the user > > to have an XY account to relay the call. > > > > We are doing this for 500 at ekiga.net, it is restricted to Ekiga.net > > users. However, Ekiga.net users can be called by anyone without needing > > the remote peer to have an ekiga.net sip address. > > > > It is a question of policy. > > I hate to bring up the "S" word (it royally pisses me off when > Skype can do something that Ekiga can't) but the fact is that I have > yet to come across a single 1800 number in the US that Skype can't > reach at no charge. This without registering to anything other than > Skype. > > How come that Skype can do it whereas Ekiga can't? Because they are different products? Btw, not too long ago I consistently got so bad audio quality on 1800 numbers from skype that they were practically unusable.... ~David From paulino90 at tenbit.pl Mon Oct 29 21:18:15 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Mon, 29 Oct 2007 22:18:15 +0100 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. Message-ID: <18214.19991.980028.366199@localhost.localdomain> Hallo group members I'm trying to install (with make install) ekiga as non-root user to some directory my user has access to. I configured ekiga with following parameters: $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr config and make went smoothly. "make install" went quite far. It failed on: /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied make[2]: *** [install-doc-omf] Error 1 make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' make: *** [install-recursive] Error 1 I do not see eny more prefix'es to use below. ONLY PREFIX and EPREFIX are used. $ ./configure --help: Fine tuning of the installation directories: --bindir=DIR user executables [EPREFIX/bin] --sbindir=DIR system admin executables [EPREFIX/sbin] --libexecdir=DIR program executables [EPREFIX/libexec] --datadir=DIR read-only architecture-independent data [PREFIX/share] --sysconfdir=DIR read-only single-machine data [PREFIX/etc] --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] --localstatedir=DIR modifiable single-machine data [PREFIX/var] --libdir=DIR object code libraries [EPREFIX/lib] --includedir=DIR C header files [PREFIX/include] --oldincludedir=DIR C header files for non-gcc [/usr/include] --infodir=DIR info documentation [PREFIX/info] --mandir=DIR man documentation [PREFIX/man] have You got any ideas on how to fix this? Regards, Pawel From alanslists at gmail.com Mon Oct 29 21:29:59 2007 From: alanslists at gmail.com (Alan Lord) Date: Mon, 29 Oct 2007 21:29:59 +0000 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. In-Reply-To: <18214.19991.980028.366199@localhost.localdomain> References: <18214.19991.980028.366199@localhost.localdomain> Message-ID: <472650D7.7090005@gmail.com> PawelCarqowski wrote: > Hallo group members > > I'm trying to install (with make install) ekiga as non-root user to some directory my user has access to. > > I configured ekiga with following parameters: > > $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr > > config and make went smoothly. "make install" went quite far. It failed on: > > /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf > /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf > /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf > scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga > /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied > make[2]: *** [install-doc-omf] Error 1 > make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > make: *** [install-recursive] Error 1 > > I do not see eny more prefix'es to use below. ONLY PREFIX and EPREFIX are used. > > $ ./configure --help: > > Fine tuning of the installation directories: > --bindir=DIR user executables [EPREFIX/bin] > --sbindir=DIR system admin executables [EPREFIX/sbin] > --libexecdir=DIR program executables [EPREFIX/libexec] > --datadir=DIR read-only architecture-independent data [PREFIX/share] > --sysconfdir=DIR read-only single-machine data [PREFIX/etc] > --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] > --localstatedir=DIR modifiable single-machine data [PREFIX/var] > --libdir=DIR object code libraries [EPREFIX/lib] > --includedir=DIR C header files [PREFIX/include] > --oldincludedir=DIR C header files for non-gcc [/usr/include] > --infodir=DIR info documentation [PREFIX/info] > --mandir=DIR man documentation [PREFIX/man] > > > have You got any ideas on how to fix this? > > Regards, > Pawel I haven't tried this but why not just configure it with a normal prefix like /usr and then make it, then do a make DESTDIR=/home/misc/ekiga/site-usr install That should install a whole new tree under your site-usr directory. On another note, --locatstatedir normally points to var so you might need to add that switch if you want to do it the "long way" HTH Alan From damailings at mcbf.net Mon Oct 29 21:37:27 2007 From: damailings at mcbf.net (David Mohr) Date: Mon, 29 Oct 2007 15:37:27 -0600 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. In-Reply-To: <18214.19991.980028.366199@localhost.localdomain> References: <18214.19991.980028.366199@localhost.localdomain> Message-ID: <472d4b250710291437h5716eabfl1c3b68ffef09d03d@mail.gmail.com> On 10/29/07, PawelCarqowski wrote: > Hallo group members > > I'm trying to install (with make install) ekiga as non-root user to some directory my user has access to. > > I configured ekiga with following parameters: > > $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr > > config and make went smoothly. "make install" went quite far. It failed on: > > /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf > /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf > /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf > scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga > /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied It looks to me like a bug in the Makefile because `scrollkeeper-update' is still referring to /var when it probably should be using $PREFIX/var or maybe the localstatedir. This might be an easy fix to do yourself, just look where scrollkeeper-update is called. ~David > make[2]: *** [install-doc-omf] Error 1 > make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > make[1]: *** [install-am] Error 2 > make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > make: *** [install-recursive] Error 1 > > I do not see eny more prefix'es to use below. ONLY PREFIX and EPREFIX are used. > > $ ./configure --help: > > Fine tuning of the installation directories: > --bindir=DIR user executables [EPREFIX/bin] > --sbindir=DIR system admin executables [EPREFIX/sbin] > --libexecdir=DIR program executables [EPREFIX/libexec] > --datadir=DIR read-only architecture-independent data [PREFIX/share] > --sysconfdir=DIR read-only single-machine data [PREFIX/etc] > --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] > --localstatedir=DIR modifiable single-machine data [PREFIX/var] > --libdir=DIR object code libraries [EPREFIX/lib] > --includedir=DIR C header files [PREFIX/include] > --oldincludedir=DIR C header files for non-gcc [/usr/include] > --infodir=DIR info documentation [PREFIX/info] > --mandir=DIR man documentation [PREFIX/man] > > > have You got any ideas on how to fix this? > > Regards, > Pawel > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > From jpuydt at free.fr Mon Oct 29 21:48:40 2007 From: jpuydt at free.fr (Julien Puydt) Date: Mon, 29 Oct 2007 22:48:40 +0100 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. In-Reply-To: <472d4b250710291437h5716eabfl1c3b68ffef09d03d@mail.gmail.com> References: <18214.19991.980028.366199@localhost.localdomain> <472d4b250710291437h5716eabfl1c3b68ffef09d03d@mail.gmail.com> Message-ID: <47265538.3030208@free.fr> David Mohr a ?crit : > On 10/29/07, PawelCarqowski wrote: >> Hallo group members >> >> I'm trying to install (with make install) ekiga as non-root user to some directory my user has access to. >> >> I configured ekiga with following parameters: >> >> $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr >> >> config and make went smoothly. "make install" went quite far. It failed on: >> >> /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf >> /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf >> /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf >> scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga >> /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied > > It looks to me like a bug in the Makefile because > `scrollkeeper-update' is still referring to /var when it probably > should be using $PREFIX/var or maybe the localstatedir. This might be > an easy fix to do yourself, just look where scrollkeeper-update is > called. If that's something that simple, we'll gladly have feedback about it to apply the fix to svn trunk. Thanks, Snark on #ekiga From 1.41421 at gmail.com Tue Oct 30 00:01:10 2007 From: 1.41421 at gmail.com (JCA) Date: Mon, 29 Oct 2007 17:01:10 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: > Skype has paid contracts with long-distance providers, ekiga.net > relies on those available free-of-charge through the likes of > freeworlddialup. I am expect Skype has leverage with one of its > providers to properly terminate all 1-800 calls without charging you. > > If you register your copy of Ekiga with a SIP provider that has POTS > relationships, then you will probably get better 1-800 service. Thanks for the explanation. This does sound plausible - for better or worse, Skype seems to have more financial muscle than Ekiga at this point in time. From 1.41421 at gmail.com Tue Oct 30 00:08:20 2007 From: 1.41421 at gmail.com (JCA) Date: Mon, 29 Oct 2007 17:08:20 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: >> I hate to bring up the "S" word (it royally pisses me off when >> Skype can do something that Ekiga can't) but the fact is that I have >> yet to come across a single 1800 number in the US that Skype can't >> reach at no charge. This without registering to anything other than >> Skype. >> >> How come that Skype can do it whereas Ekiga can't? > > Because they are different products? I like Ekiga as much as the next guy, but I prefer to describe things accurately: In this particular respect, Skype beats Ekiga. > Btw, not too long ago I consistently got so bad audio quality on 1800 > numbers from skype that they were practically unusable.... Fair enough. That's not my experience: They both give me comparable sound quality when calling 1800 numbers. But, it will still be the case for you and for me that there are some 1800 numbers that we can dial with Skype for free, but not with Ekiga. From lists at dcorking.com Tue Oct 30 07:22:21 2007 From: lists at dcorking.com (David Corking) Date: Tue, 30 Oct 2007 07:22:21 +0000 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: On 10/30/07, JCA wrote: > This does sound plausible - for better > or worse, Skype seems to have more financial muscle than Ekiga at this > point in time. I would hazard a guess that it is a loss leader for Skype or their partner. By Ekiga you actually mean ekiga.net - which is a spare time project of a couple of people here. ekiga.net gets no financial support from the community that I am aware of (except maybe a small commission from diamondcard - I don't know.) I don't think they asked for any support. ekiga.net is optimised for voip-to-voip calls to build a community around the Ekiga software. voip-to-voip needs much less resources. I have not tried to use the 1800 service through freeworlddialup for a year or two. I do recall difficulties with it. I don't understand why freeworlddialup doesn't have the muscle to keep the 1800 service going consistently. Unlike ekiga.net, it is based in the US. Perhaps they just have other fish to fry, or insufficient phone lines. Therefore my advice would be - if you are in the US, get Asterisk or similar and a line card - and hook it up to your landline. If you are outside the US, 1. try ekiga.net first - if the 1800 number is not reachable by ekiga.net then 2. register with a kind friend in the US with Asterisk, or 3. register with a paid SIP or H323 provider - you can probably get calls to the US, including 1800, for around one cent per minute, but maybe you will find someone willing to throw in 1800 free-of-charge (if you do please let us know.) From paulino90 at tenbit.pl Tue Oct 30 07:46:14 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Tue, 30 Oct 2007 08:46:14 +0100 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. In-Reply-To: <472650D7.7090005@gmail.com> References: <18214.19991.980028.366199@localhost.localdomain> <472650D7.7090005@gmail.com> Message-ID: <18214.57670.187398.186411@localhost.localdomain> Alan Lord writes: > PawelCarqowski wrote: > > Hallo group members > > > > I'm trying to install (with make install) ekiga as non-root user to some directory my user has access to. > > > > I configured ekiga with following parameters: > > > > $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr > > > > config and make went smoothly. "make install" went quite far. It failed on: > > > > /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf > > /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf > > /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf > > scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga > > /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied > > make[2]: *** [install-doc-omf] Error 1 > > make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > > make[1]: *** [install-am] Error 2 > > make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > > make: *** [install-recursive] Error 1 > > > > I do not see eny more prefix'es to use below. ONLY PREFIX and EPREFIX are used. > > > > $ ./configure --help: > > > > Fine tuning of the installation directories: > > --bindir=DIR user executables [EPREFIX/bin] > > --sbindir=DIR system admin executables [EPREFIX/sbin] > > --libexecdir=DIR program executables [EPREFIX/libexec] > > --datadir=DIR read-only architecture-independent data [PREFIX/share] > > --sysconfdir=DIR read-only single-machine data [PREFIX/etc] > > --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] > > --localstatedir=DIR modifiable single-machine data [PREFIX/var] > > --libdir=DIR object code libraries [EPREFIX/lib] > > --includedir=DIR C header files [PREFIX/include] > > --oldincludedir=DIR C header files for non-gcc [/usr/include] > > --infodir=DIR info documentation [PREFIX/info] > > --mandir=DIR man documentation [PREFIX/man] > > > > > > have You got any ideas on how to fix this? > > > > Regards, > > Pawel > > I haven't tried this but why not just configure it with a normal prefix > like /usr and then make it, then do a > > make DESTDIR=/home/misc/ekiga/site-usr install > > That should install a whole new tree under your site-usr directory. > > On another note, --locatstatedir normally points to var so you might > need to add that switch if you want to do it the "long way" > > HTH > > Alan > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list I'll try to use "make DESTDIR=/home/misc/ekiga/ekiga-site install" way. Regards, Pawel From paulino90 at tenbit.pl Tue Oct 30 08:48:27 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Tue, 30 Oct 2007 09:48:27 +0100 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. In-Reply-To: <472650D7.7090005@gmail.com> References: <18214.19991.980028.366199@localhost.localdomain> <472650D7.7090005@gmail.com> Message-ID: <18214.61403.445076.220556@localhost.localdomain> Alan Lord writes: > PawelCarqowski wrote: > > Hallo group members > > > > I'm trying to install (with make install) ekiga as non-root user to some directory my user has access to. > > > > I configured ekiga with following parameters: > > > > $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr > > > > config and make went smoothly. "make install" went quite far. It failed on: > > > > /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf > > /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf > > /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf > > scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga > > /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied > > make[2]: *** [install-doc-omf] Error 1 > > make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > > make[1]: *** [install-am] Error 2 > > make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' > > make: *** [install-recursive] Error 1 > > > > I do not see eny more prefix'es to use below. ONLY PREFIX and EPREFIX are used. > > > > $ ./configure --help: > > > > Fine tuning of the installation directories: > > --bindir=DIR user executables [EPREFIX/bin] > > --sbindir=DIR system admin executables [EPREFIX/sbin] > > --libexecdir=DIR program executables [EPREFIX/libexec] > > --datadir=DIR read-only architecture-independent data [PREFIX/share] > > --sysconfdir=DIR read-only single-machine data [PREFIX/etc] > > --sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com] > > --localstatedir=DIR modifiable single-machine data [PREFIX/var] > > --libdir=DIR object code libraries [EPREFIX/lib] > > --includedir=DIR C header files [PREFIX/include] > > --oldincludedir=DIR C header files for non-gcc [/usr/include] > > --infodir=DIR info documentation [PREFIX/info] > > --mandir=DIR man documentation [PREFIX/man] > > > > > > have You got any ideas on how to fix this? > > > > Regards, > > Pawel > > I haven't tried this but why not just configure it with a normal prefix > like /usr and then make it, then do a > > make DESTDIR=/home/misc/ekiga/site-usr install > > That should install a whole new tree under your site-usr directory. > > On another note, --locatstatedir normally points to var so you might > need to add that switch if you want to do it the "long way" > > HTH > > Alan I finally tried 3 cases: 1) $ make DESTDIR=/home/misc/ekiga/ekiga-site install - installed ekiga at /home/misc/ekiga/ekiga-site - but it produced huge amount of lines, like: /usr/bin/install -c -m 644 ekiga-es.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-es.omf /usr/bin/install -c -m 644 ekiga-fr.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-fr.omf /usr/bin/install -c -m 644 ekiga-oc.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-oc.omf /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf scrollkeeper-update -p /home/misc/ekiga/site-var -o /home/misc/ekiga/site-usr/share/omf/ekiga Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied Cannot write to log file: /var/log/scrollkeeper.log : Permission denied make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' make[1]: Entering directory `/home/misc/ekiga/ekiga-svn/ekiga' make[2]: Entering directory `/home/misc/ekiga/ekiga-svn/ekiga' make[2]: Nothing to be done for `install-exec-am'. test -z "/home/misc/ekiga/site-usr/share/applications" || mkdir -p -- "/home/misc/ekiga/site-usr/share/applications" /usr/bin/install -c -m 644 'ekiga.desktop' '/home/misc/ekiga/site-usr/share/applications/ekiga.desktop' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults gconftool-2 --makefile-install-rule ekiga.schemas 2>&1 > /dev/null None of the resolved addresses are writable; saving configuration settings will not be possible WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `th': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `cs': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `dz': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `fa': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `bn': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `nl': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path ..... 2) $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr --localstatedir=/home/misc/ekiga/site-var $ make install - again failed on: /usr/bin/install -c -m 644 ekiga-pt_BR.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-pt_BR.omf /usr/bin/install -c -m 644 ekiga-uk.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-uk.omf /usr/bin/install -c -m 644 ekiga-sv.omf /home/misc/ekiga/site-usr/share/omf/ekiga/ekiga-sv.omf scrollkeeper-update -p /var/lib/scrollkeeper -o /home/misc/ekiga/site-usr/share/omf/ekiga /var/lib/scrollkeeper/scrollkeeper_docs: Permission denied make[2]: *** [install-doc-omf] Error 1 make[2]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' make[1]: *** [install-am] Error 2 make[1]: Leaving directory `/home/misc/ekiga/ekiga-svn/ekiga/help' make: *** [install-recursive] Error 1 because, _localstatedir is used by ekiga, so.... 3) $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr $ make _sklocalstatedir=/home/misc/ekiga/site-var install - installed ekiga, but again, produced many lines as in case 1. Regards, Pawel From alanslists at gmail.com Tue Oct 30 09:12:22 2007 From: alanslists at gmail.com (Alan Lord) Date: Tue, 30 Oct 2007 09:12:22 +0000 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails. In-Reply-To: <18214.61403.445076.220556@localhost.localdomain> References: <18214.19991.980028.366199@localhost.localdomain> <472650D7.7090005@gmail.com> <18214.61403.445076.220556@localhost.localdomain> Message-ID: <4726F576.4000803@gmail.com> PawelCarqowski wrote: ... > because, _localstatedir is used by ekiga, so.... > > 3) > $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr > $ make _sklocalstatedir=/home/misc/ekiga/site-var install > > - installed ekiga, but again, produced many lines as in case 1. > > Regards, > Pawel After autogen (which you should only need to do once, after pulling down the svn source), try and run ./configure --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr *--localstatedir=/home/misc/ekiga/site-var* (Omit the asterisks, they are just to highlight the switch!) make make install Looking at your switches, do you actually have ptlib and opal installed where you say? These sort of switches are normally used to point to unusual locations of *already installed* system libraries. On a "normal" system, they would probably be installed in /usr/lib or /usr/local/lib and the corresponding include directories. 'ldconfig -p | less' is your friend here. Secondly, I don't really know what scrollkeeper-update is but my guess is it has a hard-coded reference somewhere to /var/log/scrollkeeper.log If you grep the clean source directory for '/var/log' what files does it bring up? Take a look in those files for hardcoded paths and try changing them... Also, if you use the DESTDIR solution, it looks like you can run make install as root and it will be able to write to the scrollkeeper.log file, and everything else will be written to DESTDIR. Just tee the output of make install into a log file then you can see where everything has been installed to. Something like: make install 2>&1 | tee -a ../ekiga-make-install.log should do it. HTH ideas help. Alan -- The way out is open! http://www.theopensourcerer.com From 1.41421 at gmail.com Tue Oct 30 16:25:44 2007 From: 1.41421 at gmail.com (JCA) Date: Tue, 30 Oct 2007 09:25:44 -0700 Subject: [Ekiga-list] Dialing 1-800 numbers in the US Message-ID: > I don't understand why freeworlddialup doesn't have the muscle to keep > the 1800 service going consistently. Unlike ekiga.net, it is based in > the US. Perhaps they just have other fish to fry, or insufficient > phone lines. > > Therefore my advice would be - if you are in the US, get Asterisk or > similar and a line card - and hook it up to your landline. If you are > outside the US, > > 1. try ekiga.net first - if the 1800 number is not reachable by ekiga.net then > 2. register with a kind friend in the US with Asterisk, or > 3. register with a paid SIP or H323 provider - you can probably get > calls to the US, including 1800, for around one cent per minute, but > maybe you will find someone willing to throw in 1800 free-of-charge > (if you do please let us know.) That's good advice, and I'll follow it - when I get the chance. At this point I just want to be able to call certain 1800 numbers toll free from my computer, hassle free. Sadly, that currently means using Skype, not Ekiga. From dsandras at seconix.com Tue Oct 30 16:30:58 2007 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Oct 2007 17:30:58 +0100 Subject: [Ekiga-list] Dialing 1-800 numbers in the US In-Reply-To: References: Message-ID: <1193761858.6433.8.camel@scorpion> Le mardi 30 octobre 2007 ? 09:25 -0700, JCA a ?crit : > > I don't understand why freeworlddialup doesn't have the muscle to keep > > the 1800 service going consistently. Unlike ekiga.net, it is based in > > the US. Perhaps they just have other fish to fry, or insufficient > > phone lines. > > > > Therefore my advice would be - if you are in the US, get Asterisk or > > similar and a line card - and hook it up to your landline. If you are > > outside the US, > > > > 1. try ekiga.net first - if the 1800 number is not reachable by ekiga.net then > > 2. register with a kind friend in the US with Asterisk, or > > 3. register with a paid SIP or H323 provider - you can probably get > > calls to the US, including 1800, for around one cent per minute, but > > maybe you will find someone willing to throw in 1800 free-of-charge > > (if you do please let us know.) > > That's good advice, and I'll follow it - when I get the chance. At > this point I just want to be able to call certain 1800 numbers toll > free from my computer, hassle free. Sadly, that currently means using > Skype, not Ekiga. There is nothing we can do about it... -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From hunteke at earlham.edu Tue Oct 30 18:00:10 2007 From: hunteke at earlham.edu (Kevin Hunter) Date: Tue, 30 Oct 2007 14:00:10 -0400 Subject: [Ekiga-list] download page icon question Message-ID: <4727712A.6000902@earlham.edu> Hi List, I was idly perusing the Ekiga download page (http://www.ekiga.org/index.php?rub=5) and noted that both the Windows and Skype icons are sort of a blue-white-grey don't-look-as-good-as-usual icons. Is that an issue of copyright or something? Thanks, Kevin From michel.memeteau at gmail.com Tue Oct 30 18:09:59 2007 From: michel.memeteau at gmail.com (michel memeteau) Date: Tue, 30 Oct 2007 19:09:59 +0100 Subject: [Ekiga-list] download page icon question In-Reply-To: <4727712A.6000902@earlham.edu> References: <4727712A.6000902@earlham.edu> Message-ID: On 10/30/07, Kevin Hunter wrote: > > and Skype icons are sort of a blue-white-grey I Guess he meant Slackware :-) -- %<------------------------------------------------------->% Michel memeteau Blog 0.2 : http://memeteau.free.fr Fixe : 0874763294 Mobile : 0624808051 VOIP | Visio: sip:freechelmi at gizmoproject.com jabber/GoogleTalk : xmpp:freechelmi at jabber.fr -------------- next part -------------- An HTML attachment was scrubbed... URL: From hunteke at earlham.edu Tue Oct 30 18:12:07 2007 From: hunteke at earlham.edu (Kevin Hunter) Date: Tue, 30 Oct 2007 14:12:07 -0400 Subject: [Ekiga-list] USB headset and use/detection Message-ID: <472773F7.6040100@earlham.edu> Hi List, Ubuntu Feisty, Ekiga 2.0.11. I note that Ekiga seems to only scan the available sound devices on startup. So, if I start up with the headset on, make a call, hangup, and then make another call but unplug the headset, Ekiga gives me a couple of errors, rather than defaulting to another sound system. The same is true if I start up with no headset plugged in, and then plug them in before a call. I know about selecting the sound I/O devices with Edit->Preferences->Devices->Audio Devices, so it's not a big deal, but what would be the obstacles in implementing automatic detection/use with D-Bus? Thus, Ekiga could have a "Default device if available" plan, and do a quick devices check just before initiating every call. Thanks, Kevin From hunteke at earlham.edu Tue Oct 30 18:23:08 2007 From: hunteke at earlham.edu (Kevin Hunter) Date: Tue, 30 Oct 2007 14:23:08 -0400 Subject: [Ekiga-list] download page icon question In-Reply-To: References: <4727712A.6000902@earlham.edu> Message-ID: <4727768C.7050307@earlham.edu> At 2:09p -0400 on 30 Oct 2007, Michel Memeteau wrote: >> and Skype icons are sort of a blue-white-grey > > I Guess he meant Slackware :-) Yes, yes I did. Gee, that's embarrassing. Kevin From dsandras at seconix.com Tue Oct 30 20:48:43 2007 From: dsandras at seconix.com (Damien Sandras) Date: Tue, 30 Oct 2007 21:48:43 +0100 Subject: [Ekiga-list] USB headset and use/detection In-Reply-To: <472773F7.6040100@earlham.edu> References: <472773F7.6040100@earlham.edu> Message-ID: <1193777323.4333.2.camel@scorpion> Le mardi 30 octobre 2007 ? 14:12 -0400, Kevin Hunter a ?crit : > Hi List, > > Ubuntu Feisty, Ekiga 2.0.11. > > I note that Ekiga seems to only scan the available sound devices on > startup. So, if I start up with the headset on, make a call, hangup, > and then make another call but unplug the headset, Ekiga gives me a > couple of errors, rather than defaulting to another sound system. The > same is true if I start up with no headset plugged in, and then plug > them in before a call. > > I know about selecting the sound I/O devices with > Edit->Preferences->Devices->Audio Devices, so it's not a big deal, but > what would be the obstacles in implementing automatic detection/use with > D-Bus? Thus, Ekiga could have a "Default device if available" plan, and > do a quick devices check just before initiating every call. It is on the TODO list :) But if you feel like implementing it, feel free to step in. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From paulino90 at tenbit.pl Tue Oct 30 22:08:05 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Tue, 30 Oct 2007 23:08:05 +0100 Subject: [Ekiga-list] ekiga - svn. installing as non-root user fails - continue Message-ID: <18215.43845.872899.315596@localhost.localdomain> Hallo Alan & group members I missed thread (that's why "- continue"), but not the last email, which is below. Sorry for inconvinience. See comments in a message Alan Lord writes: > PawelCarqowski wrote: > > ... > > because, _localstatedir is used by ekiga, so.... > > > > 3) > > $ ./autogen.sh --prefix=/home/misc/ekiga/site-usr --exec-prefix=/home/misc/ekiga/site-usr --sysconfdir=/home/misc/ekiga/site-etc --with-ptlib-dir=/home/misc/ekiga/site-usr --with-opal-dir=/home/misc/ekiga/site-usr > > $ make _sklocalstatedir=/home/misc/ekiga/site-var install > > > > - installed ekiga, but again, produced many lines as in case 1. > > > > Regards, > > Pawel > > After autogen (which you should only need to do once, after pulling down > the svn source), try and run > > ./configure --prefix=/home/misc/ekiga/site-usr > --exec-prefix=/home/misc/ekiga/site-usr > --sysconfdir=/home/misc/ekiga/site-etc > --with-ptlib-dir=/home/misc/ekiga/site-usr > --with-opal-dir=/home/misc/ekiga/site-usr > *--localstatedir=/home/misc/ekiga/site-var* (Omit the asterisks, they > are just to highlight the switch!) > > make > > make install > > Looking at your switches, do you actually have ptlib and opal installed > where you say? These sort of switches are normally used to point to > unusual locations of *already installed* system libraries. On a "normal" > system, they would probably be installed in /usr/lib or /usr/local/lib > and the corresponding include directories. 'ldconfig -p | less' is your > friend here. Yes, they are installed there. Both pltlib and opal (and ekiga as well) are taken from svn and my goal is not to install them in any place in the system, and I think it's fine for unstable sources. During running ekiga I will just do: env PATH=$PATH:_path_to_ekiga_site_bin_dir_ LD_LIBRARY_PATH=_path_to_ekiga_site_lib_dir_ ekiga > > Secondly, I don't really know what scrollkeeper-update is but my guess > is it has a hard-coded reference somewhere to /var/log/scrollkeeper.log > > If you grep the clean source directory for '/var/log' what files does it > bring up? Take a look in those files for hardcoded paths and try > changing them... > > Also, if you use the DESTDIR solution, it looks like you can run make > install as root and it will be able to write to the scrollkeeper.log > file, and everything else will be written to DESTDIR. Just tee the > output of make install into a log file then you can see where everything > has been installed to. Something like: > > make install 2>&1 | tee -a ../ekiga-make-install.log > > should do it. > > HTH ideas help. > > Alan > > -- > The way out is open! > http://www.theopensourcerer.com > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list Finally I cleaned up everything (ptlib, opal and ekiga) and used the idea with DESTDIR set to /home/misc/ekiga/site-dir for each componen: ptlib, opal and ekiga, while putting the following params to ./configure and autogen. Literally: DESTDIR=/home/misc/ekiga/site-dir pltib: ./configure --prefix=/usr --enable-plugins --disable-oss --enable-v4l2 opal: ./configure --prefix=/usr ekiga: ./autogen.sh --prefix=/usr --exec-prefix=/usr --sysconfdir=/etc --with-ptlib-dir=${DESTDIR}/usr --with-opal-dir=${DESTDIR}/usr ptlib and opal compile and install without any problem to my DESTDIR ekiga also compiles without any problem, but installation produces the following warnings: test -z "/usr/share/applications" || mkdir -p -- "/home/misc/ekiga/site-dir/usr/share/applications" /usr/bin/install -c -m 644 'ekiga.desktop' '/home/misc/ekiga/site-dir/usr/share/applications/ekiga.desktop' GCONF_CONFIG_SOURCE=xml:merged:/etc/gconf/gconf.xml.defaults gconftool-2 --makefile-install-rule ekiga.schemas 2>&1 > /dev/null None of the resolved addresses are writable; saving configuration settings will not be possible WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `th': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path WARNING: failed to install schema `/schemas/apps/ekiga/devices/audio/plugin' locale `cs': Can't overwrite existing read-only value: Value for `/schemas/apps/ekiga/devices/audio/plugin' set in a read-only source at the front of your configuration path ..... mamny, many lines like these above.... I finally decided to do: make DESTDIR=/home/misc/ekiga/site-dir install as root user to solve the warnings above. It helped. Installation finished. best regards, Pawel From paulino90 at tenbit.pl Tue Oct 30 22:34:06 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Tue, 30 Oct 2007 23:34:06 +0100 Subject: [Ekiga-list] ekiga 2.1.0 (svn) segmentation fault. compilation: fc6. Message-ID: <18215.45406.487224.155040@localhost.localdomain> Hallo group members. Segmentation fault is at the very beginning. Ekiga does not start at all. $ env PATH=/home/misc/ekiga/site-dir/usr/bin:${PATH} LD_LIBRARY_PATH=/home/misc/ekiga/site-dir/usr/lib ekiga (process:21709): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function (process:21709): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (process:21709): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Segmentation fault config options of ekiga are: ================ Final configuration =================== Installing into prefix : /usr OPAL Version is : 3.1.0 OPAL Directory is : /home/misc/ekiga/site-dir/usr PTLIB Version is : 2.1.0 PTLIB Directory is : /home/misc/ekiga/site-dir/usr ptlib-config is : /home/misc/ekiga/site-dir/usr/bin/ptlib-config GNOME support : enabled GConf support : enabled Evolution-Data-Server support : enabled Esound support : enabled LDAP support : enabled XVideo support : enabled DBUS support : enabled mDNS/DNS-SD support : enabled OS Type : linux-gnu Machine Type : i686 ================================= when running not stripped version in GDB I have the following: (gdb) set environment LD_LIBRARY_PATH=/home/misc/ekiga/site-dir/usr/lib (gdb) run Starting program: /home/misc/ekiga/ekiga-svn/ekiga/src/ekiga [Thread debugging using libthread_db enabled] [New Thread -1219008800 (LWP 8432)] (process:8432): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function (process:8432): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed (process:8432): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1219008800 (LWP 8432)] 0x006c9bde in gconf_client_reverse_change_set () at /home/misc/ekiga/site-dir/usr/include/ptclib/http.h:498 (gdb) bt #0 0x006c9bde in gconf_client_reverse_change_set () at /home/misc/ekiga/site-dir/usr/include/ptclib/http.h:498 #1 0x006cd1e9 in gconf_client_get_default () at /home/misc/ekiga/site-dir/usr/include/ptclib/http.h:498 #2 0x080f90d7 in gm_conf_init () at gmconf-gconf.c:277 #3 0x080c7da4 in main (argc=1, argv=0xbfb6ab24, envp=0xbfb6ab2c) at gui/main.cpp:4039 Have You got idea what might be the reason? Should I do anything else before initial running of ekiga. Ekiga is installed in the running system (/usr, /etc). ptlib and opal are installed in /home/misc/ekiga/site-dir. ptlib, opal and ekiga sources were taken from svn 2 hours ago (Tuesday, October 30 2007, Time: 11 33 PM, Eastern europe time). regards, Pawel From paulino90 at tenbit.pl Wed Oct 31 08:33:33 2007 From: paulino90 at tenbit.pl (PawelCarqowski) Date: Wed, 31 Oct 2007 09:33:33 +0100 Subject: [Ekiga-list] ekiga 2.1.0 (svn) segmentation fault. compilation: fc6. In-Reply-To: <18215.45406.487224.155040@localhost.localdomain> References: <18215.45406.487224.155040@localhost.localdomain> Message-ID: <18216.15837.486699.979123@localhost.localdomain> PawelCarqowski writes: > Hallo group members. > > Segmentation fault is at the very beginning. Ekiga does not start at all. > > $ env PATH=/home/misc/ekiga/site-dir/usr/bin:${PATH} LD_LIBRARY_PATH=/home/misc/ekiga/site-dir/usr/lib ekiga > > (process:21709): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function > > (process:21709): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed > > (process:21709): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed > Segmentation fault > > > config options of ekiga are: > ================ Final configuration =================== > Installing into prefix : /usr > > OPAL Version is : 3.1.0 > OPAL Directory is : /home/misc/ekiga/site-dir/usr > PTLIB Version is : 2.1.0 > PTLIB Directory is : /home/misc/ekiga/site-dir/usr > ptlib-config is : /home/misc/ekiga/site-dir/usr/bin/ptlib-config > > > GNOME support : enabled > GConf support : enabled > Evolution-Data-Server support : enabled > Esound support : enabled > LDAP support : enabled > > XVideo support : enabled > > DBUS support : enabled > mDNS/DNS-SD support : enabled > > OS Type : linux-gnu > Machine Type : i686 > ================================= > > when running not stripped version in GDB I have the following: > > (gdb) set environment LD_LIBRARY_PATH=/home/misc/ekiga/site-dir/usr/lib > (gdb) run > Starting program: /home/misc/ekiga/ekiga-svn/ekiga/src/ekiga > [Thread debugging using libthread_db enabled] > [New Thread -1219008800 (LWP 8432)] > > (process:8432): GLib-GObject-CRITICAL **: gtype.c:2242: initialization assertion failed, use IA__g_type_init() prior to this function > > (process:8432): GLib-GObject-CRITICAL **: g_object_new: assertion `G_TYPE_IS_OBJECT (object_type)' failed > > (process:8432): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread -1219008800 (LWP 8432)] > 0x006c9bde in gconf_client_reverse_change_set () at /home/misc/ekiga/site-dir/usr/include/ptclib/http.h:498 > (gdb) bt > #0 0x006c9bde in gconf_client_reverse_change_set () at /home/misc/ekiga/site-dir/usr/include/ptclib/http.h:498 > #1 0x006cd1e9 in gconf_client_get_default () at /home/misc/ekiga/site-dir/usr/include/ptclib/http.h:498 > #2 0x080f90d7 in gm_conf_init () at gmconf-gconf.c:277 > #3 0x080c7da4 in main (argc=1, argv=0xbfb6ab24, envp=0xbfb6ab2c) at gui/main.cpp:4039 > > > Have You got idea what might be the reason? > Should I do anything else before initial running of ekiga. > > Ekiga is installed in the running system (/usr, /etc). ptlib and opal are installed in /home/misc/ekiga/site-dir. > > ptlib, opal and ekiga sources were taken from svn 2 hours ago (Tuesday, October 30 2007, Time: 11 33 PM, Eastern europe time). > > regards, > Pawel > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list The problem was that for compilation of ptlib and opal I used: make opt, instead of plain make regards, Pawel From stefano.costa at bluewind.it Wed Oct 31 10:25:14 2007 From: stefano.costa at bluewind.it (stefano costa) Date: Wed, 31 Oct 2007 11:25:14 +0100 Subject: [Ekiga-list] Ekiga on Windows: speaker as a ring device Message-ID: <4728580A.90600@bluewind.it> Hello, I'm using Ekiga under Windows in my office and like it a lot. Only problem is: we usually phone with headsets here, and it's not usefull to hear the incoming call "ring" in the headsets themselves. It should be possible to send the ring to the PC speaker, but I can't find such option. In the "Preferences", I see an "alternate perihperal" selection but I only have a choice for the PC soundcard, while with other phone clients I can also select the PC speaker. Any hint? Thanks!! -- Stefano Costa, R&D Manager www.bluewind.it/stefanoco M +39 335 6565749 Skype stefanocosta.bluewind From iskaz at intracomdefense.com Wed Oct 31 12:41:31 2007 From: iskaz at intracomdefense.com (=?UTF-8?B?zqPOus6xzrbOr866zrfPgiDOmc+JzqzOvc69zrfPgg==?=) Date: Wed, 31 Oct 2007 14:41:31 +0200 Subject: [Ekiga-list] Ekiga + FlyDVB-T Duo video card Message-ID: <472877FB.6060706@intracomdefense.com> Hi, I have installed a FlyDVB-T Duo video card (PCMCIA) in my system which works with Mandriva 2008 Linux. The ekiga version which I am running is 2.0.11 The video device (works with saa7134, saa7134_dvb modules) has been recognized (as a V4l2 device) both from operating system and ekiga. My problem is that in the ekiga video window the picture aspect ratio is not correct. The video works fine, but it is not covering the whole video window. At the right site of the video window, I see a big black line which fills the gab between the video window and the ekiga application. Is there any way to set manually the resolution of the video or the aspect ratio? Regards, Ioannis Skazikis From DAVE.HIGTON at nice.com Wed Oct 31 12:41:26 2007 From: DAVE.HIGTON at nice.com (Dave Higton) Date: Wed, 31 Oct 2007 12:41:26 -0000 Subject: [Ekiga-list] Ekiga rpm for Fedora Core 5? In-Reply-To: References: Message-ID: > Have you considered using RHEL instead because of > the longer support cycle? > > Best wishes, > Oisin Feeley > > 1. FedoraLegacy may not be around much longer! They have problems > with getting enough community support/funding. Most people that want > a platform with longer maintenance times use RHEL (or if they can't > afford the licensing CentOS). Probably you know that. Good luck. The economics require that the OS we use must be legally free. RHEL doesn't meet that criterion, does it? We will update quite soon, probably to FC8. Once we have a system in place for dealing with updates, we will be able to do it easier and therefore probably more frequently. Dave ************************************************************************************************************************************************************************************************************************************************* NICE CTI Systems UK Limited ("NICE") is registered in England under company number, 3403044. The registered office of NICE is at Tollbar Way, Hedge End, Southampton, Hampshire SO30 2ZP. Confidentiality: This communication and any attachments are intended for the above-named persons only and may be confidential and/or legally privileged. Any opinions expressed in this communication are not necessarily those of NICE. If this communication has come to you in error you must take no action based on it, nor must you copy or show it to anyone; please delete/destroy and inform the sender by e-mail immediately. Monitoring: NICE may monitor incoming and outgoing e-mails. Viruses: Although we have taken steps toward ensuring that this e-mail and attachments are free from any virus, we advise that in keeping with good computing practice the recipient should ensure they are actually virus free. **************************************************************************************************************************************************************************************************************************************************** From dsandras at seconix.com Wed Oct 31 13:10:13 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 31 Oct 2007 14:10:13 +0100 Subject: [Ekiga-list] Ekiga on Windows: speaker as a ring device In-Reply-To: <4728580A.90600@bluewind.it> References: <4728580A.90600@bluewind.it> Message-ID: <1193836213.16764.5.camel@scorpion> Hello, Le mercredi 31 octobre 2007 ? 11:25 +0100, stefano costa a ?crit : > Hello, > I'm using Ekiga under Windows in my office and like it a lot. Only > problem is: we usually phone with headsets here, and it's not usefull to > hear the incoming call "ring" in the headsets themselves. It should be > possible to send the ring to the PC speaker, but I can't find such option. > > In the "Preferences", I see an "alternate perihperal" selection but I > only have a choice for the PC soundcard, while with other phone clients > I can also select the PC speaker. Any hint? We do not support playing sound through the PC Speaker, however, if you have speakers connected to your soundcard, it will play the sound through those speakers. Actually, we are using the WIN32 API and anything that will appear as a Speaker will work. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From dsandras at seconix.com Wed Oct 31 13:13:04 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 31 Oct 2007 14:13:04 +0100 Subject: [Ekiga-list] Ekiga + FlyDVB-T Duo video card In-Reply-To: <472877FB.6060706@intracomdefense.com> References: <472877FB.6060706@intracomdefense.com> Message-ID: <1193836384.16764.7.camel@scorpion> Le mercredi 31 octobre 2007 ? 14:41 +0200, ???????? ??????? a ?crit : > Hi, I have installed a FlyDVB-T Duo video card (PCMCIA) in my system > which works with Mandriva 2008 Linux. > The ekiga version which I am running is 2.0.11 > > The video device (works with saa7134, saa7134_dvb modules) has been > recognized (as a V4l2 device) both from operating system and ekiga. > > My problem is that in the ekiga video window the picture aspect ratio is > not correct. > The video works fine, but it is not covering the whole video window. > At the right site of the video window, I see a big black line which > fills the gab between the video window and the ekiga application. > > Is there any way to set manually the resolution of the video or the > aspect ratio? > In Ekiga 3.00, you will have that possibility, however, it is not supported in Ekiga 2.00. -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From david.bercot at wanadoo.fr Wed Oct 31 13:30:51 2007 From: david.bercot at wanadoo.fr (David BERCOT) Date: Wed, 31 Oct 2007 14:30:51 +0100 Subject: [Ekiga-list] STUN - NAT : impossible to connect... In-Reply-To: <20071029161035.0fda6909@wanadoo.fr> References: <20071029154658.6be6084e@wanadoo.fr> <20071029161035.0fda6909@wanadoo.fr> Message-ID: <20071031143051.1d5be076@wanadoo.fr> Hi, I'm sorry to bother you again, but I think it is possible to use Ekiga through a tunnel, no ? If I'd like to specify a particular way, it would be possible ? Thank you very much. David. Le Mon, 29 Oct 2007 16:10:35 +0100, David BERCOT a ?crit : > Hi again, > > Le Mon, 29 Oct 2007 15:58:00 +0100, > "michel memeteau" a ?crit : > > Hi what kind of tunnel ? Over http(s) ? > > No, a direct tunnel !!! For example : > ssh -N -f monserveyr -L9110:pop.wanadoo.fr:110 > > > How do you connect to the web ? via a http proxy ? > > At work, yes. But through my tunnel, I can do what I want ;-) > > David. > > > On 10/29/07, David BERCOT wrote: > > > > > > Hi, > > > > > > At work, I've just tried to connect with Ekiga (Ekiga-snapshot on > > > Debian/Sid). > > > I've launched the STUN detection and the result is : "blocked" !!! > > > (in French "R?sultat du test STUN : bloqu?"). > > > > > > Now, I have a tunnel between my computer and my home which I use > > > for many things : mail, MSN, so on... > > > > > > Do you know how can I use this tunnel for Ekiga ? Which ports and > > > which servers ? > > > > > > Thank you very much. > > > > > > David. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: not available URL: From dsandras at seconix.com Wed Oct 31 14:17:28 2007 From: dsandras at seconix.com (Damien Sandras) Date: Wed, 31 Oct 2007 15:17:28 +0100 Subject: [Ekiga-list] STUN - NAT : impossible to connect... In-Reply-To: <20071031143051.1d5be076@wanadoo.fr> References: <20071029154658.6be6084e@wanadoo.fr> <20071029161035.0fda6909@wanadoo.fr> <20071031143051.1d5be076@wanadoo.fr> Message-ID: <1193840248.16764.14.camel@scorpion> Hi, Le mercredi 31 octobre 2007 ? 14:30 +0100, David BERCOT a ?crit : > Hi, > > I'm sorry to bother you again, but I think it is possible to use Ekiga > through a tunnel, no ? > > If I'd like to specify a particular way, it would be possible ? I don't see how it can be done, but perhaps it is indeed possible... > Thank you very much. > > David. > > Le Mon, 29 Oct 2007 16:10:35 +0100, > David BERCOT a ?crit : > > > Hi again, > > > > Le Mon, 29 Oct 2007 15:58:00 +0100, > > "michel memeteau" a ?crit : > > > Hi what kind of tunnel ? Over http(s) ? > > > > No, a direct tunnel !!! For example : > > ssh -N -f monserveyr -L9110:pop.wanadoo.fr:110 > > > > > How do you connect to the web ? via a http proxy ? > > > > At work, yes. But through my tunnel, I can do what I want ;-) > > > > David. > > > > > On 10/29/07, David BERCOT wrote: > > > > > > > > Hi, > > > > > > > > At work, I've just tried to connect with Ekiga (Ekiga-snapshot on > > > > Debian/Sid). > > > > I've launched the STUN detection and the result is : "blocked" !!! > > > > (in French "R?sultat du test STUN : bloqu?"). > > > > > > > > Now, I have a tunnel between my computer and my home which I use > > > > for many things : mail, MSN, so on... > > > > > > > > Do you know how can I use this tunnel for Ekiga ? Which ports and > > > > which servers ? > > > > > > > > Thank you very much. > > > > > > > > David. > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- _ Damien Sandras (o- //\ Ekiga Softphone : http://www.ekiga.org/ v_/_ NOVACOM : http://www.novacom.be/ FOSDEM : http://www.fosdem.org/ SIP Phone : sip:dsandras at ekiga.net From thedogfarted at gmail.com Wed Oct 31 14:45:23 2007 From: thedogfarted at gmail.com (=?UTF-8?Q?J=C4=81nis_Ruk=C5=A1=C4=81ns?=) Date: Wed, 31 Oct 2007 16:45:23 +0200 Subject: [Ekiga-list] STUN - NAT : impossible to connect... In-Reply-To: <1193840248.16764.14.camel@scorpion> References: <20071029154658.6be6084e@wanadoo.fr> <20071029161035.0fda6909@wanadoo.fr> <20071031143051.1d5be076@wanadoo.fr> <1193840248.16764.14.camel@scorpion> Message-ID: Hi, On 10/31/07, Damien Sandras wrote: > Hi, > > Le mercredi 31 octobre 2007 ? 14:30 +0100, David BERCOT a ?crit : > > Hi, > > > > I'm sorry to bother you again, but I think it is possible to use Ekiga > > through a tunnel, no ? > > > > If I'd like to specify a particular way, it would be possible ? > > > I don't see how it can be done, but perhaps it is indeed possible... > As far as I understand the only way to reach outside world is through SSH, all other ports are blocked. If so, the only thing that comes in mind is to setting up a SIP proxy on the remote box, tunneling the whole port range (requires some hacks because SSH is capable of TCP tunneling only) and configuring localhost as an outbound proxy. Even if that works, I expect the sound quality will be bad in the best case. > > Thank you very much. > > > > David. > > > > Le Mon, 29 Oct 2007 16:10:35 +0100, > > David BERCOT a ?crit : > > > > > Hi again, > > > > > > Le Mon, 29 Oct 2007 15:58:00 +0100, > > > "michel memeteau" a ?crit : > > > > Hi what kind of tunnel ? Over http(s) ? > > > > > > No, a direct tunnel !!! For example : > > > ssh -N -f monserveyr -L9110:pop.wanadoo.fr:110 > > > > > > > How do you connect to the web ? via a http proxy ? > > > > > > At work, yes. But through my tunnel, I can do what I want ;-) > > > > > > David. > > > > > > > On 10/29/07, David BERCOT wrote: > > > > > > > > > > Hi, > > > > > > > > > > At work, I've just tried to connect with Ekiga (Ekiga-snapshot on > > > > > Debian/Sid). > > > > > I've launched the STUN detection and the result is : "blocked" !!! > > > > > (in French "R?sultat du test STUN : bloqu?"). > > > > > > > > > > Now, I have a tunnel between my computer and my home which I use > > > > > for many things : mail, MSN, so on... > > > > > > > > > > Do you know how can I use this tunnel for Ekiga ? Which ports and > > > > > which servers ? > > > > > > > > > > Thank you very much. > > > > > > > > > > David. > > _______________________________________________ > > ekiga-list mailing list > > ekiga-list at gnome.org > > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- > _ Damien Sandras > (o- > //\ Ekiga Softphone : http://www.ekiga.org/ > v_/_ NOVACOM : http://www.novacom.be/ > FOSDEM : http://www.fosdem.org/ > SIP Phone : sip:dsandras at ekiga.net > > > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list -- Ian From hazel_russman at yahoo.co.uk Wed Oct 31 16:37:37 2007 From: hazel_russman at yahoo.co.uk (Hazel Russman) Date: Wed, 31 Oct 2007 16:37:37 +0000 (GMT) Subject: [Ekiga-list] could not connect to remote host In-Reply-To: Message-ID: <655635.29604.qm@web25009.mail.ukl.yahoo.com> > > 1. Could not connect to remote host (Hazel > Russman) > 2. Re: Could not connect to remote host (yannick) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 29 Oct 2007 16:53:06 +0000 (GMT) > From: Hazel Russman > Subject: [Ekiga-list] Could not connect to remote > host > To: ekiga-list at gnome.org > Message-ID: > <264823.97234.qm at web25012.mail.ukl.yahoo.com> > Content-Type: text/plain; charset="iso-8859-1" > > I am having difficulty in getting ekiga working. I > have an account at ekiga.net and it appears to be > valid as I can log in there. But when I try the echo > test, I get first "Registration failed - timeout" > and > then "Could not connect to remote host". > > My setup: I am using Linux pppoe behind a SMC > Barricade adsl router/modem. This has a built-in > firewall (configurable via the web browser) but I > have > not changed its default settings. As far as I can > see, > it is not doing any packet filtering or nat, > although > there are timing checks to prevent DoS attacks. The > ekiga configuration druid's nat test reported "open > nat". I normally have a simple iptables-based > firewall > on the computer itself but I flushed it away before > testing ekiga. > > I have looked at the ekiga manual but have not found > anything that looks relevant (apparently this error > message is sometimes caused by a nat problem but not > with open nat). > > I attach the transcript of a level-4 debug run > (slightly edited for privacy) which I hope will be > useful for pinpointing what is going wrong. > > Thanks in advance > Hazel > > > > > ------------------------------ > > Message: 2 > Date: Mon, 29 Oct 2007 18:31:57 +0100 > From: yannick > Subject: Re: [Ekiga-list] Could not connect to > remote host > To: Ekiga mailing list > Message-ID: <1193679117.7000.7.camel at achille> > Content-Type: text/plain; charset=utf-8 > > Hi, > > Maybe this wont solve your issue, you're using a > *very* old version of > ekiga (2.0.1), we now are up to 2.0.11 > > Consider upgrading it. > > Regards, > Yannick > > Thanks, Yannick. but that's not so easy. I am using Ubuntu Dapper and this version is the latest that it recognises (at least for my present list of repositories). I notice that the version available from ekiga.org is for Feisty. Would that one actually run on Dapper if I installed it? Or would it be better to download source and build it myself? I have a little experience with building packages (though not on Ubuntu) but I don't want to do anything that involves upgrading libraries. You can really louse up your system doing that kind of thing! ___________________________________________________________ Yahoo! Answers - Got a question? Someone out there knows the answer. Try it now. http://uk.answers.yahoo.com/ From sevmek at free.fr Wed Oct 31 17:32:52 2007 From: sevmek at free.fr (yannick) Date: Wed, 31 Oct 2007 18:32:52 +0100 Subject: [Ekiga-list] could not connect to remote host In-Reply-To: <655635.29604.qm@web25009.mail.ukl.yahoo.com> References: <655635.29604.qm@web25009.mail.ukl.yahoo.com> Message-ID: <1193851972.12149.9.camel@achille> Le mercredi 31 octobre 2007 ? 16:37 +0000, Hazel Russman a ?crit : > > > > 1. Could not connect to remote host (Hazel > > Russman) > > 2. Re: Could not connect to remote host (yannick) > > > > > > > ---------------------------------------------------------------------- > > > > Message: 1 > > Date: Mon, 29 Oct 2007 16:53:06 +0000 (GMT) > > From: Hazel Russman > > Subject: [Ekiga-list] Could not connect to remote > > host > > To: ekiga-list at gnome.org > > Message-ID: > > <264823.97234.qm at web25012.mail.ukl.yahoo.com> > > Content-Type: text/plain; charset="iso-8859-1" > > > > I am having difficulty in getting ekiga working. I > > have an account at ekiga.net and it appears to be > > valid as I can log in there. But when I try the echo > > test, I get first "Registration failed - timeout" > > and > > then "Could not connect to remote host". > > > > My setup: I am using Linux pppoe behind a SMC > > Barricade adsl router/modem. This has a built-in > > firewall (configurable via the web browser) but I > > have > > not changed its default settings. As far as I can > > see, > > it is not doing any packet filtering or nat, > > although > > there are timing checks to prevent DoS attacks. The > > ekiga configuration druid's nat test reported "open > > nat". I normally have a simple iptables-based > > firewall > > on the computer itself but I flushed it away before > > testing ekiga. > > > > I have looked at the ekiga manual but have not found > > anything that looks relevant (apparently this error > > message is sometimes caused by a nat problem but not > > with open nat). > > > > I attach the transcript of a level-4 debug run > > (slightly edited for privacy) which I hope will be > > useful for pinpointing what is going wrong. > > > > Thanks in advance > > Hazel > > > > > > > > > ------------------------------ > > > > Message: 2 > > Date: Mon, 29 Oct 2007 18:31:57 +0100 > > From: yannick > > Subject: Re: [Ekiga-list] Could not connect to > > remote host > > To: Ekiga mailing list > > Message-ID: <1193679117.7000.7.camel at achille> > > Content-Type: text/plain; charset=utf-8 > > > > Hi, > > > > Maybe this wont solve your issue, you're using a > > *very* old version of > > ekiga (2.0.1), we now are up to 2.0.11 > > > > Consider upgrading it. > > > > Regards, > > Yannick > > > > > Thanks, Yannick. but that's not so easy. I am using > Ubuntu Dapper and this version is the latest that it > recognises (at least for my present list of > repositories). I notice that the version available > from ekiga.org is for Feisty. Would that one actually > run on Dapper if I installed it? Or would it be better > to download source and build it myself? I have a > little experience with building packages (though not > on Ubuntu) but I don't want to do anything that > involves upgrading libraries. You can really louse up > your system doing that kind of thing! > Hi, You can try this repository: https://help.ubuntu.com/community/Ekiga?action=recall&rev=78#head-57385c7cf79361cbb4d7195b9f43c1bb33c1e94c Regards, Yannick > > ___________________________________________________________ > Yahoo! Answers - Got a question? Someone out there knows the answer. Try it > now. > http://uk.answers.yahoo.com/ > _______________________________________________ > ekiga-list mailing list > ekiga-list at gnome.org > http://mail.gnome.org/mailman/listinfo/ekiga-list > -- Me joindre en t?l?phonie IP / vid?oconf?rence ? sip:yannick at ekiga.net Logiciel de VoIP Ekiga : http://www.ekiga.org http://wiki.ekiga.org/index.php/Which_programs_work_with_Ekiga_%3F From h.riesbeck at sympatico.ca Wed Oct 31 19:25:24 2007 From: h.riesbeck at sympatico.ca (H.Riesbeck) Date: Wed, 31 Oct 2007 15:25:24 -0400 Subject: [Ekiga-list] Ekiga very slow disconnecting Message-ID: <4728D6A4.6040208@sympatico.ca> I am new user to Ekiga. It runs in SuSE 10.3. When disconnecting a call, it takes abnormally long to disconnect although I can hang up on a call with ctrl D. I do not know if that is normal. So in order to place another call, I force the application to quit. This however results in requiring to reboot the system otherwise the application will not start again after a forced quit. Any remedial suggestions would be much appreciated. -hr