Re: [Ekiga-list] Ekiga.net discontinued

[Damien Sandras]

Hi,

Le jeudi 06 décembre 2018 à 22:55 +0100, Gerhard Pircher a écrit :
> Am 2018-12-01 um 18:35 schrieb Damien Sandras:
> > Due to the lack of time, and to the last outages, I have taken
> > thedecision to discontinue EKIGA.NET before the end of the year.
> > Thank you for your support during all those years.
> > It has been a pleasure!
> I just wanted to say thank you for keeping the ekiga.net service
> upand running all those years!

Thank you for the nice words!
Best regards,
-- 
Damien Sandras 
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net discontinued

[Stuart D. Gathman]

On Sat, 1 Dec 2018, A Human via ekiga-list wrote:


how can i unsubscribe from this list pls


Use the link at the bottom.  I'm copying it here:

https://mail.gnome.org/mailman/listinfo/ekiga-list


--
  Stuart D. Gathman 
"Confutatis maledictis, flamis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net discontinued

[Damien Sandras]

Hi Bret,
Thank you for your email and support.
You are absolutely right...
Actually, Ekiga, the software, is not discontinued. Ekiga.net, the SIP
platform that goes with it, will be shutting down by the end of the
year.
However, actually, the state of the software is not better. I have
actively maintained ekiga during more or less 12 to 13 years. A new
version is nearly ready (without instant messaging support anymore, and
without STUN/NAT support). A few years ago, I asked for help to finish
it. It was a call to developers, but nobody answered.
Having to maintain the software, the SIP platform, the websites, the
manuals, the documentation for that new release alone is simply not
possible. It would be if I was unemployed. But in that case, the "free"
as "free beer" aspect of Open Source would be annoying for me :-)
So well, if developers want to keep working on the Ekiga software, they
are welcome. The code is in GNOME's git, available for everyone!
Le dimanche 02 décembre 2018 à 06:15 +0800, Bret Busby via ekiga-list a
écrit :
> On 02/12/2018, Damien Sandras  wrote:
> > Hi all,
> > Due to the lack of time, and to the last outages, I have taken
> > thedecision to discontinue EKIGA.NET before the end of the year.
> > Thank you for your support during all those years.
> > It has been a pleasure!--
> > 
> > 
> > 
> > 
> > 
> > 
> > Damien SANDRAS
> > 
> > 
> > Ekiga Project
> > http://www.ekiga.org
> > 
> > 
> > 
> > 
> 
> Hello.
> I am wondering whether, given that Ekiga is said to be open
> source,rather than, as its owner, simply shutting it down, it would
> not bemore appropriate and consistent with the (perceived) nature of
> opensource,, to seek a new group of people, to take it on, for the
> sake ofits continuance.
> More and more good  Linux software, has been
> abandoned/discontinued,and, with MS apparently determined to
> progressively eliminate skype(MS has been p[rogressively hobbling
> skype, since MS bought it out), adeveloping technology in IT - the
> means od making video calls, amongstother uses, is being eliminated.
> It is a bit like, if Alexander Bellhad decided that he had had enough
> of trying to develop telephony, andsaid "Stuff it - I've had enough -
> I am going to put it all into boxesand bury it.", rather than passing
> it on to others to continue thedevelopment.
> Imagine what the world would be like, if we had not had
> telephony.Imagine what the wotld could be like, if we would have
> video calls andvideoconferencing, as commonplace, as telephony has
> been.
> Here in Australia, members of the federal parliament, fly thousands
> ofkilometres, to sit in the parliament (when they can be
> botheredturning up for "work" - the federal parliament is apparently
> scheduledto meet, for only ten days, in the next eight months, while
> itsmembers hibernate (and, hide from each other) ), and, whilst
> theAustralian federal partliament does not want to progress from
> thestone age, if its members used virtual attendance,
> throughvideoconferencing, it could save the country a fortune, and,
> show thatAustralia is not really such a stupid and backward country,
> that itappears to be (we have a federal government, that is obsessed
> withburning as much cpoall as possible, as it is worried about
> theincreasing chill in the air).
> So, while MS is doing as much as it can, to obstruct
> communications,with its progressive hobbling of skype, if Ekiga could
> be turned intoa community project, and, thence, continue to be
> developed andmaintained, instead of being abandoned, like so much
> other Linuxsoftware, we could have hope, that communications
> technology willcontinue to advance, instead of being abandoned  and
> left in unusablepieces on the side of the road..
> So, rather than simply abandoning Ekiga, I ask whether it could
> beoffered as a community project, so as to provide for its
> continueddevelopment, maintenance, and, support, rather than simply
> abandoningit.
-- 



  
  


Damien SANDRAS



Ekiga Project 

http://www.ekiga.org



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

Re: [Ekiga-list] Ekiga.net discontinued

[A Human via ekiga-list]

how can i unsubscribe from this list pls

Le sam. 1 déc. 2018 à 20:45, Stuart D. Gathman  a
écrit :

> On Sun, 2 Dec 2018, Bret Busby via ekiga-list wrote:
>
> > On 02/12/2018, Damien Sandras  wrote:
> >> Due to the lack of time, and to the last outages, I have taken the
> >> decision to discontinue EKIGA.NET before the end of the year.
>
> > I am wondering whether, given that Ekiga is said to be open source,
> > rather than, as its owner, simply shutting it down, it would not be
> > more appropriate and consistent with the (perceived) nature of open
> > source,, to seek a new group of people, to take it on, for the sake of
> > its continuance.
>
> Ekiga.net is not needed for peer to peer calls.  It is only to help
> out unfortunate souls still in IP4 NAT jail because they haven't learned
> how to join the IP6 world.  ISPs will never offer IP6.  You have to
> peer with friends and/or sign up with a general tunnel broker like
> he.net.
>
> There are other sites offering free IP4 SIP call brokering (generally
> charging for POTS connections to make their money).
>
> I moved to Linphone (another open source SIP client) because it
> supported IPv6.  Peer to peer SIP really requires IPv6.
>
> The Cjdns IPv6 mesh VPN allows authenticated, encrypted peer to peer calls
> anywhere in the world without any exchange of certs, etc, and a device
> keeps its IP as it moves around.  The IPv6 is a hash of the public key
> of the node.
>
> Even without a VPN, IPv6 allows direct peer to peer without needing
> a public IP4 or a centralized site to help with all the NAT workarounds.
>
> Ekiga does a number of things better than linphone (e.g. addressbook).
> But the lack of IPv6 was a deal killer.  There were efforts to
> add IPv6 support to ekiga, but never finished that I was aware of.
> Actually, IPv6 support in Linphone is a pain - it can't listen on
> IP4 (for commercial SIP to POTS services) and IP6 simultaneously.
> You have to switch back and forth in preferences.  Ekiga could do it so
> much better.
>
> --
>   Stuart D. Gathman 
> "Confutatis maledictis, flamis acribus addictis" - background song for
> a Microsoft sponsored "Where do you want to go from here?" commercial.
> ___
> ekiga-list mailing list
> ekiga-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/ekiga-list
>
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net discontinued

[David Ford via ekiga-list]

Thanks for all the work you put in over the years Damien - sometimes it is
best to allow the world to move on without us. There is a tide in the
affairs of man - and all that Shakespeare stuff.
Sad to see it go - but you can only do so much.

Thanks again
David
Bedtime Stories (4 - 8 years)
http://www.everopenstorybook.com
Nature
https://www.ja2da.com
Random Thoughts
https://medium.com/@ford.davidj/latest



On Sat, 1 Dec 2018 at 17:36, Damien Sandras  wrote:

> Hi all,
>
> Due to the lack of time, and to the last outages, I have taken the
> decision to discontinue EKIGA.NET before the end of the year.
>
> Thank you for your support during all those years.
>
> It has been a pleasure!
>
> --
>
> Damien SANDRAS
>
> *Ekiga Project*
> http://www.ekiga.org
> ___
> ekiga-list mailing list
> ekiga-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/ekiga-list
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] Ekiga.net discontinued

[Damien Sandras]

Hi all,

Due to the lack of time, and to the last outages, I have taken the
decision to discontinue EKIGA.NET before the end of the year.

Thank you for your support during all those years.

It has been a pleasure!
-- 



  
  


Damien SANDRAS



Ekiga Project 

http://www.ekiga.org



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

Re: [Ekiga-list] Ekiga.net directory is blank

[Bob Williams]

Damien,

Many thanks. Your restart co-incided with my firewall changes, so I
incorrectly thought I'd solved the problem by opening the outgoing STUN
ports.

Ha Ha.

Bob

On Thu, 16 Mar 2017 12:06:55 +0100
Damien Sandras  wrote:

> Hi,
> The service was down. I restarted it.
> Le jeudi 16 mars 2017 à 10:19 +, Bob Williams a écrit :
> > Hi,
> > 
> > I've just installed Ekiga on openSUSE Leap 42.2 with KDE Frameworks
> > 5.
> > I've done a successful echo test so it looks like I've opened the
> > correct ports in my router and firewall.
> > 
> > When I open the Address Book, the Ekiga.net directory is empty.
> > Clicking on the Find button with no search string does nothing, but
> > there is a status bar message saying -1 users found.
> > 
> > Could I have missed some configuration option? Do I need to run an
> > openldap server?
> > 
> > Many thanks
> > 
> > Bob
> > ___
> > ekiga-list mailing list
> > ekiga-list@gnome.org
> > https://mail.gnome.org/mailman/listinfo/ekiga-list  
> -- 
> 
> 
> 
>   
>   
> 
> 
> Damien SANDRAS
> 
> 
> 
> Ekiga Project 
> 
> http://www.ekiga.org
> 
> 



-- 
Bob Williams
   System:  Linux 4.4.49-16-default
   Distro:  openSUSE 42.2 (x86_64)
   Desktop: KDE Frameworks: 5.26.0, Qt: 5.6.1 and Plasma: 5.8.2


pgppRCGn94xby.pgp
Description: OpenPGP digital signature
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net directory is blank

[Damien Sandras]

Hi,
The service was down. I restarted it.
Le jeudi 16 mars 2017 à 10:19 +, Bob Williams a écrit :
> Hi,
> 
> I've just installed Ekiga on openSUSE Leap 42.2 with KDE Frameworks
> 5.
> I've done a successful echo test so it looks like I've opened the
> correct ports in my router and firewall.
> 
> When I open the Address Book, the Ekiga.net directory is empty.
> Clicking on the Find button with no search string does nothing, but
> there is a status bar message saying -1 users found.
> 
> Could I have missed some configuration option? Do I need to run an
> openldap server?
> 
> Many thanks
> 
> Bob
> ___
> ekiga-list mailing list
> ekiga-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/ekiga-list
-- 



  
  


Damien SANDRAS



Ekiga Project 

http://www.ekiga.org


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

Re: [Ekiga-list] Ekiga.net directory is blank [SOLVED]

[Bob Williams]

On Thu, 16 Mar 2017 10:19:58 +
Bob Williams  wrote:

> Hi,
> 
> I've just installed Ekiga on openSUSE Leap 42.2 with KDE Frameworks 5.
> I've done a successful echo test so it looks like I've opened the
> correct ports in my router and firewall.
> 
> When I open the Address Book, the Ekiga.net directory is empty.
> Clicking on the Find button with no search string does nothing, but
> there is a status bar message saying -1 users found.
> 
> Could I have missed some configuration option? Do I need to run an
> openldap server?
> 
> Many thanks
> 
> Bob

OK, I've found the problem. I had to open the STUN ports 3478, 3479 for
outgoing udp traffic.

Sorry for the noise.

Bob
-- 
Bob Williams
   System:  Linux 4.4.49-16-default
   Distro:  openSUSE 42.2 (x86_64)
   Desktop: KDE Frameworks: 5.26.0, Qt: 5.6.1 and Plasma: 5.8.2


pgpVYutkB_DzY.pgp
Description: OpenPGP digital signature
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] Ekiga.net directory is blank

[Bob Williams]

Hi,

I've just installed Ekiga on openSUSE Leap 42.2 with KDE Frameworks 5.
I've done a successful echo test so it looks like I've opened the
correct ports in my router and firewall.

When I open the Address Book, the Ekiga.net directory is empty.
Clicking on the Find button with no search string does nothing, but
there is a status bar message saying -1 users found.

Could I have missed some configuration option? Do I need to run an
openldap server?

Many thanks

Bob
-- 
Bob Williams
   System:  Linux 4.4.49-16-default
   Distro:  openSUSE 42.2 (x86_64)
   Desktop: KDE Frameworks: 5.26.0, Qt: 5.6.1 and Plasma: 5.8.2


pgpER7Yeh8PQf.pgp
Description: OpenPGP digital signature
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net Could not register (Globally not acceptable)

[Mark Smith]

On 14/06/14 20:56, Mark Smith wrote:

   It has been several years since I was able to use my ekiga.net account.
   On the account status I get

   ekiga.net Could not register (Globally not acceptable)

   There is also an error message telling me that I need to manually
   configure port forwarding. However, I also have an account on iptel and
   ideasip. I have not had problems with them. Also, I have tried changing
   the port forwarding parameters with no success.

   It used to work, but something changed. A debug output is attached.

You are now behind a symmetric NAT (i.e. the error message about port 
forwarding), which is not well taken into account by ekiga. Your output 
contains: 2014/06/14 13:42:58.722 0:02.866 StunDetect...f2da08d700 OPAL 
STUN server stun.ekiga.net replies Symmetric NAT ... Something has 
recently changed in your network configuration, either you or your 
Internet provider. Do you know anything about that?


--
Eugen

Eugen,

Thanks for the note. I am running Fedora and it is possible that the firewall 
configuration has changed when I have
updated versions. But I have internet access complicated by use of an ooma VOIP 
device. I have the ooma device connected
to the cable modem and then a wireless router connected to the ooma. I am 
running ddwrt on the router. Do you have any
suggestions of how to find where the symmetric NAT is occurring?

Thanks,
Mark

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

[Ekiga-list] ekiga.net Could not register (Globally not acceptable)

[Mark Smith]

Resend: Christian sent me a message saying that when I originally sent 
this it ended up in his spam folder. Did this happen on other accounts 
also? I have not gotten any feedback on my question.


Thanks

It has been several years since I was able to use my ekiga.net account.
On the account status I get

ekiga.net Could not register (Globally not acceptable)

There is also an error message telling me that I need to manually
configure port forwarding. However, I also have an account on iptel and
ideasip. I have not had problems with them. Also, I have tried changing
the port forwarding parameters with no success.

It used to work, but something changed. A debug output is attached.

Thanks






output.txt.gz
Description: application/gzip
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net Could not register (Globally not acceptable)

[Eugen Dedu]

On 21/06/14 17:39, Mark Smith wrote:

Resend: Christian sent me a message saying that when I originally sent
this it ended up in his spam folder. Did this happen on other accounts
also? I have not gotten any feedback on my question.

Thanks

It has been several years since I was able to use my ekiga.net account.
On the account status I get

ekiga.net Could not register (Globally not acceptable)

There is also an error message telling me that I need to manually
configure port forwarding. However, I also have an account on iptel and
ideasip. I have not had problems with them. Also, I have tried changing
the port forwarding parameters with no success.

It used to work, but something changed. A debug output is attached.


I answered you, see 
https://mail.gnome.org/archives/ekiga-list/2014-June/msg3.html.


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

Re: [Ekiga-list] ekiga.net Could not register (Globally not acceptable)

[Eugen Dedu]

On 14/06/14 20:56, Mark Smith wrote:

It has been several years since I was able to use my ekiga.net account.
On the account status I get

ekiga.net Could not register (Globally not acceptable)

There is also an error message telling me that I need to manually
configure port forwarding. However, I also have an account on iptel and
ideasip. I have not had problems with them. Also, I have tried changing
the port forwarding parameters with no success.

It used to work, but something changed. A debug output is attached.


You are now behind a symmetric NAT (i.e. the error message about port 
forwarding), which is not well taken into account by ekiga.  Your output 
contains:


2014/06/14 13:42:58.722	  0:02.866	StunDetect...f2da08d700	OPAL	STUN 
server stun.ekiga.net replies Symmetric NAT ...


Something has recently changed in your network configuration, either you 
or your Internet provider.  Do you know anything about that?


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

[Ekiga-list] ekiga.net Could not register (Globally not acceptable)

[Mark Smith]

It has been several years since I was able to use my ekiga.net account. 
On the account status I get


ekiga.net Could not register (Globally not acceptable)

There is also an error message telling me that I need to manually 
configure port forwarding. However, I also have an account on iptel and 
ideasip. I have not had problems with them. Also, I have tried changing 
the port forwarding parameters with no success.


It used to work, but something changed. A debug output is attached.

Thanks



output.txt.gz
Description: application/gzip
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] ekiga.net available again

[Eugen Dedu]

... sorry for the inconvenience.

We will upgrade the server soon, hope such interruptions will disappear.

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

Re: [Ekiga-list] ekiga.net available again

[Jan Laugesen]

Ok, looking forward to the upgrades. When I was using the 3.2 version I never experienced any problems. It was really working every day and was always registering.



Gesendet:Freitag, 21. Dezember 2012 um 11:06 Uhr
Von:Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr
An:Ekiga mailing list ekiga-list@gnome.org

Betreff:[Ekiga-list] ekiga.net available again


... sorry for the inconvenience.

We will upgrade the server soon, hope such interruptions will disappear.

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




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

Re: [Ekiga-list] Ekiga.net does not appear to use password hashes

[Eugen Dedu]

On 16/07/12 21:10, ek...@phillipsjk.ca wrote:

Hello,

When I tried to sign up for Ekiga.net, my high information password:
RojrpKw@8jU=RhT'
Got mangled to:
RojrpKw@8jU=RhT\#039;
When I tried to change my password to another high-information password,
the password update e-mail contained a password with only about 20 bits
of information (rather than 96 bits).


So this is a problem with ekiga.net, right?  If yes, I personnally have 
no access to this server.



When I try to connect, I get an error message of:
Registration failed: Forbidden
I am using a Cone NAT and have STUN (using stun.ekiga.nt) enabled, even
though I don't think it will work. I am faily certain I can only recieve


Cone NAT is supported, no need to configure anything.  But as shown 
below you use an old version, I do not know how it works for it...



incomming connections on ports I explicitly forward; or in response
to an outgoing request.
I have not tried forwarding ports yet. I hope to eventually set up an
Asterix gateway, then point Ekiga to that.

Regards,

James Phillips

PS: I hope to eventually use IPv6 and encryption as well. Not sure how
suitable Ekiga would be for that.


I would say that IPv6 could be available in a few months, if everything 
goes well, but sometimes I am very bad at guessing dates.  Encryption is 
more tricky, I have really no estimation.



PPS: I may be testing an old version of Ekiga: 2.0.12


Indeed.  Personnally, I have never worked in 2.x version.

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

[Ekiga-list] Ekiga.net does not appear to use password hashes

[Ekiga]

Hello,

When I tried to sign up for Ekiga.net, my high information password:
RojrpKw@8jU=RhT'
Got mangled to:
RojrpKw@8jU=RhT\#039;
When I tried to change my password to another high-information password, 
the password update e-mail contained a password with only about 20 bits 
of information (rather than 96 bits).

When I try to connect, I get an error message of:
Registration failed: Forbidden
I am using a Cone NAT and have STUN (using stun.ekiga.nt) enabled, even 
though I don't think it will work. I am faily certain I can only recieve 
incomming connections on ports I explicitly forward; or in response 
to an outgoing request.
I have not tried forwarding ports yet. I hope to eventually set up an 
Asterix gateway, then point Ekiga to that.

Regards,

James Phillips

PS: I hope to eventually use IPv6 and encryption as well. Not sure how 
suitable Ekiga would be for that.
PPS: I may be testing an old version of Ekiga: 2.0.12

-- 
OpenPGP Public Key: http://phillipsjk.ca/OpenPGP0712.asc


signature.asc
Description: Digital signature
___
ekiga-list mailing list
ekiga-list@gnome.org
https://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] Ekiga.net Echo Test down?

[Dave Koelmeyer]

5...@ekiga.net is not working for me, anybody else as well?

--
Dave Koelmeyer
http://blog.davekoelmeyer.co.nz

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

Re: [Ekiga-list] Ekiga.net Echo Test down?

[Pietro]

In data martedì 04 ottobre 2011 12:33:22, Dave Koelmeyer ha scritto:
 5...@ekiga.net is not working for me, anybody else as well?

Yes, I'm tryng but ecotestis not run.
Ciao Pietro
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net Echo Test down?

[Eugen Dedu]

On 04/10/11 12:33, Dave Koelmeyer wrote:

5...@ekiga.net is not working for me, anybody else as well?


It's down again :o(

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

Re: [Ekiga-list] Ekiga.net Echo Test down?

[Eugen Dedu]

On 04/10/11 13:13, Eugen Dedu wrote:

On 04/10/11 12:33, Dave Koelmeyer wrote:

5...@ekiga.net is not working for me, anybody else as well?


It's down again :o(



It works now.

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

Re: [Ekiga-list] Ekiga.net Echo Test down?

[Genghis Khan]

On Tue, 04 Oct 2011 13:13:42 +0200
Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote:

 On 04/10/11 12:33, Dave Koelmeyer wrote:
  5...@ekiga.net is not working for me, anybody else as well?
 
 It's down again :o(
 
Why don't you try one of these?

sip:*850...@ekiga.net Idea SIP's echo test
sip:*031...@ekiga.net Echo test from Voxalot (Europe)
sip:*061...@ekiga.net Echo test from Voxalot (Australia)
sip:*010...@ekiga.net Echo test from Voxalot (USA)

Via: http://wiki.ekiga.org/index.php/Fun_Numbers
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] Ekiga.net uses alphanumeric usernames .....

[Walter Vermeir]

... but each has a numerical alias to enable dialing from a standard 
telephone key pad.


http://wiki.ekiga.org/index.php/FAQ#SIP_Numbers

Hi,

I am trying the find the numerical alias of a specific user I wish to 
call. Because I am using a hardware VOIP-phone I need numbers, not letters.


Can someone tell me how to do that please? (or maybe a workaround way)

Thank!

Walter
--
Wikizine.org - community newsletter - It keeps coming back!
gopher://gopher.wikizine.org - http://www.wikizine.org
You have news? - walter AT wikizine DOT org

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

Re: [Ekiga-list] ekiga.net subscribe spam

[Eugen Dedu]

On 28/06/11 14:07, Tiberiu Breana wrote:

Hello. Is there any way to stop Ekiga from spamming SUBSCRIBE requests to
5...@ekiga.net?
I'm not using the Ekiga account service and these messages are disturbing my
SIP server.


Please look at https://bugzilla.gnome.org/show_bug.cgi?id=618607 for a 
workaround.  Also, remove 500 account.


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

[Ekiga-list] ekiga.net subscribe spam

[Tiberiu Breana]

Hello. Is there any way to stop Ekiga from spamming SUBSCRIBE requests to
5...@ekiga.net?
I'm not using the Ekiga account service and these messages are disturbing my
SIP server.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Stuart Gathman]

On 05/25/2011 01:52 PM, Jānis Rukšāns wrote:
 If the phone supports either STUN or ICE, it is usually indicated by a
 public IP in the Contact address. I'm pretty sure diamondcard.us have
 a relay server, thus they don't care whether the IP is public or
 private. Ekiga.net doesn't have a relay server, therefore it's
 reasonable that it rejects registrations with private IPs.
But only if the private IP is in the Contact address.  In the cases we
are complaining about, the Contact is a public IP, but ekiga.net rejects
it anyway.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Rukš??ns wrote:

 [...]
 From the traces it looks like it doesn't support any way to traverse
 NAT. It is not really a bug, but rather important missing feature,
 something they should do.

Wait a second... then why do the registrations at sip.poivy.com
and sip.diamondcard.us work?  Doesn't this mean that my
SIP-client *is* somehow able to traverse NAT? (I'm afraid i'm
missing technical background about NAT-traversal here to be able
to answer this question myself :-(

 Technically ekiga.net is wrong about the Via (but not Contact), but
 with no NAT support in phone (either classic STUN or ICE, or
 whatever), it doesn't make any difference to you. As Damien told in
 another post, you will experience audio problems (almost certainly).
 
 But the cool thing about SIP is you're not tied to a single provider.
 You can call anyone with a SIP address no matter what your provider
 is. If the phone has no NAT support, there are multiple providers with
 media relay, select the one(s) you like, and configure to use their
 outbound proxy. At least audio should work fine.

OK.  So let me try to summarize the conclusions of this
discussion:

1) The ekiga.net server is wrong in returning a 606 Not
Acceptable because of a private IP in the Contact header of the
REGISTER message.  We have to wait for the ekiga.net admins to
fix this.  It is not at all clear how trivial this fix is.

2) If I want my Android 2.3.4 native SIP client to work with
ekiga.net, I will have to wait until it supports STUN, ICE or
another NAT traversal technology.

3) I can register with another SIP account (e.g. my poivy or
diamondcard account), but then this means I won't be reachable
at my ekiga.net SIP-address... and to be honest, because i
support the Open Source philosophy, i would really like it if
people could call me at my ekiga.net address and not some other
address from a commercial provider...

4) I can try another SIP-client on android, like CSipSimple or
Sipdroid.  It will need some more testing to see if these work
with ekiga.net...  More on this later :-)

Regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 nativeSIP-client

[herman]

  Wed May 25 2011 12:06:04 AM MST from  Bart Vandewoestyne
bart.vandewoest...@telenet.be  Subject: Re: [Ekiga-list] Ekiga.net account
with Android 2.3.4 nativeSIP-client

  On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Rukscaron;??ns wrote:
 
  
[...]
 From the traces it looks like it doesn't support any way to traverse
 NAT. It is not really a bug, but rather important missing feature,
 something they should do.


  



  
There is a good description of the Ekiga problems on the Jitsi web site:

  
http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net

  



  

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Dave Koelmeyer]

On 25/05/11 07:06 PM, Bart Vandewoestyne wrote:


4) I can try another SIP-client on android, like CSipSimple or
Sipdroid.  It will need some more testing to see if these work
with ekiga.net...  More on this later :-)


Hi Bart,

FWIW Sipdroid is what I use on a Motorola Milestone, and it works fine 
with Ekiga.net


If you observe anything of note while trying out different SIP clients, 
would be useful to know so we can update the Android compatibility list at:


http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android

Cheers,

--
Dave Koelmeyer
http://davekoelmeyer.wordpress.com/

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Wed, May 25, 2011 at 07:35:45PM +1200, Dave Koelmeyer wrote:

 Hi Bart,
 
 FWIW Sipdroid is what I use on a Motorola Milestone, and it works
 fine with Ekiga.net
 
 If you observe anything of note while trying out different SIP
 clients, would be useful to know so we can update the Android
 compatibility list at:
 
 http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android

Hmm... I just tried creating an account so that I could update
the information, but apparently creating accounts does not work
(or I am not allowed to do it...)

If somehow I can get an account to edit that info, I would be
happy to try and keep it up-to-date and add all possible info
concerning Android (2.3.4) compatibility.

Regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Eugen Dedu]

On 25/05/11 09:59, Bart Vandewoestyne wrote:

On Wed, May 25, 2011 at 07:35:45PM +1200, Dave Koelmeyer wrote:


Hi Bart,

FWIW Sipdroid is what I use on a Motorola Milestone, and it works
fine with Ekiga.net

If you observe anything of note while trying out different SIP
clients, would be useful to know so we can update the Android
compatibility list at:

http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android


Hmm... I just tried creating an account so that I could update
the information, but apparently creating accounts does not work
(or I am not allowed to do it...)

If somehow I can get an account to edit that info, I would be
happy to try and keep it up-to-date and add all possible info
concerning Android (2.3.4) compatibility.


Created.

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Wed, May 25, 2011 at 10:05:08AM +0200, Eugen Dedu wrote:

 If somehow I can get an account to edit that info, I would be
 happy to try and keep it up-to-date and add all possible info
 concerning Android (2.3.4) compatibility.
 
 Created.

Thanks Eugen!  I've updated the information at

http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android

with all that I know.  Please check and if certain things are not
well done or well written, please correct.

I'll keep on experimenting with Android and update the info when
necessary.

Kind regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

On Wed, May 25, 2011 at 10:06 AM, Bart Vandewoestyne
bart.vandewoest...@telenet.be wrote:
 On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Rukš??ns wrote:

 [...]
 From the traces it looks like it doesn't support any way to traverse
 NAT. It is not really a bug, but rather important missing feature,
 something they should do.

 Wait a second... then why do the registrations at sip.poivy.com
 and sip.diamondcard.us work?  Doesn't this mean that my
 SIP-client *is* somehow able to traverse NAT? (I'm afraid i'm
 missing technical background about NAT-traversal here to be able
 to answer this question myself :-(

No, it doesn't mean that the client is able to traverse NAT. It
means that either the *server* is able to traverse NAT by relaying the
audio, or you will have no audio in an actual call (either incoming or
both ways).

The technical background is that when you make a call, the phone sends
an INVITE message, telling the other end your IP and the port where to
send audio. However, if you're behind NAT, that IP and port is
generally not reachable from the outside world. Which means that with
no NAT support, the audio sent by the other end will not reach you.
The same applies to the called phone, if it is behind NAT as well, you
will have no audio at all.

There are several ways to counter this:
1) classic STUN - the phone can discover the corresponding public IP
and port by contacting a STUN server, and then uses it in the INVITE.
However this doesn't work for more complex types of NAT, and the whole
thing is a bit sketchy. Therefore classic STUN has been deprecated
for some time.
2) ICE - instead of contacting a dedicated STUN server, the endpoints
communicate between themselves to find out each others public IPs and
ports used for audio. This works in most cases, except when both
parties are behind a very restrictive NAT.
3) Dedicated media relay server - instead of sending audio directly to
the other party, the audio is sent through a dedicated server with a
public IP. This works even with no NAT support in the client, but is
very costly to the provider (in terms of bandwidth, hardware and
money).

If the phone supports either STUN or ICE, it is usually indicated by a
public IP in the Contact address. I'm pretty sure diamondcard.us have
a relay server, thus they don't care whether the IP is public or
private. Ekiga.net doesn't have a relay server, therefore it's
reasonable that it rejects registrations with private IPs.

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Nikolai Cassanova]

I was reading the results of your test with ekiga.net on android 2.3.4 
built in sip, which i use for my daily life only on tmobile-usa 3g 
network.  I think you can get ekiga.net to work with android but it 
would have to be through a middle man.  That middle man would have to be 
pbxes.org which is what i use as my sip provider on android 2.3.4 built 
in sip client.  It registers and connects fine, but for people to call 
you on ekiga.net you would have to go to pbxes.org and forward the 
incoming call going to your sip address at pbxes.org to ekiga.net and 
vice versa.  So if someone calls your ekiga.net sip address it would be 
forwarded to your pbxes.org sip address then you would be able to pick 
up phone call on your android 2.3.4 device's sip client which would be 
registered to your pbxes.org sip address.  In terms of calling other 
people on sip you could simply just return the call and use pbxes.org 
web browser system settings to tell people that the incoming call-id 
would show your ekiga.net sip address instead of your pbxes.org sip address.


Basically what i think could solve your problem would be to use another 
sip provider to forward and direct your calling through your ekiga.net 
sip address.  Hope this helps.


Also if you are still certain about using a third party app over the 
built in sip client which i use to do on my android phone before android 
got built in sip, both sipdroid and csipsimple are fantastic.  I think I 
will have to give csipsimple more thumbs up and praise because i feel 
that app is a little more polished than sipdroid and also they have in 
there settings an actual pre-made settings for users who use ekiga, so 
getting ekiga registered with that sip client is easier in my opinion, 
they also have actually a whole bunch of sip providers settings already 
pre-made for users.


On 05/25/2011 04:05 AM, Eugen Dedu wrote:

On 25/05/11 09:59, Bart Vandewoestyne wrote:

On Wed, May 25, 2011 at 07:35:45PM +1200, Dave Koelmeyer wrote:


Hi Bart,

FWIW Sipdroid is what I use on a Motorola Milestone, and it works
fine with Ekiga.net

If you observe anything of note while trying out different SIP
clients, would be useful to know so we can update the Android
compatibility list at:

http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android


Hmm... I just tried creating an account so that I could update
the information, but apparently creating accounts does not work
(or I am not allowed to do it...)

If somehow I can get an account to edit that info, I would be
happy to try and keep it up-to-date and add all possible info
concerning Android (2.3.4) compatibility.


Created.




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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

(Bringing this back to the mailing list)

On Tue, May 24, 2011 at 11:11 PM, Bart Vandewoestyne
bart.vandewoest...@telenet.be wrote:
 OK.  The tcpdump I did with my android phone is online at

 http://www.kuleuven-kortrijk.be/~bartv/android.pcap

 I've configured 4 SIP accounts and they all try to register.
 These are my findings:

 1) For you server, I see a 400 Bad Contact address server
 response, and as I understand it, this is because of the private
 IP in the Contact header in the REGISTER message.

 2) registration for sip.poivy.com and sip.diamondcard.us seem to
 work, even with the private IP in the Contact header.

Right.

 3) registration at ekiga.net fails, server returns a 606 Not
 Acceptable, probably because of the private IP in the Via header.

First one (unregister others) because of the Via, the second because
of the Contact. Your previous ekiga.net trace was missing the second
REGISTER message, which led me to believe that Via was the main fault.

 My main questions are:

 * Do you see a bug in the Android 2.3.4 client?  Can it send
  REGISTER messages with private IP's in the Via and Contact
  header or is this not allowed?

From the traces it looks like it doesn't support any way to traverse
NAT. It is not really a bug, but rather important missing feature,
something they should do. IPv6 is not going to take over IPv4 any time
soon, and there are other good reasons to use NAT (eg. my provider
charges me for each public IP).

 * Is ekiga.net wrong by returning the 606 Not Acceptable?

 If ekiga.net is wrong, I still feel we should try to convince the
 ekiga.net admins to make it work... it will be a big step forward
 for Ekiga on the Android/mobile market.

Technically ekiga.net is wrong about the Via (but not Contact), but
with no NAT support in phone (either classic STUN or ICE, or
whatever), it doesn't make any difference to you. As Damien told in
another post, you will experience audio problems (almost certainly).


But the cool thing about SIP is you're not tied to a single provider.
You can call anyone with a SIP address no matter what your provider
is. If the phone has no NAT support, there are multiple providers with
media relay, select the one(s) you like, and configure to use their
outbound proxy. At least audio should work fine.

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Dave Koelmeyer]

On 20/05/11 08:02 PM, Bart Vandewoestyne wrote:

Damien?  What's your opinion on changing the ekiga.net config so
that these issues get resolved?

Kind regards,
Bart


My concern is that for the end-user this is undermining the usefulness 
of Ekiga.net, and therefore adoption of Ekiga as a SIP client. I have 
tested *four* different Mac OS SIP clients from behind a NAT router, and 
all four of them cannot and will not connect to Ekiga.net:


- Jistsi (aka Sip Communicator)
- Telephone
- Blink
- X-Lite 4

For the end-user, I can easily see this as a case of interoperability 
with Ekiga users potentially not being worth the effort, so move on to 
something else. It makes evangelising Ekiga for me (and SIP as an 
alternative to Skype for example) very challenging, when the promoted 
back-end service is broken with regards to cross-client interoperability.


Some further discussion about this with a view to knowing if it can be 
resolved would be really useful at this point.


--
Dave Koelmeyer
http://davekoelmeyer.wordpress.com/

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

On Mon, May 23, 2011 at 3:35 PM, Dave Koelmeyer davekoelme...@me.com wrote:
 On 20/05/11 08:02 PM, Bart Vandewoestyne wrote:

 Damien?  What's your opinion on changing the ekiga.net config so
 that these issues get resolved?

 Kind regards,
 Bart

 My concern is that for the end-user this is undermining the usefulness of
 Ekiga.net, and therefore adoption of Ekiga as a SIP client. I have tested
 *four* different Mac OS SIP clients from behind a NAT router, and all four
 of them cannot and will not connect to Ekiga.net:

 - Jistsi (aka Sip Communicator)
 - Telephone
 - Blink
 - X-Lite 4

You can add Empathy and Nokia N900 to that list.

 For the end-user, I can easily see this as a case of interoperability with
 Ekiga users potentially not being worth the effort, so move on to something
 else. It makes evangelising Ekiga for me (and SIP as an alternative to Skype
 for example) very challenging, when the promoted back-end service is broken
 with regards to cross-client interoperability.

 Some further discussion about this with a view to knowing if it can be
 resolved would be really useful at this point.

Promoting SIP as an alternative to Skype will always be challenging, due to:
1) The large user base of Skype, and different protocols being used.
Although there is an official Skype/SIP gateway, it is paid service,
buggy and limited in functionality (you cannot simply call any Skype
user).
2) NAT issues. In theory they are applying to Skype as well, but by
installing Skype you're agreeing that your computer can be used for
relaying other users' traffic, something that's not that easy with
SIP. Setting up a dedicated server for media relay however can be
expensive, and it doesn't scale well.

Also I think that the average user's mindset plays a role here. For
the non-computer savvy Jane Doe, VoIP and Skype are synonyms, just
like PC and Windows, or, until recently, the Internet and IE. People
will use whatever comes preinstalled, and one has to convince them
that the alternative is significantly better. Of course sub-par
services don't do any good here, but in the same time you cannot
expect Damien to provide a media relay server, given that the service
is gratis.

Just my $.02
-- 
Ian
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Fri, May 20, 2011 at 02:45:58AM +0300, J??nis Rukš??ns wrote:

 [...]
 I'm not so sure about this particular case anymore (because of the
 unregister), but in general, yes, it shouldn't. First, 6xx errors are
 considered global, and second, it definitely shouldn't give an error
 on Via.
 
 Like I said, the idea is to send the first message to discover one's
 public address (the server inlcludes it in the response), and then
 send a second one which should succeed. Keeping the private IP in Via
 allows some server side tricks to traverse the NAT.
 
 If you're willing to experiment, I can give you an access to my own
 server at work (I'm using it for testing - writing SIP software is
 what I'm getting paid for). You won't be able to call anyone but at
 least we'll see if the phone sends the second REGISTER. Let me know if
 you're up to that, I'll send you the details tomorrow.

Nice to hear that people are getting payd for fun jobs like
writing SIP software ;-)

As for the testing: I also have a SIP account with diamondcard.us
and poivy.com and for these accounts I have no problem
registering with my Android 2.3.4 phone (not using STUN that is).
I've played around with tcpdump and wireshark yesterday evening
and iirc this was what was happening with both these accounts:

1) Android phone sends a REGISTER message
2) registrar sends back an error message (something with not
   authorized or credentials missing or so... if i recall
   correctly, it was a 401 Unauthorized message...)
3) Android phone sends second REGISTER message, now including
   some login info (and probably some kind of authentication
   stuff)
4) registrar sends back 200 OK.

This was also from behind my Asus RT-N16 router running dd-wrt.

I'm at work now and can't experiment, but I'll make a tcpdump of
this flow this evening and put the .pcap file online somewhere.
Please be patient for let's say 10 hours ;-)

Knowing that these registrations work, confirms my suspision that
the problem is really on the ekiga.net server side and not with
my phone.  From the above, i deduce that one should also be able
to make it work *without* a STUN server.  Having the STUN support
possibility in the Android client would of course also be nice,
as that would maybe be a trick to circumvent the ekiga.net server
config problem.

Damien?  What's your opinion on changing the ekiga.net config so
that these issues get resolved?

Kind regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Thu, May 19, 2011 at 12:31:49AM +0300, J??nis Rukš??ns wrote:

 Judging from 
 http://www.onsip.com/blog/leo/2011/01/05/our-evaluation-of-android-gingerbreads-native-sip-calling-with-the-nexus-s
 it seems that the Android SIP client is working fine from behind NAT -
 the SIP traces show a private IP in Via header, and a public one in
 Contact.
 
 Most likely your registration fails because ekiga.net is apparently
 configured to require a public IP in both Via and Contact headers. I
 cannot be 100% sure without seeing the actual SIP messages, but I
 guess a private IP in Via is why your registration fails.
 
 And sending 606 Not Acceptable Anywhere to REGISTER is a violation of
 the SIP standard on it's own.

OK, so if I get things right, there are two possible reasons for
me not being able to register with ekiga.net with the native
Android 2.3.4 SIP client, namely:

1) it is because the native Android 2.3.4 SIP client does not
support a STUN server yet.

2) it is a problem with the ekiga.net server configuration.

I would be glad to help out here, but I'm not really sure how I
can help.  My educated guess is that I should somehow be able to
grab the SIP messages from and to my Android phone, but I have no
idea how I can do this.  I have some basic familiarity with
wireshark on Linux, but I have never done packet sniffing on an
Android phone.

If somebody knows, please let me know how I can get to the real
SIP-traffic, so we can diagnose this problem more in depth.

Kind regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Thu, May 19, 2011 at 09:50:08AM +0200, Bart Vandewoestyne wrote:

 OK, so if I get things right, there are two possible reasons for
 me not being able to register with ekiga.net with the native
 Android 2.3.4 SIP client, namely:
 
 1) it is because the native Android 2.3.4 SIP client does not
 support a STUN server yet.
 
 2) it is a problem with the ekiga.net server configuration.
 
 I would be glad to help out here, but I'm not really sure how I
 can help.  My educated guess is that I should somehow be able to
 grab the SIP messages from and to my Android phone, but I have no
 idea how I can do this.  I have some basic familiarity with
 wireshark on Linux, but I have never done packet sniffing on an
 Android phone.
 
 If somebody knows, please let me know how I can get to the real
 SIP-traffic, so we can diagnose this problem more in depth.

OK.  I've played a bit around with tcpdump on my dd-wrt Asus
RT-N16 router and this is what I did:

* turned off my Android phone
* issued the following command:
root@asus:~# tcpdump -i eth1 host 192.168.1.138 -w sip_capture.pcap
* turned on my Android phone and played a bit around
* turned off my android phone
* CTRL+C the tcpdump command

The output (to be visualised with e.g. wireshark) is here:

http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap

All I can see is that the following is happening:

1) an UDP packet is being sent to ekiga.net
2) ekiga.net replies with a SIP message 606 Not Acceptable

I cannot judge why sending of 1) results in a 606 Acceptable... I
hope more experienced people can tell me what's going wrong here:
is the problem on my side (not having STUN support) or is the
problem on the ekiga.net server side?

Kind regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Eugen Dedu]

On 19/05/11 22:48, Bart Vandewoestyne wrote:

On Thu, May 19, 2011 at 09:50:08AM +0200, Bart Vandewoestyne wrote:


OK, so if I get things right, there are two possible reasons for
me not being able to register with ekiga.net with the native
Android 2.3.4 SIP client, namely:

1) it is because the native Android 2.3.4 SIP client does not
support a STUN server yet.

2) it is a problem with the ekiga.net server configuration.

I would be glad to help out here, but I'm not really sure how I
can help.  My educated guess is that I should somehow be able to
grab the SIP messages from and to my Android phone, but I have no
idea how I can do this.  I have some basic familiarity with
wireshark on Linux, but I have never done packet sniffing on an
Android phone.

If somebody knows, please let me know how I can get to the real
SIP-traffic, so we can diagnose this problem more in depth.


OK.  I've played a bit around with tcpdump on my dd-wrt Asus
RT-N16 router and this is what I did:

* turned off my Android phone
* issued the following command:
 root@asus:~# tcpdump -i eth1 host 192.168.1.138 -w sip_capture.pcap
* turned on my Android phone and played a bit around
* turned off my android phone
* CTRL+C the tcpdump command

The output (to be visualised with e.g. wireshark) is here:

http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap

All I can see is that the following is happening:

1) an UDP packet is being sent to ekiga.net
2) ekiga.net replies with a SIP message 606 Not Acceptable


There is a problem with your output.  Captured packet is truncated to 62 
bytes, so the full SIP packet is not shown.


Could you retry tcpdump to have full packets in the file?

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Thu, May 19, 2011 at 10:57:11PM +0200, Eugen Dedu wrote:

 There is a problem with your output.  Captured packet is truncated
 to 62 bytes, so the full SIP packet is not shown.
 
 Could you retry tcpdump to have full packets in the file?

I've updated the file, i think we now have the full information.
The new version is at the same url, namely

http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap

Please let me know if this is enough info to debug my problem.
If not, then let me know what to do.  I'm glad to be able to help
here!

Regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote:

 I've updated the file, i think we now have the full information.
 The new version is at the same url, namely
 
 http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap
 
 Please let me know if this is enough info to debug my problem.
 If not, then let me know what to do.  I'm glad to be able to help
 here!

OK.  I've done some more searching, and this is what I have so
far.  If I try with Ekiga on my laptop, then this is how a typical
REGISTER message looks like:


REGISTER sip:ekiga.net SIP/2.0
CSeq: 2 REGISTER
Via: SIP/2.0/UDP 
178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport
User-Agent: Ekiga/3.2.7
From: 
sip:bart.vandewoest...@ekiga.net;tag=282f826b-cb80-e011-82e5-00216b30c960
Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960@maverick
To: sip:bart.vandewoest...@ekiga.net
Contact: sip:Bart.Vandewoestyne@178.117.245.74;q=1, 
sip:Bart.Vandewoestyne@192.168.1.105;q=0.500
Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
Expires: 3600
Content-Length: 0
Max-Forwards: 70


If I use my Android phone, then i have


REGISTER sip:ekiga.net SIP/2.0
Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138
CSeq: 8429 REGISTER
From: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net;tag=4156217873
To: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net
Via: SIP/2.0/UDP 
192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport
Max-Forwards: 70
User-Agent: SIPAUA/0.1.001
Contact: *
Expires: 0
Content-Length: 0


The most important differences that I notice are:

* Ekiga uses the public WAN address of my router in the Via header, whereas my
  android phone has the local LAN address and port.

* Ekiga uses both the public WAN address and the local LAN address in the
  Contact header, whereas my Android phone simply sets the '*'-symbol.

My question to this list is still the same:

Is this a bug or a missing feature (STUN) in the native Android client, or is 
the problem on the ekiga.net server side?

Regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

On Fri, May 20, 2011 at 12:30 AM, Bart Vandewoestyne
bart.vandewoest...@telenet.be wrote:
 On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote:

 I've updated the file, i think we now have the full information.
 The new version is at the same url, namely

 http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap

 Please let me know if this is enough info to debug my problem.
 If not, then let me know what to do.  I'm glad to be able to help
 here!

 OK.  I've done some more searching, and this is what I have so
 far.  If I try with Ekiga on my laptop, then this is how a typical
 REGISTER message looks like:


 REGISTER sip:ekiga.net SIP/2.0
 CSeq: 2 REGISTER
 Via: SIP/2.0/UDP 
 178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport
 User-Agent: Ekiga/3.2.7
 From: 
 sip:bart.vandewoest...@ekiga.net;tag=282f826b-cb80-e011-82e5-00216b30c960
 Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960@maverick
 To: sip:bart.vandewoest...@ekiga.net
 Contact: sip:Bart.Vandewoestyne@178.117.245.74;q=1, 
 sip:Bart.Vandewoestyne@192.168.1.105;q=0.500
 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING
 Expires: 3600
 Content-Length: 0
 Max-Forwards: 70


 If I use my Android phone, then i have


 REGISTER sip:ekiga.net SIP/2.0
 Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138
 CSeq: 8429 REGISTER
 From: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net;tag=4156217873
 To: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net
 Via: SIP/2.0/UDP 
 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport
 Max-Forwards: 70
 User-Agent: SIPAUA/0.1.001
 Contact: *
 Expires: 0
 Content-Length: 0


 The most important differences that I notice are:

 * Ekiga uses the public WAN address of my router in the Via header, whereas my
  android phone has the local LAN address and port.

 * Ekiga uses both the public WAN address and the local LAN address in the
  Contact header, whereas my Android phone simply sets the '*'-symbol.

 My question to this list is still the same:

 Is this a bug or a missing feature (STUN) in the native Android client, or is 
 the problem on the ekiga.net server side?

This is something I didn't expect at all - the message your phone
sends actually asks ekiga.net to unregister everyone from
sip:bart.vandewoest...@ekiga.net. I can only guess why. It could be
that the phone is trying to ensure it is only device registered.
Whatever the reason, I expected at least two REGISTER messages - the
first with the private IP in both Via and Contact (to discover it's
public IP), followed by a second one with the public IP in Contact.

The unregister could be a bug, but it is also possible that the phone
is using it as a way to get the public IP, but doesn't send the second
REGISTER because of the 606 error code.

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Fri, May 20, 2011 at 01:32:03AM +0300, J??nis Rukš??ns wrote:

  If I use my Android phone, then i have
 
  REGISTER sip:ekiga.net SIP/2.0
  Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138
  CSeq: 8429 REGISTER
  From: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net;tag=4156217873
  To: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net
  Via: SIP/2.0/UDP 
  192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport
  Max-Forwards: 70
  User-Agent: SIPAUA/0.1.001
  Contact: *
  Expires: 0
  Content-Length: 0
  [...]

 This is something I didn't expect at all - the message your phone
 sends actually asks ekiga.net to unregister everyone from
 sip:bart.vandewoest...@ekiga.net. I can only guess why.

I'm not a SIP-protocol expert.  Can you explain me how you see
this for the above message?  Is it because of the asterisk in the
Contact header?  I have searched, but couldn't find the meaning
of the * in the Contact header.

 It could be that the phone is trying to ensure it is only
 device registered.  Whatever the reason, I expected at least
 two REGISTER messages - the first with the private IP in both
 Via and Contact (to discover it's public IP), followed by a
 second one with the public IP in Contact.

OK.  I'll play a bit more around, getting myself more comfortable
with tcpdump and wireshark for my SIP-protocol debugging...
 
 The unregister could be a bug, but it is also possible that the
 phone is using it as a way to get the public IP, but doesn't
 send the second REGISTER because of the 606 error code.

OK.  And for as far as I understand it from

  http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net
  http://mail.gnome.org/archives/ekiga-list/2010-October/msg00040.html
  http://mail.gnome.org/archives/ekiga-list/2010-October/msg00041.html

ekiga.net should not sent this 606 error, right?

So the conclusion is that the problem is actually on the
ekiga.net server side and I have to hope that it gets fixed?

Regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Wed, May 18, 2011 at 10:34:22PM +, Dave Koelmeyer wrote:
 
 Most likely it is neither you nor the Android SIP client. The
 ekiga.net server has an overly restrictive configuration, which
 prevents any sufficiently up-to-date SIP client from registering from
 behind NAT. There have been numerous posts on the list regarding this.
 
 I imagine this isn't a trivial issue to fix, but all the same do we know who 
 looks after Ekiga.net and w???ould this be something that could be addressed?
 
 Cheers,
 Dave

Dave,

According to the info on
http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#FAQ
it is Damien Sandras who looks after ekiga.net

I've searched the mailing list archives for mails from Damien
about this issue, but haven't found any the last few months.

It would be nice to know what he thinks of the issue in this
thread and how it can be fixed...  I hope he has the time and is
willing to fix it...

In my opinion, it would really be a Big step forward for the Open
Source VoIP community if the native Android 2.3.4 SIP client
could register and work with ekiga.net accounts...

Regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

On Fri, May 20, 2011 at 2:02 AM, Bart Vandewoestyne
bart.vandewoest...@telenet.be wrote:
 On Wed, May 18, 2011 at 10:34:22PM +, Dave Koelmeyer wrote:

 Most likely it is neither you nor the Android SIP client. The
 ekiga.net server has an overly restrictive configuration, which
 prevents any sufficiently up-to-date SIP client from registering from
 behind NAT. There have been numerous posts on the list regarding this.

 I imagine this isn't a trivial issue to fix, but all the same do we know who 
 looks after Ekiga.net and w???ould this be something that could be addressed?

 Cheers,
 Dave

 Dave,

 According to the info on
 http://wiki.ekiga.org/index.php/Ekiga.net_VoIP_service_subscription#FAQ
 it is Damien Sandras who looks after ekiga.net

 I've searched the mailing list archives for mails from Damien
 about this issue, but haven't found any the last few months.

 It would be nice to know what he thinks of the issue in this
 thread and how it can be fixed...  I hope he has the time and is
 willing to fix it...

See http://mail.gnome.org/archives/ekiga-list/2011-May/msg00105.html

 In my opinion, it would really be a Big step forward for the Open
 Source VoIP community if the native Android 2.3.4 SIP client
 could register and work with ekiga.net accounts...

Well, I'm not so sure about Android anymore, but removing the private
Via restriction would allow sofia-sip based clients (Empathy, Maemo,
probably some Nokia phones) to work with ekiga.net
-- 
Ian
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

On Fri, May 20, 2011 at 1:56 AM, Bart Vandewoestyne
bart.vandewoest...@telenet.be wrote:
 On Fri, May 20, 2011 at 01:32:03AM +0300, J??nis Rukš??ns wrote:

  If I use my Android phone, then i have
 
  REGISTER sip:ekiga.net SIP/2.0
  Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138
  CSeq: 8429 REGISTER
  From: Bart.Vandewoestyne 
  sip:bart.vandewoest...@ekiga.net;tag=4156217873
  To: Bart.Vandewoestyne sip:bart.vandewoest...@ekiga.net
  Via: SIP/2.0/UDP 
  192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport
  Max-Forwards: 70
  User-Agent: SIPAUA/0.1.001
  Contact: *
  Expires: 0
  Content-Length: 0
  [...]

 This is something I didn't expect at all - the message your phone
 sends actually asks ekiga.net to unregister everyone from
 sip:bart.vandewoest...@ekiga.net. I can only guess why.

 I'm not a SIP-protocol expert.  Can you explain me how you see
 this for the above message?  Is it because of the asterisk in the
 Contact header?  I have searched, but couldn't find the meaning
 of the * in the Contact header.

The * in Contact header is allowed only when unregistering (Expires:
0) and means every IP that is currently registered at the particular
address in To header. For example, if you have logged in from let's
say laptop and work, the above will force both of those clients to log
out (given that the server allows it).

 It could be that the phone is trying to ensure it is only
 device registered.  Whatever the reason, I expected at least
 two REGISTER messages - the first with the private IP in both
 Via and Contact (to discover it's public IP), followed by a
 second one with the public IP in Contact.

 OK.  I'll play a bit more around, getting myself more comfortable
 with tcpdump and wireshark for my SIP-protocol debugging...

 The unregister could be a bug, but it is also possible that the
 phone is using it as a way to get the public IP, but doesn't
 send the second REGISTER because of the 606 error code.

 OK.  And for as far as I understand it from

  http://www.jitsi.org/index.php/Documentation/FAQ#ekiga.net
  http://mail.gnome.org/archives/ekiga-list/2010-October/msg00040.html
  http://mail.gnome.org/archives/ekiga-list/2010-October/msg00041.html

 ekiga.net should not sent this 606 error, right?

 So the conclusion is that the problem is actually on the
 ekiga.net server side and I have to hope that it gets fixed?

I'm not so sure about this particular case anymore (because of the
unregister), but in general, yes, it shouldn't. First, 6xx errors are
considered global, and second, it definitely shouldn't give an error
on Via.

Like I said, the idea is to send the first message to discover one's
public address (the server inlcludes it in the response), and then
send a second one which should succeed. Keeping the private IP in Via
allows some server side tricks to traverse the NAT.

If you're willing to experiment, I can give you an access to my own
server at work (I'm using it for testing - writing SIP software is
what I'm getting paid for). You won't be able to call anyone but at
least we'll see if the phone sends the second REGISTER. Let me know if
you're up to that, I'll send you the details tomorrow.

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[David Ford]

On 18/05/11 13:46, Bart Vandewoestyne wrote:

On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Rukš??ns wrote:

Most likely it is neither you nor the Android SIP client. The
ekiga.net server has an overly restrictive configuration, which
prevents any sufficiently up-to-date SIP client from registering from
behind NAT. There have been numerous posts on the list regarding this.

Hmm... having googled around a bit, my guess would rather be that
i cannot register because the native Android 2.3.4 SIP client
seems not to support STUN.  Couldn't this be the major problem
for me not being able to register instead of an 'overly
restrictive configuration' of the ekiga.net server?

If others agree that this lack of STUN support is most likely the
reason why my registration fails, then it seems like a good idea
to vote for

http://code.google.com/p/android/issues/detail?id=15685

or maybe even add some comments there.  This might speedup the
STUN support in the native Android 2.3.4 SIP client, thereby
making Ekiga much more accessible to the mobile world...

Kind regards,
Bart

STUN is now depreciated - it has been recognised that it really doesn't 
work very well.


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

[Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

Hello all,

I'm trying to use the native Android 2.3.4 SIP client (on my
Samsung Google Nexus S) with my Ekiga.net account.  Apparently,
nothing about it is listed on
http://wiki.ekiga.org/index.php/Ekiga_Interoperability#Android so
I hope I can help here in testing.

I tried adding my Ekiga.net account using (in Android)

  - Menu
- Settings
  - Call settings
- Internet call settings
  - Accounts
- Add account

There, I add the following info:

  Username: MyFirstName.MyLastName
  Password: my_ekiga_password
  Server: ekiga.net
  Set as primary account: selected

Under the Optional settings I did not touch anything, so I have

  Authentication username: left empty
  Display name: left empty
  Outbound proxy address: left empty
  Port number: 5060
  Transport type: UDP
  Send keep-alive: Automatic

With these settings, I cannot seem to register myself, I get the
error

Primary account. Account registration failed: (Not Acceptable
(606)); will try later


Am I doing something wrong here or can the native Android 2.3.4
SIP client not work with Ekiga accounts yet?  If not, then maybe
somebody can tell me what features are missing in order to get
Ekiga up and running, so we can submit a feature request at
http://source.android.com/source/report-bugs.html ?  Wouldn't
that be a nice step forward?

Kind regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

Hi,

On Wed, May 18, 2011 at 2:53 PM, Bart Vandewoestyne
 With these settings, I cannot seem to register myself, I get the
 error

 Primary account. Account registration failed: (Not Acceptable
 (606)); will try later


 Am I doing something wrong here or can the native Android 2.3.4
 SIP client not work with Ekiga accounts yet?  If not, then maybe
 somebody can tell me what features are missing in order to get
 Ekiga up and running, so we can submit a feature request at
 http://source.android.com/source/report-bugs.html ?  Wouldn't
 that be a nice step forward?

Most likely it is neither you nor the Android SIP client. The
ekiga.net server has an overly restrictive configuration, which
prevents any sufficiently up-to-date SIP client from registering from
behind NAT. There have been numerous posts on the list regarding this.

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

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Bart Vandewoestyne]

On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Rukš??ns wrote:

 Most likely it is neither you nor the Android SIP client. The
 ekiga.net server has an overly restrictive configuration, which
 prevents any sufficiently up-to-date SIP client from registering from
 behind NAT. There have been numerous posts on the list regarding this.

Hmm... having googled around a bit, my guess would rather be that
i cannot register because the native Android 2.3.4 SIP client
seems not to support STUN.  Couldn't this be the major problem
for me not being able to register instead of an 'overly
restrictive configuration' of the ekiga.net server?

If others agree that this lack of STUN support is most likely the
reason why my registration fails, then it seems like a good idea
to vote for

http://code.google.com/p/android/issues/detail?id=15685

or maybe even add some comments there.  This might speedup the
STUN support in the native Android 2.3.4 SIP client, thereby
making Ekiga much more accessible to the mobile world...

Kind regards,
Bart

-- 
Share what you know.  Learn what you don't.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client

[Jānis Rukšāns]

On Wed, May 18, 2011 at 3:46 PM, Bart Vandewoestyne
bart.vandewoest...@telenet.be wrote:
 On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Rukš??ns wrote:

 Most likely it is neither you nor the Android SIP client. The
 ekiga.net server has an overly restrictive configuration, which
 prevents any sufficiently up-to-date SIP client from registering from
 behind NAT. There have been numerous posts on the list regarding this.

 Hmm... having googled around a bit, my guess would rather be that
 i cannot register because the native Android 2.3.4 SIP client
 seems not to support STUN.  Couldn't this be the major problem
 for me not being able to register instead of an 'overly
 restrictive configuration' of the ekiga.net server?

 If others agree that this lack of STUN support is most likely the
 reason why my registration fails, then it seems like a good idea
 to vote for

Judging from 
http://www.onsip.com/blog/leo/2011/01/05/our-evaluation-of-android-gingerbreads-native-sip-calling-with-the-nexus-s
it seems that the Android SIP client is working fine from behind NAT -
the SIP traces show a private IP in Via header, and a public one in
Contact.

Most likely your registration fails because ekiga.net is apparently
configured to require a public IP in both Via and Contact headers. I
cannot be 100% sure without seeing the actual SIP messages, but I
guess a private IP in Via is why your registration fails.

And sending 606 Not Acceptable Anywhere to REGISTER is a violation of
the SIP standard on it's own.

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

[Ekiga-list] ekiga.net, registration failed: 401 Unauthorized

[Andre Robatino]

Using Twinkle, over the last few weeks I've frequently gotten the error

ekiga.net, registration failed: 401 Unauthorized

from the server. When this happens, the client no longer attempts to
register, so I have to re-register manually. This almost never happened
before. Nothing has changed at my end so the problem must be at the server.



signature.asc
Description: OpenPGP digital signature
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net down again

[Eugen Dedu]

On 08/12/10 02:57, Dave Koelmeyer wrote:

On 08 Dec, 2010,at 11:32 AM, Allen T Parkertpar...@cpsco.net  wrote:


 The ekiga.net server is down again. It's been down all of today and at least
 part of yesterday.
 http://mail.gnome.org/mailman/listinfo/ekiga-list


I am presently getting consistent could not register errors on two machines
here (yesterday was okay).


Well, here it works right now too.  As always, the debug output is 
needed to track down the problem...


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

[Ekiga-list] ekiga.net down again

[Allen T Parker]

The ekiga.net server is down again.  It's been down all of today and at
least part of yesterday.


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

Re: [Ekiga-list] ekiga.net down again

[Eugen Dedu]

On 07/12/10 23:32, Allen T Parker wrote:

The ekiga.net server is down again.  It's been down all of today and at
least part of yesterday.


5...@ekiga.net is working right now...

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

Re: [Ekiga-list] ekiga.net down again

[Dave Koelmeyer]

On 08 Dec, 2010,at 11:32 AM, Allen T Parker tpar...@cpsco.net wrote:



  
  

The ekiga.net server is down again. It's been down all of today and at least part of yesterday.I am presently getting consistent "could not register" errors on two machines here (yesterday was okay). Cheers,Dave
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net server not properly configured?

[Jānis Rukšāns]

On Sun, Nov 28, 2010 at 12:10 AM,  pal...@inwind.it wrote:
 On Sat, 27 Nov 2010 11:31:58 -0600
 Anthony Base base.anth...@gmail.com wrote:

 Hi guys! Empathy users like me would love to use your Ekiga server, but
 there's something whacked out about your server configuration that is
 preventing other clients from connecting to yours.

 Could you be more specific about the problems encountered by Empathy when 
 trying to connect to ekiga.net?

I think the links Anthony provided are very specific about the
problems. To reiterate - ekiga.net responds to REGISTER w/ 606 Not
Acceptable Anywhere when behind NAT, supposedly because of a private
IP in the top Via. This breaks clients that use SIP Outbound for
traversing NAT.

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

[Ekiga-list] Ekiga.net server not properly configured?

[Anthony Base]

Hi guys! Empathy users like me would love to use your Ekiga server, but 
there's something whacked out about your server configuration that is 
preventing other clients from connecting to yours.


https://bugzilla.gnome.org/show_bug.cgi?id=624751
http://sourceforge.net/tracker/index.php?func=detailaid=2412241group_id=143636atid=756076

These are some really big showstoppers for VoIP lovers who also want to 
chat. Is there any chance that these server configurations can be fixed 
in the near future? Thanks in advance!

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

Re: [Ekiga-list] Ekiga.net server not properly configured?

[palama]

On Sat, 27 Nov 2010 11:31:58 -0600
Anthony Base base.anth...@gmail.com wrote:

 Hi guys! Empathy users like me would love to use your Ekiga server, but 
 there's something whacked out about your server configuration that is 
 preventing other clients from connecting to yours.
 

Besides ekiga, there are at least 4 other clients which are able to connect to 
an ekiga.net account:
twinkle, linphone, asterisk and telephone
so maybe the problem is not in the configuration of the ekiga.net server but 
somewhere else.
Could you be more specific about the problems encountered by Empathy when 
trying to connect to ekiga.net?

Best regards,

Antonio Palamà

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

Re: [Ekiga-list] Ekiga.net refuses registering Twinkle

[palama]

On Sat, 25 Sep 2010 15:03:14 +0200
Eugen Dedu eugen.d...@pu-pm.univ-fcomte.fr wrote:

 Hello Antonio, glad to hear from you.
 
 I think this is a bug (I do not think there is a preference on Ekiga 
 over other clients), but as I am not admnistrator I cannot be sure.
 
Hello Eugen,

it usually happens in late evening after Twinkle has been registered for many 
hours.
I would like to help debbugging but, unfortunately it seems twinkle has no 
debug option so I will have to cut and paste from the log window or use the 
command line version with tee.
Do you know whom should I mail this logs to find out what happens?
Best regards,

Antonio

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

Re: [Ekiga-list] Ekiga.net refuses registering Twinkle

[Eugen Dedu]

On 28/09/10 09:41, pal...@inwind.it wrote:

On Sat, 25 Sep 2010 15:03:14 +0200
Eugen Dedueugen.d...@pu-pm.univ-fcomte.fr  wrote:


Hello Antonio, glad to hear from you.

I think this is a bug (I do not think there is a preference on Ekiga
over other clients), but as I am not admnistrator I cannot be sure.


Hello Eugen,

it usually happens in late evening after Twinkle has been registered for many 
hours.
I would like to help debbugging but, unfortunately it seems twinkle has no 
debug option so I will have to cut and paste from the log window or use the 
command line version with tee.
Do you know whom should I mail this logs to find out what happens?


Well, it should be Twinkle developers who need to be contacter.

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

[Ekiga-list] Ekiga.net refuses registering Twinkle

[palama]

At random occasions but at least once a day it happens that ekiga.net refuses 
my registration if I use twinkle 1.4.2 while it accepts registration if I use 
ekiga 2.0.12, same username and same password of course.
Does anybody know if this the normal behaviuor of ekiga.net, maybe due to 
giving priority to people using ekiga, or if it is a bug?
Best regards,

Antonio Palamà

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

Re: [Ekiga-list] Ekiga.net refuses registering Twinkle

[Eugen Dedu]

On 25/09/10 14:40, pal...@inwind.it wrote:

At random occasions but at least once a day it happens that ekiga.net refuses 
my registration if I use twinkle 1.4.2 while it accepts registration if I use 
ekiga 2.0.12, same username and same password of course.
Does anybody know if this the normal behaviuor of ekiga.net, maybe due to 
giving priority to people using ekiga, or if it is a bug?
Best regards,


Hello Antonio, glad to hear from you.

I think this is a bug (I do not think there is a preference on Ekiga 
over other clients), but as I am not admnistrator I cannot be sure.


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

[Ekiga-list] Ekiga.net fails to interoperate with non-ekiga SIP clients behind NAT

[Nikolai Gauntlet Cassanova]

Hi, was trying to get my ekiga.net account to work with imsdroid
softphone for android and put in my information but kept getting failed
so, searched on google on how to get ekiga to work with imsdroid and
came across the bug 624751 at bugzila which basically says ekiga.net
fails to interoperate with non-ekiga sip clients behind NAT.  I wanted
to know if the bug was fixed already?
-- 
Nikolai Gauntlet Cassanova ncassanov...@gmail.com

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

Re: [Ekiga-list] Ekiga.net 3cxphone (Android)

[Nikolai Gauntlet Cassanova]

Hi, I have an Android phone and I have never tried 3cxphone as a
softphone app but I know that the linphone app works flawlessly to
register my ekiga account.  The only thing is that I just started
playing with the linphone app, so I can't give you an opinion on how
well it functions when it comes to calls.  Since reading your message, I
will have to give 3cxphone a try as I am looking for a good softphone
client/app that will work with my ekiga account and allow me to make 100
percent voip calls with out using cellular minutes.

If I find out anything on getting 3cxphone registration to work with my
ekiga account settings will let you know.

On Thu, 2010-08-12 at 16:12 +0200, Kojiro Ame Kamex wrote:
 I'm trying to get Ekiga.net working with 3cxphone on Android.
 Sometimes the connection works but most of the time I can't authenticate.
 
 Is there anything I can try to fix this?
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list

-- 
Nikolai Gauntlet Cassanova ncassanov...@gmail.com

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

[Ekiga-list] Ekiga.net 3cxphone (Android)

[Kojiro Ame Kamex]

I'm trying to get Ekiga.net working with 3cxphone on Android.
Sometimes the connection works but most of the time I can't authenticate.

Is there anything I can try to fix this?
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] Ekiga.net certificate

[palama]

www.ekiga.net certificate expired on 12/16/2009
What should people do when connecting to the site?

Best regards,

Antonio


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

Re: [Ekiga-list] Ekiga.net certificate

[Yannick]

Le samedi 19 décembre 2009 à 16:59 +0100, pal...@inwind.it a écrit :
 www.ekiga.net certificate expired on 12/16/2009
 What should people do when connecting to the site?
 

For now, just pass the warning. I'm trying to get my hand on a free
certificate...

Thank you for bringing it to our attention.

Best regards,
Yannick

 Best regards,
 
 Antonio
 
 


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

Re: [Ekiga-devel-list] [Ekiga-list] Ekiga.net service interruption

[Damien Sandras]

Le dimanche 01 novembre 2009 à 15:53 +0100, Damien Sandras a écrit :

 Le dimanche 01 novembre 2009 à 15:06 +0100, Damien Sandras a écrit :
 
  Hello to all,
  
  Due to an upgrade, Ekiga.net will be unavailable in the following
  minutes for an undetermined period of time.
  
  I apologize for the inconvenience, (but well, it's a free service).
 
 
 The brand new kamailio 1.5.3 is up and running.
 
 I will update the configuration soon.


It's up and running. You should even receive notifications when your
peers are doing calls.


-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   
___
Ekiga-devel-list mailing list
Ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list

[Ekiga-list] Ekiga.net service interruption

[Damien Sandras]

Hello to all,

Due to an upgrade, Ekiga.net will be unavailable in the following
minutes for an undetermined period of time.

I apologize for the inconvenience, (but well, it's a free service).


-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] ekiga.net STUN server down

[Andre Robatino]

The STUN server stun.ekiga.net (alias for stun01.sipphone.com which is
Gizmo5's STUN server) has been down for a while.  Should Ekiga have its
own STUN server?



signature.asc
Description: OpenPGP digital signature
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net

[Damien Sandras]

Le mardi 13 octobre 2009 à 12:43 -0700, peasth...@shaw.ca a écrit :
 Speaking of ekiga.net, can a donation be submitted 
 _via_ Paypal?  I have money in an account and 
 prefer to use that rather than a credit card.
 

Yes Paypal works (see the button).

 Also, I wonder whether https://www.ekiga.net might 
 have a graphical indicator of donation progress 
 vs. target.  A thermometer is often used in 
 fundraising, for example.

We could use that, but we have no target (and very few donations,
perhaps 50 € every 3 months).



-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

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

Re: [Ekiga-list] ekiga.net

[Damien Sandras]

Le mardi 13 octobre 2009 à 00:31 +0200, W.P. a écrit :
 Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be.
 
 (because of lacking of possibility to edit account?, etc - some time in
 the past it WAS possible).

What relationship do you see between the possibility to edit an account
and the fact that it would be dead ?

-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

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

Re: [Ekiga-list] ekiga.net

[JimmyVolatile]

Ok. So this is why I've never been able to register on Ubuntu...

/JimmyVolatile

On Tue, Oct 13, 2009 at 6:11 AM, yannick sev...@free.fr wrote:

 W.P. a écrit :
  Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be.
 
  (because of lacking of possibility to edit account?, etc - some time in
  the past it WAS possible).
 

 I will start working on this in a few days (in 1 week or 2 most probably)

 Best regards,
 Yannick

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

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

Re: [Ekiga-list] ekiga.net

[yannick]

JimmyVolatile a écrit :
 Ok. So this is why I've never been able to register on Ubuntu...
 

It is not related. I'm using Ubuntu, and I can register. You issue is
something else.

 /JimmyVolatile
 
 On Tue, Oct 13, 2009 at 6:11 AM, yannick sev...@free.fr wrote:
 
 W.P. a écrit :
 Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be.

 (because of lacking of possibility to edit account?, etc - some time in
 the past it WAS possible).

 I will start working on this in a few days (in 1 week or 2 most probably)

 Best regards,
 Yannick

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

 

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

[Ekiga-list] ekiga.net

[peasthope]

Speaking of ekiga.net, can a donation be submitted 
_via_ Paypal?  I have money in an account and 
prefer to use that rather than a credit card.

Also, I wonder whether https://www.ekiga.net might 
have a graphical indicator of donation progress 
vs. target.  A thermometer is often used in 
fundraising, for example.

Thanks, ... Peter E.



-- 
Google pathology workshop

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

[Ekiga-list] ekiga.net

[W.P.]

Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be.

(because of lacking of possibility to edit account?, etc - some time in
the past it WAS possible).

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

Re: [Ekiga-list] ekiga.net

[yannick]

W.P. a écrit :
 Is ekiga.net DEAD? With 3 PROMILLE active users it seems to be.
 
 (because of lacking of possibility to edit account?, etc - some time in
 the past it WAS possible).
 

I will start working on this in a few days (in 1 week or 2 most probably)

Best regards,
Yannick

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

Re: [Ekiga-list] ekiga.net server down again

[Damien Sandras]

Le jeudi 09 juillet 2009 à 09:41 -0400, Andre Robatino a écrit :
 The server is down again.  It's been down for at least a few hours.

It should be back, thanks for warning us!
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

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

Re: [Ekiga-list] ekiga.net server down again

[Jan Willamowius]

I'm not sure what kind of process is dying on ekiga.net, but sometimes
it can be very helpful to use an automatic restarter until the real
problem is fixed:

#!/bin/sh

START_PROC=/usr/local/bin/dying_process -a -b -c
NOTIFY_EMAIL=f...@bar.com

while :; do
$START_PROC
EXITSTATUS=$?
if [ $EXITSTATUS -gt 128 ]; then
echo Process has crashed | /usr/bin/mail -s 
Crash$NOTIFY_EMAIL 
elif [ $EXITSTATUS == 0 ]; then
echo Normally Stoped
exit
fi
echo Restarting Process
sleep 4
done




Andre Robatino wrote:
 The server is down again.  It's been down for at least a few hours.

-- 
Jan Willamowius, j...@willamowius.de, http://www.gnugk.org/
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] ekiga.net server down again

[Andre Robatino]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

The server is down again.  It's been down for at least a few hours.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAkpV84AACgkQ0pavuo9EGO//MgCfaatFlSmtcaiKx86m5QCz2tFu
R1cAn2OkNsgR5YYNgm9LnAnkT/7fuOJO
=Qs5Q
-END PGP SIGNATURE-
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] ekiga.net down again

[Andre Robatino]

The ekiga.net server is down again.  It's been down for at least an hour 
or two but may have been for much longer.


smime.p7s
Description: S/MIME Cryptographic Signature
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net down again

[Allen T Parker]

Yes.  I've been unable to connect for nearly 24 hours.



On Thu, 2009-04-30 at 02:03 -0400, Andre Robatino wrote:

 The ekiga.net server is down again.  It's been down for at least an hour 
 or two but may have been for much longer.
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net down again

[yannick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

AFAICT, ekiga.net is down since yesterday, ~19H30 (UTC+0200)

Allen T Parker a écrit :
 Yes.  I've been unable to connect for nearly 24 hours.
 
 
 
 On Thu, 2009-04-30 at 02:03 -0400, Andre Robatino wrote:
 
 The ekiga.net server is down again.  It's been down for at least an hour 
 or two but may have been for much longer.
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list
 
 
 
 
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkn5R1MACgkQaP9jcuuuScDbowCfZXA6L6xDgztLOrnKV+nmFF18
LVAAn0YmRGhiM3Im1R3pTT2HFaBYwlps
=j7cN
-END PGP SIGNATURE-
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net down again

[Damien Sandras]

Le mercredi 29 avril 2009 à 23:25 -0700, Allen T Parker a écrit :
 Yes.  I've been unable to connect for nearly 24 hours.
 

I restarted it. However, I'll be offline for several days. If it crashes
again, nobody will be able to restart it.
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

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

Re: [Ekiga-list] ekiga.net down again

[Dave Higton]

On 2009 April 29, Damien Sandras wrote:
 
 Le mercredi 29 avril 2009 à 23:25 -0700, Allen T Parker a écrit :
  Yes.  I've been unable to connect for nearly 24 hours.
  
 
 I restarted it. However, I'll be offline for several days. If 
 it crashes
 again, nobody will be able to restart it.

But /why/ does it fall over so 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.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net down again

[Damien Sandras]

Le jeudi 30 avril 2009 à 07:49 +0100, Dave Higton a écrit :
 On 2009 April 29, Damien Sandras wrote:
  
  Le mercredi 29 avril 2009 à 23:25 -0700, Allen T Parker a écrit :
   Yes.  I've been unable to connect for nearly 24 hours.
   
  
  I restarted it. However, I'll be offline for several days. If 
  it crashes
  again, nobody will be able to restart it.
 
 But /why/ does it fall over so frequently?

No idea. We should upgrade it. As long as I do not have an internet
connection at home, I can't upgrade it.
-- 
 _ Damien Sandras
(o-  
//\Ekiga Softphone : http://www.ekiga.org/
v_/_   Be IP   : http://www.beip.be/
   FOSDEM  : http://www.fosdem.org/
   SIP Phone   : sip:dsand...@ekiga.net
   

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

Re: [Ekiga-list] ekiga.net down again

[Evan Murphy]

 No idea. We should upgrade it.

Sounds like a great idea! How do we go about it?

Regards,
Evan Murphy
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] ekiga.net problems again?

[Palo S .]

I cannot register to ekiga.net from two computers in
different countries for around 30 minutes now. Is 
there a problem with ekiga.net again?

P.


__
http://auto.sme.sk - Všetko o autách (novinky, testy, autosalón, autoškola, 
porovnaj si auto)

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

Re: [Ekiga-list] ekiga.net problems again?

[Andre Robatino]

 I cannot register to ekiga.net from two computers in
 different countries for around 30 minutes now. Is
 there a problem with ekiga.net again?

It went down sometime between 2030 and 2050 UTC.  It's obvious when 
running Twinkle since the yellow star turns gray when it's not 
registered to any server.  It would be nice if the Start Tray icon for 
Ekiga did the same, if there isn't some obvious way to tell (I haven't 
used Ekiga in a while).


smime.p7s
Description: S/MIME Cryptographic Signature
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net problems again?

[Evan Murphy]

 I cannot register to ekiga.net from two computers in
 different countries for around 30 minutes now. Is
 there a problem with ekiga.net again?

I've been unable to register from Mexico today as well.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] ekiga.net problems again?

[Evan Murphy]

2009/4/26 Andre Robatino an...@bwh.harvard.edu:
 I cannot register to ekiga.net from two computers in
 different countries for around 30 minutes now. Is
 there a problem with ekiga.net again?

 It went down sometime between 2030 and 2050 UTC.

Any updates on this? I still can't connect.
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net numeric aliases

[yannick]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hello,

I'm the one who wrote the new web interface for ekiga.net. I know
numeric aliases are important for our users, ufortunately I'm facing
quite a lot of troubles in my life and the developement is very, very
slow at the moment.

The source code is available here:
http://webxser.tuxfamily.org/
and a bug for this particular feature has been opened here:
http://webxser.tuxfamily.org/flyspray/index.php?do=detailstask_id=5

but the plan is first to move the webinterface to drupal first. Still if
anyone want to add this feature in the meantime to webxser, this help
will be welcome.

Sorry for not being able to help you now,
Best regards,
Yannick

Simos a écrit :
 2009/3/25 Catalin Francu c...@francu.com:
 Hi Simos,

 Well, I'm new to ekiga, but if I understand correctly, each account, say
 sip:j...@ekiga.net, can have a numeric alias, say 1234...@ekiga.net, so that
 I can call John from an ATA (i.e., my phone has a numeric keypad, but not a
 full keyboard). I understand this functionality used to exist, but was
 removed sometime in 2008, along with the web-based account maintenance. I
 just cast my vote to bring it back. :-)

 I will look up this issue in Bugzilla, thanks for the pointer.
 
 I see. It looks like this issue is not an Ekiga issue but a feature in
 the SIP server at ekiga.net.
 That is, the SIP server at ekiga.net could be configured to allow
 these 'numeric aliases',
 that correspond to some index number (for example, the first person
 which subscribed to ekiga.net is 1, the second is 10001 and so on).
 
 For this, you can ask the admin at ekiga.net. I am not sure if s/he
 reads this list.
 
 It could be possible for Ekiga to provide support with a smart way
 that assigns numbers to individual accounts that you may have in your
 addressbook,
 something similar to the feature you have on a mobile phone. For
 example, when you
 dial '1' and it takes you to an entry in your addressbook that you
 configured earlier.
 Such a feature would work well when you have many different SIP
 providers enabled in your Ekiga.
 If you feel this would be more reasonable, then you need to search at
 bugzilla.gnome.org as
 instructed before.
 
 Hope this helps,
 Simos
 
 On Wed, Mar 25, 2009 at 1:50 PM, Simos simos.li...@googlemail.com wrote:
 2009/3/25 Catalin Francu c...@francu.com:
 Hi,

 First of all, thanks for Ekiga! Second, I'd like to add my vote to bring
 back the web interface, or at least the numeric alias feature.

 As a bit of background, I am looking for a new VoIP provider for a
 circle of
 about 20 family and friends. We have used FreeWorldDialup in the past,
 and
 even paid for membership in 2008, but their service has been appalling
 lately. We all use Handytone 286/386/486 ATAs, and we would like to keep
 using them. Most of these people are non-technical users and they would
 have
 a hard time using a soft phone; besides, they are not in the habit of
 keeping their computers on 24/7. Me and my brother took the time to set
 up
 and configure all these ATAs.

 Now we would love to switch to ekiga.net (we have been free software
 fans
 for many years), but to do so, we need numerical aliases in order to
 continue using ATAs and regular phones.

 There are several advantages to using an ATA over a soft phone: there is
 no
 need to keep the computer up 24/7, we can use any phone we like (e.g. a
 cordless one or an answering machine) etc. Please, bring back numeric
 aliases!
 I am not sure what you mean with numeric aliases. Can you give an example?

 The way to go forward with this request is to
 1. Check at http://bugzilla.gnome.org/browse.cgi?product=ekiga
 is the issue has been already reported.
 You normally go through the bug reports and try to find a similar request.
 2. If [1] was fruitful, subscribe to the bug report.
 3. If [2] was not fruitful, then you can add a bug report (of the type
 'feature request')
 and put here the URL to this bug report. Other users that are interested
 can subscribe to the report and add their input.

 Hope this helps,
 Simos
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list

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

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

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknLQJsACgkQaP9jcuuuScBCowCggsUwHfRPRv5RiCJU13bhyL+4
hHYAnirsS0yfMJzE1ImeuPTfqfv2QerK
=GYWs
-END PGP SIGNATURE-
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

[Ekiga-list] Ekiga.net numeric aliases

[Catalin Francu]

Hi,

First of all, thanks for Ekiga! Second, I'd like to add my vote to bring
back the web interface, or at least the numeric alias feature.

As a bit of background, I am looking for a new VoIP provider for a circle of
about 20 family and friends. We have used FreeWorldDialup in the past, and
even paid for membership in 2008, but their service has been appalling
lately. We all use Handytone 286/386/486 ATAs, and we would like to keep
using them. Most of these people are non-technical users and they would have
a hard time using a soft phone; besides, they are not in the habit of
keeping their computers on 24/7. Me and my brother took the time to set up
and configure all these ATAs.

Now we would love to switch to ekiga.net (we have been free software fans
for many years), but to do so, we need numerical aliases in order to
continue using ATAs and regular phones.

There are several advantages to using an ATA over a soft phone: there is no
need to keep the computer up 24/7, we can use any phone we like (e.g. a
cordless one or an answering machine) etc. Please, bring back numeric
aliases!

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

Re: [Ekiga-list] Ekiga.net numeric aliases

[Simos]

2009/3/25 Catalin Francu c...@francu.com:
 Hi,

 First of all, thanks for Ekiga! Second, I'd like to add my vote to bring
 back the web interface, or at least the numeric alias feature.

 As a bit of background, I am looking for a new VoIP provider for a circle of
 about 20 family and friends. We have used FreeWorldDialup in the past, and
 even paid for membership in 2008, but their service has been appalling
 lately. We all use Handytone 286/386/486 ATAs, and we would like to keep
 using them. Most of these people are non-technical users and they would have
 a hard time using a soft phone; besides, they are not in the habit of
 keeping their computers on 24/7. Me and my brother took the time to set up
 and configure all these ATAs.

 Now we would love to switch to ekiga.net (we have been free software fans
 for many years), but to do so, we need numerical aliases in order to
 continue using ATAs and regular phones.

 There are several advantages to using an ATA over a soft phone: there is no
 need to keep the computer up 24/7, we can use any phone we like (e.g. a
 cordless one or an answering machine) etc. Please, bring back numeric
 aliases!

I am not sure what you mean with numeric aliases. Can you give an example?

The way to go forward with this request is to
1. Check at http://bugzilla.gnome.org/browse.cgi?product=ekiga
is the issue has been already reported.
You normally go through the bug reports and try to find a similar request.
2. If [1] was fruitful, subscribe to the bug report.
3. If [2] was not fruitful, then you can add a bug report (of the type
'feature request')
and put here the URL to this bug report. Other users that are interested
can subscribe to the report and add their input.

Hope this helps,
Simos
___
ekiga-list mailing list
ekiga-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-list

Re: [Ekiga-list] Ekiga.net numeric aliases

[Catalin Francu]

Hi Simos,

Well, I'm new to ekiga, but if I understand correctly, each account, say
sip:j...@ekiga.net sip%3aj...@ekiga.net, can have a numeric alias, say
1234...@ekiga.net, so that I can call John from an ATA (i.e., my phone has a
numeric keypad, but not a full keyboard). I understand this functionality
used to exist, but was removed sometime in 2008, along with the web-based
account maintenance. I just cast my vote to bring it back. :-)

I will look up this issue in Bugzilla, thanks for the pointer.

Catalin

On Wed, Mar 25, 2009 at 1:50 PM, Simos simos.li...@googlemail.com wrote:

 2009/3/25 Catalin Francu c...@francu.com:
  Hi,
 
  First of all, thanks for Ekiga! Second, I'd like to add my vote to bring
  back the web interface, or at least the numeric alias feature.
 
  As a bit of background, I am looking for a new VoIP provider for a circle
 of
  about 20 family and friends. We have used FreeWorldDialup in the past,
 and
  even paid for membership in 2008, but their service has been appalling
  lately. We all use Handytone 286/386/486 ATAs, and we would like to keep
  using them. Most of these people are non-technical users and they would
 have
  a hard time using a soft phone; besides, they are not in the habit of
  keeping their computers on 24/7. Me and my brother took the time to set
 up
  and configure all these ATAs.
 
  Now we would love to switch to ekiga.net (we have been free software
 fans
  for many years), but to do so, we need numerical aliases in order to
  continue using ATAs and regular phones.
 
  There are several advantages to using an ATA over a soft phone: there is
 no
  need to keep the computer up 24/7, we can use any phone we like (e.g. a
  cordless one or an answering machine) etc. Please, bring back numeric
  aliases!

 I am not sure what you mean with numeric aliases. Can you give an example?

 The way to go forward with this request is to
 1. Check at http://bugzilla.gnome.org/browse.cgi?product=ekiga
 is the issue has been already reported.
 You normally go through the bug reports and try to find a similar request.
 2. If [1] was fruitful, subscribe to the bug report.
 3. If [2] was not fruitful, then you can add a bug report (of the type
 'feature request')
 and put here the URL to this bug report. Other users that are interested
 can subscribe to the report and add their input.

 Hope this helps,
 Simos
 ___
 ekiga-list mailing list
 ekiga-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/ekiga-list

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