[jitsi-dev] SIP Via/Contact headers have wrong IP address on multhomed Mac


#1

Boris,

:Could be related to the change of the JVM version, although I do not
:know how exactly.
:See http://lists.jitsi.org/pipermail/dev/2014-November/022689.html

If there's no reliable way of doing this in a Java context, how
possible would it be for there to be an account knob to specify the
interface used, then? I always know I want to talk to Account X over
whatever IP address corresponding to interface en0, for example, so
can "src interface" be added as a proxy configuration option?

I'm surprised that Java6 (which appears to be what my old Jitsi has
baked in it) got this right while newer Java does not. I would've
expected some sort of "netstat"-ish API. Ideally, I'd want Jitsi to
figure this out all by itself -- use the interface for populating
those SIP fields that corresponds to "route get [sip proxy]" (in a
Mac/BSD context, "ip route get [sip proxy]" in a Linux context, etc.).
But I'd settle for being able to hardcode it.

Make sense?
-Mike

···

--
Michael J. O'Connor mjo@dojo.mi.org
=--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=
"Archimedes made the first steamboat and power drill." -Non Campus Mentis


#2

Boris,

:Could be related to the change of the JVM version, although I do not
:know how exactly.
:See http://lists.jitsi.org/pipermail/dev/2014-November/022689.html

If there's no reliable way of doing this in a Java context, how
possible would it be for there to be an account knob to specify the
interface used, then? I always know I want to talk to Account X over
whatever IP address corresponding to interface en0, for example, so
can "src interface" be added as a proxy configuration option?

Delegating this choice to the user would solve only a very small
percentage of the occurrences since most of the time people won't know
what to answer. We'd rather have something automated here.

I'm surprised that Java6 (which appears to be what my old Jitsi has
baked in it) got this right while newer Java does not. I would've
expected some sort of "netstat"-ish API. Ideally, I'd want Jitsi to
figure this out all by itself -- use the interface for populating
those SIP fields that corresponds to "route get [sip proxy]" (in a
Mac/BSD context, "ip route get [sip proxy]" in a Linux context, etc.).
But I'd settle for being able to hardcode it.

That's exactly what we do. Apparently it is failing in the new Jitsi
stable. This could be due to Java 7 or something else. We should have
a look in the following days since many people are seeing the issue.

Emil

···

On Fri, Feb 6, 2015 at 1:15 AM, Mike O'Connor <mjo@dojo.mi.org> wrote:

Make sense?
-Mike

--
Michael J. O'Connor mjo@dojo.mi.org
=--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--==--=
"Archimedes made the first steamboat and power drill." -Non Campus Mentis

_______________________________________________
dev mailing list
dev@jitsi.org
Unsubscribe instructions and other list options:
http://lists.jitsi.org/mailman/listinfo/dev

--
https://jitsi.org