-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Salutations,
I recently installed linphone and found I would get an error on startup: - ----- Could not start tls transport on port 50656, maybe this port is already used. - ----- Several things there, I thought SIP with TLS usually used port 5061. Furthermore, upon inspection the linphone is not compiled with the flag "with-ssl" in the PKGBUILD. I added that flag myself, but still get the same error. Any idea what's going on with the TLS transport?
Regards, Mark
On Sun, Jun 1, 2014 at 12:05 AM, Mark Lee mark@markelee.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Salutations,
I recently installed linphone and found I would get an error on startup:
Could not start tls transport on port 50656, maybe this port is already used.
Several things there, I thought SIP with TLS usually used port 5061. Furthermore, upon inspection the linphone is not compiled with the flag "with-ssl" in the PKGBUILD. I added that flag myself, but still get the same error. Any idea what's going on with the TLS transport?
Regards, Mark
See FS#39956 [1] and the thread [2] at linphone devel. Workaround has been mentioned in [3]: add sip_tls_port=0 to the [sip] section in the .linphonerc
[1] https://bugs.archlinux.org/task/39956 [2] https://lists.nongnu.org/archive/html/linphone-developers/2014-04/msg00076.h... [3] http://lists.gnu.org/archive/html/linphone-users/2014-03/msg00039.html
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 06/01/2014 03:35 AM, Lukas Jirkovsky wrote:
On Sun, Jun 1, 2014 at 12:05 AM, Mark Lee mark@markelee.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
Salutations,
I recently installed linphone and found I would get an error on startup:
Could not start tls transport on port 50656, maybe this port is already used.
Several things there, I thought SIP with TLS usually used port 5061. Furthermore, upon inspection the linphone is not compiled with the flag "with-ssl" in the PKGBUILD. I added that flag myself, but still get the same error. Any idea what's going on with the TLS transport?
Regards, Mark
See FS#39956 [1] and the thread [2] at linphone devel. Workaround has been mentioned in [3]: add sip_tls_port=0 to the [sip] section in the .linphonerc
[1] https://bugs.archlinux.org/task/39956 [2] https://lists.nongnu.org/archive/html/linphone-developers/2014-04/msg00076.h... [3] http://lists.gnu.org/archive/html/linphone-users/2014-03/msg00039.html
Salutations,
Is there any particular reason why polarssl isn't in the official repos? Also, I looked at the bug report and it is strange that the severity of the bug is marked very low. Isn't this a security issue?
Regards, Mark
arch-general@lists.archlinux.org