The first one to be tried (q=1) is a public one. There is indeed also a private one, but with a lower priority. I rather suspect interoperability issue here, than a real bug in ekiga.
Still, it's true I've also seen cases where the issue is there is only 1 private address (most of time due to router policy), but it is not the case here.
Funatiker,
In this particular case, ekiga provide several IPs for contact with priority order:
Contact: <sip:4994199999 99@79.209. 54.40:61224> ;q=1, <sip:4994199999 99@79.209. 54.40>; q=0.667, <sip:4994199999 99@192. 168.2.101> ;q=0.334
The first one to be tried (q=1) is a public one. There is indeed also a private one, but with a lower priority. I rather suspect interoperability issue here, than a real bug in ekiga.
Still, it's true I've also seen cases where the issue is there is only 1 private address (most of time due to router policy), but it is not the case here.
Best regards,
Yannick