|
Re: Sip Authentication failed on Diablo
Packet capture:
tcpdump can be used on the Nokia device. Wireshark/Ethereal could be used from another host. See http://maemo.org/development/documen...s/tcpdump.html for more information. General questions to check for SIP issues: * Do you use NAT? * If it's a SIP account, what are the account parameters? Is transport set to UDP in the Advanced settings of your SIP account? * Could you also provide a syslog? To do so, start a terminal window. Now export TPORT_LOG=1 and export SOFIASIP_DEBUG=all in the environment (e.g. by editing /etc/osso-af-init/af-defines.sh) for telepathy-sofiasip. Exporting SOFIASIP_PERSIST=1 also prevents telepathy-sofiasip from exiting due to no connections being requested. Now SIP traffic logs get dumped into syslog. Also see http://maemo.org/development/tools/doc/diablo/syslog/ . * Access Point Make and model? * Access Point Firmware version? * Access Point Hardware revision? * What are the encryption settings? (open/WEP/WPA-PSK/WPA-EAP) > Has anyone contacted the developers of according packages? The correct way is to file a bug report with the requested info included at bugs.maemo.org |
Re: Sip Authentication failed on Diablo
I'm new at Maemo. Where can i find a packed version of sysklogd for maemo?
|
Re: Sip Authentication failed on Diablo
Hi all,
I've the same problem and looked at the network traffic with wireshark when my N810 tries to register with sip.1und1.de. What happens is the following: Code:
N810: REGISTER 123456789@sip.1und1.deThe problem is that the server doesn't accept local (RFC1819) IPs (marked with *) to be registered. When I try to use an ekiga account with the N810's sip software the problem is the same. If a RFC1819 IP is in the contacts the server refuses to register. On the other hand one could say the problem is on client side, because telepathy (this is the N810's sip software) tries to register with the local IP. It should use the NAT's (the router you are behind) public IP instead, which it found out using STUN. I guess that in chinook telepathy was only registering the public IP, this is why it was working there. The solutions could be to reconfigure the 1und1 server to allow local IPs, which is practically not possible. The other solution would be to tell telepathy not to register the local IP. Does anyone out there know how to do that? Would it be possible to do that via config files or is the registration procedure something completely hardcoded? If there are config files for telepathy, where can one find them? Is there a documentation? |
Re: Sip Authentication failed on Diablo
Interesting findings, I would be interested in some way to configure telepathy to use the public IP too..
|
Re: Sip Authentication failed on Diablo
@ quantenschaum
These are some very interesting findings. Thanks for your work so far. I wasn't able to figure out anything new lately. In the meantime i'm still using Gizmo with the 1und1 account; But would really love to use the build in client again. ;) |
Re: Sip Authentication failed on Diablo
The same happens with eutelia network from Italy, i've got the traces with wireshark both chinhook and diablo.
If Discover Public IP is active the first REGISTER is always with private IP and fails... then the second REGISTER is different between chinhook and diablo: - Chinhook tries to register with one contact using the public IP address and succeed - Diablo tries with two contacts one with private IP and one with public IP and the server refuse the authentication If someone want to see the traces... just ask! |
Re: Sip Authentication failed on Diablo
@SteelBlade
Please post the traces as well. So we can gather as much information here in this thread as possible. Thanks for your effort. |
Re: Sip Authentication failed on Diablo
Quote:
I use Ekiga from my Fedora desktop with no problem. The maemo built-in client gets errors. Same settings, same 192.168.5.0/24 network .... I've been getting the 403 messages (without the indication of "RFC1819" space) for months .... [Whoops - it's a 606 message, and I've been getting it since Oct 2008 -- I found my old post about it. This had been working in summer of 2008. I've just chalked it up to another in the growing list of non-working "features" on the N810] |
Re: Sip Authentication failed on Diablo
1 Attachment(s)
Hi fattomm,
Yes that's a typo, I meant RFC1918 IPs, but I think you got what I meant. You may doubt it, but exactly this is the problem. As said Quote:
Code:
N810: REGISTER 123456789@sip.1und1.deSomeone asked for the wireshark trace, here it is. Happy computing, Q. |
Re: Sip Authentication failed on Diablo
So I suspect I have the same problem ("Internet Call" works with non-NATed Internet connection but does not work behind a NAT)
One problem I have is confusion with the the seemingly convoluted state of the rtcomm project. So I have an N810 with Diablo, fully updated as far as I know (are there some tests for this?), and I have a lot of repositories in my installer catalogue including "packages.collabora.co.uk/maemo diablo user". I do NOT have pidgin installed. I tried installing the package listed in this thread for installing the rtcomm beta installer ver 6 and ran it. It installed an installer in my menu, which I then ran. It looked liked it got most of the way through but then failed. An "rtcomm" is no longer listed in my installer under non-installed files, but I have both rtcomm-beta-os2008 (V2.4-1), and rtcomm-beta-installer (v.06) listed in "installed applications". So do I have a working version of rtcomm for Diablo? Is there a working version for Diablo? Can I now remove the rtcomm-beta-installer? Reviewing my SIP setup: I am using Ekiga.NET It logs in and works when non NATed I have STUN set to "stun.ekiga.net" and the default port of 3478 and the "Auto-detect STUN" turned off. I have the "Authentication" tab things set up with the same user name and password as I have in the "connection" tab. I am not sure what this is for anyway. So when NAT'ed I get the flashing icon (from green to red with white line through it) and an occasional message of "Unable to connect to one or more accounts". Again, once I switch to a non-NAT'ed connection, this setup seems to work fine, in that I can call the ekiga echo test and talk to myself. |
Re: Sip Authentication failed on Diablo
Oh yea, and from the same NAT'ed network I can start up and run Ekiga on my desktop computer and have it connect and talk to myself.
Since both are attempting to use the same Ekiga account, I think I am careful not to run them both at the same time. I have no ports forewarded on my router for any of this either. |
Re: Sip Authentication failed on Diablo
Okay, here is an update on my progress.
I am now pretty sure I have the latest rtcomm installed. It was harder than it should have been to get there. I had to manually download and install (with dpkg -i) a lot of dependant packages and deal with hiding some symlinks in /etc/rc2.d to make the installer happy. Very messy. Although I still have the same NAT problem, I then configured another SIP provider (Gizmo) and it worked! So I guess this is an Ekiga problem? Maybe I'll bug them and see if they have an answer. It's funny, I've had my N810 for about a year-and-a-half and this is the first time I've played around with its VoIP capability. Although it has been fun, I'm not sure yet how practical it is since my N810 is often out of Internet range, and I seem to have plenty of traditional phone services around. In fact I only stated messing around with this to configure my N810 to test a point-to-point Skype setup for a video conference. Too bad the N180 Skype client doesn't do video. I've also joined the masses in waiting for Google-Voice to become available to new users again. |
Re: Sip Authentication failed on Diablo
Quote:
Summary: Linux Fedora 9 + Ekiga Application works fine through NAT N810 + RTComm + Ekiga breaks N810 + RTComm + Gizmo works I have a few issues of Fedora9+EkigaApp+Ekiga with video to/from N810+RTComm+Gizmo, but I'll leave that for another day ... |
Re: Sip Authentication failed on Diablo
Oh yes, I agree and have the same experience, as noted above I have Ekiga working from a software SIP phone on my desktop PC on the same NATed network as well. My thoughts are that Ekiga is either being much more strict with the protocols or simply have something wrong compared to a provider like Gizmo.
|
Re: Sip Authentication failed on Diablo
Just found that there is a bug report on that issue in bugzilla
Bug id=4259 It is a know Sofia-SIP bug and tagged as wontfix. I have not yet fully understood if adding support for that non-compliant SIP server behavior would break anything.... |
Re: Sip Authentication failed on Diablo
I am trying to configure the n800 (diablo) caller to use a sip service. I am under a NAT, and I've tried voipbuster, Ekiga and Gizmo accounts and I have the same problem of inability to register.
Is this bug related using any server, or just ekiga? I do believe I managed to connect once using voipbuster, but I can't do it anymore. Maybe it's my router making fun of me?... Is there any way I can configure my router to at least see if I can make it work? What ports do I have to forward to my tablet? BTW, the Gizmo client works OK, only the camera didn't work... (I tested with the Linux version, not sure this could be the problem) |
Re: Sip Authentication failed on Diablo
donno if it helps or not , but I noticed I managed to establish a call using open wifi system , while it failed on a WPA-PSK one ...
-- http://rzr.online.fr/q/sip |
| All times are GMT. The time now is 06:10. |
vBulletin® Version 3.8.8