Robert Moskowitz wrote:
Well, of course this is going to fail for me, as they only have an IPv4
address. STUN does not make much sense in a strickly IPv6 environment.
I want to turn STUN off completely, but there is no dialog that shows the
STUN servers. It least where I have looked. There is the Advanced
feature for SIP accounts to specify a proxy, but not really the same
So of course I have to wait for the timeout of looking up an IPv4 address...
I did not explain myself clearly, my bad.
We are not using STUN (not unless you explicitly enable it by setting
the STUN_SERVER_ADDRESS config property). We are not even contacting the
stun.iptel.org host in any way. We were simply planning on maybe using
it one day as an example of an Internet connected host. This is now
deprecated as we have better, destination dependent mechanisms for local
address selection. (that's the part I missed in my previous mail)
Therefore, the only thing that you are probably having a problem with is
that once you start the application you'll have to wait for the DNS
query to expire before being able to use the NetworkAddressManager, or
in other words, before being able to actually make a call. Note that
this would only happen if you have a DNS server that is not responding.
Is this your case?
Anyways, that's an easy fix. The code is a vestige of previous
intentions and it's completely disposable. I can fix it next week if you
could open an entry in our issue tracker.
I cannot find any option for controlling what STUN servers are used.
How do I disable this.
Also I would like to turn off IPv4 entirely, can this be done?
Try removing any IPv4 addresses from your interfaces. This should do it.
First you cannot remove IPv4 from l0, so you always have IPv4 in the
kernel. It is too baked into Linux.
True, but that one wouldn't have been a problem anyway.
Then I am working with the HIPL implementation of the HIP protocol for
security and mobility. I am storing the HIP HI records in my DNS along
with the AAAA records, and using the hipdnsproxy app to allow 'legacy'
(read non-HIP aware) apps to run over HIP. Thing is that hipdnsproxy
will not only generate the HIT from the HI RR and pass that on to the
app so that an IPv6 app is fat and happy and not even know it is running
over HIP (A HIT is an ORCHID IPv6 address), hipdnsproxy also generates
an LSI from the HI RR so that IPv4 apps (like TightVNC) will work over
HIP over IPv6.
This means that even though the source and target hosts do not have
routable IPv4 addresses, they have 'Local Scope Identities' that an IPv4
app believes are IPv4 address (in fact the HIPL code uses addresses like
22.214.171.124 as a destination address with 126.96.36.199 as the source address). So
an app that is both IPv4 and IPv6 and tries IPv4 first will use the LSI
shim when I want it to use HITs and work as an IPv6 app. So I look for a
'switch' in an app to force it to use IPv6 and ignore any IPv4 addresses.
OK, then in this case all you need to do is to specify that you'd prefer
to try AAAA DNS resolution before going for IPv4. There's a java
property that allows you to do this:
If you are running SC from one of the installation packages then you'd
need to modify your sip-communicator.sh file. On the line that actually
executes SC, add
somewhere before "net.java.sip.communicator.launcher.SIPCommunicator".
You'll see other similar properties being set there so just paste it
between two of them.
If you are running from sources, then simply grep for the following in
the build.xml file:
and change it to:
Hope this helps
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com