Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client
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
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
On Wed, May 25, 2011 at 10:06 AM, Bart Vandewoestyne wrote: > On Wed, May 25, 2011 at 02:04:10AM +0300, J??nis Rukš??ns wrote: >> >> [...] >> From the traces it looks like it doesn't support any way to traverse >> NAT. It is not really a bug, but rather important missing feature, >> something they should do. > > Wait a second... then why do the registrations at sip.poivy.com > and sip.diamondcard.us work? Doesn't this mean that my > SIP-client *is* somehow able to traverse NAT? (I'm afraid i'm > missing technical background about NAT-traversal here to be able > to answer this question myself :-( No, it doesn't mean that the client is able to "traverse" NAT. It means that either the *server* is able to traverse NAT by relaying the audio, or you will have no audio in an actual call (either incoming or both ways). The technical background is that when you make a call, the phone sends an INVITE message, telling the other end your IP and the port where to send audio. However, if you're behind NAT, that IP and port is generally not reachable from the outside world. Which means that with no NAT support, the audio sent by the other end will not reach you. The same applies to the called phone, if it is behind NAT as well, you will have no audio at all. There are several ways to counter this: 1) "classic" STUN - the phone can discover the corresponding public IP and port by contacting a STUN server, and then uses it in the INVITE. However this doesn't work for more complex types of NAT, and the whole thing is a bit sketchy. Therefore "classic" STUN has been deprecated for some time. 2) ICE - instead of contacting a dedicated STUN server, the endpoints communicate between themselves to find out each others public IPs and ports used for audio. This works in most cases, except when both parties are behind a very restrictive NAT. 3) Dedicated media relay server - instead of sending audio directly to the other party, the audio is sent through a dedicated server with a public IP. This works even with no NAT support in the client, but is very costly to the provider (in terms of bandwidth, hardware and money). If the phone supports either STUN or ICE, it is usually indicated by a public IP in the Contact address. I'm pretty sure diamondcard.us have a relay server, thus they don't care whether the IP is public or private. Ekiga.net doesn't have a relay server, therefore it's reasonable that it rejects registrations with private IPs. Cheers -- Ian ___ 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
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
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
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
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
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 native SIP-client
(Bringing this back to the mailing list)
On Tue, May 24, 2011 at 11:11 PM, Bart Vandewoestyne
wrote:
> OK. The tcpdump I did with my android phone is online at
>
> http://www.kuleuven-kortrijk.be/~bartv/android.pcap
>
> I've configured 4 SIP accounts and they all try to register.
> These are my findings:
>
> 1) For you server, I see a 400 Bad Contact address server
> response, and as I understand it, this is because of the private
> IP in the Contact header in the REGISTER message.
>
> 2) registration for sip.poivy.com and sip.diamondcard.us seem to
> work, even with the private IP in the Contact header.
Right.
> 3) registration at ekiga.net fails, server returns a 606 Not
> Acceptable, probably because of the private IP in the Via header.
First one ("unregister others") because of the Via, the second because
of the Contact. Your previous ekiga.net trace was missing the second
REGISTER message, which led me to believe that Via was the main fault.
> My main questions are:
>
> * Do you see a bug in the Android 2.3.4 client? Can it send
> REGISTER messages with private IP's in the Via and Contact
> header or is this not allowed?
From the traces it looks like it doesn't support any way to traverse
NAT. It is not really a bug, but rather important missing feature,
something they should do. IPv6 is not going to take over IPv4 any time
soon, and there are other good reasons to use NAT (eg. my provider
charges me for each public IP).
> * Is ekiga.net wrong by returning the 606 Not Acceptable?
>
> If ekiga.net is wrong, I still feel we should try to convince the
> ekiga.net admins to make it work... it will be a big step forward
> for Ekiga on the Android/mobile market.
Technically ekiga.net is wrong about the Via (but not Contact), but
with no NAT support in phone (either classic STUN or ICE, or
whatever), it doesn't make any difference to you. As Damien told in
another post, you will experience audio problems (almost certainly).
But the cool thing about SIP is you're not tied to a single provider.
You can call anyone with a SIP address no matter what your provider
is. If the phone has no NAT support, there are multiple providers with
media relay, select the one(s) you like, and configure to use their
outbound proxy. At least audio should work fine.
Cheers
--
Ian
___
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
On Mon, May 23, 2011 at 3:35 PM, Dave Koelmeyer wrote: > On 20/05/11 08:02 PM, Bart Vandewoestyne wrote: >> >> Damien? What's your opinion on changing the ekiga.net config so >> that these issues get resolved? >> >> Kind regards, >> Bart > > My concern is that for the end-user this is undermining the usefulness of > Ekiga.net, and therefore adoption of Ekiga as a SIP client. I have tested > *four* different Mac OS SIP clients from behind a NAT router, and all four > of them cannot and will not connect to Ekiga.net: > > - Jistsi (aka Sip Communicator) > - Telephone > - Blink > - X-Lite 4 You can add Empathy and Nokia N900 to that list. > For the end-user, I can easily see this as a case of interoperability with > Ekiga users potentially not being worth the effort, so move on to something > else. It makes evangelising Ekiga for me (and SIP as an alternative to Skype > for example) very challenging, when the promoted back-end service is broken > with regards to cross-client interoperability. > > Some further discussion about this with a view to knowing if it can be > resolved would be really useful at this point. Promoting SIP as an alternative to Skype will always be challenging, due to: 1) The large user base of Skype, and different protocols being used. Although there is an official Skype/SIP gateway, it is paid service, buggy and limited in functionality (you cannot simply call any Skype user). 2) NAT issues. In theory they are applying to Skype as well, but by installing Skype you're agreeing that your computer can be used for relaying other users' traffic, something that's not that easy with SIP. Setting up a dedicated server for media relay however can be expensive, and it doesn't scale well. Also I think that the average user's mindset plays a role here. For the non-computer savvy Jane Doe, VoIP and Skype are synonyms, just like PC and Windows, or, until recently, the Internet and IE. People will use whatever comes preinstalled, and one has to convince them that the alternative is significantly better. Of course sub-par services don't do any good here, but in the same time you cannot expect Damien to provide a media relay server, given that the service is gratis. Just my $.02 -- Ian ___ 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
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
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
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
Re: [Ekiga-list] Ekiga.net account with Android 2.3.4 native SIP-client
On Fri, May 20, 2011 at 1:56 AM, Bart Vandewoestyne wrote: > On Fri, May 20, 2011 at 01:32:03AM +0300, J??nis Rukš??ns wrote: >> >> > If I use my Android phone, then i have >> > >> > REGISTER sip:ekiga.net SIP/2.0 >> > Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138 >> > CSeq: 8429 REGISTER >> > From: "Bart.Vandewoestyne" >> > ;tag=4156217873 >> > To: "Bart.Vandewoestyne" >> > Via: SIP/2.0/UDP >> > 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport >> > Max-Forwards: 70 >> > User-Agent: SIPAUA/0.1.001 >> > Contact: * >> > Expires: 0 >> > Content-Length: 0 >> > [...] >> >> This is something I didn't expect at all - the message your phone >> sends actually asks ekiga.net to unregister everyone from >> sip:bart.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
On Fri, May 20, 2011 at 2:02 AM, Bart Vandewoestyne 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
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
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" ;tag=4156217873 > > To: "Bart.Vandewoestyne" > > Via: SIP/2.0/UDP > > 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport > > Max-Forwards: 70 > > User-Agent: SIPAUA/0.1.001 > > Contact: * > > Expires: 0 > > Content-Length: 0 > > [...] > > This is something I didn't expect at all - the message your phone > sends actually asks ekiga.net to unregister everyone from > sip:bart.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
On Fri, May 20, 2011 at 12:30 AM, Bart Vandewoestyne wrote: > On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote: >> >> I've updated the file, i think we now have the full information. >> The new version is at the same url, namely >> >> http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap >> >> Please let me know if this is enough info to debug my problem. >> If not, then let me know what to do. I'm glad to be able to help >> here! > > OK. I've done some more searching, and this is what I have so > far. If I try with Ekiga on my laptop, then this is how a typical > REGISTER message looks like: > > > REGISTER sip:ekiga.net SIP/2.0 > CSeq: 2 REGISTER > Via: SIP/2.0/UDP > 178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport > User-Agent: Ekiga/3.2.7 > From: > ;tag=282f826b-cb80-e011-82e5-00216b30c960 > Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960@maverick > To: > Contact: ;q=1, > ;q=0.500 > Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING > Expires: 3600 > Content-Length: 0 > Max-Forwards: 70 > > > If I use my Android phone, then i have > > > REGISTER sip:ekiga.net SIP/2.0 > Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138 > CSeq: 8429 REGISTER > From: "Bart.Vandewoestyne" ;tag=4156217873 > To: "Bart.Vandewoestyne" > Via: SIP/2.0/UDP > 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport > Max-Forwards: 70 > User-Agent: SIPAUA/0.1.001 > Contact: * > Expires: 0 > Content-Length: 0 > > > The most important differences that I notice are: > > * Ekiga uses the public WAN address of my router in the Via header, whereas my > android phone has the local LAN address and port. > > * Ekiga uses both the public WAN address and the local LAN address in the > Contact header, whereas my Android phone simply sets the '*'-symbol. > > My question to this list is still the same: > > Is this a bug or a missing feature (STUN) in the native Android client, or is > the problem on the ekiga.net server side? This is something I didn't expect at all - the message your phone sends actually asks ekiga.net to unregister everyone from sip:bart.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
On Thu, May 19, 2011 at 11:15:58PM +0200, Bart Vandewoestyne wrote: > > I've updated the file, i think we now have the full information. > The new version is at the same url, namely > > http://www.kuleuven-kortrijk.be/~bartv/sip_capture.pcap > > Please let me know if this is enough info to debug my problem. > If not, then let me know what to do. I'm glad to be able to help > here! OK. I've done some more searching, and this is what I have so far. If I try with Ekiga on my laptop, then this is how a typical REGISTER message looks like: REGISTER sip:ekiga.net SIP/2.0 CSeq: 2 REGISTER Via: SIP/2.0/UDP 178.117.245.74:5060;branch=z9hG4bK1c2c966b-cb80-e011-82e5-00216b30c960;rport User-Agent: Ekiga/3.2.7 From: ;tag=282f826b-cb80-e011-82e5-00216b30c960 Call-ID: 7a1e826b-cb80-e011-82e5-00216b30c960@maverick To: Contact: ;q=1, ;q=0.500 Allow: INVITE,ACK,OPTIONS,BYE,CANCEL,SUBSCRIBE,NOTIFY,REFER,MESSAGE,INFO,PING Expires: 3600 Content-Length: 0 Max-Forwards: 70 If I use my Android phone, then i have REGISTER sip:ekiga.net SIP/2.0 Call-ID: 261a54f294918a1eae37a14f2dc7dc89@192.168.1.138 CSeq: 8429 REGISTER From: "Bart.Vandewoestyne" ;tag=4156217873 To: "Bart.Vandewoestyne" Via: SIP/2.0/UDP 192.168.1.138:45061;branch=z9hG4bK686f4bc2b5692c50ca09b29d1f26e6283531;rport Max-Forwards: 70 User-Agent: SIPAUA/0.1.001 Contact: * Expires: 0 Content-Length: 0 The most important differences that I notice are: * Ekiga uses the public WAN address of my router in the Via header, whereas my android phone has the local LAN address and port. * Ekiga uses both the public WAN address and the local LAN address in the Contact header, whereas my Android phone simply sets the '*'-symbol. My question to this list is still the same: Is this a bug or a missing feature (STUN) in the native Android client, or is the problem on the ekiga.net server side? Regards, Bart -- "Share what you know. Learn what you don't." ___ 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
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
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
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
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
On 19 May, 2011,at 12:35 AM, Jānis Rukšāns wrote:Hi, On Wed, May 18, 2011 at 2:53 PM, Bart Vandewoestyne > With these settings, I cannot seem to register myself, I get the > error > > "Primary account. Account registration failed: (Not Acceptable > (606)); will try later" > > > Am I doing something wrong here or can the native Android 2.3.4 > SIP client not work with Ekiga accounts yet? If not, then maybe > somebody can tell me what features are missing in order to get > Ekiga up and running, so we can submit a feature request at > http://source.android.com/source/report-bugs.html ? Wouldn't > that be a nice step forward? Most likely it is neither you nor the Android SIP client. The ekiga.net server has an overly restrictive configuration, which prevents any sufficiently up-to-date SIP client from registering from behind NAT. There have been numerous posts on the list regarding this. I imagine this isn't a trivial issue to fix, but all the same do we know who looks after Ekiga.net and would this be something that could be addressed?Cheers, Dave___ 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
On Wed, May 18, 2011 at 3:46 PM, Bart Vandewoestyne wrote: > On Wed, May 18, 2011 at 03:35:07PM +0300, J??nis Rukš??ns wrote: >> >> Most likely it is neither you nor the Android SIP client. The >> ekiga.net server has an overly restrictive configuration, which >> prevents any sufficiently up-to-date SIP client from registering from >> behind NAT. There have been numerous posts on the list regarding this. > > Hmm... having googled around a bit, my guess would rather be that > i cannot register because the native Android 2.3.4 SIP client > seems not to support STUN. Couldn't this be the major problem > for me not being able to register instead of an 'overly > restrictive configuration' of the ekiga.net server? > > If others agree that this lack of STUN support is most likely the > reason why my registration fails, then it seems like a good idea > to vote for Judging from http://www.onsip.com/blog/leo/2011/01/05/our-evaluation-of-android-gingerbreads-native-sip-calling-with-the-nexus-s it seems that the Android SIP client is working fine from behind NAT - the SIP traces show a private IP in Via header, and a public one in Contact. Most likely your registration fails because ekiga.net is apparently configured to require a public IP in both Via and Contact headers. I cannot be 100% sure without seeing the actual SIP messages, but I guess a private IP in Via is why your registration fails. And sending 606 Not Acceptable Anywhere to REGISTER is a violation of the SIP standard on it's own. -- Ian ___ 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
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
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
