<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#333333">
Hi,<br>
<br>
<br>
Apparently, and for the archives, force_tcp_alias() is the solution
for connection reuse.<br>
<br>
Damien<br>
<br>
Le 05/07/13 17:33, Damien Sandras a écrit :
<blockquote cite="mid:51D6E767.2010601@seconix.com" type="cite">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
Hi,<br>
<br>
I have a question about TCP connection reuse.<br>
<br>
Let's imagine a phone that REGISTERs to OpenSIPS using TCP.
tcp_persistent_flag is enabled, and the appropriate setflag is
called a bit before the save function.<br>
<br>
The phone creates a TCP connection with source port 55555 (for
example) to OpenSIPS port 5060, but indicates a Contact field with
its IP address and port 5060 (not port 55555).<br>
<br>
Before the REGISTER occurs, OpenSIPS already knew the IP address
of the phone and was relaying OPTIONS requests with a separate TCP
connection (say OpenSIPS source port 123456 and phone destination
port 5060).<br>
<br>
When relaying new requests (OPTIONS, NOTIFY, INVITE), should
OpenSIPS use the registrar connection ?<br>
It seems to me that it reuses the previous TCP connection to phone
port 5060 or that it creates a new one to phone port 5060 instead
of reusing the registrar connection.<br>
<br>
I had in mind that with TCP, we could ignore the Contact field in
the REGISTER request and reuse the same connection.<br>
<br>
Is there some flag or variable I should change ?<br>
<br>
Thanks,<br>
<br>
Damien<br>
<br>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">This body part will be downloaded on demand.</pre>
</blockquote>
<br>
</body>
</html>