[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: TCP/TLS support in current (>5.0) eXosip releases

From: Aymeric Moizard
Subject: Re: TCP/TLS support in current (>5.0) eXosip releases
Date: Wed, 23 Feb 2022 16:51:45 +0100

Hi David!

I'm really sorry for this change.

It is correct that there is no default option to have ENABLE_MAIN_SOCKET in configure. This is mostly because exosip, smash you've understood, is meant to always create and maintain the connection in client dev.

You can definitely just add it in cflag to compile and it should work the same way it was before.

This code is not tested much, but you shouldn't have new issue with it.


Le mer. 23 févr. 2022 à 15:27, David Sugar <tychosoft@gmail.com> a écrit :
I think I figured it out.  TCP mode is only usable in client mode currently. I was expecting to see a bound tcp listener because I used eXosip_listen_addr(), but apparently that is not true anymore.

SipWitchQt actually had a hard requirement for a bound TCP listener, but I already vendor eXosip2 in it, so I can have that locally build with ENABLE_MAIN_SOCKET. Most of my more recent stuff actually does not, so until I noticed there was no bound socket, I did not even realize this change :). For example, in coventry, I want to do upstream/trunking as sip tcp, but even there I only look like a client registering to an upstream provider.

On Wed, 2022-02-23 at 08:48 -0500, David Sugar wrote:
There is a define now in the eXosip2 sources, "ENABLE_MAIN_SOCKET".  There did not seem to be any configure option for doing this at build time.  It also appears that support for TCP/TLS sip is effectively dead thru eXosip_listen_addr as the socket is never bound nor listen() called unless this is set.  This define also touches epoll behavior a small bit in eXtl_udp.c.

Is this safe to enable/inject at build time?  How else would one even get a working tcp sip service again without it? Should this be a configure option? I know I used to be able to use tcp with eXosip2 in earlier (?4.0?) releases and it worked back then, with some interesting limitations related to connection reuse.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]