Perhaps 5060 is already in use for TCP by linphone or another application.
Try 5061 instead.
On Apr 9, 2016 6:01 PM, <
address@hidden> wrote:
All,
I've been vicariously enjoying following this list since discovering Linphone, which I have successfully used (among other VoIP apps) on multiple platforms, including PCs and mobile devices. Among the key reasons to select Linphone was the innovative and open development, and the availability of ZRTP.
However, I request your collective assistance with a hopefully simple issue (and hopefully simple solution, ha ha?), regarding an evident anomaly with Linphone when installed on LINUX, at least on all flavors of MINT and Ubuntu that I have tried so far....
THE ISSUE:
Does LINUX have an incompatibility issue with Linphone for SIP(TLS)??
If so, how can I fix it? Did I miss a handy solution somewhere? Clues Please??
OBSERVATIONS:
After an evidently normal and successful installation of Linphone on LINUX, via either repository or apt-get means, Linphone is unable to access the standard port 5060 for SIP(TLS) connections. It reports the port in use?? Any attempts to use any other port results the same error messages....
SPECIFIC CLUES:
- Conventional Dell laptop, 32bits, i386, 2B RAM, 40GB HD, 1GB LAN...
- Recent/latest LINUX, including Ubuntu 14.04 or 15.10, or MINT 17.3, any flavor (Desktop, or Cinnamon, MATE, KDE...)
- Fresh installations of LINUX Ubuntu/MINT, no other additional apps installed, except standard initial updates/upgrade via apt-get.
- Linphone installed evidently successfully via repository or apt-get (tried both, same results)
- I access Options / Preferences to Settings / Network settings....
- For "Network protocol and ports" I selected SIP(TLS) and kept default port 5060
- Got error message: "Could not start tls transport on port 5060, maybe this port is already used."
- Get NO error messages if selecting SIP(UDP) or SIP(TCP), regardless of port 5060 or others...
- FYI - Using standard other default values: MTU 1300, Audio 7080, Video 9078...
- FYI - Selected "NAT and Firewall" ICE (but all selections provide same behavior, anyway)
- These standard settings all work great for all other devices in the system...
- Attempts to try SIP(TLS) using alternative ports, many randomly selected over entire range up to 64K, provides same error message.
- Likely a software bug in the LINUX version of Linphone, or a underlying LINUX bug, vice an actual port reservation issue??
THE NETWORK:
- FYI - For background of the testing environment, although unlikely to be the basic cause...
- Using multiple PCs & mobile devices, all resident on local subnet, with access to internet & sip.linphone.org
- Using various Windows XP SP3 and 7, LINUX Ubuntu 14.04 and 15.10, Android (via WiFi & celldata)
- Each device has it's own VoIP name/address for remote Linphone SIP connections using <username>@sip.linphone.org
- Each device also has it's own VoIP name/address for direct point-to-point connections <username>@<local-IP-address>
- For best results, I normally set this direct <username>@<local-IP-address> as default "My current identity".
- Thus, I can call easily both local direct IP and also via Linphone SIP servers.
- Incoming calls easily arrive via both means.
- Everybody can _usually_ call everybody, and it _usually_ all works great!
- Until I tried to test LINUX Ubuntu & MINT... <:-(
- For testing, I employed three PCs: "JOE" (LINUX MINT), "BOB" (WinXP), "VIC" (Win7), and "LOU" (LINUS Ubuntu).
SOLUTIONS??
Soooooo, can anybody here Please provide a solution, or at least some insight, into what is failing? And how to fix it?
P.S.- As a separate issue, I also note that there is NO availability of ZRTP for LINUX? Windows and Android apps provide it. Is Linphone missing or unable to do ZRTP for LINUX?? Again, Clues Please?
Thanks!
Gene :)
address@hidden
_______________________________________________
Linphone-users mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/linphone-users