Re: [GnomeMeeting-list] Avahi Howto?
- From: Damien Sandras <dsandras seconix com>
- To: GnomeMeeting mailing list <gnomemeeting-list gnome org>
- Subject: Re: [GnomeMeeting-list] Avahi Howto?
- Date: Fri, 07 Apr 2006 17:20:49 +0200
Le vendredi 07 avril 2006 à 16:54 +0200, Jan Kasprzak a écrit :
> Jan Kasprzak wrote:
> : Hi all,
> :
> : is there any howto on what to do in order to use avahi with ekiga?
> [...]
> : My system is Fedora Core 5. Thanks,
>
> Hmm, despite being linked against avahi libraries, Ekiga in FC5
> is not compiled with avahi support. Sorry for the noise.
>
> However, there is another problem - my coworker uses Gizmo,
> and I can see him in the "Contacts near me" address list. I can
> "right-click + call contact" on the address book, but his line
> is somewhat different than other lines - his line in the address book
> has the following fields:
>
> Name: sip:<nickname>@proxy01.sipphone.com:5060
> Software: <empty>
> VoIP URL: sip:<his local IP address>:64064
>
> so when I do "right-click -> Add contact to the address book", I have
> his real SIP address stored as a "name", and his temporary address
> (the IP on the local net he is currently using) is stored as a
> "VoIP URL". This is probably wrong, because the later could change
> any time, while the former (sip:<nickname>@proxy01.sipphone.com:5060)
> is - I think - permanent.
>
There is nothing we can do about that.
The VoIP URL published by Gizmo is the local IP + local port, so that
you can call the user "locally". The Name published by GIZMO is the
public SIP URL, which is wrong and typical of GIZMO. Ekiga publishes
your real name, as you can see.
We can not add specific behaviors from specific software to the "Add
contact" menu.
Notice also that if the user is reachable through the "Contacts Near Me"
address book section using the local IP, he is not necessarily reachable
using <nickname>@proxy01.sipphone.com:5060 from inside your LAN. If
GIZMO registers his public IP and public port obtained from STUN to
proxy01.sipphone.com, it is very possible that your NAT router doesn't
redirect packets coming from the inside and going to the public
port/public interface, to the internal destination.
--
_ Damien Sandras
(o-
//\ Ekiga Softphone: http://www.ekiga.org/
v_/_ FOSDEM 2006 : http://www.fosdem.org/
SIP Phone : sip:dsandras ekiga net
sip:600000 ekiga net
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]