Re: Sip Authentication failed on Diablo
 

Lon, you may well be right. It's not a STUN issue.
Have a look at that thread:
http://www.gossamer-threads.com/list...velopers/35572
I think we 1und1 users might be in a similar position.

/b.

Re: Sip Authentication failed on Diablo
 

I've tried the settings quoted above for my callcentric account, and yet it still says "Network Error", even when I put the N810 as the DMZ device. Any other advice on how to debug this?

tarek : )

Re: Sip Authentication failed on Diablo
 

I think username is wrong. I also use callcentric and my login/password for SIP are different from the phone number and (I think) web-admin login/password. You might want to double-check with callcentric support as to what to use.

Re: Sip Authentication failed on Diablo
 

I am 1und1 user too :-(
Is there any solution/workaround out there now?

If it works for chinook - I cannot understand why it is not possible to get it working for diablo. Has anyone contacted the developers of according packages?

Re: Sip Authentication failed on Diablo
 

Hmm .. I have just discovered that I can login to my 1und1 account from my neighbors internet connection (it is telekom dsl).

That should help to solve the problem - should not? Perhaps it is a matter of correct configuration of the router. Any idea?

How can I tunnel all the network traffic of my n810 to server x (for testing)?

Re: Sip Authentication failed on Diablo
 

after testing for a while i am nearly sure that it is not a problem with 1und1! the problem is the router 1und1 is shipping with a contract. it has voip capabilities using similar ports needed by maemo phone software.

is there anyone out there who can help me going further?

Re: Sip Authentication failed on Diablo
 

I also think these two are linked (sip-client on n800 and on router), but before diablo, both sip clients worked side by side allowing n800-sip inside an fritz.box-sip network.
So there must be some change in diablo that prevents this now. Might be a bugfix though...

Re: Sip Authentication failed on Diablo
 

I am using voxalot now. It is great. Just works :)

Re: Sip Authentication failed on Diablo
 

it's a german problem, ...maybe.

I'm using:
a N800, OS2008 (diablo?) Ver. 4.2008.36-5.

"Internetanruf" doesn't connect to Ekiga when i stay behind an Asus WL500GP router.
At work i could connect. But i haven't tried calling yet.

My configuration:
Benutzername: [p******k] @ [ekiga.net]
Kennwort: [**************]
PSTN-Anrufe [aktiv]

Erweitert:
(Verbindung)
Transport: [Automatisch]
Ausgehender Proxy: [ekiga.net]
Port: [5060]
Öff. Adr. erkennen: [Aktiv]
Keepalive-Mech.: [Automatisch]
Keepalive-Freq.: [0]

(Authentifizierung)
Authentifizierung-Benutzername: [p******k]
Kennwort: [**************]

(STUN)
Automatische STUN-Erkennung: [Aktiv]
STUN-Server:
STUN-Port:



Ekiga's Software using on a PC does connect from behind my Router.
Tomorrow at work I will check, if connecting will work while using a STUN-Server (maybe stun.ekiga.net) - without "Automatische STUN-Erkennung".

Re: Sip Authentication failed on Diablo
 

I changed the values of “Öff. Adr. erkennen” to false and
“Automatische STUN-Erkennung” to false. So I set ekiga.net as stun server and port to 3478. it does connect at work.

edit: i'm able to talk to 500@ekiga.net.