Home / Browse / Sofia-SIP / Tracker / Bugs / View

Sofia-SIP

Tracker: Bugs

5 Registration to Ekiga.net fails - ID: 2412241

Last Update: Comment added ( kxra )

Details:

The Ekiga.net checks during registration that both the Via and Contact headers contain a public IP address. The registation fails with 606 if the Via header contains a NATted address from the private address space.

Submitted:

Pekka Pessi ( ppessi ) - 2008-12-09 10:06:22 PST

Priority:

Status:

Open

Resolution:

None

Assigned:

Pekka Pessi

Category:

None

Group:

None

Visibility:

Public

Comments ( 12 )

Date: 2012-03-28 09:09:07 PDT Sender: kxra Any updates?
Date: 2010-07-19 08:39:48 PDT Sender: gehrehmee Reported against ekiga's bug tracker at: https://bugzilla.gnome.org/show_bug.cgi?id=624751
Date: 2010-07-19 08:33:51 PDT Sender: gehrehmee Affecting Ubuntu via https://bugs.launchpad.net/ekiga/+bug/294994 , debian via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535796 , both via telepathy-sofiasip on https://bugs.freedesktop.org/show_bug.cgi?id=19328
Date: 2010-01-21 09:34:52 PST Sender: jbrnd I'm not 100% sure I did everything correctly, but using sofia-sip trunk didn't change anything for me.
Date: 2009-11-13 08:26:09 PST Sender: mzabaluev What do you know, it works for me with the sofia-sip build we use in Maemo 5. Can somebody else confirm if it works with sofia-sip trunk?
Date: 2009-10-15 04:47:41 PDT Sender: mzabaluev > So, if the problem is with ekiga.net, has anyone contacted them about it yet? Sort of; last word I heard from them is, they need this restriction so that their own client keeps working. I still think they shouldn't impose a restriction on the address in Via, and sofia-sip should now re-register with a discovered mapped address in Contact. I didn't press this last comment to them yet, though.
Date: 2009-10-12 22:50:34 PDT Sender: murrayc So, if the problem is with ekiga.net, has anyone contacted them about it yet?
Date: 2009-06-08 06:54:45 PDT Sender: mzabaluev I reverse my stance from the earlier comments The modification of transport address in Via may cause interoperability problems with proxies that implement support for RFC 3581 and rely on the specified behavior for NAT-aware policies. The restriction imposed by the proxy is arbitrary. It does not follow any specification or best practice published by IETF that I'm aware of. The answer is, fix the proxy.
Date: 2009-04-09 02:51:22 PDT Sender: riot69 Maemo downstream ticket: https://bugs.maemo.org/show_bug.cgi?id=4259
Date: 2009-03-03 10:49:13 PST Sender: mzabaluev It shouldn't be an interop problem to put the public transport address in the client's Via. When the binding breaks, the proxy should signal it with rport and received which will be different from the address in Via.
Date: 2008-12-10 05:17:01 PST Sender: mzabaluev >The UA application must take care of the contact address by: >-Using some kind of STUN mechanism >- Learning from the REGISTER response ( checking the Via parameters ) and reusing a new REGISTER Sure, we do the latter, but the ekiga.net proxy rejects this REGISTER with 606 Not Acceptable.
Date: 2008-12-09 11:48:51 PST Sender: incarose Why do you think this is a sofia-sip problem ? There is nothing wrong whit that. Ekiga SIP server will end up sending the response to the udp-src address ignoring the Via host address. The UA application must take care of the contact address by: -Using some kind of STUN mechanism - Learning from the REGISTER response ( checking the Via parameters ) and reusing a new REGISTER - or not taking care at all and failing to get incoming calls.

Sofia-SIP

Tracker: Bugs

Comments ( 12 )

Attached File

No Files Currently Attached

Change

No changes have been made to this artifact.