On 14/03/12 10:57, Vineet Menon wrote:
Hi,
Ya, I noticed it too..... but didn't pay heed to it!!
But what can I do now?? I mean to prevent this from happening??
I really don't know from where ekiga is getting that ip!! 0.0.0.0
There were so many changes on notify system between 3.2.7 and the
current version that I prefer to ask you if you can test with the newest
version, especially that you compiles ekiga yourself. So please try
master/trunk from http://wiki.ekiga.org/index.php/Download_Ekiga_sources
and if the problem is still there we will look deeper into it.
On 14 March 2012 15:20, Reda Aouad<reda.ao...@gmail.com> wrote:
Your other UA at 33.236 is also broadcasting a SIP NOTIFY neighbor@0.0.0.0in
packets 1-4.
It seems Ekiga is not binding to the correct interface...
I suspect more a network problem than a SIP one.
Reda
On Wed, Mar 14, 2012 at 10:24, Vineet Menon<mvineetme...@gmail.com>wrote:
Hi,
I just installed kamailio for my sip testing. I am using it for simple
registrar purposes...
The config file is default file with debugging enabled.
I registered 2 UAs with kamailio, but am not able to call using aor
dialing.
I inspected packets with wireshark, which i think is a bit problematic.
my server's at 31.21.33.238, while UAs are at 31.21.33.250 and
31.21.33.236.
I have attached the wireshark file for packets. see packet number.5 and
7. Why has ekiga put the from field as ip:0.0.0.0.??? Isn't der something
wrong here???
_______________________________________________
ekiga-devel-list mailing list
ekiga-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/ekiga-devel-list