[Ekiga-list] Ekiga.net SIP Server Moved

2006-12-23 Thread Damien Sandras
Hello to all,


I have moved the Ekiga.net SIP server and associated services to its new
host.

I have updated the IP address of the server, the DNS server should
shortly make ekiga.net point to 86.64.162.35.

If it doesn't, then it means you are still registering to the old
server. The consequences are the following :
- you can not reach users registered to the new server
- users registered to the new server can not reach you
- if the old server had sent you an e-mail so that you can confirm your
account, it will not be possible to confirm it on the old server. You
will have to wait for your DNS server to point to the new server in
order to be able to confirm the account.

The new server also has a new module for audio conferencing, using the
same numbers.

I will make an official announcement later.
-- 
 _  Damien Sandras
(o- 
//\   Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
  FOSDEM  : http://www.fosdem.org/
  SIP Phone   : sip:[EMAIL PROTECTED]
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] ekiga help system

2006-12-23 Thread yannick
Le samedi 23 décembre 2006 à 14:50 -0600, Gene Imes a écrit :
> I use gentoo which has an automatic installer. What must I do to get 
> ekiga help to work?

You need the gnome help reader : "yelp"

Regards,
Yannick

> 
> Thanks,
> 
> 
-- 
Me joindre en téléphonie IP / vidéoconférence ?
sip:[EMAIL PROTECTED]

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Suggestion: a front end hook for ekiga

2006-12-23 Thread ael
Damien Sandras wrote:
> Le samedi 23 décembre 2006 à 16:16 +, ael a écrit :
> 
>>>The real question is : why do you have to do that? Mixer settings should
>>>be remembered accross reboots, and should not be changed while you are
>>>logged.
>>>
>>
>>1) I don't want a microphone active when I am not using it. Also
>>possible security issues there.
>>
>>2) I find that I need to adjust PCM, FM and master volume levels among
>>others to suit various applications. Some are otherwise just too quiet,
>>others deafen me.
>>
>>3) Capture selection/setting also needs adjusting for various
>>applications. When I install ekiga on a new machine, I often think the
>>microphone is not working until I remember that it must be in Capture
>>mode for ekiga. I have been caught by that several times :-)
>>
>>4) If I start ekiga with my default mixer setting ekiga does not work:
>>no microphone input, and very quiet output.
>>
>>So I find that I freqently need to adjust mixer settings depending on
>>which application I am running. mplayer, realplayer [spit], aplay,
>>timidity, aplaymidi, ekiga and so on...
> 
> 
> That's a good justification :-)

:-) And I forgot one of the most important:-

5) If I am running another sound application and a call comes in to
ekiga, I don't have time to launch a mixer control program, and fiddle
with the settings before answering in ekiga...

My current bash script does the job, but I wonder why other people don't
(apparently) have the same problem.

A E Lawrence

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] ekiga help system

2006-12-23 Thread Gene Imes
I use gentoo which has an automatic installer. What must I do to get 
ekiga help to work?

Thanks,


-- 
Gene Imes = ozob.net
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


[Ekiga-list] uvc cam and green video

2006-12-23 Thread Gene Imes
I have a uvc cam which is a ProScopeHR. I works with luvcview nicely 
however with ekiga the image is green with every other scan line missing.

Is there some setting I can set to change the type of video?

With luvcview I must start it like so to work:

luvcview -d /dev/video0 -f yuv

Thanks for any help at all,


-- 
Gene Imes = ozob.net
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] STUN registration

2006-12-23 Thread Damien Sandras
Hi Wolfgram,

Le samedi 23 décembre 2006 à 21:01 +0100, Wolfram Wagner a écrit :
> Thanks for your reply. It took a while until I had time again.
> 
> Please remember, I have problems with registration and get a 404 not 
> found message.
>  Last time you answered me, that I should sniff a bit. So I did.
> 
> I found out, that registration at STUN server is done maybe by using a 
> wrong IP. My current IP is 84.159.48.129.
> 
> 
> In STUN Registration I see contact binding:
>   URI: 
> 
> Then my client sends SUBSCRIBE using the same wrong IP Address.
> 
> Next I get a 404 Error (not found) telling me 
> Sent-by Address: 84.159.61.31
> Sent-by port: 5074
> ...
> RPort: 5074
> Received: 84.159.48.129
> ...
> Warning: 392 192.168.70.52:5060 "Noisy feedback tells:  pid=16986 
> req_src_ip=84.159.48.129 req_src_port=5074 
> in_uri=sip:[EMAIL PROTECTED] 
> out_uri=sip:[EMAIL PROTECTED] via_cnt==1"
> 
> 
> So I wonder where this IP 84.159.61.31 comes from. I checked it and it 
> is one of the dynamic addresses used by my provider. The check via 
> ekiga.net/ip returnes the correct ip.
> 
> After three more Register retries it gives up.
> 
> 
> Might it be possible that this wrong ip address makes problems in 
> registration. Maybe the answer packages are sent to this machine.
> 

Most probably.

Either STUN is unable to determine the correct public IP address because
of complex NAT mechanisms. Or something in between is rewriting the SIP
packets. But I must admit I'm a bit lost. Try comparing the packets sent
by Ekiga with those that you are able to snif, if they are different,
then one of the routers is changing the packets.


> Thanks and Have a very nice Christmas!
> 

Thanks, you too!!!


> Wolfram
> 
> Your last answer:
> Le vendredi 01 d?cembre 2006 ? 20:57 +0100, Wolfram Wagner a ?crit :
> 
> > I have posted it to  http://pastebin.ca/263742
> > 
> > I see a 404 Error followed by a timeout when waitung for PDU. I have 
> not 
> > enough insight to know what this means... 
> > 
> 
> The 404 is for the SUBSCRIBE (it is a normal behavior). The timeout is
> for the REGISTER.
> 
> That means that :
> - the SUBSCRIBE reaches ekiga.net
> - the REGISTER, which is identical, doesn't reach ekiga.net OR the reply
> to the REGISTER doesn't reach your internal host
> 
> Can you sniff the traffic on the routers to see what happens?
> 
> I have the feeling that one of them is either dropping the REGISTER, or
> dropping the answer to the REGISTER or simply rewriting the REGISTER in
> such a way that the answer never reaches you...
> ___
> ekiga-list mailing list
> ekiga-list@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:[EMAIL PROTECTED]
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Sipcall and Ekiga

2006-12-23 Thread Damien Sandras
Le samedi 23 décembre 2006 à 17:48 +0100, Gregor Horvath a écrit :
> Damien Sandras schrieb:
> > Their realm is first advertised as :
> > voipgateway.org
> > then as :
> > 212.117.200.148
> > 
> > Which explains the problem.
> > 
> > Can you try setting 212.117.200.148 as realm when registering?
> 
> Thank's. I have tried and there is some progress. Now the called mobile 
> phone rings one time but then the connection is closed and ekiga says 
> connection was terminated because of an error.
> Here's the log:
> 
> http://gregor-horvath.com/output2.txt
> 

 Can you try without video?
-- 
 _  Damien Sandras
(o- 
//\   Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
  FOSDEM  : http://www.fosdem.org/
  SIP Phone   : sip:[EMAIL PROTECTED]
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Suggestion: a front end hook for ekiga

2006-12-23 Thread Damien Sandras
Le samedi 23 décembre 2006 à 16:16 +, ael a écrit :
> > 
> > The real question is : why do you have to do that? Mixer settings should
> > be remembered accross reboots, and should not be changed while you are
> > logged.
> > 
> 
> 1) I don't want a microphone active when I am not using it. Also
> possible security issues there.
> 
> 2) I find that I need to adjust PCM, FM and master volume levels among
> others to suit various applications. Some are otherwise just too quiet,
> others deafen me.
> 
> 3) Capture selection/setting also needs adjusting for various
> applications. When I install ekiga on a new machine, I often think the
> microphone is not working until I remember that it must be in Capture
> mode for ekiga. I have been caught by that several times :-)
> 
> 4) If I start ekiga with my default mixer setting ekiga does not work:
> no microphone input, and very quiet output.
> 
> So I find that I freqently need to adjust mixer settings depending on
> which application I am running. mplayer, realplayer [spit], aplay,
> timidity, aplaymidi, ekiga and so on...

That's a good justification :-)
-- 
 _  Damien Sandras
(o- 
//\   Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
  FOSDEM  : http://www.fosdem.org/
  SIP Phone   : sip:[EMAIL PROTECTED]
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] STUN registration

2006-12-23 Thread Wolfram Wagner
Hello Damien, 

Thanks for your reply. It took a while until I had time again.

Please remember, I have problems with registration and get a 404 not 
found message.
 Last time you answered me, that I should sniff a bit. So I did.

I found out, that registration at STUN server is done maybe by using a 
wrong IP. My current IP is 84.159.48.129.


In STUN Registration I see contact binding:
URI: 

Then my client sends SUBSCRIBE using the same wrong IP Address.

Next I get a 404 Error (not found) telling me 
Sent-by Address: 84.159.61.31
Sent-by port: 5074
...
RPort: 5074
Received: 84.159.48.129
...
Warning: 392 192.168.70.52:5060 "Noisy feedback tells:  pid=16986 
req_src_ip=84.159.48.129 req_src_port=5074 
in_uri=sip:[EMAIL PROTECTED] 
out_uri=sip:[EMAIL PROTECTED] via_cnt==1"


So I wonder where this IP 84.159.61.31 comes from. I checked it and it 
is one of the dynamic addresses used by my provider. The check via 
ekiga.net/ip returnes the correct ip.

After three more Register retries it gives up.


Might it be possible that this wrong ip address makes problems in 
registration. Maybe the answer packages are sent to this machine.

Thanks and Have a very nice Christmas!

Wolfram

Your last answer:
Le vendredi 01 d?cembre 2006 ? 20:57 +0100, Wolfram Wagner a ?crit :

> I have posted it to  http://pastebin.ca/263742
> 
> I see a 404 Error followed by a timeout when waitung for PDU. I have 
not 
> enough insight to know what this means... 
> 

The 404 is for the SUBSCRIBE (it is a normal behavior). The timeout is
for the REGISTER.

That means that :
- the SUBSCRIBE reaches ekiga.net
- the REGISTER, which is identical, doesn't reach ekiga.net OR the reply
to the REGISTER doesn't reach your internal host

Can you sniff the traffic on the routers to see what happens?

I have the feeling that one of them is either dropping the REGISTER, or
dropping the answer to the REGISTER or simply rewriting the REGISTER in
such a way that the answer never reaches you...
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Sipcall and Ekiga

2006-12-23 Thread Gregor Horvath
Damien Sandras schrieb:
> Their realm is first advertised as :
> voipgateway.org
> then as :
> 212.117.200.148
> 
> Which explains the problem.
> 
> Can you try setting 212.117.200.148 as realm when registering?

Thank's. I have tried and there is some progress. Now the called mobile 
phone rings one time but then the connection is closed and ekiga says 
connection was terminated because of an error.
Here's the log:

http://gregor-horvath.com/output2.txt

--
Gregor
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Suggestion: a front end hook for ekiga

2006-12-23 Thread ael
Damien Sandras wrote:
> Le vendredi 22 décembre 2006 à 23:43 +, ael a écrit :
> 
>>My sound card is rather complex as viewed by ALSA. To use ekiga, I need
>>to launch alsamixer or one of its variants and set at least 4 different
>>controls which are not very memorable.
>>
>>Instead I have used alsactl to store the configuration in a special
>>"ekiga-alsa.cfg" file. Then I can use
>>alsactl -f /path/ekiga-alsa.cfg restore ; ekiga &
>>
>>In fact, I just wrap that up as a tiny little bash script called
>>ekiga_go. I would probably forget that path = /usr/local/etc/ otherwise :-)
>>
>>This is probably re-inventing the wheel, but should ekiga have a
>>facility to run a custom sound set-up script at start up? Or have I
>>missed the documentation?
> 
> 
> 
> The real question is : why do you have to do that? Mixer settings should
> be remembered accross reboots, and should not be changed while you are
> logged.
> 

1) I don't want a microphone active when I am not using it. Also
possible security issues there.

2) I find that I need to adjust PCM, FM and master volume levels among
others to suit various applications. Some are otherwise just too quiet,
others deafen me.

3) Capture selection/setting also needs adjusting for various
applications. When I install ekiga on a new machine, I often think the
microphone is not working until I remember that it must be in Capture
mode for ekiga. I have been caught by that several times :-)

4) If I start ekiga with my default mixer setting ekiga does not work:
no microphone input, and very quiet output.

So I find that I freqently need to adjust mixer settings depending on
which application I am running. mplayer, realplayer [spit], aplay,
timidity, aplaymidi, ekiga and so on...

A E Lawrence
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Sipcall and Ekiga

2006-12-23 Thread Damien Sandras
Their realm is first advertised as :
voipgateway.org
then as :
212.117.200.148

Which explains the problem.

Can you try setting 212.117.200.148 as realm when registering?

Le samedi 23 décembre 2006 à 12:44 +0100, Gregor Horvath a écrit :
> Damien Sandras schrieb:
> 
> > 
> > Please post a -d 4 output somewhere.
> 
> 
> http://gregor-horvath.com/output.txt.bz2
> 
> 
> Thanks for your help
> 
> --
> Gregor
> 
> 
> ___
> ekiga-list mailing list
> ekiga-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/ekiga-list
-- 
Damien Sandras <[EMAIL PROTECTED]>

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Sipcall and Ekiga

2006-12-23 Thread Gregor Horvath
Damien Sandras schrieb:

> 
> Please post a -d 4 output somewhere.


http://gregor-horvath.com/output.txt.bz2


Thanks for your help

--
Gregor


___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Sipcall and Ekiga

2006-12-23 Thread Damien Sandras
Le vendredi 22 décembre 2006 à 07:51 +0100, Gregor Horvath a écrit :
> Hi,
> 
> I have an account at Sipcall.at and it works with sjphone but not with 
> Ekiga. It does connect, but a call to a normal telephone fails with an 
> authentifaction error.
> 
> I have exactly the same issues as found in this thread:
> 
> http://www.mail-archive.com/gnomemeeting-list@gnome.org/msg03567.html
> 
> Any news on this?
> 
> If needed I can send the debug output.

Please post a -d 4 output somewhere.
-- 
 _  Damien Sandras
(o- 
//\   Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
  FOSDEM  : http://www.fosdem.org/
  SIP Phone   : sip:[EMAIL PROTECTED]
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list


Re: [Ekiga-list] Suggestion: a front end hook for ekiga

2006-12-23 Thread Damien Sandras
Le vendredi 22 décembre 2006 à 23:43 +, ael a écrit :
> My sound card is rather complex as viewed by ALSA. To use ekiga, I need
> to launch alsamixer or one of its variants and set at least 4 different
> controls which are not very memorable.
> 
> Instead I have used alsactl to store the configuration in a special
> "ekiga-alsa.cfg" file. Then I can use
> alsactl -f /path/ekiga-alsa.cfg restore ; ekiga &
> 
> In fact, I just wrap that up as a tiny little bash script called
> ekiga_go. I would probably forget that path = /usr/local/etc/ otherwise :-)
> 
> This is probably re-inventing the wheel, but should ekiga have a
> facility to run a custom sound set-up script at start up? Or have I
> missed the documentation?


The real question is : why do you have to do that? Mixer settings should
be remembered accross reboots, and should not be changed while you are
logged.

-- 
 _  Damien Sandras
(o- 
//\   Ekiga Softphone : http://www.ekiga.org/
v_/_ NOVACOM : http://www.novacom.be/
  FOSDEM  : http://www.fosdem.org/
  SIP Phone   : sip:[EMAIL PROTECTED]
   

___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list