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
 

I've had Gizmo up and running from the N810 pretty well. I thought it was maybe a Ekiga problem -- but I also have fine connectivity to Ekiga via a desktop that is sitting on the same NAT'd network (though running the Ekiga app). Like you, I take pains to make sure only a single agent is logged in at a time.

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