search

uedev / imsdroid

Automatically exported from code.google.com/p/imsdroid
0 stars 0 forks source link

Ekiga Account #22

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Ekiga Account 
2.
3.

What is the expected output? What do you see instead?
I tried to configure the account of Ekiga on IMS droid. I tried to put my 
account as follows: 
Display Name : Aabhas Garg
Public Identity: aabhasgarg@ekiga.net
Private Identity : aabhasgarg
Password :  -----
Realm: sip:ekiga.net
Uncheck 3GPP Early IMS Security

Check either Enable WiFi or 3G
Proxy CSCF Host:ekiga.net
Proxy-CSCF Port: 5060
Transport: UDP
Proxy-CSCF Discovery:None
Uncheck Enable SigComp

Return to Home screen and click the sign in and say " Trying to register" but 
it did not work and say the message "UnRegistered: Dialog Terminated" " and 
then again to return the home screen and tried to configure NATT as I suspected 
:
Check Enable STUN/TURN
Check the radio button : Use this STUN/TURN Server
Server Address : stun.ekiga.net
Server Port: 3478

and then return to home screen again and click the sign in and say the same 
message as above.

Please let  me know if you have any idea.

Aabhas

What version of the product are you using? On what operating system?
Android EVO

Please provide any additional information below.

Original issue reported on code.google.com by AabhasG...@gmail.com on 5 Aug 2010 at 10:11

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Unfortunately the client will not work with ekiga.net because there is a bug on 
their server. Have you managed to get non-Ekiga (e.g. xlite) client behind a 
NAT to register to their server?
Just some remarks:
 * your public identity should be a valid SIP URI (scheme is missing)
 * you should use a STUN server which supports the latest version (2.0) as per RFC 5769 like "numb.viagenie.ca"
Here is a reference to the bug from their tacker: 
https://bugzilla.gnome.org/show_bug.cgi?id=624751
Their explanation does make sense and is not based on any specification.

Original comment by boss...@yahoo.fr on 6 Aug 2010 at 1:29

GoogleCodeExporter commented 9 years ago 
I have created a wiki page here: 
http://code.google.com/p/imsdroid/wiki/ekiga_org.
Will be updated when you (or I) find a way to connect to their server.

Original comment by boss...@yahoo.fr on 6 Aug 2010 at 1:30

GoogleCodeExporter commented 9 years ago 
I changed the stun server as you suggested but it does not seems work. I 
understand ekiga has some bugs. I mostly used so everything should be fine in 
ekiga. Did you know sipdroid in google code. I think it seems work perfect with 
ekiga stun server.

Original comment by AabhasG...@gmail.com on 6 Aug 2010 at 2:33

GoogleCodeExporter commented 9 years ago 
The problem is not only about the STUN server but also on the SIP proxy. I know 
Sipdroid and it's not a reference. We cannot change the code just to work with 
Ekiga. Their implementation  is not correct and doesn't follow any 
specification. I had attached the reference to the bug: 
https://bugzilla.gnome.org/show_bug.cgi?id=624751.
I will check SipDroid to see if it works with Ekiga.

Original comment by boss...@yahoo.fr on 6 Aug 2010 at 2:43

GoogleCodeExporter commented 9 years ago 
OK I want to join the member of your project as I intend to propose your 
project and change some source code for the deaf accessibility like connect 
from android to PC and vice versa. Can you active my member as 
aabhasgarg@gmail.com ?

Original comment by AabhasG...@gmail.com on 31 Jul 2011 at 6:58