Hi all,
I have a question concerning SIPS and TCP ports:
We use Sofia SIP V1.12.6 for an IP Phone supporting multiple accounts,
each account uses its own nua instance on a different port. The port is
set by specifying NUTAG_URL in the nua_create() call.
This works fine for UDP transport. NUA sends requests from the transport
address specified in NUTAG_URL and receives responses on this transport
address.
Plain TCP transport is not a requirement and thus not considered.
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.
Is it possible to force the stack to use a specific port without falling
back to the NTA interface?
Thanks for your help
Stefan
-------------------------------------------------------------------------
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
