2007/9/12, Stefan Leuenberger <[EMAIL PROTECTED]>: > For SIPS/TLS transport, NUA establishes a listening socket on the transport > address specified in NUTAG_URL (IP and port) when calling nua_create(). > > The registration request to the proxy contains this transport address and > establishes the correct AOR in the proxy. > > The stack keeps the TCP/TLS connection - established to send the REGISTER > request – up using keep-alives. This would allow the proxy to reuse this > connection to send an INVITE request as proposed by RFC 3261, section > 26.3.2.1. > > The problem is that the nua uses an ephemeral port for the initial TCP/TLS > connection (to send the REGISTER request). Thus the proxy does not reuse the > existing connection but establishes a new one to the port specified in the > REGISTER request. Now the phone must act as TLS server side and we would > like to prevent this. The initial connection shall be reused for all > messages and the phone shall *always* act as a TLS client that establishes > the connection to the server.
So you don't want to have tls server socket there, but rather specify Contact URL that matches the local socket address? > Is it possible to force the stack to use a specific port without falling > back to the NTA interface? Currently, I'm afraid that answer is almost always no. If your proxy fills in rport and received on the topmost via even if you are using TCP, then it might work. Perhaps you have to be behind a NAT even then. The setup that you describe is certainly interesting but it requires some work in nta and perhaps in nua/outbound.c, too. -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
