[Rtcomm] [Rtcomm] [Bug 5348] Trouble connecting to Fritz!Box SIP server

[From: bugzilla-daemon at maemo.org]

https://bugs.maemo.org/show_bug.cgi?id=5348





------- Comment #16 from mikhail.zabaluev at nokia.com  2009-10-20 11:14 GMT+3 -------
(In reply to comment #15)
> > 1. Here, the Sofia-SIP stack ill-chooses an IPv6 binding in Via headers, but
> > this doesn't seem to hurt anything.
> 
> It's actually not ill-chosen. The router does speak IPv6 just fine. That's why
> it works...

Yeah, it's not technically incorrect, but the stack ought to have chosen the
IPv4 binding to put into the Via, when using an IPv4 transport.

BTW, how does the registration differ on N810?

> > 2. The first REGISTER already has an Authorization header with a password
> > digest computed on a nonce. Normally, Sofia-SIP puts this header only when
> > challenged by the proxy. Did you post the complete sequence? Were there any
> > previous connection attempts?
> 
> Yes this is the complete sequence. However, this account was configured months
> ago, so maybe Telepathy stores some data about the server? Dunno?

As far as I know the code I maintain, we don't store authentication state
between connections.
It would be interesting to see the output of telepathy-sofiasip running this
case for Empathy in the following environment:

TPSIP_DEBUG=all
NUA_DEBUG=7
TPORT_LOG=1

It's possible to run telepathy-sofiasip from the command line with DBus session
bus variables set up, with TPSIP_PERSIST=1 added to the environment.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=5348
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.