On Fri, 01 Apr 2011 17:57:47 +0200, Simon Morlat
<[email protected]> wrote:
Hi Liviu,
Not related to alsa at all, but the bad consequence of this:
linphone-error : eXosip: Cannot bind socket node:0.0.0.0 family:2
Address already in use
linphone-error : eXosip: Cannot bind on port: 5060
Apparently another program is using port 5060.
Indeed, this is the issue. After a reboot I get this
root@liv-laptop:/home/liv# netstat -ltupn | grep 5060
udp 0 0 0.0.0.0:5060
0.0.0.0:* 1785/sipw
It turns out that I installed sipwitch and that the daemon (or whatever
that is) starts at boot and attaches itself to the same port that Linphone
uses. After I terminated sipw Linphone started again as expected.
As a temp solution, I'll probably remove sipwitch. But does this amount to
normal interaction between the two? Or can I avoid the conflict? Regards
Liviu
However it should not crash so I'm fixing for this part.
Simon
Le mardi 29 mars 2011 à 11:50 +0200, Liviu Andronic a écrit :
On Tue, 29 Mar 2011 11:40:12 +0200, Liviu Andronic <[email protected]>
wrote:
> If I'm starting with a clean profile it generates the same pop-up
message
> (see attached shot), but doesn't crash (see second log).
>
liv@liv-laptop:~$ linphone --verbose &> /tmp/linphone1.log
I forgot the --verbose argument. Here's a new log when using a clean
profile and there's no crash.
Liviu
_______________________________________________ Linphone-users mailing
list [email protected]
http://lists.nongnu.org/mailman/listinfo/linphone-users
_______________________________________________
Linphone-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/linphone-users
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
Linphone-users mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/linphone-users
