I did some more reading and it seems a similar problem happened a while ago where ipv4 and v6 functionality on older kernels was buggy, it caused problems with 32-bit ipaddrinfo and snmptrapd.
That made me wonder if this Linphone problem is a bug related to initialising IPv4, I then found this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743494#20 It may be an exosip bug concerning protocol versions? You may have to patch it. Make sure you're using "SIP (UDP)" globally and TLS is disabled everywhere, for testing. On Thu, 6 Sep 2018, 21:57 Laurent Caumont, <[email protected]> wrote: > Thank you Christopher but I already saw this thread but that didn't help. > I also tried to start linphone as root with sudo but that doesn't > change the behavior. > > It seems that the port is correctly detected by nmap. > pi@raspberrypi:~ $ nmap -p 5061 sip.linphone.org > > Starting Nmap 7.40 ( https://nmap.org ) at 2018-09-06 22:50 CEST > Nmap scan report for sip.linphone.org (91.121.209.194) > Host is up (0.048s latency). > rDNS record for 91.121.209.194: sip1.linphone.org > PORT STATE SERVICE > 5061/tcp open sip-tls > > Nmap done: 1 IP address (1 host up) scanned in 0.46 seconds > > > Regards, > Laurent > Le jeu. 6 sept. 2018 à 11:34, Christopher Woods > <[email protected]> a écrit : > > > > This seems like it may be an old bug, try: > > > > usermod -aG plugdev lolo > > > > Then log out and log back in. > > > > > https://askubuntu.com/questions/866453/linphone-could-not-start-tls-transport-on-port-5060-maybe-this-port-is-already > > > > Regards > > Chris > > > > On Thu, 6 Sep 2018, 07:53 Laurent Caumont, <[email protected]> wrote: > >> > >> Hi, > >> > >> > >> I tried several options (TCP, stun...) without success. It always > complain about the port number. > >> With IPv6 option, it doesn't complain but is not able to register. > >> I also opened port 5061 on my internet provider box and set it in > linphone. No success. > >> > >> On my local netdb.h file, -9 is > >> EAI_ADDRFAMILY The specified network host does not have any network > addresses in the requested address family. > >> > >> What does that mean? > >> > >> Regards > >> > >> > >> Le jeu. 6 sept. 2018 01:59, Aymeric Moizard <[email protected]> a > écrit : > >>> > >>> Hi! > >>> > >>> You should check the meaning of the return code for getaddrinfo which > is "-9". > >>> > >>> This will tell you why it fails or at least will help you to make > progress on a fix. > >>> > >>> Aymeric > >>> > >>> Le mer. 5 sept. 2018 à 22:19, Laurent Caumont <[email protected]> a > écrit : > >>>> > >>>> Hello, > >>>> > >>>> I'm trying to make linphone work on my Linux computers. > >>>> I tried on my raspberry pi 3 and on my ubuntu laptop. > >>>> Both report that the port 5060 can't be used. > >>>> I tried several other values without success. > >>>> I'm using the 3.6.1 version. > >>>> > >>>> It works fine on my android on the same network. > >>>> Any idea how to fix that ? > >>>> > >>>> Thanks > >>>> Regards, > >>>> Laurent > >>>> > >>>> pi@raspberrypi:~ $ uname -a > >>>> Linux raspberrypi 4.14.62-v7+ #1134 SMP Tue Aug 14 17:10:10 BST 2018 > armv7l GNU/Linux > >>>> > >>>> lolo@lolo-1025C:~$ uname -a > >>>> Linux lolo-1025C 4.15.0-33-generic #36-Ubuntu SMP Wed Aug 15 13:44:35 > UTC 2018 i686 i686 i686 GNU/Linux > >>>> > >>>> > >>>> here is the log: > >>>> message: Using (r/w) config information from .linphonerc > >>>> message: Initializing LinphoneCore 3.6.1 > >>>> message: oRTP-0.22.0 initialized. > >>>> message: assigning PCMU/8000 payload type number 0 > >>>> message: assigning GSM/8000 payload type number 3 > >>>> message: assigning PCMA/8000 payload type number 8 > >>>> message: assigning speex/8000 payload type number 110 > >>>> message: assigning speex/16000 payload type number 111 > >>>> message: assigning speex/32000 payload type number 112 > >>>> message: assigning telephone-event/8000 payload type number 101 > >>>> message: assigning G722/8000 payload type number 9 > >>>> message: assigning H263/90000 payload type number 34 > >>>> message: assigning theora/90000 payload type number 97 > >>>> message: assigning H263-1998/90000 payload type number 98 > >>>> message: assigning MP4V-ES/90000 payload type number 99 > >>>> message: assigning H264/90000 payload type number 102 > >>>> message: assigning VP8/90000 payload type number 103 > >>>> message: assigning x-snow/90000 payload type number 96 > >>>> message: assigning iLBC/8000 payload type number 100 > >>>> message: assigning AMR/8000 payload type number 104 > >>>> message: assigning AMR-WB/16000 payload type number 105 > >>>> message: assigning 1015/8000 payload type number 106 > >>>> message: assigning G726-16/8000 payload type number 107 > >>>> message: assigning G726-24/8000 payload type number 108 > >>>> message: assigning G726-32/8000 payload type number 109 > >>>> message: assigning G726-40/8000 payload type number 113 > >>>> message: assigning AAL2-G726-16/8000 payload type number 114 > >>>> message: assigning AAL2-G726-24/8000 payload type number 115 > >>>> message: assigning AAL2-G726-32/8000 payload type number 116 > >>>> message: assigning AAL2-G726-40/8000 payload type number 117 > >>>> message: assigning SILK/8000 payload type number 118 > >>>> message: assigning SILK/12000 payload type number 119 > >>>> message: assigning SILK/16000 payload type number 120 > >>>> message: assigning SILK/24000 payload type number 121 > >>>> message: assigning G729/8000 payload type number 18 > >>>> message: assigning mpeg4-generic/22050 payload type number 122 > >>>> message: assigning mpeg4-generic/44100 payload type number 123 > >>>> message: assigning opus/48000 payload type number 124 > >>>> message: assigning 1016/8000 payload type number 1 > >>>> message: assigning GSM/8000 payload type number 3 > >>>> message: assigning G723/8000 payload type number 4 > >>>> message: assigning LPC/8000 payload type number 7 > >>>> message: assigning PCMA/8000 payload type number 8 > >>>> message: assigning G722/8000 payload type number 9 > >>>> message: assigning L16/44100 payload type number 10 > >>>> message: assigning L16/44100 payload type number 11 > >>>> message: assigning G729/8000 payload type number 18 > >>>> message: assigning H261/90000 payload type number 31 > >>>> message: assigning MPV/90000 payload type number 32 > >>>> message: assigning H263/90000 payload type number 34 > >>>> message: Mediastreamer2 2.9.1 (git: 2.9.0-7-g51d3c20) starting. > >>>> message: ms_base_init() done > >>>> message: Registering all soundcard handlers > >>>> message: Card 'ALSA: default device' added > >>>> warning: Could not attach mixer to card: Argument invalide > >>>> warning: Strange, sound card HDA Intel does not seems to be capable > of anything, retrying with plughw... > >>>> message: Card 'ALSA: HDA Intel' added > >>>> message: Card 'PulseAudio: default' added > >>>> message: New PulseAudio context state: PA_CONTEXT_CONNECTING > >>>> message: Registering all webcam handlers > >>>> message: New PulseAudio context state: PA_CONTEXT_AUTHORIZING > >>>> message: New PulseAudio context state: PA_CONTEXT_SETTING_NAME > >>>> message: New PulseAudio context state: PA_CONTEXT_READY > >>>> message: Webcam V4L2: /dev/video0 added > >>>> message: Webcam StaticImage: Static picture added > >>>> message: ms_voip_init() done > >>>> message: Loading ms plugins from > [/usr/lib/i386-linux-gnu/mediastreamer/plugins] > >>>> message: Cannot open directory > /usr/lib/i386-linux-gnu/mediastreamer/plugins: Aucun fichier ou dossier de > ce type > >>>> message: Cannot open directory /usr/lib/liblinphone/plugins: Aucun > fichier ou dossier de ce type > >>>> message: linphone_core_set_playback_gain_db(): no active call. > >>>> message: linphone_core_set_mic_gain_db(): no active call. > >>>> message: MTU is supposed to be 1300, rtp payload max size will be 1240 > >>>> message: Could not find encoder for 1016 > >>>> message: Could not find decoder for 1016 > >>>> message: Could not find encoder for GSM > >>>> message: Could not find decoder for GSM > >>>> message: Could not find encoder for G723 > >>>> message: Could not find decoder for G723 > >>>> message: Could not find encoder for LPC > >>>> message: Could not find decoder for LPC > >>>> message: Could not find encoder for G729 > >>>> message: Could not find decoder for G729 > >>>> message: Could not find encoder for iLBC > >>>> message: Could not find decoder for iLBC > >>>> message: Could not find encoder for telephone-event > >>>> message: Could not find decoder for telephone-event > >>>> message: Could not find encoder for AMR > >>>> message: Could not find decoder for AMR > >>>> message: Could not find encoder for AMR-WB > >>>> message: Could not find decoder for AMR-WB > >>>> message: Could not find encoder for 1015 > >>>> message: Could not find decoder for 1015 > >>>> message: Could not find encoder for SILK > >>>> message: Could not find decoder for SILK > >>>> message: Could not find encoder for SILK > >>>> message: Could not find decoder for SILK > >>>> message: Could not find encoder for SILK > >>>> message: Could not find decoder for SILK > >>>> message: Could not find encoder for SILK > >>>> message: Could not find decoder for SILK > >>>> message: Could not find encoder for mpeg4-generic > >>>> message: Could not find decoder for mpeg4-generic > >>>> message: Could not find encoder for mpeg4-generic > >>>> message: Could not find decoder for mpeg4-generic > >>>> message: Could not find encoder for H261 > >>>> message: Could not find decoder for H261 > >>>> message: Could not find encoder for MPV > >>>> message: Could not find decoder for MPV > >>>> message: Could not find encoder for x-snow > >>>> message: Could not find decoder for x-snow > >>>> message: Could not find encoder for H264 > >>>> message: TLS server method > >>>> warning: no system certificate loaded > >>>> error: eXosip: Couldn't read CA list > >>>> error: eXosip: DH_generate_parameters_ex failed! > >>>> message: eXosip: Trusted CA folder : '/etc/ssl/certs' > >>>> warning: no system certificate loaded > >>>> message: getaddrinfo failure. 0.0.0.0:5061 (-9) > >>>> warning: Could not start tls transport on port 5061, maybe this port > is already used. > >>>> message: Local interface to reach 87.98.157.38 is 192.168.1.104. > >>>> message: Local interface to reach 87.98.157.38 is 192.168.1.104. > >>>> message: New local ip address is 192.168.1.104 > >>>> message: Network state is now [UP] > >>>> message: Local interface to reach sip.linphone.org is 192.168.1.104. > >>>> error: wrong state: create transport layer first > >>>> error: wrong state: create transport layer first > >>>> error: wrong state: create transport layer first > >>>> message: allocating transaction resource 1 1322765239 > >>>> message: Local interface to reach 87.98.157.38 is 192.168.1.104. > >>>> _______________________________________________ > >>>> Linphone-users mailing list > >>>> [email protected] > >>>> https://lists.nongnu.org/mailman/listinfo/linphone-users > >>> > >>> _______________________________________________ > >>> Linphone-users mailing list > >>> [email protected] > >>> https://lists.nongnu.org/mailman/listinfo/linphone-users > >> > >> _______________________________________________ > >> Linphone-users mailing list > >> [email protected] > >> https://lists.nongnu.org/mailman/listinfo/linphone-users > > > > _______________________________________________ > > Linphone-users mailing list > > [email protected] > > https://lists.nongnu.org/mailman/listinfo/linphone-users > > _______________________________________________ > Linphone-users mailing list > [email protected] > https://lists.nongnu.org/mailman/listinfo/linphone-users >
_______________________________________________ Linphone-users mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/linphone-users
