Re: [Wengophone-devel] Wengophone and generic SIP Account (ekiga) through NAT(?) problems
Hi! On 24.02.2008 18:58, Thomas Monjalon wrote: Darshaka Pathirana a écrit : I am not even able to login. Are my settings correct? Does anybody have experience with connecting Wengophone to the ekiga.net server? I tried this (it didn't work) and the result of my test was: the HTTP tunnel proxy which helps to pass through NAT doesn't work with a generic SIP account. Does that mean WengoPhone is not (and never was) able to connect to any other SIP-Provider (because the HTTP tunnel proxy does not support that)? This IS serious (at least for me). Any ideas on how to overcome this limitation? Wengo tries to connect to ekiga with [EMAIL PROTECTED] (why that?) and gets a 401 Unauthorized back from ekiga.net. After that Openwengo tries to REGISTER with From: sip:[EMAIL PROTECTED] but this time never gets an answer. What's going on there? The first register with nobody is a SIP ping to test the server. It is defined in wifo/netlib/src/netlib.cpp. It needs improvements but it works fine in your case. Ok. That sounds ok. I don't remember why you have a response to the SIP ping but not for the true register. I think that the solution is in HTTP proxy... Could you send your wireshark log ? Yes I have the same concern. I've attached the pcap-file of my trace... The HTTP tunnel is not implemented in generic SIP. You can check it in SipAccount::discoverForSIP (wengophone/src/model/account/SipAccount.cpp) and in WengoAccount::discoverForSIP (wengophone/src/model/account/wengo/WengoAccount.cpp). I ever tried to implement HTTP tunnel in generic SIP but it didn't work. I think that it is a political reason in proxy implementation. Ok. Thank you for pointing out. I had no idea that SIP is tunneled through a HTTP tunnel. Is there no other solution? It seems that I have to read into it... So my first statement seems to be true... right? *sigh* Thanks for your help! Greetings, - Darsha wengophone_ekiga.pcap Description: Binary data ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] New Project Name
Hi, Patrick Aljord wrote: On Sun, Feb 24, 2008 at 3:21 PM, Dave Neary [EMAIL PROTECTED] wrote: I find it a little disheartening that what was initially announced as a competition to choose a new name has now been announced as a unilateral decision... at the very least, I would have liked to see a shortlist of 4 or 5 candidates registered and thrown out to the community for voting/comments. As Vadim explained, this is technically not possible. I don't know if you've ever tried to buy a domain name, but people just try to speculate and buy everything in the dictionary or not. Doing a public contest would be impossible cause some people would simply buy the winner and try to sell it to the community later. I have about a dozen domain names mostly lying idle. Some will be used in the future. You can buy a domain name for a year for under $10. Let's say that after doing the first level of filtering, you whittle things down to 5 names whose domain names in .com and .org are available - register 2*5 domain names for $100, and publish the short list. If all else fails, sell the other 8 :) It's a little self-important to imagine domain name hoarders following our little mailing list by the way :) There are also projects who use names derived from the project name - think of sane-project.org, spreadfirefox.com getfirefox.com (not sure why MoFo didn't buy the .orgs associated with those, though...), mono-project.com, etc. While having the right domain name is important, it's not the end of the world to have a related domain name (like say pidgin.im) as long as it's distinctive memorable. Cheers, Dave. -- Dave Neary [EMAIL PROTECTED] ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] Wengophone and generic SIP Account (ekiga) through NAT(?) problems
Darshaka Pathirana wrote: On 24.02.2008 18:58, Thomas Monjalon wrote: Darshaka Pathirana wrote: I am not even able to login. Are my settings correct? Does anybody have experience with connecting Wengophone to the ekiga.net server? I tried this (it didn't work) and the result of my test was: the HTTP tunnel proxy which helps to pass through NAT doesn't work with a generic SIP account. Does that mean WengoPhone is not (and never was) able to connect to any other SIP-Provider (because the HTTP tunnel proxy does not support that)? This IS serious (at least for me). Any ideas on how to overcome this limitation? In rare cases where tunnelling is useless, I think it is possible to use generic SIP account. A solution is to implement another tunnel proxy but the bandwidth is difficult to support. Maybe that the best solution is to have distributed proxies like Skype do. I don't remember why you have a response to the SIP ping but not for the true register. I think that the solution is in HTTP proxy... Could you send your wireshark log ? Yes I have the same concern. I've attached the pcap-file of my trace... It seems that your NAT allow SIP because you have a response to your SIP ping in a true UDP packet. But the second register doesn't have a response. What is the difference ? Maybe the via line with local address... Could you try to remove the via ? You can comment osip_message_set_via() in wifo/eXosip/src/jrequest.c The HTTP tunnel is not implemented in generic SIP. You can check it in SipAccount::discoverForSIP (wengophone/src/model/account/SipAccount.cpp) and in WengoAccount::discoverForSIP (wengophone/src/model/account/wengo/WengoAccount.cpp). I ever tried to implement HTTP tunnel in generic SIP but it didn't work. I think that it is a political reason in proxy implementation. Ok. Thank you for pointing out. I had no idea that SIP is tunneled through a HTTP tunnel. Is there no other solution? It seems that I have to read into it... -- Thomas ___ Wengophone-devel mailing list Wengophone-devel@lists.openwengo.com http://dev.openwengo.com/mailman/listinfo/wengophone-devel
Re: [Wengophone-devel] G772 and P2P SIP/SIMPLE
On Fri, Feb 22, 2008 at 06:17:57PM +0100, Vadim Lebedev wrote:
Ralf we did a lot of fixes to presence stuff
Please try latest version
Hmm, I've just compiled tested without much further news:
- When turning on p2p presence, it still doesn't work for our
infrastructure
- ekiga.net is still not using presence at all (no matter if p2p is
turned on or off) although this used to work
I'd like to revert to an older version (maybe to the one when you moved
to hg) -- can you give me a short intro how I can revert to the start of
the hg version of the 2.2 branch, then I re-test ekiga.net to make sure
they didn't change anything that makes presence fail.
- I had to patch src/presentation/main.cpp, otherwise it errors out when
compiling, seems that getSipChatWhithouPresence isn't defined (looks
like a typo, but searching for getSipChat didn't find anything either):
diff -r a58d652beefd wengophone/src/presentation/main.cpp
--- a/wengophone/src/presentation/main.cpp Fri Feb 22 18:13:12 2008 +0100
+++ b/wengophone/src/presentation/main.cpp Tue Feb 26 08:38:59 2008 +0100
@@ -288,10 +288,10 @@ int main(int argc, char * argv[]) {
else
w-setSipOptions(sip.p2p_presence, false);
- if(config.getSipChatWhithouPresence())
+ //if(config.getSipChatWhithouPresence())
w-setSipOptions(sip.chat.whithout.presence, true);
- else
- w-setSipOptions(sip.chat.whithout.presence, false);
+ //else
+ //w-setSipOptions(sip.chat.whithout.presence, false);
if(config.getSipUseTypingState())
w-setSipOptions(sip.use_typing_state, true);
Ralf
--
Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16
Open Source Consulting Fax: +43/2243/26465-23
Reichergasse 131www: http://www.runtux.com
A-3411 Weidling email: [EMAIL PROTECTED]
osAlliance member email: [EMAIL PROTECTED]
___
Wengophone-devel mailing list
Wengophone-devel@lists.openwengo.com
http://dev.openwengo.com/mailman/listinfo/wengophone-devel
